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?
Related
Hello everyone,
I got me a GIO for christmas and I'm quite content with this phone, but I've had frequent reboots due to a bug in the WLAN driver (as far as I have read). So I decided to install a custom ROM and I chose CM 7.2, which works great most of the time apart from one major annoyance: every time I restart the phone (had to switch it off during exams, the phone's misbehaving, whatever reason) I'm getting into bootloops. The only solution: wipe user data, reflash, wipe user data, restore all settings, etc.
I read that these bootloops aren't uncommon, but I feel that I should be able to reboot my phone without having to set everything up again.
So my questions are: a) Is it perfectly normal what I am experiencing? b) Is there something obvious I am doing wrong? c) What could I do better? Is there a good way to backup my user data and restore it into a fresh system without having to reboot? How could I possible get rid of those bootloops? How could I help the ROMs developer to help me get rid of the bootloops?
I'd be very thankful for any directions
Hpi said:
Hello everyone,
I got me a GIO for christmas and I'm quite content with this phone, but I've had frequent reboots due to a bug in the WLAN driver (as far as I have read). So I decided to install a custom ROM and I chose CM 7.2, which works great most of the time apart from one major annoyance: every time I restart the phone (had to switch it off during exams, the phone's misbehaving, whatever reason) I'm getting into bootloops. The only solution: wipe user data, reflash, wipe user data, restore all settings, etc.
I read that these bootloops aren't uncommon, but I feel that I should be able to reboot my phone without having to set everything up again.
So my questions are: a) Is it perfectly normal what I am experiencing? b) Is there something obvious I am doing wrong? c) What could I do better? Is there a good way to backup my user data and restore it into a fresh system without having to reboot? How could I possible get rid of those bootloops? How could I help the ROMs developer to help me get rid of the bootloops?
I'd be very thankful for any directions
Click to expand...
Click to collapse
a no
use titanium backup,
then flash the rom with clockworkmod
flash gapps
wipe data cache
reboot
restore titaniumbackup you made
done
thats all
sent from my Samsung Galaxy Gio using XDA premium
Hi voetbalremco,
Thank you for your prompt reply. I have installed Titanium Backup now, for all I have read that should at least make restoring my "system" after a re-flash more bearable. The only thing I'm worrying about is that the TB wiki states that I have to reboot the phone after restoring system settings, but thanks again for the hint. I'll tell you how it worked, when (hopefully if) I run into the need of a re-flash.
Hpi said:
Hi voetbalremco,
Thank you for your prompt reply. I have installed Titanium Backup now, for all I have read that should at least make restoring my "system" after a re-flash more bearable. The only thing I'm worrying about is that the TB wiki states that I have to reboot the phone after restoring system settings, but thanks again for the hint. I'll tell you how it worked, when (hopefully if) I run into the need of a re-flash.
Click to expand...
Click to collapse
You can make a full backup if you want in CWM
Sent from my GT-S5660 using xda premium
Maybe your download was corrupt or whatever... try re-downloading the latest CM7.2.
I doubt that the download was corrupt. I have had this problem for various versions now (CM7.1RC + subsequent patches, CM7.2 + patch). But just to make sure, are the md5 sums of the original files anywhere?
Is there a way I could turn off the boot animation and get debug output on the screen so I can see what's going on when it bootloops?
HI all,
I've flashed CWM5.5 from the recomended thread and installed Cyanogen 9 Alpha 1. Unfortunatly the phone seems to boot up but does never leave the boot animation screen (yes I've also flashed gapps after cyanogen).
Anyone can identify this pattern? On a normal device I could hook it up through a serial cable and try to debug the boot... Eventually how can I do that with a I8150?
Well, any help would be most welcome. I'm totally available for testing and I do have some experience with Linux even at a very low level/system space.
Install
Use CWM5.
Warning: Only use this recovery to flash CM9. Otherwise, you risk bricking your phone!
Wipe data and cache.
Flash update*.zip.
Flash gapps*.zip. You must flash gapps after every upgrade to CM9 since /system is formatted, wiping your previous add-ons.
Reboot phone.
After you setup your Google account, reinstall the three apps from Market in order to restore most of your apps, call log and SMS history.
Warning: Do not restore backup data of system apps!
If you restore a bad backup with cached settings in telephony.db in data/data/com.*.*.telephony it can break MMS.
It seems that restoring backups can also break Calendar sync.
read it thoroughly ...
1st you must flash update*.zip
2nd gapps*.zip
that just about it ....
what is your current kernel ?
That was pretty much it... I've restored not the original operator crap ROM, but instead the Value Pack ROM.
CyanogenMod9 seemed to install ok, but just looped and the phone didn't finished the boot. I'm not really sure on what happened. I'm just finishing restoring the stuff
I'm guessing you didn't wipe data/cache.
I did a factory reset, but sure, it might not have wiped the whole thing... Going to try again.
@argo68
True mate, the issue was not wiping the user cache. I've wiped the cache now from ClockWorkMod and it worked ok. Takes some time to boot compared to the stock samsung ROMs but it works fine
Anything you need tested ? I can most likely help.
I do have a problem with apps though, for example, GMAIL doesn't show the body of the message... as you can see on the screenshot, but I guess this is a app related issue maybe?
http://susepaste.org/images/39081870.png
After a reboot somehow it boots a bit faster and the gmail app is now displaying the body of the email and it seems a bit faster...
Good work, gonna ride this for a few days and see what happens.
@argo68
If you need beta testers, let me know. I'm off work this days but can't wait to get into my lab and check this stuff deeper
@argo68
he is arco68
just in case he takes offence, which I don't believe he would
Hopefully not, all the norwegians I knew personally were very nice people and always ready for some bear
ketheriel said:
Hopefully not, all the norwegians I knew personally were very nice people and always ready for some bear
Click to expand...
Click to collapse
reAdy for some BEAR ????
do you actually mean bear or beer ??
chocolemon said:
reAdy for some BEAR ????
do you actually mean bear or beer ??
Click to expand...
Click to collapse
Maybe it's the Nordic ascendance. They fight a bear with one hand while holding the beer with the other.
Hi I'm using this cyanogen mod for quite a few days now. The back side of the phone is always warm and the battery is drained very fast. Anyone have this similar problem?
I'm sure that I install the ROM correctly as i cleared everything on the phone with CWM 5.0.0.4 before and after. (Phone data / Cache Partition / Dalvik Cache / Battery Cache)
Any help would be appretiated
No such problem here. You should use an app to check what frequency the phone is running at in idle, and also how much load there is on the cpu.
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
If someone can solve my app issue there will be a reward in the form of a donation! How's that for an incentive?
I understand I posted a similar thread before to this but I wasn't resolved and I am completely out of ideas.
Which ever rom I'm on, which ever kernel, after a random amount of time using my phone an app with crash,
which seems to set off a chain reaction and then all my apps begin crashing.
It's usually google apps that start it, such as messaging, play store or contacts. Apex launcher also often gets affected.
Killing all apps and restarting the phone occasionaly fixes the problem for a little while.
I have used different kernels, used different android builds, factory reset the phone, wiped the sd card, cleared cache etc etc. Is this a hardware issue?
Things that might be worth knowing
When entering bootloader I get the following error messages:
Code:
Sd Checking...
Failed to open usb master mode
[COLOR="Red"][Preload] failed to open usb master mode[/COLOR]
[COLOR="Blue"]loading PJ46IMG.zip image...[/COLOR]
Failed to open usb master mode
[COLOR="blue"]Please plug off USB[/COLOR]
I can not save images, in other words it seems I cannot write to the SD card, looking in mounts and storage in CWM
reads:
Code:
unmount /cache
mount /data
mount /sdcard
mount /system
format /cache
format /data
format /sdcard
format /system
format /system
mount USB storage
Which implies that everything is unmounted? Surely this can't be right and this is why I cant write to SD? Mounting them fixes the writing to SD problem temporarily.
When I get problems occuring next time I'll try to capture screenshots. I really hope someone has an idea what's going on here, if it's hardware I guess I'm screwed as the phone is out of warranty? :S
I have attached logcat's from around when the crashing happened last time, maybe someone can skim through them and identify the issue? Thanks
did you try different gapps???
I've tried lots of different gapps, the miui Rom im using now came with gapps as well
Both of your observations are normal, no problem there.
App force closing does not relate to kernel.
You should make a logcat when the apps start crashing so someone can assist you in diagnosing the issue. (Google it if you don't know how)
Also try re-download the ROM, possibly could be corrupted ROMs that you flashed.
tomascus said:
Both of your observations are normal, no problem there.
App force closing does not relate to kernel.
You should make a logcat when the apps start crashing so someone can assist you in diagnosing the issue. (Google it if you don't know how)
Also try re-download the ROM, possibly could be corrupted ROMs that you flashed.
Click to expand...
Click to collapse
Ok I'll make a logcat now, cheers bud. And I have tried with multiple different roms so it seems unlikely its a download issue
Heres the files. It took me ages to get any results, its typical when you want it to crash, it doesn't! Can someone more tech savvy then me have a thumb through them and try to identify the issue? Thank you very much
I think there is errors in both the logs but more in the second!
Now offering a reward for some help leading me to resolving this issue
bump
Taking a look, check back tomorrow.
Sent from my HTC One X using xda app-developers app
hahhahhaaa said:
Taking a look, check back tomorrow.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Cheers man, really appreciate it!
If it helps, my hunch (baring in mind I'm not that savvy with this) is something to do with partitions unmounting themselves? when looking in CWM
sometimes they are mounted sometimes they aren't
That error in the bootloader is common for all phones, simply unplug the USB and replug it in.
The USB not mounting is caused by old CWM versions, here is the latest.
About the second problem, it seems you are using custom ROMS and the problem started by the SQL management (i would eliminate hardware as a cause)
But please inform me which Rom you are intending to use so I can confirm the procedure, and whether its Sense/Sense+/AOSP.
For now, try the following:
- Re-Install the Rom with SQL tweaks ON,EXT4 tweak, and FORCED GPU rendering OFF.(if options available)
- DON'T restore anything from the system partition
Are you using the latest CWM recovery v5.8.4.0?
The error you get in bootloader has nothing to do with apps crashing and is totally normal. Even I get the same error.
And like the guy above me told, the FC's are caused by SQlite trying to write to readonly databases.
Similar problems to this have been fixed by wiping phone. Have you restored app using e.g. titanium backup?
And also, try formatting sd-card using pc, not recovery.
Vcek said:
That error in the bootloader is common for all phones, simply unplug the USB and replug it in.
The USB not mounting is caused by old CWM versions, here is the latest.
About the second problem, it seems you are using custom ROMS and the problem started by the SQL management (i would eliminate hardware as a cause)
But please inform me which Rom you are intending to use so I can confirm the procedure, and whether its Sense/Sense+/AOSP.
For now, try the following:
- Re-Install the Rom with SQL tweaks ON,EXT4 tweak, and FORCED GPU rendering OFF.(if options available)
- DON'T restore anything from the system partition
Click to expand...
Click to collapse
I am using the most up to date version of CWM 5.8.4.0
What exactly is SQLite anyway?
Currently I'm using ADRH The ICS version, in the instilation I checked all the tweaks so I expect the EXT 4 tweak was on.
What do you mean about restoring from the system partition? I don't restore anything and still get the problems.
hahhahhaaa said:
Are you using the latest CWM recovery v5.8.4.0?
The error you get in bootloader has nothing to do with apps crashing and is totally normal. Even I get the same error.
And like the guy above me told, the FC's are caused by SQlite trying to write to readonly databases.
Similar problems to this have been fixed by wiping phone. Have you restored app using e.g. titanium backup?
And also, try formatting sd-card using pc, not recovery.
Click to expand...
Click to collapse
I have wiped using - Factory reset (bootloader), factory reset (CWM and factory reset in the phone (running sense)
And nope I left titanium backup alone. Do you mean as in mount storage and format in windows, FAT32?
[★] said:
I am using the most up to date version of CWM 5.8.4.0
What exactly is SQLite anyway?
Currently I'm using ADRH The ICS version, in the instilation I checked all the tweaks so I expect the EXT 4 tweak was on.
What do you mean about restoring from the system partition? I don't restore anything and still get the problems.
I have wiped using - Factory reset (bootloader), factory reset (CWM and factory reset in the phone (running sense)
And nope I left titanium backup alone. Do you mean as in mount storage and format in windows, FAT32?
Click to expand...
Click to collapse
Don't ever wipe from the bootloader if on custom roms/recovery.
Don't check all the tweaks, especially the force gpu rendering, this one is known well for causing FCs.
Sent from my EndeavorU
Unfortunately, i am still having the same problems that you are, and still cant seem to get my phone to boot, but i am on the latest Hboot 1.31 but still getting all the same apps crashing as you are
I am hoping for a potential Jelly bean RUU to released maybe?
try running in safe mode and see if a 3rd party app is causing this. Hold the turn off option in the power menu.
Vcek said:
Don't ever wipe from the bootloader if on custom roms/recovery.
Don't check all the tweaks, especially the force gpu rendering, this one is known well for causing FCs.
Sent from my EndeavorU
Click to expand...
Click to collapse
Alright I'll remember that next time haha! How come anyway?
Installed again, no tweaks, stripped it down with rom cleaner, disabled gps services and haven't (yet) synced my google account just to be safe, we will see what happens
Stuar said:
Unfortunately, i am still having the same problems that you are, and still cant seem to get my phone to boot, but i am on the latest Hboot 1.31 but still getting all the same apps crashing as you are
I am hoping for a potential Jelly bean RUU to released maybe?
Click to expand...
Click to collapse
It's a real pain isn't it! Yeah man the sooner the new RUU (1.28 first please!) come out the better.
Vcek said:
try running in safe mode and see if a 3rd party app is causing this. Hold the turn off option in the power menu.
Click to expand...
Click to collapse
I get this error before installing any apps usually so I dont think 3rd party apps have the chance to cause trouble
First problem which I have had before on a sense rom, Pressing the send button on a message does nothing. This usually leads to apps beginning to crash
Followed by a random screen 'turn off' and phone reboot followed by being stuck in splash screen
..Yep, still getting crashed. Can I reformat the whole memory? What would be the best way to go about this?
[★] said:
First problem which I have had before on a sense rom, Pressing the send button on a message does nothing. This usually leads to apps beginning to crash
Followed by a random screen 'turn off' and phone reboot followed by being stuck in splash screen
..Yep, still getting crashed. Can I reformat the whole memory? What would be the best way to go about this?
Click to expand...
Click to collapse
You could reflash the RUU file to get your phone back to stock and work from there. --this rewrites all partitions
You need to downloading it (there's a thread in android development listing them all), relock your bootloader, and run it as administrator from windows.
peedub said:
You could reflash the RUU file to get your phone back to stock and work from there. --this rewrites all partitions
You need to downloading it (there's a thread in android development listing them all), relock your bootloader, and run it as administrator from windows.
Click to expand...
Click to collapse
would this work for someone on jelly bean?
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: