And now I'm boot looping won't go past n color startup animation wth
Sent from my Cyanogen Mod EVO using Tapatalk
I had that problem on my NC when it was rooted. Luckily I had another problem that let me get out by the 8 times reset manual method. Mine would occasionally update itself back to version 1.0.0. When it did that I managed to reset it & now a new NC is on its way to replace this one.
This probably won't help solve the issue but at least it lets you know you're not alone.
Mine boot looped and I did the full 8X reboot thing and then the 3 button data reset. All of that puts you back to "out-of-the-box" stock. You can then redo the autonooter rooting procedure.
Can't get out
I am stuck in a boot loop and cant get out.
First it was stuck on the droid boot animation from the auto config. After I put the autonooter card back in it started looping the rooted boot animation.
Did the 3 button thing and that forced an update but went back to bootlooping the rooted animation.
Then did the 8X reboots manually and that also forced the down arrow update, but then it still bootloops.
I tried getting in from PuTTy (as admin) but it never connects. Do I just use port 22? (to 192.168.2.2 with Data and username as root?)
adb doesn't work... going to bed now and will try again tomorrow after work.
What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App
Bigger Issues.... First Brick?
Nate731 said:
What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
So ... I left my Nook in what I thought was an "OFF" state last night, only to bring it to work and find it says "Battery too low to Power on" "Please wait 15 minutes and try again"
I think... no worries... plug it in and let 'er sit for an hour.... an hour passes and I'm still getting the same screen.
Is this better or worse? let me see...
1) if it stays like this, I can return/exchange it at B&N and they won't be able to verify that it was rooted due to non-bootiness
2) If it eventually boots, I will have to try to get it out of bootloop.
3) If it comes to life and I can't get it out of bootloop, I will drain the battery again and go back to #1.
Any thoughts besides this current train?
sort of working?
OK....
so after charging on USB port (all I have at work today as I forgot the base to the charger), it will bootloop again... yay!
problem is... the bootloops take too much juice and won't allow me to fail 8 reboots. I can't even charge it up enough since I'm on USB charging and it keeps trying to turn itself on.
2 Options i see:
1) Go home and charge it on the wall and see if that helps
2) Discharge it to death and return within my 30 days (X-mas gift)
Doubt this will work, but have you tried putting in an autonooter sdcard and then plug it into the usb? If it tries to boot maybe it will boot from that sdcard?
Boot from the Froyo SD card, then fix /rom/devconf/BootCnt from ADB.
Cal you never mentioned if you cleared the user data... Did you?
Nate731 said:
Cal you never mentioned if you cleared the user data... Did you?
Click to expand...
Click to collapse
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)
cal3thousand said:
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)
Click to expand...
Click to collapse
Try Geezer's tip but do this:
Do three button reset WITH the autonooter card in there.
Got it working
Finally got it working after creating a Nookie Froyo card and booting off of that.
Then I reinstalled ADB on my work computer and reset the BootCnt file to 8...
that successfully restored /system and then the 3 finger trick actually gave an option to wipe.
Now to start over.
New Question: How likely is this hardware related and should I be looking to replace it before my 30 days is up>?
I ran into the same problem, trying the same solution - any luck the second time?
JasonBunting said:
I ran into the same problem, trying the same solution - any luck the second time?
Click to expand...
Click to collapse
My Nook has been great since the fix. But I also needed to use a program to turn off Wifi when I turn the display off.
I did it all from my Nookie...
confused?!
I was wondering how you fixed this..i have read everywhere, but nothing...im stuck in the nook co screen. This happened right after i plugged my nook to charge after my battery was drained...thnks
Related
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
Alright I am stuck. I've spent three days searching all the forums I can find, trying everything I find, and none of it has worked.
I was running the Decrap ROM on my phone no problem up until the OTA update started coming through. It failed the couple of times it tried to install. Then the Revolt ROM 1.0 came out. Made a backup, and flashed that one over the Decrap ROM, no problems. Revolt 1.1 is released, I flashed back to stock, then flashed 1.1 over it. It was running fine for a few days, except for two FC on the phone. Then I got a call from my girlfriend, tried to answer it, and the phone FC but was still ringing. I tried opening the dialer to call back, and it kept force closing. I rebooted the phone, and my real problems started.
The phone now goes through this process...Vibrate > LG splash screen > blank screen > Vibrate > LG splash screen > blank > repeat.
The only way to make it stop is taking the battery out. Every time I plug it into the wall or computer (with or without a battery) the process starts automatically. I cannot get into any sort of recovery no matter how long I hold the volume and power keys. I tried taking the battery out, SIM card, and SD card. I plugged it into the wall with and without a battery, let it charge overnight, no luck. I tried the SDK method with fast boot but I cannot get my computer to recognize the device because it keeps trying to restart itself.
The only thing I have not tried is the LGNPST method because I read of problems people were having even after recovering their phone, and I figured that if the SDK method would not work because my computer did not recognize the device neither would this.
Does anyone have any other suggestions? Or am I going to have to bite the bullet and pay for a replacement?
Thanks!
Sent you a pm
Sent from my VS910 4G using XDA Premium App
I have not had the exact problem you do, I can get the phone to charge. But I have also had repeated problems with not being able to boot my Revolution. This has happened consistently no matter which ROM I've used. I've factory reset and tried Decrap and Revolt both. I can reboot my phone fine, but if I ever turn it off overnight, I go back to a blank screen after boot in the morning.
It seems a number of non-root users have this problem. You might be able to go in for a replacement, see:
https://www.youtube.com/watch?v=IOGM__SQB6Y
I'm not sure if having a low battery contributes to the problem, but I do know that Clockwork works better with a full battery.
Have you tried plugging it in without the SIM and SD card?
Charging without Battery
http://forum.xda-developers.com/showthread.php?t=1211935&highlight=can't+boot+to+clockwork
Well, this morning, I ended up in exactly your positions, despite having a full battery.
I tried the suggestion of plugging the phone in without the battery and letting the bottom lights flash on and off about five times. Then I put the battery back in and it booted to the charger.
still can't get to Clockwork though, if you find a solution, please post.
Update: I ended up getting back to Clockwork. Can't say exactly what did it, but what seemed to work was:
1. Charging the battery fully overnight
2. Removing the battery and holding the power button down for 30 seconds
3. Leaving the battery out for some time, about an hour I guess
4. With the battery still removed, plugging the phone in and allowing the bottom lights to flash about 10 times
5. Replacing the battery, holding down the power button and volume down.
After a full day of not being able to get into Clockwork, I was able to get in and do a factory reset.
Returning Revolution to Verizon
FYI, I took my rooted, non bootable phone into a Verizon store, and they ordered a replacement. Didn't try anything special and they didn't ask about or look for rooting on the phone.
I am having a similar but not identical problem. After trying to downgrade with LGNPST, my phone just sits at the initial LG logo. Well, it comes up, then blinks and vibrates and then comes back. It will sit there forever. I have been unable to get the hard reset menu to come up.
The phone is detected under Windows, but it tries to install a new device driver "LGE CDMA USB MODEM" for which I do not have drivers for. It does not show up as a device in LGNPST.
Any ideas?
nesterbation said:
I am having a similar but not identical problem. After trying to downgrade with LGNPST, my phone just sits at the initial LG logo. Well, it comes up, then blinks and vibrates and then comes back. It will sit there forever. I have been unable to get the hard reset menu to come up.
The phone is detected under Windows, but it tries to install a new device driver "LGE CDMA USB MODEM" for which I do not have drivers for. It does not show up as a device in LGNPST.
Any ideas?
Click to expand...
Click to collapse
Try pulling battery, put battery back in, press and hold volume up, press and hold power button, hold both thru the lg screen. Hopefully it will boot into a download mode that is recognized in lgnpst.
Sent from my VS910 4G using xda premium
Didn't seem to do anything different. Still prompting for those USB modem drivers.
nesterbation said:
Didn't seem to do anything different. Still prompting for those USB modem drivers.
Click to expand...
Click to collapse
You are downgrading correct? If so the drivers you downloaded from the downgrade instructions delete those. Go to LGs website download those drivers and then retry again. That's what I did yesterday when it wouldn't recognize my phone in the program. Let me know if it works.
I've Revolted have you?
When this happened to me I contacted Verizon about the issue. Apparently I was not the first person this had happened to. I found on a couple of other forums that non root users had the same problem. Sounds like it may be an issue with the phone in general.
Sent from my VS910 4G using xda premium
I've had a hunt around the forum and the net in general to look for solutions, but haven't come across the same issue.
The tab was running Overcome 4.10 just fine, but I decided I'd wipe everything in CWM and go for some ICS action instead. I used every wipe option.
In retrospect, I should have RTFM, but I used every wipe option in CWM.
After I did this I rebooted the tab and it went back to CWM. I decided I didn't want to do anything there and then, so I turned the tab off and came back to it later.
Hit the power button - no joy. Plugged in my charger cable and after a few seconds it came to life showing the battery charging screen, but it did not change from the first few seconds where there is a spinning/loading icon over the battery. I've left it plugged in for well over 4 hours in total now and still no joy - the battery screen comes on and goes off of it's own accord.
Now, I'm hoping I just have a dodgy charger cable and I'm going to resolder it just now while I wait for responses.
Any suggestions if that doesn't sort it out?
EDIT -
I've resoldered the cable and it's made no difference.
Also, a bit obvious, but I didn't mention that it will not go into download or recovery mode. The turning it on whilst touching the screen trick doesn't do anything either.
EDIT 2 -
I opened the tab up, disconnected the battery for a few minutes and reconnected. No difference.
adb, Kies and one-click unbrick don't see the tab. Win7 has seen the 2 sd card directories, but couldn't mount/access them. This isn't consistent, though.
Any ideas? I don't know what else I can do
Soft Bricked?My ***
I am very sorry to tell u that this thing looks like Hard Bricked
Anyway try these links
http://forum.xda-developers.com/showthread.php?t=1133590
http://forum.xda-developers.com/showthread.php?t=1127978
Thanks for your reply and the links. Unfortunately, I've tried everything in the first thread with no luck.
I think I'll practice my soldering and try AdamOutler's UnbrickableMod.
I'm curious what exactly bricked it :-/ Wiping the battery stats with no ROM in place?
Oh well
nelsonoski1972 said:
I am very sorry to tell u that this thing looks like Hard Bricked
Anyway try these links
http://forum.xda-developers.com/showthread.php?t=1133590
http://forum.xda-developers.com/showthread.php?t=1127978
Click to expand...
Click to collapse
Hmmm... this looks more like you messed up CWM. Normally, if one chooses to shut down his phone while in CWM, after reboot it gets back into CWM on auto. Try getting into CWM or download-mode by holding the buttons untill you see something happening on the screen.
If that fails, I guess you have a new goodlooking paperweight...
Any idea how CWM might have been messed up? No battery stats maybe confusing things? I find it strange that it did reboot into CWM after I wiped that stuff and then after being powered off it did not turn back on.
A mystery, but you're right - it is a very pretty paperweight
dirlan2001 said:
Hmmm... this looks more like you messed up CWM. Normally, if one chooses to shut down his phone while in CWM, after reboot it gets back into CWM on auto. Try getting into CWM or download-mode by holding the buttons untill you see something happening on the screen.
If that fails, I guess you have a new goodlooking paperweight...
Click to expand...
Click to collapse
Today my 4X encountered a strange problem: It shut down itself (I thought the battery was empty and charged it), and after restarting it just shuts down immediately. It shows the lockscreen saying "no SIM" and then shuts down. Anyone know a solution to fix this? I suppose a factory reset might do it, but I don't have a backup now and would like to keep my data.
muellersmattes said:
Today my 4X encountered a strange problem: It shut down itself (I thought the battery was empty and charged it), and after restarting it just shuts down immediately. It shows the lockscreen saying "no SIM" and then shuts down. Anyone know a solution to fix this? I suppose a factory reset might do it, but I don't have a backup now and would like to keep my data.
Click to expand...
Click to collapse
If it is the SIM then try a different SIM, or put a folded piece of paper between the holder and the SIM - I always do that with phones just to make sure it keeps good contact at all times.
Other than that, no real idea mate - sorry
I think it should also work without a SIM. But as said, it just shows the lockscreen for ~2 seconds and then shuts down. I have tried without a sim, it's the same. I'll try with a different one, but I suppose that won't help much. I think i'll also try a kdz reflash, but i'll have to set up my father's PC to do so. Just thought maybe someone knows a quick solution.
Alright, i've just done a kdz reflash - same situation. Is there a way to adb pull the /data/data from any of the other modes (recovery, Emergency etc.?)
muellersmattes said:
Alright, i've just done a kdz reflash - same situation. Is there a way to adb pull the /data/data from any of the other modes (recovery, Emergency etc.?)
Click to expand...
Click to collapse
Weird... Reflash use to replace all files and stock settings unless you have some app avoiding them to run... Reflash don't delete installed apps most part of the time. If you have frozen apps they'll remain frozen. Did you factory reset before reflash?
Sent from my LG-P880 using xda app-developers app
RuedasLocas said:
Weird... Reflash use to replace all files and stock settings unless you have some app avoiding them to run... Reflash don't delete installed apps most part of the time. If you have frozen apps they'll remain frozen. Did you factory reset before reflash?
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
No, as said i wanted to try everything before doing a factory reset (don't have a recent backup because Ubuntu won't recognize the MTP mode properly). I have restarted the phone many times before without that strange behaviour and didn't freeze anything since then. I just can't tell where the problem comes from. BTW, the SIM is recognised now (after the reflash), but still shutting down.
muellersmattes said:
No, as said i wanted to try everything before doing a factory reset (don't have a recent backup because Ubuntu won't recognize the MTP mode properly). I have restarted the phone many times before without that strange behaviour and didn't freeze anything since then. I just can't tell where the problem comes from. BTW, the SIM is recognised now (after the reflash), but still shutting down.
Click to expand...
Click to collapse
You notice some over heat, you try to use it without SD card, it keeps rebooting when charger is connected?...
Cause appart of hardware malfunction, I can't see any other reason... of course we don't know if the system file is corrupted or not...
If the phone is ON time enough, you can copy the data files/ folders to your SD card, after save them all you can factory reset...
Wait for better help cause I have no idea... sorry
RuedasLocas said:
You notice some over heat, you try to use it without SD card, it keeps rebooting when charger is connected?...
Cause appart of hardware malfunction, I can't see any other reason... of course we don't know if the system file is corrupted or not...
If the phone is ON time enough, you can copy the data files/ folders to your SD card, after save them all you can factory reset...
Wait for better help cause I have no idea... sorry
Click to expand...
Click to collapse
It's not because of heat, the phone is really cool. It just stays on for a second or so, just enough to see the lockscreen or the "Enter PIN" screen and then it shuts down. It's like the battery was empty, but it's charged. It even shows the charged battery symbol. Guess I'll have to do a factory reset and lose my data. As root is gone, I also can't boot to the bootstrap recovery (with this method) to backup there. Should have done that before doing a reflash...
muellersmattes said:
It's not because of heat, the phone is really cool. It just stays on for a second or so, just enough to see the lockscreen or the "Enter PIN" screen and then it shuts down. It's like the battery was empty, but it's charged. It even shows the charged battery symbol. Guess I'll have to do a factory reset and lose my data. As root is gone, I also can't boot to the bootstrap recovery (with this method) to backup there. Should have done that before doing a reflash...
Click to expand...
Click to collapse
You can try to downgrade before factory reset... some apps won't work but, maybe the phone just don't turn OFF and you'll be able to save your data.
So downgrading didn't work either. I'll use the LG Support Tool to upgrade and factory reset now (with data loss). That should hopefully fix it.
Well, the LG Support tool also didn't fix it. Data is lost now, so I can freely do whatever I want
I've tried to get into the "low-level mode" (http://forum.xda-developers.com/showpost.php?p=35524491&postcount=11), but no success. Can someone point me into the right direction and on how to press those buttons? I've tried several combinations, but they all didn't work out - either the battery symbol appeared or the phone booted to recovery or to the "do not touch cable notice" mode.
As far as I understand I should do the following steps:
1) Remove the battery and USB cable
2) Insert the battery and plug in the cable. The phone vibrates once, then shows the LG logo, then shows a battery symbol and then turns off the screen.
3) Press Vol+ and power and hold it. The battery logo shows again. There is a sound indicating that some device is connected to Windows. The screen turns off and there is a sound indicating that the device is disconnected from Windows. Let go off the buttons.
4) Press the buttons again until there is a sound indicating that a device is connected to Windows. Let go off the buttons. The screen should remain off.
Is this correct? What am I doing wrong? Do I have to wait at some point for some action? As said, all I ever got was the "battery symbol" again (for a few seconds).
muellersmattes said:
Well, the LG Support tool also didn't fix it. Data is lost now, so I can freely do whatever I want
I've tried to get into the "low-level mode" (http://forum.xda-developers.com/showpost.php?p=35524491&postcount=11), but no success. Can someone point me into the right direction and on how to press those buttons? I've tried several combinations, but they all didn't work out - either the battery symbol appeared or the phone booted to recovery or to the "do not touch cable notice" mode.
As far as I understand I should do the following steps:
1) Remove the battery and USB cable
2) Insert the battery and plug in the cable. The phone vibrates once, then shows the LG logo, then shows a battery symbol and then turns off the screen.
3) Press Vol+ and power and hold it. The battery logo shows again. There is a sound indicating that some device is connected to Windows. The screen turns off and there is a sound indicating that the device is disconnected from Windows. Let go off the buttons.
4) Press the buttons again until there is a sound indicating that a device is connected to Windows. Let go off the buttons. The screen should remain off.
Is this correct? What am I doing wrong? Do I have to wait at some point for some action? As said, all I ever got was the "battery symbol" again (for a few seconds).
Click to expand...
Click to collapse
Once that data is gone, just reflash the phone.
My advice, like always is, downgrade, factory reset, upgrade , root, factory reset.
hope you don't tell me that you have problems with flash method...
I have tried that. Flashed v10a, wiped data in recovery, upgraded to v10h via LG Support Tool. Still shutting down. I thought the emergency recovery might fix it but I cant get the emergency mode to work. I'll call the LG support tomorrow and hope they'll bring me a new phone.
Gesendet von meinem ASUS Transformer Pad TF300TG mit Tapatalk 2
muellersmattes said:
I have tried that. Flashed v10a, wiped data in recovery, upgraded to v10h via LG Support Tool. Still shutting down. I thought the emergency recovery might fix it but I cant get the emergency mode to work. I'll call the LG support tomorrow and hope they'll bring me a new phone.
Gesendet von meinem ASUS Transformer Pad TF300TG mit Tapatalk 2
Click to expand...
Click to collapse
If when you're flashing, you use "web upgrade" instead of normal upgrade, it will upgrade with LG Tool, official firmware, what it means that is the same than the emergency recovery that you're trying to use.
The difference is that you don't need to use IMEI. The detection is automatic.
RuedasLocas said:
If when you're flashing, you use "web upgrade" instead of normal upgrade, it will upgrade with LG Tool, official firmware, what it means that is the same than the emergency recovery that you're trying to use.
The difference is that you don't need to use IMEI. The detection is automatic.
Click to expand...
Click to collapse
Thanks, I thought the Emergency Recovery was still different. So no chance to fix this now. LG's support won't work on Christmas, so three more days stuck with it.
I got the phone back today. Put the battery in, started, and... it shut down. AGAIN. They were supposed to fix that! Anyone near me who has a spare battery for testing? After all that might be faulty.
muellersmattes said:
I got the phone back today. Put the battery in, started, and... it shut down. AGAIN. They were supposed to fix that! Anyone near me who has a spare battery for testing? After all that might be faulty.
Click to expand...
Click to collapse
It goes down when charger is connected?
Yes, it does. And it recognises the battery as full, that's why I don't suppose it's because of that. But one never knows.
mines done it a couple times recently too! just living with it till the update!
Problem solved. A new battery did the trick. But I still don't know why it would shut down with the old one.
I'll try to make this short.....
I am using N910T3. Phone was charging in car while using (stop by roadside). Out of sudden it shutdown and went into reboot loop and the phone is extremely hot. I took the battery out for soft reset and try to turn on again. Phone will freeze at different screen (Lock Screen, Home Page, Samsung Logo, Powered by Android) and give two separate vibration before reboot.
I thought it is battery problem so I bought a new battery to try, but still the same problem. So I went on to backup all file before I perform hard reset. While doing that, I find out the phone can be use for longer before reboot if it was stay off for a long time. So I have this crazy idea: put it in a fridge. Surprisingly it works! The phone will not reboot anymore and I can manage to backup all file before doing anything else. Also, the phone will not charge if you plug in right after a few reboot.
Then, along with the fridge method, I perform factory reset through normal android setting. Now it will just stuck at powered by android screen while in reboot loop. I then try to flash with Odin, multiple times. Flash by Odin is complete, phone restart, then it freeze and reboot, at different screen (Installing system update, Erasing, powered by android).
Out of frustration I try with the fridge method to flash, and IT WORKS AGAIN!!!. The phone can now boot to welcome screen where you first setup your phone. However, it will then freeze again and reboot while doing so.
There was only this one time, where I left the phone off for a day after flash with a previous stock ROM, turn it on and skip as much setup as I can, finally reach the homepage screen, then will stay on without any reboot issue. I thought I finally fix it. I then power off the phone, put in my Sim Card and SD Card, power it on, then again, reboot issue appear.
I tried flash with latest stock ROM, previous stock ROM (one updates away), flash any stock ROM with pit file. I sometimes will get error code on device after flash (can't remember the exact error). I also cannot boot into recovery mode without flashing a twrp. Sometimes if success, I will get straight to Lock Screen without going through the phone welcome setup process. But again, none of these I tried can solve the reboot loop.
I may went too far and mix up all steps to the phone. Does anyone have any idea how to fix this? Or is my phone, as I believe, has a faulty motherboard that cause the reboot loop? Thanks in advance for reading through my problem!
Hello there, I had a Tmo Note 4 which I loved it until the end, it's a hardware problem and there is no fix for it unless you replace the board, by the time you buy the board and what you need to pay for labor you're going to expend a few hundred dollars, I also tried the freezer method but it finally the phone gave up, it does not turn on anymore. That was my experience. Good luck bud.
oscarmaldonado said:
Hello there, I had a Tmo Note 4 which I loved it until the end, it's a hardware problem and there is no fix for it unless you replace the board, by the time you buy the board and what you need to pay for labor you're going to expend a few hundred dollars, I also tried the freezer method but it finally the phone gave up, it does not turn on anymore. That was my experience. Good luck bud.
Click to expand...
Click to collapse
Seems like that's the case I guess.....But if anyone has any suggestion please do tell so I can give it a shot.
jackgan said:
Seems like that's the case I guess.....But if anyone has any suggestion please do tell so I can give it a shot.
Click to expand...
Click to collapse
Try a firmware flash before newsest. Then take the ota
anyone know if a 910t3 mother board will fit in a 910t frame? Asking cuz I wanna switch them out.