Ok so as explained in my other thread I lost some programs i wanted after I ran the super cleaner, so I ran a restore with Rom Manager and I started getting an error every few seconds. So I tried to do a restore with odin. I restored the system and kernel. Phone was runing fine, but every time I shut if off when it turns on it acts like it a fresh start and I have to do the wizard.
So next I tried a factory reset, its still doing the same thing but now I lost my contacts.
Any help would be very appreciated.
Thank you in advance.
Sorry for the double post, but I got it fixed.
Thanks
Related
first things first: the hd2 is my very first windows mobile device. i've already read the wiki and searched the forum/the internet for help, but i didn't find a solution for my problem. i'm also not a newcomer when it comes to flashing (i've gained some experience from my psp/wii/nokia n82/creative zen).
so i got my htc hd2 a few days ago and one of the first things i tried was flashing a rom (i didn't like the t-mobile branding).
i had absolutely no problems installing hspl (this forum was very informative) and flashing the artemis rom (i strictly followed the instructions), which i found in the rom developement sub forum. since everything seemed to work fine, i started adding my contacts and some applications, still no problems.
but after a while one of the apps seemed to have crashed and the phone became unresponsive.
i removed the battery and turned my phone back on, but it was stuck in the boot screen (the very first screen on which it says "r g d" in red at the bottom). since i didn't know what to do, i simply flashed the artemis rom another time and so the story repeats: at first everything worked fine and after a while the phone got stuck again.
after 4 tries i decided to switch to the shock star r9 rom (also found on xda), which also seemed to work fine at first, but it didn't take long for the phone to freeze again. i took out the battery again and turned the phone back on. this time (to my surprise) it didn't get stuck on bootup, but instead it (automatically) performed a hard reset. the phone now does a hardreset everytime i turn it back on, which makes it pretty much unusable...
since i'm getting REALLY tired of adding my email accounts/favorites/application shortcuts (by now i'm just installing them on the sd card, so i don't have to reinstall them)/facebook associations for my contacts/etc and i thought i'd better ask for help.
does anyone know what causes this issue and/or how i can solve this problem? help would be appreciated!
and since i'm here, what should i use to backup my phone (once it's running perfectly)? i already tried pim backup (sadly it doesn't create a backup of everything) and spb backup (freezes on registry recovery). would it be possible to create a rom that contains ALL of my information (settings/contacts/favorites/applications/registry tweaks/...)?
tl;dr:
my hd2 automatically performs a hardreset on bootup, how do i fix it?
please ignore any grammar errors, i'm tired and not a native english speaker
I have the same problem exactly regarding self-hard-reset. I still did not find any reasonable cause for this problem which is starting really to push on my nerves
This sounds to me like a corrupt file system, which can happen after ROM flashes. I would try this:
http://forum.xda-developers.com/showthread.php?t=644781
@Moandal: thanks for the answer. i just flashed the shock star rom again and the phone boots up normally again. but i really doubt that it will stay like this, unless i know what caused the problem. next time it happens, i'll try the program from your link.
but if i'm not mistaken, that program also hardresets the phone (correct me, if i'm wrong), so i could just flash a rom instead and that's what i'm trying to prevent (as i said, i don't want to have to enter my personal stuff again and again and again...).
what exactly could cause a corrupt file system? could it be a problem with the rom(s) or am i just doing something completely wrong?
A "simple" custom ROM flash only overwrites the ROM's contents without prior erasing, which on the HD2 has been found to sometimes cause trouble like the continuous hard resets you've suffered.
The solution is a full erase of the ROM before flashing the new ROM, which this mtty command does. So, you obviously can't do it without hard resetting/reflashing.
@kilrah: ok, that made things much clearer. i'm going to use the program posted above and flash the rom again, i hope that will fix future issues.
thanks for the fast help, guys
I had the same issues, at first I thought it was the artiums rom but having done MTTY walkthrough I'm 1 week into the Miri rom without much issues (apart from the odd program crash)
since it started pretty much straight away on the first rom, id be a little concerned that it might be an issue with the phone.
if it continues after you mtty/task 29 then id flash back to stock, including spl, and monitor that for a few days.
Code:
@samsamuel: since my last post the phone crashed only once (i was using opera 9.7 when it became unresponsive again), but this time it didn't perform a hard reset!
the main issue seems to be solved and that's good enough, for the time being.
if the problem occurs again, i'll follow your advice.
opera 9.7 - have you moved the cache to the memory card? I've had a lot of freezes the last few days with opera 9 7, turns out it was cos the cache was on the sd card (default 2 gig that came with it).
moved the cache to the phone yesterday, not a crash in 30 hours.
no, but i was actually going to. won't do it now, obviously
please help cause it went crash and hardreset by itself over again..... how can I fix this??
Hey,
Im pretty new to rooting and everything was going well I had root and just about everything the way i wanted, but then i looked on the rom manager and saw that they had updated roms and kernels, I downloaded them directly from rom manager and did a full back up and data wipe before installing... everything was going fine I rebooted and had a tun of force closes... so I went in and restored data to my last build and that went through and I finally got all the force closes to stop by doing another data wipe, but when i tried to go to download and go back to my last build I noticed that my phone has no storage cap at all. I have done everything that i could think of to try to fix this issue to no avail.
Any help would be awesome
Thanks
Spitfil2e8
Search for the thread about 0.00 internal storage, should help you fix your problem.
Hey, adrynalyne posted a thread about how to fix this problem. Too bad he no longer helps here any longer.
I finally decided to attempt to load a custom ROM on my Samsung Fascinate after a couple of months of owning it. Before I started anything, I backed up my current ROM twice using ROM Manager, then used ROM Manager to do the new ROM download and install.
Things didn't go well. At all.
Once the new ROM was installed, my phone restarted, got back to the puzzle screen (thinking I was in business!) and as soon as I unlocked the screen the force closes just kept on coming. One right after another. Pretty much anything and everything force closes, so much so that it is the only thing you can do on the phone now. I have tried force closing things for as much as 5 minutes thinking I might get to the end of it, but no luck.
So now I have 2 backups on my SD card. I went into my Android System Recovery (+, - volume and power button), selected apply sdcard:update.zip which gets me to ClockworkMod Recovery v. 2.5.1.0. From there I go into Backup and Restore, select Restore and then my restore file. After some time the restore process is complete and the phone asks to reboot. I do the reboot and low and behold nothing seems to have changed in the phone. I still have the custom ROM with all of the force closes.
Am I missing something with this CWM restore process? I have read what seems like dozens of forum entries and nobody else seems to have problems with the restoration.It seems like it is pretty straight forward but I am not having any luck with it at all.
Any help is appreciated!
Try This and see if it helps:
http://forum.androidcentral.com/fascinate-roms-hacks/38029-how-escape-force-close-loop-hell.html
Perfect! I am back in business thanks to you. Sure appreciate your help!
Did you wipe first?
Hi all,
I'm hoping someone may be able to help me. Here's the situation:
A few weeks ago, I updated and rooted my SGS4 to 4.4.2 using Odin. Worked alright, but kept getting random restarts. Did a factory reset, and all was good.
A few days ago, PlayStore had an update for SuperSU, so I applied it. The random restarts returned, so I considered doing a factory reset, but found that Titanium Backup wasn't allowing me to do any new backups because I had insufficient space. I didn't really - I had plenty of space. A little googling lead me to here: http://forum.xda-developers.com/showthread.php?t=2675778
I followed the instructions, rebooted my phone, and was bombarded with [app] has stopped working right away. Thinking this was no good, and I had somehow messed something important up, I did a factory reset anyway with the hopes of just restoring back to my backups from a few weeks ago.
Things got even worse - I'm now stuck on the Samsung welcome screen, where it wants me to put in my wifi password, but Myscript Resource Manager keeps failing, making the keyboard disappear. I now have no way to get back into my phone.
The TL;DR version:
I factory reset my phone, but can't get past the 'Enter Wifi Password' part of setting it up becuase Myscript Resource Manager keeps failiing.
Things I've tried:
* Wiping Cache data
* Factory Resets (again)
* Reflashing my phone with the 4.4.2 update that worked for me a few weeks ago
Does anyone have any other ideas?
The only way was to reflash from Odin, fresh firmware. Download different version of your firmware, other than the one you stated. And reflash back with Odin, make sure your steps using Odin is correct.
Thanks for the reply. I finally got it working after my third time flashing it and formatting the cache a few times. Scary stuff!
Alas, the sporadic reboot still continues, so I'll have to work out how to fix that problem again now.
Thanks again.
Simpler fix from at&t device support center
c0dewana said:
Hi all,
I'm hoping someone may be able to help me. Here's the situation:
A few weeks ago, I updated and rooted my SGS4 to 4.4.2 using Odin. Worked alright, but kept getting random restarts. Did a factory reset, and all was good.
A few days ago, PlayStore had an update for SuperSU, so I applied it. The random restarts returned, so I considered doing a factory reset, but found that Titanium Backup wasn't allowing me to do any new backups because I had insufficient space. I didn't really - I had plenty of space. A little googling lead me to here: http://forum.xda-developers.com/showthread.php?t=2675778
I followed the instructions, rebooted my phone, and was bombarded with [app] has stopped working right away. Thinking this was no good, and I had somehow messed something important up, I did a factory reset anyway with the hopes of just restoring back to my backups from a few weeks ago.
Things got even worse - I'm now stuck on the Samsung welcome screen, where it wants me to put in my wifi password, but Myscript Resource Manager keeps failing, making the keyboard disappear. I now have no way to get back into my phone.
The TL;DR version:
I factory reset my phone, but can't get past the 'Enter Wifi Password' part of setting it up becuase Myscript Resource Manager keeps failiing.
Things I've tried:
* Wiping Cache data
* Factory Resets (again)
* Reflashing my phone with the 4.4.2 update that worked for me a few weeks ago
Does anyone have any other ideas?
Click to expand...
Click to collapse
I just had the same problem, spontaneously, from an unidentified source. Went to my carrier's, AT&T, local Device Support Center on a Sunday at noon, and one of the techs fixed the problem in under 3 minutes, impressively simply.
You will have to keep clicking OK when the error message repeatedly appears to continue with this process. That is normal.
Go to Settings > Application Manager > (scroll right to: ) ALL > (scroll down to: ) My Script Resource Manager (which should not be running) > Turn Off
Problem solved without Factory Reset. She impressed me and saved me a lot of time.
Hi everybody.
Dis morning I woke up and I realized that my phone was gone. I used AOSP Extendend ROM when it happens. At first, the rom completely froze. I thought it was a bug, so I rebooted the phone, but after did dis, the phone kept on rebooting and froze on first screen and I couldn't do anything. Touch didn't respond, nothing worked.
So I tried to go on recovety, but nothing.
At the end, I gave up about take back my data and try to install the stock ROM through MiFlash. I tried different stock ROM, but at the first they works, but during the installation guide they froze again and reboot. I can't even finish the setup!
So I tried again, unlock bootloader, flash TWRP, but still there:
- only TWRP v2.0 works, other versions won't start
- even with TWRP v2.0, after did wipe everything and format, when I tried to install a custom ROM, even TWRP froze and reboot the phone
- TWRP is pretty useless, it keeps on froze and when I boot recovery again, TWRP is locked and I have to format everything again, but still don't work.
Someone could tell me what happened to my phone? Any suggestions about what I could to to install something on my phone?
Pls help me, I am completely lost and disperate
You may in deed have a serious hardware problem.
What you can do without opening it up is to try charging it overnight, and see how it works tomorrow.
You have tried everything else you can think of, I assume, like wiping & formatting everything you can in TWRP, and possibly "repairing file system" if there is such an option.
The next thing I would try is opening it up and disconnecting the battery for a while, then connecting it again to see what happens.
cobben said:
You may in deed have a serious hardware problem.
What you can do without opening it up is to try charging it overnight, and see how it works tomorrow.
You have tried everything else you can think of, I assume, like wiping & formatting everything you can in TWRP, and possibly "repairing file system" if there is such an option.
The next thing I would try is opening it up and disconnecting the battery for a while, then connecting it again to see what happens.
Click to expand...
Click to collapse
Ok, I will listen your tip. Yeah, I have tried everything but nothing. Technically, I bought this phone last december, so it's still covered by warranty, but I have to send it to China, I would avoid that if I can.
I hoped there would be something that I didn't but...nothing.
Thanks anyway dude