Hi guys,
Been out of the loop for quite a while on any firmware changes with my Note 8 GT-N5110 and have ran into a problem and need some advice so I don't brick this thing, lol.
Recently the wireless started randomly turning itself off and on. I tried the usual power cycle with no luck so I ended up just doing a "restore" from the tablets menu and that didn't help either.
So, I am not sure what the next step should be. It is on version 4.1.2 and was/is rooted (although it has been so long since I did it that I do not remember a whole lot about the process).
Any suggestions? If it involves rooting/firmware, I am probably going to need detailed instructions if possible. Thanks!
Related
Hey all, Recently I've done a ton of browsing and googling and finally figured out how to S-Off and Unlock the Bootloader on my phone, but now I've come across a problem that has royally stumped me, every time that I flash a custom rom to my phone, my touch screen fails to work upon boot.
The rom installs just fine and doesn't have any issues, I get service and all that cool stuff, just the touchscreen is fully unfunctional.
I am using roms that are CDMA Specific so I don't think that could be the issue here...
Any help with this issue would be greatly appreciated as I do not wish to continue my journey with a gay ass stock rom.
I've also tried the DIAG Calibration for the phone,
unfortunately my phone just gets stuck at "Jumping to DIAG..."
Thanks in advance,
~Skaterneko
Hi. So I'm totally at a loss as to what to do. I've had a Galaxy S3 for a little over a year now, and just recently decided to try and root it. I'm not very experienced with phone software in general, but I've got enough understanding of how Android works to want to try my hand at this.
I followed mrRobinson's really helpful root via Odin guide, found here: http://forum.xda-developers.com/showthread.php?t=1774722
I never got past step 2, however. I got everything downloaded, got my phone plugged in and going, and...it's stuck now. It still says it's in the middle of download, but it's been downloading "cache.img.ext4" for about an hour now. Clearly there's something not right.
Here is a screenshot of what this has looked like: http://i.imgur.com/jy21pHd.jpg
I'd heard that using a third party cable was not advisable, but unfortunately that was something I learned after the download had already begun. As of right now, my phone is still in download mode. What do I do? Is there a way for me to go back to normal and try rooting it again with a stock cord? Or is there something I haven't done that'll finish the download? I'm terrified of unplugging it or messing with it in any way without knowing what the consequences will be.
PS: Please explain this to me as simply as possible. I'm not familiar with a lot of Android jargon, I apologize.
nuclearteacup said:
Hi. So I'm totally at a loss as to what to do. I've had a Galaxy S3 for a little over a year now, and just recently decided to try and root it. I'm not very experienced with phone software in general, but I've got enough understanding of how Android works to want to try my hand at this.
I followed mrRobinson's really helpful root via Odin guide, found here: http://forum.xda-developers.com/showthread.php?t=1774722
I never got past step 2, however. I got everything downloaded, got my phone plugged in and going, and...it's stuck now. It still says it's in the middle of download, but it's been downloading "cache.img.ext4" for about an hour now. Clearly there's something not right.
Here is a screenshot of what this has looked like: http://i.imgur.com/jy21pHd.jpg
I'd heard that using a third party cable was not advisable, but unfortunately that was something I learned after the download had already begun. As of right now, my phone is still in download mode. What do I do? Is there a way for me to go back to normal and try rooting it again with a stock cord? Or is there something I haven't done that'll finish the download? I'm terrified of unplugging it or messing with it in any way without knowing what the consequences will be.
PS: Please explain this to me as simply as possible. I'm not familiar with a lot of Android jargon, I apologize.
Click to expand...
Click to collapse
I don't think its going to work without the stock cord. But I think unplugging it would just result in a failed root I don't think it would brick. Not positive though
Sent from my SPH-L710 using xda app-developers app
nuclearteacup said:
...
PS: Please explain this to me as simply as possible. I'm not familiar with a lot of Android jargon, I apologize.
Click to expand...
Click to collapse
did you unplug the phone yet? how did it go?
Just FYI since it sounds like you are new to this, there are a few different s3 models depending on carrier. Make sure you flash something compatible with your phone.
From your screenshot, looks like everything flashed except the cache partition. Are there any other images in the .tar.md5 file you downloaded?
Here's the issue, that I've resolved, but I'm looking for a reason why this happened.
Have a Galaxy Note 10.1 (2014 Edition) running Android 5.11, rooted and running xposed.
Arrived home a few days ago and my PIN is no longer recognized to unlock the device. I been using the same pin for months and nothing of any significance had changed on the device. A couple of days earlier I had upgraded busybox and a certificate I use for an email account had expired, but I've restarted the device and used the lock screen pin multiple times after both events. Very strange that the device just stopped recognizing the pin as the correct one.
Anyway I was, fortunately, able to find a way to get into the device and authorize adb connections and took care of the issue (without having to reflash anything).
Anyone have any ideas why the device would just stop allowing the pin to unlock the device?
Mark
mlutzow said:
Here's the issue, that I've resolved, but I'm looking for a reason why this happened.
Have a Galaxy Note 10.1 (2014 Edition) running Android 5.11, rooted and running xposed.
Arrived home a few days ago and my PIN is no longer recognized to unlock the device. I been using the same pin for months and nothing of any significance had changed on the device. A couple of days earlier I had upgraded busybox and a certificate I use for an email account had expired, but I've restarted the device and used the lock screen pin multiple times after both events. Very strange that the device just stopped recognizing the pin as the correct one.
Anyway I was, fortunately, able to find a way to get into the device and authorize adb connections and took care of the issue (without having to reflash anything).
Anyone have any ideas why the device would just stop allowing the pin to unlock the device?
Mark
Click to expand...
Click to collapse
Can you please point me in the direction of a good guide to follow to root my p607t on official 5.1.1?
I've looked all over the place and there's no real confident answer out there and I'm afraid to mess anything up, cause boot loops, ect. I've got lots of experience rooting Androids in the past but this specific T-Mobile modem sounds like it is super picky.
Much thanks to anybody who can help :good:
Galaxy_Guardian_S said:
Can you please point me in the direction of a good guide to follow to root my p607t on official 5.1.1?
I've looked all over the place and there's no real confident answer out there and I'm afraid to mess anything up, cause boot loops, ect. I've got lots of experience rooting Androids in the past but this specific T-Mobile modem sounds like it is super picky.
Much thanks to anybody who can help :good:
Click to expand...
Click to collapse
Sorry for the delay in response, autoroot works great. Just find the closet match to the lt...
So, my phone reset itself randomly today and I noticed it was unable to turn on Wi-Fi for some reason. I uninstalled an app I've had for a long time called Power Toggles as I know it also can turn on/off the Wi-Fi (to make sure the phone and it weren't fighting) and I got the idea to check the root using Root Checker. Turns out, it failed . . . So something funny is going on.
I have not knowingly taken any type of update but every once in a while, my phone has tried to update and then said it aborted it due to suspected root. Not sure if that's what happened this time around as it happened while it was in my pocket (or at least it was working before I put it away and then later on, it basically stopped working and just seems to continuously reboot for funsies).
I tried rooting my phone using Kingoroot, an LG one click method (both script and GUI) with no luck. I've never had trouble rooting my phone, especially with one click roots before! I reinstalled LG drivers, disabled and re-enabled USB debugger, switched between MTP and PTP connections, etc. I can't seem to get it to recognize the phone. When doing one root method though, it reminded me to accept the RSA fingerprint and I realized that my phone is not asking me for the RSA fingerprint for my computer. I even tried revoking previous fingerprints and no luck there either. So I'm not sure what might be repressing that option but I'm assuming that's the "root" of my rooting issue.
Anyway, does anyone know
a) why my phone would suddenly be acting this way (I think I read someone else had similar symptoms in one of the one click root forums. Tried searching for more mentions but the website seems to be halting and letting me know the issue has been sent to administrators or something to that effect).
b) how do I solve this?
Below is what I'm running:
Android Version
5.0.1
Kernal Version:
3.4.0
Build Number:
LRX21Y
Software Version:
D85021I
Security Software Version:
MDF v1.1 Release 2
I have a TWRP backup made from quite a while ago (possibly a year ago) so i can try and utilize that but I'm not sure if that will do me any good if I can't root my phone first. I don't want to do anything out of desperation that's going to put me into more trouble down the road. At least as of now, my phone boots up correctly (even if it does seem to reset fairly regularly and has a constant battery drain from trying to turn on the wifi).
Any help you guys can give me would be greatly appreciated. Hopefully, I won't just have to buy a new phone . . . Thanks in advance!
Turns out Bluetooth no longer works either. Just thought that might be worth mentioning.
http://forum.xda-developers.com/lg-g3/help/wi-fi-bluetooth-fm-radio-d855-t3284582 Old problem, not much that can be done :|
jbrookley said:
So, my phone reset itself randomly today and I noticed it was unable to turn on Wi-Fi for some reason. I uninstalled an app I've had for a long time called Power Toggles as I know it also can turn on/off the Wi-Fi (to make sure the phone and it weren't fighting) and I got the idea to check the root using Root Checker. Turns out, it failed . . . So something funny is going on.
I have not knowingly taken any type of update but every once in a while, my phone has tried to update and then said it aborted it due to suspected root. Not sure if that's what happened this time around as it happened while it was in my pocket (or at least it was working before I put it away and then later on, it basically stopped working and just seems to continuously reboot for funsies).
I tried rooting my phone using Kingoroot, an LG one click method (both script and GUI) with no luck. I've never had trouble rooting my phone, especially with one click roots before! I reinstalled LG drivers, disabled and re-enabled USB debugger, switched between MTP and PTP connections, etc. I can't seem to get it to recognize the phone. When doing one root method though, it reminded me to accept the RSA fingerprint and I realized that my phone is not asking me for the RSA fingerprint for my computer. I even tried revoking previous fingerprints and no luck there either. So I'm not sure what might be repressing that option but I'm assuming that's the "root" of my rooting issue.
Anyway, does anyone know
a) why my phone would suddenly be acting this way (I think I read someone else had similar symptoms in one of the one click root forums. Tried searching for more mentions but the website seems to be halting and letting me know the issue has been sent to administrators or something to that effect).
b) how do I solve this?
Below is what I'm running:
Android Version
5.0.1
Kernal Version:
3.4.0
Build Number:
LRX21Y
Software Version:
D85021I
Security Software Version:
MDF v1.1 Release 2
I have a TWRP backup made from quite a while ago (possibly a year ago) so i can try and utilize that but I'm not sure if that will do me any good if I can't root my phone first. I don't want to do anything out of desperation that's going to put me into more trouble down the road. At least as of now, my phone boots up correctly (even if it does seem to reset fairly regularly and has a constant battery drain from trying to turn on the wifi).
Any help you guys can give me would be greatly appreciated. Hopefully, I won't just have to buy a new phone . . . Thanks in advance!
Click to expand...
Click to collapse
Well ok, you have that TWRP backup, how about accessing TWRP?
Can you enter recovery?
Does it display your IMEI in system settings, what does it do when you try to enable wifi?
Can you make backup of your current ROM in TWRP, then try to restore the old one, try restoring only system partition if the backup was made on same Android Lollipop 5.0.1. ?
Well, I was able to get into recovery and run an old image but it appears to have the same issue. My IMEI is fine (I did a full backup including IMEI but it had a valid IMEI before as well) so that wasn't the issue. Looking at that other thread someone posted, it looks like my phone is just screwed and this is a well known issue. It looks like people were able to fix it by replacing the motherboard, which is obviously not an option for me. If that's the case, I'm guessing this is my first and last LG phone. I've never had this kind of issue with a Samsung. In fact, I'm now back on an old S4 until I can figure out what to do. Not sure what phone to get at this point.
Natus, to answer your question, the Wi-Fi icon just kinda goes in a loop like it's trying to start it up. Opening up the Wi-Fi menu has it say it's starting up the Wi-Fi but never gets there. Unfortunately, it eats up battery fast, heats it up quickly, and eventually restarts.
I'm open to any other ideas but I'm guessing it's a hardware problem at this point. Thanks for the info, everyone! I do appreciate the help!
If you have any suggestions for a new phone, I'm all ears. Trying to stay out of a payment plan so I'm looking at the Nexus 6P but I'm wondering if there's one coming down the pipeline I might want to hold off for. I'd rather buy directly from the manufacturer than go through AT&T, given the option. Might need to start a new thread for that one though . . . Thanks!
jbrookley said:
Well, I was able to get into recovery and run an old image but it appears to have the same issue. My IMEI is fine (I did a full backup including IMEI but it had a valid IMEI before as well) so that wasn't the issue. Looking at that other thread someone posted, it looks like my phone is just screwed and this is a well known issue. It looks like people were able to fix it by replacing the motherboard, which is obviously not an option for me. If that's the case, I'm guessing this is my first and last LG phone. I've never had this kind of issue with a Samsung. In fact, I'm now back on an old S4 until I can figure out what to do. Not sure what phone to get at this point.
Natus, to answer your question, the Wi-Fi icon just kinda goes in a loop like it's trying to start it up. Opening up the Wi-Fi menu has it say it's starting up the Wi-Fi but never gets there. Unfortunately, it eats up battery fast, heats it up quickly, and eventually restarts.
I'm open to any other ideas but I'm guessing it's a hardware problem at this point. Thanks for the info, everyone! I do appreciate the help!
If you have any suggestions for a new phone, I'm all ears. Trying to stay out of a payment plan so I'm looking at the Nexus 6P but I'm wondering if there's one coming down the pipeline I might want to hold off for. I'd rather buy directly from the manufacturer than go through AT&T, given the option. Might need to start a new thread for that one though . . . Thanks!
Click to expand...
Click to collapse
I'd wait for note 7 or even iphone 7 =]
Hey everyone. Several years ago, I loaded a custom ROM on my Nexus 7. I'd like to flash it back to original and use it again for reading or maybe as my home automation hub. It's been so long since I rooted a device or anything, that I don't remember much of anything about it. The problem is, I don't have a PC anymore. All I have is a Macbook Pro and a Chromebook.
Can someone give me step-by-step directions to get this thing up and going again, please? Thank you!