No CWM recovery? - HD2 Android Q&A, Help & Troubleshooting and Genera

my hd2 is rooted and has rom manager and super user and all that good stuff. but when i go to ad recovery it doesn't load up into recovery.
is that possible that somehow i don't have CWM recovery installed?
im trying to update to an ICS rom and im guessing thats the easiest way

blackbeasst said:
my hd2 is rooted and has rom manager and super user and all that good stuff. but when i go to ad recovery it doesn't load up into recovery.
is that possible that somehow i don't have CWM recovery installed?
im trying to update to an ICS rom and im guessing thats the easiest way
Click to expand...
Click to collapse
Which ROM are you running? You DID flash whatever it was via CWM right? And it's not the easiest way to update to CWM, it's the ONLY way.

Nigeldg said:
Which ROM are you running? You DID flash whatever it was via CWM right? And it's not the easiest way to update to CWM, it's the ONLY way.
Click to expand...
Click to collapse
bought it this way. it has an older cm7 on it and i was looking to put on ICS but like i said i can't get into recovery from magldr.

blackbeasst said:
bought it this way. it has an older cm7 on it and i was looking to put on ICS but like i said i can't get into recovery from magldr.
Click to expand...
Click to collapse
Backup your apps in Titanium Backup then flash CWM. Chances are you would have needed to change the partition size anyway. After that, just flash ICS and you should be fine. Oh, also note that ROM Manager is not compatible with MAGLDR, so trying to use it could corrupt the recovery (from what I've heard) which may be where you went wrong

Nigeldg said:
Backup your apps in Titanium Backup then flash CWM. Chances are you would have needed to change the partition size anyway. After that, just flash ICS and you should be fine. Oh, also note that ROM Manager is not compatible with MAGLDR, so trying to use it could corrupt the recovery (from what I've heard) which may be where you went wrong
Click to expand...
Click to collapse
whats the latest cwm?

blackbeasst said:
whats the latest cwm?
Click to expand...
Click to collapse
V1.3 is the latest, if i am not mistaken
Sent from my HD2 using XDA

blackbeasst said:
whats the latest cwm?
Click to expand...
Click to collapse
(Didn't mean to hit thanks BTW, but you get a free thanks ) If I'm not mistaken the latest version is 5.0.2.6 although I'm using 3.0.2.5 and I really can't see the difference. 3.0.2.5 is also supposed to be the stablest version from what I've heard, but I haven't tried any others.
EDIT: Well clearly I'm wrong but I could've sworn I've seen 5.0.2.6 somewhere (it isn't something you just make up) but yeah here's the thread.
EDIT 2: Actually adil and I are both correct, 5.0.2.6 is the actual recovery version and 1.3 is the release version for the HD2 (in the same way NexusHD2 is on v2.2 whilst the actual ROM is ICS 4.0.4)

so i ran the daf.exe and got the following when trying to flash:
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (723)
i was trying it for cwm 1.2

blackbeasst said:
so i ran the daf.exe and got the following when trying to flash:
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (723)
i was trying it for cwm 1.2
Click to expand...
Click to collapse
Haven't tried it myself, but here's the fix for USB init failed. Dunno if it will work or not though.

Nigeldg said:
Haven't tried it myself, but here's the fix for USB init failed. Dunno if it will work or not though.
Click to expand...
Click to collapse
yeah i saw that. looks like its an xp thing though. im running win7 so i might have to find another route.

well i finally was able to run the daf but now it doesn't boot and says "nand kernel open failed" and kicks back to magldr.
edit: wait for it.......

blackbeasst said:
so i ran the daf.exe and got the following when trying to flash:
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (723)
i was trying it for cwm 1.2
Click to expand...
Click to collapse
I get that error too sometimes. When running DAF.exe, right click it and run it as administrator. Usually works for ne
Sent from my HD2 using XDA

blackbeasst said:
well i finally was able to run the daf but now it doesn't boot and says "nand kernel open failed" and kicks back to magldr.
edit: wait for it.......
Click to expand...
Click to collapse
Does it say that when you choose option 8. AD recovery. ?
Sent from my HD2 using XDA

looks like we have ICS! thanks nigel. that link work. it didn't have anything to do activesync. not sure why cwm wasn't working or how the previous user installed everything but i think im up and running.
thanks to you as well adil

blackbeasst said:
looks like we have ICS! thanks nigel. that link work. it didn't have anything to do activesync. not sure why cwm wasn't working or how the previous user installed everything but i think im up and running.
Click to expand...
Click to collapse
He probably used DAF.exe. No problem, glad to see you got it working

Related

Issues with clockwork recovery backup feature?

I recently did a back up if my stock mt4g using clockwork. When I went to do a restore of that rom and rebooted it stayed stuck on the mt4g load screen. Anyone else have this problem? Did I do something wrong?
Sent from my HTC Glacier using XDA App
what version of clockwork did you use to make the backup?
3.0.0.5
Sent from my HTC Glacier using XDA App
spokenjeremy said:
3.0.0.5
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Welcome to brick world, that's exactly what destroyed my phone and, like you, I was running 3.0.0.5 If you ever do get the phone working again let me know how you did it, please?
Not sent from my MyTouch 4G because it's a brick now!
xs11e said:
Welcome to brick world, that's exactly what destroyed my phone and, like you, I was running 3.0.0.5 If you ever do get the phone working again let me know how you did it, please?
Not sent from my MyTouch 4G because it's a brick now!
Click to expand...
Click to collapse
The reason your phone appears to be bricked is it (CWRM 3.0.0.5) is a ext4 recovery image, and 2.2 is a ext3 ROM....
. If you find a 2.x version of CWRM you can flash it via the ADB commands and restore the phone.
OR
boot into recovery and flash the CM7 w/ gapps then download CWRM ( the free one ) and flash 2.x that way. You'll have to scroll to the bottom and select one of the 2.x recovery images.
If you can get into Recovery or into fastboot your phone is not truly bricked.
I have CM7 installed and Rom Manager, but when i try to flash an older recovery it says it cannot be flashed. How exactly would you flash the 2.X version via ADB? Thanks.
xs11e said:
Welcome to brick world, that's exactly what destroyed my phone and, like you, I was running 3.0.0.5 If you ever do get the phone working again let me know how you did it, please?
Not sent from my MyTouch 4G because it's a brick now!
Click to expand...
Click to collapse
You nor he is bricked.
Pentlander said:
I have CM7 installed and Rom Manager, but when i try to flash an older recovery it says it cannot be flashed. How exactly would you flash the 2.X version via ADB? Thanks.
Click to expand...
Click to collapse
If you can get into CwM recovery then just flash my zip and use the 3.0.0.6 recovery that is included. Then make sure that you make/restore all backups from recovery and not rom manager. Rom manager is not compatable with CwM 3.0.0.X when it comes to making nandroids.
Thanks a lot, but i keep running into and issue at the recovery. I followed the instructions from your thread, and i got into the blue recovery screen, but it says
"E:Can't mount CACHE:recovery/command
E:Can't mount DATA:data/recovery/log"
And the only option to restore is the Applysdcard:update.zip and that fails
Pentlander said:
Thanks a lot, but i keep running into and issue at the recovery. I followed the instructions from your thread, and i got into the blue recovery screen, but it says
"E:Can't mount CACHE:recovery/command
E:Can't mount DATA:data/recovery/log"
And the only option to restore is the Applysdcard:update.zip and that fails
Click to expand...
Click to collapse
So, that is the stock recovery. You need to choose the 3.0.0.5 version from "All ClockworkMod recoveries" if using my zip. If that wont work, try sending a new recovery via fastboot or terminal emulator.
You can set up adb/fastboot by checking out the link in my sig and using the command (make sure you rename the recovery to recovery.img for ease of use)
Code:
fastboot flash recovery recovery.img
or you can try terminal method by placing the recovery on your sd card and renaming it recovery.img Then open up TE and type "su" then the flollowing
Code:
flash_image recovery recovery.img
If that doesnt work, then let me know and we will find some other things to try.
Whoops haha. Thanks for all the help it's working great now
Pentlander said:
Whoops haha. Thanks for all the help it's working great now
Click to expand...
Click to collapse
What step got it working again for you?
neidlinger said:
The reason your phone appears to be bricked is it (CWRM 3.0.0.5) is a ext4 recovery image, and 2.2 is a ext3 ROM....
If you can get into Recovery or into fastboot your phone is not truly bricked.
Click to expand...
Click to collapse
Can't do either.

CWM Problems

UPDATE: To fix 3.0.2.4 from not formatting /system
Open rom manager and select settings, and check erase recovery. hit menu again and select clear cache, then flash 3.0.2.4 again.
now if your in recovery and you cant boot back up to use rom manager, use the file below. It will allow you to restore your backup then once booted back up use the method above to fix 3.0.2.4.
The reason im leaving custom over 3.0.2.4 is bc i know fastboot flash with this one will allow you to restore without wiping recovery or clear cache or anything else.
http://www.mediafire.com/file/b8ejhqbf3tgnsoe/recovery.img - this is CMW 3.0.1.4 just altered for installing zips. linking for people needing a recover img to boot up
To install:
1. If in recovery, open ur terminal on ur pc and type adb reboot boatloader
2. Once in bootloader it will load fast boot and say fastboot usb in red
3. cd to the folder with fastboot.exe and also place recover.img in that folder
4. then enter fastboot flash recovery recovery.img
5. adb reboot recovery
6. restore your backup and boot up
RafficaX said:
Little FYI for all, cwm recovery wont format system on a restore. made a backup, tried a flash and went to restore and it fails formatting system.
So be careful with flashing and all bc yo may not be able to restore currently with cwm.
UPDATE: format system in menu also fails! be careful bc you pretty much cant restore or flash atm!
Click to expand...
Click to collapse
Oh how I miss Amon_Ra
jlevy73 said:
Oh how I miss Amon_Ra
Click to expand...
Click to collapse
im really hoping Amon_Ra does do his recovery on T-Bolt. I like Rom Manager and its features but would rather loose features for stability and reliability on each use.
RafficaX said:
im really hoping Amon_Ra does do his recovery on T-Bolt. I like Rom Manager and its features but would rather loose features for stability and reliability on each use.
Click to expand...
Click to collapse
QFT
can't wait for amon-ra
raffica, what version of CWM worked for you?
MYxdaUSERNAME said:
raffica, what version of CWM worked for you?
Click to expand...
Click to collapse
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.
Thanks for the heads up I agree I always loved CWM on my N1 but it started giving me all kinds of grief for several different reasons so I finally went to Amon Ra.
RafficaX said:
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.
Click to expand...
Click to collapse
Can you help me out and provide it because right now i cant even boot
RafficaX said:
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.
Click to expand...
Click to collapse
isnt UD banned on these forums?
just curious dont flame me or anything! cuz when a Ud rom hit the inc the thread was deleted in minutes
superchilpil said:
isnt UD banned on these forums?
just curious dont flame me or anything! cuz when a Ud rom hit the inc the thread was deleted in minutes
Click to expand...
Click to collapse
yeah, if you go on their forums all they do is flame XDA left and right. But I find it funny since their roms take advancements from XDA developers and then they incorporate it into their roms...
nosympathy said:
yeah, if you go on their forums all they do is flame XDA left and right. But I find it funny since their roms take advancements from XDA developers and then they incorporate it into their roms...
Click to expand...
Click to collapse
See that's what I thought, but wasn't sure
Sent from my ADR6300 using XDA Premium App
Yes Clockwork 3.0.2.4 is borked on Thunderbolt. I've been helping people on AndIRC's thunderbolt channel all day. Install 3.0.2.2, it's given me no problems.
jgrimberg1979 said:
Can you help me out and provide it because right now i cant even boot
Click to expand...
Click to collapse
I ran into the same problem. I tried to do a restore and got stuck. I used an sd card reader and put the 3rd file from the root thread PG05IMG.zip on the root of my sd card. I then put the card back in. Rebooted into recovery holding the volume down and the power button. It reflashed the file automatically and I followed the steps from 7 on to regain root. Worked for me, but now I have to start over. Hopefully they will get CWM working again. I will be much more careful about what I delete from now on. I think I will freeze it in TiBackup first to make sure everything is still working correctly. Hope this helps.
lynseyw said:
I ran into the same problem. I tried to do a restore and got stuck. I used an sd card reader and put the 3rd file from the root thread PG05IMG.zip on the root of my sd card. I then put the card back in. Rebooted into recovery holding the volume down and the power button. It reflashed the file automatically
Click to expand...
Click to collapse
This is the exact procedure I used when the same thing happened on my N1
i added the recovery.img i used to OP with instructions for those stuck in recovery or bootloader.
jeffnucci said:
Yes Clockwork 3.0.2.4 is borked on Thunderbolt. I've been helping people on AndIRC's thunderbolt channel all day. Install 3.0.2.2, it's given me no problems.
Click to expand...
Click to collapse
Latest Rom manager is 3.0.1.3 sorry if I am missing something I am a bit of a clockwork noob.
Sent from my ADR6400L using XDA App
miketoasty said:
Latest Rom manager is 3.0.1.3 sorry if I am missing something I am a bit of a clockwork noob.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Newest Rom Manager is 3.0.1.3 but the newest ClockworkMod Recovery for the tbolt is 3.0.2.4
Under flash clockworkmod recovery it stats the current and latest recovery.
My battery died and am in the same position. Got an expensive paperweight at the moment. I'll try to get another battery today and give this a try. After fooling around with it last night, the computer wouldn't even recognize the phone. Ughh!
RafficaX said:
Newest Rom Manager is 3.0.1.3 but the newest ClockworkMod Recovery for the tbolt is 3.0.2.4
Under flash clockworkmod recovery it stats the current and latest recovery.
Click to expand...
Click to collapse
Good call just checked and 3.2 does wipe date and cache properly.
Sent from my ADR6400L using XDA App
miketoasty said:
Good call just checked and 3.2 does wipe date and cache properly.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Where did you get 3.2? 3.0.2 you mean?

[Q] Error while trying to boot into Recovery. HELP please! :(

My HTC HD2 won't boot into recovery it displays "ERROR: ERROR: Invalid boot image header"
Can't seem to solve it, help would be much appreciated...
Thanks
What exact Clockwork Mod Recovery did you flash to you're HD2? As there is two was of installing it and two ways of booting it.
I'm in the same problem, i upgraded ROM Manager from market and then reflashed recovery from rom manager, from which we can find HTC HD2 listed now, and when i entered recovery, same error appears: Invalid boot image header. Please help us. Before this upgrade, i have reflashed recovery using Desire HD listed with no problems at all.
Edit: i have to reflash selecting DESIRE HD and had to reflash the whole Hyperdroid GBX v12 build to fix it.
Yes, i have the same issure. After the upgrade to v4.0.0.6 from market and selection for recovery CwM for HD2 i was unable to boot in this partition.
I´ve tried to install all older versions 3.0.0.5 and 3.0.0.6 (new one is 3.0.2.5) but it seems, that the recovery system is now demaged.
Also the selection for recovery CwM Desire and Desire HD does not run
Please help...iam not able to flash a new system anymore without lose my data
Hi! Same here.. please help!!
PG
tberndt said:
Yes, i have the same issure. After the upgrade to v4.0.0.6 from market and selection for recovery CwM for HD2 i was unable to boot in this partition.
I´ve tried to install all older versions 3.0.0.5 and 3.0.0.6 (new one is 3.0.2.5) but it seems, that the recovery system is now demaged.
Also the selection for recovery CwM Desire and Desire HD does not run
Please help...iam not able to flash a new system anymore without lose my data
Click to expand...
Click to collapse
Try reflashing Recovery, i use 150M_recovery, then reflash your build. That should help. I think it's the only way to fix it, at least worked for me.
Traukoman said:
Try reflashing Recovery, i use 150M_recovery, then reflash your build. That should help. I think it's the only way to fix it, at least worked for me.
Click to expand...
Click to collapse
Thanks
Yes, thats the problem...when i reflash with recovery_150M i lost my data, because this prepare a new partition layout.
If i do it, i have the CwM Recovery system, but no android anymore
polskiii said:
My HTC HD2 won't boot into recovery it displays "ERROR: ERROR: Invalid boot image header"
Can't seem to solve it, help would be much appreciated...
Thanks
Click to expand...
Click to collapse
Hi,
I had the same problem.I think the new ROM manager is currently only working with CLK.That's why it's screwing up our MAGLDR.
I'm going to try loading it back manually from this thread:
http://forum.xda-developers.com/showthread.php?t=987531.
I will report back.
(EDIT)
Yup ,it worked fine.
Used "magldr_recovery_3.0.2.5.zip" For MAGLDR 1.13, booting from NAND.
It updated to 3.0.2.5,then I restored a previous backup.
Everything back to normal.
Thanks malybru for this help
yes, that works fine, but i lost my data.
For the future... i have to make more backups before i update to a new version of CwM
Thorsten
(EDIT)
Nooooo....i have the same issure again.
After flashing the new recovery system and backup, i´ve installed the CwM Update from market.
The same again...
i think its an issure of CwM :-(
tberndt said:
Thanks malybru for this help
(EDIT)
Nooooo....i have the same issure again.
After flashing the new recovery system and backup, i´ve installed the CwM Update from market.
The same again...
i think its an issure of CwM :-(
Click to expand...
Click to collapse
Hi,
What "CWM UPDATE" from market did you install?
malybru said:
Hi,
What "CWM UPDATE" from market did you install?
Click to expand...
Click to collapse
I wanted the last one v4.0.0.6
I have actually the ROM Manager Premium v3.0.2.0
After your hint its the 3.0.2.5 CwM Recovery System
tberndt said:
I wanted the last one v4.0.0.6
I have actually the ROM Manager Premium v3.0.2.0
After your hint its the 3.0.2.5 CwM Recovery System
Click to expand...
Click to collapse
It's ok to go to market and type ROM manager and update it.
However,do not use the program if you have MAGLDR,because it will not work,yet.
At the moment ,it will only work if you have CLK installed.
Solved my issue.
I thank you all for your efforts, much appreciated!
A few hours after panicking i just reflashed the 400MB system partition and everything was totaly fine.
Since a day I'm running MIUI 2.3 and it is really something
Greets,
Polskiii
My issue solved.
I thank you all for your efforts, much appreciated!
A few hours after panicking i just reflashed the 400MB system partition and everything was totaly fine.
Since a day I'm running MIUI 2.3.3 and it is really something else
Greets,
Polskiii
malybru said:
It's ok to go to market and type ROM manager and update it.
However,do not use the program if you have MAGLDR,because it will not work,yet.
At the moment ,it will only work if you have CLK installed.
Click to expand...
Click to collapse
Okay, tnx...
Maybe it's the best to install clk, it's solves another problem with the directly cwm recovery ;-)
tberndt said:
Okay, tnx...
Maybe it's the best to install clk, it's solves another problem with the directly cwm recovery ;-)
Click to expand...
Click to collapse
Hi,
If you want a push in the right direction,this was the advice given to me.
http://forum.xda-developers.com/showpost.php?p=13024428&postcount=13
Good luck.
malybru said:
Hi,
If you want a push in the right direction,this was the advice given to me.
http://forum.xda-developers.com/showpost.php?p=13024428&postcount=13
Good luck.
Click to expand...
Click to collapse
Member zach.anger did a good job in that post instructing on the proper ADB commands to type in. But Icwas pointed to a very good guide by senior member arif-ali, who is one of the main developers that worked and is still working with cedesmith to get cLK perfected, which it is pretty much close to that now. Anyway he directed me to senior member stirkac's really good guide. You can find it at the link below. Thought I would share it with everyone as it is kinda barrier in the cLK thread.
http://forum.xda-developers.com/showpost.php?p=12327648&postcount=844
Ari Alif has released the ultimate Magldr Recovery solution for this issue, her it is:
http://forum.xda-developers.com/showthread.php?t=987531&page=44
malybru said:
Hi,
What "CWM UPDATE" from market did you install?
Click to expand...
Click to collapse
The same exact thing happened to me with both of my HD2s, I quickly figured that there is an issue. So the solution was to to ref lash everything and reload a previous backup.
Go here and follow each one accordingly for MAGLDR or cLK:
http://forum.xda-developers.com/showthread.php?t=933951
Clean Install MAGLDR:
1. Task 29
2. Flash Radio(2.15 Recommended)
3. MAGLDR 1.13
4. MAGLDR 150MB System/5MB Cache (ClockworkMod Recovery v3.0.2.5)
5. Install TyphooN CyanogenMod 7 .zip with CWM
Clean Install cLK:
Follow Charmacas's tutorial
[email protected]

[Q] Clockwork Mod Recovery broken

So I decided to flash Clockwork Mod Recovery I had version 3.0.1.9 and I wanted 3
.0.2.5 I went into ROM Manager and flashed to that version. But now when I go into AD Recovery it says ERROR: Invalid boot image header and goes back to MAGLDR. Can someone help me fix this and get the most recent version of Clockwork Mod on my HD2. Thanks! Kind of a newbie sorry!
error
i have had the same problem what is did went here and re download the ROM manager 3.025 or what you were using before the error once you do that is i should work again but you mite have to install your ROM again i had to but when you download and flash it with the daf file just make sure you find the one that was working before you flash it you don't what to get the same thing again hope that help if not let me know good luck
starblade18 said:
So I decided to flash Clockwork Mod Recovery I had version 3.0.1.9 and I wanted 3
.0.2.5 I went into ROM Manager and flashed to that version. But now when I go into AD Recovery it says ERROR: Invalid boot image header and goes back to MAGLDR. Can someone help me fix this and get the most recent version of Clockwork Mod on my HD2. Thanks! Kind of a newbie sorry!
Click to expand...
Click to collapse
rko2010 said:
i have had the same problem what is did went here and re download the ROM manager 3.025 or what you were using before the error once you do that is i should work again but you mite have to install your ROM again i had to but when you download and flash it with the daf file just make sure you find the one that was working before you flash it you don't what to get the same thing again hope that help if not let me know good luck
Click to expand...
Click to collapse
Hi,
ROM Manager ONLY works with cLK,NOT magldr.
Use THIS TOOL (Don't forget to thank him)
to re-install magldr
Magdlr is still installed, just Option 8 does not work. Will this reinstall MAGDLR and Clockwork Mod?
starblade18 said:
Magdlr is still installed, just Option 8 does not work. Will this reinstall MAGDLR and Clockwork Mod?
Click to expand...
Click to collapse
Hi,
To install CWM,use the installer...
Top line,magldr update recovery,choose the size of the partition you want for your new ROM and click update in bottom left hand corner.
It didn't work. Said no space left on the device
starblade18 said:
It didn't work. Said no space left on the device
Click to expand...
Click to collapse
Hi,
No memory left means the last version of recovery you installed was smaller than the current one. You need to completely repartition MAGLDR in order to install new version in that case.
Is there an average partition size and cache size? I need to choose?
starblade18 said:
Is there an average partition size and cache size? I need to choose?
Click to expand...
Click to collapse
Hi,
I think you should start the process again from the beginning.
Task 29
Install magldr
Install CWM by using the partition you want for your new ROM.So look at the [OP] of your new ROM, get the CWM partition and flash that.
Then you can go straight to installing the ROM.

[Q] Cant get into recovery, re-install under Linux?

I have flashed several roms using CLW already and it always worked fine, but now I'm really stuck.
The problem is that I installed the Hyperdroid CM7 rom. It worked fine. But when I wanted to install the Google Apps I just couldn't get into the recovery mode from the MAGLDR menue anymore. It just says "ERROR ERROR: Cannot read ramdisk image". I tried to update the CLW using the Rom Manager but it didn't solve my problem. Unfortunatelly I also can't boot the rom anymore now (I can't since I formated the SD card).
Can I now just install CLW again (over the existing version) with the "USB Flasher" option from the boot menue? Or can I repair the installed version somehow?
Is there a way of installing CLW under Linux? I've tried using WINE to run the daf.exe but it didn't work since it couldn't find the the usb connection.
Which would be the preffered method of installing roms NAND roms with Linux?
Thanks for any help in advance!
Mr.Mobody said:
I have flashed several roms using CLW already and it always worked fine, but now I'm really stuck.
The problem is that I installed the Hyperdroid CM7 rom. It worked fine. But when I wanted to install the Google Apps I just couldn't get into the recovery mode from the MAGLDR menue anymore. It just says "ERROR ERROR: Cannot read ramdisk image". I tried to update the CLW using the Rom Manager but it didn't solve my problem. Unfortunatelly I also can't boot the rom anymore now (I can't since I formated the SD card).
Can I now just install CLW again (over the existing version) with the "USB Flasher" option from the boot menue? Or can I repair the installed version somehow?
Is there a way of installing CLW under Linux? I've tried using WINE to run the daf.exe but it didn't work since it couldn't find the the usb connection.
Which would be the preffered method of installing roms NAND roms with Linux?
Thanks for any help in advance!
Click to expand...
Click to collapse
ROM Manager isn't compatible with MAGLDR, which is probably why your phone was messed up when you tried to use it. It only works if you use the cLK bootloader. As for your problem, I really can't see much else you can do other than fresh installing CWM through USB Flasher. I don't use Linux so I can't help you there, sorry.
Oh, I wasn't aware that MAGDLR isn't compatible with the ROM manager because it came with the MAGDRL/CWM rom i flashed. But thanks for that information!
Can I just install CWM "over" the allready installed but not existing version? Or will that cause even mor eproblems?
Mr.Mobody said:
Oh, I wasn't aware that MAGDLR isn't compatible with the ROM manager because it came with the MAGDRL/CWM rom i flashed. But thanks for that information!
Can I just install CWM "over" the allready installed but not existing version? Or will that cause even mor eproblems?
Click to expand...
Click to collapse
I think that would be fine, there isn't much point in Task29ing unless you are having major issues.
Ok,so since I couldn't get hold of a windows PC yet I couldn't re-install clockwork flashing with USB cabel.
But I couldn't load CWM recovery from SD card as described in this post #4 of this topic: http://forum.xda-developers.com/showthread.php?t=1352395
I was not able install the CWM then in the second step form zip file on the SD card. Some error message appeared, but I was able to flash a ROM. So my CWM is still broken, but the ROM is working fine which is ok for me now. When I get access to a Windows PC I'll re-flash CWM too.
So the "Linux problem" isn't solved but anyone experiencing problems to get into recovery from MAGDRLR menu should try the way in the above mentioned post.
Mr.Mobody said:
Ok,so since I couldn't get hold of a windows PC yet I couldn't re-install clockwork flashing with USB cabel.
But I couldn't load CWM recovery from SD card as described in this post #4 of this topic: http://forum.xda-developers.com/showthread.php?t=1352395
I was not able install the CWM then in the second step form zip file on the SD card. Some error message appeared, but I was able to flash a ROM. So my CWM is still broken, but the ROM is working fine which is ok for me now. When I get access to a Windows PC I'll re-flash CWM too.
So the "Linux problem" isn't solved but anyone experiencing problems to get into recovery from MAGDRLR menu should try the way in the above mentioned post.
Click to expand...
Click to collapse
Glad to hear it You aren't putting CWM 5.0.2.6 SD as a zip on your SD card by any chance are you? Because you need to extract it to your SD, I misread it first time around and was quite confused as to how that worked as a .zip file.
http://forum.xda-developers.com/showthread.php?t=1352395
this should help
deckoff said:
http://forum.xda-developers.com/showthread.php?t=1352395
this should help
Click to expand...
Click to collapse
LOL, I linked you to that thread on your other post because I saw it on this thread, and you've now managed to make it come back around here
Nigeldg said:
LOL, I linked you to that thread on your other post because I saw it on this thread, and you've now managed to make it come back around here
Click to expand...
Click to collapse
Endless loop, they say
At least this means I read what it says

Categories

Resources