Related
Bugger. It was all working so well, then, in a 'diminishing returns' attempt at upgrading to the latest radio, I flashed wizard_radio version-2.25.11 from the Ftp site.
Bugger, has completely killed my wizard.
it is now 'running' unbearably slowly, with no radio connectivity, no activesync (so I can't flash another ROM), and, bizarrely enough, seems to have reset to an earlier ROM image.
Is there any way I can do a ROM install off the SD card? or does anyone have any bright ideas... (have tried hard resets but this returns it to a corrupt state; SPB back-up doesn't seem to do any good).
It's expensive brick time. Any help very much appreciated
well you say it's running slow therefore it isn't a brick, whynot just redo the ROM? perhaps the file was corrupt or you didn't get a good install for whatever reason, if it's booting up there is hope however
no AS connectivity!
there is a link on another post I missed earlier; am following up an let you know.
First things First....
What Rom version were you running prior to flashing the 2.25.11 Radio Rom?
Is your device CID unlocked (which is different from SIM unlocked).
IF you reset your device and enter Bootloader mode, then plug in the USB cable do you see "USB" in the lower left of the screen?
no 'USB'
hate to admit, but I didn't note down which ROM version; I installed this one RUU_Wizard_1050402_101_11210_O2_ENG.exe
two weeks ago (and of course it was running fine, but I decided to upgrade the radio from a '1.x' to an AKU '2.x', using wizard_radio version-2.25.11, which wiped the device!)
I am reading a couple of other threads, and there are a few people with similar problems.
After a hard reset, I get the RGB colour bars (as per normal bootlader) but only see IPL 1.01, two 'blank' lines, then SPL 1.01. the bottom of the screen, where I would hopeto see USB, is just a blnak white bar.
I am looking everywhere to see if anyone has a backup image I can copy to my SD card to run from there.
Ahem
yes, is CID unlocked
THE CURE
ok, thanks to the tip from a99tandem.
Reset, holding down the camera button, allows you to go into boatloader, and you can flash a ROM from the PC using RUU. Bootloader comes up with 'USB' in the corner.
Thank god for that; that's 5 hours wasted...
Now I'll explain what you did wrong.
If you read the thread that had all of the Radio Roms you would have seen that 2.x Radio Roms DO NOT WORK with 1.x Bootloaders (IPL/SPL).
You could have fixed your device by simply flashing a 1.x Radio Rom (there is one listed).
If you want to use a 2.x Radio Rom you must upgrade to a full (included Bootloader, OS, & Radio) 2.x Rom FIRST.
I hope this helps...
Fellow Android fans. I am out of ideas and could use a benevolent lending hand of help. I have been searching this site for three days now and have attempted everything I can think of (and have found in searches) to get my phone back up again. I have found a couple of posts where people were stuck at the splash screen but just wiping/reflashing typically fixed their issue. I however cannot get past the G1 screen after each boot regardless of the ROM NOR can I even access my SD card which I suppose are two different problems all together.
HISTORY: I have had every modified ROM since JF released his first version last year. I have flashed, backed up, changed radios, put apps/cache/data to my SD (8gb Class 6) with rare issues. The couple times I did get stuck at the splash screen, I would just use Fastboot to go back to a backed up nandroid ROM. But then I decided to go to the latest JF Lucid 1.5 ROM. That’s when it all went downhill. (Certainly no one's fault but my own I know) Though I wiped initially, it seemed that some links were still stuck on the phone for I couldn’t get my apps to SD. The ROM was working fine and I could install market apps without issue, but I wanted to have 100+ apps for absolutely no good reason other than “because I could.” So I was talking with Marcus who suggested I repartition my SD card. This is where the noob came out of me. My trial period had ended with Partition Manager so I used Window’s Device Manager to delete the partition (I backed everything up thankfully) After I did so I powered down the phone to see if all was ok. It wasn’t. It just gets stuck on the G1 screen.
Attempts to Restore:
• I can access the Recovery tool and wipe/flash an older known working update.zip file and it says that it loads successfully, but when I reboot I get stuck at the G1 screen.
• I can access Fastboot and flash a backed up ROM (known working backups that have worked before mind you), it says loaded successfully, but when I reboot it gets stuck at the G1 screen.
• When I insert my SD card into a card reader I cannot access the card as it says “insert disc”.
• I went into Windows Device Manager and it shows that have a memory card but says “Unreadable”.
• I put an older 2gb SD card in the phone and loaded an older RC33 ROM and flashed it. It flashed just fine but gets stuck at the G1 screen.
• So I downloaded the Ubuntu Live CD and attempted to reformat my SD card via Gparted. No dice. It won’t even recognize it as an available disk. (I tried both with it in my phone connected via USB and in the micro SD card adapter and card reader)
I have Windows XP, a Ubuntu Live Cd, JF Lucid 1.5, and a headache after the numerous failed attempts at getting this straight.
I am completely out of ideas. I am not however, familiar with ADB so I am really hoping that there are some commands or something out there can bring my phone back from the dead. If I have to buy a new SD card, so be it, but I am trying to avoid having to buy a new phone. Long story short, I suppose my question is two fold:
1) By deleting my partition did that ruin the SD card and ultimately cause these boot loop issues? I just can't figure that out how that is possible since a partition isn't even a requirement of flashing a ROM
2) Is it possible to reclaim my phone and if so, how?
Thank you very much for your time and any suggestions...
Haters Need Not Post
Interesting problem you got there. Not that i have any answers for ya, but a few ideas. I've read the boards here for a lil while at least, and i know that if you had custom boot images, the second one can cause hangs when switching to certain roms. You didn't say, have you tried flashing the original dreamimg.nbh? When you formatted your sdcard, did you have apps to sd and that dalvic cache to sd card too? possibly pointers on the main partition pointing to a non existing mount point. Hope you get it up and running again
what spl were you on? have you tried the sapphire spl? or hardspl?
I've done this before too. Easiest way to fix it is to flash DREAIMG.NBH, and then re-install test keys and the SPL of your choice and reflash JF1.5
I forgot to mention that yes I had apps, data, and dalvik all moved to the SD card but NO custom boot images. I am assuming the data or dalvik move is what caused the initial problems when I flashed to ADP 1.5. I currently am running the HardSPL (HSPL10.95.3000)
I haven't tried flashing the DREAIMG.NBH yet but assumed it wouldn't work as I have flashed numerous other ROMs to no avail. I suppose I shouldn't assume. I will try that today. On the other hand, any ideas on how to reformat (or just make it recognizable for that matter) my SD card?
Thanks gang!
bahnburner said:
I've done this before too. Easiest way to fix it is to flash DREAIMG.NBH, and then re-install test keys and the SPL of your choice and reflash JF1.5
Click to expand...
Click to collapse
How do I go about reinstalling the test keys? And do I need to flash to an SPL other than the HardSPL (which I have now) for the DREAIMG.NBH to flash appropriately?
Thanks man
gPhunk said:
I forgot to mention that yes I had apps, data, and dalvik all moved to the SD card but NO custom boot images. I am assuming the data or dalvik move is what caused the initial problems when I flashed to ADP 1.5. I currently am running the HardSPL (HSPL10.95.3000)
I haven't tried flashing the DREAIMG.NBH yet but assumed it wouldn't work as I have flashed numerous other ROMs to no avail. I suppose I shouldn't assume. I will try that today. On the other hand, any ideas on how to reformat (or just make it recognizable for that matter) my SD card?
Thanks gang!
Click to expand...
Click to collapse
flashing the nbh should be the way to go .. it basically images the whole phone .. whereas flashing the ROM files does not .. each update.zip only deletes the /system portion of the phone .. performing ALT+W deletes the /system AND /data portions of the phone
flash the nbh like you were starting from scratch with the root process .. go back thru all the steps .. put the new recovery.img etc blah blah blah
odd
I'm not real sure as far as the test keys go. But as long as your phone is rooted with a hard spl (which is just a edited engineering spl) you should be able to reflash any rom including rc29 (dreamimg.img) just rebember to go thourgh the bootloader to do so not recovery. The very way you originally rooted you dream.
Have you tried simply doing a wipe yet? Sounds like you need to clear out the /data partition, and be patient when it boots up the first time after a wipe - it can take a while.
LucidREM said:
flashing the nbh should be the way to go .. it basically images the whole phone .. whereas flashing the ROM files does not .. each update.zip only deletes the /system portion of the phone .. performing ALT+W deletes the /system AND /data portions of the phone
flash the nbh like you were starting from scratch with the root process .. go back thru all the steps .. put the new recovery.img etc blah blah blah
Click to expand...
Click to collapse
Thanks guys - The DREAMIMG flash worked. You truly are life savers. (My wife has been on my ARSE the last 4 days for this.. lol) I do have a quick question for Lucid.
First, thank you for ALL the fine work you have done. Basically all of my ROMs have been yours (and JF's of course). So my question is with the linking of the data and dalvik cache. Even though I wiped when flashing to 1.5 it seemed I still had file folders stuck in my partition which were preventing me from updating the links again. What should I have done to re-link them appropriately? I tried your "undodata / dalvik" scripts but still couldn't get them linked.
Again guys - Thank you
daveid said:
Have you tried simply doing a wipe yet? Sounds like you need to clear out the /data partition, and be patient when it boots up the first time after a wipe - it can take a while.
Click to expand...
Click to collapse
Ya I wipe with every flash. I even let it boot up overnight (as I read that it can take a while) but when I woke up it was still at the G1 screen. Have no idea what caused this but the DREAMIMG.nbh flash worked.
great news
Good to hear you got your dream up and running again. I'm happy to see the community so willing to help. Keep posting issues, keep responding to those who you think you can help. This is the reason why xda-devlopers site is the go to site for xda issues.
SDcard probs....
Did you ever get your SD Card working again?
If not, download the free version of killdisk from http://software.lsoft.net/KillDiskSuiteFree-Setup.exe and use it to wipe the entire sd card with zeros. After that, remove the card from your windows box then reinsert it. Windows should ask you to format it and you should be golden. I've seen this problem happen with flash drives as well and this always gets them back.
I suspect that the disk is dead. In any case, windonkey isn't the right thing to use to try to recover it. Boot on the livecd, insert the disk, type 'dmesg', which should output the device file, i.e. 'sdb', then as root do a "dd if=/dev/zero of=/dev/sd?" where ?=whatever that was from 'dmesg', wait until it finishes, pull the card, push the card, run gparted. More than likely, the output of 'dmesg' will show a problem with the card, in which case, melt it, burn it, break it in half, throw it out, warranty it, whatever makes you happy that results in you not accidentally trying to use the thing.
ipaqkiller said:
Did you ever get your SD Card working again?
If not, download the free version of killdisk from http://software.lsoft.net/KillDiskSuiteFree-Setup.exe and use it to wipe the entire sd card with zeros. After that, remove the card from your windows box then reinsert it. Windows should ask you to format it and you should be golden. I've seen this problem happen with flash drives as well and this always gets them back.
Click to expand...
Click to collapse
Thanks for the suggestion. Tried it but it couldn't write to it. I suppose it's hosed. Just ordered another. Thanks for your help though!
Can flash DREAMIMG.nbh - but not a modded ROM
I was able to regain my phone by flashing DREAMIMG.nbh. (thank you all) I followed all of the directions (to the "T") from this post (http://www.kyubinc.org/files/AndroidMod.zip) that I saw Lucid recommended in an April post. I was able to get through the steps and rooted the phone successfully (made sure I could get "#" when typing "su" into Term Em) BUT when I go to flash RC33, I get hung up at the freaking G1 screen AGAIN !!! <<I'd pull my hair out if I had any>>
I let it boot for 90min before I decided to request suggestions so I don't think it's a patience thing. The only error I noticed while rooting was when I entered the recovery console, at the top it said "Can’t open /cache/recovery/command". Can't remember if that was normal or not as it's been so long but it let me successfully flash the update.zip from the SD card so didn't think much of it. But when I rebooted it is stuck at the G1 screen.
Now I know that my 8gb SD card is hosed so am using the 1gb that came with the phone until I get my new one. So I am using a completely different SD card but am getting the same "stuck at the splash screen" issue. Anyone have an idea what in my phone is surviving all of these wipes/flashes that is perpetuating this issue? It just doesn't make since that I can flash an OEM ROM (DREAMIMG.nbh) just fine but not a modded one (RC33). I certainly am not ruling out user error, but it just seems like a directory or file or WHATEVER inside the phone has been corrupted or something because it's the only constant in this whole process.
Thanks again
dunno
When you went through the root process again did you reinstall the hard spl again. And then protect it
gPhunk said:
I was able to regain my phone by flashing DREAMIMG.nbh. (thank you all) I followed all of the directions (to the "T") from this post (http://www.kyubinc.org/files/AndroidMod.zip) that I saw Lucid recommended in an April post. I was able to get through the steps and rooted the phone successfully (made sure I could get "#" when typing "su" into Term Em) BUT when I go to flash RC33, I get hung up at the freaking G1 screen AGAIN !!! <<I'd pull my hair out if I had any>>
I let it boot for 90min before I decided to request suggestions so I don't think it's a patience thing. The only error I noticed while rooting was when I entered the recovery console, at the top it said "Can’t open /cache/recovery/command". Can't remember if that was normal or not as it's been so long but it let me successfully flash the update.zip from the SD card so didn't think much of it. But when I rebooted it is stuck at the G1 screen.
Now I know that my 8gb SD card is hosed so am using the 1gb that came with the phone until I get my new one. So I am using a completely different SD card but am getting the same "stuck at the splash screen" issue. Anyone have an idea what in my phone is surviving all of these wipes/flashes that is perpetuating this issue? It just doesn't make since that I can flash an OEM ROM (DREAMIMG.nbh) just fine but not a modded one (RC33). I certainly am not ruling out user error, but it just seems like a directory or file or WHATEVER inside the phone has been corrupted or something because it's the only constant in this whole process.
Thanks again
Click to expand...
Click to collapse
and you followed these steps precisely?
http://files.lucidrem.us/jf/ROOT/g1_root.txt
just making sure
O dear, I am experiencing the same issue - I pulled my SD out this morning was not able to get it recognized, and upon reboot got stuck on the splash screen. I have wiped several times and am still stuck at splash 2. I am at work so cannot try to access my card thru my PC to see if I am having the same problem as gPhunk, but can only assume that i fried my SD card. I am a n00b, so really nervous of my ability to get myself back up and running.
To install the dreaming.nbh, is it the same as any other flash - rename it update.zip and ctrl-s from the recovery screen? Does that bring back to an RC build so i have to re-root?
Help! And thank you so much!
LucidREM said:
and you followed these steps precisely?
http://files.lucidrem.us/jf/ROOT/g1_root.txt
just making sure
Click to expand...
Click to collapse
Similar - but the ones I followed were these
http://www.kyubinc.org/files/AndroidMod.zip
I will try this set this time..
Hey all, I hadnt visited xda for about 10 days until yesterday, to see how the different builds with Hero were going. Then I see the SuperHero post, and I remember that I have a partitioned 2gig MicroSD. So I go and re-root my phone(I unrooted due to rebooting issues) and install the HardSPL. After installing the Hard SPL, I try to Install Hay's Radio, then after a succesful Install, Install Hayk's SPL. Now, its kind of weird, but it doesnt want to boot. I got bricked and DREAIMG.nbh my way back to RC29. I read all about it, and saw that you need a PVT board and all that, which I do. I also remember he said there was a 99.99 Chance it will work with pvt, which, again, im guessing im that 0.01??? I am sure I have a PVT Board, it says PVT 32B or something like that..Its kind of awkward, so if anyone has any suggestions to tell me I would appreciate it. Also Mods if youre going to move this, please advice me first, I want to be able to track my Post.
I really could not track your steps but did you flash the radio update before you flashed the new spl?
Was it hung at the G1 screen? If so go back into the recovery and reflash the SPL. After it has completed, do not go into the console and type "reboot recovery". Instead reboot with the home and back buttons. It should then reboot twice and end back up in the recovery again. You should then be able to flash the ROM of your choice. That is what worked for me.
Vermithrax
Flashing the SPL will change the size of the system and data partitions of the internal memory, so you must flash your system again and wipe.
In general, find it there
Got the same problem, can't even get to recovery.
Hope there is a solution soon.
billc.cn said:
Flashing the SPL will change the size of the system and data partitions of the internal memory, so you must flash your system again and wipe.
Click to expand...
Click to collapse
And there it is.
Yes, I have been having the same problem as well, I believe a thread needs to be created in order to solve the current solution. There is no possible way for me to get into the phone what so ever at this time unfortunately. I am stuck at the G1 screen and I am unable to pass into recovery mode. Perhaps a brute force connection is necessary?
TylerKinkade said:
Yes, I have been having the same problem as well, I believe a thread needs to be created in order to solve the current solution. There is no possible way for me to get into the phone what so ever at this time unfortunately. I am stuck at the G1 screen and I am unable to pass into recovery mode. Perhaps a brute force connection is necessary?
Click to expand...
Click to collapse
This thread has been created. "Let's fix that SPL" by haykuro.
i bought this phone one month ago,it's great but in the last two weeks it starts to become very very slow, it happens one or two times a day, mostly after i have a phone call, when i end call it for a 5-6 sec still shows that it isn't end and after thet everything is very very slow, when the minute is changing on the clock it takes the whole 3-4 sec, terrible, only switching off or soft reset helps, and another thing i noticed is the battery, e.g. before this hapends battery is yellow and 53% and after it slows down and i switch it off or soft reset when the phone switch on it's on like red and 23%.please help and sorry on my bad english.
tino1708 said:
i bought this phone one month ago,it's great but in the last two weeks it starts to become very very slow, it happens one or two times a day, mostly after i have a phone call, when i end call it for a 5-6 sec still shows that it isn't end and after thet everything is very very slow, when the minute is changing on the clock it takes the whole 3-4 sec, terrible, only switching off or soft reset helps, and another thing i noticed is the battery, e.g. before this hapends battery is yellow and 53% and after it slows down and i switch it off or soft reset when the phone switch on it's on like red and 23%.please help and sorry on my bad english.
Click to expand...
Click to collapse
Hi tino1708,
since you have already performed a soft reset, you may want to think about a HARD reset, which is a complete wipe of the device back to factory condition - this will hopefully eradicate the problems you are currently facing, making your device function more efficiently.
Note: Everything disappears and you are left with a spanking clean device. This is done as a last resort.
Let us know if you think you would consider doing this.
Regards.
thank you mastoid for a quick answer i will try this. but i forgot something to ask, is it maybe becouse a hot fix to enhance response time for HTC Touch HD isn't installed, or what about a memory in use, the memory in use on my touch hd when i make soft reset, so when no program is started only the activesync is running i 32-41%, is this normal?
tino1708 said:
thank you mastoid for a quick answer i will try this. but i forgot something to ask, is it maybe becouse a hot fix to enhance response time for HTC Touch HD isn't installed, or what about a memory in use, the memory in use on my touch hd when i make soft reset, so when no program is started only the activesync is running i 32-41%, is this normal?
Click to expand...
Click to collapse
hmm... your cpu usage is quite high, especially since you do not have any other applications running in the background.
I would suggest that you can try the hotfix if you think it is related to your current problem - you should find this on the official HTC website:
Here is the link to the patch for fixing the response time issue: http://www.htc.com/www/SupportDownload.aspx?p_id=179&cat=0&dl_id=448
However, if your situation does not improve then I would suggest you also try a hard reset just to discover whether or not you have installed any software which could be causing device conflicts.
If you would like to perform a hard reset, please try the following:
1. With the device turned off, press and hold the VOLUME UP and VOLUME DOWN buttons, then briefly press the POWER button.
2. Continue pressing the VOLUME UP and VOLUME DOWN buttons until you see this message on the screen:
Warning! Your device will be set back to factory default settings. Please ensure any additional installed programs and/or user data have been backed up before a hard reset is performed.
3. Release the VOLUME UP and VOLUME DOWN buttons, press the VOLUME UP button to perform the hard reset, or press any other button to cancel the reset.
If you would like to be more adventurous, you could also try flashing your phone back to the stock ROM (and then maybe to a custom ROM of your choice) to see if this improves your phone's condition (i can also provide you with instructions on how to flash to a custom ROM)
Best of luck.
i will perform a hard reset just becouse of this high memory (cpu) usage that worrying me and only the activesync is running(it always running), it was suspicious to me to.thank you very much mastoid i will post my results tommorow.
regards.
tino1708 said:
i will perform a hard reset just becouse of this high memory (cpu) usage that worrying me and only the activesync is running(it always running), it was suspicious to me to.thank you very much mastoid i will post my results tommorow.
regards.
Click to expand...
Click to collapse
No problem mate.
I think it is best to try this step by step. Let us know how you get on.
p.s. there is nothing wrong with your English, it's very good
Things you can try...
Before you try the Hard Reset tomorrow, you can Backup any important data (i.e. Contacts, etc) using PIM Backup application. If your phone situation does not improve, then you can try the hotfix(s) on HTC's website.
If you still experience issues and nothing else works, then you can try downgrading (to stock ROM) and then upgrading (to custom ROM) your ROM version. If not already done so, you need to decide if you want to use HSPL (Hard SPL) or USPL (User SPL). USPL is a temporary upgrade in memory only, to make the change permanent (survive a reset) you should use HSPL.
You also need to check what SPL version you have, boot the phone holding the volume down button. This will put the phone in it’s “bootloader” screen. My phone had version 1.54 and I have a 1.56+ version ROM. In order to upgrade to a custom ROM you must change your SPL to allow uncertified upgrades, such a SPL has been made by “Olinex” and you must first install/flash this to you phone.
A guide and all the files you need are found in this tutorial; http://forum.xda-developers.com/showthread.php?t=505377. This will explain the terms more in detail if you want.
If you have any difficulty in following the above guide, you can refer to the following blog which explains the flashing process step-by-step:
http://journal.zenyee.com/2009/06/21/custom-rom-upgrade-for-dummies/
Please Note: Before flashing, make sure you have .NET Framework 3.5 installed and make sure your phone's battery is charged to at least 50%.
Regards.
thanks on your help end links. i couldn't wait till tomorow so i have performed hard reset now, i will see tomorow how the phone behaves and is it going to be slow again, but after the hard reset the memory usage is still 32% (with activesync running), why so high?
tino1708 said:
thanks on your help end links. i couldn't wait till tomorow so i have performed hard reset now, i will see tomorow how the phone behaves and is it going to be slow again, but after the hard reset the memory usage is still 32% (with activesync running), why so high?
Click to expand...
Click to collapse
There could be a number of reasons for this behaviour including applications running in the background. I remember when when memory usage used to be quite high, around 30% - 41% (even when left idle), which was quite normal in predecessor ROM editions, especially in Windows Mobile 6.1 OS, but the biggest changes for the latest ROMs was the incorporation of Windows Mobile 6.5 OS, which has been tremedously improved in the area of memory utilization and performance.
It may be worth checking the available memory in settings:
Go to Start/Settings/System/Memory and write down what the figures say for both Program and Storage memory.
Storage: Total 322.79MB In Use: 28.79MB Free: 294MB
Program: Total: 195.58MB In Use: 70.75MB Free: 124.83MB
Sometimes, simple things may work.
First, you should read about the ActiveSync tweaks (i.e. creating a fake server, etc.) cause ActiveSync (on your device) may also be a cause for slowdowns or lots of other trouble: http://forum.xda-developers.com/showpost.php?p=1078848&postcount=2 - who knows, you can always try, it doesn't hurt, for ActiveSync will continue working normally afterwards.
Next, you should install CleanRAM to help you clean RAM without rebooting (if it helps then there is some nasty app running in the background which should be uninstalled, check your list of recently installed apps/themes and list them here):
http://forum.xda-developers.com/showthread.php?t=514333
Finally, I can see from your signature that you still seem to use the old Blackstone ROM. HTC has released an official upgrade available in April 2009. So it may be worthwhile upgrading to the official ROM because a lot (!) of improvements have come with that upgrade (beware to backup ALL your data before doing anything like this or you will regret it !!):
http://www.htc.com/europe/SupportDownload.aspx?p_id=179&cat=2&dl_id=533 - this step should be taken once you know a bit more what you are doing ...
thank you georgeus2008, i will try some of this, but when i write my serial number it says Sorry, this software download is not suitable for your device.
Georgeous2008 said:
Sometimes, simple things may work.
First, you should read about the ActiveSync tweaks (i.e. creating a fake server, etc.) cause ActiveSync (on your device) may also be a cause for slowdowns or lots of other trouble: http://forum.xda-developers.com/showpost.php?p=1078848&postcount=2 - who knows, you can always try, it doesn't hurt, for ActiveSync will continue working normally afterwards.
Next, you should install CleanRAM to help you clean RAM without rebooting (if it helps then there is some nasty app running in the background which should be uninstalled, check your list of recently installed apps/themes and list them here):
http://forum.xda-developers.com/showthread.php?t=514333
Finally, I can see from your signature that you still seem to use the old Blackstone ROM. HTC has released an official upgrade available in April 2009. So it may be worthwhile upgrading to the official ROM because a lot (!) of improvements have come with that upgrade (beware to backup ALL your data before doing anything like this or you will regret it !!):
http://www.htc.com/europe/SupportDownload.aspx?p_id=179&cat=2&dl_id=533 - this step should be taken once you know a bit more what you are doing ...
Click to expand...
Click to collapse
As Georgeous2008 has mentioned, if the first two steps do not make any difference then i really think it would be a wise decision to upgrade to a newer and more stablr ROM version. I would definately first try the official ROM (April 2009) shown above from HTC's official website before trying a custom ROM - this way at least you know that you are upgrading to a stock version, which is standard.
tino1708 said:
thank you georgeus2008, i will try some of this, but when i write my serial number it says Sorry, this software download is not suitable for your device.
Click to expand...
Click to collapse
The serial number is specific to a region. You can either:
try changing the last 5 digits in the serialnumber you enter on HTC's homepage, and you will eventually find one that works with your language;
or
update your devices SPL version, then you can upgrade to the latest ROMs.
If it still won't accept the serial number then all you can really do is upgrade to a custom ROM version - many of these are stable and have been developed with many modifications and enhancements. I am currently using XannyTechROM GRID EVO 1.7C, which is a great ROM and I would reccommend trying this one out. Here is a link detailing the latest and greatest builds: http://forum.xda-developers.com/showthread.php?t=569715
Before you can do this though (upgrade to a custom ROM), as previously suggested, you will need to check your SPL version. Please refer to my previous post and this explains how to do this.
thank you both. ok i will try this steps,i also think that is beter to upgrade to newer version of ROM but i can't download it from the official site i will try to find some other link to it.
yes, i am from croatia and i can only select Europe home becouse there isn't listed my country
it worked i changed the last number from 1 to 2 end now i'm downloading thank you very muc mate!
this is what the bootloader screen says
BLAC100 32M
SPL-1.14.0000
MicroP-BlackStone (LED) v6
tino1708 said:
yes, i am from croatia and i can only select Europe home becouse there isn't listed my country
Click to expand...
Click to collapse
Yes, HTC is conducting a preliminary verification to ensure security when it comes to your device and flashing it. Based on the serial number you've entered, the system rejected it because most probably your device is from another region than the update addresses.
try this link, unfortunately i cannot understand your language so tell me if there is a ROM update suggested here for your device:
http://www.htc.com/cz/supportdownloadlist.aspx?p_id=179&act=sd&cat=all
Great
tino1708 said:
it worked i changed the last number from 1 to 2 end now i'm downloading thank you very muc mate!
this is what the bootloader screen says
BLAC100 32M
SPL-1.14.0000
MicroP-BlackStone (LED) v6
Click to expand...
Click to collapse
good stuff
keep us updated, especially if you run into any further problems.
EDIT: Yep, the Bootloader screen confirms that you still have your stock spl 1.14.0000 (very old) installed. In order to flash the latest roms you need either use HSPL 1.56.Olinex or USPL, which requires you to upgrade your spl to 1.54.0000. Refer to the guides i posted previously on the first page... it is not that difficult if you read the guide and follow the steps. If you have any further questions please post them. Remember, in order to upgrade to a custom ROM, many require SPL version 1.56+ to be installed.
Try this ROM upgrade from HTC website first - if you notice no improvements, upgrade your SPL version and then install a custom ROM.
ok i will, but this i'll realy do tomorow especially becouse it's my first time to upgrade rom and it's late for me so thank you and god night.
p.s. you should really come to croatia and see our beautiful coast (and learn some words) .
im trying several different roms and both of which have resulted in the splash logo and nothing else, it just hangs there. one of the roms was the kingkkklair droid eris2 g1 and i followed all of the directions it just didnt work. please help!
Could you share more info?
What phone do you have?
What radio/spl?
Are you sure you read and followed instructions?
are you sure you posted this in the right section?
turn the phone off, restart it by pressing back and power together and tell us the version information. most likely you have a 32a and you're trying to install roms for 32b or vice versa...
Not ROM Development related.
Moved to General.
Reziukas said:
Could you share more info?
What phone do you have?
What radio/spl?
Are you sure you read and followed instructions?
Click to expand...
Click to collapse
By viewing his recent posts, it appears that he is using a MyTouch 1.2 device.
ref: http://forum.xda-developers.com/showthread.php?p=5782312#post5782312
OP, you need to wipe before flashing any rom.
Please provide SPL, Radio versions as well as ext partition type (ext2, ext3, ext4) as well as rom details.
Bonus points if you can provide a logcat from ddms.bat and use pastebin.com to provide it to us.
My theory, the wrong ext paritition is being used. Some SenseUI roms require an ext3 partition.
Or...
A wipe of data, dalvik-cache, ext partition is likely needed.
no i have a 32b phone im sure, i got rid of that other phone and now have this one. my radio is 2.22.19.261 and my hboot is 1.33.0006. i followed the directions exactly and the roms are not working at all. here is the link to the rom please help me out. http://forum.xda-developers.com/showthread.php?t=644275&highlight=kingklick
I think i found out the problem. It said i need the latest radio, whatever that is. do you know what the latest radio for the mytouch is?
metaltorizo said:
I think i found out the problem. It said i need the latest radio, whatever that is. do you know what the latest radio for the mytouch is?
Click to expand...
Click to collapse
I'm pretty sure it's 2.22.23.02 but your current radio should work too (i think).
Do you have an ext partition?
If yes, what kind?
If yes, did you wipe the entire partition?
If no to either question, that's likely your problem.
Did you wipe your data?
If no that's likely your problem.
Do you know how to use logcat?
If yes then give us a logcat of what is going on while your phone tries to boot.
If no then use the command prompt and type 'adb shell logcat' wiith your phone connected to your pc.
Can you use other roms?
If yes then which ones have you tried?
If no then try different versions (preferably that don't have special requirements such as spl, ext partitions, swap, etc.
And check here if it's an issue with rooting your device.
http://forum.xda-developers.com/showthread.php?t=551920&highlight=click+root
I think that applies to your specifications.
Also try asking in that particular thread too. More than likely someone else in that thread has your same configuration and can give you more advice.
In all honesty, if you can flash other roms and are just busting your butt just to flash a Sense UI rom, you will be inevitably disappointed. They are fun at first but later on during the day you will probably become frustrated. MyTouch devices were not made to support the Sense UI interface. All devices that have Sense UI (aka Rosie, aka Hero) have at least twice the ram, faster cpu and more rom space. It'll be like installing Vista on a Pentium 2 computer with only 64mb of ram (just an example). Even if you could get it to work, it will eventually start running like dirt. It's not 100% stable or functional. The lack of bluetooth is an ongoing issue that most developers had pretty much given up on. So basically you are posting several threads and spending countless hours trying to get a rom flashed on your phone that will have no bluetooth and in a matter of hours will only provide slow constant and slow reloading with an occasional lockup/freeze/reboot. And I know that you're thinking 'But it looks really neat!' Really... stability and functionality will always win over eye candy. So go through the trouble, experiment with it if you wish but in a few days time you will be wanting to flash a more stable rom and all of this trouble that you are going through will be for nothing. Just my advice though.
Good luck.
Yes, i had a ext4 partition, and i did a full wipe before flashing. how do you delete the entire ext partition?
metaltorizo said:
Yes, i had a ext4 partition, and i did a full wipe before flashing. how do you delete the entire ext partition?
Click to expand...
Click to collapse
Wipe it from Recovery.
Depending on what rom and what recovery you are using you can just
cd /sd-ext (for Cyanogen 5.0.7+ roms)
cd /system/sd for most other roms (older roms)
then rm -r *