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.
Related
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.
I have been trying to help a friend install Android on his HD2. We actually had it working but didn't know anything about APN so we couldn't figure out how to get the 3g data working. Ultimately I wound up flashing it back to Windows, and then figured I would try flashing Android again after that. Unfortunately we are now stuck with Windows because it seems that we cannot flash MAGLDR. When we try, the progress bar sits there, stuck at 0%.
I had downloaded the image from T-mobile's website here:
http://www.t-mobile.com/wmupgrade/
But I found this post archived:
http://forum.xda-developers.com/archive/index.php/t-612580-p-78.html
It has some information stating that "If you cannot reflash and you stay at the 0 percent screen, then another solution is to flash first an original stock HTC ROM (1.66). Enter bootloader, connect to PC/Laptop and flash this ROM. When that has been succesfull, you can then reflash Artemis ROM."
Unfortunately the ROMs they are referring to (1.66, 1.72, etc.) appear to be non-US ROMs. I found the 1.72 website for the UK:
http://www.htc.com/uk/SupportViewNews.aspx?dl_id=936&news_id=638
But the site specifically says not to use that ROM to flash a T-Mobile(US) HTC HD2 as doing so can have unintended consequences. Is this true even when using HSPL? As part of the Android process we obviously had to install HSPL 2.08. I thought the point of HSPL was that you could always flash a ROM and even if the ROM didn't work, you will drop into the bootloader where another ROM can be flashed. So basically you can't brick the device any longer since you can always access the bootloader and flash a new ROM.
It seems people had success flashing one of those 1.66/1.72 ROMs and then installing some other ROM. I tried using the US ROM and it flashes just fine (doesn't get stuck at 0 percent) but when I try reflashing MAGLDR it just gets stuck. I don't intend on booting up and using the UK ROM...I'm just curious if I can flash that on this US based phone and then try to flash MAGLDR again to see if it works. Is this a good idea?
Oops...didn't mean to post this in the dev forum! Moderators please feel free to move this to Q&A.
flash any non tmous compatible cooked rom to a tmous and it wont boot past the RGD screen.
flash any STOCK non tmous rom to a tmous and it is bricked, full stop, dead. The radio contained in non tmous roms is permanently fatal to tmous phones.
This is true regardless of HSPL or any thing.
Simply put, you should never flash any rom where the chef doesnt explicitly state tmous compatible.
I havent used artemis, though glancing through the first post i see it is is based on the Leo S 3.14 rom, which is for the regular hd2 (LEO S means regular). What it doesnt make is any mention of tmous compatibility, so unless someone knows for certain i'd stay away from it.
Is this a good idea?
Click to expand...
Click to collapse
not at all.
If your aim is magldr, put phone into bootloader, connect usb, run hspl4, choose 2.08.hspl, your radio is already OK, because if it wasn't your phone would already be bricked (all tmous radios are ok for magldr by default), return to bootlaoder, flash magldr.
EDIT - Oh and once you are on android, you dont need to worry, all roms are tmous compatible.
Great thanks for the info...I definitely don't want to brick his phone with an incompatible radio. As for loading HSPL 2.08 that is precisely what I did. I flashed Windows back on there, then flashed HSPL 2.08, then tried to flash the same radio. It got stuck at 0% so I pulled the battery and tried again but it was a no go. So then I just tried MAGLDR and it also got stuck.
At this point I read the thread about flashing Windows back so I tried that again and am still unable to flash MAGLDR. You think I should flash HSPL again and then it will work? I think I used HSPL 3...so maybe I need to try HSPL 4.
Sent from my Evo via the xda app.
Also I don't plan on using Artemis...I just found that post while trying to fix the 0% issue while flashing. I had installed prj clean desire and he really liked that. He isn't too techie so I don't worry about him wanting to flash new ROMs to try them. As long as it is not Windows mobile he is happy. Unfortunately he is stuck on that for the moment.
Sent from my Evo via the xda app.
hanging at 0%, , two possibles, either you accidentaly chose 2.08.0000 instead of 2.08.hspl when you ran hspl, or your computer is timing out, in which case dont touch the phone, reconnect to a different usb port and run the flash again.
Also, if you flashed that http://www.t-mobile.com/wmupgrade/ 3.14 rom from there, then you already have the latest radio and dont need to change it.
Oh snap you might be right...I might have chosen 2.08.0000 and not the HSPL version. I seriously doubt the computer is timing out because it works fine with that same USB port to flash the Windows ROM. I bet you're right and I just flashed the wrong SPL! I'll get his phone and just bring it home with me soon. He can use his old phone for a day or two while I iron things out.
I'll try to remember to login from my computer and hit the thanks button. I don't see any way to do that in this app...
Sent from my Evo via the xda app.
gamblor01 said:
it works fine with that same USB port to flash the Windows ROM.
Click to expand...
Click to collapse
also worth considering - once magldr is running and you are into the android side of things, go into wmdc without phone connected, choose connections settings (or whatever it says) and UNtick allow usb connections, , you don't want wmdc grabbing the usb connection. (probably also need the "google usb driver" if its your first time with android on that pc,, google them.)
Flashing from bootloader needs that box ticked, hence the slightly confusing instructions in flashing guides to 'get an activesync connection', it doesn't really mean a sync connection, but that those drivers have grabbed the usb.
samsamuel said:
also worth considering - once magldr is running and you are into the android side of things, go into wmdc without phone connected, choose connections settinsg (or whatever it says) and UNtick allow usb connections, , you don't want wmdc grabbing the usb connection. (probly also need the "google usb driver" if its your first time with android on that pc,, google them.)
Click to expand...
Click to collapse
Yeah that causes a different error. Something about USB init failed and it complains about a source file called rspl.cpp or something like that. I had to fix that issue before I could ever install the prj ROM the first time. It's ActiveSync 4.5 though (I'm running XP on this partition -- I don't buy any Microsoft products any longer -- or Apple for that matter), but the steps are essentially the same. You just have to prevent it from establishing USB connections.
@samsamuel
Thank you so much for all of your help! I got his phone back today and it looks like the Windows ROM flashed 2.10.0000 on there. I launched HSPL3 again and this time made sure that I selected 2.08HSPL. It flashed right on, as did MAGLDR 1.13, and ultimately the prj clean Desire ROM. It's back to working again and we'll plug in the APN settings when I give it back to him tonight. Victory!
gamblor01 said:
Victory!
Click to expand...
Click to collapse
heh, a happy ending, nice.
Hi there,
Its been couple of months that my phone froze during web browsing. And when I pull the battery out and reinserted, the phone would go through the booting and either freezes right after 123456 go go go or it would freeze during the Android Logo loading. It would take me many battery pull outs and re inserts to get it back on. During this time, I ran Hyperdroid 2.3.4 on NAND with Mgldr 1.13.
yesterday I tried to reinstall the OS, i task29, reflash the radio to 2.15... and reinstalled mgldr1.13. I have chosen Typhoon's 2.3.5 NAND CWM. After the installation, the same problem of not being able to go past 1234 go go go persists. I tried to pull out the battery again and after few try i managed to log in to Android.
It seems, the longer the battery is out, the more effective it is in booting the OS. I am seriously concerned about HW issue. Please help me identify the problem.
Thanks
Did you try installing the stock Winmob ... then doing a clean android installation (complete with re-installing the HSPL)?
I am going to do that next. It seems, all freezing during normal operation happens when I am browsing on Edge (my phone is incompatible with 3G on the network i am).
Secondary note, when I remove battery and reinsert, not only I cant make it back to Android boot but also, when I load up Mgldr Recovery, the AD Recovery function also does not load beyond 12345...
I am going to load a WinMo 6.5 ROM probably NRG's and reinstall HSPL.
Parsian86 said:
I am going to do that next. It seems, all freezing during normal operation happens when I am browsing on Edge (my phone is incompatible with 3G on the network i am).
Secondary note, when I remove battery and reinsert, not only I cant make it back to Android boot but also, when I load up Mgldr Recovery, the AD Recovery function also does not load beyond 12345...
I am going to load a WinMo 6.5 ROM probably NRG's and reinstall HSPL.
Click to expand...
Click to collapse
as I said before... use the stock windows, not the cooked ones (you can get it off the HTCs website)...
maybe,,, make sure you have the right partion size for your rom. check your roms page, it should say what size you need. if you have the wrong size, your phone can do all kinds of stupid things. speaking from my own screw up thinking i had the right size,,,
Sorry for the late response. I am now flashing it with STOCK ROM. I couldnt first find on HTC thats why I went and download the NRG's ROM. Today I just found that HTC pulled the ROM and now they are only available on T-mobile website so eventually I got it and now installing it. I will update about the progress
Thanks
So I downloaded the ROM and put my phone into HSPL screen by pressing volume. I open the .exe file (ROM) and set it to install. However, during the installation, the process gets stock around 18% and I waited it out couple of times for more than 10 minutes and does not go pass that.
I tried to Task29 it and re-flash it but the problem maintains.
UPDATE: I re run HSPL and restore to SPL 2.8... and then run the Stock Rom installation. This time, it finished the installation however, when it booted up, it got stock on the pink logo "stick together"... I tried to hard reset by holding the Up and Down Volume and when i did it, and when through the manufacturing reset process, the problem maintains. I cannot get into Stock WinMo.
Thanks
My phone has the exact same problem. Doesn't anybody have a solution for this?
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?
Hello folks, I appear to have gotten into bother during a rom flash. After successfully installing a MAGLDR nand rom via CWM, the first boot of said rom just gives me the frozen splash screen without animation and the boot does not complete. Happens the same with three different roms.
I suspected somewhere further back in the boot process was at fault so I reflashed a known working radio rom, but problem still persists.
Despite a LOT of reading I can't see much about freezes at this point in the boot process on MAGLDR roms.
Bits that work - HSPL rainbow boot screen happily comes up, Task 29 works, magldr reinstalls and works fine, CWM perfect. Installs roms from SD (freshly reformatted) and appears to be ready to go, until boot actually begins then... splash screen freeze.
I have redownloaded various versions of everything to ensure no issues with corrupt files. I have also used different SD cards and ensured freshly formatted FAT32.
If it helps anyone, I have previously used NDT CM7 12.1 for about a month with zero problems.
Any other less obvious stuff I'm missing?
I'm off to bed so will be approx 7 hours from post time when I start responding. In the meantime I've put MAGLDR 1.10 on the phone so at least it can charge!
Many thanks in advance for reading.
Replying to self with update:
Installed OzRom Winmo 6.5 via the tried and trusted CustomRUU method, and it appears to work perfectly. What is winmo doing that android nand roms don't? I assumed if there had been bad blocks on the nand the much larger windows mobile rom would have covered this, and thus failed on boot.
At least opens the door to using an SD build till I can troubleshoot. Odder and odder.
Forgive my ignorance, but if the CustomRUU flash method still works for me, are there any modern android roms that don't need MAGLDR or clk?
Again, many thanks.
drachers said:
Replying to self with update:
Installed OzRom Winmo 6.5 via the tried and trusted CustomRUU method, and it appears to work perfectly. What is winmo doing that android nand roms don't? I assumed if there had been bad blocks on the nand the much larger windows mobile rom would have covered this, and thus failed on boot.
At least opens the door to using an SD build till I can troubleshoot. Odder and odder.
Forgive my ignorance, but if the CustomRUU flash method still works for me, are there any modern android roms that don't need MAGLDR or clk?
Again, many thanks.
Click to expand...
Click to collapse
How long have you been leaving the ROM on the boot screen? A first install of an Android ROM can take anywhere up to and over 15 mins for first boot. I also remember one when installing a hyperdroid ROM I had to restart the phone once to get passed boot splash.
I'd recommend flashing a popular ROM, leaving it for 20 mins, restarting and leaving another 20 mins. What do you have to lose? Just remember magldr doesn't have charge while off capabilities!
Also check your partition sizes and layout (you have to edit flash.cfg for magldr builds, partition sizes depend on the rom you pick but will be specified in the ROM thread).
Thanks for the reply. Each time I left the rom on the boot screen for a good half hour, and in one case an hour. I have installed NDT 12.1 and the newer v16 successfully before, so I know what sort of timescales are involved. I also had a go at an earlier Typhoon build. Naturally I used only the recovery sizes specified in each rom's own thread, using versions of MAG/CWM specified there, and Task 29 beforehand.
I have an update to all this, however. Previously I said Winmo installed, but now it is bugging out to all hell. This might fit my "bad blocks in nand" hypothesis, perhaps the files covering the bad area are less critical than the ones in each android build, and Winmo just crosses its fingers and tries to boot anyway!
In any case, if I can get an SD android build running I'll cut my losses and stick with whatever works.
Cheers again, hopefully this random screed of info will help people. Seems to be if all else fails, try winmo.