Advanced features. Features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. Hellomy redmi note4x (mido)ebbg screenflashed AEX ROM 5.5 BUTCANNOT FLASH MAGISKbecause its showed cannot mount vendoritried a lot typr magiskor code in. Flash magisk is show cannot mount /vendor,Xiaomi MIUI Official Forum.
Hi everyone,So I got a nexus 5 from a friend that he said was broken. He told me that he was doing and update and was taking too long so he rebooted his phone. Now the phone is stuck in a boot loop. Everything is stock on the phone and he said he never rooted it. I followed the steps on this thread(method 2 manually flashing each img) Here is the output from the CMD window:C:UsersbradDesktophammerhead-lrx22c-factory-0f9eda1bhammerhead-lrx22cfastboot flash bootloader bootloader.imgtarget reported max download size of bytessending 'bootloader' (2579 KB).OKAY 0.298swriting 'bootloader'.OKAY 0.515sfinished. I had the same thing happen after allowing the 5.0 update, as in the forever dancing dots screen. I tried manually flashing like you did but also ran into errors while flashing system partition, think it was something to do with available storage, which there was PLENTY of.All in all, I had to downgrade to the OG KitKat, 4.4.1 I believe?
Then followed with a factory wipe, and let the phone upgrade 3 times before reaching 5.0 that would actually boot up. And this was done by downloading the 4.4.1 TGZ image from Google, and running the flash-all script that comes with it. Hope that helps.SpecEdit: I had TWRP for recovery and running DU at the time, was only able to get out of the boot loop by flashing DU once again. Wiped that clean, then ran 4.4.1 flash script! That's not good, as there is no slot to insert one. Your onboard SD partition got messed up somehow. Weird, out of all of the bricking and flashing disasters I've done to my N5, I've never managed to do that.
In fact I've never heard of that happening in the N5 forums either.I wouldn't worry just yet, that can probably be easily fixed.I would try doing a factory wipe (if possible) and/or flashing the firmware again. If you booted up, obviously the phone's share of the SD is working, just weird why your side of it is nonexistent. Odd things are going on. I am able to create folders in the internal storage on the phone with windows. So I thought maybe my cache is still messed up as all those apps that were crashing you cache. So I reflashed everything manually and now I am stuck on flashing the cache.
This is what it shows:C:UsersbradDesktophammerhead-lrx22c-factory-0f9eda1bhammerhead-lrx22cfastboot flash cache cache.imgtarget reported max download size of byteserasing 'cache'.It's been like this for about 20 minutes. Why does it write to cache when I flash the 4.4.4 cache IMG. See:OKAY 14.446serasing 'cache'.OKAY 0.525sformatting 'cache' partition.Creating filesystem with parameters:Size: 734003200Block size: 4096Blocks per group: 32768Inodes per group: 7472Inode size: 256Journal blocks: 2800Label:Blocks: 179200Block groups: 6Reserved block group size: 47Created filesystem with 11/44832 inodes and 5813/179200 blockssending 'cache' (13348 KB).writing 'cache'.OKAY 1.862s. It's not booting. I powered it off after it was stuck at erasing from unlocking it. I then installed CWM recovery. I saw options to format system, cache, data etc.
I formatted the cache and data fine and it got stuck formatting system. I let it run for about 1hr and it was still stuck. I powered off the phone and then on and it booted into Kitkat?
4.4.4 Camera still crashes. It crashes even before android was done the setup. So same symptoms as before.
When I download a file in chrome says no SD card. When I try to update software the download doesn't start.So I guess now it is booting again. I have no clue what I did to get it to boot either.
4.4.4 that you didn't install? It sounds like you may have revived what was on the phone when it was given to you, but how.
I had the same issue when I got into the 5.0 upgrade mess. Wondering how my DU was still there when it shouldn't have been.?There is an option to repair partitions in TWRP, something else worth a try. I strongly recommend downloading the toolkit that I gave you a link for.
It literally does everything for you, so no typing a bunch of crap in ADB. You may have to wipe, format, repair, flash, crash and re-flash firmware several times before it may actually work right. At least that's how it happened for me.Start with getting TWRP or use CWM to obliterate the internal memory. Do it twice, maybe even thrice.
Then do a factory reset. Reboot and see what it does. I can't guide you through CWM, don't have it on my N5.
Welcome to the subreddit.Before posting please use the search function or read the, popular questions covered in the will be removed.FiltersRules (subject to alteration).Use common sense.No affiliate Links.Check the and search the sub to see if your topic has already been discussed and covered. Do not spam!.Topics that benefit the community and promote discussion are welcome.Posts and comments regardless of intent that contain racist, sexist, homophobic or abusive content will be removed! Please follow reddiquette.User flair is available, please choose your device, memory and any useful information deemed relevant. Profanity and abuse will not be tolerated and you could be banned.Android N preview questions go on, not here.Battery SOT bragging posts go on, not here.Photos are only allowed in the weekly stickied photos thread.Posts asking about OTA updates (When will i get my update, still dont have the update) are not allowed. Also, posts simply stating 'i just got the update' are not allowed.This subreddit is not the place to sell phones, accessories, nor other.
These posts will be removed. Posts to retailers such as Amazon are however, allowed.Please take the time to flair your post appropriately. If you do not know how, message the moderators with a link to your post.No threads.Discuss Battery issues in the.Wiki Pages Official Links Related Pages Switching from an iPhone? Related subreddits.
I accidentally started flashing a sys.img to vendor and then boom I was screwed for half a day. No fastboot commands trying to flash stock firmware. No busybox love.
No adb.What Did fix it was going to each partition(that you can't mount aside from otg obviously)restorerepairchange file system on all that are problematic from ext4 to exfat and then back to ext4. Then go back to terminal and busybox mount -o rw,remount /system or adb remount.Just wanted to spread the word because 50% of the threads out there I attempted half the people never solved their issue and apparently it's not always as simple as fastboot flashing every time.