Hey xda!
I rooted my phone 2-3 months ago, and regretted every day since!
I tried the guide on the forum, but i may have done something wrong.
Because it is still rooted, not with SuperSU, tho with TWRP.
Its not that the fact that my phone is rooted irritates me, its more that, i cannot update from kitkat 4.4.2 to kitkat 4.4.4.
and my Phonenetwork Signal & 3g/4g network connection is lost every 20-30 minutes.
When i am trying to Unroot, it is necessary to find my model number with the CMD. This worked for me the first time, but at that time, i couldnt find the right stock recovery backup. But now i cannot even see which model i have, because my device is never found using the developer kit tool.
I dont know how to do it, and i am very sad that i spent so many money on such a good phone, and then i "corrupted" it.
I dont know if somebody has an Easy Fix for me. i dont think so.
But if somebody knows how to do this, i would happily send it to the person who have courage to try Unroot my phone!
I will pay a fair wage for the process. Tho, HTC repair center offered me to change my internal storage and motherboard for bout 200euros.
I hope there is a superHero out there! :good::good::good:
best regards
szEIgo
First off, your understanding of what root does and means seems shaky at best. Root is just a permission change. Nothing more, nothing less. Root does not affect signal strength. Something else is going on there, that has nothing to do with root. Updating the phone might help, might not. I don't expect a drastic change in signal issues from OTA updates.
Root will also not effect the USB connectivity to your computer. This may be due to USB ports or cables; or very frequently just an issue with drivers. It too has nothing to do with being rooted.
Root in itself will not prevent OTA, although having custom recovery installed and/or any system files altered by root will prevent OTA from installing. But neither will prevent OTA notification and download from occurring. The more pressing issue, is that if you did not receive and/or able to install the 4.4.3 OTA, you won't received the 4.4.4 OTA either, as they need to be installed in sequence.
My advice is to troubleshoot the USB connectivity issue. Once you have that figured out, get CID and restore the stock nandroid and recovery. This will hopefully force the 4.4.3 OTA, then the 4.4.4 OTA.
Ty for your reply - but its not exactly what i meant in all ways.
Its not that the USB connectivity isnt working.
My pc can transfer, edit and read files from and to the HTC phone.
Its just that it cant seem to find the CID, because i did something wrong in the unrooting process.
I dont know much about all of this rooting, as you said.
Tho, I did not have any problems about my phones network connectivity, until i rooted my phone!
Im almost hundred procent sure, that this is some kind of software bug, because it has perfectly signal strength everywhere, its just that, some settings, makes it reset my phones 3g and network connection every 20 minutes or so.
Its like its going on airplane-mode, and then shortly comes back to normal.
to begin i thought i made some stupid settings on it, but then i looked all settings on the phone thru, 600 times, and couldnt find nothing!
Thank you for your reply.
I hope somebody is familiar with both of my problems:
1. cant find CID, because im stuck on some step of the unrooting process.
2. Resetting my network settings automatically every 20 minutes or so. (in short)
szEIgo said:
Its not that the USB connectivity isnt working.
My pc can transfer, edit and read files from and to the HTC phone.
Click to expand...
Click to collapse
That doesn't prove anything. You can have MTP connectivity (internal storage access) but broken fastboot and/or adb connectivity. I've seen this many times here before.
adb/fastboot not finding the device is almost always a matter of connectivity (usually a driver issue).
If you have HTC Sync and/or HTC drivers installed, try to uninstall them and see if this fixes adb/fastboot connectivity.
szEIgo said:
I dont know much about all of this rooting, as you said.
Tho, I did not have any problems about my phones network connectivity, until i rooted my phone!
Click to expand...
Click to collapse
Rooting doesn't affect the phone's performance or signal. Period.
If its a software bug, it must be due to some mod your applied, or some app you installed. I assume you must have applied some mods, or using a root app, otherwise why did you root?
And are you sure it isn't just a carrier network issue?
Related
Anyone that can help me with this one, can be my new bestfriend
After getting really really depressed over being on the Official HTC Sense ROM with my Desire, I decided to change to the Starburst ROM. As the new Unrevoked doesn't work with the latest official build of Froyo from HTC I always, always use this when I want to downgrade and root, to install new roms.
Normally, I will use the utility as indicated, everything will go smoothly, Eclair 2.1 will install, however normally my phone will be locked, and I will have to remove my SIM, update to 2.2, my phone will become Unlocked after updating, and I will root. However this time, when the utility copied a misc_partition or something like that to my SD Card, it came up with a load of write errors, saying there wasn't enough room on my SD Card, which I know is wrong as there is well above 6GB on there, and it's a Goldcard. One advantage of the utility is, if anything goes wrong you can press CRTL-C and the utility will stop with no changes made to your phone, however in my case this wasn't so. I stopped the utility, thinking if I continued due to the write error I would encounter some more errors, and I decided to do a complete wipe of my phone using the on-board Factory Reset in the Setting's menu. After doing this, I started to encounter some problems.
First of all, when the phone enters the setup wizard, it says I have 4 bars of signal, and a 3G connection. After around 15 seconds of being in the Wizard, I will suddenly loose all mobile connection. After completing the setup wizard, I will be prompted by a notice telling me I need to Insert an SD Card. Well my card is in there, and I know its working because after these problems I put it into my brothers phone, and formatted it, and it showed up as working just fine. If an LG POP can mount my phone, surely a frigging HTC Desire can?
I have noticed that if I remove my SD Card, then the problems with the Network will go away and I will be able to connect, however sometimes when I boot it my phone will connect to the Network for about 5 minutes with the SD inserted, then return back to Limited Service. *I have attached a picture of what I am seeing.* This is really annoying me, I am going to download the Froyo 2.2 ROM from Shipped-Roms as the SD Card seems to mount fine in HBoot. Please though, can anyone help me. Thanks.
*This is starting to become very annoying now, I have been working on this for several hours now, and I still have no fix or nothing. I can't exactly be patient and I don't mean to sound like a tech addict, but my world revolves around my phone, I use it for business ect. When I connect my phone to my computer, I get a message saying 'Install Drivers For Qualcomm CDMA Technologies MSM' I have heard of CDMA before, but I don't think my phone is CDMA? My phone was originally branded Orange in the UK? Anyone that can help, just please please help me!
Hi, sorry I can't help with your problem as it seems too complicated to me (noob here) but reading what you wrote sort of alarmed me as I've been reading/watching videos on rooting and I thought that unrevoked (latest version) worked on any desire. It says so on the unrevoked site but you wrote you can't do it on yours because of new build of froyo.
Don't understand that, I'm on vodafone and asked advice to a few people about rooting and nobody told that I couldn't use unrevoked. Are you sure you can't use it. How about you do a factory reset and reflash rom and see how it goes. I do hope you're wrong about unrevoked though as I'm about to use it any day now (building up the courage...) Hope you get your problem solved.
well try to reinstall whole software via pc ...............
but check download latest version of official rom
back up your data as ur whole system sofware will be replaced
and do format ur sd in pc ( not a quick format )
hopefully it might resolve ur issues ( otherwise it seems a hardware issue >>>>>)
and i am not responsible for any sim locking or data loss sort of problems
wilborama said:
Hi, sorry I can't help with your problem as it seems too complicated to me (noob here) but reading what you wrote sort of alarmed me as I've been reading/watching videos on rooting and I thought that unrevoked (latest version) worked on any desire. It says so on the unrevoked site but you wrote you can't do it on yours because of new build of froyo.
Don't understand that, I'm on vodafone and asked advice to a few people about rooting and nobody told that I couldn't use unrevoked. Are you sure you can't use it. How about you do a factory reset and reflash rom and see how it goes. I do hope you're wrong about unrevoked though as I'm about to use it any day now (building up the courage...) Hope you get your problem solved.
Click to expand...
Click to collapse
Basically on the latest Froyo build from HTC (2.29.405.5) if you use Unrevoked, everything will go fine until it boots out of the bootloader to the actual software. On reboot Unrevoked will say 'Waiting for system to Settle'. This will never dissappear and it will wait for the system to settle forever and ever. However becuase you are branded on Vodafone, the chances are you're not running Froyo build 2.29.405.5, but a slightly older one. This is because when HTC release an update the phone companies have to put their software onto it, the the 2.29.405.5 update was only 5Mb, barely enough for the companies to be even bothered messing around with, so chances are you WOULD be able to root anyway, thanks for commenting.
commando0 said:
well try to reinstall whole software via pc ...............
but check download latest version of official rom
back up your data as ur whole system sofware will be replaced
and do format ur sd in pc ( not a quick format )
hopefully it might resolve ur issues ( otherwise it seems a hardware issue >>>>>)
and i am not responsible for any sim locking or data loss sort of problems
Click to expand...
Click to collapse
Oh I know about data loss, Sim Locking and all that, been there, done that, got the T-Shirt, I've got a Utility on my computer that will unlock my phone and as for Data Loss, Google servers have it all
I've got a bit of an update though, I know your saying it's a hardware error but I think there are two key components here that aren't working.
- The SD Card
- The SIM Card
I have come to believe this, because I managed to use the PB99IMG file to update to the latest Froyo, and now my phone is saying there is an SD in there, but stats about the SD are unavailable in my phone, and also when trying to connect to the network, my phone will not connect to Orange. If I click on Manually Select, and I click on Orange, I get a message saying SIM won't allow connection to this network, if I do it with Automatic however, it just says unable to connect to the network at this time. I'm gutted I haven't been able to fix this yet, it's really annoying me because normally I would be able to sort this, been up all night trying to do it, any help is greatly appreciated.
2.29.405.5 roots absolute fine with unrEVOked - if it didn't I wouldn't be rooted!!
EddyOS said:
2.29.405.5 roots absolute fine with unrEVOked - if it didn't I wouldn't be rooted!!
Click to expand...
Click to collapse
Possibly a problem with my Device or HBoot? Could anyone point me to the correct RRU for me to reset my phone with? I am running the latest software version with a goldcard, the card won't mount when the phone is turned on, thanks.
This is for the 2.29.405.5 RUU
http://www.multiupload.com/LEJCW182AH
EddyOS said:
This is for the 2.29.405.5 RUU
http://www.multiupload.com/LEJCW182AH
Click to expand...
Click to collapse
Really appreciate it mate, thankyou
*Update, I flashed this RRU, it's not working though :/
When you say not working what do you mean? More info needed!
Also, edit the 'Qualcom CDAM' thingy, that means its trying to install modem drivers - sounds you USB-bricked the phone
EddyOS said:
When you say not working what do you mean? More info needed!
Also, edit the 'Qualcom CDAM' thingy, that means its trying to install modem drivers - sounds you USB-bricked the phone
Click to expand...
Click to collapse
Yeah it won't connect in any way USB wise, and when IS ay not working, the OS works fine, connects to the network for the first 5 minutes, SD card won't mount, then after 5 minutes I get locked out of the network, and if I try and connect I get a message saying my sim won't allow connection to Orange :/ Think you can help?
OK, I posted in the Q&A section, but not finding much love. Hopefully someone here might be more help.
The first thing to put out there is that I did not accept the Gingerbread OTA. Still on 2.2.
Here's the story: A couple of days ago I tried running unrevoked on my Evo. One month old, HW version 0004. I'm pretty sure I did everything as instructed, but the procedure failed. Machine would run for 30 seconds or so then drop into diagnostic mode (5 vibrations & lock).
So I tried re-flashing back to stock. The first stock image I tried screwed the phone up in that: (1) it would no longer see USB connections (2) no longer saw my Micro SD card (3) would no longer charge when the phone was on.
So I tried flashing a newer stock image, the third one on this page:
http://forum.xda-developers.com/showthread.php?t=884060
That only made matters worse, as now I've lost bluetooth, too.
Keeping in mind that I cannot communicate with the phone via USB (unrevoked now just keeps waiting for me to plug the phone in, as does HTC Sync, which I installed after everything else as a last shot) and am not rooted, what are my options here? I really want to get this device back to stock, because I need a phone that works.
If I take it back to a Sprint repair store will they even look at it? Can they flash it back to stock for me or am I SOL there?
I've been thinking that I could let the OTA install and if everything's still broken take it to Sprint and tell them the OTA screwed up my phone, but I'm worried I've left traces that would tell them I'm bullshitting.
Hell at this point I'm willing to pay $$ to get this thing fixed, motherboard swap or whatever, but I'm not sure Sprint will even do that.
Gotta have my phone back guys, any help greatly appreciated.
Let me clarify... So at the moment you have a version of a stock rom on the phone, and it will actually turn on?
However, you can't "connect" per se to the phone?
You could either email yourself the files you need or use "Awesome Drop"
OR
I've read that if you've bricked or screwed your phone around the time of an OTA happening to come out, you can go to Sprint and tell them you tried to accept the OTA update, Make up some BS about blah blah blah, and then you're left here with a phone that's acting really weird and is borked.
Generally the tech will re-flash as they are familiar with the issues OTAs can cause.... Or they may give you a refurb.
TF1984 said:
Let me clarify... So at the moment you have a version of a stock rom on the phone, and it will actually turn on?
However, you can't "connect" per se to the phone?
You could either email yourself the files you need or use "Awesome Drop"
OR
I've read that if you've bricked or screwed your phone around the time of an OTA happening to come out, you can go to Sprint and tell them you tried to accept the OTA update, Make up some BS about blah blah blah, and then you're left here with a phone that's acting really weird and is borked.
Generally the tech will re-flash as they are familiar with the issues OTAs can cause.... Or they may give you a refurb.
Click to expand...
Click to collapse
I'm not rooted, though, so I doubt any files I could e-mail myself would do any good.
I am considering taking the phone back to Sprint, but I don't know whether to accept the OTA then make up some story about losing Bluetooth, SD Card access and USB, or just being honest and telling them what I did.
At this point I just want to get my phone back to stock and working as it should. I'll leave the rooting adventures to others. Rooting my Nook Color is one thing, since it's basically a $250.00 toy, but I can't live without my phone.
Try this:
http://forum.xda-developers.com/showthread.php?t=695243
However, will need root to fix the USB problem. You should look into some temp root options that will allow you to use a terminal emulator to fix the USB issue. I've never tried a temp root method, so you're going to have to do some digging around for that. Maybe someone who knows more about temp root can chime in and help.
You could start one of two ways...
Either email yourself the S-Off and Recovery Image files, move them to proper place
Or take it to Sprint. Just tell them teh OTA messed something up. Don't think up a whole world of stories or truths. Trust me, they're used to it.
TF1984 said:
You could start one of two ways...
Either email yourself the S-Off and Recovery Image files, move them to proper place
Or take it to Sprint. Just tell them teh OTA messed something up. Don't think up a whole world of stories or truths. Trust me, they're used to it.
Click to expand...
Click to collapse
So, accept the GB OTA, then?
My Sprint store is also a repair facility. Do they have hardware and tools that can re-flash the device to stock regardless of what you've done to it? because that's what I'm thinking of doing at this point.
My biggest problem with attempting to fix it myself is that not being rooted and not having USB access I seem to be SOL.
BTW: I just testes WiMax and it works, so at least my WiMax key is good.
Will your phone recognize the SD at all? If you can get another card to work, you could theoretically run a PC36IMG of the RUU through the bootloader. However, you'll need your SD card working. If your computer will recognize it but the phone won't, you can try backing up the contents, then formatting/partitioning the card. Then move just the PC36IMG to the card, boot into the bootloader, and hopefully it'll ask you to update.
If you can't get anything to work, then download the OTA and start installation. The OTA may fix it... but probably not. If it does fix it, hooray!, but you're stuck without root until an exploit is found. If it doesn't fix it, take it into Sprint and tell them you took the update and your phone is acting funny. Technically if you word it that way, you're not lying
If the card can't be recognized, don't worry about the files on it. If it can, just delete any PC36IMGs or other files related to rooting/troubleshooting. Other than the SD card, there shouldn't be any way to tell you attempted to root as long as you're s-on & cannot access recovery.
If you don't have insurance, I'm not sure how Sprint will handle it. If you do, they should either fix it or replace it for free.
(from... Evo/MIUI/Tapatalk)
plainjane said:
Will your phone recognize the SD at all? If you can get another card to work, you could theoretically run a PC36IMG of the RUU through the bootloader. However, you'll need your SD card working. If your computer will recognize it but the phone won't, you can try backing up the contents, then formatting/partitioning the card. Then move just the PC36IMG to the card, boot into the bootloader, and hopefully it'll ask you to update.
If you can't get anything to work, then download the OTA and start installation. The OTA may fix it... but probably not. If it does fix it, hooray!, but you're stuck without root until an exploit is found. If it doesn't fix it, take it into Sprint and tell them you took the update and your phone is acting funny. Technically if you word it that way, you're not lying
If the card can't be recognized, don't worry about the files on it. If it can, just delete any PC36IMGs or other files related to rooting/troubleshooting. Other than the SD card, there shouldn't be any way to tell you attempted to root as long as you're s-on & cannot access recovery.
If you don't have insurance, I'm not sure how Sprint will handle it. If you do, they should either fix it or replace it for free.
(from... Evo/MIUI/Tapatalk)
Click to expand...
Click to collapse
When boot into the bootloader and choose "restore" it does recognize the SD card. That's how I managed to flash this image (third klink on page) and get back to stock:
http://forum.xda-developers.com/showthread.php?t=884060
So it's definitely a software issue with the phone preventing me from seeing the card/USB or connecting to bluetooth.
At this point I don't mind not being rooted. Having a working phone is more important.
And unfortunately I don't have insurance, but I'll pay the repair fee if they ask me to.
dsf3g said:
When boot into the bootloader and choose "restore" it does recognize the SD card. That's how I managed to flash this image (third klink on page) and get back to stock:
http://forum.xda-developers.com/showthread.php?t=884060
So it's definitely a software issue with the phone preventing me from seeing the card/USB or connecting to bluetooth.
At this point I don't mind not being rooted. Having a working phone is more important.
Click to expand...
Click to collapse
Did you try the SD card fix I posted above? I think with the SD card fixed and temp root you'll be able to fix both problems.
rugedraw said:
Did you try the SD card fix I posted above? I think with the SD card fixed and temp root you'll be able to fix both problems.
Click to expand...
Click to collapse
Thanks, I'll try that. I saw that thread earlier, and I just noticed that someone answered my question about fastboot. So I'll see if I can fix USB using that.
What really bugs me now is the lack of Bluetooth!
XDA search is down right now so I can't see if there are any others who have experienced this.
Please note that with the link I gave you, you can fix the SD card not being detected issue, but to fix the USB port using those instructions, you need root. Since Unrevoked won't work without the USB, you would have to either try a temp root method (I've never used it so I can't offer you much help there) or some other manual root method where the USB port isn't needed.
Step 1, Go into Device Manager
Start Device Manager.
Windows 7
Click Start > Control Panel > System and Security > Device Manager. Windows Vista
Click Start > (Settings) Control Panel > (System and Maintenance) > Device Manager. Note If prompted, click Continue. Windows 2000 / XP
Click Start > (Settings) Control Panel > (Performance and Maintenance) > System > Hardware > Device Manager.
Step 2, These Devices are typically installed when you Install HTC Sync or Just connect your Android Device, If their are no conflicts uninstall all of them and restart your PC, Then Reconnect your android Device
The following devices are normally installed:
If a red X, yellow ! or yellow ? is displayed to the left of a listed device, a conflict is present and the drivers must be updated or reinstalled.
Note Driver conflicts may also be indicated by a device entry labeled Other Devices or Unknown.
Android USB Devices
My HTCDisk drives
HTC Android Phone USB DeviceModems
HTC Modem (if using as a tethered modem)Portable Devices
E:/ (Where E represents the assigned drive letter.)Universal Serial Bus controllers
USB Composite Device USB Mass Storage Device
kingakuma said:
Step 1, Go into Device Manager
...
Click to expand...
Click to collapse
Thanks, Kingakuma, I'll try that, but I don't think the problem is on the PC side. My Evo won't recognize the charger when it's plugged in, so I'm pretty sure the issue is on the Evo.
dsf3g said:
Thanks, Kingakuma, I'll try that, but I don't think the problem is on the PC side. My Evo won't recognize the charger when it's plugged in, so I'm pretty sure the issue is on the Evo.
Click to expand...
Click to collapse
are you using the same usb cable for the charger?
if so try a different usb cable
so rom boots but somethings just do not work correct? bluetooth and usb and sdcard correct? follow the above advice to fix sdcard as mentioned then download z4root from here, to try and root since you are still on froyo temp root should work, at which point download rom manager. use rom manager to install either clockwork or amon ra recovery, boot to recovery, flash rom, profit!
link for z4root
http://forum.xda-developers.com/showthread.php?t=833953
DomSim said:
so rom boots but somethings just do not work correct? bluetooth and usb and sdcard correct? follow the above advice to fix sdcard as mentioned then download z4root from here, to try and root since you are still on froyo temp root should work, at which point download rom manager. use rom manager to install either clockwork or amon ra recovery, boot to recovery, flash rom, profit!
link for z4root
http://forum.xda-developers.com/showthread.php?t=833953
Click to expand...
Click to collapse
Thanks, but how can I download or install this without an SD card mounted?
dsf3g said:
Thanks, but how can I download or install this without an SD card mounted?
Click to expand...
Click to collapse
ok, we can't help you if you do not follow directions. read my post, and those of the others who posted. one contains a link to a thread to fix the sdcard. you have been told to do this several times. i told you to do this first then get z4root. im done helping you, good luck.
Use z4root in order to achieve temp root for previous mentioned fixes.
Wohooo! I've fixed the SD Card issue! Thanks all, even DomSim, who's apparently given up on me in frustration. Give a noob a break, DomSim. I'm new to all this and am trying to balance reading this stuff with a family that also needs my attention.
I've got Z4Root installed and verified root, too. I'll probably fix the USB issue at work, since I don't need a computer connection for that and it's getting late (yeah, I usually leave for work just after 5:00 AM).
Once I've got the USB issue sorted I'll have to take a look at the bluetooth issue. I'm hoping its related to the USB situation and will be cured at the same time, but suspect that's just wishful thinking on my part.
Just completed the USB repair portion and.... SUCCESS!!!!! BEYOND MY WILDEST DREAMS, actually, as Bluetooth now works also.
I was hoping that the bluetooth functionality depended on USB (I think I recall that the bluetooth module on my Dell Mini 9 was USB based) and lo and behold, it does!!!!
Thanks again to everyone who helped out. You guys are first class!
I have been using PDAnet for a couple of years now and never had a problem with the USB tether until I got an update a week or so ago and now it just gets stuck on "connecting to your phone....". I have been emailing the website for PDAnet and they seem to think the update screwed up a driver or something so I reinstalled everything on the phone and PC including the phone drivers. I preferr stock since I am too lazy and too old to keep up with the speed at which changes come so has anyone else had this problem? If so is there a fix? If theres no fix how hard is it to roll back this last update?
Tethering is important to me so all options are on the table even if I have to get back into rooting (though I preferr not to since you guys would get sick of my dumb questions).
Now this has me bothered. Ive never posted a question in here that didn't get some kind of assistance. That would ordinarily make me think my problem was unique except for I have found others with the same issue posting in the PDAnet and PDAnet plus feedback on the Play store.
I'll take any attempt at something I haven't tried from one of you smarter folks. I did a factory reset and it did nothing to help the problem.
Then complain to PDAnet as they probably need to update their app to work with 4.2.2
I have and they are being quite useless. I've just always had good luck here on XDA. Oh well maybe it isnt meant to be.
On another note does anyone have any suggestions on another app to try for tethering without root?
It's not hard to roll back, except that you'll have to unlock the device's bootloader, which wipes its data. Also, you'll have to find a factory image of 4.2.1 for your device, unless you roll back to 4.1.2, then get an update to 4.2.1 and figure out how to disable it for the 4.2.2 update. http://forum.xda-developers.com/showthread.php?t=1626895
When new versions of Android are released its normal for apps to require an update to work properly.
Koush has that no root usb tethering app. Can't remember the name, search the play store fore more apps from the Rom Manager dev and you will see it. Never used it but that's the one I know of.
Just about any custom firmware will have any tethering block or tracker disabled so you can just tether natively with a ROM.
Solved with jTether (root needed).
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 =]
I've tried searching around here for an answer, but I haven't really been able to find anything solid regarding the issue that I'm experiencing. The other day I popped my sim card into my sgh-i467, as I do from time to time, to check for any OTA updates. This device is usually mounted in my vehicle, so I don't regularly check for updates. Sure enough, an OTA update was available. Tablet was at maximum charge, so I went ahead and chose to do the update. Unfortunately, the update failed at around 93% and went into a boot loop. There was nothing crucial on the device, so I figured it'd be no big deal to just re-flash the firmware if need be. However, I can only seem to find a KIES image for 4.1.2, and while I didn't think to verify exactly what version I was on before the bootloop/brick, I'm fairly certain I was on 4.2.xx.
From what I understand, the bootloader updates with 4.4, correct? With the bootloader getting updated, downgrading to 4.1.2 isn't possible or feasible, right? I didn't think to confirm this before I attempted to flash the KIES image for 4.1.2 via odin (kies never seems to actually see my device), which fails every attempt. I was originally able to get into recovery, but I kept seeing that /system wasn't found. I'm assuming that the OTA update partially installed, before failing, and either corrupted the partition scheme or updated the bootloader but not the system?
I'm dead in the water at this point, and AT&T is obviously no help. Plus, I don't the device on contract with them anyway, so I'm starting to think that my only option is to contact Samsung. However, I really don't want to have to send the unit in, and given it's age, I don't think it's worth investing anything in it if the repair isn't covered somehow. Plus I enjoy tinkering, I'm not new to the scene, and I'd really like to come up with a solution that doesn't require Samsung.
I don't suppose any kind people out there have any suggestions, similar experiences, etc. do they? I'd really like to hear from anyone who's got something to offer! Thanks in advance for your help!
pbrady5 said:
I've tried searching around here for an answer, but I haven't really been able to find anything solid regarding the issue that I'm experiencing. The other day I popped my sim card into my sgh-i467, as I do from time to time, to check for any OTA updates. This device is usually mounted in my vehicle, so I don't regularly check for updates. Sure enough, an OTA update was available. Tablet was at maximum charge, so I went ahead and chose to do the update. Unfortunately, the update failed at around 93% and went into a boot loop. There was nothing crucial on the device, so I figured it'd be no big deal to just re-flash the firmware if need be. However, I can only seem to find a KIES image for 4.1.2, and while I didn't think to verify exactly what version I was on before the bootloop/brick, I'm fairly certain I was on 4.2.xx.
From what I understand, the bootloader updates with 4.4, correct? With the bootloader getting updated, downgrading to 4.1.2 isn't possible or feasible, right? I didn't think to confirm this before I attempted to flash the KIES image for 4.1.2 via odin (kies never seems to actually see my device), which fails every attempt. I was originally able to get into recovery, but I kept seeing that /system wasn't found. I'm assuming that the OTA update partially installed, before failing, and either corrupted the partition scheme or updated the bootloader but not the system?
I'm dead in the water at this point, and AT&T is obviously no help. Plus, I don't the device on contract with them anyway, so I'm starting to think that my only option is to contact Samsung. However, I really don't want to have to send the unit in, and given it's age, I don't think it's worth investing anything in it if the repair isn't covered somehow. Plus I enjoy tinkering, I'm not new to the scene, and I'd really like to come up with a solution that doesn't require Samsung.
I don't suppose any kind people out there have any suggestions, similar experiences, etc. do they? I'd really like to hear from anyone who's got something to offer! Thanks in advance for your help!
Click to expand...
Click to collapse
You need to upgrade to keis 3.0 and reboot, then start kies, then boot note into download mode and have kies detect and reload the update.
Too bad you let the Note update to Kit Kat, Jellybean is better, on the LTE Note.
gooberdude said:
You need to upgrade to keis 3.0 and reboot, then start kies, then boot note into download mode and have kies detect and reload the update.
Too bad you let the Note update to Kit Kat, Jellybean is better, on the LTE Note.
Click to expand...
Click to collapse
Thank you very much for the information! Unfortunately, I've tried Kies 3.0. It notifies me that my device isn't compatible with Kies 3.0. With the other version of Kies, 2.6 maybe(?), it never ends up being able to connect. I've tried manual initialization, but when after I enter my model number, it won't accept my serial.
Take it to a BEST BUY with a Samsung Experience Center (Kiosk (Most all of them in larger cities have them) and they will fix your SGH-i467 for free. I did almost the same exact thing as you (trying to solve a EFS problem) and was stuck. I have posted about it on here before. They will not charge you BUT you may run into a clueless rep now and then. If you do, ask them to call for help and they will get you fixed up in a hurry. Hope this helps.