Related
Hi,
after the upgrade from 1.9.1 to 2.0.0 my DellStreak permanently reboots by itself. I have it on homescreen in standby and 10 minutes later it reboots. Or i write a sms and it reboots. I think every 30 minutes it reboots.
And this is very horrible :/
I flashed it via ClockModRecovery and flasht the new DSP, too via fastboot.
Only baseband i dont flash, but this doesn't matter I think.
Can someone help me.
Did you try a factory reset. I've been reading a lot on the forums about people having random reboot issues, but I have not had one. Be sure that you do the factory reset from the first menu, dells four option menu. Its option number 1. Your phone will immediately reboot after the reset when it does hold down the volume up and down buttons and do the factory reset again for good measure. I always do this and never have reboot problems. Hope that helps.
Sent from my Dell Streak using XDA Premium App
Thank you I will try it now, and repost if problems are solved or still appears.
Yeah. Factory reset, then put the new baseband and amss. Then put streakdroid. In fact, run qdltool first, then do all that, so you'll at least be back to a fresh setup.
Hi ok I think it works fine. I only Hardreset via ClockModRec. And this every Time But ok it works so fine
But baseband is still offline in thread. So I cannot update this, but now it still works fine.
Hi,
My phone started behaving strangely (random but very frequent restarts). Here is what I have done so far:
- Bought new battery - charged externally as well
- Tried separate sim cards
- Formatted the SD card
- Using Flashtool v0.9
- Flashed stock and numerous other ROMs
- Unlocked the boot loader / root the phone
- I did remove userdata and cache when flashing
However neither the upgrade to 2.3.3 nor the downgrade using the Sony ericsson suite helped. Now I have the android v2.3.4 from http://forum.xda-developers.com/showthread.php?t=1516960.
The frequency of reboots and shutdowns has definitely reduced but it still occurs rather often and sometimes even before you get to the home screen.
Please suggest what else can I do about it now.
regards
Ali
My phone also started to make me the same problem he's stuck for a few seconds and then do a restart
It happens several times a day
Hope someone will help us :/
How much free RAM and internal memory do you have?
Sent from my X10i using xda app-developers app
Same here stock rom and everything lots of free ram (around 80MB most of the time) the problem comes when i start to use it to start the browser or upload a photo or if i want to play a game.... i think i saw a similar thread in the forum but it ended in the advice to flash z kernel and it didn't work at lest for me
X10-Sucks said:
Hi,
My phone started behaving strangely (random but very frequent restarts). Here is what I have done so far:
- Bought new battery - charged externally as well
- Tried separate sim cards
- Formatted the SD card
- Using Flashtool v0.9
- Flashed stock and numerous other ROMs
- Unlocked the boot loader / root the phone
- I did remove userdata and cache when flashing
However neither the upgrade to 2.3.3 nor the downgrade using the Sony ericsson suite helped. Now I have the android v2.3.4 from http://forum.xda-developers.com/showthread.php?t=1516960.
The frequency of reboots and shutdowns has definitely reduced but it still occurs rather often and sometimes even before you get to the home screen.
Please suggest what else can I do about it now.
regards
Ali
Click to expand...
Click to collapse
Hi, this ROM from championshipwinner i've been using for a year and was great and only with v8.3 i had rebooting problems, but when you installed this ROM, did you perform a clean installation of it?
Check the installation guide from here
Check also for the discussion thread
Hope that helps
Im Argentinean first of all and I'd bought my new GS2 3 days ago on mercadolibre.com.ar (a site like ebay.com) to a guy that imports it from factory. After of almost 50 days of waiting, i did got my new mobile phone, when i got it i'd upgraded to JellyBean with the official samsung rom, and that's when the problems showed up, the top left corner come overheat turning off the device, over and over again. So after some failed testing I'd chosed to change the kernel to Siyah expecting some performance improve but it become kind of worst because when the screen blackout the device just reboot itself, but if i keep doing something on it nothing happens, just when the screen comes black.
So i guessed that it may was related to the kernel, so downloaded another official rom jelly bean, this one was a Pre-Release rom, that some time ago i'd installed on a friend's galaxy s2 and it worked fine (despite the increased battery drain). This wasn't any solution though, because it keeps rebooting when the screen comes black.
I did tested to turning on without the simcard and microsd card, with the same results.
Another fact is that if i left the music playing and turn of the screen with the power button, nothing happens, it works perfectly.
It seems that is some kind of trigger when the mobile actually suspend itself doing really nothing.
Now i dont know what to do, should i test some custome rom/kernel?? should i get the chances to use the warranty? (implies to send again the device to china i guess ¬¬)
Please help, and thanks in advance.
hackkpo said:
Im Argentinean first of all and I'd bought my new GS2 3 days ago on mercadolibre.com.ar (a site like ebay.com) to a guy that imports it from factory. After of almost 50 days of waiting, i did got my new mobile phone, when i got it i'd upgraded to JellyBean with the official samsung rom, and that's when the problems showed up, the top left corner come overheat turning off the device, over and over again. So after some failed testing I'd chosed to change the kernel to Siyah expecting some performance improve but it become kind of worst because when the screen blackout the device just reboot itself, but if i keep doing something on it nothing happens, just when the screen comes black.
So i guessed that it may was related to the kernel, so downloaded another official rom jelly bean, this one was a Pre-Release rom, that some time ago i'd installed on a friend's galaxy s2 and it worked fine (despite the increased battery drain). This wasn't any solution though, because it keeps rebooting when the screen comes black.
I did tested to turning on without the simcard and microsd card, with the same results.
Another fact is that if i left the music playing and turn of the screen with the power button, nothing happens, it works perfectly.
It seems that is some kind of trigger when the mobile actually suspend itself doing really nothing.
Now i dont know what to do, should i test some custome rom/kernel?? should i get the chances to use the warranty? (implies to send again the device to china i guess ¬¬)
Please help, and thanks in advance.
Click to expand...
Click to collapse
You should try custom rom. Try to Flash Neatrom or any stock custom rom.
Hope it solves your problem.
Sent from my iPhone using Tapatalk
Firstly, you need to verify that it's a genuine S2. Turn the phone off, take the battery out and post on here EXACTLY what you see on the sticker in the battery compartment.... Just don't post the IMEI number...
Sent from my GT-I9100 using xda app-developers app
Model: GT-I9100
SSN: -I9100GSMH
RATED: 3.7V ------- : 1000 mA
FCC ID: A3LGTI9100
MADE IN KOREA BY SAMSUNG
IMEI: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
S/N: R5XA73828F1
That's all, its seems original, right?
i'd just installed the last samsung official Rom, form nordic countrys, and it seems to work just fine. I'll keep updated if it goes wrong again. Im so happy.
EDIT: Ok so i just leave it chargin the battery and it reboot itself 3 times again and 1 time just it turned off. I didnt tried leave it without the charger because it didnt have any charge. So im in trouble again >.<
hackkpo said:
i'd just installed the last samsung official Rom, form nordic countrys, and it seems to work just fine. I'll keep updated if it goes wrong again. Im so happy.
EDIT: Ok so i just leave it chargin the battery and it reboot itself 3 times again and 1 time just it turned off. I didnt tried leave it without the charger because it didnt have any charge. So im in trouble again >.<
Click to expand...
Click to collapse
Go to recovery and do wipe data/ factory restet and wipe cache . Reboot . Phone will start working again.
Sent from my iPhone using Tapatalk
Jeetu said:
Go to recovery and do wipe data/ factory restet and wipe cache . Reboot . Phone will start working again.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Ok since that post i'd installed cyanogenmod 10.1.3 with JB 4.2.2 and it rebooted itself like 4 times and finally it keeped on like 10 minutes now.
hackkpo said:
Ok since that post i'd installed cyanogenmod 10.1.3 with JB 4.2.2 and it rebooted itself like 4 times and finally it keeped on like 10 minutes now.
Click to expand...
Click to collapse
Yes do the same what i posted above and then flash your rom again.
Sent from my iPhone using Tapatalk
Jeetu said:
Yes do the same what i posted above and then flash your rom again.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Why would i reflash again? i dont get it
hackkpo said:
Why would i reflash again? i dont get it
Click to expand...
Click to collapse
Because your phone is now in Bootloop.
Bootloops can occur pretty easily, it’s mainly caused because system files interfering with each other which causes instability and/or crashes at the boot sequence.
Think of system apps that are compiled incorrectly, permissions that are not set correctly, files from other devices and even an init.d script, everything is possible.
To find the cause of a bootloop you have to think about what you did before getting the bootloop.
Choose one of the following reasons that caused the bootloop for you and try out its solution.
– After flashing a new rom
If you flash a new (base)rom on your device it may not automatically wipe your dalvik-cache, This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
Note: by wiping “/cache” and “dalvik-cache” you make sure it’s completely deleted, some roms use /data and some use /cache for the dalvik-cache
If the problems still exists after doing that, you could try to wipe your /data partition. before you do that first make a backup of your phone (in it’s current bootlooping state)
1. Start your phone in CWM Recovery
2. Now go to “Backup & Restore”
3. Choose “backup” (it may also be called “backup to internal/external sdcard)
When that’s done you are free to wipe /data, you can achieve this by doing:
1. Now go to “Mounts & Storage”
2. Choose “Wipe /data”
3. Choose “Wipe /cache”
4. Reboot your phone
If the rom still doesn’t boot correctly it’s probably the rom which isn’t working, contact the rom creator then and try an other rom for the meanwhile.
Jeetu said:
Because your phone is now in Bootloop.
Bootloops can occur pretty easily, it’s mainly caused because system files interfering with each other which causes instability and/or crashes at the boot sequence.
Think of system apps that are compiled incorrectly, permissions that are not set correctly, files from other devices and even an init.d script, everything is possible.
To find the cause of a bootloop you have to think about what you did before getting the bootloop.
Choose one of the following reasons that caused the bootloop for you and try out its solution.
– After flashing a new rom
If you flash a new (base)rom on your device it may not automatically wipe your dalvik-cache, This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
Note: by wiping “/cache” and “dalvik-cache” you make sure it’s completely deleted, some roms use /data and some use /cache for the dalvik-cache
If the problems still exists after doing that, you could try to wipe your /data partition. before you do that first make a backup of your phone (in it’s current bootlooping state)
1. Start your phone in CWM Recovery
2. Now go to “Backup & Restore”
3. Choose “backup” (it may also be called “backup to internal/external sdcard)
When that’s done you are free to wipe /data, you can achieve this by doing:
1. Now go to “Mounts & Storage”
2. Choose “Wipe /data”
3. Choose “Wipe /cache”
4. Reboot your phone
If the rom still doesn’t boot correctly it’s probably the rom which isn’t working, contact the rom creator then and try an other rom for the meanwhile.
Click to expand...
Click to collapse
No is not, the cellphone starts normal, and while im using it nothing wear happens, but when i left it the screen goes black and the device reboot itselfs. But now im seeing that doesnt happen anymore, i dont know why.
Still with cyanogenmod rom, i connected the phone to charge the battery, and i saw a tendency of reboots and turnings off while the percentaje comes to 100% and a increasing overheat on the left-top of the phone, i suspect that the problem may be related with the amount of charge from battery and the overheating... Hardware problem?
Well... After all this time my cellphone went through the argentinean official service of samsung and the tech guy told me that he couldn't do anything on my device because he tried installing a lot of samsung official roms and the device was still malfunctioning. So he gave up on it, so i'd tooked it to another service (non official this time) and that guy told me that it may be a non official device, so he wouldnt do nothing on it, because i couldnt get the hardware that possible was malfunctioning. So here im now, with the all money spent for nothing.
My question is, what can i do to know if is or isnt an ORIGINAL samsung device? Knowing that i'll choose how to proceed. Txs!
I own a stock rom rooted note2 with Os 4.3 JB. Since few days battery is draining fastly, it is discharging when being charged but it doesn't discharge when the phone is switched off. Also, whenever I restart or power on android it starts with logo which says - " Android is upgrading.... Starting apps.... finishing boot...", this happens on every start up although android works after that but drains at very fast rate. This happened after flashing audio zip for increasing volume from this thread " http://forum.xda-developers.com/showthread.php?t=2799537 ".
Please help! ! it has imp. data, and I have to recharge it again and again, avg battery capacity of note2 stands for 8 hrs but it just drains out within 2 ~ 4hrs on light usage.
I know the android is upgrading saying means that your dalvik cache seems to get wiped and rebuilt every time you start the phone
However I don't know why that's happening have you tried to factory reset?
I know you have sent it is important dated like you said can you back that up before you do a factory reset?
Sent from my HUAWEI Y536A1 using XDA Free mobile app
nobreak1970 said:
I know the android is upgrading saying means that your dalvik cache seems to get wiped and rebuilt every time you start the phone
However I don't know why that's happening have you tried to factory reset?
I know you have sent it is important dated like you said can you back that up before you do a factory reset?
Sent from my HUAWEI Y536A1 using XDA Free mobile app
Click to expand...
Click to collapse
No, I didn't try it because it has got very imp. data and settings which I don't want to be lost. Yes, I did wipe out dalvik cache because of problem with super user which is working well right now( this fix I found on XDA). I went to recovery mode to find problem for the same I.e Android upgrading, there on clicking both reboot and shutdown ( once at a time), error poped out saying- " root possibly lost? ... no... .no... fix root (/system/xbin) etc., then after applying fix, the device rebooted and showed android upgrading ... finishing boot... then I went to root checker it said rooted and all the other root functions are working, but now battery is draining,(discharging even while charging), after switching to recovery mode and again rebooting, same root fix error repeats itself and Android is upgrading ... finishing boot .. logo is displayed. Could you please suggest any other way so that instead of doing factory reset I can revert back these errors without unrooting or factory resetting as I myself had thought of doing the same but it is not possible, even reloading rom cannot happen since I didn't save latest rom which I was supposed to do after eradicating earlier problem but now this error has occurred.
Thanks in advance.
Have you tried to download gsam or betterbatterystats to determine exactly what is causing it to die so quickly?
Sent from my SPH-L720 using XDA Free mobile app
Ok here's the fix for this(Android is upgrading...)error, it is mainly due to odex files which are created by lucky patcher so deleting these files using lucky patcher itself will surely remove this error with 50 percent success rate. Here's the fix; open lucky patcher, there in lower left section you can see Toolbox, click Toolbox button then select 4th last option i.e Remove all odex files. Thats it android will reboot on itself and vola no android is upgrading. . Even if u didn't install apps like LP just try to remove faulty odex files(for location refer to attachment).
Check out attachement for help.
:good:Hits Thanks If I helped u:good:
Hey guys! This is my first thread here, but I knew this site before. I've got an M4 Aqua E2303, Android 5.0, Build 26.1.A.2.167 (upgraded from .99 with TWRP to keep the root.).
The story : I've got this phone like 4 months ago, I was so happy etc... After it updated to 5.0 it kept restarting randomly. Total random, when it was not under using, if I use it, it does not restart itself. Sometimes the restarts occurs when it's under charging, and sometimes when I want to unlock it and use it, and sometimes total randomly, and sometimes it shuts down. For different verions the problem was different too. On 26.1.A.2.99 it was the worst, it restarded and stuck on the boot screen until reached 0% battery. On 26.1.A.2.128 It turend off the screen, but the phone was running and the LED was red (even when fully charged) and only started with the hard off button in the SD card slot.
I've got the default "Diagnostics" app, now it says that the Phone got system errors 42 times in 10 days. It was worse before (over 140). But it doesn't say why did it restart, I'm hoping for help from any of you, who had this issue and solved it, or someone who knows a better diagnostic tool that will explain what caused the system fault.
I appreciate all the helps!
Have you performed a factory reset? (It will delete all your data and apps)
rp-x1 said:
Have you performed a factory reset? (It will delete all your data and apps)
Click to expand...
Click to collapse
Yes, when the phone was new and the restarts were annoying. It fixed it for 1 day. The next day it was restarting again.
This would point to an app you've installed causing the issue. Factory reset again and install each app one by one until the restarts happen to find out which.
SteveTM said:
Hey guys! This is my first thread here, but I knew this site before. I've got an M4 Aqua E2303, Android 5.0, Build 26.1.A.2.167 (upgraded from .99 with TWRP to keep the root.).
The story : I've got this phone like 4 months ago, I was so happy etc... After it updated to 5.0 it kept restarting randomly. Total random, when it was not under using, if I use it, it does not restart itself. Sometimes the restarts occurs when it's under charging, and sometimes when I want to unlock it and use it, and sometimes total randomly, and sometimes it shuts down. For different verions the problem was different too. On 26.1.A.2.99 it was the worst, it restarded and stuck on the boot screen until reached 0% battery. On 26.1.A.2.128 It turend off the screen, but the phone was running and the LED was red (even when fully charged) and only started with the hard off button in the SD card slot.
I've got the default "Diagnostics" app, now it says that the Phone got system errors 42 times in 10 days. It was worse before (over 140). But it doesn't say why did it restart, I'm hoping for help from any of you, who had this issue and solved it, or someone who knows a better diagnostic tool that will explain what caused the system fault.
I appreciate all the helps!
Click to expand...
Click to collapse
If you used the pre-rooted zip to maintain root while updating to the latest android, this will fix your rebooting problem. Follow this guide:
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
cmstew said:
If you used the pre-rooted zip to maintain root while updating to the latest android, this will fix your rebooting problem. Follow this guide:
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
Click to expand...
Click to collapse
Will try it when I'll have time for it, thanks for the help!