Hey ppl, i just flashed my phone to the generic world firmware. And after i root it with gingerbreak, the battery became 1% and therefore i took out the batt and try to reinsert it... However, my phone just died after that... Can't press anything and my laptop can't even detect the phone. Its just like a phone without battery=( Anyone has any idea how to fix this? I don't want to have a bricked phone...
Charge your phone 20-30min/with 1% stay/then update OTA newes update or update last one with same, or just take out batt for few min. and put it back. Hope its help
i am very curious right now. How can i get the 2.3.4 ota update for my phone? i am currently on uk firmware. Went to generic world last night and the batt bug scared the hell out of me. Now back on uk. Do you have any idea? =)
http://forum.xda-developers.com/showthread.php?p=17848218#post17848218
this is serious matter where most of people having the same issue.so here's a suggestion, http://forum.xda-developers.com/showthread.php?t=1274572
Related
I have an interesting problem, kind of. Bought my phone second hand as supposedly unlocked & debranded but on boot up it after the HTC logo I get the Virgin Media logo, not really an issue though. Anyway the problem is when I switch the phone off and then switch on again it boots up fine to the home screen and then it will reboot itself and carries on doing this. i.e. boot up to home screen then reboot again continuously.
To get out of this reboot loop I have to remove the sim & boot the phone with no sim in it then switch off and insert my normal Vodafone phone sim and switch on again. after that the phone is fine until I power down and then the same thing happens.
Anybody else experienced this or got any ideas?? It came with 1.15.405.4 firmware already installed and I have tried reflashing with the same firmware using the goldcard method & it worked but the problem remains. When the sim registers on the network is when the reboot loop seems to start.
did you try reflashing it ?
hold down the side button (down) and press on at the same time.
then select erase data and press on again
if you bought it second hand, its hard to say what the previous user has done with it ...
Yep tried reflashing it, just about to reflash again with an older rom. It's just wierd that a sim card authenticating to the network would cause a reboot loop.
TieT said:
did you try reflashing it ?
hold down the side button (down) and press on at the same time.
then select erase data and press on again
if you bought it second hand, its hard to say what the previous user has done with it ...
Click to expand...
Click to collapse
Maybe it's a dumb question - But I'm having some issues that doesn't seem to get solved by a factory reset - Would it be an idea to reflash it for this, so the phone gets a fresh rom?
How would I do it specifically? Do you know of a guide somewhere?
sudman said:
Yep tried reflashing it, just about to reflash again with an older rom. It's just wierd that a sim card authenticating to the network would cause a reboot loop.
Click to expand...
Click to collapse
have you tried a different sim card ?
Ye tried a different sim card, boots fine and all is good till you reboot the phone and then the same happens again. Anyways flashing was a disaster this time round as I was doing it on my work pc and Symantec kicked in thinking it found a virus with adb.exe and halted the process & quarrantined the file. Now everytime I try and reflash on a different PC I get the dreaded error(110):file open error. Disconnect the phone & all I get is a black screen & HTC logo. Nice. Thanks Symantec you've just bricked my Desire!!
*UPDATE* - Fixed.
Removed the battery, left it for a few hours then reflashed on a different pc and it flashed fine. Then thought I'd try & repeat so reflashed with the older rom from here (originally used the newer rom posted on Modaco) and got the error again and again couldn't flash back to the newer. Removed the battery left for an hour and then could reflash again and get it working!! Wierd
I had the same problem.
My Solution: remove battery, remove the SIM, put battery reboot, turnoff, remove battery, put SIM, put battery, boot
first i want to excuse my bad english,hope you will undestand what i´m trying to say.
i have the same problem since a few days.
first time i notice it,was when the desire was charching and i used it a bit,it restarts again and again.so i put out the battery and wait a few minutes,than it works.
it´s also,when i use it a long time with wifi or 3G....the the phone turns off and i have the boot loop.
but when i take out my sim,it works fine.
my question is,do i need a new sim or is it a hardware problem?
does anybody know?
greetz from germany!
sorry, wrong thread
same here.
Tequila98 said:
first i want to excuse my bad english,hope you will undestand what i´m trying to say.
i have the same problem since a few days.
first time i notice it,was when the desire was charching and i used it a bit,it restarts again and again.so i put out the battery and wait a few minutes,than it works.
it´s also,when i use it a long time with wifi or 3G....the the phone turns off and i have the boot loop.
but when i take out my sim,it works fine.
my question is,do i need a new sim or is it a hardware problem?
does anybody know?
greetz from germany!
Click to expand...
Click to collapse
i have the exact same problem!! any solution? after that the phone will boot loop over and over! damn!
I had the same problem last week.
I suspected it had to do with the EXT3 partition.
Solved it by first flashing the OTA 2.2 ROM (for rooted users) as this does not use the EXT3. Then used Rom manager to recreate the EXT3.
Now all ROMs that use the EXT3 run fine!
hmmp
as long as i know, i did not install anything on my phone lately so thats the problem so far and i think tequila98 also having the same problem as me, cause when i remove my sim card the phone works fine. but ive reset my phone yesterday and not restarting so far hope this will continue.
I really wished there was a dead fix to this problem we are all having!
My problem:
My phone was running fine until a few weeks ago. There was no rebooting problems when I first got my phone (April) and when I flashed my phone for the first time (May). Happened a few weeks ago when I was browsing on YouTube where my phone suddenly restarted on it's own.
Before it was once a couple of days, now it has gotten more frequent and annoying.
I don't think the heat is the problem because I don't go on the internet much because of my data plan. I use wifi when I browse the web, youtube, etc. And I certainly don't use Google maps or any heavy duty applications. That's just what I think...
My phone rebooted 3 times today in a time span of 4 hours? I noticed that my phone rebooted itself when I use the camera to take a picture or video. Doesn't happen everytime, but that's what happened today. Also, when my phone rebooted today, my application Advanced Task Killer was automatically removed from my phone! That was weird... But I experienced another reboot even after having the app removed.
I really hope someone can find the core of this problem and fix it!
My phone is running on DeFroST 2.0b Android 2.2
My battery stats: 42% for display, 26% for cell standby, 21% for phone idle, 4% for android system, 3% for voice calls, 2% for android OS
jxleung said:
I really wished there was a dead fix to this problem we are all having!
My problem:
My phone was running fine until a few weeks ago. There was no rebooting problems when I first got my phone (April) and when I flashed my phone for the first time (May). Happened a few weeks ago when I was browsing on YouTube where my phone suddenly restarted on it's own.
Before it was once a couple of days, now it has gotten more frequent and annoying.
I don't think the heat is the problem because I don't go on the internet much because of my data plan. I use wifi when I browse the web, youtube, etc. And I certainly don't use Google maps or any heavy duty applications. That's just what I think...
My phone rebooted 3 times today in a time span of 4 hours? I noticed that my phone rebooted itself when I use the camera to take a picture or video. Doesn't happen everytime, but that's what happened today. Also, when my phone rebooted today, my application Advanced Task Killer was automatically removed from my phone! That was weird... But I experienced another reboot even after having the app removed.
I really hope someone can find the core of this problem and fix it!
My phone is running on DeFroST 2.0b Android 2.2
My battery stats: 42% for display, 26% for cell standby, 21% for phone idle, 4% for android system, 3% for voice calls, 2% for android OS
Click to expand...
Click to collapse
same problem here guys why desire have a this problem ? why no one cant find any solution ?
PLZ help us
Ehsan021 said:
same problem here guys why desire have a this problem ? why no one cant find any solution ?
PLZ help us
Click to expand...
Click to collapse
It's probably hardware problem with motherboard. Therefore I recommend you to take your phone to repair center and they should replace mobo with new one. That's what I did and now everything is ok.
I am having the exact same problem. Seems to be related to the SIM.
But the SIM works fine in another phone.
Did anyone find any more information?
If you get random reboots its most likely ther motherboard there is a massive thread about it on the forums. You need to send it off to a HTC repair centre.
Just got this problem.
I rooted yesterday. Today I made a nandroid backup. After that the phone is in a reboot loop.
How is this possible from just and backup???
Tnx.
R
Edit:
Restored backup and is working fine again.
nandroid backup loop
rottunix said:
I rooted yesterday. Today I made a nandroid backup. After that the phone is in a reboot loop.
How is this possible from just and backup???
Click to expand...
Click to collapse
I have the same problem.
rottunix said:
Restored backup and is working fine again.
Click to expand...
Click to collapse
I will try it. Maybe the backup is not only a backup but also a remove? Strange.
I will comment if this works also for me.
EDIT: Restore helps
I just got a new Evo yesterday from having my old one replaced due to screen seperation.
So my Evo Android 2.2 and all the newest OTA on it..
Before my Evo was rooted running CM6 and life was great. Now I can't get the thing unrooted with Unrevoked 2.3.1 and can't find a new method with the Evo I have now with all the newest OTA..
Any suggestions on what to do so I can get this awful HTC Sense off my phone A.S.A.P..
Thanks so much to every one in advance.
Your sure that it didn't work because its not like the old days were it flashed and engineered version. When the phone reboots it will have the same ROM as it did when you started the process. Only the stock ROM will be rooted. I'm sure you checked to see if it has ClockworkMod recovery on it now. I just rooted a EVO I received two days ago it worked fine.
on unrevoked it says that it failed and say it happens some times and to try again.
I tried about 5 times this morning and it failed every time.
power down pull the battery spin in a circle three times while chanting unrevoked will revoke the carriers attempt to prevent me from rooting. Then try again!
ok so really the battery part is the only part that you HAVE to do but the rest is still kinda fun. My friend had this problem and whether it was coincidence or not pulling the battery and then putting it back seemed to do the trick first time through it worked after.
Thanks.
I will give it a try when i get home from work.. Now I just have to wait 5 more hours till I get off work, durrrrrrrrrrrrrrrrrrr.
A battery pull did the trick..
Thanks for the help..
Hi after days of searching the internet I have finally realised I need to post here and ask for help, sorry if this has been posted before though as I have really looked hard everywhere!
Anyway, after flashing a RCMix rom my desire started to drop calls as soon as I either picked up or answered one and only ever rarely got 2G signal in what I know is H signal zones. I changed roms but the problem persisted and after countless hours of searching and trying my sim in other phones, I have deducted that it is my desire which is the problem.
So I'm going to take it back to a t-mobile store, as I were unrooting using the RUU exe I got the 140 error, my phone will no longer boot but still has bootloader, fastboot and recovery working! Is my phone bricked, I can't find any help anywhere on how to put my desire back to stock
Please could any of you shine some light onto my situation?
Many many thanks
You have recovery? Did you try installing another rom to make the phone work again?
After that you can try to unroot it again, I think...
Okay, I will try installing a froyo rom now, will post the results of a second unroot...
Right very strange indeed, just flashed AceSMod007 and signal problems have seem to have gone away (although I had tried this before with many roms - maybe the unrooting process fixed my phone somehow?)... so this means there is no need to unroot and send back to t-mobile, hmmmm all seems to good to be true! thanks for the help though, wouldn't of tried flashing another rom if you hadnt mentioned it
Hello guys,
Long time reader/user, first post...
Here is the story... On a concert last week, my GF's Galaxy S3 fell into one big beer glass... it was an accident, nothing to do about it.
After we cleaned all we can in site and let it dry for 24 hours, we turned it on and found the screen was damaged... damn... ok, I got a working screen from a friend and replaced the original... At first everything was OK, but after some 8-10 hours, the screen started to go blank on random events (pressing the apps button, opening an SMS, pressing the power button to lock, and several other actions)...
We did a factory reset, it worked for a while and then failed again... removed the battery and put it back on... worked for some time and then it happened again...
As it was recently upgraded to 4.3 (TCE) software, and it stops happening from time to time, I thought it was a software issue, so then I reinstalled the stock firmware using Odin... it worked for 8-9 hours and then it happened again.
Then, I rooted the device and installed CM 10.2 ... Worked fine again for a while and then it got even worse.
Tried to install Stock ICS (4.1.1) firmware downloaded from sammobile.com, but the install failed and the phone was soft-bricked.
Used Odin again to install 4.3 stock firmware again and it worked... for some hours again...
Tried using a different battery... same issue... removed the SDCARD... same issue...
I still think the stock ICS 4.1.1 (TCE) firmware may work, but unfortunately I cannot find it to download... all the sites (including posts here on XDA) direct to a link on "Hotfile", that unfortunately was taken down by the goverment for piracy issues.
I'm out of ideas now, so, if you guys have this firmware, please help me sharing it, or if you have other ideas to troubleshoot this issue, it will be greatly appreciated... my GF has only one month with this phone and is very frustrated.
Thanks in advace. Kind regards,
--
Bureizu (Xperia S LT26i - LB - JellySlim_FullPower)
[BUMP 25/12/2013]
Hey guys.
No response yet? Help please.
Ok, cleaned all the apps installed by Google Play from the computer... flashed back stock JB... and we're installing apps one by one... problem reappeared but less frequently...
I'm thinking memory issue... not really sure...
If anyone has some advice, it will be greatly welcome...
Hi
I've been going back and forth for a couple of days now , thinking if i should post this post or not .
so here it goes , i had a n910p for a couple of months now it was on 4.4.4 when i got it and it worked just fine no problems except some dying battery related problems -phone shuts down when using the flash camera, the phone shuts down without any warning and then i find the battery at 5% when turned back on - ( i didn't know it was a battery problem back then ) , but everything else was just fine .
-i should mention i'm in Jordan not the US so the phone is unlocked sim .
So i wanted to upgrade to Marshmallow maybe the problems got fixed , so in order to upgrade to MM i had to first upgrade to 5.x.x and i did and tested it for a couple of days it had some Freezes but nothing unmanageable , i changed the battery while i was on 5.1.1 there was no problem here no freezes no random shutdowns .
And then i upgraded to MM that's when the problems started to show one after the other , all described here and add to that i had to add and remove the battey 3-4 times in order to turn on the phone.
so i thought to my self it started since i upgraded to MM , maybe if i downgraded to kitkat it'll go away .
i downgraded to 4.4.4 not the stock just to see if it was any better, and it was !!
no freezes no random shutdowns except for one problem if i wanted to shutdown the phone or do a restart i had to remove and add the battery in order to get back on .
so my question is , why is this happening ?
is it a hardware problem and just my luck it started popping out when i started upgrading ?
why is it there is less problems when i downgraded to Kitkat ?
P.S: i upgraded to 5.x.x first by flashing it, because i couldn't upgrade OTA .
Mohannad_Almasharqa said:
Hi
I've been going back and forth for a couple of days now ,
.......
P.S: i upgraded to 5.x.x first by flashing it, because i couldn't upgrade OTA .
Click to expand...
Click to collapse
This problem is a little confusing and beyond me, but I have to ask and suggest one thing.
Instead of doing OTA, Have you tried to just use odin to flash the Marshmallow firmware you want?
Mohannad_Almasharqa said:
Hi
I've been going back and forth for a couple of days now , thinking if i should post this post or not .
so here it goes , i had a n910p for a couple of months now it was on 4.4.4 when i got it and it worked just fine no problems except some dying battery related problems -phone shuts down when using the flash camera, the phone shuts down without any warning and then i find the battery at 5% when turned back on - ( i didn't know it was a battery problem back then ) , but everything else was just fine .
-i should mention i'm in Jordan not the US so the phone is unlocked sim .
So i wanted to upgrade to Marshmallow maybe the problems got fixed , so in order to upgrade to MM i had to first upgrade to 5.x.x and i did and tested it for a couple of days it had some Freezes but nothing unmanageable , i changed the battery while i was on 5.1.1 there was no problem here no freezes no random shutdowns .
And then i upgraded to MM that's when the problems started to show one after the other , all described here and add to that i had to add and remove the battey 3-4 times in order to turn on the phone.
so i thought to my self it started since i upgraded to MM , maybe if i downgraded to kitkat it'll go away .
i downgraded to 4.4.4 not the stock just to see if it was any better, and it was !!
no freezes no random shutdowns except for one problem if i wanted to shutdown the phone or do a restart i had to remove and add the battery in order to get back on .
so my question is , why is this happening ?
is it a hardware problem and just my luck it started popping out when i started upgrading ?
why is it there is less problems when i downgraded to Kitkat ?
P.S: i upgraded to 5.x.x first by flashing it, because i couldn't upgrade OTA .
Click to expand...
Click to collapse
Odin MM like suggested.. Don't do any mods. If it persist, then you might be looking at faulty hardware ie main board.
i just flashed MM after reading your replay , and will test it out.
any tips on what to do with the phone if it's a hardware problem ?
so right at the first boot i had this error shown in the images (attachment)
i removed the battery and restart the phone and it booted correctly , the same problems began to show freezing random restart and it keeps booting to recovery and i had to add and remove the battery a couple of times to turn the phone on .
i returned to stock 5.1.1 apparently it's the most stable thing i can use right now , honestly i'm puzzled on this problem i'm quite sure it's hardware and software somehow and if i send it to a local shop they probably will say "i don't know what seem to be the
problem "
so i'm just going to keep using it until it becomes a replacement parts for his other brothers . :crying:
I'm no expert, but i've poured through dozens, maybe hundreds of pages about this issue. Happened entirely with MM, and most people have thrown their hands up calling it "faulty hardware".
All the accounts, the symptoms, the timing, and the root problem (eMMC error) point to a bug in MM that messes something up when it installs itself- *sometimes*. Those unlucky enough to catch this bug are stuck with it, and end up with essentially a brick or returning it.
Hardware doesn't make sense, not when the issue completely coincides with an update. Unfortunately, I don't know how to completely 100% wipe this device and re-load it from scratch, which is what I think it's gonna take. I don't even know what all *can* be wiped 100% :/
akira6968 said:
I'm no expert, but i've poured through dozens, maybe hundreds of pages about this issue. Happened entirely with MM, and most people have thrown their hands up calling it "faulty hardware".
All the accounts, the symptoms, the timing, and the root problem (eMMC error) point to a bug in MM that messes something up when it installs itself- *sometimes*. Those unlucky enough to catch this bug are stuck with it, and end up with essentially a brick or returning it.
Hardware doesn't make sense, not when the issue completely coincides with an update. Unfortunately, I don't know how to completely 100% wipe this device and re-load it from scratch, which is what I think it's gonna take. I don't even know what all *can* be wiped 100% :/
Click to expand...
Click to collapse
Here is the thing though (I have the same issue). If you remove the battery and put it back in, say 30 seconds later, it won't turn on. If you remove the battery for like 5 minutes and then put back in, it might turn on. I'm talking about the first little vibrate it does when holding the power button to turn on. It really acts like a hardware issue to me. The only work around that has worked for me is an app called wakelock. Using this app and selecting partial partial wake lock makes the phone run completely normal.
What REALLY sucks right now is that I have an OTA update waiting for me and the phone needs to reboot to install. The phone won't reboot. When it turns off, it won't turn back on without removing the battery for 5+ minutes.
IT is the MM Update
Im not an expert or anything but i have the same problem cant update cuz phone has to be restarted i finally had enough of it took it in told them (sprint) to update it thay said thay did but thay didnt. Called and thay couldnt fix it so i said the heck with it and i flashed it still doe the same must use wake lock app wish someone could figuer this out.
gbennett21 said:
Im not an expert or anything but i have the same problem cant update cuz phone has to be restarted i finally had enough of it took it in told them (sprint) to update it thay said thay did but thay didnt. Called and thay couldnt fix it so i said the heck with it and i flashed it still doe the same must use wake lock app wish someone could figuer this out.
Click to expand...
Click to collapse
Yes having the same issue as well but now even the wakelock app won't keep it. The phone wil stay for maybe an hour, then reboots and will continue to reboot until I take the battery and then start it again afterwards. The length of time the phone stays on varies really and it could be as long as 3 or 4 hours, but it will definitely reboots itself, I cannot got 1 day without this happening. At this point the phone is unusable. I am on another phone at the moment.
I did flash the MM updates (even went back 3 or 4 older versions) using ODIN and same issue. I am debating whether I flash an older Lollipop version and see if that makes a difference.