Related
Hi, this is my first post on this forum so first of all I would like to appolagise for all the things I've either just done wrong, or am about too....
I am trying to install android on to my phone, I am on the stock rom but have succsesfully installed HSPL3 and radio version 2.11.50.20.
I have tried a few builds of Android but allways have one of 2 results.
Once I've run clrcad followed by harlet, it tells me I'm booting to linux. The screen then goes black, it runs about 8 lines of code, stops there and changes to a black screen with a green HTC. Where it remains indefinatly.
A friend with anouther HD2 has android working fine on his device, and altho he has a custom rom he tells me its not essential, as ive read up on the potential risks I would rather stick with the stock but will change if thats whats causing the problem.
I would really appreciate some suggestions, thanks in advance for your time and help.
Peter
forgot to add, the second result is the screen going blue indefinatly, which I presume from my extensive knowledge.........lol is a blue screen of death
upgrade your radio, im on 2.12.50, and the newest is 2.15.50
also, try a modded windows mobile rom, i use standard energy with no issues.
also, make sure you only have that one android build on your SD card. and that it's a new build, not an ancient one. (check http://android.hd2roms.com/)
you shouldnt have any more issues.
Thanks for the advice, unfortunatly before seeing your post I uprgraded too chuckeys rom, not energy, but get the exact same error... Leads me to beleive the problem is elsewhere. Will keep trying tho hope its worth it.
Jai meme problme mon rom est miri hd2 v_18.0 wwe ? Radio 2.15.50.14 ?
Same problem here, tried to change my wm rom and didn't work. I'm looking tonight if I can find a solution...
A little disclaimer
I will not be for any damage that may be caused to your device, HSPL remove warranty so be carefull. Don't forget to have more than 50% of battery remaining before the process !
So, maybe here is the solution:
I've try again with differents roms, changing my wm rom etc. and nothing works.
But, at the end I've change my radio rom to Leo_RADIO_2.12.50.02_2 found here http://forum.xda-developers.com/showthread.php?t=611787
Then installed Chucky GTX Lite rom found here http://forum.xda-developers.com/showthread.php?t=618787
And to finish I've installed the bootloader and download MDJFroYoRevolution 1.4 with android 2.2
I've use the 512 Data img too (just unzip your MDJFroYoRevolution, take the 512 or 1Go file and put this file on your Android root.) isn't necessary but takes less time to work first time.
After that still not working so I managed to try to remove all files from my sd card (2Go only) and I put on ONLY MDJFroYoRevolution 1.4+512Mo Data img !
Then after 10mn~ it works !
I think the bug is only because sd card haven't enough space to create all files so the HTC logo stuck and no error message appear.
Don't forget to install the bootloader on your memory internal storage! and not the on the sd card!
Good luck everyone and I hope it will help.
ps: sorry for my english hope you understand anything
Having the same problem here. I've tried different versions of WM, different Android builds, updated the latest radio rom, all without success.
Strange thing is though that Android boots the first few times, but after resetting it more than about three times it gets stuck on the black screen with the HTC letters in the middle. The only way to get it running again is reformatting my SD card (8G). Only thing on it is the Mdeejay Froyo Sense v2.3 Clean...
Solution for the freeze screen after second boot
I put android not in the root directory but in a \Android directory on the SD CARD.
of course, I add set cmdline "rel_path=Android" in the Startup.txt file and now i can reboot my phone when i want.
Ghirt said:
Having the same problem here. I've tried different versions of WM, different Android builds, updated the latest radio rom, all without success.
Strange thing is though that Android boots the first few times, but after resetting it more than about three times it gets stuck on the black screen with the HTC letters in the middle. The only way to get it running again is reformatting my SD card (8G). Only thing on it is the Mdeejay Froyo Sense v2.3 Clean...
Click to expand...
Click to collapse
exactly the same issue here
ROM: Energy build 28244
Radio: 2.15.50.14
Android: MDJ FroYo Sense Clean v. 2.4
Having same issue.
Energy Rom
Just reformatted MS
Hspl 2.08
radio 2.15.50.4
htc desire android build
getting same green htc screen.
icemanscion said:
Energy Rom
Just reformatted MS
Hspl 2.08
radio 2.15.50.4
htc desire android build
getting same green htc screen.
Click to expand...
Click to collapse
Do you got this issue at the first boot or after few reboots as Ghirt and I have ?
peterbeer said:
Hi, this is my first post on this forum so first of all I would like to appolagise for all the things I've either just done wrong, or am about too....
I am trying to install android on to my phone, I am on the stock rom but have succsesfully installed HSPL3 and radio version 2.11.50.20.
I have tried a few builds of Android but allways have one of 2 results.
Once I've run clrcad followed by harlet, it tells me I'm booting to linux. The screen then goes black, it runs about 8 lines of code, stops there and changes to a black screen with a green HTC. Where it remains indefinatly.
A friend with anouther HD2 has android working fine on his device, and altho he has a custom rom he tells me its not essential, as ive read up on the potential risks I would rather stick with the stock but will change if thats whats causing the problem.
I would really appreciate some suggestions, thanks in advance for your time and hel
Peter
Click to expand...
Click to collapse
Always use the custom winmo Rom sugested by the Android Builder. Simple as. The myth of "Stock ROM will be sufficient" should end
Peter[/QUOTE]
Same problem!!
Ive updated my radio to: 2.15.50.14
tried 3 roms.
before installing radio - I had the Kernal problem.
and now I have the black screen with green htc.
has anyone found a solution?
is their something that im not doing?
thanks!
jigners said:
Always use the custom winmo Rom sugested by the Android Builder. Simple as. The myth of "Stock ROM will be sufficient" should end
Peter
Click to expand...
Click to collapse
[/QUOTE]
Not true. I've installed on a couple of peoples HD2's using the latest stock WWE rom with radio 2.15. It does work, and it works very well.
I'm not saying you shouldn't use custom roms, that is everyone's prerogative (as you can see from my sig I use VBN's rom and it's perfect for me).
Try to move a folder called Android from sd card to another folder or delete it and it should help. It worked in my case. Good luck!
has someone hear find an answer?
given up
I have tried many combos and radios and still stucked at green htc loading logo now i am just hoping for nand. strange thing its the volume down and end does not bring bootloader anymore.
I am new to XDA because I'm knew to the HTC HD2 T-mo USA. I like Win 6.5, works fine, but have the need to tinker. Seriously, have been researching how to install Android for about 12-14 hours combined. See plenty of guides that are not easy to understand, and then don't mention HSPL, etc. Could anyone help me safely install? I have loaded (but not installed) froyo sense 3.2 and dual boot loader. Everything appears to be okay, pressed clrcad, then hared and the HTC logo comes up??? I have not installed HSPL, is that the problem? A complete layman's guide would be very helpful. If I install HSPL can't I just remove my sim card to not lose contacts? Links to help, will probably not be helpful, I think I've read them all, as well as the rest of the Internet.
My info:
Radio 2.10 stock
Rom Vers. 2.13.531.1 stock
Thanks to all here, you guys are way beyond me and your mercy would be appreciated!
When you saw the htc logo how long did you wait for? If it's your first boot then boot time should take roughly 20 mins max. Unless you've downloaded a data image with the build you're trying out and placed the data image in the same android folder, then boot time should be faster. So if you didn't copy a data image file that you've downloaded, into the android folder, go into the android folder, delete the data image file that the system has created, and try to boot android again, wait for about 20 mins and android should be ready, complete the setup or not (DO not install any apps). Then reboot your phone, start up android again, then you're ready to go. HSPL does not remove sim contacts if i remember correctly.
The only problem with HSPL is the possibility of voiding your warranty.
Thanks!
First, thanks for your reply. In videos about installing, after people click haret, massive amount of script(?) start running, that just never happened. HTC logo comes up instantly, waited about 10 minutes, due to many people saying it took about 7 min. I was just expecting scrolling script/code(?)
Again, thanks for your help. I will certainly wait longer if that's what you believe I should do. Does HSPL need to be installed to install Android? Seen talk about radio, appears my 2.10 version is okay?
It's okie, it's normal for current android builds not to show those massive amounts of scripts. If i remember correctly stock roms don't really bode well with android so i suggest you flash a custom rom. I would recommend you HSPL the device first however since HSPL is recommended for both flashing winmo and booting android, HSPL 2 or 3 will do. You can remove the HSPl by flashing a stock rom through sd card when you don't want the HSPL anymore.Your radio is okie i think, i'm not sure about the prerequisites for running android on a t-mo hd2 however.
Hi, the videos you have watched are of the older versions of android which showed all the script when launching linux. Now they are all nicely concealled under the HTC logo, if you want a nice safe build to get you started, try darkstones superRAM rom.
It loads itself onto your ram rather than running off the SD card, and also runs perfect on stock phones without HSPL.
Simply drag+drop onto your SD card then lanch CLRCAD+haret, and away you go.
Heres a link:
http://forum.xda-developers.com/showthread.php?t=870518
Hope this can get you started
Yes I believe you have to use hspl for your phone for the android process to be complete and work properly.
phoneman09 said:
Yes I believe you have to use hspl for your phone for the android process to be complete and work properly.
Click to expand...
Click to collapse
No, you do not need HSPL, I use Android every day on the ROM in my sig, with regular stock SPL.
No robot voice, no SOD, everything works.
Just place the Android folder on the root (not inside any folders, just on the sd card) of your sd card, go into file explorer in WinMo, navigate to Android folder, press CLRCAD, press Haret, and enjoy Android. First boot can take 10-15 mins.
try this,its very simple very quick to do and works very well
http://forum.xda-developers.com/showthread.php?t=870518
Problem:
Won't boot into any ROM.
Phone Details at Start:
Telstra HD2, HSPL 2.08, Radio 2.15.50.14, magldr 1.12, Windows Phone 7
Description:
I was running Windows Phone 7 when it decided to crash and restart. However it got stuck in a restarting loop; restart then crash during loading which caused it to restart then crash, etc. Then magldr came up with 1EFATAL HIT 1.
I figured WP7 had somehow corrupted part of the install but nothing I can do seems to fix it.
I have tried:
-Reflashing it with WP7.
-Reflashing it with another WP7 build.
-Reflashing to magldr 1.13 then WP7 again.
But none of these worked so I tried to go for a NAND Android build. However I couldn't get the ClockWork Mod to work. It too failed to boot with the same problem as WP7. Now I just wanted to get the phone in a working state again so I have tried:
-Formatting the SD card
-Reflashing to a custom winmob6.5 build
-Reflashing to a custom winmob6.5 build I had previously used and worked fine
-Changing the Radio to 2.14.50.02 then reflash to a custom wm6.5
-Changing the Radio to 2.12.50.02_02 then reflashing to a custom wm6.5
When I try the custom wm6.5 rom I see the boot screen but it just sits there and goes no further. I have tried installing an old copy of the chunky rom (as it changed the boot screen ) but still just sits at the boot screen.
I have tried redownloading all of the files I'm flashing with in case there was a problem downloading it. Also I have tried using files I already had which were working, but nothing seems to have fixed it.
Some things I have noticed are:
-that all flashings have and still load without error
-that it doesn't have any problems loading into the HSPL
-when ever I tried an install with magldr usb flash (CWM or WP7) it would work but at the end of the flash it said it would restart but never did. I had to remove the battery
-loading into magldr I could select the restart or powerdown option but it would just hang and again I had to remove battery to turn it off
Does anyone have any suggestions as to what I can try to get it fixed? The only things have haven't tried are flashing with a stock rom or reflashing another HSPL. Both of those I though could cause trouble for the currently working HSPL, which if I lost would cause more problems. Currrently I am under the impression it is a hardware failure as no rom (mb6.5, WP7 or CWM) will boot and magldr installed fine but wasn't able to restart the phone.
Check your battery pins to see if they're in anyway bent. If they are, just push them back a little bit with your finger.
Have you tried Task29? I think the only other way would be to flash stock again and start over.
Sent from my HTC Vision using XDA App
Skellyyy said:
Check your battery pins to see if they're in anyway bent. If they are, just push them back a little bit with your finger.
Have you tried Task29? I think the only other way would be to flash stock again and start over.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Yes, I have tried Task29 and then tried installing both magldr then CWM and wm6.5. It however didn't make a different as I still got the same error. Sorry, I forgot to mention this in initial post.
I have also read about the battery pins being bent. I haven't tried it but from what I can see mine are all about the same height and seem pretty straight. When I put in the battery they also seem to be pushed back a bit so I am assuming they are all making contact. I was a bit worried about over extending them but I might give it go if no other option becomes available.
I've seen several times people with a phone that seems to flash, but nothing actually changes.
The only way you can visually test this in your current state is to change spl to something different, and look in bootloader see if it changed, but you said you don't wanna, so.
You can try flashing HSPL 4 and select HSPL 3.03 and see if gbiz is sucessful. If you have HSPL 3.03 in bootloader then you know it is flashing and you can go back to HSPL 2.08. Also you can try flashing your stock Telstra ROM via USB cable and computer as this method will not change your HSPL 2.08 but flashing it via SD card will revert you back to SPL. I think flashing the stock ROM will be your best bet for now.
Well I originally had the energy boot screen and when I flashed to a copy of the chunky rom it changed to its one. I would have thought it was at least partly flashing. Also I have removed with magldr with task29 then reflashed (with magldr) and was able to boot into magldr. So I think the flashing is happening successfully.
I you think reflashing the HSPL could work then I'll give that a try. As I haven't done that yet. If that doesn't work I'll take a look at flashing the Telstra ROM. I know flashing a stock rom is mentioned as a solution but I wasn't sure why I would make the phone work any better than a custom rom with concerns to booting.
Thank you for your suggestions.
Just to cover all bases here, your HD2 is not getting really warm or warmer than usual is it? If so this is a sign of thermal breakdown, but like I said this is just to cover all bases here.
From what I can tell it hasn't been getting any hotter than usual.
Re:"why to use stock instead of custom"
Its because a stock rom flashes everything, spl, splashscreen, radio and rom.
Also, some customs use a secondary splashscreen, which would replace magldr, so if things aren't right, starting over by flashing your correct rom is often advised just to draw a line under the current attempts and start over.
Don't forget that even if the stock flash fails, if you did it from bootloader then Hspl is likely gone, and magldr too, possibly.
Just an update. I flash a Telstra ROM which to my surprise it booted... after a couple of tries. Decided to reboot it to see if it starting up was just luck which it turns out it was. I couldn't get it to start again then it refused to even get into the bootloader. So I am sure enough now that it is a hardware failure and am taking it in for warranty.
Thanks again for the help.
I have been using NAND since the public release on NYE. Most recenly when updating ROMs I had tons of freezing, & still do. Initially i thought it was a problem with the SD and did the panasonic format util & tried booting with no card at all. Same **** happened again. So I thought to flash a stock rom (winmo6.5) and see if there were any problems. I figured let's do a Task29, I even reflashed the radio & HSPL. When I flash an offical or custom ROM its gets to like 53% and then vibrates like 5 times. The process finishes normally, but upon reboot it makes the same 5 vibrates and stays stuck on the "Stick Together" screen. Also I did get OzDroid to fully boot one time, but the screen was unresponsive 100%. I don't know what the deal is, but this is all the stuff I know how to do & after much searching I still don't know what the multiple vibrates mean. I don't know if its time to send it in or what
Try to redownliad another official rom. Maybe it was F'ed up
Already did that. Tried using the SD method using LEOIMG.nbh on the root, by renaming the the official Tmousa .exe to .zip and extracting the RUU_signed.nbh
I got it to boot finally, but when it came to the initial settings screen (picking carriers etc) it got completely unresponsive. I have tried flashing an Energy rom, OzDroid, official tmousa ship rom, t-mobile.com official update rom; All ending in failure. I think UltimateDroid fried it.......i'm gonna cap who ported that crap
Edit:
I got it working again by doing a factory restore (vol+ & vol-) + power, and then flashing the most recent RUU_signed.ngh found in the latest tmousa .exe - Haven't tried to flash magldr or any other roms as I suspect the nand/and/or ram is damaged. We'll see how it goes, it may have been bad sectors or a ****ed up allocation of some kind. Hopefully this fixed it.
Edit2:
It's still ****ed.......tried to install magldr and it works.......sometimes. Sometimes it won't load the recovery at all. Sometimes it boots the android rom all the way and then freezes when it gets to the initial setup screen (which I have also tried bypassing w/the 4 corners method) but it still freezes eventually. Guess this piece is ****ed.
That sucks man. Definitely something wrong
Hehe good luck bro
It's probably user error. I'm almost certain it is as no HD2 will mess up from nand. You should sell it and get a nokia 3595. Leave the smart phones to smart people.
Alas, the old companion HD2 seems totally locked...
In my attempt to flash to an Android ROM, I spent two whole days digging through XDA. So I got me the HD2toolkit, a backup stock .exe, and the target ROM.
installing hSPL worked
magldr wouldn't install. So I updated the phone to get the right radio. This unfortunately upped hspl to 3.03. So i downgraded that by installing hspl4 and opting for 2.08.
Magldr then installed nicely, but the phone would not restart: the OS wouldn't start.
So I task29 succesfully, and install the windows update on the phone again. Works just fine.
Back to installing magldr, since hspl is still at 2.08 according to the tricolor screen. (that surprised me, since at the first time it went to 3.03).
And then it all went to bits. I get an HTC screen on white background, but no 'quietly brilliant' for 5 mins. Going to bootloader works, it recognizes the USBcable (can hear the telltale sound on the PC as well), but no data can be sent across that cable... No hd2toolkit orders (202 connection errors), and no official ROM executables will connect.
Tell me, is this now an official brick? Or might one of you have The Ultimate Revival Secret for me?
myrtthin said:
Alas, the old companion HD2 seems totally locked...
In my attempt to flash to an Android ROM, I spent two whole days digging through XDA. So I got me the HD2toolkit, a backup stock .exe, and the target ROM.
installing hSPL worked
magldr wouldn't install.
Click to expand...
Click to collapse
do you mean magldr wouldnt START? see note at the end**
So I updated the phone to get the right radio. This unfortunately upped hspl to 3.03.
Click to expand...
Click to collapse
no need, you could have just flashed teh radio, thus avoiding changing teh whole rom, removing magldr and hspl, and taking about ten minutes less.
So i downgraded that by installing hspl4 and opting for 2.08.
Magldr then installed nicely, but the phone would not restart: the OS wouldn't start.
Click to expand...
Click to collapse
ummm, what OS? you havent flashed one yet
So I task29 succesfully, and install the windows update on the phone again. Works just fine.
Back to installing magldr, since hspl is still at 2.08 according to the tricolor screen. (that surprised me, since at the first time it went to 3.03).
Click to expand...
Click to collapse
spl is prevented from being changed by usb flashing once hspl is installed
And then it all went to bits. I get an HTC screen on white background, but no 'quietly brilliant' for 5 mins.
Click to expand...
Click to collapse
again, there is nothing to boot, , flashing magldr removes winmo, and you havent yet flashed an android rom.
Going to bootloader works, it recognizes the USBcable (can hear the telltale sound on the PC as well), but no data can be sent across that cable... No hd2toolkit orders (202 connection errors), and no official ROM executables will connect.
Tell me, is this now an official brick?
Click to expand...
Click to collapse
not even close. So far everything sounds like a simple missmatch between magldr spl and radio, made more confusing because you arent really 100% sure of what exactly is being added / removed at each step. (Sorry, not having a go, just being blunt )
the connection errors might be an issue, but probably not, give your PC a reboot, use a different usb port.
in bootloader, what do the top line, and the spl line say? does it say USB at the bottom?
With your phone in bootloader and connected to PC, on the PC, click start - right click 'computer' (or 'my computer', depending on win version) choose properties, find device manager, and see what entry is listed for the phone.
**NOTE when you flash magldr, if the radio or spl is wrong, magldr will be there, it just wont show up, it will go straight to the boot screen and hang there. You dont have to re flash magldr, just change the spl/radio to the correct ones, and magldr is still there and should start, no need to re flash it. Magldr is only removed by flashing a stock winmo rom (or a cooked winmo rom that includes splash screens)
Be still, my beating heart...
Thanks for your answer, Sam. No harm done in the bluntness, you quite rightly marked me as a noob. Indeed not all is clear on the boards, but we all do our best.
As you said, I had no clue all the OS on my phone were gone. So i saved me another ten minutes (thank you, again) and flashed a new radio. And behold! Magldr is back!
You, sir, should be kissed!
Now to find out how to install a Zimage, that still seems to elude me (seeing there is no daf.exe or install.exe)... I'm aiming for this one to install: http://forum.xda-developers.com/showthread.php?t=1250703. hd2toolkit will only help out on nb or nbh, though.
If you could point me in the right direction?
And muchos thankyous are coming your way!
well first up you should add cwm on top of magldr, most roms are clockwork(cwm, cwr its called slightly different things, all mean the same, , 'clockwork mod recovery') roms.
You can do this with the toolkit, but instead of the hd2 being in bootloader, enter magldr and choose 5 usb flashing, then in the toolkit, choose a partition size, (160 by the looks of it, for an eu model) and when thats done,
restart,
enter magldr
option 8 ad recovery - will start cwm,
then choose 'install zip from sdcard' - 'choose zip from sdcard'
but remember BEFORE you do all the above, you should
1 - set up your ext partition (you can do that in cwm, , 'advanced' - 'Partition sd card', but be warned it will wipe the whole card)
and
2 - copy the romname.zip onto teh sd cards fat32 partition.
EDIT - oh and most roms have two versions, a magldr version and a cLK version, dont confuse cLK with CWM, theyre different things. For now stick to teh magldr versions, you can find out about cLK later.
Now we're getting places!
So if I understand correctly, the toolkit has not installed CWM. OK, I'll go and look for that rom.
However, the android I pointed out is, if I read you correctly, not NAND? It was posted in the NANDcategory, so that confuses me. Bummer, I need my SDcard for data.
yea its a nand rom. most nand roms use an EXT partition, and for most sense 2 roms, its advisable, and for sense 3 roms it simply wont work without it. Look at the partition size for the tmous version(which is the same but doesnt use an EXT),,,435meg, that's just for the system partition, it would leave you about 50meg for apps and data.
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
myrtthin said:
So if I understand correctly, the toolkit has not installed CWM. OK, I'll go and look for that rom.
Click to expand...
Click to collapse
not a rom, as such. Go into the toolkit, with teh phone in magldr, option 5 'usb flashing',,at the top of toolkit 'magldr repartition', below that click the 'custom' size, below that cache size 5 (from the 5/160/5, personally i use 45 regardless of what teh rom says, but thats just me, its not absolutely critical), then below that 'repartition', , a popup will ask you teh custom size, 160, OK,and off it goes installing cwm.
Hm, interesting.
Thanks to your feedback, i get magldr 1.13 up and running, just fine.
Next to that, flashing ROMs seems to be working smoothly.
However, none of the android ROMs are taking! I downloaded (from several sources to exclude download errors) three ROMS:
1) rom Based RUU Desire HD 3.06.405.1 - With sense 3.0 - Android 2.3.5 http://forum.xda-developers.com/showthread.php?t=1264828
2) Desire_S_sense3.5_Android.2.3.4_v1.2_EU.zip http://forum.xda-developers.com/showthread.php?t=1250703
3) GBLeor3 http://forum.xda-developers.com/showthread.php?t=1256581
nrs. 1 and 3 are installing, but on startup hang on HTC's splashscreen. Nr 2 is not installing (aborting during install, status 0), tried both on 5/160 and 5/200.
Seems like android install through magldr is not working at all! Any thoughts?
To be complete, I installed:
hSPL 2.08
magldr 1.13
radio 2.15.50.14
repartitioning through hd2toolkit
It all started with stock winmo, wich i updated to 3.14.404.2. It's an EU phone.
Don't forget it takes a while on first boot, especially the large ones,I can well believe a sense 3 rom that is writing 300+ Meg to the ext partition would take well in excess of ten/fifteen minutes and more first boot.
Also, if you flash a rom and then go to flash another, you will be leaving parts of the old rom on the SD card. In cwm before the flash choose wipe data/factory reset. That's in cwm, not magldr. Also, did you set up the ext through cwm?
My advice would be go for a simpler rom, one of the cm7 roms, typhoon for example, purely to show its working.
The desire S (sense 3.5) did not even install after 6 hrs, so I'm guessing something's wrong there ;-)
I'll wipe data between flashes, and per your suggestion, try something light as an appetizer first. Not before next weekend though! I lost enough sleep )
Thanks again!
When I started flashing nand, very often(six times in ten maybe?) the first boot never completed, and I soon learned that if after a few minutes nothing happened,I'd pull the battery and it would Start the next boot. Also, keeping the hard keys lit (touch every min or so) seemed to help.
I know I'm straying into "lucky socks" and good luck charm territory,but can't help to try, and I DO know I've seen one rom in the past where the instructions mention keeping the screen on as being important, so who knows?? Not this stoned and overtired techaddict!
I've had a stable rom that I've been just flashing updates for some months now, so I've not had that situation for a while. The wipe data command in cwm is deff important tho.
The only other thing that consistently causes non starting is too small a partition size.
cyanogen is stable
Yub yub, commander, time for an update. Cyanogen has been installed and working for close to 3 months now. So it actually does all work!
On the boards, I can now see updates on the ROM I crave (sense 3.5 from htc desire), and those updates are suggesting 260 Mb partitions (no ext). So it would seem my first partition was indeed too small.
So tempted to try those again...
Too bad cyanogens rom backup is acting weird. Otherwise it'd be no problem just to try, eh?