Hi
I record updating to 4.3 without removing root (I just lost it and the recovery asked if I wanted to redo it), so I decided to try the samething with 4.4. Well, things got very bad.
After I got the notification that 4.4 was available, I clicked to download it, the phone then rebooted and I installed it via the recovery.
Then Android booted and got stuck after Google's logo (balls moving) for more than 5 minutes, so I decided something was wrong and shut it down.
So far I tried going to adb shell and mounting sdcard (so I could make a backup), but apparently fstab had /sdcard datamedia /dev/null (huh?)
Then I tried to adb sideload 4.3 and 4.4 (from https://developers.google.com/android/nexus/images ), and both failed for different reasons (4.3 just said "(bad)", 4.4 said something with "set_meta_recursive").
Then I did a "fastboot oem unlock" (please don't tell me this lose all the data - including sdcard) and retried that. Also didn't work.
(I cleaned cache before trying)
Then I found some tutorials telling to "fastboot flash bootloader/radio/...", but those versions (4.3 and 4.4) from the site above doesn't have files named "bootloader-mako-makoz20i.img" or so. I could find it for 4.2 (makoz10), so I tried with that and it apparently worked. Except also got on boot loop (different logo).
Then I downloaded an image that was on a link for 4.3 that had makoz20, so I tried with that and got the same result (it worked, but got on boot loop).
Now even recovery isn't working anymore.
I was careful to not run "fastboot -w" (or flash-all.sh) and/or to delete userdata.img from the .zip, so I have some hope I didn't lose all data.
Any hints on how to proceed from here?
thanks!
Lem0nHead said:
Hi
I record updating to 4.3 without removing root (I just lost it and the recovery asked if I wanted to redo it), so I decided to try the samething with 4.4. Well, things got very bad.
After I got the notification that 4.4 was available, I clicked to download it, the phone then rebooted and I installed it via the recovery.
Then Android booted and got stuck after Google's logo (balls moving) for more than 5 minutes, so I decided something was wrong and shut it down.
So far I tried going to adb shell and mounting sdcard (so I could make a backup), but apparently fstab had /sdcard datamedia /dev/null (huh?)
Then I tried to adb sideload 4.3 and 4.4 (from https://developers.google.com/android/nexus/images ), and both failed for different reasons (4.3 just said "(bad)", 4.4 said something with "set_meta_recursive").
Then I did a "fastboot oem unlock" (please don't tell me this lose all the data - including sdcard) and retried that. Also didn't work.
(I cleaned cache before trying)
Then I found some tutorials telling to "fastboot flash bootloader/radio/...", but those versions (4.3 and 4.4) from the site above doesn't have files named "bootloader-mako-makoz20i.img" or so. I could find it for 4.2 (makoz10), so I tried with that and it apparently worked. Except also got on boot loop (different logo).
Then I downloaded an image that was on a link for 4.3 that had makoz20, so I tried with that and got the same result (it worked, but got on boot loop).
Now even recovery isn't working anymore.
I was careful to not run "fastboot -w" (or flash-all.sh) and/or to delete userdata.img from the .zip, so I have some hope I didn't lose all data.
Any hints on how to proceed from here?
thanks!
Click to expand...
Click to collapse
You may have missed this.. http://www.xda-developers.com/android/how-to-fix-a-broken-rom-flash-in-certain-kitkat-roms/
ravindrank said:
You may have missed this.. http://www.xda-developers.com/android/how-to-fix-a-broken-rom-flash-in-certain-kitkat-roms/
Click to expand...
Click to collapse
I am facing the same problem. The bootloader is stuck in a loop. Is there any way to recover the stock android??
true! It's interesting how google doesn't show results if you put it on quotes ("set_metadata_recursive: some changes failed")
gonna try that, thanks!
hm, well
I tried flashing using fastboot now (following method D on http://forum.xda-developers.com/showthread.php?t=2010312 ), so I guess set_metadata_recursive or something like that doesn't matter
it flashed correctly, but it still doesn't work (now I get stuck in black screen after google's logo)
oops, sorry. not black screen (I forgot to flash system), not it's stuck on the 4 balls animation, as it was right after the update ;(
you did a factory reset prior to booting and after flashing?
playya said:
you did a factory reset prior to booting and after flashing?
Click to expand...
Click to collapse
no, I'm trying to avoid losing data
since nexus 4 sdcard isn't removable (and now I'm regretting have accepted that), is there anyway to save my data?
as I said, I tried mounting it, but for some reason /sdcard is pointing to /dev/null no fstab.
Now I already flashed the stock recovery, so maybe I need to flash something else to try that again, but is there anything I can do differently?
thanks
Lem0nHead said:
no, I'm trying to avoid losing data
since nexus 4 sdcard isn't removable (and now I'm regretting have accepted that), is there anyway to save my data?
as I said, I tried mounting it, but for some reason /sdcard is pointing to /dev/null no fstab.
Now I already flashed the stock recovery, so maybe I need to flash something else to try that again, but is there anything I can do differently?
thanks
Click to expand...
Click to collapse
stock recovery wipe data and may I ask you what do you think you are going to lose? You are only going to lose apps and app data not photos or files which honestly you should have a free dropbox and save everything on there for the reason mentioned before... NO SDCARD
hm, maybe it's related with encryption I'd set from Security? I know the password, but it doesn't ask me for it anywhere
Lem0nHead said:
hm, maybe it's related with encryption I'd set from Security? I know the password, but it doesn't ask me for it anywhere
Click to expand...
Click to collapse
man just do a wipe...
playya said:
man just do a wipe...
Click to expand...
Click to collapse
I think currently I'm more worried with not losing data than with getting my phone back working.
Sorry, but I find it ridiculous that it isn't easy to extract data from your phone easily. Even if it's encrypted, as long as I know the password there should be a tool to help with that.
Apparently there might be something like "recovery --set_encrypted_filesystem=off" (on adb shell), but I'm getting "sh: /sbin/postrecoveryboot.sh: not found", so no luck yet
Lem0nHead said:
I think currently I'm more worried with not losing data than with getting my phone back working.
Sorry, but I find it ridiculous that it isn't easy to extract data from your phone easily. Even if it's encrypted, as long as I know the password there should be a tool to help with that.
Apparently there might be something like "recovery --set_encrypted_filesystem=off" (on adb shell), but I'm getting "sh: /sbin/postrecoveryboot.sh: not found", so no luck yet
Click to expand...
Click to collapse
what data are you trying to save?
playya said:
what data are you trying to save?
Click to expand...
Click to collapse
encrypted files on /sdcard
Lem0nHead said:
encrypted files on /sdcard
Click to expand...
Click to collapse
wipe/data factory reset from custom recovery has nothing to do with sdcard based files. Its only going to delete any files in your data portion of your rom and not your sdcard. area... two completely different things, have you done your research on android and how everything works. Its good to search and read up on this stuff especially since its interesting and you apparently need a few answers to your questions
playya said:
factory reset has nothing to do with sdcard based files. Its only going to delete any files in your data portion of your rom and not your sdcard area
Click to expand...
Click to collapse
are you sure this stands for nexus 4, which have just an internal sdcard?
Lem0nHead said:
are you sure this stands for nexus 4, which have just an internal sdcard?
Click to expand...
Click to collapse
come on man this aint my first rodeo and do you think every time you did a factory reset it was going to delete your music? Do some research my man there are multiple wipes and an Internal SD Card wipe will delete everything but a factory reset with a custom recovery or factory will only reset your settings to factory
playya said:
Its good to search and read up on this stuff especially since its interesting and you apparently need a few answers to your questions
Click to expand...
Click to collapse
well, as I said before, I was following http://forum.xda-developers.com/showthread.php?t=2010312
it says "this command will wipe your device (including /sdcard)"
maybe this isn't true, but I guess it's a trusted thread
Lem0nHead said:
well, as I said before, I was following http://forum.xda-developers.com/showthread.php?t=2010312
it says "this command will wipe your device (including /sdcard)"
maybe this isn't true, but I guess it's a trusted thread
Click to expand...
Click to collapse
hold on let me take a look now that might be a different procedure I am referring to a wipe from recovery but in your case a full wipe may be necessary
hm, I didn't try any kind of wipe
so which one is safe (so I can try at least)? "wipe data / factory reset" from recovery?
Related
I encrypted my 10.1 yesterday without thinking all the way though. I found out that I could no longer flash kernels while the tablet is encrypted, since the SD card is not accessible in CWR.
I've tried doing a factory reset on my tab and each time, it boots up like nothing happened. I've also tried removing the pin that I put on it and the option to remove it is grayed out.
Do any of you know of a way to do a full wipe on the 10.1? Or could I reflash it using ODIN?
Thanks in advance.
id like to know this as well
still nothing? im starting to think this is an easy fix that nobody has posted about yet
there has to be something that im missing
try post # 6 in the linked thread, restore with unmodified vanilla version image from second link provided in the post, after booting from fastboot into recovery with clockworkmod recovery img; pushing it into the device sd with adb commandline, check the post for modifications and the link for details.
http://forum.xda-developers.com/showthread.php?t=1161325
whenever i try to reset to factory defaults, it just reboots like nothing happened
re-flash a stock firmware via odin as tar or fastboot/nandroid as img (backup restore)
Ones the tab is encrypted, there's no way to un do it. Unless you do what mughalgxt suggested. Good luck
Thanks guys, I went through some of these steps and found some other good tutorials to get me back up and running. All i wanted was to try the new kernel/bonsai rom out and I'm now able to do that
**** encryption, put a lockscreen password and be done with it.
I'm still struggling with this, as well: off to read some of the linked threads, because even with flashing a stock image with ODIN I'm still not able to recover the device. At least I managed to proceed past the boot loop I WAS in (when attempting to flash from CWM) - but now, I can get to the point where the device prompts me for the decryption key (meaning, it's clearly not yet restored to factory defaults) - but can't get it boot to completion. I also note that I've still got CWM Recovery, not stock.
It seems, at some point, encryption-key be damned, right? Meaning, if I don't care about recovering the contents of the encrypted partition - surely these low-level tools have the ability to simply format the partitions? Perhaps not - at least, not CWM - as attempts to format /data continue to fail.
Off to review the linked threads to try to gain some additional insight.
I ran into this same issue a long while back. As I recall (and it's been a while), you won't be able to wipe from CWM, but you can wipe from Settings / Privacy / Factory Data Reset. I could be wrong, but I know that I didn't have to do any adb pushing or anything with special images.
Hi SacTilt-
Thanks for the reply - and agreed: Had I actively started the effort from a functioning device, I think I could have selected that option.
As it turns out - I ran CWM, rebooted into recovery, and... next thing I knew, I was in boot loop hell.
I've tried flashing a variety of files via ODIN: Some at least allow the device to boot to the point where I get the initial password prompt - which I can provide, and proceed past... but then the device just 'goes blank'.
What I'm looking for is a 'start-from-scratch', no concern for data loss, delete the dang encrypted /data folder already, will ya?... approach.
As I've mentioned, a variety of ODIN files from a myriad of sources haven't seemed to quite do the trick. I feel like I'm missing something obvious - but can't find the right angle to spot it.
Perhaps fastboot might be what I'm looking for?
FWIW: the device was rooted when I started, so I've got full Titanium backups, with which I can restore, once I recover the actual device / OS.
Thanks for any insight.
Hey guys...if anybody finds a solution to this, please let me know...I am stuck with this same damn experimental ROM I've had from day one...it's getting really old. All I want is to get rid of this stupid encryption. Thanks for any help. Tried ODIN flashing, wiping data from security screen, wiping from CMR, etc.
Have you tried formatting the sd? Whenever i had my ns4g i accidentially did the same thing and i wiped the SD and it removed the encryption.
Sent from my GT-P7510 using XDA Premium HD app
Hi guys,
I tried to update my Nexus 4 to 4.4 when Google pushed the update out for it yesterday, I forgot I had unlocked the phone (I don't have any custom ROMs on it, just SuperSU.)
Every time I try and power it on, the loading screen is endless, although I can hold power and volume down to enter recovery mode, nothing seems to be working.
I am a bit of a novice so any help or suggestions would be really appreciated!
Thanks.
The first few pages of the forum is littered with posts like this, i was in the same situation.
What i did was download the 4.3 rom from google, and flash /boot and /system onto the phone. I suspect the 4.4 rom would also work.
This got the phone booting without harming (most of) my data, but much of the UI was mangled and didnt work properly. I tried to backup my images over USB but it didnt work, you might have a better result. I also wanted to backup my SMS but they had all vanished.
I rebooted the phone to recovery (TWRP) and used adb to backup the sdcard (adb pull /sdcard sdcard) then did a full flash using the 4.4 rom downloaded from google and that got it working again. Then i reflashed the latest version of TWRP recovery and SuperSU.
Hope that helps.
That's really helpful, thanks! Is there ANY chance of a step-by-step? I'm a complete 'noob' probably a mistake to root in the first place :crying:
If you're busy don't worry, just don't want to **** things up more than I have haha.
Thanks, appreciate it.
GeorgeAmodio said:
That's really helpful, thanks! Is there ANY chance of a step-by-step? I'm a complete 'noob' probably a mistake to root in the first place :crying:
If you're busy don't worry, just don't want to **** things up more than I have haha.
Thanks, appreciate it.
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
gee2012 said:
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
Click to expand...
Click to collapse
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
arffrhn said:
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
Click to expand...
Click to collapse
Cheers guys, a lot more helpful than the bloke from Google. Will try it in the morning!
This will surely help
If somebody is facing boot loop after kitkat update on nexus 4 and no data backup can try to go to safe mode and backup their data. To goto safe mode on boot screen just keep pressing up and down volume button for some time phone will get into safe mode and can be backed up.
Hi,
It also happened to me, dont know if it is related to having ROOT or not, but i had to manually flash factory image (4.4) and it worked. I flashed everything except userimage.img but on first boot it took like 15 minutes to reboot and then all my personal data (photo, music...) was gone....
So just be cautious before upgrading!
Hi,
It also happened to me, dont know if it is related to having ROOT or not, but i had to manually flash factory image (4.4) and it worked. I flashed everything except userimage.img but on first boot it took like 15 minutes to reboot and then all my personal data (photo, music...) was gone....
So just be cautious before upgrading!
gee2012 said:
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
Click to expand...
Click to collapse
Yeah that is pretty much what I did to fix mine except that I did not flash the userdata (step 10 in chapter D) so that I would't loose my data.
arffrhn said:
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
Click to expand...
Click to collapse
What did you end up doing for your PC to detect your phone?
iamj00 said:
What did you end up doing for your PC to detect your phone?
Click to expand...
Click to collapse
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
arffrhn said:
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
Click to expand...
Click to collapse
I don't know what any of that means or how to do it...
iamj00 said:
I don't know what any of that means or how to do it...
Click to expand...
Click to collapse
This is sideload guide. And the is the rom I used to sideload before: Purity. After I had successfully booted into the system. I flashed 4.4 factory images using this awesome noob friendly guide for a clean kitkat update.
arffrhn said:
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
Click to expand...
Click to collapse
iamj00 said:
What did you end up doing for your PC to detect your phone?
Click to expand...
Click to collapse
Installing the driver. Refer to this thread http://forum.xda-developers.com/showthread.php?t=1992345
Boot to bootloader and connect to your PC, usually Windows will find the driver automatically
What kind of method would I need to use to be able to get my phone back to stock? I tried to take the update, but failed, and then in a haste deleted all of my storage on the phone. I know that I need to use the OTG cable, but I'm not sure how to go about it. I put a .tot file on the root of a thumb drive to see if i could see it through TWRP but I couldn't. I am in a bootloop that goes straight to TWRP, but I don't have any files to flash to get it to boot up the rest of the way. Do I need to use the KDZ file instead? I have no experience using ADB either so if that is what I need to do, I definitely need assistance with it. Thanks in advance I hope?
No worries, nice and simple fix. Terminal command is awesome.
http://forum.xda-developers.com/showthread.php?t=2451696
Let us know how it goes!
asdfvtn said:
No worries, nice and simple fix. Terminal command is awesome.
http://forum.xda-developers.com/showthread.php?t=2451696
Let us know how it goes!
Click to expand...
Click to collapse
Where will this get me? I dont think I have any kind of rom or anything to boot to because I deleted my memory on accident after I was already in the bootloop. Does the stock rom still exist under everything despite wiping all of memory? Not just data but EVERYTHING (yes I know, I shouldn't have been so antsy while not being familiar with TWRP).
joshuaclogg said:
Where will this get me? I dont think I have any kind of rom or anything to boot to because I deleted my memory on accident after I was already in the bootloop. Does the stock rom still exist under everything despite wiping all of memory? Not just data but EVERYTHING (yes I know, I shouldn't have been so antsy while not being familiar with TWRP).
Click to expand...
Click to collapse
When you wiped, you selected dalvik, cache, and data, correct? If so, you'll be fine (If you truly wiped everything already, you wouldn't have TWRP anyway). The line from that link I posted simply deletes the OTA you downloaded. If you type it exactly as written, nothing else will be done to your phone. Be sure to triple check what you're typing though.
Feel free to keep looking around though if you like.
Best of luck
asdfvtn said:
When you wiped, you selected dalvik, cache, and data, correct? If so, you'll be fine (If you truly wiped everything already, you wouldn't have TWRP anyway). The line from that link I posted simply deletes the OTA you downloaded. If you type it exactly as written, nothing else will be done to your phone. Be sure to triple check what you're typing though.
Feel free to keep looking around though if you like.
Best of luck
Click to expand...
Click to collapse
Both of the methods there do the same? And I selected format data which now that I read is so far from what I wanted haha
joshuaclogg said:
Both of the methods there do the same? And I selected format data which now that I read is so far from what I wanted haha
Click to expand...
Click to collapse
Yeah, Both methods result in the same thing. Format data won't wipe everything.
Okay, so I feel like I've looked everywhere and tried everything for this problem with my Nexus 7. The closest thing I found was this:
(Google: Nexus 7 2012 rebooting reverts back to previous state)(I can't post outside links as I am a new member)
and there was no followup reply, and the thread was closed.
Here's my problem (I want to be very detailed in case I missed something):
I've had Cyanogenmod 11 on my Nexus 7 for a long time (I think I started with M1 release). I recently installed the M7 release after previous nightly and it was working so smooth that I had finally decided there was no need to install nighties anymore. Everything was going fine until the night after when I noticed it kept rebooting, so I reverted it back to the nightly I had before (June 11th?) because I assumed it was probably something bad with the update. Except it did the same thing, rebooting after a couple minutes, which is weird because it never did that with this nightly. There was never enough time to download the nightlies before it reboots so I tried downloading them on my laptop and then just transferring them to my nexus via usb. I put it in the cmupdate folder so that I could quickly go to settings and press install (as it can see the update from there). It rebooted to install, but it went into cwm with what appears that nothing happened, and I usually never see cwm when updating this way. So I figured, while I'm here, I could just "install zip" and find that zip I just transferred and install, right? Nope. The zip mysteriously vanished, yet the other two updates were still there (M7 and the previous nightly). So I just rebooted just to try the process again, maybe the file transfer didn't work. Same thing happened. So I went to cwm and tried wiping cache, nothing. Wiped dalvik cache, nothing. So I went and did it, wiped data/factory reset, that did NOTHING, as in I rebooted and everything was still there.
So I got to the point where I just wanted to see if I could just revert back to stock so I have a place to start from, maybe contemplate on just staying there for a while where there shouldn't be problems. So I got that all set up with fastboot, got the latest 4.4.3 image, unarchived until I could get to the flashall.bat I ran that and it was successful. Okay now I can just boot into that, right? Suddenly I see the cyanogenmod boot graphic. What happened? Even all of my apps are still there. Still freezing and rebooting.
I tried reverting to stock manually by erasing then formating everything that I can, flashed bootloader (grouper 4.23), flashed zip, locked bootloader, unlocked bootloader (trying to erase as much as I can). This did nothing, still cyanogenmod. I tried a third time while rebooting to bootloader with each step. Nothing. I tried doing a factory reset within cyanogenmod, but when I press the "erase everything" button it doesn't lead anywhere, so I could never get that to start the process. I also tried doing the erasing and formatting from cwm (which isn't being overwritten, as it seems, by all the attempts at flashing stock?), nothing.
I was curious. I uninstalled Netflix because it was right there in my dock. Then I rebooted myself. When it came back up, Netflix was still there. I tried various things, also going back to locking the bootloader and rebooting the bootloader, it still said it was unlocked. So I came to the conclusion that literally nothing was being written or committed to the sdcard no matter what I do.
I did some more research and found that article up top. So I tried uninstalling some apps because it said it may have something to do with a third-party app misbehaving (seems a bit extreme, I'll do it anyways), but there's never enough time to erase everything before it reboots. It also said to try to get it into safemode. I think I might have gotten there once but it still rebooted (which makes me think that it didn't get to safemode), the rest of the times it wouldn't even get to the lockscreen.
What I'm currently attempting is to see if I can get it into safemode, or I'm trying to uninstall or stop/clear data for every single app with an intentional reboot each time.
Anyone got any idea what's going on? Is it maybe a bad sector, or worse, bad sdcard?
Gonna bump this. Still no luck on my part.
Anyone have any idea?
Perhaps somehow something got triggered to prevent anything being written to the sdcard? (Kinda like the lock switch on actual sdcards?) Is everything I've been doing going straight to memory since everything reverts back after a reboot? That's the only explanation I can think of.
Perhaps there's more I could try. I'm only moderately knowledgeable with things like fastboot and roms, so maybe someone with more experience might have more insight. Please, chime in.
Thanks in advance,
JM
Same problem here....
Flash factory image
USBhost said:
Flash factory image
Click to expand...
Click to collapse
Although you flash the factory image, the previously ROM boots again, that is precisely the problem.
Amd64bits said:
Although you flash the factory image, the previously ROM boots again, that is precisely the problem.
Click to expand...
Click to collapse
O ok
Amd64bits said:
Same problem here....
Click to expand...
Click to collapse
Curious, how did you get to the point where it boots the previous rom? Same as me or something else? Are you using cyanogenmod? I want to try and rule out some possibilities.
I'm at the same point since last time. Trying to nuke the hell out of cyanogenmod but it won't go away!
This just outright baffles me!
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
USBhost said:
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
Click to expand...
Click to collapse
I have clockworkmod recovery v6.0.4.3 probably from installing cyanogenmod, however formating any of those partitions does literally nothing. I'm not sure what file system it formats it to, but the process seemed too quick for a full format.
I cannot flash a different recovery because... well... it doesn't remember me flashing a recovery (even when nothing "fails" when flashing). So I'm stuck with whatever is already on my internal storage. Nothing is writing to the sdcard, and nothing is being deleted.
violoncellemuse said:
I have clockworkmod recovery v6.0.4.3 probably from installing cyanogenmod, however formating any of those partitions does literally nothing. I'm not sure what file system it formats it to, but the process seemed too quick for a full format.
I cannot flash a different recovery because... well... it doesn't remember me flashing a recovery (even when nothing "fails" when flashing). So I'm stuck with whatever is already on my internal storage. Nothing is writing to the sdcard, and nothing is being deleted.
Click to expand...
Click to collapse
Boot twrp temporary from the bootloader
USBhost said:
Boot twrp temporary from the bootloader
Click to expand...
Click to collapse
I'm unfamiliar with this, how do I boot temporarily?
violoncellemuse said:
I'm unfamiliar with this, how do I boot temporarily?
Click to expand...
Click to collapse
1 set getting on computer
Okay, so I was able to boot twrp and change the partitions to f2fs. No dice. Still cyanogenmod.
violoncellemuse said:
Okay, so I was able to boot twrp and change the partitions to f2fs. No dice. Still cyanogenmod.
Click to expand...
Click to collapse
then you did boot twrp temporary
USBhost said:
then you did boot twrp temporary
Click to expand...
Click to collapse
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
violoncellemuse said:
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
Click to expand...
Click to collapse
thats not normal
ok i know why its a new cyanogenmod feature
no matter what you do cyanogenmod is now unkillable lol
this is such a strage problem
USBhost said:
thats not normal
ok i know why its a new cyanogenmod feature
no matter what you do cyanogenmod is now unkillable lol
this is such a strage problem
Click to expand...
Click to collapse
Do you have any more info? Perhaps my sdcard is "softlocked" or something.
violoncellemuse said:
Do you have any more info? Perhaps my sdcard is "softlocked" or something.
Click to expand...
Click to collapse
i have been noticing CWMR is the root of all the problems
i dont sorry but your not the only one i think there are 3+ people that have this same problem
formating should have fixed it
USBhost said:
i have been noticing CWMR is the root of all the problems
i dont sorry but your not the only one i think there are 3+ people that have this same problem
formating should have fixed it
Click to expand...
Click to collapse
I do thank you for trying to help me out.
I found a thread with someone with the same problem I'd like to direct people towards: http://forum.xda-developers.com/showthread.php?t=2800064
violoncellemuse said:
Curious, how did you get to the point where it boots the previous rom? Same as me or something else? Are you using cyanogenmod? I want to try and rule out some possibilities.
I'm at the same point since last time. Trying to nuke the hell out of cyanogenmod but it won't go away!
This just outright baffles me!
Click to expand...
Click to collapse
Well, I have Paranaoid Android 4.4.4, not Cyanogen, and everything seemed ok until I installed Cloudmagic (and maybe Busybox?) that poped up a Play Store error (I don't remember which one), and suddenly all the problems began. It started to reboots, rebooted so many times that I decided to flash another ROM... but this wasn't possible.
My recovery is TWRP, so we can discard Cyanogen, ParanoidAndroid, CMW and TWRP as guilty, I think.
USBhost said:
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
Click to expand...
Click to collapse
Tried that, nothing happened, still with Paranoid Android.
violoncellemuse said:
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
Click to expand...
Click to collapse
Same here.
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