Hi there,
Today I restored an old copy of my data but when it finished I lost the ability to touch de screen, everything works (like software and hardware buttons) but touch screen doesn't. I have TWRP so I can't use the recovery either. Please help me!
Thank you in advance!
What data did you restore? I would flash the system.img from the factory image in fastboot.
Sent from my Nexus 5
jd1639 said:
What data did you restore? I would flash the system.img from the factory image in fastboot.
Sent from my Nexus 5
Click to expand...
Click to collapse
Restored an old backup made by the same recovery, can't understand why this happened. Will try that when I get home! Thanks.
jpmrno said:
Restored an old backup made by the same recovery, can't understand why this happened. Will try that when I get home! Thanks.
Click to expand...
Click to collapse
a backup wouldnt do that. and even if it did(if it was a software derp), it wouldnt affect the recovery. the recovery has its separate software, and a separate kernel. a hardware issue would affect both. id try reflashing the factory img, if it does not help, then it is a hardware issue.
simms22 said:
a backup wouldnt do that. and even if it did(if it was a software derp), it wouldnt affect the recovery. the recovery has its separate software, and a separate kernel. a hardware issue would affect both. id try reflashing the factory img, if it does not help, then it is a hardware issue.
Click to expand...
Click to collapse
Yes but the problem is that it was working correctly until the backup finished restoring. After it finished, I couldn't touch the restart buttom on the TWRP screen so I turned off and on again the device and discovered that the touch wasn't working. Kind of weird.
Restored everything to stock and still doesn't work. Should be a hardware issue but can't understand how it happened, it was working correctly until the TWRP restore.
Restored everything to stock and still doesn't work. Should be a hardware issue but can't understand how it happened, it was working correctly until the TWRP restore.
Click to expand...
Click to collapse
Probably just coincidence but if reassuring to stock didn't cure it it probably is a hardware issue.
Sent from my Nexus 5
jpmrno said:
Restored everything to stock and still doesn't work. Should be a hardware issue but can't understand how it happened, it was working correctly until the TWRP restore.
Click to expand...
Click to collapse
it could have been just a coincidence. ive had those kind before, where i swear it was one thing but turned out another.
simms22 said:
it could have been just a coincidence. ive had those kind before, where i swear it was one thing but turned out another.
Click to expand...
Click to collapse
jd1639 said:
Probably just coincidence but if reassuring to stock didn't cure it it probably is a hardware issue.
Sent from my Nexus 5
Click to expand...
Click to collapse
Well I tried everything, it's probably hardware, too bad. Thank you anyway!
Related
Okay so I am running CM10 stable on i9023. Its been fine for like a month I think with just a couple of reboots. But today I have been getting reboot whenever I turn on bluetooth. Its a very ugly situation where upon boot the phone reboots again as soon as trying to turn on bluetooth. I then clear dalvik cache and cache to make it work again. However it seems like I really am stuck now it just wont boot anymore.
I have tried clearing cache again but it still wants to turn on bluetooth and reboots. Even took out the battery for several minutes but to no avail.
My titanium backup is a bit old so please what should I do here that doesnt require data reset?
Does nandroid backup also restore those apps which were moved to SD card?? Would it even solve the situation here?
Thanks.
Okay I finally got it running again but what do I do about the bluetooth problem now? I am scared even touching bluetooth now but I really need it from time to time. :S
So everything was fine for a few hours then I decided to do a normal reboot and bam I get the bootloop again. Something has seriously got messed up I guess.
Please anyone what would you suggest me?
Do a factory reset from recovery. If that still fails, flash the factory images and see if everything works.
Sent from my Nexus S 4G using xda app-developers app
rasengan82 said:
Do a factory reset from recovery. If that still fails, flash the factory images and see if everything works.
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Yes that's what I have decided to do.
Sent from my Nexus S using xda app-developers app
Did factory reset and everything is working fine so far including bluetooth. I just wish it doesnt happen again or I'll be really put off by CM.
Gambler_3 said:
Did factory reset and everything is working fine so far including bluetooth. I just wish it doesnt happen again or I'll be really put off by CM.
Click to expand...
Click to collapse
Had you installed something just before the problem started? I'm also on CM10 and make extensive use of bluetooth, so you just scared me
Gambler_3 said:
Did factory reset and everything is working fine so far including bluetooth. I just wish it doesnt happen again or I'll be really put off by CM.
Click to expand...
Click to collapse
How can you blame CM for that? Or any rom for that matters?
You had multiple reboots, the early ones which might have be caused by something unrelated to the rom, and the later ones something was probably corrupted. If data was being written when it rebooted on you, it's no wonder you'll have problems...
fgumo said:
Had you installed something just before the problem started? I'm also on CM10 and make extensive use of bluetooth, so you just scared me
Click to expand...
Click to collapse
Well my bluetooth is now working fine after a factory reset.
Infact yes I did install/uninstall this app a few days ago but I suppose I cant be sure about blaming it for it.
http://forum.xda-developers.com/showthread.php?t=1987032
polobunny said:
How can you blame CM for that? Or any rom for that matters?
You had multiple reboots, the early ones which might have be caused by something unrelated to the rom, and the later ones something was probably corrupted. If data was being written when it rebooted on you, it's no wonder you'll have problems...
Click to expand...
Click to collapse
It wasnt the first time CM rebooted on me, stock rom on the other hand was very stable.
And then this whole mess happens.
only had some bugs with newer nightlies.
reflashing the rom w/o factory reset did the job
Ok, so I probably know the answer to this already :crying:
Brief story - stock rooted ROM with custom kernel. Made backup with TWRP. Flashed stock boot,img and system.img in fastboot, flashed downloaded update from 4.4 -> 4.4.2 in recovery. Wiped cache and dalvik - started but recovery locked up. Had to hold power to reboot phone. Booted fine but no network, no IMEI, no baseband.
And no I don't have and EFS backup
I take it the phone is now buggered.
Is there anything I can do to fix this??
Appreciate anything that might help this.
Cheesy Wotsit said:
Ok, so I probably know the answer to this already :crying:
Brief story - stock rooted ROM with custom kernel. Made backup with TWRP. Flashed stock boot,img and system.img in fastboot, flashed downloaded update from 4.4 -> 4.4.2 in recovery. Wiped cache and dalvik - started but recovery locked up. Had to hold power to reboot phone. Booted fine but no network, no IMEI, no baseband.
And no I don't have and EFS backup
I take it the phone is now buggered.
Is there anything I can do to fix this??
Appreciate anything that might help this.
Click to expand...
Click to collapse
The same thing happened to me. Flash the latest version of TWRP, wipe your cache again, and your phone will be back to normal.
not true for all you may end up having to RMA I had my efs backup it still didn't fix it sorry to be the bearer of bad news but they make it sound like bringing it back is 100% but in some cases that's not true
Sent from my Nexus 4 using xda app-developers app
ddloco said:
not true for all you may end up having to RMA I had my efs backup it still didn't fix it sorry to be the bearer of bad news but they make it sound like bringing it back is 100% but in some cases that's not true
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
In his case, if he just does what I said to do he'll be fine. He didn't lose his EFS, he rebooted in the middle of a cache wipe and his partitions got messed up. Updating TWRP and wiping the cache again will set everything straight. This is a fairly common issue with older versions of TWRP.
_MetalHead_ said:
In his case, if he just does what I said to do he'll be fine. He didn't lose his EFS, he rebooted in the middle of a cache wipe and his partitions got messed up. Updating TWRP and wiping the cache again will set everything straight. This is a fairly common issue with older versions of TWRP.
Click to expand...
Click to collapse
I'm just saying the same thing happens to me and nothing that's suggested fixed it that's why I say its not 100% me and another guy both had the same problem and the only way was to RMA I also had my efs but even after doing everything from going back to stock updateubg twrp and reflashing my esf backup my phone would not correct its self so I'm not saying that this method doesn't work for some people but for me and another used it was a no go
So why are you guys still using twrp if it is causing issues?
Just use cwm instead!
Sent from my Nexus 5 using Tapatalk
Elisha said:
So why are you guys still using twrp if it is causing issues?
Just use cwm instead!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
because the majority dont have any problems.
and people, take precautionary measures and back up your efs partition, its the first thing i did as soon as i had a custom recovery. it takes 2 seconds. and store it somewhere OTHER then your phones internal storage, like on a comp or dropbox
TheAtheistOtaku said:
because the majority dont have any problems.
and people, take precautionary measures and back up your efs partition, its the first thing i did as soon as i had a custom recovery. it takes 2 seconds. and store it somewhere OTHER then your phones internal storage, like on a comp or dropbox
Click to expand...
Click to collapse
This is not an EFS issues. Simple matter of twrp messing up partitions.
Sent from my Nexus 5 using Tapatalk
Elisha said:
This is not an EFS issues. Simple matter of twrp messing up partitions.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i know, still doesnt hurt to be caution though
ddloco said:
I'm just saying the same thing happens to me and nothing that's suggested fixed it that's why I say its not 100% me and another guy both had the same problem and the only way was to RMA I also had my efs but even after doing everything from going back to stock updateubg twrp and reflashing my esf backup my phone would not correct its self so I'm not saying that this method doesn't work for some people but for me and another used it was a no go
Click to expand...
Click to collapse
Yeah but did it happen to you the way it happened to OP? So far every single person that I have come across who was in this boat due to a bad cache wipe in TWRP was able to fix it by updating TWRP and re-wiping the cache. It's a well known issue.
_MetalHead_ said:
Yeah but did it happen to you the way it happened to OP? So far every single person that I have come across who was in this boat due to a bad cache wipe in TWRP was able to fix it by updating TWRP and re-wiping the cache. It's a well known issue.
Click to expand...
Click to collapse
Thanks for the help guys. Got it up and running again more by accident than anything. Seems like MetalHead was correct, the partition was fine but just not readable. Unfortunately in order to get up and running again I flashed all the stock images in flasboot and did a full factory reset in the stock recovery which fixed the problem. Sounds like I could have done without the full wipe after all but at least it's all fixed now.
As for backing up the EFS, lesson learned. I had the 1st official TWRP on the phone which had no option for EFS backup like the current one. Guess what I'll be doing right now??
Anyway, happy man again and thanks to all that replied :good:
I must apologize for saying its not 100% but the truth is I had the exact same thing happen and no stock or fast boot cache fixed it I'm living proof that it works for the masses but under rare circumstances this just doesn't solve it oh man how I wish this would've fixed mine I been using a inspire 4g its killing me I feel like I jumped out of a beemer and landed in a pinto lol
Sent from my Nexus 4 using xda app-developers app
Glad that the OP got the issue resolved !
on a side note , can anyone tell me what is the safest version of TWRP there ? i.e without this cache wipse issue ( taking too long to wipe ? )
ddloco said:
I must apologize for saying its not 100% but the truth is I had the exact same thing happen and no stock or fast boot cache fixed it I'm living proof that it works for the masses but under rare circumstances this just doesn't solve it oh man how I wish this would've fixed mine I been using a inspire 4g its killing me I feel like I jumped out of a beemer and landed in a pinto lol
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thats a bummer man. What kind of phone are you using now?
Lowresolution said:
Glad that the OP got the issue resolved !
on a side note , can anyone tell me what is the safest version of TWRP there ? i.e without this cache wipse issue ( taking too long to wipe ? )
Click to expand...
Click to collapse
I believe 2.6.3.4 is the latest version. That's the one I'm on, works just fine.
Sent from my Nexus 5 using XDA Premium 4 mobile app
_MetalHead_ said:
Thats a bummer man. What kind of phone are you using now?
I believe 2.6.3.4 is the latest version. That's the one I'm on, works just fine.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got it , thanks mate Just upgraded my version of TWRP .
the nexus 4 is my phone I gave to my wife now that its hers I'm lucky to pick it up just to hop on xda but when its her Facebook time she hurrie up and kick me off lol the phone I'm using is an HTC inspire 4g it sucks
Sent from my Nexus 4 using xda app-developers app
Recently I unlocked bootloader, installed twrp and succesfully rooted my device, but while I was tinkering with my device I accidentally wipe all data, partition, etc in TWRP now I guess I wiped out everything including OS !!!
How can I restore ? Do I need to flash new hammerhead image ?
Right now I'm following this tutorial
http://forum.xda-developers.com/showthread.php?t=2513701
It'll be great if anyone of you can point me right way.
You can just flash any custom rom using this
http://forum.xda-developers.com/showthread.php?t=2575150
Or
Follow the thread you posted to restore a factory image..
But restoring a factory image will unroot your device..
You have twrp so the first thing you did was make a nandroid, right? Live and learn.
Thanks for the help, I just flashed new image. Everything works good except wifi, random drops + slow speed.
I contacted google for replacement and they send me RMA form. Unrooted the phone, bootlocker locked + flag reset.
Thanks for the help, I just flashed new image. Everything works good except wifi, random drops + slow speed.
I contacted google for replacement and they send me RMA form. Unrooted the phone, bootlocker locked + flag reset.
Huh? You're doing an RMA why?
sent from my hammerhead
albertpaulp said:
Thanks for the help, I just flashed new image. Everything works good except wifi, random drops + slow speed.
I contacted google for replacement and they send me RMA form. Unrooted the phone, bootlocker locked + flag reset.
Click to expand...
Click to collapse
Why are you rma'ing it. Was wifi messed up before you erased everything?
jd1639 said:
Why are you rma'ing it. Was wifi messed up before you erased everything?
Click to expand...
Click to collapse
Before rooting wifi problem was rarely occur now after rooting problem arise more frequently, now even after unrooting wifi is super slow sometimes not even connecting. I hate RMAing but seems like no other way.
http://forum.xda-developers.com/showthread.php?t=2586410
jd1639 said:
You have twrp so the first thing you did was make a nandroid, right? Live and learn.
Click to expand...
Click to collapse
Awesome advice. I made a nandroid of my N5 first thing after getting all my apps straight. Playing with flashing a rom in TWRP I did a manual "wipe data" which proceded to wipe out the entire SDCARD in the process including my nandroid. Sooooo.... Yes, make a nandroid but also back it up to your computer or dropbox right away.
albertpaulp said:
Before rooting wifi problem was rarely occur now after rooting problem arise more frequently, now even after unrooting wifi is super slow sometimes not even connecting. I hate RMAing but seems like no other way.
http://forum.xda-developers.com/showthread.php?t=2586410
Click to expand...
Click to collapse
Don't RMA it, there's nothing wrong with the hardware. All you have to do is reflash the factory image. If you didn't know what you were doing, you shouldn't have been messing around with your phone in the first place. Reflash your phone back to its factory state and next time do your homework before you start tinkering. People like you are going to cause Google to change their return policy so that returns are much more heavily scrutinized.
BirchBarlow said:
Don't RMA it, there's nothing wrong with the hardware. All you have to do is reflash the factory image. If you didn't know what you were doing, you shouldn't have been messing around with your phone in the first place. Reflash your phone back to its factory state and next time do your homework before you start tinkering. People like you are going to cause Google to change their return policy so that returns are much more heavily scrutinized.
Click to expand...
Click to collapse
Before rooting wifi problem was rarely occur now after rooting problem arise more frequently, now even after unrooting wifi is super slow sometimes not even connecting. I hate RMAing but seems like no other way.
Click to expand...
Click to collapse
You know how to read right ? also I did reflashed to stock image and unrooted + locked bootloader but problem persists, what do you propose I do now ? I started loving my phone now I'm getting new one, it's hard for me too, it's like adopting a son.
idk what happened i was using my phone as normal and was using snapchat, then my camera crashed and rebooted my phone. then i noticed that i didn't have signal so i went to the settings and noticed that everything that has to do with ril is gone like imei, imei sv.
i have tried taking the sim out and back in but it wont work,
also my camera wont work, google play store crashes, but one weird thing is that my modem version does not show in settings but it does in when entering the bootloader. i flashed stock 4.4.2 but still nothing is working
please i need help, have tried searching the forums but cant find any thing this similar sorry if this has been answered before (and i don't have a efs backup because im stupid..)
try reflashing your rom/gapps
Which mods did you have on your phone before it crashed?
Sent from my Nexus 5 using Tapatalk
simms22 said:
try reflashing your rom/gapps
Click to expand...
Click to collapse
already did that, but still no go, also it turns out i cant access my sd card on the pc nor on the nexus 5
nemofbaby2010 said:
Which mods did you have on your phone before it crashed?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
was using multirom with the sense 6.0 port, and xposed. that was pretty much it
FettleifIsMyUserName said:
was using multirom with the sense 6.0 port, and xposed. that was pretty much it
Click to expand...
Click to collapse
did you flash the stock rom zip or did you use the actual factory images?
try using the factory images youll lose everything but you might get your phone back: https://developers.google.com/android/nexus/images#hammerheadkot49h
nemofbaby2010 said:
did you flash the stock rom zip or did you use the actual factory images?
try using the factory images youll lose everything but you might get your phone back: https://developers.google.com/android/nexus/images#hammerheadkot49h
Click to expand...
Click to collapse
used the factory image didnt work, internal sdcard is gone, gonna try one more time
flashed the 4.4.2 factory image, still the same problems no imei or nothing and the sdcard is blank
FettleifIsMyUserName said:
flashed the 4.4.2 factory image, still the same problems no imei or nothing and the sdcard is blank
Click to expand...
Click to collapse
Sounds like another flash memory failure. Call Google and see if they'll RMA it.
FettleifIsMyUserName said:
flashed the 4.4.2 factory image, still the same problems no imei or nothing and the sdcard is blank
Click to expand...
Click to collapse
Have you flashed the cache.img? Try flashing it 2-3 times... Or just head over to stock recovery and format cache 2-3 times and then do a factory reset.. These things needs to be done via the stock recovery and not a custom one.
I had a similar problems some weeks ago and this solved it!
theesotericone said:
Sounds like another flash memory failure. Call Google and see if they'll RMA it.
Click to expand...
Click to collapse
i live in norway we cant send them to google directly it has to go trough the company where u bought it, say for an example my carrier telenor which would then deal with the problem. but i bought mine of ebay because i wanted it faster (due to problems of the 2012s nexus 7 where we didnt receive it before november.) so i guess the phone is pretty much useless now?
vin4yak said:
Have you flashed the cache.img? Try flashing it 2-3 times... Or just head over to stock recovery and format cache 2-3 times and then do a factory reset.. These things needs to be done via the stock recovery and not a custom one.
I had a similar problems some weeks ago and this solved it!
Click to expand...
Click to collapse
didn't notice your comment, ill try it and report back
nope...wiped the cache 3 times then a factory reset in stock recovery booted up still the same problems
Don't know if this will work in your case but it may be worth a try http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
Give a try to this method too maybe it will work for you.:good:
http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
i had the same issue when running the Nexsense port. There was a known issue that it would break the sensors back when it first got released but the DL link got removed immediately. after that there was a post to correct the sensors. but there was another issue with it as well. seeing as it was a NAND backup, it was very possible it re-wrote you EFS partition on your phone which stores you IMEI and other data like that. The only possibility of getting that back, is if you did a backup of the EFS partition prior to having an issue. just a warning: DO NOT FLASH ANOTHER PHONES EFS PARTITION TO YOURS. the only way to get the phone to work again with a messed up EFS partition (from what i have seen) is through replacement device unfortunately
http://forum.xda-developers.com/showthread.php?p=52414651 to let all of you know it is solved
Tapatalk-kal küldve az én Nexus 5-el
I was messing around with CM and I went into twrp to restore a backup and now my phone is locked. Can anyone point me where to go with this?
If you encrypted your device they only solution to decrypt is to factory reset.
Sent from my HTC6525LVW using Tapatalk
You need to search around here. This is a documented issue with aosp ROMs. Someone put out a command line fix (i think it's in the noon-carrier-specific m8 forum) or you can use the ruu files found in this forum.
electric turd said:
I was messing around with CM and I went into twrp to restore a backup and now my phone is locked. Can anyone point me where to go with this?
Click to expand...
Click to collapse
i just sent in my phone after this same issue i had tried the newest nightly from CM and flashed fine ran through the whole set up process then found out my bluetooth dont work so i restored my most recent bak booted my phone up and i get a message to put in my password that i have never set up
electric turd said:
I was messing around with CM and I went into twrp to restore a backup and now my phone is locked. Can anyone point me where to go with this?
Click to expand...
Click to collapse
I have had this twice now, i fixed it by formatting data in twrp then factory resetting and restoring a backup from my sd. I lost all my internal storage.
factory reset dont work either sorry were both S.O.L. unless u have insurance then just "loose ur phone"
I'm back guys!!!!! I ruu'ed in fastboot. Weird thing was when my phone booted back up it still had supersu!!!!!! That made me happy. I then flashed twrp through flashify and restored a back up I made before this whole fiasco. Thanks again for everything!!!!
So you returned your phone to Verizon over this? If it turns on you can fix it.
electric turd said:
I'm back guys!!!!! I ruu'ed in fastboot. Weird thing was when my phone booted back up it still had supersu!!!!!! That made me happy. I then flashed twrp through flashify and restored a back up I made before this whole fiasco. Thanks again for everything!!!!
So you returned your phone to Verizon over this? If it turns on you can fix it.
Click to expand...
Click to collapse
mine turns off right after it boots dosent matter where it boots to
skcitzo said:
i just sent in my phone after this same issue i had tried the newest nightly from CM and flashed fine ran through the whole set up process then found out my bluetooth dont work so i restored my most recent bak booted my phone up and i get a message to put in my password that i have never set up
Click to expand...
Click to collapse
So you sent in a phone that you broke and that can be fixed but are too lazy to research? And this is why companies lock down bootloaders. If you cant do basic searching, then dont root your phone.