yashsingh1/xdaforums huggingface dataset:
[Nexus 5X General] X3NOM:
Nope I installed nothing, it just went dead again, I have two devices that did the same thing after I applied the fix and now I have two bricks :(
[Nexus 5X General] creeshu:
Hi,

please ignore my previous post i've managed to flash it all and it works ! thank you so much.

Just a question, is there any way to get rid of "corrupt" system while loading?
[Nexus 5X General] PatcheZ:
My second 5X just started bootlooping so I tried flashing Nov system image followed by the 4 core boot.img to no avail. Still the same old bootloops :(

Still, great work OP and thanks.
[Nexus 5X General] Abfox2:
Did the above steps.

But as soon as i try to get in recovery menu

it says cant check software for corruption, then the google logo appears then nothing happens. cant get into recovery menu, power button and volume up didnt help too.
[Nexus 5X General] truekasun:
Did you flash the 4 core recovery.img?
[Nexus 5X General] Abfox2:
I actually made it work. It wasn't working for this particular recovery idk why, so I tried the 4 core trwp from the original bootloop thread and it worked fine.

No bootloop as of yet.

But another problem is that my phone can't recognize the sim card. This problem happened to me just before the first boot loop. After applying all this fix, my sim card worked for first 15 minutes, but it's again showing no sim card inserted-emergency calls only. I have reinserted it multiple times. Also the sim works fine on other phones. Thanks.
[Nexus 5X General] _Ghost:
[MENTION=4524516]truekasun[/MENTION] Could you help in how to do this modding of the boot.img ? I'm a complete noon to this stuff.
[Nexus 5X General] truekasun:
If you are not much experienced in modding the kernel, you better keep away from those coding. You can just flash the provided boot.img files in the OP.

Meanwhile, if you are willing to learn how to do it, refer this Git Repository by [MENTION=5288606]XCnathan32[/MENTION]

You can see the modifications in the commits section. :good:
[Nexus 5X General] _Ghost:
Thanks ,If I'm able to replace those codes with the ones in the commit , then repacking it is enough ?
[Nexus 5X General] glasslung:
Is it safe to upgrade from 7.1.2. (Aug patch) to 8.0 (Nov patch)? Are there any special instructions for this upgrade? Does it require wiping data? The guide doesn't cover upgrading from 7.x to 8.
[Nexus 5X General] truekasun:
If you are updating by the direct OTA from the device, Yes it's safe and you will need to flash the respective recovery and the boot.img.

If you are familiar with these things (and willing to struggle), continue with the OTA, otherwise my advice is to flash the system image. ;)
[Nexus 5X General] rayencool:
hello, kindly tell me why I have this error the 3rd command is not successful

thank you

https://ibb.co/bAoR3R
[Nexus 5X General] truekasun:
It seems you have skipped the 2nd step (Boot the device into bootloader and flash the boot-img-unmodified-opr4.170623.009.img [The update script verify the boot image]) of the guide that you have to flash the unmodified boot.img (of the current system) before hand the OTA side-load.

The update package can't verify the current boot partition. Flash the unmodified boot.img and side-load the OTA update package. ;)
[Nexus 5X General] rayencool:
thanks for your answer, the problem remains as the guide I did not miss any passage I'm locked in this stage gets to 47% then I get that error
[Nexus 5X General] truekasun:
I've faced to a similar error sometimes, you just have to restart the device (hold the power button around 10 seconds) and again try to side-load the OTA package again. Hopefully it will work. (I don't know what is the exact reason for that, but check your battery level before flash something)

All the best! :good:
[Nexus 5X General] truekasun:
Yeah that's it! :cool:
[Nexus 5X General] rayencool:
I skipped this passage and I continued with the guide and now and I installed the stock the smarthponee came back to running smoothly, are not strange things you do not like?

I did try to install a custom rom via twrp but the rom does not start up and the smartphone is restarting continuously, now i should re-run the new procedure and keep the rom stock for the moment

thanks for the great work you did and for your availability

See you soon
[Nexus 5X General] anshul:
[MENTION=4524516]truekasun[/MENTION] thanks for maintaining this.

I tried the System Image method and had to also use the 4 core recovery to make it work. It would be great if you can update your post accordingly.
[Nexus 5X General] truekasun:
Can you please let me know when did you use the 4 core recovery in the system image process so I can update the process accordingly.
[Nexus 5X General] Vonsmalhausen:
Hi i just flash android o and boot.img and recovery.img and phone start up but only for a while. And after that goes to bootloop again. Is here any chance to stable 4 core mode? Thanks
[Nexus 5X General] anshul:
I used the 4 core recovery in the end. After I had already pushed the 4 core boot img. Not sure if the order would matter between these two though.

Longer version of what happened:

I was on the nov build and then booted in fastboot mode. Realized after reading the post that I just need to take the 4 core boot and proceed but that updation didn't help. I thought I might be on different build so tried bunch of other combinations but didn't work.

Then I decided to take the system image route and installed nov image afresh and updated the boot image as well as second step but this also didn't work. Finally decided to update the recovery as well to the 4 core version and it worked.
[Nexus 5X General] zoeij:
I've tried the following:

flash the OPR6.170623.023.zip

tried to do the sideload but can't boot to recovery

flashed the unmodified boot 4 core

reboot phone but still the same, boot loop

is there anything I've missed?
[Nexus 5X General] kakrikakri:
Quick question - I was on a custom rom based on 7.1.2 July patch when hit by BLOD. Can I directly flash the 8.0 November factory system image and then the 4 core boot and recovery images? In short can I go from 7.1.2 July to 8.0 November by only using system image?
[Nexus 5X General] zoeij:
this is what I did, and still boot loop... jump from 6 to 8.0 then unmodified 4 cores, then boot loop again
[Nexus 5X General] Jeremy.Stewart85:
Thank you so much for this post! My 5X manufacture date October 2015 had been working without any issue until yesterday and then got hit with the loops. This method was able to allow me to get to recovery and get my pictures and make a nandroid backup to transfer app data to my old phone. My problem is that my old phone doesn't work with my current service so I'm still kind of sunk.

There must be something to the 4 core part of the fix for me as recovery would not function without the 4 core image of TWRP. However, using the November full system image and the 4 core Nov boot image I get stuck on the boot animation (no loop, just sits on the android animation, even left it on overnight). Has anyone else gotten stuck here?

Steps I took, please note my phone is encrypted which seems like it might have something to do with this and is running stock Android 8:

1) Flash the full system image manually, according to step 9 in https://xdaforums.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930

2) While still in fastboot, flash 4-core-boot and 4-core-TWRP-3.1.1. I've tried doing this as a part of the steps from #1 and just doing it after going through those steps.

3) Reboot to recovery works, TWRP asks for my encryption password and can see /data and /system

4) Reboot system fails at this point, sitting at the boot animation, so next:

5) Flash 4-core EX Kernel in 4-core TWRP and reboot, still sits at boot animation :(. This is the point where it would usually ask for my data password so it can mount my encrypted partitions. Is this a limitation of the 4-core boot img? Does it not work with encryption?

I've tried a ton of different combinations of the steps above doing things in different orders or with the original October patches and haven't been able to figure it out. Can we maybe get a reference set of steps to go from what a typical user might have to do?

Scenarios:

Going from < October security update stock -> 4-core November security update

Going from > October security update stock -> 4-core November security update

I feel like I'm so close to being able to use this phone again, would love to be able to hang onto it for a little while longer until I figure out a proper replacement. Thanks for any help!
[Nexus 5X General] Jeremy.Stewart85:
As a follow up to my last post, since I could make a nandroid backup I bit the bullet and did a complete wipe of the phone and installed the November system image (using flash-all.sh) and then flashing these patched images on top. Worked like magic! I was able to get the phone working again which is huge right before the holiday.

I did see that encryption seems unsupported, even going through settings -> security -> encrypt phone will reboot the device but not actually encrypt anything, it just winds up being a normal reboot. That's not horrible but would love to see that ability if at all possible, I use this phone for work so having encryption is pretty much a requirement. I'm completely ignorant of what all is required for encryption to happen, maybe a modified boot image makes that impossible?

Is there a build process documented somewhere of how to make these boot images for future security updates? Thanks!
[Nexus 5X General] srnoth:
These boot images have encryption support completely removed from the bullhead.fstab file.

Since running without encryption isn't really an option for me, I use Android Kitchen to repack the boot images supplied here with the stock FSTAB file. Then flash SuperSU which removed the vmverify and encryption requirement, but still supports encryption if you already have it.

It's been said that the reason for removing encryption support is because of poor performance with only the four small cores, but I haven't had any issue with it.
[Nexus 5X General] Jeremy.Stewart85:
Excellent, thanks for the response! That's what I meant when I said I had no idea about what was involved. Seems so easy. When people mentioned that force encryption was off I thought that's what it meant and that it was optional, not that encryption wasn't supported at all.

Going on a long trip so all I really wanted at the moment was the phone to function at all before I leave home but will come back to this little project when I get the chance to see if I can get that to work. I'm sure others would be really interested in this process if you can document the steps, [MENTION=3347292]srnoth[/MENTION].
[Nexus 5X General] truekasun:
If you can't get into recovery, that's probably because you didn't flash the 4 core recovery beforehand. If you are going to sideload the November patch, you gotta flash the October patch 4 core recovery.
[Nexus 5X General] truekasun:
Of course you can. The easiest and the safest way is flashing the system image if you are coming from nougat.
[Nexus 5X General] truekasun:
You gotta flash the modified boot.img
[Nexus 5X General] pkelly517:
It's not that they have encryption support removed, it's that they don't require the data partition to be encrypted. There's a difference. They still work with an encrypted device. It's just not required to boot the device.
[Nexus 5X General] zoeij:
I just tried the october 4 core img and still the same....

can you please share the steps that you did?

what OS should I flash first?

step by step instructions please.... I badly need my phone....
[Nexus 5X General] truekasun:
- Download the complete system image - Link

- Flash the system image via ADB

fastboot flash bootloader [bootloader-file-name.img]
fastboot reboot-bootloader
fastboot flash radio [radio-file-name.img]
fastboot reboot-bootloader
fastboot -w update [image-file-name.zip]

- Reboot into the booloader

- Flash the modified boot.img - Link

fastboot flash boot boot-img-4core-opr6.170623.023.img

That's it.
[Nexus 5X General] zoeij:
I just tried this and it's still the same. it was stuck on the Google logo for about 20minutes, and then it turns off then boot loop again
[Nexus 5X General] truekasun:
Then probably this fix wont work on your device... reportedly It happens for some people here.

Note: Try flashing the 4 core recovery and do a factory reset (Some people has been succeeded with this steps even-though it doesn't have any logical point in there)
[Nexus 5X General] Jeremy.Stewart85:
That was not the case at least for me. My device was already encrypted prior to the BLOD, patching it with these boot images (without wiping data) did not allow me to successfully boot. I could get to recovery via the 4 core stock recovery or 4 core TWRP and then decrypt+mount and get a nandroid made, but it would not complete the normal boot process. All it would do is stay stuck on the android spinning wheels animation. I should have tried to get some logs on that and seen what the hell was going on and fixed it properly, but I was running out of time before my trip so I just had to get a working phone pronto.

Only after I wiped data and flashed the patched boot WITHOUT encrypting could I successfully boot all the way into my phone. It also doesn't allow me to encrypt after the fact, when I try to it reboots with the google maintenance droid but goes into the normal boot cycle and never encrypts the partition.

Really interested in getting a proper build process setup to allow the fstab for encrypted /data in the boot image so that I can keep this thing trucking along with security updates and encryption for a little while longer. I'll be away for 10 days but maybe that would be a good distraction if it's a rainy day on vacation or something.
[Nexus 5X General] srnoth:
Same experience here. I'll post more detail of what I did to get encryption working when I get back from Thanksgiving weekend.
[Nexus 5X General] adilau:
If you can access recovery, not TWRP, do 3 times wipe data/factory reset and again 3 times wipe cache.

It works for me with this trick!
[Nexus 5X General] arrche:
[MENTION=4524516]truekasun[/MENTION]

I followed your steps with Image file of October and the phone is still working amazingly fine.thank you soo much.

Currently it automatically downloaded the November patch in the phone and awaiting the restart.

Pls tell me ,if the phone restart, will it again go into bootloop after the automatic installation of November patch.?

What steps should I perform to prevent it ?

screenshot of update window : https://ibb.co/nbhNL6
[Nexus 5X General] truekasun:
It will not get updated if you reboot the device in the normal procedure but if you choose to install the update.

You need to do the steps mentioned in November patch section to get updated. Otherwise it will fail since the recovery and boot.img has been modified by a third-party.
[Android Q&A, Help & Troubleshooting] Tissemand:
HI, just made another post earlier because i was having problems rooting my phone and having played around for yet a couple of hours i think i would like to try to throw on a custom ROM if possible.

Never really played around with my phones like this so not really too familiar with the different options here, so you guys have some tips on what to put on etc?

I have a filipino Cloudfone Excite Prime 2 running Android 7, I can't link to the phone since im not allowed to post links

TIA
[Xiaomi Mi MIX  Questions & Answers] zakenz:
Hi everyone,

everything is in the title, yesterday I bricked my Mix when I tried to install a new version via recovery (Mi Pc suite chinese version).

It updated, started working (I entered the rom) then restarted because it asked for a reset, had to say yes, when it restarted I was in a bootloop of Xiaomi logo and couldn't go into recovery mode anymore.

Only fastboot works, but still can't install rom via because I didn't unlocked the bootloader yet and didn't check for usb debugging.

Any ideas would be really appreciated.

Regards
[Xiaomi Mi MIX  Questions & Answers] james1089:
So you still be able to flash official with miflash?
[Xiaomi Mi MIX  Questions & Answers] zakenz:
When I try to flash via Mi flash it says critical partition error thing (probably because I still don't have unlock the bootloader)
[Xiaomi Mi MIX  Questions & Answers] james1089:
Shouldn't need unlock to install genuine ROM from xiaomi with miflash, you are using the fastboot ROM right?

Likewise USB debugging shouldn't be necessary, as far as I know. Like if you have no ROM it wouldn't know anything about USB debugging.
[Xiaomi Mi MIX  Questions & Answers] zakenz:
Yes I'm using fastboot rom

On this page: http://en.miui.com/a-234.html You can see Mi Mix is listed as it needs to unlock before any flash with fastboot.

When I try flash with MiFlash, it says Flash xbl error : https://i.imgur.com/ct0xAQY.png
[Xiaomi Mi MIX  Questions & Answers] james1089:
You have unpacked the file correctly?

Think they mean if you're not using miflash.

http://xiaomitips.com/guide/how-to-flash-miui-fastboot-rom-on-mi-max-with-locked-bootloader/

Don't know if it would work on mix
[Xiaomi Mi MIX  Questions & Answers] zakenz:
Yes I did, with all the bat files the images folder.

I'll try one more time when I get home.

Or wait some days to get the unlock permissions by xiaomi
[Xiaomi Mi MIX  Questions & Answers] james1089:
Might be safer to just wait. If you do it now you will have to do it again in a day.
[Xiaomi Mi MIX  Questions & Answers] zakenz:
I tried to unlock again with no success, it says error because I didn't enable the "OEM Unlock" option..

Any suggestions?
[Xiaomi Mi MIX  Questions & Answers] james1089:
https://m.youtube.com/watch?v=4Q4MopLMprE
[Xiaomi Mi MIX  Questions & Answers] zakenz:
EDL not working on Mix models.. I already tried and it bootloops again
[Xiaomi Mi MIX  Questions & Answers] james1089:
Yea no edl mode but thought maybe that might work

---------- Post added at 06:30 PM ---------- Previous post was at 06:29 PM ----------

Just never heard of anyone been bricked when fastboot is available. Didn't read it just something to check

https://www.technobuzz.net/use-mi-pc-suite-to-flash-fastboot-rom-on-bricked-xiaomi-phones/
[Xiaomi Mi MIX  Questions & Answers] zakenz:
I'm kinda ****ed.. gotta replace it
[Xiaomi Mi MIX  Questions & Answers] zakenz:
Because of bootloader not unlocked and usb debugging disabled. Thanks for help though
[Xiaomi Mi MIX  Questions & Answers] zakenz:
I tried without success :(
[Xiaomi Mi MIX  Questions & Answers] zakenz:
Do you know why can't I get in recovery mode anymore ?
[Xiaomi Mi MIX  Questions & Answers] james1089:
Have you tried reinstalling the recovery,

From command prompt or from the same command prompt , reboot recovery. Any of these useful?

https://www.google.co.uk/amp/s/www....0-basic-terminal-commands-you-should-know?amp
[Xiaomi Mi MIX  Questions & Answers] james1089:
I'm sure you have disabled driver signature on Windows but just checking.
[Xiaomi Mi MIX  Questions & Answers] zakenz:
These are all adb commands and since I don't have usb debugging enabled :/

And yes signature disabled
[Xiaomi Mi MIX  Questions & Answers] james1089:
Last option is "deep flash cable" to go into edl mode, buy 1 or make 1
[Xiaomi Mi MIX  Questions & Answers] zakenz:
I was looking to make my own, do you know if I can plug my type c cable to a USB male to female and do the operation as on a micro USB on it? I don't wanna break my type c
[Xiaomi Mi MIX  Questions & Answers] james1089:
I don't know about that I would of thought it would be OK, have a search.
[Xiaomi Mi MIX  Questions & Answers] james1089:
Have you got any where?
[Xiaomi Mi MIX  Questions & Answers] zakenz:
No sadly, I emailed the reseller for a refund. I also emailed Xiaomi without success
[Xiaomi Mi MIX  Questions & Answers] malleus:
I had the same problem (although mine occurred as a result of issuing an ADB lock command while rooted), I can confirm that the deep-flash method works (somewhat) perfectly. The problem is that Xiaomi has blocked EDL mode for the Mix so you can't access it without a deep-flash cable.

You can make your own deep-flash without cutting your USB-C, however you may damage your used USB port or the PC's motherboard if you short-circuit the cable by accidentally letting the wire bridge the wrong pins! Follow these steps:

Use a short length of very thin copper wire to bridge the "Data +" pin from the USB plug with the "Ground". The safest way to do this is to lay the wire flat along the "Data +" pin (the second pin from the left when holding the plug with the metal contacts on top) and bridge it with the metal casing of the USB plug (which is grounded). Use tweezers to make sure the wire doesn't touch ANY of the other pins in the plug or it may short. Tape it into position to help avoid this, but make sure the tape allows the wire to be pulled off quickly.

Make sure the Mix is switched off. Attach the USB-C end of the cable to the phone, then plug the other end into a USB 2 (

Not USB3!!!

) port. If the Mix shows a charging screen you screwed up the cable, go back and try again. If it's not in charging mode, then continue on.

Wait 8 seconds, then remove the wire from the USB plug. Some people say to yank it out with a pair of pliers (which works but may jolt the wire into contact with another pin if you're not careful). I've been successful simply pulling the plug from the PC, removing the wire, and reinserting (into the same USB port). As long as you do this in 2.5 seconds or less it should be effective.

If your PC recognizes your phone then you're now in EDL mode. You may need to install the "Qualcomm QDLoader" USB Drivers.

Run MiFlashTool on PC. Extract the image from archive into a short directory (ie, C:\XM\). Click "refresh" to show the phone, then click "select" to choose the directory you extracted the image to. Select the "Clean All" or "Clean All & Lock" option for best results (although a dirty flash can often be functional also). When you've set these options click "Flash" in the top right corner and let it do its thing.

This will allow you to flash any fastboot image using MiFlash without triggering the xbl writing error. If the flash stalls on the XBL write or returns an error, then you're most likely not in EDL mode. Make sure you're using a Mix Fastboot ROM as the image or you may brick your phone.

Good luck!
[Xiaomi Mi MIX  Questions & Answers] zakenz:
Hi guys, quick update on my case here:

So I had no time with this phone until now, I finally connected it to the computer as Qualcomm port via Test point. It flashed correctly but the phone is still in a bootloop like nothing happened..

I'm near the end of this !
[Xiaomi Mi MIX  Questions & Answers] pauzepro:
Hello everyone!

I have the same problem with a Mi Mix with locked bootloader, my question is could I flash a Dev rom if I tried the EDL method? Or would it end as a brick or bootloop?

Can't do anything with a locked bootloader...:crying:

Please need some help
[Xiaomi Mi MIX  Questions & Answers] james1089:
Not even miflash? As far as I know there is no EDL mode on mix, so deep flash cable might be you're only option.
[Xiaomi Mi MIX  Questions & Answers] Super_SU01:
Did you fix it yet?
[Sony Xperia X ROMs, Kernels, Recoveries, & Other D] lubik1:
[ROM][8.0.0][AOSP][SUZU] Oreo Builds​

SUZU F5121 and F5122​

Just builded AOSP from source for test. Not develop, only for testing new futures, so now you can try Oreo AOSP

i'm not responsible for any damage caused with your device after flashing this ROM. Flash only on your own risk.

Download (GDrive repo)

AOSP Drive

Install:

1) Copy to SD card and flash with recovery

2) Download SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v05_loire.img and flash it via fastboot with:

fastboot flash oem SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v05_loire.img

3) Flash SuperSU

4) Reboot.

Feature​

Working:

- Wi-Fi

- Bluetooth

- Fingerprint (partially)

- Gapps included

- GPS

- Sensors

- Dual Sim (need testers)

- Camera

Not working for now:

- You tell me

Builded with

https://github.com/SonyAosp

sources

Screenshots:

View attachment 4292871View attachment 4292872View attachment 4292873