Related
The idea is very well, but every build has its own recovery (or flash.cfg) so instead of using only the sdacrd for flashing (the original idea) now we must use the 2 things : the usb flasher with DAF and the update.zip in the sdacrd
Really did you have to post this question here?
This is an important question. I don't quite understand the idea as well. I don't think anyone has explained anything here like that, especially taking in consideration that we've never used android before except just recently.
really intereseted in that answer to!
but for me another question is: what is the special thing about a2sd+ ?
I did not use recovery yet but isn't it that you flash the recovery 1 time and than you can download the .zip and flash roms via the recovery.
OR
You don't flash it via recovery but just via DAF.exe like I do at this moment.
The a2sd+ makes a part of your SD card act like it's internal storage so you can install more apps than on 280mb that is left when you don't have the 1024leo phone (usa = leo1024 , eur = leo512).
1. You can make a full backup of your system so if you hose your data you can wipe and restore back to the last backup.
2. You can install new roms from the microsd card as long as the system partition fits what you have set. Some people prefer it that way, and some people have bad usb ports and need it that way.
pr0x2 said:
I did not use recovery yet but isn't it that you flash the recovery 1 time and than you can download the .zip and flash roms via the recovery.
Click to expand...
Click to collapse
it must be like that, but in the real world, every rom builder, uses differents MTD partitions sizes, so we have to reflash its recovery again, even if we have already flashed it before with the defaults sizes (150, 250 or 400 MB)
Why every build do not uses a standard sizes, fixed by the Recovery builder, RaiderX303 ?
RaiderX303, you have make a very interesting work, thank you very match for that, but can you please continue you works and resolve this ?
Recovery allows people to download and flash roms from the SD card, no need for a pc except for the first time install using DAF to flash the partition layout, it allows people to switch easily between roms, some people like myself have a Rom they prefer to use, when a new Rom comes out that looks good I can backup the Rom I'm using and flash the new Rom, if I don't like the new Rom I can flash back to my old Rom and not lose any data
Sent from my Desire HD using XDA App
Hey guys, i'm using MJD's 2.1. I thought the benefit of ClockworkMod was to enable me to go into recovery from the reboot menu. Also, it was supposed to allow me to reset to factory settings. It seems that none of that is working.
If I reboot into bootloader or recovery it just reboots into Android again. Resetting to factory settings does absolutely nothing apart from rebooting.
What am I doing wrong?
Dear Friends,
I usually flash ZIP Android using CWM, through menu no.8 in MAGLDR menu. CMW was flashed via USB Flasher menu no.5 in MGLDR menu.
But after several times of failures, I gave up. I hope somebody can inform me what went wrong.
Here is the issue:
After flashing CWM (partition layout) and try to go into recovery mode, the screen says:
"ANDROID LOAD RAW
ERROR: ERROR: Cannot read kernel image"
I tried so many attempts but always like that. I did task 29, reflashing MAGLDR, radio, I even tried to go back to Winmo and back again to reflash HSPL 2.08 and so on. But no luck
I remember that this happen after I tried flashing CWM using SD Card method (via menu no.2 in MAGLDR). If I used this method, I can go into recovery mode. I dont like this method, because I never succeeded flashing ZIP ANdroid using this method. That is why I want to go back to recovery mode via menu no.8 in MAGLDR.
Is the problem related with what i did (flashing CWM via SD Card method)? Is the NAND is damaged?
Is there a way to solve that?
Many thanks in advance
silverwind said:
After flashing CWM (partition layout)
Click to expand...
Click to collapse
what are the contents of flash.cfg? (you can open that file in notepad)
samsamuel said:
what are the contents of flash.cfg? (you can open that file in notepad)
Click to expand...
Click to collapse
Which one? is it the one with CWM partitioner lay out?
This one was flashed when I tried to flash: Ultimate Droid v.3.1.1.v2:
misc ya 1M
recovery rrecov|ro|nospr filesize recovery-raw.img
boot yboot|ro 5M
system ya 150M
cache ya 30M
userdata ya|asize|hr allsize
And this one is the standard one with 150MB lay out:
misc ya 1M
recovery rrecov|ro|nospr filesize recovery-raw.img
boot yboot|ro 5M
system ya 150M
cache ya 44M
userdata ya|asize|hr allsize
I used either one as per instruction in the relevant thread
hmm, and there is deffinitely a file called recovery-raw.img in the same folder? do you get any error messages on the phone screen when you flash the cwm layout?
samsamuel said:
hmm, and there is deffinitely a file called recovery-raw.img in the same folder? do you get any error messages on the phone screen when you flash the cwm layout?
Click to expand...
Click to collapse
Yes. Never happened before until I flashed cwm using ad method as explained in the following:
http://forum.xda-developers.com/showthread.php?t=987531
once you install CWM you are installing a rom from zip arent you?
if you just install cwm then it wont boot any existing rom, thats what i have found from past experience
Richy99 said:
once you install CWM you are installing a rom from zip arent you?
if you just install cwm then it wont boot any existing rom, thats what i have found from past experience
Click to expand...
Click to collapse
After flashed Recovery via AD SD boot, I flashed the ROM. But it won't boot. So, I decided to reflashed Recovery via USB FLasher (of course I did task 29, flash MAGLDR again).
After that, I went into MAGLDR menu and selected no.8 (AD Recovery). And, it wont boot to Recovery. It says ERROR cannot read kernel image.
My point is that I want to flash ROM via CWM (this CWM was flashed via USB Flasher), but the CWM itself failed to boot (after successful flashing).
I dont have problem boot into CWM if it is flashed via AD BOOT (menu no.2 in MAGLDR) and I cant flash the ROM (though the ROM fails to boot).
Any idea?
ive not used that edited/tweaked cwm, but two things come to mind.
First off, latest magldr required, check? (im not scrolling back to read, so sorry if you already said that)
and secondly, from teh error you are getting, it can only be that somewhere, (possibly when you are restoring from a backup taken when there was no recovery partition?) you are either wiping the recovery partition, or you arent loading back the contents of the recovery partition.
samsamuel said:
ive not used that edited/tweaked cwm, but two things come to mind.
First off, latest magldr required, check? (im not scrolling back to read, so sorry if you already said that)
and secondly, from teh error you are getting, it can only be that somewhere, (possibly when you are restoring from a backup taken when there was no recovery partition?) you are either wiping the recovery partition, or you arent loading back the contents of the recovery partition.
Click to expand...
Click to collapse
Yes Magldr 1.13. I didn't restore any nandroid backup. How can I restore if recovery failed to boot?
It seem this tweaked cwm did/wrote something In the NAND that cannot be erased by task 29 or by flashing stock rom. I stiil can bot recovery through AD boot (menu no.2 in magldr) the tweaked recovery show version 3.0.1.9. Maybe I
should try mtty?
think id concentrate on getting back to winmo stock with an sd card flash, wipe the lot and start over yet again.
As far as I remember, after you flash magdlr 1.13 you need to flash CWM to get the menu point 8 (ad recovery) working. Magdlr 1.13 itself doesn't have the CWM built in, but it supports CWM.
Sent from my HTC HD2 using XDA App
samsamuel said:
think id concentrate on getting back to winmo stock with an sd card flash, wipe the lot and start over yet again.
Click to expand...
Click to collapse
Like I said, I did start it all over again
But, still it didnt help. That is why I am beginning to think that task 29 does not erase all NAND or else there is a damaged/defect in the physical NAND. Should I try use MTTY?
greg17477 said:
As far as I remember, after you flash magdlr 1.13 you need to flash CWM to get the menu point 8 (ad recovery) working. Magdlr 1.13 itself doesn't have the CWM built in, but it supports CWM.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Yes I know. There are 3 methods (as I know from XDA ) to boot Recovery Clockword Mode (CWM). Firstly, flashing via USB Flasher (menu no.5) and after flashing, we should select menu no.8 to go into CWM mode (this one is the issue I am talking about), secondly, flashing via AD Boot (menu no.2), it will directly bring you into the CWM menu, and thirdly, using cLK (which I never try it).
I just wanted to try the second method and it works. However, due to the partition lay out issue (as far as I am concerned, the second method doesnt provide flexibility in providing partition lay out. it uses 150MB lay out). So, for the ROM requires different partition layout, I need to flash CWM in accordance with the relevant ROM requirement. This can only be done if we flash CWM via First method. When I flash CWM (for different partition lay out), it seems flashing successful , but when I selected menu no.8 to go into CWM mode it then says: "Error, cannot read kernel image".
Up to now, I can only boot CWM using second method. I just hope the dev of this method can provide a way to flash different partition lay out or did I miss something?
thanks
does this occur with the standard content of raiderx' recovery download, for example the 400m layout...? you can try to edit the "recovery" line inside flash.cfg: remove "filesize" and instead type "6M", so it shows
...
recovery rrecov|ro|nospr 6M recovery-raw.img
...
maybe there are bad blocks on NAND (which is normal, especially after excessive flashing, which is native to us hd2 users due to the mass of roms available for it ) which are causing this.
alternatively you can try to first delete the original "recovery-raw.img" inside the original raiderx recovery folder and then copy the new one; or to use another windows machine (or harddrive in your computer, if exist). maybe there is sth wrong...?
if all you've tried already and other tipps isn't / aren't working, it would be interesting to know if this occurs if you're using cLK; pure testing purpose
i hope you'll get this running... the sd method is no solution in my opinion.
seadersn said:
does this occur with the standard content of raiderx' recovery download, for example the 400m layout...? you can try to edit the "recovery" line inside flash.cfg: remove "filesize" and instead type "6M", so it shows
...
recovery rrecov|ro|nospr 6M recovery-raw.img
...
maybe there are bad blocks on NAND (which is normal, especially after excessive flashing, which is native to us hd2 users due to the mass of roms available for it ) which are causing this.
alternatively you can try to first delete the original "recovery-raw.img" inside the original raiderx recovery folder and then copy the new one; or to use another windows machine (or harddrive in your computer, if exist). maybe there is sth wrong...?
if all you've tried already and other tipps isn't / aren't working, it would be interesting to know if this occurs if you're using cLK; pure testing purpose
i hope you'll get this running... the sd method is no solution in my opinion.
Click to expand...
Click to collapse
Thank Bro, I will try your suggestion and let u know the result.
I also guess there is something wrong with the NAND, maybe the cluster, block, etc. Maybe need to be defragmented (is there any app for doing that?)
I use standar 150MB partion layout from Raider x and also 135MB layout for flashing Typhoon Cyanogenmod.
I still can flash using DAF, but since there is only few ROM for this method, then I would prefer to go through via CWM
thanks again
sure, no problem! one additional question: this really started out since you've used the sdcard files?
cwm is essential and really needed, especially as the most of chefs doesn't provide DAF ROMs anymore. you want to flash typhoon cm7, right? if nothing is working for you, i'll create a daf version for you, so that you at least can use this ROM. just let me know.
seadersn said:
sure, no problem! one additional question: this really started out since you've used the sdcard files?
cwm is essential and really needed, especially as the most of chefs doesn't provide DAF ROMs anymore. you want to flash typhoon cm7, right? if nothing is working for you, i'll create a daf version for you, so that you at least can use this ROM. just let me know.
Click to expand...
Click to collapse
Yes, since I tried the SD card CWM (no offense Bro )
You are right, CWM is app you cant live without it if you are an Android lover
I highly appreciate if you can provide DAF version. I only knows how to convert from ZIP to DAF but not the other way round
Many thanks
k, i will create it todays evening ~ 20:00 gmt+1; but first, pls try to test the other tipps (6M for adding "some spare blocks" and if nothing helps cLK pls).
i'll pm you if i'm ready ok?
i have to do it tomorrow; today i've painted the livingroom of a friend and didn't go home. that's ok? or is there sth new on your side? did you test cLK?
greetings
seadersn said:
i have to do it tomorrow; today i've painted the livingroom of a friend and didn't go home. that's ok? or is there sth new on your side? did you test cLK?
greetings
Click to expand...
Click to collapse
No need to push yourself mate I am patient enough to learn
For installing cLK, I will do it later because I have to learn it since I am not familiar with it (or else if you have or know tutorial for newbie, i would go for it)
I will start with flashing with Recovery with 150MB layout provided by Raider x. Currently I am using Winmo with HSPL 4.
Here is what I will do:
1. Turn of the phone.
2. Go into bootloader mode
3. Task 29
4. Flashing HSPL 2.08
5. Flashing MAGLDR 1.13
6. Flashing CWM 150MB via USB Flasher in MAGLDR menu no.5
7. Boot into Recovery Mode via MGLDR menu no.8
This is the point where i got the problem. If it works, then I can go into Recovery mode to install ZIP ROM , but if fails then it will say Error: cannot read kernel image and it will bring me back to MAGLDR screen.
EDIT:
After flashing MAGLDR 1.13, the phone reboot and I unplugged the usb cable.
It booted and the screen says:
"Booting Android from SD
Android load at 11800000
from Micro SD
Load zimage
k: / zimage
ssSD kernel open failed"
then it brought me to MAGLDR screen menu.
I thought it is normal, isnt it?
then I flash CWM using USB flasher via menu no.5
After flashing CWM complete, the phone reboot and again it showed the above screen and finally went back into MAGLDR screen.
Here is the same old problem. In MAGLDR screen, I selected menu no.8 in order to boot the Recovery mode.
But it failed and the screen says:
"LOAD ANDROID RAW
ERROR: ERROR: cannot read kernel image"
So, it happens again.
Before I continue with the next trial, I wanna hear your opinion about that.
BTW, the winmo before I started this, is ENERGY ROM.
PC I used is WIN XP SP2.
Battery is full, SIM CArd was in but Micro SD was removed.
Do you think I miss something?
Thanks in advance
Apologies if I am at all asking a question that has been answered before (forum search did not help much), but I am trying to find out how to safely flash a different ROM onto my device.
I have installed HSPL3, Radio 2.15, MAGLDR 1.13, ClockworkMod Recovery and NexusHD2-Gingerbread V2.7 using the NAND method.
I want to shop around and check a few different ROM's before donating to the one that suits my needs, but I need to know if it is simply a case of flashing a new ROM over the existing one using the same methods or is it slightly more complicated than that?
Thanks.
Ugh no need to flash over hspl, magldr, or radio. Just use cwm to flash it. However depending on the rom, you may need to flash a different cwm. Eg. Cyano is the 150mb partition, sense is the biggest partition.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Kailkti said:
Ugh no need to flash over hspl, magldr, or radio. Just use cwm to flash it. However depending on the rom, you may need to flash a different cwm. Eg. Cyano is the 150mb partition, sense is the biggest partition.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Hi,
If I were you ,I would backup your existing ROM in CWM(go to backup and restore).
That way if your next ROM is no good or if there is any problem,you can easily restore the original.
Before you install a new ROM,READ the [OP] carefully ,paying special attention to the size of the new recovery partition.
Then you can flash the new recovery partition,wipe data,cache partition and dalvik(in advanced),
then install zip from sd card.
Do I need to clear anything for smaller ROMS/MODS?
I currently am running the latest GingerTh3ory Rom with its respective radio. Then in it's candystor3 app I downloaded the 'honeycomb battery' full mod pack so that it uses a honeycomb UI with the battery and small things like that.
When I change the battery and do system and individual MODS should I clear anything? I don't want to slow my phone down by keep flashing MODS over top of one another? My friend convinced me to root and so now I'm getting used to this.
Any help is much appreciated!
Thanks
I have come to find that most new Rom's usually will format everything needed when you are flashing over another Rom. Just to be cautious go into CWM and maually fomat Boot, system, cache, sd-ext(if applies) data, and then go to advanced and wipe Dalvik cache...
What I'm trying to say is, when I got my hd2 It already had magldr 1.13 and a nice gingerbread rom installed. What I want to know is how can I go back to a clean Leo and start fresh so that I can learn how to install android myself. I could use some help with the i android install afterward as well. thanks in advance.
Sent from my Touchpad using xda premium
You could use the hd2 toolkit from this post. It will wipe your rom (task29 option), install mgldr, then you would be good to go to install recovery and another rom.
I have just been using it, its a great tool. I think this would only apply to nand roms, sd roms maybe do it differently?
Peace
Edit: also, I found post #4 from this thread invaluable help for flashing my first leo android rom.
If you truly want to go to a "Fresh LEO" download a stock leo winmo rom, change the .exe to .zip find the RUU or something like RUU_signed.nbh ( should be like 270MB in size) and change the name to LEOIMG.NBH and transfer it a 4GB or less microSD card and insert into phone. Start the phone holding the red power button and the volume down button. it should go into the bootloader and flash stock radio/spl/rom and you can start from scratch. CM7 was the best thing to happen to the HD2. CAN'T WAIT FOR CM9!!!!
Okay people now I REALLY need your help, okay so I flashed clockwork mod recovery through magldr, and thats working fine, but after doing so, when it tries to boot it says something like failed to load kernel, so I figured that roms toast so I used the option in magldr to "Ad hard reset" because the hd2 toolkits task 29 wipe kept failing as well. So I need help finding a rom that will install from clockwork mod recovery. Im hoping it will take care if my kernel problem. Any links to Cwm roms would be great and thanks in advance.
Sent from my Touchpad using xda premium
Truth650 said:
Okay people now I REALLY need your help, okay so I flashed clockwork mod recovery through magldr, and thats working fine, but after doing so, when it tries to boot it says something like failed to load kernel, so I figured that roms toast so I used the option in magldr to "Ad hard reset" because the hd2 toolkits task 29 wipe kept failing as well. So I need help finding a rom that will install from clockwork mod recovery. Im hoping it will take care if my kernel problem. Any links to Cwm roms would be great and thanks in advance.
Sent from my Touchpad using xda premium
Click to expand...
Click to collapse
Pretty much any newer ROM will be flashed through CWM. Just look at the OP and flash the correct partition size, then place the 'MAGLDR' version of the ROM (zipped folder) on your SD card and flash
Wait lemme see if I have this correct. When I see roms that say magldr version, I can flash THOSE through CWM recovery? If u could help me find cm7 that I can flash through cwm I'd be most appreciative. Thanks again.
Sent from my HTC HD2 using xda premium
Truth650 said:
Wait lemme see if I have this correct. When I see roms that say magldr version, I can flash THOSE through CWM recovery? If u could help me find cm7 that I can flash through cwm I'd be most appreciative. Thanks again.
Sent from my HTC HD2 using xda premium
Click to expand...
Click to collapse
Any CM7 ROM in the NAND Development section really. Typhoon, Hyperdroid, Dorimanx etc.
first check the CWM recovery requirements of the ROM(it will say something like CWM 5/120/5) then check your current recovery if its the same. If not you need to download the zip file for the CWM recovery required by the ROM. unzip the file on a computer and run the .exe and follow prompts on the screen(doing this will completely delete the current ROM install on your phones internal memory). Once the correct recovery is flash on your phone, you can flash the ROM itself
Hi,
a friend gave me an HD2 which stopped booting about three months ago, when he tried to install android on it, without really knowing what he was doing.
I have a bit of experience in installing custom roms in some android devices (HTC Vision, Samsung P1000...), but I know nothing about HD2 or any windows phones.
This is what it says after switching on:
tinypic.com/r/2hywdp4/5
This is after switching on with windows key pressed:
tinypic.com/r/29y43fb/5
This is after switching on with volume key pressed:
tinypic.com/r/25i3f9c/5
[sorry I can't create links because I'm new to xda]
Is there a way to go back to a working status?
If I fix it, I'll earn some glory and a free beer.
The final aim would be to install a NAND android rom, preferably CM7 or similar.
Thanks a lot.
Correct me if i'm wrong guys, but this pic :
tinypic.com/r/25i3f9c/5
is the bootloader mod and it says that you have HSPL 2.08
In my opinion, you just have to flash back a windows 6.5 ROM and follow the whole process to get android (Flash MAGLDR, [....] , and flash a CM7 NANDROID Rom using the clockworkmod) refering to the tutorials in the NANDROID section.
Its not bricked. Just restart the process to install Android as jediL pointed out and you should be good to go. Check here for a detailed explanation on how.
Ok the pictures help a lot. From what I see the first picture is what you see when you boot a HD2 that has clk installed for the custom bootloader but does not have as Android ROM in memory to boot. This is the only reason you well ever see clk at all if you just power on a HD2 with clk installed.
The second pictures is clk trying to boot into recovery but is not able to. It probably either has some kind of problem booting the flashed version or it just does not have a custom recovery flashed to it. My bet is it does not have a custom recovery flashed to it. As most people have problems Glasgow.g a recovery after flashing clk if they are not using the HD2 NAND Toolkit.
The third picture is the the stock bootloader of the HD2 and yes it shows you have HSPL 2.08 installed so you are good with HSPL and do not need to flash HSPL 2.08 to your HD2.
Now to get you on to getting Android up and running. Seeing as you already have clk on your HD2 you do not need to flash it. You do need to flash a custom recovery and you can either check out the guide linked in my sig to flash it via fasboot comands manually or you can use the HD2 NAND Toolkit to flash it in a more automatic way, or to be more specific a more noob friendly way. There is a link to the toolkit in the guide linked in my sig.
You need to pick out what Android ROM you want to use and read the first few post by the ROM chef to see what partition size you need to have and use the Toolkit to repartition the NAND memory to that size. Next download the .zip file for the ROM, make sure you get the version that is for clk. Some ROMs have only one version though that works with MAGLDR and clk. Next copy the .zip to the root of your SD card and then power on your HD2 holding down the home button and your recovery will boot up. Then just find the option that says install from SD card and then select the ROM file and flash it.
I installed HD2 NAND Toolkit.
I executed the following operations:
- Wipe (Task29)
- cLK repartition (150mb)
- cLK install recovery
then I rebooted into CWM recovery and installed the HyperDroid rom.
Now I have a fully working CM7-based android phone!
Thanks a lot!