Related
Okay, today I was about to flash a new rom so I attempted to wipe, but I got an error that the phone could not mount the cache (and later couldn't mount data). It says "E:Can't mount CACHE:recovery/command" on the next line "E:Can't mount CACHE:recovery/log" and the next "E:Can't open CACHE:recovery/log". So I have tried reflashing recovery to fix it and it did not work. I cannot flash any rom without an error or restore my nandroid backups. I am in the process of trying to restore the nandroid backups throught fastboot. Can anyone give me any help on this?
SOLUTION: blancoisgod recommends formatting the cache partition to fix this problem
Did you pull the battery and retry?
Yep. Actually, the phone wont even turn on anymore. I will just have to return it to tmobile tomorrow
toby4059 said:
Yep. Actually, the phone wont even turn on anymore. I will just have to return it to tmobile tomorrow
Click to expand...
Click to collapse
This is exactly why manufacturers don't want people rooting and messing with their phones.
So because of your stupidity and lack of foresight you're now going to return your phone?! That's laughable.
Now T-Mobile and HTC have to pick up the bill for someone else's ignorance.
Note to self....remember your name and never help you!
No man dont turn it into tmobile. Now everyone is gonna ride you because you broke it and your going to return it because of what you have done,not the manufacturer.
Go ahead and turn it in, but please read around a bit before you do this again.
CBConsultation said:
This is exactly why manufacturers don't want people rooting and messing with their phones.
So because of your stupidity and lack of foresight you're now going to return your phone?! That's laughable.
Now T-Mobile and HTC have to pick up the bill for someone else's ignorance.
Note to self....remember your name and never help you!
Click to expand...
Click to collapse
Your right it is my fault; although, I am not sure what I did wrong. I am not a complete idiot and have been doing this stuff for a while. I did everything by the instructions and this happened. I actually saw this happen to someone in the G2 forum but no one found a solution. I see how returning the phone would be wrong but what are my options? I am only 15, no income, so what could I do. If I had income of course I would just pay for a new phone. I hope I am not coming off as a dumb juvenile crook, I apologize.
toby4059 said:
Your right it is my fault; although, I am not sure what I did wrong. I am not a complete idiot and have been doing this stuff for a while. I did everything by the instructions and this happened. I actually saw this happen to someone in the G2 forum but no one found a solution. I see how returning the phone would be wrong but what are my options? I am only 15, no income, so what could I do. If I had income of course I would just pay for a new phone. I hope I am not coming off as a dumb juvenile crook, I apologize.
Click to expand...
Click to collapse
Did you make a backup image? If so you could just flash your recovery image and be golden. If not, then your options are very limited.
I was not trying to hurt or insult your feelings but we constantly see people who 'think' they know what they're doing with these same issues all day every day.
My advice is limited as well at this point because I'm not sure exactly what you've done or precautions you had in place for this.
Can you even boot into the OS at all? Do a factory reset?
CBConsultation said:
Did you make a backup image? If so you could just flash your recovery image and be golden. If not, then your options are very limited.
I was not trying to hurt or insult your feelings but we constantly see people who 'think' they know what they're doing with these same issues all day every day.
My advice is limited as well at this point because I'm not sure exactly what you've done or precautions you had in place for this.
Can you even boot into the OS at all? Do a factory reset?
Click to expand...
Click to collapse
I cannot turn the phone on what so ever. I was flashing my backup through fastboot then tried to reboot and now it will no longer turn on. I fastboot erased recovery, system, userdata, and boot and restored them from the nandroid backup I had taken prior to the error. The day prior I had rooted successfully and flashed the desire z port. I decided I wanted to try the HD port so I wiped and flashed the rom. When I rebooted it got to the lockscreen and it showed some graphical corruption then began to boot loop. I turned it off and went to recovery and thats when the CACHE errors started. Was I supposed to wipe the dav cache because I am pretty sure I did. I just want to find out what I did wrong so it won't happen to me or anyone else.
toby4059 said:
I cannot turn the phone on what so ever. I was flashing my backup through fastboot then tried to reboot and now it will no longer turn on. I fastboot erased recovery, system, userdata, and boot and restored them from the nandroid backup I had taken prior to the error. The day prior I had rooted successfully and flashed the desire z port. I decided I wanted to try the HD port so I wiped and flashed the rom. When I rebooted it got to the lockscreen and it showed some graphical corruption then began to boot loop. I turned it off and went to recovery and thats when the CACHE errors started. Was I supposed to wipe the dav cache because I am pretty sure I did. I just want to find out what I did wrong so it won't happen to me or anyone else.
Click to expand...
Click to collapse
Between ROM's, you said you wiped. What did you wipe? Cache? Dalvik? Partition?
You said you're not too sure so I am going to assume you either didn't wipe something you should have or you did wipe something you shouldn't have.
Try this. Remove the battery for 10 minutes. When the battery is removed, hold the power button for about 2 minutes. This will drain any residual current left on the board. After the 10 minutes are up, try reinserting the battery, hold the volume- button and try to power on. We'll see if you can manage to boot into recovery at this point.
CBConsultation said:
Between ROM's, you said you wiped. What did you wipe? Cache? Dalvik? Partition?
You said you're not too sure so I am going to assume you either didn't wipe something you should have or you did wipe something you shouldn't have.
Try this. Remove the battery for 10 minutes. When the battery is removed, hold the power button for about 2 minutes. This will drain any residual current left on the board. After the 10 minutes are up, try reinserting the battery, hold the volume- button and try to power on. We'll see if you can manage to boot into recovery at this point.
Click to expand...
Click to collapse
Okay I will give that a try thanks.
I had the same error just right now man
What you want to do is format the cache partition when you get the thing booted.
blancoisgod said:
I had the same error just right now man
What you want to do is format the cache partition when you get the thing booted.
Click to expand...
Click to collapse
Did you do that and did it fix? I did that through adb and thats when it stopped booting, although I think the boot issue is unrelated to my current problem.
i did it via clockwork
Alright, I will try this if I can ever get my phone started again.
Simple question, one i didn't find a quick simple answer too.
I know the main differences between one-click root and unlocking the bootloader, and the biggest for me was the warranty. I used one-click root so just in case, I could revert back. Now my warranty is just about up, and I figure why not? My biggest question is, will it provide any benefits?
For some reason I have never been able to install themes (either update.zip files or through metamorph), I just go into an infinite boot loop. I was hoping this was the only issue. But I don't know enough to know the answer
Benefits are safer radio flashing, and if you ever **** the phone up so bad you can't boot into anything other than the bootloader, you can fastboot flash everything required to get going again.
Rusty! said:
Benefits are safer radio flashing, and if you ever **** the phone up so bad you can't boot into anything other than the bootloader, you can fastboot flash everything required to get going again.
Click to expand...
Click to collapse
One more little question; Should i reflash CM7 (im running the nightlies currently) when its done? I read that it will wipe all data (already got everything backed up ready to go) but I was just wondering if I would need to reflash anything right now, like CM7 or the recovery?
Take NANDroid, unlock, restore NANDroid, continue as if nothing happened.
Rusty! said:
Take NANDroid, unlock, restore NANDroid, continue as if nothing happened.
Click to expand...
Click to collapse
Tons of awesomesauce I guess thats what I will go ahead and do! Thank you so very much for the quick help!
EDIT: Done, restoring the NANDroid backup now I hesitated a little bit when hitting that button though, a year of me holding back doing it because of the warranty was still making my trigger finger nervous
... And back in my rom, everything normal once again And again thanks for the quick help.
Well not so normal; I have lost my setup accounts, and everytime I try restoring a NANDroid the accounts are still gone, and there isn't an option to add in a google account and none of the google apps work. No force closes just closes the second you try to open it.
I have tried reflashing both the rom and gapps, still no good.
Am i going to need to wipe?
Certainly shouldn't do, I unlocked my bootloader in the same way and everything continued as normal.
Bit odd that you can't add your account back though, the option should be there under accounts & sync.
It sounds like what happens when you try and use CM without adding GApps
That's what I thought too. So I tried flashing gapps, nothing.
Went ahead and did a full wipe. Quite amazed so far what all android is restoring for me. Nearly all back
Sent from my Nexus One using XDA App
There are many stories here on XDA Note about wierd problems. They appear and disappear without much sense how.
On Nexus One, if you do a wipe and install a ROM on 5 different phones with different use then each will be identical after wipe/install.
Galaxy Note seems to be different. How do you do a true wipe so 5 phones with same hardware but wierdly defective firmware will be the same after?
The Note is awesome but these wierd problems really let it down for many of us.
Wifi overheat, GPS wakelocks, USB charging failing, hot screen, etc. When a problem comes but then just goes away you know it was never a hardware problem. It was a software problem. The software at the very bottom is the firmware. Its probably the culprit of wierdness.
Can we "true wipe" and get a defective unit into the as new condition that was intended?
Sent from my GT-N7000 using xda premium
What?
GALAXY NOTE
^^^+1 to WHAT???..lol
I think the OP wants to know on how to properly wipe a galaxy note as based on his observation some users fix issues by performing a wipe before installing a firmware while others can never get to fix it with just 1 wipe.
@OP
I know what you mean but I mostly blame the custom firmware used especially when I got back to full stock and I dont see the same rubbish issue. When I perform a wipe I always do it 3 times. Thats out of habit from the Galaxy S and Galaxy S2 days.
I may not have wrote clearly
There are a lot of threads about a lot of different types of problems which a lot of different people have also had. Problems like overheating coming from the wifi. Problems with wakelocks coming from the GPS. And many others.
For some people the phone is fine, and then a problem comes from no where. They wipe and wipe and it doesn't go away after wiping and flashing many different roms. Then one time for no known reason flashing something does make the problem go away. but why not earlier?
Personally I had the same problem when I flashed CM9 alpha. Upon booting it came up with some kind of error that it couldn't open wssyncmlps. I wiped and flashed another ROM but the error didn't go away. Flashed a couple more different ROMs and still the error. Eventually I did a recovery and that got rid of the error.
I would have thought a factory wipe would fix that. But it didn't. That proved a factory wipe DIDN'T REALLY wipe everything.
My housemate just got back from the Android DevCon today in Melbourne. Maybe I should have got him to ask one of the Google engineers about it LOL
I may not have wrote clearly
There are a lot of threads about a lot of different types of problems which a lot of different people have also had. Problems like overheating coming from the wifi. Problems with wakelocks coming from the GPS. And many other common and uncommon problems.
For some people the phone is fine, and then a problem comes from no where. They wipe and wipe and it doesn't go away after wiping and flashing many different roms. Then one time for no known reason flashing something does make the problem go away. but why not earlier?
Personally I had the same problem when I flashed CM9 alpha. Upon booting it came up with some kind of error that it couldn't open wssyncmlps. I wiped and flashed another ROM but the error didn't go away. Flashed a couple more different ROMs and still the error. Eventually I did a recovery and that got rid of the error.
I would have thought a factory wipe would fix that. But it didn't. That proved a factory wipe DIDN'T REALLY wipe everything. Maybe its a fault with the recovery software? Maybe this new RedPill recovery software that Angelom has put into Abyss 3.5 will help? I wonder. I'm flashing Rocket V21 now to see what happens...
My housemate just got back from the Android DevCon today in Melbourne. Maybe I should have got him to ask one of the Google engineers about it LOL
PurpleMelbourne said:
I may not have wrote clearly
There are a lot of threads about a lot of different types of problems which a lot of different people have also had. Problems like overheating coming from the wifi. Problems with wakelocks coming from the GPS. And many other common and uncommon problems.
For some people the phone is fine, and then a problem comes from no where. They wipe and wipe and it doesn't go away after wiping and flashing many different roms. Then one time for no known reason flashing something does make the problem go away. but why not earlier?
Personally I had the same problem when I flashed CM9 alpha. Upon booting it came up with some kind of error that it couldn't open wssyncmlps. I wiped and flashed another ROM but the error didn't go away. Flashed a couple more different ROMs and still the error. Eventually I did a recovery and that got rid of the error.
I would have thought a factory wipe would fix that. But it didn't. That proved a factory wipe DIDN'T REALLY wipe everything. Maybe its a fault with the recovery software? Maybe this new RedPill recovery software that Angelom has put into Abyss 3.5 will help? I wonder. I'm flashing Rocket V21 now to see what happens...
My housemate just got back from the Android DevCon today in Melbourne. Maybe I should have got him to ask one of the Google engineers about it LOL
Click to expand...
Click to collapse
Erase = removing the entry that leads to that data on the storage medium.
The data are there till the get overwrite by something. Even you format/wipe/clear you may get the data on your next install/reboot when the OS scans your medium.
Sent from my GT-N7000 using Tapatalk
Maybe under CWM you need to format system then format data would help ?
What!!!??!!!!!
Braxos said:
Erase = removing the entry that leads to that data on the storage medium.
The data are there till the get overwrite by something. Even you format/wipe/clear you may get the data on your next install/reboot when the OS scans your medium.
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
so a format command in android is equal to a quick format in windows only removing the file index? where did you get this info?
Sent from my GT-N7000 using xda premium
If you want to erase all personal information or personal usage history on a desktop or laptop then you need specialist software which overwrites everything.
So it is unreasonable to be disappointed if the Note does not do it and I suspect no other Palmtop does it either.
As far as weird defects goes, Samsung only guarantees the Note will work providing it has only ever used the official ROM for the region.
Gaugerer said:
If you want to erase all personal information or personal usage history on a desktop or laptop then you need specialist software which overwrites everything.
Click to expand...
Click to collapse
your talking about recovering lost files that's not the issue for instance a laptop never accidentally sees deleted files as not deleted
Gaugerer said:
So it is unreasonable to be disappointed if the Note does not do it and I suspect no other Palmtop does it either.
Click to expand...
Click to collapse
you mean a Phone right? ;-)
Gaugerer said:
As far as weird defects goes, Samsung only guarantees the Note will work providing it has only ever used the official ROM for the region.
Click to expand...
Click to collapse
but THIS place is mostly about custom stuff i guess that's why its posted her and not emailed to Samsung support
/Jeriz
jeriz said:
you mean a Phone right? ;-)
Click to expand...
Click to collapse
No I mean a Palmtop running a phone app amongst many others
but THIS place is mostly about custom stuff i guess that's why its posted her and not emailed to Samsung support
Click to expand...
Click to collapse
Click to expand...
Click to collapse
THIS place is the sub-forum for general chat and is NOT mostly about custom stuff.
/Jeriz[/QUOTE]
Gaugerer said:
THIS place is the sub-forum for general chat and is NOT mostly about custom stuff.
Click to expand...
Click to collapse
got me there
/Jeriz
but does anyone know if a cwm wipe actually does format or just deletes?
/Jeriz
jeriz said:
got me there
/Jeriz
Click to expand...
Click to collapse
What a gracious light-hearted response and much appreciated
Well im not actually an ass im just posing as one to blend in
/Jeriz
I think wiping the phone is a very common problem/conundrum for users.
I am in the process of wiping and installing rocketrom 21, and I find that not everything specific to me has been wiped -after a "factory data reset", and a CWM "wipe data/factory reset" and a "wipe cache partition". E.g. right now I'm going into the sd card, using cwm, and finding a long list of folders from apps that I've long since uninstalled. These "wipe/reset" options don't seem to touch them.
Can somebody who knows how these things really work shed some light on... what specifically wipes what?
One last thing, optional: If I find an option to wipe every single partition on the device, how do I then get a ROM on there afterwards? Do I put it in download mode and plug it into my computer and use ODIN? Again only an expert would know.
maybe it is a defective unit....
trumpetboy101 said:
I am in the process of wiping and installing rocketrom 21, and I find that not everything specific to me has been wiped -after a "factory data reset", and a CWM "wipe data/factory reset" and a "wipe cache partition". E.g. right now I'm going into the sd card, using cwm, and finding a long list of folders from apps that I've long since uninstalled. These "wipe/reset" options don't seem to touch them.
Click to expand...
Click to collapse
The internal SD is never wiped as part of a factory reset or wipe - this is by design, as it is considered to be 100% user data, just as if it were a real user replaceable SD card.
In order to clear the internal SD, you can reformat from the storage menu, or flash another ROM via Odin with a PIT file.
Regards,
Dave
Sent from my Transformer Prime TF201 using Tapatalk
Folks,
I've been running the ICS Kang project build without any issues (2.3) for the past while. Last night the tablet locked up on me and I powered it off by holding down the on/off button. When I went to turn it back on it now permanently hangs during boot. I can still get into CWM but attempting to wipe either the D. Cache or data hangs. Anyone got any ideas?
Can you restore a backup?
If you can't do anything in CWM then you might have to Odin back to stock....
I can flash a new rom but there appears to be something wrong with the data partition - can't wipe it and tablet wont boot.
You don't happen to have a link to restoring tab via ODIN? I was just browsing for that...
powercrazy said:
I can flash a new rom but there appears to be something wrong with the data partition - can't wipe it and tablet wont boot.
You don't happen to have a link to restoring tab via ODIN? I was just browsing for that...
Click to expand...
Click to collapse
http://www.teamovercome.net/p7500/?page_id=5
Scroll down to where is says Re-Stocking Yer System and follow the instructions.. Make sure you choose the correct download (7500 or 7510)
Thanks - I'll let you know what happens.
Its bizarre, flashed roms lots of times, never had an issue even close to this...
powercrazy said:
Thanks - I'll let you know what happens.
Its bizarre, flashed roms lots of times, never had an issue even close to this...
Click to expand...
Click to collapse
No problem... It should go nice and smooth and once it boots back up check in settings for system updates..
Well, thanks! That did the trick! I am back to the stock Samsung firmware and have already reflashed clockwork. I really don't know what went wrong in the first place, but I suppose that's what you get for living on the 'alpha' edge...
Thanks again! (BTW I did click the 'thanks' button ;-) )
BTW - for anyone interested or suffering a similar problem, in the end this required a full reset - all data was lost which sucked for me as I had all my backups on the device too (don't bother calling me stupid, I've already done it)....
I'm guessing some bug in the ICS KANG alpha screwed the partitions up which nothing short of a full reset could fix...
Sweet! Glad you are back up and rockin'...
phew!
I had exactly the same problem yesterday, and I thought my tab was completely fubar until I came across this post.
I was running the "official unofficial" CM9 snapshot for p4wifi, and before that I ran AOPK build 27, I think. I did not perform a full wipe before going to CM9.
I change roms on my tab very often to try to find the best, so something must have gotten messed up, but it's somewhat odd since it worked in the morning, and then when I came to work it had totally b0rked up on me.
Anyway, this post was a life saver although I lost all my data (didn't keep a titanium backup or a CWM backup on another storage than the internal storage. shame on me).
So - thanks alot raqball!
Br,
primpa
primpa said:
I had exactly the same problem yesterday, and I thought my tab was completely fubar until I came across this post.
I was running the "official unofficial" CM9 snapshot for p4wifi, and before that I ran AOPK build 27, I think. I did not perform a full wipe before going to CM9.
I change roms on my tab very often to try to find the best, so something must have gotten messed up, but it's somewhat odd since it worked in the morning, and then when I came to work it had totally b0rked up on me.
Anyway, this post was a life saver although I lost all my data (didn't keep a titanium backup or a CWM backup on another storage than the internal storage. shame on me).
So - thanks alot raqball!
Br,
primpa
Click to expand...
Click to collapse
Never understood why people don't do a full wipe and expect nothing to go wrong.
Sent from my GT-P7510 using XDA Premium HD app
Hehe, well, I usually do a wipe but this time I read somewhere that you probably didn't need to when going from aokp to cm9, since they are pretty much the same.
But..... Lesson learned
/primpa
primpa said:
Hehe, well, I usually do a wipe but this time I read somewhere that you probably didn't need to when going from aokp to cm9, since they are pretty much the same.
But..... Lesson learned
/primpa
Click to expand...
Click to collapse
Understandable... but unless the Dev. says no wipe needed, I would always suggest it, even when it's virtually the same ROM, thread, Dev., etc...
At least it wasn't too hard of a lesson.
Sent from my GT-P7510 using XDA Premium HD app
Last night my phone wanted to update to 4.4.4 because it's been wanting to for a while, but I know it wouldn't work because my phone is rooted. It had tried this at least 3 times before and everything was fine; download update, tries to install, fails, boots right back up. I wanted to get rid of the Update notification in the top bar, so I just ran it again thinking it'd be okay. Well, this time it bricked my phone, leaving me at a neverending loop at the boot animation. I first tried to wipe the cache and dalvik cache, which did nothing. Then I tried a factory restore, which also did nothing. Then I reinstalled the stock 4.4.3 rom I had been using, which did nothing. Then I wiped the SD card completely and reinstalled a stock 4.4.4 rom through sideload, which has done nothing. My phone just sits at the boot animation and taunts me. Worse yet, I have a 16-hour drive tomorrow and my phone was going to be the majority of my sanity during that time.
What should I do?? Is there anything I can do? Normally I would just contact Google to get a replacement (I've done this before when the 4.2 update was causing a lot of bricks,I think it was 4.2 anyway, I forgot) but I'd like to have a working phone for my 16 hour trip..... if possible. Any help would be greatly appreciated! Thank you.
Well, I never had heard of any devices that still stuck in the bootanimation after flashing the factory image. There is something really wrong.
Did you already tried flashing a custom rom? Can you boot into recovery?
CCody said:
Well, I never had heard of any devices that still stuck in the bootanimation after flashing the factory image. There is something really wrong.
Did you already tried flashing a custom rom? Can you boot into recovery?
Click to expand...
Click to collapse
I had a Vanir 4.4.3 rom on my phone that I tried to flash as well, but for some reason it went right into "Optimizing Apps" after the first boot, something I hadn't seen before. Then it got stuck at "Starting Apps...", then after a restart, it too was stuck at the boot animation.
I can boot into recovery luckily, but that's all I can do. I have CWMR v6.0.3.5. I've tried just about everything I can think of. [edit] I was able to contact Google for some live chat support and am now #2 in the queue. Hopefully they can either help me or get a replacement going. Either way, I'd still love any help you guys can give me, I'd really like to get it fixed rather than waiting for a replacement.
Okay, try this: Wipe everything via recovery and with everything i mean really everything! Cache, dalvik, storage, your whole system. There must be nothing left on your phone. Then flash a rom of your choice. Wipe cache and dalvik afterwards and see if it works
CCody said:
Okay, try this: Wipe everything via recovery and with everything i mean really everything! Cache, dalvik, storage, your whole system. There must be nothing left on your phone. Then flash a rom of your choice. Wipe cache and dalvik afterwards and see if it works
Click to expand...
Click to collapse
I've done that already, Factory Reset + wipe cache + wipe dalvik cache + format system/data/cache/sdcard/data/media. The phone was completely bare and that's when I sideloaded the stock 4.4.4 rom (otherwise it's stuck at the Google boot screen). I'll try it again, though.
Okay right now I'm using the Nexus Toolkit to flash the stock 4.4.4 .tgz image directly from google and unroot my phone (checking the option that the phone is Soft-bricked/Bootloop.
....Okay that finished and I'm still stuck at the boot animation and now I don't have CWMR. ****. [EDIT] But I can still boot into a custom recovery through the toolkit, which is good.
RawrNate said:
Okay right now I'm using the Nexus Toolkit to flash the stock 4.4.4 .tgz image directly from google and unroot my phone (checking the option that the phone is Soft-bricked/Bootloop.
....Okay that finished and I'm still stuck at the boot animation and now I don't have CWMR. ****. [EDIT] But I can still boot into a custom recovery through the toolkit, which is good.
Click to expand...
Click to collapse
Damn, I really am stumped right now. That's really strange. Normally everything should be fine after a factory reset...
I've search several threads with bootloop problems, but none of them have this persistent bootloop. I believe you have damage your storage somehow, so that the system can't read the files and boot up properly. Maybe because of this 4.4.4 OTA update. Man, that's kinda sucks right now...
CCody said:
Damn, I really am stumped right now. That's really strange. Normally everything should be fine after a factory reset...
I've search several threads with bootloop problems, but none of them have this persistent bootloop. I believe you have damage your storage somehow, so that the system can't read the files and boot up properly. Maybe because of this 4.4.4 OTA update. Man, that's kinda sucks right now...
Click to expand...
Click to collapse
Yeah haha, it's really really strange. I appreciate you trying to help me, though! Lucky for me I'm getting a "One-time exception replacement" since my warranty is expired but they must be super stumped with the issue as well xD
I forgot something! Did you also flashed the 4.4.4 binaries?
https://developers.google.com/android/nexus/drivers#makoktu84p
I also read somewhere, that the LG Fashtool may help.
Try this out!
CCody said:
I forgot something! Did you also flashed the 4.4.4 binaries?
https://developers.google.com/android/nexus/drivers#makoktu84p
I also read somewhere, that the LG Fashtool may help.
Try this out!
Click to expand...
Click to collapse
Hm, I didn't think I'd need to with the factory image, but I'll try that. I tried the 4.4.3 factory image as well but that didn't work either. I also can't find anything about the LG Flashtool that's Nexus 4 specific, but I'll try to look more into it.
Wait, how do I flash the binaries since they're .tgz files?
RawrNate said:
Hm, I didn't think I'd need to with the factory image, but I'll try that. I tried the 4.4.3 factory image as well but that didn't work either. I also can't find anything about the LG Flashtool that's Nexus 4 specific, but I'll try to look more into it.
Click to expand...
Click to collapse
This is really strange man. Flashing stock ROM is the last resort but even that seems to be failing for you.
Have you tried downloading the stockRom again (just to make sure it isn't corrupted). Also, maybe you can try using TWRP instead of CWM this time.
Good luck.
RawrNate said:
Wait, how do I flash the binaries since they're .tgz files?
Click to expand...
Click to collapse
No need to flash them, since you are on a factory image, sry.
Woah now, I've made progress! Maybe.... Anyway, in TWRP, I "fixed permissions" and mounted "system" but now I'm at the "Android is Upgrading, Optimizing Apps - Starting Apps" screen again (it only had to optimize 23 apps?). I was at this issue before when I was flashing roms last night trying to fix it, but going back to here is better than not getting it to boot at all. What else should I try next?
Note: I'm on the 4.4.4 factory image now and TWRP is just temporary through the Nexus Root Toolkit.
RawrNate said:
Woah now, I've made progress! Maybe.... Anyway, in TWRP, I "fixed permissions" and mounted "system" but now I'm at the "Android is Upgrading, Optimizing Apps - Starting Apps" screen again (it only had to optimize 23 apps?). I was at this issue before when I was flashing roms last night trying to fix it, but going back to here is better than not getting it to boot at all. What else should I try next?
Note: I'm on the 4.4.4 factory image now and TWRP is just temporary through the Nexus Root Toolkit.
Click to expand...
Click to collapse
And? Did it boot up or just stuck in 'optimizing apps'? I would suggest to try another android version, like 4.3 or 4.4.2 at least.
CCody said:
And? Did it boot up or just stuck in 'optimizing apps'? I would suggest to try another android version, like 4.3 or 4.4.2 at least.
Click to expand...
Click to collapse
30 minutes later and it's still at "Starting apps..."
I tried factory images of 4.4.3 and 4.3, still nothing.
RawrNate said:
30 minutes later and it's still at "Starting apps..."
I tried factory images of 4.4.3 and 4.3, still nothing.
Click to expand...
Click to collapse
Jesus!
What about custom ROM? Cyanogenmod maybe? Make sure to downlaod the M7-Release.
Hm, alright, I'll give that a shot.
On a side note, is there a way to lock the bootloader again while in either recovery or bootloader? I fear that if it's unlocked, I won't get the $250 refund for the replacement.
RawrNate said:
Hm, alright, I'll give that a shot.
On a side note, is there a way to lock the bootloader again while in either recovery or bootloader? I fear that if it's unlocked, I won't get the $250 refund for the replacement.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=tZbvuikfnks
CCody said:
https://www.youtube.com/watch?v=tZbvuikfnks
Click to expand...
Click to collapse
Oh good that was easier than I thought xD