So my phone is having a weird problem and i dont think i know the trigger. It works fine before, and suddenly it just shut down by itself. At first, i have to wait 1 hour, yes 1 hour and i can turn it on and get into android and use it again. If i turn it on before 1 hour, it cant go into the android system, and soon after the mi logo it will turned off and i have to wait again for 1 hour, weird right? And after that it works fine as long as i dont turn it off or restart it, or if it doenst turn off it self and i can use it for days. BUT, now, it just wont get into the android system even when i already wait 1h+, and now its just sitting there for dayss, still cant get into the system.
Do you guys know whats the problem? Can i just re flash it with the newest miui? Last time i use it, it still on miui 11 i think, so can i just flash it with miui 11 again with no problems? I dont really know about the anti rollback something or whatever im afraid i will hardbrick it lol.
P.S. i already had the same issue before, but not long after that the phone's dead, literally dead, no responses or anything just totally dead, and i brought it to mi service center, problem solved. I think they said they replaced the board so i got fresh new phone hw inside. But now i got the same issue again but, the difference is it still can be turned on, not dead.
zianix said:
So my phone is having a weird problem and i dont think i know the trigger. It works fine before, and suddenly it just shut down by itself. At first, i have to wait 1 hour, yes 1 hour and i can turn it on and get into android and use it again. If i turn it on before 1 hour, it cant go into the android system, and soon after the mi logo it will turned off and i have to wait again for 1 hour, weird right? And after that it works fine as long as i dont turn it off or restart it, or if it doenst turn off it self and i can use it for days. BUT, now, it just wont get into the android system even when i already wait 1h+, and now its just sitting there for dayss, still cant get into the system.
Do you guys know whats the problem? Can i just re flash it with the newest miui? Last time i use it, it still on miui 11 i think, so can i just flash it with miui 11 again with no problems? I dont really know about the anti rollback something or whatever im afraid i will hardbrick it lol.
P.S. i already had the same issue before, but not long after that the phone's dead, literally dead, no responses or anything just totally dead, and i brought it to mi service center, problem solved. I think they said they replaced the board so i got fresh new phone hw inside. But now i got the same issue again but, the difference is it still can be turned on, not dead.
Click to expand...
Click to collapse
There is no anti rollback in redmi 5 plus (vince),so try
Related
Hello!
Well... I have this phone since yesterday... I plugged to the computer with Kies, and well, a update was available... now the phone have Froyo and the aesthetics changed completely, it looks awesome.
But, the phone have this ANNOYING problem that, after using it... like 5~10 minutes of no activity, when I try to use the phone again it doesnt work... doesn't respond to any button, I have to take off the battery in order to restart it and that over and over again...
I've realized also that this happens when I'm using wifi, if I left the phone with wifi on this happens, without wifi seems to work fine.
Somebody have any clue what could be? there's little information about this issue in the internet...
I think I'm going to return it but I want to try everything I can do (without voiding the warranty) since the phone was perfect for what I wanted.
Thanks in advance!
Hey. I got the same problem here. It only happened a few times when I just had froyo that came stock on my galaxy 5 but I recently installed cyanogenmod 7 and now its happening everytime I put my phone down.
So I'm guessing it may be directly related to what rom is installed? I've heard about it happening a bit to people who have 2.1 installed to.
I dont know too much but it seems the only fix is to take out battery and turn on.
Sorry I can't help more. I hope somebody knows a bit more than me on this.
Think this is called something like the 'wifi sleep of death', something to do with the rom. i'd try change the rom and see if it still occurs
Thanks for the hints tho!, but I returned the phone... it seems that is a bug related to the update of the phone, since I know that with the out of the box 2.1 version it doesn't have that issue...
You know, the mobile carriers also do weird stuff to the roms... -__-
Hey guys, long time xda user but never really bothered making an account and posting lol, but **** just got serious so I need some specific help. So I have been flashing roms almost since the first day I got this phone, never had a problem not even flashing ICS roms. But in this case, I was running [ROM] Blue 2.2 Frankenstein-FishmanMod Final and it was working perfect, had battery for days, no lag , and everything was smooth as usual. Then out of the blue, my vibrant decides to shutdown(no I still got plenty of battery left), so I wouldnt call this an infinite reboot because it doesnt reboot it just shuts down every time I turn it back on! It usually shuts down a couple of secs after I turn it on. And now im having a hard time even getting to CWM. I tried odin(multiple times) but no cigar, problem still persist. WTF . Does anyone know what I can do?
You could try to wipe everything if the phone dosent shutsdown, did you try using Heimdall(I think thats the name) and what especific problem you have with Odin?
Hob0dan-T959
Hi guys! First off, I know this sounds like a common problem, but I've looked through several times and haven't found a solution yet.
I have a SGS2, came as 2.3.3 stock but upgraded a while back to 2.3.5 through Kies. It was working perfectly for as long as I remember.
About a month ago the battery started acting weird going from 80% to 20% in no time, heating up too, I do remember dropping the phone once during this period, but it was nothing (just thought I should include this, also, I usually leave the phone plugged into the charger overnight as I do not have a power source at work (i work outdoors) i probably need a battery replacement)
The screen brightness would sometimes flicker and then POOF! The phone shuts off...At first this would happen at any activity, nothing specific, BUT, I have noticed that it intensifies with the Facebook app.
Anyways, usually plugging the phone back into the charger and powering it up would bring it back online, but not this time. It would get stuck looping the animation of the 'S' at the beginning and no booting up. I have a valid warranty card which I'm guessing will get the phone either fixed or replaced but I need help to try to salvage whatever info I can get my hands on, preferably everything, but my memos are most important to me.
Thanks for the help!
sherief87 said:
Hi guys! First off, I know this sounds like a common problem, but I've looked through several times and haven't found a solution yet.
I have a SGS2, came as 2.3.3 stock but upgraded a while back to 2.3.5 through Kies. It was working perfectly for as long as I remember.
About a month ago the battery started acting weird going from 80% to 20% in no time, heating up too, I do remember dropping the phone once during this period, but it was nothing (just thought I should include this, also, I usually leave the phone plugged into the charger overnight as I do not have a power source at work (i work outdoors) i probably need a battery replacement)
The screen brightness would sometimes flicker and then POOF! The phone shuts off...At first this would happen at any activity, nothing specific, BUT, I have noticed that it intensifies with the Facebook app.
Anyways, usually plugging the phone back into the charger and powering it up would bring it back online, but not this time. It would get stuck looping the animation of the 'S' at the beginning and no booting up. I have a valid warranty card which I'm guessing will get the phone either fixed or replaced but I need help to try to salvage whatever info I can get my hands on, preferably everything, but my memos are most important to me.
Thanks for the help!
Click to expand...
Click to collapse
are u rooted
try flashing the stock rom again and check if u face the same issue
I'm not rooted. I tried doing that using odin and got the stock firmware from sammobile. same thing happens, stuck at the boot.
a friend suggested i try to flash the stock ICS version, same thing.
sherief87 said:
I'm not rooted. I tried doing that using odin and got the stock firmware from sammobile. same thing happens, stuck at the boot.
a friend suggested i try to flash the stock ICS version, same thing.
Click to expand...
Click to collapse
Weird. It shouldn't boot loop. You sure your version is GT-I9100 and not GT-I9100G? Since I'm in Riyadh, the latest version for GB here (Saudi Arabia) was JPKJ2, but that's for GT-I9100, dunno about the G version.
Sent from my GT-I9100 using Tapatalk 2
okay so with the help of a friend and this awesome forum, i managed to install cwm, from there i could take a nandroid backup, but i cant mount the phone as a drive or anything to copy the files, and i'm guessing i cant use this backup i just took to restore later because it'll just get me stuck at the same place im at now
i read that i can use unyaffs to extract files from the resultant backup image, so my question is, before i do a wipe, is there any other method through which i could get a backup of my stuff? the things i would very much like to get a copy off are my messages/notes/whatsapp history and pretty much anything really
thanks for the help!
Hi, I have a galaxy s2 in what i believe is hard brick mode. A little backstory, i was watching some stuff online when i noticed the battery bellow 35%. So i pluged it to the usb charger. I left it there for like 20 minutes. When i came back, i unlocked the phone only to see tons of "error" messages and the force close window. Apperently it had to force close /system?... I was puzzled so i just pulled the battery off and on and tried turning it in. Stuck at the welcome screen. I tried ro acces recovery mode. The android icon was "dead" and some error messeges appeared in red, unable to mount /system, invalid argument. I turned it off, but the welcoming screen poped up without me touching anything. I left it for a few minutes. Then i pulled the battery off for a few minutes too. When i tried to turn it on again, the phone was dead. Nothing works, i tried:
Pressing the power button for a minute
Download mode
Recovery mode
Leaving the battery out for hours
Leaving it charging for hours
Nothing. Im stunned, mainly because i never rooted it or touched anything. Im desesperated at this point, any help will be great. I abused google and made tons of search, but everything related to my problem has to do with flashing and rooting failures. Which i never did with my phone.
If you've never messed with it, and assuming it hasn't expired time-wise, send it in for warranty service. If you don't have warranty, try another battery just in case, then try a jig. Then start looking for JTAG repairers (assuming it can be JTAG'd), and if it can't, take it to local mobile repair shops & have them take a look at it. If they can't/won't fix it, then send it to Samsung/authorised repairer.
I think i voided the guarranty by updating the phone to ICS a few months back... Im trying the battery swap now.
demian93 said:
I think i voided the guarranty by updating the phone to ICS a few months back... Im trying the battery swap now.
Click to expand...
Click to collapse
That wouldnt void the warranty.
{go back to your iphone since you are an android noob}
theunderling said:
That wouldnt void the warranty.
{go back to your iphone since you are an android noob}
Click to expand...
Click to collapse
It depends on how he upgraded to ics, if he did from an official update then is ok, but if he flashed a leaked or a custom rom based on ics then no more warranty if he can't flash the original samsung rom
Already tried changing batteries, didnt work...
You know what to do next then.
I still dont understand the cause of the brick, my phone is dead and it wont even charge. This is bogling my mind. And yeah im an adroid noob, this my first smartphone.
hi all, as the title says my hox + is repeatedly crashing n rebooting. this has been happening since yesterday. the hox was fine in the morning and then randomly started playing up in the afternoon. the phone is completely stock n locked. its not the power button as when I enter fastboot the phone stays on n doesn't even freeze. it went flat after a while so I left it to completely flatten over night. its been on charge for a while now n its still rebooting even without me turning it on, it turns on by itself.....freezes.....then reboots.
any ideas guys?
really don't want to pay for insurance again n I now know it takes takes 2 weeks to replace a lost phone so god knows how long it will take them to look at a phone
"pay for insurances AGAIN"?
Does this happen randomly? Or it happens all the time? If you will be enough desperate, you can always try a factory reset as this looks like a software bug.
/\/\ said:
"pay for insurances AGAIN"?
Does this happen randomly? Or it happens all the time? If you will be enough desperate, you can always try a factory reset as this looks like a software bug.
Click to expand...
Click to collapse
yeh ive tried factory reset in fastboot and also erased cache command. im going to try a rom now ive got it to stay off n charge. it will only stay off selecting power down quickly, if I select power off in bootloader it restarts. it does seem like software though as it doesn't auto reboot in recovery or bootloader
well a new rom ddnt work.....n of course I cant find an ruu anywhere
bassyboy said:
well a new rom ddnt work.....n of course I cant find an ruu anywhere
Click to expand...
Click to collapse
you can try increasing the voltage for the CPU...
does it show something on its screen when it reboots?
cant do anything. it would boot up fully...then freeze after 5 secs or so then reboot and do the same again. Ive claimed for a new phone now tho. I couldn't find an ruu after trying a new rom so insurance repair wasn't going to happen. the phones gone now n hopefully a replacement will come soon. guessing I had a bad refurb last time iclaimed