Quasi bootloop - Atrix 4G Q&A, Help & Troubleshooting

I have 2 phones.
1 old.
1 new.
I nandroided the old(nuetrino rom) and installed on the new.
Turned on the new and it all worked.
Rebooted the new and it all worked.
For whatever reason i changed roms, then reinstalled the original nandroid on the new. and bootloop. after I tried ~80times to reboot it worked. Then when I rebooted it bootlooped again. ~80 tries more it worked. Now I think this might sound crazy but the only times it turns on is when the battery is at 100%?
I just charged the battery to 100% and tried again and it worked.
Could this be possible? If so what should I do? Otherwise if not so why is it boot looping ~80 times then working!! What problems could arrise from nandroiding one phone to the other. I noticed the android ID's are the same, and also the hostnames are the same? could this be causing a problem during the init scripts? would changing this help?
Or is this a problem with the new phone?
The bootloop occurs after finishing the bootlogo and right before you normally go to the phones "desktop"
Also if I nandroid a copy of CM10.1 from the old phone to the new it never bootloops. But if I manually try to install Neutrino.zip via CWM it does bootloop.

Ok battery at 100% wasnt the solution.. but i still think this is related to battery?
Also I see ro.bootloader=unknown
Is that normal for the bootloader to be unknown?

leathan said:
Ok battery at 100% wasnt the solution.. but i still think this is related to battery?
Also I see ro.bootloader=unknown
Is that normal for the bootloader to be unknown?
Click to expand...
Click to collapse
I just switched roms since having to reboot 80 times to get things working was annoying, but ill leave this thread open in the hopes someone knows what was happening.
I cant seem to get nuetrino rom working without the bootloops on my new phone, it had nothing to do with the nandroid. every other nandroid from my old phone works except nandroids of nuetrino rom.
EDIT: If a mod sees this feel free to delete this thread. The problem magically went away, well I don't know what happened. I just waited a few days then tried the same steps again and it appears to be working now with the same nandroid. Sorry to anyones time who I waisted.

Related

[Q]

i bought a phone off ebay in december. the phone was working well and then i decided to start installing different Roms on my phone. the phone was not s-off when i was installing these roms. about two weeks ago my phone just started to restart. it does not stay on for more than a minute before it restarts and i have no idea why it is happening. i would really appreciate any help in this matter because it is really frustrating. i think it is a software problem because the phone does not restart when it is in recovery mode or if it is in bootloader mode. if there is anything...anything at all you can do to help me it would be greatly appreciated.
hvagrantz said:
i bought a phone off ebay in december. the phone was working well and then i decided to start installing different Roms on my phone. the phone was not s-off when i was installing these roms. about two weeks ago my phone just started to restart. it does not stay on for more than a minute before it restarts and i have no idea why it is happening. i would really appreciate any help in this matter because it is really frustrating. i think it is a software problem because the phone does not restart when it is in recovery mode or if it is in bootloader mode. if there is anything...anything at all you can do to help me it would be greatly appreciated.
Click to expand...
Click to collapse
It would nice if you put a title to your thread instead of just [Q].
Anyway, if you suspect its a software problem, why not just flash back to stock and see if it persists? If the problem is still there, then it's most likely a hardware issue. I would replace the battery first.
Sorry about that .. it was the first time i posted something and wasn't really sure what to do. and i replaced the battery and the problem is still there .. i flashed and it still restarted. the weird thing is that if i'm doing something it doesn't restart. like if i'm using the phone as a hotspot it doesn't restart. but as soon as i stop it restarts. or if i'm using the camera it doesn't restart.
Did you wipe/format everything before flashing/flashing back to stock? Are you on CWM or EXT4? Some more details would be helpful.
yes i did that. i used superwipe. i am also 4EX and i S-off the device also. i tried installing the stock rom but it didnt work. it is confusing because once i am in recovery the phone stays on. but as soon as i turn it on it just keeps restarting. the phone boots up and then restarts.

[Q] Yup...yet another boot loop!

OK. I have had my Atrix 4G since it first came out. I rooted it and installed apps and made customizations to it, etc.
I never installed a custom ROM since the tweaks I made fit my taste enough to not need to install a custom ROM. I have thought of it...but that is for another time.
Anyways, I recently changed fonts on using FontChanger and everything was working fine. However, last night I decided to change to another font and after rebooting my phone, I am now stuck in the ever so pleasant "Boot Loop".
I have tried wiping and restoring back to factory defaults, which appeared to work, but once I start going thru the process of setting up the phone and getting to the "home" page, the phone will suddenly automatically reboot and start to loop again. I can perform a reset which allows me to go thru the setup process again, but it suddenly reboots again after a few minutes.
I am guessing that perhaps the font is still causing problems, but I am not sure how to check to see if that is the case or not.
I have looked at other boot loop threads but I keep getting a bit confused as to what I should attempt or not attempt to do. It seemed to me that loading the 1.2.6 SBF might be my answer, but I have read that I could brick my phone doing that. Not to mention that some of the download links are dead....
Sorry for being yet another numbnutz and the long thread, but I would greatly appreciate some guidance on how to recover!
Thanks!
Ok... So after resetting my phone a few times I noticed that it goes into the boot loop cycle once the screen shuts off/or goes into sleep mode. If I keep the system from going to sleep everything appears to work fine.
My guess is still a font issue, but I thought a factory reset would've replaced the font back to default.
Anyone experience this issue or something similar to it?
And as a second thought can someone link me to the default fonts that I can try to reload?
UPDATE: well it looks like i am good to go again. It just occured to me that I can just download and use FontChanger to replace the bad font with the stock font. i let me phone go to standby mode and it didnt boot loop.
MODERATOR - Please feel free to close this thread as I believe I solved my own problem.

Again with bootloop problems, this time with CWM

Well, my problems with recoveries are sorta of a jokle by now, but I still feel compeled to share my experiences so maybe anyone can tell me what the hell is happening on my phone....
So as I said some time ago, I experienced problems with the PhilZ recovery, which I solved swapping to CWM version 6.0.3.2. The problem was the infinite bootloop of the Samsung Galaxy GT-I9300 logo, the black screen, which did not allow me to access to the recovery. But inmediatly after flashing to the old CWM the problem was gone away. Also, in a case of a possible kernel panic due to doing some stuff with Xposed modules CWM was the only recovery I could get access into.
Now, the problem is the following. Yesterday I installed the CWM Touch version 6.0.4.7, which I got from this thread http://forum.xda-developers.com/showthread.php?t=2052091. After installing it everything was normal. However, after one hour or so the phone screen wouldnt turn off when I pressed the Power Button. In fact the Power Menu appeared, but the screen, as I said, dindt get to sleep mode. To top that, after freezing for a second the phone suddenly turned off, and then get to the infamous black screen with the model logo looping and looping.
Fortunately, after pressing Volume Up+Menu+Power I could get to the Recovery, but not after quite some seconds pressing these three buttons. And in some times it would not get me to the recovery, but instead completely rebooting the phone and working again. Just to, in half an hour, freezing and looping again and again and again.
This problem happened to me with virtually every ROM I installed, being Neat ROM, Archi, and even CM11 from Temasek. Nothing would solve that problem. The only remedy I had was a temporary one, which consisted on uninstalling and reinstalling again the kernel (I used boeffla) and the problem would not disappear that way. Also, when wiping data, for some weird reason it gave an error message while wiping the /preload partition, in the Mounts and Storage menu.
Until I got home today, and then flashed through Odin the old CWM Touch version 6.0.3.2, that finally stopped the problems. I tested it by pressing the Power buton again and again and it hadnt redirected me to the black bootloop screen. Seriously, I am wakelocking my phone on an intensive basis and nothing has happened for now, and I think it probably wont happen again. Maybe it takes three seconds, maybe the Power Menu displays again, but no bootloop again.
So I ask to you, what is happening on my phone that it wont run recoveries younger than my old 6.0.3.2
IMPORTANT EDIT: THE PROBLEMS ARE NOT SOLVED YET
Some hours ago, I was chatting using Whatsapp while charging the phone on an USB charger, when it suddenly suffered the black screen bootloop again. This time was unexpected, since I was using the CWM Touch 6.0.3.2, the one supposed to work fine. So for now I feel completely finished. My phone is officialy into a unsolvable problem.
But, thinking about it, there were some things that might help you:
-This time I did not uninstall and reflash the kernel: When I got to the recovery menu, I just selected "reboot", as such, without flashing anything else, and the phone then worked as fine, booting into the ROM bootanimation screen (this time the Neat ROM bootanimation). So basically a manual reboot through Recovery got me out of this. Also, I kept using the phone until now and there werent more problems, at least for now.
-As far as I can recall, these problems started some weeks ago, when I accidentally formated the internal SDcard. I was using PhilZ Touch Recovery and flashing a ROM as usual, when I selected without knowledge the option "Format /data and /data/media (sdcard)" in the Mounts and Storage menu. I did this after doing the usual Full Wipe before flashing an new ROM, and after that I had to turn off the phone in order to insert a ROM in the external SD card to flash it through the recovery to make the phone working again. But when I wanted to get back to the recovery, I couldnt. I had to flash CWM 6.0.3.2 because it was the only recovery that let me access to the recovery menu-the already installed PhilZ wont allow me to access to the recovery menu. So in CWM I got to the External SD card and flashed a Neat ROM, and got the phone working again. And after that I reflashed PhilZ. But since then the phone started to experiment these freezes, reboots and bootloops. One happened to me when in College, and couldnt get out of it because PhilZ wont respond to the Manual Recovery command. I had to wait to get home, to reflash the CWM 6.0.3.2 recovery through Odin because that Recovery was the only responding. And in that moment it did well, and didnt have more reboot problems. Until I flashed 6.0.4.7, which is why I am here.
-Lastly, about the reason I trust in CWM 6.0.3.2: Some time ago, when flashing Blackbox ROM 2.0.2, I downloaded the Gravity Box module from Xposed, and installed it alongside with other modules, which, supposedly, caused a kernel panic problem that sent my phone into the dreaded black bootloop again. I was using PhilZ recovery, and as you may expect now, I couldnt get access to it, so I flashed the CWM 6.0.3.2 recovery, which let me access to a recovery. I too flashed TWRP, but it accessed for one second to the recovery menu, and then faded away, returning to the bootloop logo screen. So basically PhilZ and TWRP failed me during that kernel panic problem, while CWM stood the problem. And thats why I turn to this recovery when everything else fails.
And thats why I am troubled now, because this recovery is showing signs of failure
Try cwm 6.0.4.4 as I've used this for all sorts of Roms and have no problems
andrewwright said:
Try cwm 6.0.4.4 as I've used this for all sorts of Roms and have no problems
Click to expand...
Click to collapse
I used 6.0.4.7 and I had the problems previously described....I mean, I used a more updated version than the one you propose. Do you believe its gonna work better?
And thats why I will stick to 6.0.3.2 until someone tells me whats happening. If an updated version of 6.0.4.4 gives me problems...well, go imagine.
I can confirm that 6.0.4.4 works. I Also tested it for nandroid bk up and restore and it works. I have flashed the latest tw 4.3 and the old 4.1.2 and aokp/cm/aosp 4.4.2 and all flashes with no errors. I have 6.0.4.7 but not tested it this is why I said to you to use 6.0.4.4
Only thing I haven't tested is adb.
andrewwright said:
I can confirm that 6.0.4.4 works. I Also tested it for nandroid bk up and restore and it works. I have flashed the latest tw 4.3 and the old 4.1.2 and aokp/cm/aosp 4.4.2 and all flashes with no errors. I have 6.0.4.7 but not tested it this is why I said to you to use 6.0.4.4
Only thing I haven't tested is adb.
Click to expand...
Click to collapse
Interesting. And where do I get the 6.0.4.4? I dont see it neither in the new CWM thread nor in the old one.
Look down
here. zip so just flash in recovery
andrewwright said:
here. zip so just flash in recovery
Click to expand...
Click to collapse
I apreciate your help, but now some new problems have emerged, and I need more help, because maybe I might have a corrupted partition or such, who knows.
With this quote, I too try to bump the thread, in order to gain more attention to my new problems
If anyone is interested, please look the OP, as it has been edited to describe the new problems.
Best thing to do now is go bk to stock firmware with Odin and see if any problems persist. Totally stock for a few days.
andrewwright said:
Best thing to do now is go bk to stock firmware with Odin and see if any problems persist. Totally stock for a few days.
Click to expand...
Click to collapse
I will try that in a few weeks, I am a bit busy by now to test anything...
Fortunately, the CWM 6.0.3.2, while not infallible, works better than the other recoveries...today I only had one bootloop problem, solved by simply rebooting from the recovery....I can keep it for one week or two, it doesnt worry me for now.
Also, there is a guide to reflash stock? Sometimes I reflashed stock, but it kept bootlooping on the Samsung animation...probably because I didnt know how to wipe data while reflashing stock. Thats a little problem I have with reflashing stock, any help is appreciated.
Odin wipes the phone while flashing. What rom are you on? Custom
Well, I have to bump this post again because I am having the same problems again.
I am using CWM 6.0.3.2 as my current recovery. Today, I was browsing the Facebook app when I pressed the Power Button. Then, a lag of 2 seconds happened, the Power Menu displayed on screen, and the phone got into the black boot screen again. But this time I could not get to the recovery. Whenever I pressed Volume up+Power+Menu there appeared a black screen featuring the CWM logo and then it returned again to the black boot screen again. So what I did was to remove the battery, then eject the Exterior SD Card (A Lexar, 32 gb) and put again the battery in its place. The phone started all normal again, and when I put again the SD Card it continued to work normally.
So, what do you think its happening? Not even my old recovery, the one which works better for me, is reliable anymore. Could this be a component of my phone failing? Particulary the emmc chip? Or its not a hardware problem? Should I sent the phone to reparation?
How much data do you have on ext sd? Maybe phone is scanning ext sd and if alot of data is there that maybe the cause of the reboots. Try a different sd for a few days or none at all. See if you have the problem.
andrewwright said:
How much data do you have on ext sd? Maybe phone is scanning ext sd and if alot of data is there that maybe the cause of the reboots. Try a different sd for a few days or none at all. See if you have the problem.
Click to expand...
Click to collapse
I have almost 29 gb on the sd, but I had that data since the very first day I bought the card....thats more than one year ago. And I started having the problems since february of this year....
The problem has not reappeared. But what I still have is an insane battery consumption. See, I use apps like Facebook and Twitter, but I too use Greenify to hibernate them. It even drains too much battery by using the web browser. And I repeat, those problems trace back to February...which is the month when I accidentaly formatted the internal SD Card...
One year old + battery using Facebook and twitter and all the rest of them very power hungry apps are no good for battery life. Greenify uses battery, people forget that too. Remove all the apps above and test. Also if anything formatting int SD will speed up the phone not slow it down. It get rid if all the bit left over from ROMs/Recovery's/kernel's. Formatting int sd is good for the phone once in a while. Just remember to back up data first
andrewwright said:
One year old + battery using Facebook and twitter and all the rest of them very power hungry apps are no good for battery life. Greenify uses battery, people forget that too. Remove all the apps above and test. Also if anything formatting int SD will speed up the phone not slow it down. It get rid if all the bit left over from ROMs/Recovery's/kernel's. Formatting int sd is good for the phone once in a while. Just remember to back up data first
Click to expand...
Click to collapse
Thanks! Whenever I can, I will try those tips for battery saving.
But what still puzzles me is the "Sudden reboot problem". It vaguely happens, but when it does I am basically screwed, and each time the reboots seems to get worse from recovering....Also, the reboot problems started after formatting the int sd card for first time. And, after that, I remember that, when I wiped data for installing a new ROM, it gave me "(E: unknown volume for path [/sd-ext])" or, something similar. Does this help you for identifying my problem?
OK, now I am royally screwed
I have suffered another sudden bootloop problem, and this time, even by removing the ext SD Card, phone doesnt restarts. Also, I cant access to the Recovery Menu. It does appear for a while and then fades away. But the worst part is that I cannot get into the Download Menu. When I get to the select screen, when I cant choose between Continue and Cancel, the Volume buttons doesnt work. I can not get into Continue button. And then it restarts.
So this time I can not even access to the Download Menu.
I am using the same ROM as before: Neat ROM 6.7 with CWM Touch 6.0.3.2 and Boeffla Kernel
I dont know if I can even send the phone to repair, as seen that I may have the Binary Counter...and I cant even access to Download.
Please, really, help me to get out of this, so I can factory reset this.
Take the battery out then hold buttons for download mode and while holding these buttons put the battery back in and pray mate. Not being able to get into download/recovery mode as you know is really not good. Maybe a jig to force it to download mode.
andrewwright said:
Take the battery out then hold buttons for download mode and while holding these buttons put the battery back in and pray mate. Not being able to get into download/recovery mode as you know is really not good. Maybe a jig to force it to download mode.
Click to expand...
Click to collapse
I did that, and I got into the Download Menu. But the menu was frozen as usual. I could not access to the Odin Menu. It didnt matter which option I chosed, since both of them didnt work and the menu would still be frozen, and then restarting the phone a few seconds later. I mean, I got to the screen where you can choose to get to Download Mode or to restart the phone, and it still was a stuck screen, no matter what I chose, the options did not work, and then the phone restarted again.
And I have no jig next to me. So, I am screwed. For real.
Im going to take it to the store where I bought it, which is near where I live...To see if they can do something. Otherwise...I think I will throw away this phone. Its been almost 2 years, and recently it started to fail, probably because of a crappy emmc chip...that store sells the Moto G, which is great, since I dont plan to waste a lot of money on a new phone, watching how this has ended.
And it sucks that I can not recover the data in the Internal SD

Boot loop i think?

Hey guys,
So my problem started 2 days ago.I had lollipop from the archi weekly and the last update i suddenly got random reboots and later that day it started with a constant boot loop and if i get lucky i can start my phone for a minute and then again the same thing.So i had problems with going to recovery/download mode even there i got boot loops.However,i took another battery from a friend of mine and i managed to get in recovery and delete dalvik/cache.But didnt work.So i read and realized i had to install stock rom and i did now i am with jelly bean and even now i sometimes get boot loops and after a while everything is fine.So i have a coupe of questions:
1.Is it possible that the problem might come from the battery?
2.Even now with this rom my sim card is not working,i cant call anyone how can i fix it?
3.How to fix everything ?
Thank you.
Edit: i did also a factory reset.
1. A broken battery max causes random boots. A broken power-button too. Test it with your friend's battery.
2. You probably lost your IMEI.
when i write *#06# i have IMEI number so i guess this means i havent lost it?
Compare with IMEI on label behind battery. If it's the same, you win.
well is not the same so i dont win what does it mean?
It means, it's a factory-IMEI: worthless.
Perhaps this helps.

Bootloop remains even after Stock flash in ODIN

Hello guys, I have a serious predicament that needs to be solved.
I haven't did anything major to my phone in years so the past couple days have been a nightmare. Ever since I did a wipe of cache partition after trying to get rid of this "unfortunately, contacts stopped working." message, it's sent my phone into a spiraling disaster. (I have been using stock 5.0 rooted rom for at least a year so idk why the sudden issues)
I've literally tried every method imaginable. I even tried flashing with different versions of Odin and still the exact same problems.
I can get my phone into DL mode easily but Recovery mode only works if I have the phone plugged in at this point (Actually, it seems like the only time when my phone wants to work)
Every time I'm done flashing, it'll load all the way up to the T-Mobile screen then restart the loop all over again :/
Really need help seeing as I need to get this situation handled before work today, thanks!
Nevermind, after more research, I decided to order a new battery and the problem is solved.
Bootloop solved with replacement battery
gkenga said:
Nevermind, after more research, I decided to order a new battery and the problem is solved.
Click to expand...
Click to collapse
A replacement battery also solved my boot loop issue. Prior to replacement, it would boot to Galaxy S5 screen, and then reboot. Replaced battery and boots. Put the old battery back in, and it boot looped.

Categories

Resources