Database Develop

[Q] Nexus1 rebooting loop problem

my n1 having rebooting loop problem when i use it continuosly for 5-6mins or performing some task.in airplane mode i can use it for 30-40mins but then restarts and keeps restarting until i give it 3-4min rest before starting it again.probably this happen after 2.3.3 ota updat.

Wipe data (factory reset) and try again.
If it doesn't work - use "unroot/restore" guide in Wiki, PASSIMG with FRG33 image, test it.
If still reboots - use the warranty, something's wrong with your HW.
You can also look at the logcat to see, what is the problem that causes the reboot. Looks like something's overheating.

i am Having the same problem, i have unlocked bootloader and installed the latest cyanogen rom hoping the rebooting problem would be fixed but no luck ,,the rebooting or the overheating what ever causing it persist.
i don't know what else to try??!!!
i really like the phone and don't feel like buying a new one yet. nothing on the market right now convinced me to ditch my n1.
i am just sad that the hardware life span of of the n1 is 1 year only.

yah thats is overheating causing it.because when it becomes hot it goes into restarting loop until i cool it down.still dont know exact problem though.

Jack_R1 said:
Wipe data (factory reset) and try again.
If it doesn't work - use "unroot/restore" guide in Wiki, PASSIMG with FRG33 image, test it.
If still reboots - use the warranty, something's wrong with your HW.
You can also look at the logcat to see, what is the problem that causes the reboot. Looks like something's overheating.
Click to expand...
Click to collapse
Isnt the warranty void after you've unlocked the bootloader?
kled54 said:
i am Having the same problem, i have unlocked bootloader and installed the latest cyanogen rom hoping the rebooting problem would be fixed but no luck ,,the rebooting or the overheating what ever causing it persist.
i don't know what else to try??!!!
i really like the phone and don't feel like buying a new one yet. nothing on the market right now convinced me to ditch my n1.
i am just sad that the hardware life span of of the n1 is 1 year only.
Click to expand...
Click to collapse
I had that problem when my CPU speed was over 1000. Maybe this'll help?

illuminarias said:
Isnt the warranty void after you've unlocked the bootloader?
I had that problem when my CPU speed was over 1000. Maybe this'll help?
Click to expand...
Click to collapse
I don't think it's the cpu because since 2 days ago the phone started rebooting while charging without me working on it. so now i have to turn it off before plugging the charger, or it will hang on the x for hours.
i guess it's time for me to look for a new phone..too bad, i really like the n1.

yes nothing wrong withcpu its hardware problem.i also cant recharge it while on.
i keep it in fridge then it work fine.after little heat up it goes into loop again.

I've also had the rebooting loop when I had a bad battery fwiw. Changing the battery to a new one solved the problem.

I was having the same problem when it's charging (and I use the N1 a bit) and when I use the 3G data (surfing the web, installing apps from the market, etc.)!
And it's the 3rd time that I've sent my N1 to the Tech Repair!!!
Never repaired the first 2! I hope this time will be ok... I'm waiting for my Nexus 1 to come again with me...

This seems like a big N1 defect.
I called HTC today. Out of warranty repair in the USA is 55$ to 283$ plus shipping.
Could have bought a Nexus S for the 500$ I'm spending on repairs + devices.
*************
Update 5/5/2011
HTC fixed mine even though I unlocked the bootloader. No charge. Free overnight in both directions.

this is making me so much angry.although my n1 is in canada warranty but i am now in pakistan so dont what to do?even we dont know about the exact problem.is it board or something small problem?

[Q] My G-Note is rebooting frequently !!

Hi all !!
From a few days ago, my phone is rebooting frequently by itself.
First, i thought that it was fault of new ROM i flashed, and then i've returned back to the ROM i used before, but the phone keeps rebooting randomly and frequently, i tried then some other ROMs, same thing.
After a few tries, i thought it was fault of my battery, i bought new one, result was good for first day, but after this first day of normal use without reboots, the phone reboots randomly again and frequently, so i'm now afraid, and don't know what i can do.
So, is there anything I can try to help me solve this problem ?!
Thanks in advance.

in most cases its the battery.. but you have tried a new one too.. i have seen a few similar cases and the issue is with the motherboard. have a check at Samsung Service

nokiamodeln91 said:
in most cases its the battery.. but you have tried a new one too.. i have seen a few similar cases and the issue is with the motherboard. have a check at Samsung Service
Click to expand...
Click to collapse
That's what I was afraid about. Now, I have to buy a new phone, I hope my G-Note can be fixed until the S4 comes (my next smartphone for sure).
Thanks for your reply.

did you restore aps and data? dont lol.

baz77 said:
did you restore aps and data? dont lol.
Click to expand...
Click to collapse
It reboots even if i don't restore nothing. I managed to get it works without rebooting, I'm just hoping it can keep itself working until I buy another smartphone.

same problem here,
keeps rebooting randomly,
sometimes I pick it up from desk, it reboots,
sometimes after sending a sms it reboots,
sometimes it reboots even when it's on my pocket,
so weird

Do you have an application such as JuiceDefender ? I was having regular reboot with this application.

nokiamodeln91 said:
in most cases its the battery.. but you have tried a new one too.. i have seen a few similar cases and the issue is with the motherboard. have a check at Samsung Service
Click to expand...
Click to collapse
Yeah better check at Samsung

Samsung - GT N7000
Does your system gets overheated, have you checked the temperature.....yes chances are that your motherboard is faulty.
also did you try some custom roms.... may be this forum can help you:
http://forum.xda-developers.com/showthread.php?p=39163079#post39163079
If everything failed then hardware is sure at fault.

If you dont have warrantee, go safe kernel, wipe, format and such. So no stuff is left over. Because going from one rom to another dirty can cause this

[Q] New sort of N7000 brick

At least I think this is. I have recently moved from stock to Asylum's CM10.1 but did flash a known safe kernel before any wifing occurred so I do not think this is the standard EMMC bricking.
The onset of this was gradual - phone reboobed itself a couple of times (that I noticed) but this was no huge deal for me, then a few days later the screen digitizer stopped working and I had to take the battery out - from there it degenerated fairly rapidly with more reboobs, more often returning with the digitizer not functioning and finally it is at the point where it will not boot - stuck at the loading logo.
I can reboot into recovery (CWM 6.0.3.2) but can't do a lot there - fleshing a new ROM errors out saying the package is invalid or crashes (often with a brief flickering of the screen in either case).
I can run through hg42s partition scanner - if it completes it does so without report a problem otherwise it crashes, it's about 50/50 which although it seems more reliable if mains power is connected.
If I leave the phone in CWM it will eventually reboob itself after a few minutes.
I haven't seen any magic smoke escape.
I never experienced the EMMC brick so I don't know if it was progressive as this seems to be but I get the impression it was not - and I can't rule out the same sort of problem even if the original cause is different but at the moment I am unsure about the best way to progess - I will at some point pop over to Samsung's store but ideally I'd want to get to the bottom of this with the help of the community.
So any ideas? Does this sound like a corrupt partition somewhere? Thermal sensors triggering shutdowns when they shouldn't?

interesting, try to catch the evnts in the logs, use elixer/logcat/android tuner for that.

Check the battery dude.
I had similar problesm due to bad battery.
Phone was closing itslef. And before it closesi thescreen was turning crazy
Then no boot at all....

ardicli2000 said:
Check the battery dude.
I had similar problesm due to bad battery.
Click to expand...
Click to collapse
Thanks. Did your problems occur even if the phone was on mains power? Does the battery have enough 'smart' features to affect the phone even if it is not required for powering the device?

JolyonS said:
Thanks. Did your problems occur even if the phone was on mains power? Does the battery have enough 'smart' features to affect the phone even if it is not required for powering the device?
Click to expand...
Click to collapse
I was outside when faced such a big problem. It was happening before like reboobs and stucks on logo. But after i took out the battery for 15 min I was able to boot the phone.
However, eventually, one day phone got stuck with a flickering screen and then it never booted. Tired nandroid restore. Did not help. Changed kernels etc. It was no good either. Then I changed battery. Did not work again Then made a factory reset. It worked. Using it without any problem now. But even at that time I was able to see my files in the phone via Qadb. This could be your case as well.
Try changing battery if it is older than 9 months. Make a full pit fresh Stock install.
Then Reboot. I hope t will work

JolyonS said:
At least I think this is. I have recently moved from stock to Asylum's CM10.1 but did flash a known safe kernel before any wifing occurred so I do not think this is the standard EMMC bricking.
The onset of this was gradual - phone reboobed itself a couple of times (that I noticed) but this was no huge deal for me, then a few days later the screen digitizer stopped working and I had to take the battery out - from there it degenerated fairly rapidly with more reboobs, more often returning with the digitizer not functioning and finally it is at the point where it will not boot - stuck at the loading logo.
I can reboot into recovery (CWM 6.0.3.2) but can't do a lot there - fleshing a new ROM errors out saying the package is invalid or crashes (often with a brief flickering of the screen in either case).
I can run through hg42s partition scanner - if it completes it does so without report a problem otherwise it crashes, it's about 50/50 which although it seems more reliable if mains power is connected.
If I leave the phone in CWM it will eventually reboob itself after a few minutes.
I haven't seen any magic smoke escape.
I never experienced the EMMC brick so I don't know if it was progressive as this seems to be but I get the impression it was not - and I can't rule out the same sort of problem even if the original cause is different but at the moment I am unsure about the best way to progess - I will at some point pop over to Samsung's store but ideally I'd want to get to the bottom of this with the help of the community.
So any ideas? Does this sound like a corrupt partition somewhere? Thermal sensors triggering shutdowns when they shouldn't?
Click to expand...
Click to collapse
Me too, i have some problem.

delete-

ardicli2000 said:
if it is older than 9 months.
Click to expand...
Click to collapse
Yup. This was indeed the problem - new battery in and after a few repeats of the same behaviour it kicked into life and has been fine since.
Thank heavens for replaceable batteries.

JolyonS said:
Yup. This was indeed the problem - new battery in and after a few repeats of the same behaviour it kicked into life and has been fine since.
Thank heavens for replaceable batteries.
Click to expand...
Click to collapse
Glad to hear that problem is solved

Issues upon issues upon more issues!

I may be the lucky one whose screen didn't start to peel off yet,but f*ck me this phone is starting to really piss me off.
Everything worked well after I have gone to SLiMM 1.4(way before) and as I was upgrading SLiMM versions it was slower and slower to the point where the phone is unusable!
So I thought,let's try to do a good old phone reset,reflash the ROM and go from the beginning.
I restored the apps,rebooted the phone and it was STILL painfully slow,so I resetted it again but this time restoring half the apps and half the Xposed modules I have used before.
It improved a tiny bit but nothing significant.
So I thought it is finally time to unlock the bootloader and see if there is any good AOSP ROMs,as the first one I tried was AOSP 7.1.1.
Fastest ROM I have used by far,the biggest problem,my device gets very hot from loading Messenger and jumping back to Snapchat and in AOSP 7.1.1 it would stop charging the phone because of the high temperature and this was quite a big issue.
So after using it for 2 weeks,I couldn't handle the charging thing anymore,so next best thing was Sony Concept ROM.
I install the ftf,goes well,install the recovery,install DRM fix,SuperSU and Xposed.
After rebooting I notice that Xposed didn't install properly so I jump back and flash it again,and the problem now was it would get like VERY VERY hot(you couldn't touch it) when it came to the "Android is starting" screen and of course the device started rebooting itself because it was way too hot.
So what I did was put the phone on a bag of f*cking ice to keep it cool,and it FINALLY passed that screen,only to find out a second later it returned to the bootanimation and gone into a bootloop.
Now I reflashed the ftf,but before even booting the ROM for the first time I flashed recovery,Xposed,SuperSU and the DRM fix.
It booted up fine,so I started to restore my apps and everything went well until I rebooted my device to find out it doesn't want to log in to Snapchat,the app I use very often.
So I flashed Magisk,systemless Xposed just that I can hide the root from it and disable Xposed just to log in to my account.
Even that didn't work so fine I'll try it next day.
So I decide to reboot the phone quickly and it has gone into the "Android is starting" screen and shut off in the half of the process. F*cking pissed.
I cool the phone down,boot it up,wait for it to finish and when it was close to finishing it has gone into a bootloop,and wiping cache doesn't solve it.
It is currently in a bootloop as we speak.
I really do like the phone but why is it behaving so badly? I do not know if someone had a similar experience as I did.
If anyone could give me a suggestion to make my phone stable and functional,please write a post since I need my phone to work.

Flash original android rom/kernel to the device to make device fully stock. Once it is back to stock, if problems still continue i recomend sell device and buy new one.. On my xperia, display stopped working out of blue, replaced it and my camera became blurry and vibration motor stopped working... Opened it again, fixed vibration motor, now it waits another opening to replace battery and camera lens... Disaster, but hey, device is great in hw department..

Strmy said:
Flash original android rom/kernel to the device to make device fully stock. Once it is back to stock, if problems still continue i recomend sell device and buy new one.. On my xperia, display stopped working out of blue, replaced it and my camera became blurry and vibration motor stopped working... Opened it again, fixed vibration motor, now it waits another opening to replace battery and camera lens... Disaster, but hey, device is great in hw department..
Click to expand...
Click to collapse
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.

Dinkec27 said:
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Click to expand...
Click to collapse
Jebiga mi Hrvati imamo lose srece sa mobitelima hahah
More luck next time

Dinkec27 said:
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Click to expand...
Click to collapse
internal memory is failing.

bookworth said:
internal memory is failing.
Click to expand...
Click to collapse
Awesome

bookworth said:
internal memory is failing.
Click to expand...
Click to collapse
Dinkec27 said:
Awesome
Click to expand...
Click to collapse
Exactly, I suggest the same issue. I had exactly the same problem on my Xperia T, it became slower, slower, incredibly slow after three years so I couldn't even flash anything using flashtool - it was showing many errors. Even after factory resetting the phone, it was booting and setting up for like... two hours or more, becoming VERY hot but it finally booted, still was very slow.
Two solutions - warranty or selling it.

romcio47 said:
Exactly, I suggest the same issue. I had exactly the same problem on my Xperia T, it became slower, slower, incredibly slow after three years so I couldn't even flash anything using flashtool - it was showing many errors. Even after factory resetting the phone, it was booting and setting up for like... two hours or more, becoming VERY hot but it finally booted, still was very slow.
Two solutions - warranty or selling it.
Click to expand...
Click to collapse
It just doesn't make sense to me that the internal memory could be failing just under a year...
I cannot go for warranty since I voided it with unlocking the bootloader,and selling it is not an option because I am on a contract currently and I can only sell it once it expires and then get a new phone to renew my contract.
If it is internal memory,it is a second tine in a row,before I had the Galaxy S3 and it had the same symptoms,it looks like I'm prone to internal memory failures lol

Is there a way I can test the internal memory?

T-mobile Note 4 Restart and Freeze problem gone after installing wake Lock app.

After and OTA update failed my note 4 was crashing, freezing and randomly restarting.
I tried every available troubleshoot, even installing stock firmware and changing the battery but the issue was never gone.
However after installing the wakelock power app my note 4 is working like it had never undergone any issue. But i cannot restart the phone as it does not power on easily.
What could be the culprit behind the problem which is fixed by simple installation of an app.?

I'm having the same *exact* issues. Curious to know what can be done about it

Over heating? When restarting i have to set phone in the freezer for a minute

Chupshah said:
After and OTA update failed my note 4 was crashing, freezing and randomly restarting.
I tried every available troubleshoot, even installing stock firmware and changing the battery but the issue was never gone.
However after installing the wakelock power app my note 4 is working like it had never undergone any issue. But i cannot restart the phone as it does not power on easily.
What could be the culprit behind the problem which is fixed by simple installation of an app.?
Click to expand...
Click to collapse
Holy crap i thought i was the only person with this issue, I don't know the solution but I'm slightly relieved I'm not alone. I can tell you after reflashing roms and kernels and nothing working i actually took the phone completely apart, disconnected the board and reconnected and put it back and THOUGHT i fixed the issue because it wasn't happening, for 1 day, the my issue returned. If anyone has a fix please let me know I was under the assumption it could be a board issue but now that i see others have the same problem perhaps there's a solution.

Well I can confirm for me its a hardware problem...Spacifically its the EMMC chip, I can also tell you how to find out...I found actully multiple threads here i didnt relize existed with this problem, and theres a potential solution, that would be to downgrade to ok2
You have to do this by:
Getting Odin 10.7 spacifically
Getting the pit file
Getting the OK2 stock firmware
Use odin 10.7
Check Re-Partion
Uncheck auto reboot
Load pit file you downloaded
Load Stock TAR file in AP section
Flash
Hold down vol up, vol dwn, home
Let go Vol dwn soon as screen is off
Wait and watch the spining android for 5 mins
Phone will reboot takes about 10 mins
Skip through setup go to settings and factory reset
If the problem is Fixed YAY
If not you have a hardware issue
Back everything up because you will loose it all
But yea it comes down to its a marshmallow issue or its hardware issue and both issues look the same.
---------- Post added at 12:14 PM ---------- Previous post was at 11:51 AM ----------
Same Issue 1:
https://forum.xda-developers.com/no...r-phone-issues-reboots-freezes-t3440870/page3
Same Issue 2: https://forum.xda-developers.com/note-4-tmobile/help/problems-please-help-phone-weird-sm-t3550392
How to do the downgrade:
https://forum.xda-developers.com/showpost.php?p=66879466&postcount=10
Stock ROMS
https://forum.xda-developers.com/note-4-tmobile/development/roms-10-29-2014-t2922618
More Stock Roms
https://forum.xda-developers.com/no...sy-steps-stock-odin-n910tuvu1anih-cf-t2903733
Dirict Link to OK2
http://qc2.androidfilehost.com/dl/v...12/N910TUVU2DOK2_N910TTMB2DOK2_TMB-v5.1.1.zip
Dirict Link to pit
https://1fichier.com/?izzvn6s8re
Non Dirict Link to pit (must register with sammobile)
https://www.sammobile.com/forum/showthread.php?t=29568

to majicmazo
Thanks, after flashing, seems everything is ok. not taking into account two Spontaneous rebotes

den182 said:
to majicmazo
Thanks, after flashing, seems everything is ok. not taking into account two Spontaneous rebotes
Click to expand...
Click to collapse
I might be a little concerned still about the reboots if you're back on pre mm stock and they are still happening but if it works great! If i helped you it would help me to hit the thanks button, you can also h8t it on all the original posts i listed above to help the people that led me here. I changed my board since i did i have had 0 issues.

majicmazo said:
I might be a little concerned still about the reboots if you're back on pre mm stock and they are still happening but if it works great! If i helped you it would help me to hit the thanks button, you can also h8t it on all the original posts i listed above to help the people that led me here. I changed my board since i did i have had 0 issues.
Click to expand...
Click to collapse
So need to change the whole motherboard or just a chip on it? So weird, cause it begin to happen as soon as the update came.
Please let me know did I need to do factory reset before the flashing? or after is enough?

den182 said:
So need to change the whole motherboard or just a chip on it? So weird, cause it begin to happen as soon as the update came.
Please let me know did I need to do factory reset before the flashing? or after is enough?
Click to expand...
Click to collapse
I changed the board because its much easier to do the chip is soldered on to the board. If you have experience soldering you can change the emmmc chip

I am having the same problem however, I'm not sure if it's the hardware.
I triple boot. Three systems as you can see by my sig.
The only time I have random reboots is when I am on Note7 TWiz. Using the AOSP roms there is never a problem.
It might be xposed Greenify with amplify. I am going through a process of elimination
Just my two cents

I noticed 2 or 3 white horizontal lines the moment display is shutting down before the random reboot. (just half a sec appearance)
Everybody have that?

I might have found a way to diagnose whether it's hardware or software
I am having random reboots as well, and partial wakelock fixes it. I think some people get random reboots because of software problems and some people have damaged hardware. I used AndroBench to check the speed of the NAND and it is much lower than when I didn't have random reboots (sequential read/write of 41.34/33.57 vs 207.51/95.42)
That leads me to believe my phone has motherboard damage.
Could you guys download AndroBench and post your results? Maybe we can figure out who's got hardware damage and who's got software bugs causing their phones to random reboot.

marlospain said:
I am having random reboots as well, and partial wakelock fixes it. I think some people get random reboots because of software problems and some people have damaged hardware. I used AndroBench to check the speed of the NAND and it is much lower than when I didn't have random reboots (sequential read/write of 41.34/33.57 vs 207.51/95.42)
That leads me to believe my phone has motherboard damage.
Could you guys download AndroBench and post your results? Maybe we can figure out who's got hardware damage and who's got software bugs causing their phones to random reboot.
Click to expand...
Click to collapse
Here are my results. See screenshot. Couple of days ago new update came and my phone reboots more often after that. (
Any solutions? so my problem is a software i hope.

den182 said:
Here are my results. See screenshot. Couple of days ago new update came and my phone reboots more often after that. (
Any solutions? so my problem is a software i hope.
Click to expand...
Click to collapse
Do you get any "mmc_read failed" errors while booting? If not, then it is not the problem that I'm having (my memory speeds are much slower than yours as well).
Those results are very close to what a new Note 4 would get so I don't think your memory is damaged (that would be worst case scenario - phone is slow and will reboot and freeze very frequently without partial wakelock).
Since it's probably a software issue you can look for rogue apps or as a last resort, factory reset.
Also, if anyone is reading this that has "mmc_read failed" could you please try and get AndroBench results? I suspect all of the phones with the MMC problem will get abnormally low numbers like my phone.

marlospain said:
Do you get any "mmc_read failed" errors while booting? If not, then it is not the problem that I'm having (my memory speeds are much slower than yours as well).
Those results are very close to what a new Note 4 would get so I don't think your memory is damaged (that would be worst case scenario - phone is slow and will reboot and freeze very frequently without partial wakelock).
Since it's probably a software issue you can look for rogue apps or as a last resort,es factory ret.
Also, if anyone is reading this that has "mmc_read failed" could you please try and get AndroBench results? I suspect all of the phones with the MMC problem will get abnormally low numbers like my phone.
Click to expand...
Click to collapse
Try to do factory reset your reading/writing numbers should be higher! My story is when I updated via WIFI in Jan, phone started to rebooting from time to time, and was overheated. also when I tried to check for new updates I get messages that I have modify the firmware somehow that I cannot get official updates anymore. But I didn;t do anything. So i reflashed again to the new official. I helped but no I have same random freezing and rebooting. But no it happens quite rarely. After last update that was couple of days ago rebootig and freezing happen more often.
you can look for rogue apps
Click to expand...
Click to collapse
What do you mean under this?

SolDroid said:
I am having the same problem however, I'm not sure if it's the hardware.
I triple boot. Three systems as you can see by my sig.
The only time I have random reboots is when I am on Note7 TWiz. Using the AOSP roms there is never a problem.
It might be xposed Greenify with amplify. I am going through a process of elimination
Just my two cents
Click to expand...
Click to collapse
The way i personally determined mine was a Hardwarere issue was downgrading to stock dok2 that i had before installing any roms and seeing if you still have tje issue. Plus i was getting Emmc errors in download mode.

majicmazo said:
The way i personally determined mine was a Hardwarere issue was downgrading to stock dok2 that i had before installing any roms and seeing if you still have tje issue. Plus i was getting Emmc errors in download mode.
Click to expand...
Click to collapse
I get you.
In my case it was the Power Nap . I uninstalled it and everything is fine

SolDroid said:
I get you.
In my case it was the Power Nap . I uninstalled it and everything is fine
Click to expand...
Click to collapse
Power Nap Was the app you installed manually? And that was the case of rebooting?
AND
Does anybody know may I flash same pit file with the newer firmwares i download with SamFirm. Usually that's one file firmware.

den182 said:
Power Nap Was the app you installed manually? And that was the case of rebooting?
AND
Does anybody know may I flash same pit file with the newer firmwares i download with SamFirm. Usually that's one file firmware.
Click to expand...
Click to collapse
Yes
I have amplify and greenify and had Power Nap
Uninstalled Power Nap (Xposed) and everything is fine
I'm on the Red Dragon Rom for 910t