Okay, so I am having a lot of trouble with a bootloop for seemingly no reason. I got two nexus 6'es, and i unlocked, rooted, and flashed TWRP on mine, no problem at all.
So onto my gf's, I did fastboot oem unlock, and then i went to reboot-bootloader, but i accidentally bumped the power button, which was on "Start". It launched a weird loading style screen - the green android standing up with a blue ball spinning around (NOT the stock recovery, android laying down with chest open) , and i couldn't do anything. eventually, when i hit the volume up button, it said "Formatting /data..." but it never completed.
The only thing I could do was unplug it from my computer (mac) and put it in fastboot mode again. I tried flashing all the shamu factory images, and then rebooted again. Same thing. Now, i re-locked and then unlocked the phone again. Now it's just looping at the red, blue, green and yellow circles for over ten minutes now. What the heck can i do to fix this? I can in no way get it to boot to the lock screen, but fastboot is working fine and it recognizes the device
Edit: Got into TWRP by writing it over stock recovery. Tried to factory reset in TWRP and got the following errors:
E: Unable to mount /data
Unable to mount /cache
Unable to mount /storage
Wiping the cache should fix it.
joshua.justice said:
Wiping the cache should fix it.
Click to expand...
Click to collapse
Okay, i wiped cache, userdata, system and everything just to be safe, am currently finishing flashing the rest of the factory images, waiting on system. I'll let you know
joshua.justice said:
Wiping the cache should fix it.
Click to expand...
Click to collapse
./fastboot erase cache did not work still looping the four colored circles
joshua.justice said:
Wiping the cache should fix it.
Click to expand...
Click to collapse
Got this when trying to Factory reset in TWRP Got into TWRP by writing it over stock recovery.
E: Unable to mount /data
Unable to mount /cache
Unable to mount /storage
I was trying to take picture but suddenly my phone restarted. Then after few sec it was not booting up. It was giving me blank screen, no boot animation was coming up. So now what should I do? I try to wipe/factory reset the phone but still phone was not booting up. It was still stuck on blank screen. Please help?
Device: nexus 4
I got stuck in a boot loop also. I had to reflash the factory image. See this link here. It's the best way to do it just follow the instructions you should be fine. http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865
Try to flash the unencrypted boot image, mine did the same thing when in first flashed TWRP to it and it. Then reflash the stock image and wipe the phone.
Related
I factory reset my Glass today because it wouldn't connect to my phone (I switched roms so I needed to pair Glass again). After I did the reset it went into a boot loop. When it's on the "Glass is Updating" screen it can't be accessed via ADB, but I managed to figure out how to get it into the bootloader via the buttons.
From the bootloader I've tried erasing and flashing 16.2, 16.11, and 16.0 but it just returns to the same "Glass is Updating" screen when I reboot.
When I erase, I erase boot, recovery, system, userdata, and cache. When I flash, I flash boot, recovery, and system. I've tried with and without flashing userdata.
Does anyone have any ideas as to what could be wrong?
EDIT: Something really weird is going on. I ran the erase without flashing anything back on and did a reboot. I expected it to stop at the bootloader since there should be nothing to load, but instead it continues to go into the "Glass is Updating" boot loop.
EDIT 2: I've been doing a lot of reading and it sounds like there are more partitions than just the bootloader and the 5 that I have been erasing. My guess right now is that my device downloaded the 16.2 update into some other partition before I did the factory reset and now every time it boots it's running that update. I can't get much info from the device because I can't use adb.
I had the same issue when I tried flashing 16.2. I went back to XE12 and it resolved the issue. The whole point was to get away from the train wreck that is XE16.x anyway, so I'm just going to stay on 12 until the XE17 images are available - then we'll see if that release is any more stable.
davezack said:
I had the same issue when I tried flashing 16.2. I went back to XE12 and it resolved the issue. The whole point was to get away from the train wreck that is XE16.x anyway, so I'm just going to stay on 12 until the XE17 images are available - then we'll see if that release is any more stable.
Click to expand...
Click to collapse
That did it! I didn't try a version back that far because as far as I know mine had XE16 on it when I first got it.
Thanks!
I'm on 5.1.1 and this has not happened before. I booted into the Recovery mode and tried to wipe the cache partition, but as soon as I wiped the cache partition, the phone went into a mode with "No command" on the screen. I'm not able to reboot the phone using any of the reboot methods. Does anyone know what I can do to get resolve this issue or is there a way to reboot the phone somehow through the PC?
Resolved.
incisivekeith said:
I'm on 5.1.1 and this has not happened before. I booted into the Recovery mode and tried to wipe the cache partition, but as soon as I wiped the cache partition, the phone went into a mode with "No command" on the screen. I'm not able to reboot the phone using any of the reboot methods. Does anyone know what I can do to get resolve this issue or is there a way to reboot the phone somehow through the PC?
Click to expand...
Click to collapse
I was finally able to reboot the phone using the Download Mode button combinations, which didn't work earlier. Whew!
Hello, I have an htc desire 510 cricket that became unusable. so, I attempted to factory reset it, but that did not work. So, in my quest to find an answer, I have tried many different things. I think in the process I have accidentally wiped the system and cache. Then I began to get the system and cache cannot be mounted errors. So, I followed the directions of reformatting those sections using twrp. Still they have remained unmountable. I have tried all the instructions online that I can find. However, now, I cannot load twrp. I can't even boot into twrp from fastboot. When i try recovery or factory reset in the bootloader the phone merely vibrates, blanks and then goes back to the bootloader.
anyone have any ideas how I can bring this back to life, if at all possible?
Thanks in advance for any help you may be able to give.
Dave
Another thing I just noticed
bramwell40 said:
Hello, I have an htc desire 510 cricket that became unusable. so, I attempted to factory reset it, but that did not work. So, in my quest to find an answer, I have tried many different things. I think in the process I have accidentally wiped the system and cache. Then I began to get the system and cache cannot be mounted errors. So, I followed the directions of reformatting those sections using twrp. Still they have remained unmountable. I have tried all the instructions online that I can find. However, now, I cannot load twrp. I can't even boot into twrp from fastboot. When i try recovery or factory reset in the bootloader the phone merely vibrates, blanks and then goes back to the bootloader.
anyone have any ideas how I can bring this back to life, if at all possible?
Thanks in advance for any help you may be able to give.
Dave
Click to expand...
Click to collapse
Now when I just try to start my phone normally, it automatically goes to the fastboot screen. It won't even try to boot up.
So my phone was in charger last night and when I woke up, the phone was stuck in HTC logo splash screen. I was curios to see what happened so I tried to force restart but it didn't help. The next thing I did was to enter the recovery to see if there was any problem there. What I noticed was that my sdcard was showing no data on it, so I connected it to PC and mount the sdcard, the sdcard size was suggesting that there should be data on it but there was nothing inside when I tried to open the folder. This was the first time this issue was happening to me.
So the next best thing that I had in mind was to factory reset the phone in TWRP and reinstall the ROM (Xenon HD) and then GApps. Well everything was fine and the ROM booted but since in the latest update of the ROM, root was not present, I went to recovery and installed Magisk 14.0 and then restarted it. After the restart, I notice that the phone boot loops in the ROM splash screen. So I gave it another try to reset my phone but this time only formatting the system like usual way of installing ROM. This is where the issue happened.
Every time I tried to wipe or install anything, at the first and and the end of the log, it states that "Failed to mount '/devlog' (invalid argument)". I thought it was normal and I proceeded with reinstalling the ROM but it won't boot and gets stuck in boot loop. I tried to search for this specific error but in every site, failing of mounting data or system or cache or all of them together with devlog was mentioned but not devlog by itself. I tried many ways suggested in the forums like:
Installing newer version of TWRP
Formatting the partitions to ext2 then reformat to ext4
but non helped.
I really appreciate if anyone could help me figure out how to solve this issue I'm facing. My phone is HTC M7 GSM, S-OFF and the latest GPE firmware is installed.
Thank you
I reflashed my firmware since, when I did getvar, it was showing blank version-main. This solved the error in the TWRP ( /devlog) BUT every time I try to install any ROM, after installation, it shows the ROM splash screen but then it boots loops forever. I tried many ROMS from Lolipop to Noughat all having the same problem. The other thing I forgot to mention after this issue happened there is now a black stagger line under the HTC logo whenever the phone boots. This was not there before and it only happens in that stage of booting.
I appreciate any help
Trying to give the mother in law my old N6. It was rooted / bootloader unlocked. First attempt was to factory reset from within the OS. That worked fine, until I rebooted... it wouldn't boot.
I then downloaded the Shamu factory images from Google's website (shamu-n6f27m-factory-bf5cce08) and ran the flash-all.bat script. Multiple errors showed up during the script... but I chalked it up to ADB looking for boot slots etc, whereas this one has none.
Phone booted fine. Installed apps, set up the phone, power cycled it and promptly entered a bootloop.
Ran flash.all again, phone booted fine. Flashed TWRP, booted into recovery, checked things out in there (didn't do anything but flash the TWRP) tried to reboot, phone bootloops.
Flashed TWRP, booted into Recovery, tried to erase system, etc.... multiple errors again. Booted into bootloader, ran Flash-all... phone boots. Installed some apps, rebooted phone and bootloop again.
Then I did something REALLY stupid, I locked the bootloader from ADB. Now I'm on the bootloader, but can't OEM unlock because it's asking me to boot into the OS and enable the ability from Developer options.
I've no idea why this phone is doing this - booting fine into the OS once and then getting into a bootloop every time thereafter.
If anyone can shed some light on this, I'd appreciate it. Also, how in the hell do I unlock the bootloader now that I've locked it and I can't boot into the OS or run the Flash-all.bat anymore since it's locked?
Is your recovery stock? If it is, sideload the last OTA from Google and that should get you back into Android so you can toggle the OEM Unlock button.
Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.
usafle said:
Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.
Click to expand...
Click to collapse
So did you finally figure out what it could have been that you were doing wrong?
Strephon Alkhalikoi said:
So did you finally figure out what it could have been that you were doing wrong?
Click to expand...
Click to collapse
No. I could only assume I had messed something up when I was using it back in the day and really hosed something up. System wouldn't wipe, cache wouldn't wipe, userdata wouldn't wipe in "fasboot" just kept getting "unable to find XXXX".
So multiple flashes into TWRP and bootloops trying to really REALLY wipe the device finally fixed it. I just kept erasing / wiping every partition I could find in Stock Recovery, TWRP, and with fastboot commands. Finally I got them all wiped/cleared and was able to flash the stock OS back on and have it 'stick'.