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
Related
Okay so.. I have an answer to my problem.. this is a problem that i had encountered many times in forums while i was looking for my answer.. big thanks to diablo2224 for his help and a thanks goes out to Cranvis for actually replying at all..
Okay so the home button wasn't working at all and it would flash and basically do zero (im sure this fix would help any buttons if this was the case). In the end i didnt have much to lose the home button not working was giving me the 'sheets' so i just tried to flash most things for wifi xoom as i was hoping it would crack a difference but it didnt... i ended up seeing a post from stachre for an update and in it was there he had pointed to stock motorola files.. i grabbed these and preformed all wipes (user data, cache, delvik - i doubt it would do much but i did it anyway).. using fastboot i then flashed the boot.img, the system.img, the userdata.img and finally the recovery.img (can always flash over the CWM anway so not a big deal) and booted it back up... suprise suprise the home button was perfectly functional again (every other update/flash of software would seeming 'update' and not actually flash to that portion of the device thereby leaving my problem and the stock images must have actually hit these sectors) i know my answer is long but just trying to be helpful to anyone else with this type of problem (stock Xoom WiFi MZ604 HWI69 images from Motorola)
as a side note : this was followed by flashing the CWM again and booting into CWM and flashing the 2.1 hammer and then wiping user data and booting into the freshly updated rom stoked!
okay it seems the home button is not working at present. i have wiped all data and cache and dalvik cache a thousand times and tried reflashing, etc still to no avail. does anyone have any more ideas? its painful to push the back button a million times to get anywhere lol
joshndroid said:
okay it seems the home button is not working at present. i have wiped all data and cache and dalvik cache a thousand times and tried reflashing, etc still to no avail. does anyone have any more ideas? its painful to push the back button a million times to get anywhere lol
Click to expand...
Click to collapse
ok, so a few questions.
I am guessing it is rooted so my questions are:
What ROM are you using?
Have you tried other ROMs?
Have you been experiencing this problem since you installed the rom?
have you downloaded anything (APP, Live Wall Paper, a random APK File) before this happened?
Are you using a screen protector on the Xoom?
~If yes to the last question, is there any air bubbles or dirt in that area of the button?
~If no to last question, are you aware of any dirt or scratches in that area?
Have you tried the Home tab in Landscape as well as Portrait mode?
Have you just recently updated to a OTA that was pushed out by either Motorola/Verizon/etc?
There could be many possible reasons as to why this is happening... and I would like to help you (and who ever posts afterwords) to fix this situation. I or someone else on this board will respond as soon as possible to your problem and I hope this post helps to solve the problem
Cranvis said:
ok, so a few questions.
I am guessing it is rooted so my questions are:
What ROM are you using?
Have you tried other ROMs?
Have you been experiencing this problem since you installed the rom?
have you downloaded anything (APP, Live Wall Paper, a random APK File) before this happened?
Are you using a screen protector on the Xoom?
~If yes to the last question, is there any air bubbles or dirt in that area of the button?
~If no to last question, are you aware of any dirt or scratches in that area?
Have you tried the Home tab in Landscape as well as Portrait mode?
Have you just recently updated to a OTA that was pushed out by either Motorola/Verizon/etc?
There could be many possible reasons as to why this is happening... and I would like to help you (and who ever posts afterwords) to fix this situation. I or someone else on this board will respond as soon as possible to your problem and I hope this post helps to solve the problem
Click to expand...
Click to collapse
Okay mate ill answer each question firstly i was on the manta ray with update rom.. Everything was fine i was able to use it perfect as normal no updated apks no new apks.. I was fine i cam home from work seen the update so downloaded check the md5 and did all wipes as instructed in the tiamat 2.1 rom.. I had previously installed the kernal for that the day prior and was running great.. I tried reinstalling the previous rom again after a few reflashes of the 2.1 hammer and wiped that see if the button would come back to no avail..
I have a screen protector but it is fine i was using it for days prior wirh not 1 hiccup so that is definately elimated.. No pushed updates.. I went through all otas already before i flashed the manta ray stuff and as i said that was fine all the other buttond beside it work like tje back menu and switcher just the home does nothing
Cheers
Josh
Sent from my HTC Sensation Z710e using XDA Premium App
joshndroid said:
Okay mate ill answer each question firstly i was on the manta ray with update rom.. Everything was fine i was able to use it perfect as normal no updated apks no new apks.. I was fine i cam home from work seen the update so downloaded check the md5 and did all wipes as instructed in the tiamat 2.1 rom.. I had previously installed the kernal for that the day prior and was running great.. I tried reinstalling the previous rom again after a few reflashes of the 2.1 hammer and wiped that see if the button would come back to no avail..
I have a screen protector but it is fine i was using it for days prior wirh not 1 hiccup so that is definately elimated.. No pushed updates.. I went through all otas already before i flashed the manta ray stuff and as i said that was fine all the other buttond beside it work like tje back menu and switcher just the home does nothing
Cheers
Josh
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
Thank you for the speedy reply to my questions. And I am sorry to say, this is one that is over my head. I would suggest that you go to Tiamat's (Or current ROM's) maker and inquire for their help. I am new to some of this but I thought I should at least ask you the basics and make sure on everything. (Woo A+ Tech Training haha!) But unfortunately, I cannot help you with this problem because I do not know what could be doing this other then maybe a line of code didn't get placed into memory when the device was flashed, or maybe there is a small error in the code itself and only certain devices have this problem (different model number = slightly different change to the chip-sets and code of the device.) There are many things that could be the trouble, and like i said, unfortunately, they are out of my understanding of the device.
I do hope that you are able to get an answer soon to your question and I hope it is a simple answer.
Sorry I could not help any more but I hope others can!
Good Luck
joshndroid said:
okay it seems the home button is not working at present. i have wiped all data and cache and dalvik cache a thousand times and tried reflashing, etc still to no avail. does anyone have any more ideas? its painful to push the back button a million times to get anywhere lol
Click to expand...
Click to collapse
I reported this issue once before when I was using Xoom Zone a month or so ago. I hadn't wiped data, and it was like the home button was there just to look pretty. You could click it, it would highlight, but it was broken. If anything, I can be of service as I have had this issue once before.
I will need more info though. Do you restore data and try to hit the home button, or do you try the home button after a fresh data wipe without restoring data? It's hard for me to explain what I want you to explain, but...
diablo2224 said:
I reported this issue once before when I was using Xoom Zone a month or so ago. I hadn't wiped data, and it was like the home button was there just to look pretty. You could click it, it would highlight, but it was broken. If anything, I can be of service as I have had this issue once before.
I will need more info though. Do you restore data and try to hit the home button, or do you try the home button after a fresh data wipe without restoring data? It's hard for me to explain what I want you to explain, but...
Click to expand...
Click to collapse
A fresh data wipe mate exactly as the hammer rom thread instructed to do. No restore of data as i wanted to start fresh as i find less problems arise when u try to recover too much data and as the thread specifically called for a wipe i was more than obliging lol
Sent from my HTC Sensation Z710e using XDA Premium App
joshndroid said:
A fresh data wipe mate exactly as the hammer rom thread instructed to do. No restore of data as i wanted to start fresh as i find less problems arise when u try to recover too much data and as the thread specifically called for a wipe i was more than obliging lol
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
I see. I've never heard of this version of the problem. My problem occurred when updating from the 3.1 Rom to the 3.2 Rom. I only had this problem because I didn't wipe data the first time because after it booted up I thought all was well... until I discovered the home button was broken... lol.
Anyways, even I'm at a loss here for how we can solve your problem. A simple data wipe resolved mine in a heartbeat... but it seems your problem is still persistent even after a clean data wipe install... interesting... can't say that I've ever seen a problem stay in the memory even after a complete data wipe...
The only thing I can suggest is to maybe drop back to a stock Rom, maybe 3.1, then installing Tiamat from that fresh stock Rom with another clean data wipe before and after. That's all I can think of since after a data wipe it's still there. Good luck!
I dropped back to manta still with the issue.. Would a nandroid recovery possibly help fix as it takes precedence over an update cuz thwn someone maybe be able to help
Sent from my HTC Sensation Z710e using XDA Premium App
joshndroid said:
I dropped back to manta still with the issue.. Would a nandroid recovery possibly help fix as it takes precedence over an update cuz thwn someone maybe be able to help
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
That might help. I can help as much as I can, but...
Try to go full stock first before anything. Do not use Tiamat for right now. Install a completely stock, but rooted 3.1 Rom is what I suggest for you to do so that you can see if it's still giving you troubles on a stock Rom.
I tried that from the other thread and gained a bootloop.. Maybe stock 3.1 recovery and not just an update more to the point where would i find such? I only used otas as i was just speeding process to get to 3.2 to start flashing customs
Sent from my HTC Sensation Z710e using XDA Premium App
joshndroid said:
I tried that from the other thread and gained a bootloop.. Maybe stock 3.1 recovery and not just an update more to the point where would i find such? I only used otas as i was just speeding process to get to 3.2 to start flashing customs
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
I dunno man, I'm usually one who has great helpful answers, but... uh, this one stumps me. Like I said, I've never seen a problem that still persisted after a data wipe. It's almost as if it is much deeper than a data wipe, but more like something has locked itself into your Xoom's memory and won't leave without forcing it out manually... something must be messing with your system files or something like that. Possibly something left over from the OTA updates of some sort maybe. Very strange...
I would pass this by Team Tiamat. Sorry I can't help this time. Good luck!
I need a nandroid i think from someone
Sent from my HTC Sensation Z710e using XDA Premium App
joshndroid said:
I need a nandroid i think from someone
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
So you want someone to have a completely data wiped nandroid backup of the latest Tiamat Rom so that you can use that? That should work, especially if the backup has everything working perfectly. By having the ability to use nandroid backups you have nothing to lose since it can be restored very easily.
im not picky i would like a nandroid of any rom really mate... as long as the home button was working... so basically from a wifi US xoom (if compatibility was an issue) and the rest was okay yeh that would be great... i dont know anyone else with one here in AUS so someone here would have to help me out
p.s i have already tried the one from the dev thread of the stock 3.2 but that is bogus and doesnt really work for anyone and it didnt for me
joshndroid said:
im not picky i would like a nandroid of any rom really mate... as long as the home button was working... so basically from a wifi US xoom (if compatibility was an issue) and the rest was okay yeh that would be great... i dont know anyone else with one here in AUS so someone here would have to help me out
p.s i have already tried the one from the dev thread of the stock 3.2 but that is bogus and doesnt really work for anyone and it didnt for me
Click to expand...
Click to collapse
I have a 3G Xoom, but I can make a data wiped clean nandroid backup for the latest Tiamat Rom, which I am running since Tiamat supports 3G and Wifi models alike. I can do that after work tomorrow if you would like me to...
Or you could find someone who has the Wifi model and do that.
diablo2224 said:
I have a 3G Xoom, but I can make a data wiped clean nandroid backup for the latest Tiamat Rom, which I am running since Tiamat supports 3G and Wifi models alike. I can do that after work tomorrow if you would like me to...
Or you could find someone who has the Wifi model and do that.
Click to expand...
Click to collapse
thanks for ya help... i solved my problem and edited my first post
joshndroid said:
thanks for ya help... i solved my problem and edited my first post
Click to expand...
Click to collapse
Cool! I knew it was something with the system files. Case closed.
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
Hi. I recently installed Liquid Smooth (Unofficial) 4.3 onto my Skyrocket. Since install, if I reboot the phone it will get the ever dreaded Black Screen Of Death. The only way I've found to fix this is to clear the data partition in my recovery (TWRP updated to most recent version) and then reflash the ROM and the gapps. Any ideas on how to keep the BSOD from happening again? I've tried everything I can think of. I tried just wiping the dalvek, cache and system and then flashing the ROM again. As I said, the only way I can find to "fix" it is to wipe the data partition and then flash the ROM and gapps again. I would have asked in that specific thread, but since I am a new member I can't until I reach the 10 post requirement.
CoolWolf22 said:
Hi. I recently installed Liquid Smooth (Unofficial) 4.3 onto my Skyrocket. Since install, if I reboot the phone it will get the ever dreaded Black Screen Of Death. The only way I've found to fix this is to clear the data partition in my recovery (TWRP updated to most recent version) and then reflash the ROM and the gapps. Any ideas on how to keep the BSOD from happening again? I've tried everything I can think of. I tried just wiping the dalvek, cache and system and then flashing the ROM again. As I said, the only way I can find to "fix" it is to wipe the data partition and then flash the ROM and gapps again. I would have asked in that specific thread, but since I am a new member I can't until I reach the 10 post requirement.
Click to expand...
Click to collapse
Try using the latest CWM recovery. Some people are reporting having better luck using this for the BSOD issue.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jondroid2 said:
Try using the latest CWM recovery. Some people are reporting having better luck using this for the BSOD issue.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I will try this and will get back to you. I'd still like to know what's causing the issue in the first place. I've been flashing on Samsung devices since the original Epic 4G launched. Never have had any issues like this before.
CoolWolf22 said:
I will try this and will get back to you. I'd still like to know what's causing the issue in the first place. I've been flashing on Samsung devices since the original Epic 4G launched. Never have had any issues like this before.
Click to expand...
Click to collapse
I've had the same issue and switching to cwm solved it. It's a real pita though as a prefer twrp and my nandroids are twrp. I switch back and forth between them.
jd1639 said:
I've had the same issue and switching to cwm solved it. It's a real pita though as a prefer twrp and my nandroids are twrp. I switch back and forth between them.
Click to expand...
Click to collapse
CWM fixed my BSOD. I've had 2 successful reboots so far. I too preferred TWRP over CWM. But oh well. I am in contact with the devs for TWRP to see if they are aware of the issue and can issue a fix for it.
CoolWolf22 said:
CWM fixed my BSOD. I've had 2 successful reboots so far. I too preferred TWRP over CWM. But oh well. I am in contact with the devs for TWRP to see if they are aware of the issue and can issue a fix for it.
Click to expand...
Click to collapse
There's an build of TWRP 2.7 that I've been using and haven't had any issues with. The only thing "wrong" with it is it only reads internal storage. Here's the Link
theesotericone said:
There's an build of TWRP 2.7 that I've been using and haven't had any issues with. The only thing "wrong" with it is it only reads internal storage. Here's the Link
Click to expand...
Click to collapse
Thanks. I'll download that and keep it in reserve for future reference.
Is it just my phone or does it take absolutely ages?
Sent from my Nexus 5 via Tapatalk
Nope it's not just you.
Sent from my Nexus 5
Good! Lol. Cus on my Xperia its a few seconds of a process!
Sent from my Nexus 5 via Tapatalk
Same for me! Takes a good few minutes :/ On my Nexus 4 it would be a couple seconds!
Must be something to do with Android 4.4 I assume?!
Every time I do it, wipes my imei and I have to flash the factory image...I'm actually looking for a twrp flashable cwm file if that makes any sense
Sent from my Nexus 5 using XDA Premium 4 mobile app
mrakifa said:
Every time I do it, wipes my imei and I have to flash the factory image...I'm actually looking for a twrp flashable cwm file if that makes any sense
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Haven't seen a zipped cwm for the N5 yet. Why not just flash the .img in fastboot?
I just load up fastboot in my computer and
Code:
fastboot format cache
takes 3 secs
and format data separately in recovery mode....
george241312 said:
I just load up fastboot in my computer and
Code:
fastboot format cache
takes 3 secs
and format data separately in recovery mode....
Click to expand...
Click to collapse
Lol. Not with my laptop! It takes half a day to turn on
Sent from my Nexus 5 via Tapatalk
MattyPW said:
Same for me! Takes a good few minutes :/ On my Nexus 4 it would be a couple seconds!
Must be something to do with Android 4.4 I assume?!
Click to expand...
Click to collapse
It took several minutes also for me. Really awkward. With my previouse phone, LG p880, it was a matter of few seconds.
Probably the best part of 10 minutes to wipe cache/dalvik for me today!
Its a know issue with the N5. I believe its hardware related. TWRP devs will figure it out.
eep2378 said:
Its a know issue with the N5. I believe its hardware related. TWRP devs will figure it out.
Click to expand...
Click to collapse
Yes, it is. And there is a workaround for that issue: Go to the TWRP settings and activate "format rm - rf", so your wipe takes normal time as known.
You can find more about that in the TWRP Nexus5 main thread here .
Regards
Koetermann
For me personally, wiping the cache entirely deletes my internal storage so I would avoid it at all costs until there is an update..
Ben36 said:
Is it just my phone or does it take absolutely ages?
Sent from my Nexus 5 via Tapatalk
Click to expand...
Click to collapse
It takes my device a little while to wipe via TWRP.
scottdouglasdick said:
For me personally, wiping the cache entirely deletes my internal storage so I would avoid it at all costs until there is an update..
Click to expand...
Click to collapse
Such thing never happened to me. Formatting cache takes like 3 minutes for me, but it doesn't do any awkward. Unless you reboot while formatting ofc.
I'm avoiding wiping cache in TWRP at the moment...
first time i did that it borked something and i couldnt even switch airplane mode off or open play store when i got wifi on etc...wasnt that nice
Koetermann said:
Yes, it is. And there is a workaround for that issue: Go to the TWRP settings and activate "format rm - rf", so your wipe takes normal time as known.
You can find more about that in the TWRP Nexus5 main thread here .
Regards
Koetermann
Click to expand...
Click to collapse
Yep. Everyone should use this advice.
Sent from my Nexus 5 using Tapatalk
mrakifa said:
Every time I do it, wipes my imei and I have to flash the factory image...I'm actually looking for a twrp flashable cwm file if that makes any sense
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which factory image do you use? I just ran into this issue and it's driving me nuts.
I wish I would have found this thread sooner. I just wiped my internal storage and IMEI doing this. I have a backup of my IMEI, but restoring it with TWRP doesn't seem to do anything.
Will restoring the factory image fix this, or do I need to do that and restore this backup?
SO if you change it to rm-rf it doesn't bork your cell connection? I know it'll wipe faster but still leary on cell connection. Or is it that this only happens if you make the mistake of rebooting instead of waiting???? I'm wanting to jump on SlimKat and coming from an Evo LTE the procedure to clean wipe I'm familiar with is wiping system/data/cache/davlik cache so I've been holding off worried about the cache part. I've been using 2.6.3.2
Why would wiping cache screw up your cell connection? And how does this wipe your entire phone?
sent from my beantastic almost retired Bionic
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