Hi All,
A couple of days ago, my HD was slow to respond so I did a soft reset. However, it got stuck on the 'smart mobility' startup message and wouldnt go any further.
As a test, I reflashed a radio via the SD card but this had no effect either. So I bit the bullet and reflashed another ROM from the SD card. This seemed to work and the new ROM loaded as normal but after a couple of soft resets the same thing happened (wouldnt go past 'smart mobility' on boot).
Today I flashed HardSPL again via SD but that didnt seem to work. Now my device goes straight into bootloader mode and says 'Upgrade ROM code error Please try again'.
Ive started to pull my hair out on this one, so any advice is much appreciated at this point!!
What next steps can I take?
remove the battery for 30 minutes or so then try flashing a stock ROM from SD, if you haven't yet. Also you can try flashing via RUU, just remove the SD from the slot.
If that doesn't help, perform a hard reset...
I managed to get it going by reflashing hardspl and putting on a new rom. However after a few reboots, the phone just keeps getting stuck at 'smart mobility'.
I cant keep doing hard resets as this happens everytime after soft restarting.
If the problem persists with a stock ROM and original SPL, take it back to you vendor for repair/replacement.
Ive managed to get it going with stock SPL and panosha rom.
Is it possible a corrupt memory card is causing this as now its removed, the issues no longer happen (or is it just coincidence)?
slud said:
Ive managed to get it going with stock SPL and panosha rom.
Is it possible a corrupt memory card is causing this as now its removed, the issues no longer happen (or is it just coincidence)?
Click to expand...
Click to collapse
Could be a coincidence. If you revert back to the ROM that kept failing, what happens now?
Thats actually the ROM ive been having issues with (sticking with it as I know something else is at fault here, not the ROM).
I havent tested very much yet, just using another phone for now until I get more time.
I hope there havent been threads for this kind of problem, I searched but couldnt find anything.
I recently flashed "Duttys_Leo_Sense_2.5_5.2.21889.5.0.87_1.66_Multi_Lang_V1.5_GER" onto my HD2.
after some rearranging of startmenu shortcuts I realized I couldnt add shortcuts to the sense home tab anymore, so I turned my HD2 off and on on again (first time after flash and yes I did hardreset after the flash)
To my horror the device would hang at the first splash screen where the 3 lines of red text are displayed.
After several attempts to boot it up with taking out the battery and putting it back in, my HD2 now suddenly did a hardreset when I was just turning it on the normal way.
This has ever since happened every time the HD2 is completely shut down.
I dont think its a bad rom since I havent heard anything bad about it and I dont know what else could be the problem.
Help would be much appreciated.
Thank you in advance
haveyou flashed a few roms? because roms are all slightly different lengths sometimes there will be files left over when a new rom is flashed, which can cause instability in the new flash.
go have a read of the mtty thread in rom development. basically a way to format the rom space before flashing.
Recently, my phone has become very unreliable and crashes, requiring a soft reset, every few hours.
And to make things much worse, the phone never wants to turn back on again. I have to take the battery out, replace it, and try to turn it on again, about 20 times before it actually vibrates and turns on.
Happens on several ROMs, including 1.66 with stock bootloader, so I'm pretty convinced its gone defective.
Also the phone has a habit of getting very warm when it crashes, and the battery doesn't last very long at all.
Had the phone since the start of December, so what are my options in sorting this out? Bought from mobiles.co.uk
Will Vodafone replace it, as I've heard they no longer stock the HD2, and offer Nexus One as a replacement. Is the nexus one worth having? I don't know much about Android.
sound like you have flashed several roms? you should give mtty a try. find the mtty sticky in the rom development section.
Sorry but what does MTTY actually do?
different roms are different lengths.when you flash a new rom it doesn't erase the old one just flashes over the top.this can leave data from the old rom "sticking out"past the end if the new rom, leading to instability.
mtty formats the rom memory ready for a new rom.
I always perform a hard reset after flashing, so will this still have affected me?
Hard reset doesn't wipe the rom chip. It just reloads the rom from scratch.
Mtty may not help you, yours may be a different issue, but instability and boot problems are symptoms of exactly what mtty prevents.
samsamuel said:
different roms are different lengths.when you flash a new rom it doesn't erase the old one just flashes over the top.this can leave data from the old rom "sticking out"past the end if the new rom, leading to instability.
mtty formats the rom memory ready for a new rom.
Click to expand...
Click to collapse
Thanks for that! Despite endless threads re: MTTY, this is the first simple explanation I've seen.
If you are running apps installed to mem card then try a boot without the card.
The heating up sound like a result of "hard work" by the phone and if you run apps from mem card the current draw is significantly increased.
If this is the prob then don't install anything to mem card that you don't have to. They have been known to cause exactly the symptoms that you report + more apps on card and greater access to them reduces the overall speed of operation which can cause freezes and resets!
Hey guys, I am kind of a noob but have successfully been hacking with my Touch for a while now...or so I thought. I flashed to the 3.37.78 radio a while back and have been keeping up with NSFAN's ROM's for over a year now with no problems....until a few months ago. My phone locked up and I had to soft-reset but to no avail. It got stuck on the startup screen and would not do anything so I did a hard reset and all was good. Then it happened again weeks later. Now it has been happening a lot more recently. I will be texting or on the internet with it and then all of a sudden it will lock up, I do a soft reset and it will hang up either on the startup screen or seem to boot up but then contacts will be missing and there will be no signal. Sometimes the today screen will show but I cannot do anything on it.....all of this requires a hard reset to fix. This happened after I flashed NSFAN's latest ROM so I flashed back to some of his older ROM's that I had no problem with in the past and still the same problem. It has been happening every week or 2 now to the point that I can't even bother setting up the phone the way I want because I know it will happen again. Can any of you guys tell me what the problem is? I really need to get this resolved because I am losing information everytime. Please help!!!
Im a GSM Phone user... and as a general rule, if things start to go wrong.... Flash the OEM rom. That would be the stock ROM. And then flash back to your "custom" rom... Ive had to do that with my phone(s) as well.... It basicly puts things back to 'ground zero'. BUT. Use the phone with the stock rom for a day and see if you still have the same problems... it may be a problem in the phone. In which case you may need to replace and/or send the phone back for replacement to your carrier.
Hope this helps....
Thanks for the reply.....What I ended up doing is reflashing my radio to the 3.42.50 version and then reflashing my ROM to NSFFAN's again. So far so good. I am really hard on my phones and the fact that I drop my phone on a regular basis can't help either....I just need it to last me a few more weeks until I get a new one. Thanks again...
Okay, I have honestly searched everywhere - Google, the xda forums, other forums and I still can't find something to help me with this strange problem I have.
PAST SITUATION
I installed TyphooN CyanogenMod ROM v3.5.8 around a month ago and I used it with no major problems (few android.acore repeated force closes that was dealt with by re-installation). During this time, I could power the phone off and power it on with no problems.
PRESENT SITUATION
This is where things go wrong. Recently, I decided to install TyphooN CyanogenMod ROMv3.8.5 (the latest one) by booting into MGDLR, doing a factory reset, wiping the system and dalvik caches and then installing the new 3.8.5 zip file. It installed properly and I booted into Android and was enjoying the new improvements and bug fixes. I had no problems until everything started force closing suddenly so I decided maybe a reset would fix it. AND THIS IS WHAT THE PROBLEM IS It boots to the Android Logo and stops there. I waited for 30 mins but it was still stuck at the Android logo and no matter how many times I took the battery out and put it back in and rebooted it, it was still stuck at the Android logo.
HOWEVER when I did a hard reset and wiped the system and dalvik caches and installed it again, it installed fine and booted into the system. When I tried to power it off and power it on again, the same problem happened where it was stuck on the android logo.
WHAT I TRIED TO FIX IT
1) A clean installtion, did a task 29 and installed everything again. Same problem happens.
2) I did a hard reset (wiped system and dalvik caches as well) AND THIS TIME I installed the previous version I was using with no problems (v3.5.8) and I had the same problem! Even with that version it still gets stuck on the Android logo screen.
I can use the ROM perfectly and my phone works fine, but if ever I need to reboot my phone for any issue it won't start up again and gets stuck on the android logo. I have to do a hard reset and re installation for it to work again but that means all my data, files and messages will be lost each time. So you can see the inconvenience I'm facing.
WHAT I THINK IS THE PROBLEM
1) I'm using a fairly old version of ClockworkMod Recovery. That is version 3.0.2.5 (150MB with 5MB Cache as per Typhoon's Requirements). Is this the problem?
2) I didn't remove the SIM and SD card during the entire flashing/reinstallation process. Could this be it?
Should I do a clean installation (task29) and install the previous ROM version I used with no problems and see if the problem still persists or if its only since I installed the new ROM version first?
Thanks for your help. And also I'm sorry I can't post this on the Typhoon ROM thread since I still don't have 10 posts.
did you get things sorted?:cyclops:
Well not yet. I am working on it. Does anyone have a download link to the latest version of ClockworkMod Recovery with 150MB and 5MB cache? I tried the HD2Toolkit and it just doesn't work for me, I plugged in my USB, it indicated USB Debugging was on and meh, it didn't click.
Anyways, I'm going to try task29ing the phone and installing MGDLR and the version of ClockWorkMod Recovery I have and installing the previous version of typhoonmod i used without any problems at all. Hopefully it'll just be a new version of the ROM issue.
I'll post my results here soon.
SpoonyVoid said:
WHAT I THINK IS THE PROBLEM
1) I'm using a fairly old version of ClockworkMod Recovery. That is version 3.0.2.5 (150MB with 5MB Cache as per Typhoon's Requirements). Is this the problem?
2) I didn't remove the SIM and SD card during the entire flashing/reinstallation process. Could this be it?
Thanks for your help. And also I'm sorry I can't post this on the Typhoon ROM thread since I still don't have 10 posts.
Click to expand...
Click to collapse
Sadly I can't give you any new suggestions, but I can certainly rule these two out as possibilities. I've never taken out the SIM when flashing, and you can't flash without the SD card. Recovery 3.0.2.5 is actually (from what I've heard) the most stable version. Have you tried other ROMs? Although again I highly doubt it's the issue, it's worth a shot.
You might want to consider the possibility of bad blocks, from what I've heard it can cause issues such as this (I don't actually have experience with them) so check for them (a simple forum search should give you a method as to how to do this).
SpoonyVoid said:
Well not yet. I am working on it. Does anyone
Anyways, I'm going to try task29ing the phone and installing MGDLR and the version of ClockWorkMod Recovery I have and installing the previous version of typhoonmod i used without any problems at all. Hopefully it'll just be a new version of the ROM issue.
Click to expand...
Click to collapse
Okay, So I tried this. The ROM installed fine but when I tried to power off and power on again it didn't work, the same problem happened where it got stuck on the Android logo.
WHAT I DID THEN
I decided enough's enough and that I can't really use my phone with Android if in some case something happens and I have to reboot it, I'll lose all my data and I'll have to reinstall it all over again.
So I switched to Windows 6.5 version 2.10.531.1 running Radio 2.15.50.14 and everything installed perfectly and I even rebooted the phone after installation and it worked. It came on with no problems. I'm guessing this is an issue that only affects Android then.
Nigeldg said:
Have you tried other ROMs? Although again I highly doubt it's the issue, it's worth a shot.
You might want to consider the possibility of bad blocks, from what I've heard it can cause issues such as this (I don't actually have experience with them) so check for them (a simple forum search should give you a method as to how to do this).
Click to expand...
Click to collapse
Thanks for the reply. I have not tried other ROMs out of fear of bricking my phone to be honest. Typhoon ROM is like one of the easiest for a newbie to install.
And yes, when I was searching around the forum, I did come across the issue of bad blocks. Sadly, I totally forgot to check whether it was affecting my NAND before installing WinMo 6.5. I'll try and look around the forums and google on whether I can check my bad block status on WinMo 6.5 somehow. If I can't, I think I'll use WinMo 6.5 for a while now, I can't really bear having to install and reinstall and install and reinstall, I feel like it'll make the bad block situation (If I do have it) worse.
I'm going to play around with WinMo 6.5 ROMs now. But if ever there is any development on my problem, I'll post on this thread and keep people updated.
I do have one question though, will upgrading to WinMo 7.5 be affected by the bad blocks? (If I have it)
Just saying, although it doesn't really matter, it's Windows Phone 7 (not WinMo 7). One's sh*t, and one's brilliant I don't have any actual experience with Windows Phone though, so I wouldn't know.
As for your concern about bricking your phone, there isn't any way you can do that outside of flashing an incorrect radio, and if you have an EU HD2 then AFAIK there isn't really ANY way of bricking it. Try other ROMs, they have exactly the same install process as TyphooN. In fact, starting fresh from WinMo might actually help. As long as you stick to this guide and use the correct partition size, you will never really go wrong. You can obviously also check for bad blocks after you install Android again (if you decide to do so, of course).
I have quite exciting news! well for me at least
I flashed Windows Phone 7.5 on my HD2 and was very impressed with it. It worked nicely and I really liked all the features. One thing I didn't like however was the battery drainage. The battery drained in 6 hours, and the next day it took 15 hours to drain and then again it took 6 hours to drain. I realized I couldn't use a phone daily with such uncertain battery capacity.
So I decided...*breathe*...to try out Android again, the NexusHD2 ROM by tytung in particular and hope and pray I don't have bad blocks and the rebooting problem doesn't occur.
So I uninstalled WP7, repartitioned my SD card, installed Windows 6.5 STOCK and the right radio and MAGDLR, Clockwork Recovery and flashed NexusHD2 and then did the Bad Blocks thingamabob I was supposed to do and accessed the recovery.log but I couldn't find any mention of "bad blocks" or anything related to "bad". But I dunno...
Anyways the good news is NexusHD2 Gingerbread 3.5.7 works really well and I don't have the rebooting problem anymore. Just a few android.process.media force close issues that I'm trying to figure out but the main problem is gone!
SpoonyVoid said:
I have quite exciting news! well for me at least
I flashed Windows Phone 7.5 on my HD2 and was very impressed with it. It worked nicely and I really liked all the features. One thing I didn't like however was the battery drainage. The battery drained in 6 hours, and the next day it took 15 hours to drain and then again it took 6 hours to drain. I realized I couldn't use a phone daily with such uncertain battery capacity.
So I decided...*breathe*...to try out Android again, the NexusHD2 ROM by tytung in particular and hope and pray I don't have bad blocks and the rebooting problem doesn't occur.
So I uninstalled WP7, repartitioned my SD card, installed Windows 6.5 STOCK and the right radio and MAGDLR, Clockwork Recovery and flashed NexusHD2 and then did the Bad Blocks thingamabob I was supposed to do and accessed the recovery.log but I couldn't find any mention of "bad blocks" or anything related to "bad". But I dunno...
Anyways the good news is NexusHD2 Gingerbread 3.5.7 works really well and I don't have the rebooting problem anymore. Just a few android.process.media force close issues that I'm trying to figure out but the main problem is gone!
Click to expand...
Click to collapse
Good to hear that, and it's also good that you don't have any bad blocks. Even then, you shouldn't have the FC problems, so this is quite confusing.
Nigeldg said:
Good to hear that, and it's also good that you don't have any bad blocks. Even then, you shouldn't have the FC problems, so this is quite confusing.
Click to expand...
Click to collapse
Funny thing really, I did some testing and the process.android.media force closes every time I try to open the android market ONLY AFTER I have powered off and powered on the device AFTER flashing the ROM. If I don't power off the device after flashing the ROM, I don't have that problem at all and I can access the android market with no problems.
Just to be on the safe side however and since I've decided to keep on using NexusHD2 daily, I've backed up all the system files (after a clean re-installation) with Titanium backup so if ever I have to reboot the device, I can hopefully prevent the force close messages from appearing. I've also updated the android market to the latest version just for kicks.
When trying to fix the force close problems earlier, I went to the MAGDLR bootloader screen, proceeded to the CWM menu, tapped into Advanced and fixed permissions. When I booted into Android, the force close messages stopped appearing, however the android market wouldn't open. It would appear briefly and then close automatically without displaying any sort of error message. Strange.
I seriously think I haven't done the bad blocks check properly. I'm sure I have some since this phone is around two and half years old now and was passed on to me by my brother after he experimented around with it as well. I followed AngelDeath's post in the Bad Block Awareness thread but couldn't find any mention of bad blocks and found only a few mentions of the word "block" itself on the recover.log. I didn't find anything similar to his extract of his log on the first post of that thread as well. I'm doing something wrong.
SpoonyVoid said:
Funny thing really, I did some testing and the process.android.media force closes every time I try to open the android market ONLY AFTER I have powered off and powered on the device AFTER flashing the ROM. If I don't power off the device after flashing the ROM, I don't have that problem at all and I can access the android market with no problems.
Just to be on the safe side however and since I've decided to keep on using NexusHD2 daily, I've backed up all the system files (after a clean re-installation) with Titanium backup so if ever I have to reboot the device, I can hopefully prevent the force close messages from appearing. I've also updated the android market to the latest version just for kicks.
When trying to fix the force close problems earlier, I went to the MAGDLR bootloader screen, proceeded to the CWM menu, tapped into Advanced and fixed permissions. When I booted into Android, the force close messages stopped appearing, however the android market wouldn't open. It would appear briefly and then close automatically without displaying any sort of error message. Strange.
I seriously think I haven't done the bad blocks check properly. I'm sure I have some since this phone is around two and half years old now and was passed on to me by my brother after he experimented around with it as well. I followed AngelDeath's post in the Bad Block Awareness thread but couldn't find any mention of bad blocks and found only a few mentions of the word "block" itself on the recover.log. I didn't find anything similar to his extract of his log on the first post of that thread as well. I'm doing something wrong.
Click to expand...
Click to collapse
Ah that may be the problem then. You shouldn't really be touching anything immediately after flashing. Let the ROM settle for 5 minutes, complete the set up and then reboot a few times. As for why the Android Market isn't opening, once again am completely stumped, sorry. Try clearing the app data and cache then opening it again. I don't know whether or not this would work, but try to install a new play store.apk (e.g. the updated one in the HD2 Android Themes and Apps section) and try again. On no ROMs have I ever had this issue.
As for your being unsure about the bad blocks, I would be inclined to agree with you there, as it seems unlikely that after so long there would still be no bad blocks, especially if you and your brother were often flashing things.
dmesg command from a terminal emulator might give some info on the presence of bad blocks, if you haven't already tried it.
Sent from my Nexus One using xda premium
A logcat would be really useful when:
-ever your ROM gets stuck after a reboot.
- You face any random force close.
I used to have issues with the market closing without any error, it turned out to be unsupported where I was. In the new google play, it'd open, but nothing shows up. Fixed it by using DroidVPN.
Was the market working prior to this problem?
Also, have you checked the battery pins? (sometimes, they cause unpredictable problems)
You could also give cLK a shot, and see if the problem persists.