Hi all,
I have HTC wildfire for almost a couple of years, recently it started to randomly restart, about 5-8 times a day (the phone is off during the night).
At the time it begun I had OLDWildPuzzleROM_2.2 Froyo v8.0.11 ROM, with HBoot 0.8.
Before the restarts happened I rooted my phone using unrEVOked-3-2-Windoze (it stayed S-Off though).
I don't think the restarts happened right after the root so I'm not sure that is the cause
I few days ago I flashed it with "RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.2 4H_3.35.20.10_release_160191_signed" which changed my HBoot from 0.8 to 1.01.0001. I found the ROM here and followed the instructions.
I had to make a goldcard (I formatted the SD card using the phone and not using the PC).
My phone continues to randomly restart.
We don't have HTC representative in my country, only non official labs that deal with repair, so I can't go to the company for repair. talking to the lab guy he says it is probably a software issue and not a hardware issue, though I don't understand how it is possible since I flashed a completely new ROM. Oh, and the lab guy says he will charge me whether the repair works of fails....
Do you have any suggestions?
Many thanks
PS
I read about boot loop, I'm not sure what boot loop is, but when my phone restarts it shows the HTC logo as it does during power on or full restart.
bootlooping is random restarting or continuous looping of boot.
reasons could be many......
overclocking your cpu to high.
low on memory (too many apps installed / running).
v6 / supercarger / juwwes ram scripts etc etc.
MokeeOs
So that doesn't apply to me
I don't overclock
I have restarts even without installing any apps
I don't know what v6 / supercarger / juwwes ram scripts mean
any ideas of what should I do?
slymobi said:
bootlooping is random restarting or continuous looping of boot.
reasons could be many......
overclocking your cpu to high.
low on memory (too many apps installed / running).
v6 / supercarger / juwwes ram scripts etc etc.
MokeeOs
Click to expand...
Click to collapse
Clonimus said:
So that doesn't apply to me
I don't overclock
I have restarts even without installing any apps
I don't know what v6 / supercarger / juwwes ram scripts mean
any ideas of what should I do?
Click to expand...
Click to collapse
like slymobi already mentioned it could have several reasons - but we've already excluded a few...
Another idea is to start your phone without the sdcard and look if the reboots continue
Important: flashing a different ROM to solve the issue almost doesn't help if you haven't done a complete wipe/factory reset - it has also been reported (not confirmed, though) that Clockworkmod recovery randomly fails with wiping - so it might also help to repeat the procedure.
Probably slymobi will point to a thread where he explains a complete wipe... (you could search in his threads - I'm busy and it's really hot here atm )
I mean: to be sure I always try to format + wipe + factory reset (sound redundant but feels safer...)
eventcom said:
like slymobi already mentioned it could have several reasons - but we've already excluded a few...
Another idea is to start your phone without the sdcard and look if the reboots continue
Important: flashing a different ROM to solve the issue almost doesn't help if you haven't done a complete wipe/factory reset - it has also been reported (not confirmed, though) that Clockworkmod recovery randomly fails with wiping - so it might also help to repeat the procedure.
Probably slymobi will point to a thread where he explains a complete wipe... (you could search in his threads - I'm busy and it's really hot here atm )
I mean: to be sure I always try to format + wipe + factory reset (sound redundant but feels safer...)
Click to expand...
Click to collapse
thank you,
I will try to find a tutorial that illustrates how to do a format and complete wipe, I will appreciate it if someone will have the time to point one, but will look for it myself too.
so I understand you all think it is not a hardware issue.
BTW I did a factory reset on my original ROM before I flashed a new one.
Clonimus said:
thank you,
I will try to find a tutorial that illustrates how to do a format and complete wipe, I will appreciate it if someone will have the time to point one, but will look for it myself too.
so I understand you all think it is not a hardware issue.
BTW I did a factory reset on my original ROM before I flashed a new one.
Click to expand...
Click to collapse
Sorry, couldn't find how to do a system format. can you help?
Does "wipe" as you call it the same as factory reset? if so that I did but no format.
In the recovery go under Mounts and Storage and select Format System.
Technically factory reset is a wipe, it wipes cache, data and sd-ext
Clonimus said:
thank you,
I will try to find a tutorial that illustrates how to do a format and complete wipe, I will appreciate it if someone will have the time to point one, but will look for it myself too.
so I understand you all think it is not a hardware issue.
BTW I did a factory reset on my original ROM before I flashed a new one.
Click to expand...
Click to collapse
There's another thing you might want to check: a lot of people had reboots when they (or the phone) switched on 3G. So do you have reboots, too, with data/3G off?
Furthermore I also know of at least one case where the reboots were caused by a damaged battery - so it might be a hardware issue as well - but in most cases I know of it hasn't been
Re. how to do a clean wipe/format: in this thread I describe my method (sometimes I'll do it different, though) and slymobi describes how he does it (your choice): http://forum.xda-developers.com/showthread.php?t=1833966
Lesicnik1 said:
In the recovery go under Mounts and Storage and select Format System.
Technically factory reset is a wipe, it wipes cache, data and sd-ext
Click to expand...
Click to collapse
yes but as you probably know, sometimes that might just not be clean enough...
reboot into recovery,power off then volume down button and power button at same time,in this menu,using trackball to select,
wipe data / restore factory settings,
wipe cache,
go into advanced and wipe dalvik cache.
press power button to go back.
go into mounts and storage,
format data,
format cache,
format system,
format sdext,
DONT FORMAT SDCARD
you have now wiped your phone clean.
press power button to go back,
install rom from sdcard,navigate to where your rom is on your sdcard and select / confirm,
let it install..........
don't reboot,if gapps are needed?
flash correct gapps in same way as you just flashed rom........
reboot.
MokeeOs
eventcom said:
There's another thing you might want to check: a lot of people had reboots when they (or the phone) switched on 3G. So do you have reboots, too, with data/3G off?
Furthermore I also know of at least one case where the reboots were caused by a damaged battery - so it might be a hardware issue as well - but in most cases I know of it hasn't been
Re. how to do a clean wipe/format: in this thread I describe my method (sometimes I'll do it different, though) and slymobi describes how he does it (your choice): http://forum.xda-developers.com/showthread.php?t=1833966
yes but as you probably know, sometimes that might just not be clean enough...
Click to expand...
Click to collapse
Thank you eventcom,
Actually I didn't think about it but the restarts started a bit after I started using the 3G internet.
If so will the format-wipe-flash procedure will help? this phone suppose to be 3G capable, no?
Many thanks
If the reboots happen because of you enabling 3G I think re-flashing the radio will fix that. (Not so sure on that, someone please complete me)
slymobi said:
reboot into recovery,power off then volume down button and power button at same time,in this menu,using trackball to select,
wipe data / restore factory settings,
wipe cache,
go into advanced and wipe dalvik cache.
press power button to go back.
go into mounts and storage,
format data,
format cache,
format system,
format sdext,
DONT FORMAT SDCARD
you have now wiped your phone clean.
press power button to go back,
install rom from sdcard,navigate to where your rom is on your sdcard and select / confirm,
let it install..........
don't reboot,
flash gapps in same way as you just flashed rom........
reboot.
MokeeOs
Click to expand...
Click to collapse
Thank you slymobi,
but as I wrote above, when I did the RUU thingy I had to do the goldcard procedure and so I formatted my SD card.
Does it have a ROM image after I did the RUU flash?
what is "flash gapps", is it one of the option in the menu? sorry, I'm new to all of this
thank you for your patience and valuable help
gapps is the google apps package.needed for most non sense roms I think
its fine that you have formatted the sdcard at that stage. I meant whenever your performing recovery wipes to be careful not to format sdcard as it does exactly what it says and you will delete all contents of sdcard.
MokeeOs
Lesicnik1 said:
If the reboots happen because of you enabling 3G I think re-flashing the radio will fix that. (Not so sure on that, someone please complete me)
Click to expand...
Click to collapse
can you flash just the radio?
Lesicnik1 said:
If the reboots happen because of you enabling 3G I think re-flashing the radio will fix that. (Not so sure on that, someone please complete me)
Click to expand...
Click to collapse
forgot about this.
yep I think you're correct,if it is the 3g? but what triggered it?
MokeeOs
---------- Post added at 01:36 PM ---------- Previous post was at 01:32 PM ----------
Clonimus said:
can you flash just the radio?
Click to expand...
Click to collapse
lol I knew this was coming next.
yes you can. I'm busy now so hopefully someone will guide you.
if not search forum on how to flash radio etc etc.
MokeeOs
Yes you can.
First download the file I attached and this file: http://www.mediafire.com/?lkhsl6hojm7vplv
Put both on the SD card
Flash the first one in the recovery, this will give you a temporary 2.5.X recovery, that goes away on reboot.
Within that recovery flash the second file I put up (the radio file itself)
Lesicnik1 said:
Yes you can.
First download the file I attached and this file: http://www.mediafire.com/?lkhsl6hojm7vplv
Put both on the SD card
Flash the first one in the recovery, this will give you a temporary 2.5.X recovery, that goes away on reboot.
Within that recoveryond flash the sec file I put up (the radio file itself)
Click to expand...
Click to collapse
I feel so stupid asking this, but how do I 'flash the in the recovery'? I don't know the basics, also the 'Within that recovery and flash the sec file' is a bit esoteric for me
I feel stupid since I am an electronic engineer and working with J-Tag and embedded systems
Thank a lot
Flash them both, just like you flash a ROM
Once you flash the first file a new recovery will pop up, within that one, flash the radio file
Lesicnik1 said:
Flash them both, just like you flash a ROM
Once you flash the first file a new recovery will pop up, within that one, flash the radio file
Click to expand...
Click to collapse
That's my point exactly, I never flashed a ROM on a cell phone
I used the RUU exe, it was as simple as running a windows application.
Do I have to root the device? and mimic a ROM update procedure to do that?
Or wait, is it by using the bootloader menu that comes up when you press down+power on?
lesicnik I would have thought you of all people would give better instructions. Especially after yesterdays pm. lol.
MokeeOs
Related
all,
don't really know how I got here, but I don't like it at all ...
I can get into recovery mode as always (clockwork 2.5.0.1) and flash any new ROM I pick up here. but whenever I reboot, my phone is stuck at the white HTC boot screen (I waited up to 2 hours just to be sure it's not my impatience).
I wiped everything (factory reset, cache, dalvik) at least 5 times each. I flashed the latest OD, DeFrost, and Neo ROMs a few times. but whenever I try to reboot, my phone stays forever on that initial white screen with HTC in the middle.
a Nandroid restore of a previously working configuration ends up at exactly the same place!
getting a later version of clockwork seems rasonable? but how do I update that w/o booting up to run RomManager (asked the noob )?
any ideas or suggestions how to fix this?
AtDhVaAnNkCsE
PS. sorry when this has been answered before. but all "stuck at bootscreen" threads I found had the same resolution: wipe, Wipe and WIPE and flash again - I did that plenty of times now...
format sd card and reinsert. be sure to backup important data.
btw wipe-flash-rewipe. post results
after that, try using a sense-based rom, like Pays2.0 or pinky's rom.
Some users find problems with non-sense roms. If you can get a sense rom to work at least you know that something works!
imo, Paysftw!
mariosraptor said:
format sd card and reinsert. be sure to backup important data.
btw wipe-flash-rewipe. post results
Click to expand...
Click to collapse
FUNTASTIC! thanks a lot!!
the test with sense based roms will have to wait till "next time" - formatting the SD card fixed my problem.
my windows PC could only handle the FAT32 partition - but I could still erase the rest and that's good enough for now
thanks again!
glad the community helps. personally i would suggest-if you want a nonsense rom- that you should go for the stable version of opendesire. it is 4.0.15.
regards
Marios
dampf said:
FUNTASTIC! thanks a lot!!
the test with sense based roms will have to wait till "next time" - formatting the SD card fixed my problem.
my windows PC could only handle the FAT32 partition - but I could still erase the rest and that's good enough for now
thanks again!
Click to expand...
Click to collapse
Most of this info may be extraneous, but I'll throw it in here just in case.
A few days ago, I decided to root my Evo 4G from the stock, 2.2 OS (HTC Sense?) using the Unrevoked website (using a PC running XP). It worked fine and got me rooted. Trouble began to arise when I attempted to install new ROMs such as CM-6 and Salvage. I decided to fork out a few bucks and pay for the ROM Manager Pro app, thinking that it would save me considerable hassle. After downloading the most recent CyanogenMod 7.0.0-RC2 through the app, I selected the "Install Gapps as well" option but did NOT check "Wipe Data and Cache" before letting the app do its work of installing and flashing and whatever for me. Upon completion of the installation, my phone then automatically rebooted normally, but became stuck on the boot image of the android on the skateboard with the spinning arrow. I let that sit for about 6 hours (I went to bed) thinking it was just first-time setup before I battery-pulled and booted into recovery, restored my original settings, and started over. This time I did everything the same except remembered to check "Wipe Data and Cache," as an online tutorial told me I ought to when switching from stock to another ROM, and it installed and booted correctly. I ran CM-7 for a day before deciding to try out a different ROM, downloading and installing it through the same interface, ROM Manager Pro. Everything went well until it got stuck, again, at the boot image. After about 30 min I battery-pulled and tried to restore back to CM-7, only to be greeted by another endless boot image. I was able to restore back to my original backup, but am now back to square one. What the heck am I doing wrong?
EDIT: That original backup I mentioned was made immediately after rooting the phone in preparation to install CM-7.
Sorry my technical knowledge is grossly lacking, I just got into this game. Patience and any help is GREATLY appreciated.
When switching from one rom to another, it is always important to remember to wipe data and cache. There are a few rare cases that it is not necessary to do this, but I really recommend that if you are just starting out, wipe them both for good measure until you learn enough that you can tell when you can get away with not wiping. Also, I know that one common problem that people experience with Rom Manager is that Unrevoked contains the Amon_RA recovery image, and Rom Manager is designed to with with the Clockwordmod recovery. In Rom Manager, you should be able to see which one you are currently using, and you should also be able to use Rom Manager to download and flash the latest Clockworkmod recovery. I too use Rom Manager as a convenient way of making sure that my rom is up to date, and to download roms, but I recommend that when you want to change roms, you do it by booting into recovery mode, and performing the wipe and install manually, as I have found that this method will help prevent errors like boot loops. I hope this helps!
P.S. Feel free to PM me if you ever need any help.
Sent from my DESTROYED Evo using XDA Premium app
So, for example, if I wanted to restore back to my CM-7 backup, would I want to boot into recovery and just restore to the backup or re-flash the ROM, then boot into recovery and try to restore it? I'm still getting the endless boot image.
Oh, and I am running clockworkmod, as per the instructions for ROM Manager.
Thanks for the quick reply!
Move CM7-RC2.zip and the gapps.zip (or whatever its name; ex: filename.zip) to the root of your SD card by plugging it into your computer via USB and mounting it as a drive. Go ahead and exit all that.
Turn off your phone.
Hold volume down + power.
Go to Recovery.
Wipe the following: data/factory reset, cache, (in Advanced, accessed from same menu) wipe dalvik.
Go back.
Install .zip from SD.
Choose your .zip(s) [CM7, Gapps] from your card, flash, and presto!
I'm not too experienced with ROM Manager as I do not use it whatsoever, but I know the above stated method should work perfectly.
Furthermore,
I'm not sure if a format_all.zip should be used here with CM7. If someone who knows would like to chime in about this, that'd be great.
totalanonymity said:
Move CM7-RC2.zip (or whatever it's name; ex: filename.zip) to the root of your SD card by plugging it into your computer via USB and mounting it as a drive. Go ahead and exit all that.
Turn off your phone.
Hold volume down + power.
Go to Recovery.
Wipe the following: data/factory reset, cache, (in Advanced, accessed from same menu) wipe dalvik.
Go back.
Install .zip from SD.
Choose your .zip from your card, flash, and presto!
I'm not too experienced with ROM Manager as I do not use it whatsoever, but I know the above stated method should work perfectly.
Furthermore,
I'm not sure if a format_all.zip should be used here with CM7. If someone who knows would like to chime in about this, that'd be great.
Click to expand...
Click to collapse
This is the way I would flash any roms that you want from here on out.
I have used CM7 and have not had to use the format.zip from calk, so I don't think it is absolutely necessary, but it probably wouldn't hurt.
Sent from my DESTROYED Evo using XDA Premium app
I recommend flashing the format all zip whenever switching ROMs. It completely formats the various partitions and leaves a blank slate for the new ROM to be installed. I also recommend using ROM Manager to flash Amon_Ra recovery and do everything manually instead of using ROM Manager. People seem to have a lot less problems with Amon, and I have never had any issues flashing ROMs or kernels or anything with it.
You won't be able to restore a Clockwork backup with it but it never hurts to just flash a new ROM and restore your Titanium backups, assuming that you made them.
Wow, thanks all for the fast replies!
Ok, I now have Destroyer installed and working (finally!), but I am experiencing the apparently common black-on-black text box problem. I downloaded the .zip to be flashed to fix this, but am not sure how to proceed. Do I just do the exact same thing as flashing a new ROM entirely or is there something special I need to do to let the phone know that it is an update?
RossGoldenstein said:
Wow, thanks all for the fast replies!
Ok, I now have Destroyer installed and working (finally!), but I am experiencing the apparently common black-on-black text box problem. I downloaded the .zip to be flashed to fix this, but am not sure how to proceed. Do I just do the exact same thing as flashing a new ROM entirely or is there something special I need to do to let the phone know that it is an update?
Click to expand...
Click to collapse
Not sure with ROM Manager but you can flash that from recovery the same way you flash a ROM. I'm sure there is an option in ROM Manager to flash it, I just couldn't tell you where. Do not wipe anything before flashing that though. Only wipe when flashing ROMs and kernels.
Go back into Recovery and flash that .zip the exact same way you flashed the ROM. Minus the data wipe.
Others: Does he wipe cache/dalvik as well? I've seen some posts say to do that when flashing mods that are flashable .zip and some don't. I've done both ways and seen no negative consequences (as of yet).
Yeah, that last post was dumb, I clicked "Submit" before I tried anything on my own. Flashing it the exact same way minus data wipe worked perfectly, though the prediction boxes for input in the market app (when you hit "search" and start typing, the things that drop down to give suggestions) still appear to be black on black. Bleh.
Also, the Dalvic wipe before installing was a good idea; I don't know for sure if it made a difference but a good habit to get into.
EDIT: By the way, this has got to be the least grammatical/spelling errors in a forum thread I've ever seen. I think I may like this site...
Wiping the cache and dalvik most likely isn't necessary but it can never hurt.
RossGoldenstein said:
Yeah, that last post was dumb, I clicked "Submit" before I tried anything on my own. Flashing it the exact same way minus data wipe worked perfectly, though the prediction boxes for input in the market app (when you hit "search" and start typing, the things that drop down to give suggestions) still appear to be black on black. Bleh.
Also, the Dalvic wipe before installing was a good idea; I don't know for sure if it made a difference but a good habit to get into.
EDIT: By the way, this has got to be the least grammatical/spelling errors in a forum thread I've ever seen. I think I may like this site...
Click to expand...
Click to collapse
I'm really new to this stuff myself (rooted for the first time ~2 days ago) and so I'm unsure how to further fix the blacked out predictions in the Market. Perhaps you could try contacting those within the thread of the ROM you downloaded, specifically citing that you installed the initial blacked out fix so that they don't redirect you back to the fix you've already applied, testing your patience and furthering your wait for perfection.
Aye, this site has got to be full of some of the most fluent English-speaking persons I've found on the internet.
So yea...as much as I know my desire's motherboard needs replacement...And I dont have warranty. Is there any way to fix it without changeing whole motherboard?
You provide us no information at all about what's wrong with your device.
What do you want to do with it? Solder stuff?
There is a 100% chance that you will destroy your phone when you open it and mess around with the subminiaturized highly vulnerable microelectronics.
There's something called insurance.
Swyped...
hypophysis said:
You provide us no information at all about what's wrong with your device.
What do you want to do with it? Solder stuff?
There is a 100% chance that you will destroy your phone when you open it and mess around with the subminiaturized highly vulnerable microelectronics.
Click to expand...
Click to collapse
It restarts,boot loop i think it's called. So I cant afford new motherboard so could I take my phone to some1 that knows what he's doing and could he fix it?
LordRyver said:
It restarts,boot loop i think it's called. So I cant afford new motherboard so could I take my phone to some1 that knows what he's doing and could he fix it?
Click to expand...
Click to collapse
Maybe the forum can help you
For this we need some more information:
1. Do you have the original HTC Sense ROM?
1a. If YES skip the points 2 - 5 and continue with 6.
2. If NO: which ROM you have installed?
3. Did you change the Radio ROM?
4. Have you unrooted your phone?
5. Are you S-Off / changed Hboot (partition table)
6. Do you use the original SD-Card?
7. Since your reboots started: have you installed any software just before?
8. Which program(s)
If you can answer these question we can help you - I don't think (hope) your motherboard is dead. Often there are simple solution to fix a "dead" phone
MonacoHias said:
Maybe the forum can help you
For this we need some more information:
1. Do you have the original HTC Sense ROM?
1a. If YES skip the points 2 - 5 and continue with 6.
2. If NO: which ROM you have installed?
3. Did you change the Radio ROM?
4. Have you unrooted your phone?
5. Are you S-Off / changed Hboot (partition table)
6. Do you use the original SD-Card?
7. Since your reboots started: have you installed any software just before?
8. Which program(s)
If you can answer these question we can help you - I don't think (hope) your motherboard is dead. Often there are simple solution to fix a "dead" phone
Click to expand...
Click to collapse
1. I had,but it used to turn off and get into boot loop while playing games like GRave defense. Never happened while playing shoot bubbules.
2. DevNull. First was dev,then leedroid,now back to dev. I keep him in sd card in case my phone wont turn on. Sometimes it restarts in middle of movie so I left him 2 times until morning and it first time turned on and second time didnt,again started to restart. Same with reflashing roms. Sometimes helps,sometimes no.
3.Yes.Radio_32.56.00.32U_5.17.05.08
4.Yes. I had hboot 0.83 or 0.93 and I used AlpharevX and then unrevoked.
5.Yes.
6.I dont know, I got it when I bought phone. (it was used when I bought it.)
7.Hm......Well...I dont think so...when I bought it, I turned phone off and after um... about 1 h I tryed turn it on and it started restarting. Then after some time turened on again.
And btw now it sometimes starts restarting not even hot.
So your problem is random reboots? or does your device not start up at all?
If the problem is just a bootloop, you won't need to replace the motherboard. You just need to flash the correct and working software.
mortenmhp said:
So your problem is random reboots? or does your device not start up at all?
If the problem is just a bootloop, you won't need to replace the motherboard. You just need to flash the correct and working software.
Click to expand...
Click to collapse
But that used to happened with original rom too...un...one guy said that bootloop is because motherboard is faulty. Now I just watched whole movie. And it was ok. But I tink if I would use market or opera it would restart. But im not sure. Sometimes it dosnt restart. And if I would flash all correct software my phone would turn on quicker?
oh god...
Don't answer my question with the word but. It's NOT an answer. So lets take the question again and this time do only reply to the question:
Is you problem random reboots or a bootloop?
Those 2 are NOT the same, while random reboots is exactly what the name implies a bootloop implies that your phone is unable to enter the android system due to a failure on startup.
So please in order for anyone to help you, you must make it very clear what you problem is, as otherwise we cannot tell you what to do.
Everything you have told up until now is that you have some problem(you use bootloop and random reboot equally) and that you might or might not know that it happens when running some specific apps.
mortenmhp said:
oh god...
Don't answer my question with the word but. It's NOT an answer. So lets take the question again and this time do only reply to the question:
Is you problem random reboots or a bootloop?
Those 2 are NOT the same, while random reboots is exactly what the name implies a bootloop implies that your phone is unable to enter the android system due to a failure on startup.
So please in order for anyone to help you, you must make it very clear what you problem is, as otherwise we cannot tell you what to do.
Everything you have told up until now is that you have some problem(you use bootloop and random reboot equally) and that you might or might not know that it happens when running some specific apps.
Click to expand...
Click to collapse
Sorry. By bootloop I mean my phone restarts and then just starts viberating and just stays in white htc logo screen. But after some time I can enter android system. This happanes when I do something with my phone.
If I may throw 2 cents in...
I do not know if this will be the fix for you, but if I had this issue, the first thing I would do is boot the phone up and wait until it loads properly (I gather it loads sometimes but not others, which is why you watched a movie??), make a Titanium backup of everything, then Nandroid backup.
Next, do full wipe
1 Factory reset
2 (in Mounts/Storage) Format Dalvic/data/sdext/system
3 (in Advanced) Wipe Dalvic cache.
Now reflash your ROM and restore Titanium.
Might all sound like basic stuff, but any time I have had issues with bootloops or FCs or whatever, it's usually because I didn't wipe properly. Now I always wipe everything with new ROMs and never have an issue.
If this doesn't help, you may commence panicking I'M KIDDING!!
777ace said:
If I may throw 2 cents in...
I do not know if this will be the fix for you, but if I had this issue, the first thing I would do is boot the phone up and wait until it loads properly (I gather it loads sometimes but not others, which is why you watched a movie??), make a Titanium backup of everything, then Nandroid backup.
Next, do full wipe
1 Factory reset
2 (in Mounts/Storage) Format Dalvic/data/sdext/system
3 (in Advanced) Wipe Dalvic cache.
Now reflash your ROM and restore Titanium.
Might all sound like basic stuff, but any time I have had issues with bootloops or FCs or whatever, it's usually because I didn't wipe properly. Now I always wipe everything with new ROMs and never have an issue.
If this doesn't help, you may commence panicking I'M KIDDING!!
Click to expand...
Click to collapse
Did that already...first time all was the same,but now looks kinnda better. If it wont go to restarting screen while chagring i'll be happy...After doing factory reset it started to move things from pc to sd very slowly.
777ace said:
If I may throw 2 cents in...
I do not know if this will be the fix for you, but if I had this issue, the first thing I would do is boot the phone up and wait until it loads properly (I gather it loads sometimes but not others, which is why you watched a movie??), make a Titanium backup of everything, then Nandroid backup.
Next, do full wipe
1 Factory reset
2 (in Mounts/Storage) Format Dalvic/data/sdext/system
3 (in Advanced) Wipe Dalvic cache.
Now reflash your ROM and restore Titanium.
Might all sound like basic stuff, but any time I have had issues with bootloops or FCs or whatever, it's usually because I didn't wipe properly. Now I always wipe everything with new ROMs and never have an issue.
If this doesn't help, you may commence panicking I'M KIDDING!!
Click to expand...
Click to collapse
Hello LordRyve,
follow the great description from 777ace , these are the steps which should bring your Desire back.
I only would not restore all the programs via Titanium Backup after your fresh install. The reason is that there might be a "bad" program you have installed before. Just restore a program, check if system runs without problems, then restore the next and so on.
But NEVER restore system apps via Titanium backup - this mostly WILL mess up your system!
And before flashing devnull ROM download it again and check the MD5SUM, just to be sure your downloaded ROM is ok.
Good luck
MonacoHias said:
Hello LordRyve,
follow the great description from 777ace , these are the steps which should bring your Desire back.
I only would not restore all the programs via Titanium Backup after your fresh install. The reason is that there might be a "bad" program you have installed before. Just restore a program, check if system runs without problems, then restore the next and so on.
But NEVER restore system apps via Titanium backup - this mostly WILL mess up your system!
And before flashing devnull ROM download it again and check the MD5SUM, just to be sure your downloaded ROM is ok.
Good luck
Click to expand...
Click to collapse
Well now it runs rll great And I didn't do anything different. It restarted while charging but at about 98% it was cold again and I succesufly turened it on with first try. If something will go wrong i'll try do 777ace guide. Now I would like to ask...what to do that files would get transefered from my pc to sd faster? Because when my battery is not full it starts charging and overheating and restarting. Also isnt overheating and restarting caused by bad motherboard?
MonacoHias said:
Hello LordRyve,
follow the great description from 777ace , these are the steps which should bring your Desire back.
I only would not restore all the programs via Titanium Backup after your fresh install. The reason is that there might be a "bad" program you have installed before. Just restore a program, check if system runs without problems, then restore the next and so on.
But NEVER restore system apps via Titanium backup - this mostly WILL mess up your system!
And before flashing devnull ROM download it again and check the MD5SUM, just to be sure your downloaded ROM is ok.
Good luck
Click to expand...
Click to collapse
Also if there is bad app,could I try downloading it again after restoring with titanium?
LordRyver said:
Also if there is bad app,could I try downloading it again after restoring with titanium?
Click to expand...
Click to collapse
Sure you can.
With a bad app I ment that an app can mess up your system (not a corrupted program file).
For example task killers I would name "bad" apps as they are useless in current ROM and maybe could things worse.
A very important tip at the end: perform Nandroid backups on a regular basis - so you can allways come back to a working system.
LordRyver said:
...
Now I would like to ask...what to do that files would get transefered from my pc to sd faster? Because when my battery is not full it starts charging and overheating and restarting. Also isnt overheating and restarting caused by bad motherboard?
Click to expand...
Click to collapse
Do you use Windows or Linux? For me file transfer on Linux is much slower compared to Windows. Sometimes it helps to switch to another USB port on your PC.
Does your Desire also restarts when you use the power supply (charging not via PC)?
MonacoHias said:
Do you use Windows or Linux? For me file transfer on Linux is much slower compared to Windows. Sometimes it helps to switch to another USB port on your PC.
Does your Desire also restarts when you use the power supply (charging not via PC)?
Click to expand...
Click to collapse
Windows. Yes. It gets overheat. And switching to another USB port didn't helped. But I noticed that usb cable's part that puts into pc was a bit hot.
MonacoHias said:
Sure you can.
With a bad app I ment that an app can mess up your system (not a corrupted program file).
For example task killers I would name "bad" apps as they are useless in current ROM and maybe could things worse.
A very important tip at the end: perform Nandroid backups on a regular basis - so you can allways come back to a working system.
Click to expand...
Click to collapse
hm...I think problems start when I install classic ghost radar
Ok...can some1 explain me. my phone started to restart while moving movie from pc to sd. Now it's cold. But when I turn it on, it loads and after 1 sec in android system it starts restarting again. why?
HI,
I am facing a peculiar kind of a problem. I recently rooted my Desire Z following the cyanogen wiki to the letter. I have tried many ROMS but whichever ROM I install, I am facing this problem. For the first few days of Install, my phone works perfectly. But after a few days if I reboot, my phone gets stuck is a bootloop( i dont know if thts the right word, coz it boots and it starts the android but before the launcher is started it restarts again.
First I was using Flinny's CM10.1 test builds, and then I changed it cause I thought that was the problem. Now I am using Andromadus' Mimicry 1.5 which is also giving me same problem.
Everytime this happens I have to use the PCIMG10 file to restore it and then root it again and then install the ROM..
Is there any way to solve this problem.. I'll provide logs if u require... I am desperate..
yes a log cat would help much maybe a cat /proc/last_kmsg or have adb running during the bootloop and post here.
seems a strange issue and may just be an evil app installed or something else entirely but without more info i would just be guessing. and do actually have to reroot? i mean what would happen if you were just to wipe clean and install a new rom via recovery? also it may help so could you provide all that is on your bootloader screen
also see HERE for some more help, feel free to post in there as well (trying to reduce the clutter in these forums)
demkantor said:
yes a log cat would help much maybe a cat /proc/last_kmsg or have adb running during the bootloop and post here.
seems a strange issue and may just be an evil app installed or something else entirely but without more info i would just be guessing. and do actually have to reroot? i mean what would happen if you were just to wipe clean and install a new rom via recovery? also it may help so could you provide all that is on your bootloader screen
also see HERE for some more help, feel free to post in there as well (trying to reduce the clutter in these forums)
Click to expand...
Click to collapse
I have a logcat from when I was running Flinny's CM10.1 test builds.. I faced this many times with that ROM and so I took a log last time it happened.
BootLoopLog_CM10.1
The latest time since I was in a hurry to get my phone back to working condition couldnt get a log. But soon after, it happened again. I installed only "Explorer" and "What'sapp" when this happened again. I have captured the logs and here it is.
BootLoopLog_Mimicry1.5
And ya I did try and restore a previous backup, and I also tried wiping and installing the ROM, but in both the cases the Phone will hang at the boot animation screen or restart again. Here attached is a log of the phone restarting after a clean wipe and fresh install of the ROM.
BootLoopLog_Mimicry1.5-after reinstall
Code:
Bootloader screen info
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
RADIO-26.03.02.18_M3
eMMC-boot
Sep 8 2010,15:56:30
Please help me out... this is kind of frustrating.
P.S- I did see that thread.. but since my phone was not bricked, I didnt post it over there..
are you sure you did a full wipe? there was definitely more than just a couple user apps installed, could be some leftovers from last rom. there isnt anything im seeing too specifically in the logcats to show your issue, all of them seem to bootloop in slightly different times but while running some java system frameworks
anyhow, if you were to start completely fresh, unroot, reroot, flash rom, etc - all works fine? lets say you just signed into gmail, then reboot phone, would it loop? or do you need to run the os for some time then turn it off and then it happens?
for now how about this, flash THE DZ ONE through bootloader as described in the thread,
then flash SUPERWIPE through recovery
then when all is done flash rom of choice, for fun lets do mimicry, let it boot, sign into google, let phone sit like 10min, choose reboot and see what happens
demkantor said:
are you sure you did a full wipe? there was definitely more than just a couple user apps installed, could be some leftovers from last rom. there isnt anything im seeing too specifically in the logcats to show your issue, all of them seem to bootloop in slightly different times but while running some java system frameworks
anyhow, if you were to start completely fresh, unroot, reroot, flash rom, etc - all works fine? lets say you just signed into gmail, then reboot phone, would it loop? or do you need to run the os for some time then turn it off and then it happens?
for now how about this, flash THE DZ ONE through bootloader as described in the thread,
then flash SUPERWIPE through recovery
then when all is done flash rom of choice, for fun lets do mimicry, let it boot, sign into google, let phone sit like 10min, choose reboot and see what happens
Click to expand...
Click to collapse
What I mean by full wipe is.. First I would do the factory reset from recovery, then proceed to wipe the "cache partition" , dalvik cache, battery stats, and then in the mounts and storage menu, again do a format of cache, data and system... Is there anything else I should do to do a clean wipe?
And If i start fresh, nothin happens immediately.. u need to let the OS run for a day or two and then this happens..
Anyways.. i'll try what you suggested and get back to you.... thanks for all the help..
manujosephv said:
What I mean by full wipe is.. First I would do the factory reset from recovery, then proceed to wipe the "cache partition" , dalvik cache, battery stats, and then in the mounts and storage menu, again do a format of cache, data and system... Is there anything else I should do to do a clean wipe?
And If i start fresh, nothin happens immediately.. u need to let the OS run for a day or two and then this happens..
Anyways.. i'll try what you suggested and get back to you.... thanks for all the help..
Click to expand...
Click to collapse
I did what you suggested.. and the phone is not rebooting as of now... I'll run the OS for a couple of days..and see what happens.. i'll keep you posted..
manujosephv said:
I did what you suggested.. and the phone is not rebooting as of now... I'll run the OS for a couple of days..and see what happens.. i'll keep you posted..
Click to expand...
Click to collapse
Guess what... That worked... My phones been running without bootloop till now.. :good:
Everytime I reboot, my heartbeat increases.. but it comes through smoothly at the end.. thanks a lot..
P.S - Completely off the topic.. Mimicry ROM is giving me insane battery life.. Running the phone more than 1 day without charging.. :laugh:
I have an ongoing issue with Galaxy W phone and CM.
The problem is that the phone spontaneously decides to not boot.
I had run CM10 from first Alpha, and on a couple of occasions it would, after several days or weeks use, stay on the CM spinning logo, and refuse to go to interface.
I got around this by keeping a couple of Nandroids handy and just restored them when the boot issue occurred.
On subsequent fresh install, I ran for a couple of weeks with virtually no app installations, to see if something I was running was causing the issue. Turns out no relationship.
I have just flashed Alpha 7 of CM 10 and now its doing it again. This is a fresh install.
I re-downloaded the ROM from the second mirror, and tried flashing with that, but get the same result.
Is it possible the flash memory in my phone is faulty? On a PC if you install an OS - fresh install - and it wont boot, generally its either RAM or HDD. Given this is a recurring issue, I wonder if its the phone, rather than the OS thats causing the problem - as I have tried with several of the Alphas and both download locations of the most recent Alpha and its still happening.
Can anyone suggest?
Is there a chkdsk option for phone flash memory?
thanks
Jim
[edit] just installed CM9 (last beta) and its doing the same thing - stuck at boot animation and will not get to desktop.
Anyone? Any ideas how to fix this?
Sv: [Q] CM10 A7 ongoing boot issue
Flash stock rom and see if the problem still exists. If not, flash cm again. If it does, get a new phone.
Sent through time and space from my s3mini.
16kzx81 said:
I have an ongoing issue with Galaxy W phone and CM.
The problem is that the phone spontaneously decides to not boot.
I had run CM10 from first Alpha, and on a couple of occasions it would, after several days or weeks use, stay on the CM spinning logo, and refuse to go to interface.
I got around this by keeping a couple of Nandroids handy and just restored them when the boot issue occurred.
On subsequent fresh install, I ran for a couple of weeks with virtually no app installations, to see if something I was running was causing the issue. Turns out no relationship.
I have just flashed Alpha 7 of CM 10 and now its doing it again. This is a fresh install.
I re-downloaded the ROM from the second mirror, and tried flashing with that, but get the same result.
Is it possible the flash memory in my phone is faulty? On a PC if you install an OS - fresh install - and it wont boot, generally its either RAM or HDD. Given this is a recurring issue, I wonder if its the phone, rather than the OS thats causing the problem - as I have tried with several of the Alphas and both download locations of the most recent Alpha and its still happening.
Can anyone suggest?
Is there a chkdsk option for phone flash memory?
thanks
Jim
[edit] just installed CM9 (last beta) and its doing the same thing - stuck at boot animation and will not get to desktop.
Anyone? Any ideas how to fix this?
Click to expand...
Click to collapse
What do you mean by clean install?
wipe data and cache?
Try to format /system /data /cache and /sdcard (backup your internal storage first)
MiguelPT said:
What do you mean by clean install?
wipe data and cache?
Try to format /system /data /cache and /sdcard (backup your internal storage first)
Click to expand...
Click to collapse
Thanks guys, very much for your replies
By "clean install" I have gone to wipe menu of CWM and wiped everything, then CM with wipes, then Gapps.
Ok so I need to try to flash with stock ROM. I had considered that but could not find an Australian ROM in the I8150 section of the Forum. Can anyone tell me where I can get one from?
- or -
-- maybe its ok to flash with any English ROM - will achieve the same thing? - sorry if this is a dumb question - I just dont want to make the situation any worse
Try Removing all SD Card,SIM and battery. Then reinsert battery after 15 minutes and reflash the CM10/Stock ROM. It will boot up
miki2o said:
Try Removing all SD Card,SIM and battery. Then reinsert battery after 15 minutes and reflash the CM10/Stock ROM. It will boot up
Click to expand...
Click to collapse
Ok. Thanks for the suggestion. I did that and its stuck on the Logo still. No change.
You can get stock ROM for Australian (Vodafone) from here http://www.hotfile.com/dl/187592956/3abb3c5/I8150TDULM1_I8150TVAULG1_VAU.zip.html
arya_ruby said:
You can get stock ROM for Australian (Vodafone) from here http://www.hotfile.com/dl/187592956/3abb3c5/I8150TDULM1_I8150TVAULG1_VAU.zip.html
Click to expand...
Click to collapse
Thanks very much for the link I have downloaded it
So I noticed something else thats kinda weird.
When I go to /sdcard, its not showing the content of the sd card
So if I swap out the card, it still loads the same folder, not the stuff from the sd card I have inserted.
I have a few of these. All read fine in the PC, but the phone does not seem to recognise the files, as they dont change if I reboot with a different card/different content in.
/sdcard
Code:
../
.android_secure/
Android/
LOST.DIR/
RZR/
Video/
cm-10-2013~ancora-alpha7.zip
gapps-jb-~signed.zip
SD card contents when read from PC
Code:
I8150TDULM1_I8150TVAULG1_VAU.zip
Its as though it has a partition called /sdcard, and can't mount the content of the physical card itself. Anyone seen this before? Is there a way to re-partition internal memory?
16kzx81 said:
Thanks guys, very much for your replies
By "clean install" I have gone to wipe menu of CWM and wiped everything, then CM with wipes, then Gapps.
Ok so I need to try to flash with stock ROM. I had considered that but could not find an Australian ROM in the I8150 section of the Forum. Can anyone tell me where I can get one from?
- or -
-- maybe its ok to flash with any English ROM - will achieve the same thing? - sorry if this is a dumb question - I just dont want to make the situation any worse
Click to expand...
Click to collapse
Just do full wipe you'll not wipe cwm!
My suggestion: Go the Pristineā¢ Way.
(thread in the General forum)
Sent from my GT-I8150 using xda app-developers app
arya_ruby said:
You can get stock ROM for Australian (Vodafone) from here http://www.hotfile.com/dl/187592956/3abb3c5/I8150TDULM1_I8150TVAULG1_VAU.zip.html
Click to expand...
Click to collapse
I tried that zip, but it started to install and the phone shut down/restarted at beginning of install (just after wipes)
Can anyone else confirms this file actually works?
Is there a Tread source I can refer to?
pepoluan said:
My suggestion: Go the Pristineā¢ Way.
(thread in the General forum)
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the suggestion. I tried but the problem persists.