Related
my g1 keeps on restarting after i downgraded my phone to rc29 so i can root it. this never happen to me before. if i have my charger plugged into my phone, when the phone loads and passes the g1 screen onto the android screen, it'll automatically reboot itself. if my charger isnt connected. it wont reboot, it'll just turn off. i have 2 g1s and both battery are working perfectly. what am i doing wrong? i can enter to recovery mode and fast boot without any problem. DREAMIMG is installed correctly also. a little help will be great! thanks in advance
I've just ran into this myself. I am running Biffmod 2.0, went into UI settings, changed LED notification for missed call, it rebooted, changed it back, still rebooting, rebooting itself ever since. Put it on charge as I have to go out. Picked it up, missed call. Rebooting. Went into Menu to look at LED settings, still rebooting.
:/
Give up. GAME OVER.
Well, not so dramatic. Short answer for me = Hard reset. Not much on there anyway. Done too much reflashing for that.
Scorpia said:
Give up. GAME OVER.
Well, not so dramatic. Short answer for me = Hard reset. Not much on there anyway. Done too much reflashing for that.
Click to expand...
Click to collapse
all i know that it's not bricked. there has to be a way to fix it.
WEIRD! i got it working now. took the phone apart to the main board and put it back on slowly. and WOILA! it worked lol
hey guys, I don't know what's going on with my S7 but yesterday was working fine and out of nowhere everything started to FC! From twitter to "Google Services Framwork", Gmail, browser, tweetdeck, calendar, voice, I can't pretty much use it anymore, I haven't done any new app installations so i don't know what's wrong! is it just me, or anyone else having this problem??
Any help will be much appreciated!
Thanks
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
djdanska said:
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
Click to expand...
Click to collapse
ha! i remember I already did that. After the Update we had, and I exchanged mine for a new one I decided to stay with no root (i don't know why! lol) so I guess I'll reset everything and go back to root I figured at the end I was gonna do that, but I was trying to see if it was just me or there was a fix
thanks man!
ok, so since yesterday I've been trying to factory reset the DS, and when it boots back on, everything stays the same!
I'm a little confused now, if I take a picture and I turn the tablet off, when I turn it back on, the picture disappears. Same thing happens if I move widgets, delete or create new ones on the screen, they go back to as the configuration was on friday night! GV not working, and the last message that shows there, same thing, shows the last one on friday. I don't know what can I do.... should I call dell??
duck tape and dynomite
stupid thing started crashing yesterday FC this and FC that ....cant restore it as i no longer have write access to the internal sd card
1) tried nv flash
2) tried restoring from clockwork
3) tried pushing files through adb
4) tried fastboot ....
if i didnt just dump money into this thing id blow it up ......
any help would be appreciated.......any tips to fix it or kill it completely so i can get another one
actually deleted all of the files on internal sd card and uninstalled every program on the device looked completly stock ....rebooted it and it went back to how it was yesterday ......theres gotta be a reason why other are having the same problem that started on the same day .....maybe dell pushed an OTA update and screwed us ......just a thought cause mine was fine till i went 4g yesterday so my sis could post facebook pics ....not sure but hope we can figure this out
Samething happened to me
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
jz83 said:
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
Click to expand...
Click to collapse
I'm running stock, and I discovered the hard way that you can't let the S7 battery run all the way down. The S7 will not power itself down in time. I had the same issue, and the only way around it was to do a complete factory reset, using the menu button from the main screen. I think the reset is in the "About" section, but I don't have my S7 with me now.
Being used to WM6, which powers the device down at 5%, I was not expecting the device to do this, but there it is.
dell streak 7
im not sure if I am the only one with this issue you but becareful with the streak 7 mine well both of mine wont charge properly and the newest one wont charge at all. i have to send it back to dell for them to fix it. Im not sure what cause this but my only advie is to never use a different charger for it only dell chargers. Im guessing that it messes up the battery callibration and then it gets really hot when charging
They just won't. They'll work normally when on and they'll go off after so much time of idling, but when I turn off the phone it buzzes like a complete shutdown and they just won't go off. I think it started when I loaded that leaked 2.3.3 captivate rom from SamFirmware and now it continues after a 2.1 stock downgrade and updating to 2.2 via Kies. I can't find anyone else with this problem.
hmm That's weird... if you pull the battery and replace it do they come back on?
Oh yea, I've been playing around with it and everything to see what I can do. It started happening about the same time my power/sleep button started messing up. It still is messed up, but I don't see how one would effect the other. Like I said, they work normally until I try to turn it off. Then, they don't go off until I pull the battery or boot it back up.
Jmurph3 said:
Oh yea, I've been playing around with it and everything to see what I can do. It started happening about the same time my power/sleep button started messing up. It still is messed up, but I don't see how one would effect the other. Like I said, they work normally until I try to turn it off. Then, they don't go off until I pull the battery or boot it back up.
Click to expand...
Click to collapse
if they dont go off when you turn it off until you pull the battery, it might be safe to assume your phone isnt actually off. Try reflashing whatever ROM you have going on within your cappy.
redkenji said:
if they dont go off when you turn it off until you pull the battery, it might be safe to assume your phone isnt actually off. Try reflashing whatever ROM you have going on within your cappy.
Click to expand...
Click to collapse
It has happened on two different ROMs. The 2.3.3 leak and then again when I flashed back to stock 2.1 and even after I updated to 2.2 via Kies mini.
maybe try calling samsung then. They may be able to address the issue. My friend has a vibrant that he bricked, hard bricked and they fixed it for free so, they might be able to help you out. it might be a hardware issue they can help you out with.
redkenji said:
maybe try calling samsung then. They may be able to address the issue. My friend has a vibrant that he bricked, hard bricked and they fixed it for free so, they might be able to help you out. it might be a hardware issue they can help you out with.
Click to expand...
Click to collapse
Very possible. I won't have a phone for that time, though. Haha....oh how we can't live without our mobile devices...
Att will send you a replacement first, then you send you old one back. If its still under warranty. I just told them I don't have a home phone, and they overnighted the replacement for free.
Sent from my Captivate running Continuum 5.6
Well, it randomly stopped. It shuts down and when it buzzes the backlights won't stay on. Idk what I've done for it to stop. I still have a busted power button, time to send in for a replacement.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Hey guys,
I could need a bit of help! It's now the third time I'm having this problem, don't ask me why. I've got the feeling that I read the whole forum here, but didn't find anything similiar.
The 1st time I didn't change anything (ok, rooted it, but nothing else)
The 2nd time I overclocked it slightly (~850-900 MHz)
Now I'm using MIUI.
But back to the problem:
I'm unable to use the keyboard, every time I'm sliding open the keyboard (even when it's turned off), it "crashes". The screen stops working or it freezes, the only way to turn it off is taking out the battery.
However, the bigger problem comes now: I'm barely able to restart it. It tries booting, but is restarting all the time or the screen is just turning on (in some angles you see that it is turned on but it's black). After many retries, it starts working, sometimes the bootloop is running 15min or i have to manually restart it 10 times or more. The strange thing is that the keyboard works fine, nevertheless I have to choose between using it opened (taking it with me becomes difficult ) or closed...
...the main problem now is flashing a new Rom, I'm currently trying it through the android sdk and adb, but using the power-button + x is easier
I don't think that I can solve the problem, I sent the device two times back (warranty till may 2012), but maybe someone here knows a bit more. My guess is that one of the sensors is broken, or some parts of the display that should manage the sliding process...
Anyway, thanks for your attention!
Web
If you already have Rom Manager, just click Reboot into Recovery..
inches0 said:
If you already have Rom Manager, just click Reboot into Recovery..
Click to expand...
Click to collapse
Tried to use one a time ago, but it wasn't working right....
However, now I'm not even able to boot it, the screen just flashes and turns off itself before trying to restart a few moments later....guess I lost my Milestone
Sbf back to stock?
taptaptouch said:
Sbf back to stock?
Click to expand...
Click to collapse
the computer isn't finding it anymore...I'll back up the data and try use my warranty... I hope that they don't complain about MIUI...
But I'm still not getting the point, why my mobile had these issues three times, although they "repaired" it twice...and nobody else is having the same problem
Hi there!
I was wondering if anyone around here had some ideas on what to do.
My LG G4 had been working fine until today. I unlocked the screen to check my e-mail and it completely froze. It was plugged in at the time, so I unplugged it to see if I could restart it. The charging light was still blinking, the power button didn't respond, absolutely nothing.
I took the battery out, left it for a minute or so and rebooted. It loaded, unlocked, but I could only get to the app menu before it completely froze again. Afterwards, screen went black.
On the third try, it booted up to the LG logo and that's it. It popped up about 3 times and screen went black. No other response whatsoever. I can only try to reboot again only after taking out the battery, but it does the same thing.
I switched the battery with another one of the same model, nothing changed. Computer doesn't recognize it either.
I've looked around for a bit and I can't find anything like my case. The closest thing described is the boot loop. I'm not exactly sure that's my case, but it seems similar to a certain degree.
I got it to boot to recovery mode, but it doesn't do anything. It asks me if I'm sure I want to run it, and in the second 'yes' it freezes up completely again. Screen goes black and does absolutely nothing else.
Added note, phone upgraded to 6.0 yesterday morning. I had no issues with it until now. No app updates were running at freezing time.
I'm considering taking it to the store before I try anything myself, just in case there is still some warranty active.... But any ideas would be greatly appreciated.
sinajei said:
Hi there!
I was wondering if anyone around here had some ideas on what to do.
My LG G4 had been working fine until today. I unlocked the screen to check my e-mail and it completely froze. It was plugged in at the time, so I unplugged it to see if I could restart it. The charging light was still blinking, the power button didn't respond, absolutely nothing.
I took the battery out, left it for a minute or so and rebooted. It loaded, unlocked, but I could only get to the app menu before it completely froze again. Afterwards, screen went black.
On the third try, it booted up to the LG logo and that's it. It popped up about 3 times and screen went black. No other response whatsoever. I can only try to reboot again only after taking out the battery, but it does the same thing.
I switched the battery with another one of the same model, nothing changed. Computer doesn't recognize it either.
I've looked around for a bit and I can't find anything like my case. The closest thing described is the boot loop. I'm not exactly sure that's my case, but it seems similar to a certain degree.
I got it to boot to recovery mode, but it doesn't do anything. It asks me if I'm sure I want to run it, and in the second 'yes' it freezes up completely again. Screen goes black and does absolutely nothing else.
Added note, phone upgraded to 6.0 yesterday morning. I had no issues with it until now. No app updates were running at freezing time.
I'm considering taking it to the store before I try anything myself, just in case there is still some warranty active.... But any ideas would be greatly appreciated.
Click to expand...
Click to collapse
seems like infamous bootloop... harware issue. send it to tmobile or LG.
raptorddd said:
seems like infamous bootloop... harware issue. send it to tmobile or LG.
Click to expand...
Click to collapse
I was afraid so... Went directly to the T-Mobile store where I bought it and, since the warranty was still active, they exchanged it on the spot.
I just hope this one lasts longer than the other one did...
Thanks!
sinajei said:
I was afraid so... Went directly to the T-Mobile store where I bought it and, since the warranty was still active, they exchanged it on the spot.
I just hope this one lasts longer than the other one did...
Thanks!
Click to expand...
Click to collapse
yeah.. did you know manufacture date on the one affected by bootloop or first 3 serial number.?
raptorddd said:
yeah.. did you know manufacture date on the one affected by bootloop or first 3 serial number.?
Click to expand...
Click to collapse
Yup. Actually still have the box.... the date was 05/2015.
New one's date is 03/2016.
sinajei said:
Yup. Actually still have the box.... the date was 05/2015.
New one's date is 03/2016.
Click to expand...
Click to collapse
it was a 505.. most will bootloop... new one is. 603. theres hw 1,0 and 1.1.. this you look at software info ... in hidden menu.. in dialer..
raptorddd said:
it was a 505.. most will bootloop... new one is. 603. theres hw 1,0 and 1.1.. this you look at software info ... in hidden menu.. in dialer..
Click to expand...
Click to collapse
This one (603) is a HW Version 1.0 ...
sinajei said:
This one (603) is a HW Version 1.0 ...
Click to expand...
Click to collapse
mines its 601 and same HW 1.0 if they knew they revised 1.0 to 1.1 why not use the 1.1 if they knew this back in october 2015.. theres older phone from 2015 with HW 1.1
raptorddd said:
mines its 601 and same HW 1.0 if they knew they revised 1.0 to 1.1 why not use the 1.1 if they knew this back in october 2015.. theres older phone from 2015 with HW 1.1
Click to expand...
Click to collapse
That is an excellent question...
Btw, does your screen freeze up sometimes? 'Cause mine sometimes goes unresponsive right after I unlock it... I just lock and unlock it again and keeps working just fine, but it's kind of annoying... old one did it and it, now this one does it sometimes too...
sinajei said:
That is an excellent question...
Btw, does your screen freeze up sometimes? 'Cause mine sometimes goes unresponsive right after I unlock it... I just lock and unlock it again and keeps working just fine, but it's kind of annoying... old one did it and it, now this one does it sometimes too...
Click to expand...
Click to collapse
yes it does.. but very rare... not to often... but mines does using phone and it freezes then turn off screen and when back it all works... i used power button.. not sure why but it does..but liek i said not to often. its once in a while..
raptorddd said:
yes it does.. but very rare... not to often... but mines does using phone and it freezes then turn off screen and when back it all works... i used power button.. not sure why but it does..but liek i said not to often. its once in a while..
Click to expand...
Click to collapse
Good to know it's not just me then. Guess it's a common screen glitch then.
Thank you for the info!
Well another 505 g4 bites the dust. Playing a game, backed out of it, phone froze, pulled battery, turned on to endless bootloop, pulled battery again, now nothing and I mean nothing, no boot loop, no nothing
Definitely a brick. Computer doesn't recognize or even try to charge it. Hopefully still under warranty.
Sent from my LG-VS980 using Tapatalk