Database Develop

My nexus will not flash correctly

Hello guys, ive been generally lucky in the sense that i have had no issues...until now.
I have tried installing the most recent updates (7.0, and now 7.1.1) and i continue to get this error through cmd. It does not seem to want to flash anything, and i have gotten it to flash, root, and twrp, but it still acted funky. Today, trying to remedy the situation, i attempted to flash the new 7.1.1 update, and return to stock (to later return to power user) but it is still doing it.
It says Bootloader: has-slot (not found), and a couple other things. When i try to flash individual pieces, it does not retain it. when i try to flash the flashall.bat, it flashes but does not flash everything, it will say the stuff has transferred 0 and skips it as it looks like. I cannot get my bootloader off the october one, and i have looked everywhere i can to try to fix this.. please help, its driving me mad. I will be happy to provide any information needed.
Thanks Community! You rock!

Have you tried a different USB cable? A different computer? How about a different USB AND a different computer? I think this would be a good place to start.

Can i ask you why this would matter? My usb seems to work fine, and my computer had no issues before this... i can still perform different actions, and my phone is showing up as ADB and Fastboot.

If it's not pc or usb cable related you can try to flash latest factory image step by step via fastboot without your simcard

Well, you might want to post the complete output of your flashing attempt, but if the bootloader slot isn't found, that's usually a sign of a hardware problem. Hopefully I'm wrong, but until we see more from you, I simply don't have an answer for you.

Ive tried to fastboot everything individually, and it refuses to take. I tried the flashall, same thing. I used NRT and it partially worked, but has sorta the same error. I will be flashing again and providing screenshots right now. I was able to get into a rom, root, twrp but i still cannot update all of those core things (bootloader, radio, and such) Thank you guys for the help. Much needed.

Here is the attempt to just flash the bootloader, i have tried from a different location but this is directly in Platform-Tools of the SDK. As you can also see, it does register under fastboot...

Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?

coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
yes i have, i only do it with the simcard removed. Now whats weird is it says my bootloader is on 72.01, but my cmd clearly tells me its not working correctly...

coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
I just tried what you suggest, and im not sure if it worked. It said everything wrote (on twrp) but it was very quickly done. I feel it did the same thing as CMD did.

You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu

dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
hahahaha well that could surely be the issue :silly:, but the one thing im wondering is why it wouldnt work through NRT, and i also "successfully" sideloaded the ota... Gonna try this now and hopefully it works! I shall report back when finished

dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.

Calko2882 said:
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.
Click to expand...
Click to collapse
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".

dahawthorne said:
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".
Click to expand...
Click to collapse
Ok, so what happens is that it says i am on 7.1.1 with i guess the related info, but it does not load in properly as you can see with the screenshots. I start up the initial setup, and i can get through most of it fine, but some areas *permissions* are all blotchy. like i can toggle them on to submit data but i cant see what it is exactly im agreeing to. Then i start the phone, Google App automatically crashes, along side system ui. When i updated them, it seemed to fix the problem. But the issue is, i am not receiving phone calls and texts until possibly days later, and when i send texts it says "sending" and proceeds to spam the hell outta whoever its going to (sends literally 30+ texts). When i call someone, my phones Do Not Disturb mode gets enabled, and then nicely cuts out my audio. I can turn this feature off when im in the call, but sometimes it will then glitch the phone app, and i cannot essentially "hangup". My phone also now dies at 9%, where it had not previously (when i was on other rom / older stock) This all started after i updated to the october patch, and i noticed in december that i didnt have the december patch / update. I went to install it, and the same exact thing occurred. Ive attempted a rescue ota, and a sideload ota, and now this stuff as well, but i fear the worst for my phone. Let me know if i need to add anything else

Strephon may be right in suggesting a hardware fault, but equally it may just be that your phone is now somehow corrupted. My only suggestion is that you nuke it - factory reset, TWRP, wipe everything again in TWRP, and then try installing from fresh using the 7.1.1 full (not OTA) image and the instructions I posted earlier. If it still doesn't work I'm out of ideas, but there are people with far greater experience here than I have, so don't give up. It's too nice a device to just write off.

Calko2882 said:
When i call someone, my phones Do Not Disturb mode gets enabled
Click to expand...
Click to collapse
That's a new feature of 7.1.1. So you won't have to listen to notifications while on the phone. It's disabled as soon as the phone call is over.

dahawthorne said:
Strephon may be right in suggesting a hardware fault...
Click to expand...
Click to collapse
I hope I'm wrong.

Can't Root, Can't Update TWRP - Something Fishy Happening

I can't work out what's going on.
My phone lost it's root a few days ago - I only noticed when Magisk said it had a new one. So here's the lowdown:
My TWRP is out of date.
Magisk is out of date.
I've downloaded both the magisk.zip file and an img file of the latest TWRP.
I put them on the deskop, in the adb folder (in C drive) and on the phone under "downloads".
Boot into recovery, but when I navigate to install a zip file, it can only see the system files, no "downloads" folder or pictures or anything. I can't seem to change that.
Use Powershell to try and sideload the TWRP zip and it says "waiting for device" - that seems good. However, when i then boot into fastboot mode, Powershell tells me "error: cannotload twrp... .img"
So I try and look at Magisk, but I can only download the zip (of which I've done and can't flash it via recovery), or patch boot file, of which I can't navigate to as I'm currently not rooted so it can't find the boot file anyway.
What do I type into Powershell to flash the latest Magisk (I guess I can then update TWRP after using the in-
built updater?)?
When in TWRP, I click on the three lines on the right, which say:
Could not muont /data and unable to find crypto footer.
Failed to mount '/data' (no such process)
Unable to recreate /data/media folder,.
Updating partition details
Failed to mount '/data' (no such process)
... done
Unable to mount storage
Failed to mount '/data' (no such process)
Full SELinux support is present
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount '/data' (no such process)
Click to expand...
Click to collapse
What can be causing all of this?

Probably rip UFS chip, if
Code:
fastboot format userdata
won't help, then you should send your phone for repair

Hmm.
So the only fix is to format all the data?
What data gets deleted?
I don't really want to do that if I can help it but I guess it's the only way to fix it.
Strange how it's just done it by itself.

anotherxdauser said:
Hmm.
So the only fix is to format all the data?
What data gets deleted?
I don't really want to do that if I can help it but I guess it's the only way to fix it.
Strange how it's just done it by itself.
Click to expand...
Click to collapse
Is the system bootable? If yes, then you can make a backup, if not, then you can consider your data gone.
"format userdata" removes everything you have stored on the phone

Yeah, I can boot to my Resurrection Remix rom and see everything, all my files, it's fine.
I can connect to a PC and move files to and fro the device.
It's just TWRP doesn't seem to see the storage. When looking, it just says 0Mb :S
Does Userdata mean the apps and stuff as well?
I saw a video of someone formatting the userdata to ex2, then back to ex4 but if it means I'd have to reinstall RR then it's a lot of work for something that may happen again in the near future.
I have Titanium Backup but of course, it needs root, of which I can't gain :/

Sounds a lot like a failed decrypt of an encrypted userdata partition, this is common in this phone with TWRP and custom ROMs.
Skickat från min ONEPLUS A3003 via Tapatalk

pitrus- said:
Sounds a lot like a failed decrypt of an encrypted userdata partition, this is common in this phone with TWRP and custom ROMs.
Click to expand...
Click to collapse
Is there non-destructive way to fix?

Oh, ok, I thought that the system is broken too. That's ok then, your memory chip is fine.
Can you boot an up-to-date TWRP from fastboot and try to access data?
Try with
Code:
fastboot boot twrp-3.2.3-0-oneplus3.img

Which TWRP version do you have exactly?
Sent from my ONEPLUS A3003 using Tapatalk

przemcio510 said:
Oh, ok, I thought that the system is broken too. That's ok then, your memory chip is fine.
Can you boot an up-to-date TWRP from fastboot and try to access data?
Try with
Code:
fastboot boot twrp-3.2.3-0-oneplus3.img
Click to expand...
Click to collapse
Yeah, try this first. Problably you have a twrp lower than 3.2.0? I think below that it cannot decrypt Oreo encrypted Partitions.
Second thing is. Probably you have to format Data (not Userdata) anyway. I think you probably tried to upgrade Magisk because you lost root. But Magisk hat a bug in 17.0. That corrupted the permission Database. I had the same problem and was not able to get root again until formatted data. You will loose every app and its setting when formatting it. But everything under sdcard/ will still be there. So the download folder should be fine and everything. So when you make a titanium backup of your most valuable apps. You can restore them after renewing your phone.
TLDR:
1. Make Titanium Backup if you have it and want to have your apps back as before.
2. Try przemcio510 suggestion to get new TWRP. (most important)
3. backup your partitions and copy them to your pc
4. backup everything importantto you on your "SDCard" Volume (Where Download is and everything)
5. format DATA, Cache, Dalvik/ART Cache, System
4. Reflash Full OxygenOS 5.0.5
(optional) 5. Flash Rom of your flavor (with/without Gapps)
(optional) 6. Flash magisk
7. boot up your device

przemcio510 said:
Oh, ok, I thought that the system is broken too. That's ok then, your memory chip is fine.
Can you boot an up-to-date TWRP from fastboot and try to access data?
Try with
Code:
fastboot boot twrp-3.2.3-0-oneplus3.img
Click to expand...
Click to collapse
Did this. ADB said it was "waiting for device" so I rebooted to fastboot but then the ADB window shows some options (see quote below), nothing to show it's done anything.
I put the img file on the sim card on the phone and in the directory of the adb.
Code:
PS C:\WINDOWS\system32> fastboot twrp-3.2.3-0-oneplus3.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS C:\WINDOWS\system32>
RASTAVIPER said:
Which TWRP version do you have exactly?
Click to expand...
Click to collapse
3.1.1-0
S4RGE said:
TLDR:
1. Make Titanium Backup if you have it and want to have your apps back as before.
2. Try przemcio510 suggestion to get new TWRP. (most important)
3. backup your partitions and copy them to your pc
4. backup everything importantto you on your "SDCard" Volume (Where Download is and everything)
5. format DATA, Cache, Dalvik/ART Cache, System
4. Reflash Full OxygenOS 5.0.5
(optional) 5. Flash Rom of your flavor (with/without Gapps)
(optional) 6. Flash magisk
7. boot up your device
Click to expand...
Click to collapse
My Titanium Backup needs root to work :/
It might have been when I upgraded RR Rom to the Oreo release, but it's only been the past week when I mysteriously lost root access.

anotherxdauser said:
Did this. ADB said it was "waiting for device" so I rebooted to fastboot but then the ADB window shows some options
Click to expand...
Click to collapse
To be clear, I think you mean fastboot whenever "ADB" is mentioned above. adb and fastboot are related, but 2 different things, with different usages and requirements. So it's best to refer to them in correct and distinct terms.
adb: Needs debugging enabled. Will work only in OS or custom recovery. Will not work in bootloader (even in fastboot mode) - maybe this is why you have "waiting for device"?
fastboot: Does not need debugging enabled. Only works in bootloader-fastboot mode.
fastboot is what you want for booting/flashing TWRP. Not adb (at least for the commands/methods suggested here).
anotherxdauser said:
PS C:\WINDOWS\system32> fastboot twrp-3.2.3-0-oneplus3.img
Click to expand...
Click to collapse
When command prompt shows you the list of command, this almost always means your command syntax is incorrect.
In your case, you used typed "fastboot" and a file name, without telling it what to do with that file name. The suggested command was "fastboot boot filename" (no quotes) or another usage option is "fastboot flash filename".
A little confusing I know, "fastboot" in itself is not a full command/action. I has to be "fastboot boot". Think of fastboot as a "thing" instead of an action. Thus, you still need to tell fastboot to perform an action ("boot").

anotherxdauser said:
...
3.1.1-0
My Titanium Backup needs root to work :/
It might have been when I upgraded RR Rom to the Oreo release, but it's only been the past week when I mysteriously lost root access.
Click to expand...
Click to collapse
Ah right I forgot.
As redpoint73 mentioned you have to be in fastboot mode.
When you start up your phone and the unlock Warning ist triggered. Push the volume up or down button and go to fastboot.
When you are in there the fastboot command should work.
As redpoint73 pointed out it is very important that you type "fastboot boot (ImagePath)".
To make it easier for you, you should copy the image where fastboot is.
Then you have only to enter
fastboot boot twrp-3.2.3-0-oneplus3.img
This should do the trick. If you still need help. Don't hesitate to ask.

redpoint73 said:
To be clear, I think you mean fastboot whenever "ADB" is mentioned above. adb and fastboot are related, but 2 different things, with different usages and requirements. So it's best to refer to them in correct and distinct terms.
In your case, you used typed "fastboot" and a file name, without telling it what to do with that file name. The suggested command was "fastboot boot filename" (no quotes) or another usage option is "fastboot flash filename".
Click to expand...
Click to collapse
Sorry my explanation isn't that great.
Whenever I've mentioned adb it's the dos/command prompt window.
Fastboot is that small menu where it shows whether the device bootloader is locked or not isn't it?
At any rate, tried "fastboot boot twrp-3.2.3-0-oneplus3.img" and the command prompt window shows "waiting for device". My device is on, at the homescreen, doing nothing. The command prompt window stays like that until I boot into fastboot mode, where it then just shows the large list of commands quoted above.
HOWEVER, a development!
When in fastboot mode and using the "fastboot boot twrp-3.2.3-0-oneplus3.img" command, the window now says "cannot load 'twrp-3.2.3-0-oneplus3.img': No such file or directory". So I tried typing the exact file path (C:\adb\twrp... img), which has now allowed me to boot into the updated TWRP.
Does this mean it's just booted into it, but not updated to it?
I'm able to see the contents of my sdcard now. So flashed the latest 17.1 magisk zip and... success! I'm now on the latest magisk and have been able to flash the latest TWRP to recovery.
Just to say, I really appreciate the help with this.
I know I could factory reset but it's helping me learn more.

anotherxdauser said:
Whenever I've mentioned adb it's the dos/command prompt window.
Fastboot is that small menu where it shows whether the device bootloader is locked or not isn't it?
Click to expand...
Click to collapse
You confuse some terms. adb and fastboot are programs, command prompt is the interpreter of the commands you give to these programs.
And yes, the fastboot is that mode.
anotherxdauser said:
At any rate, tried "fastboot boot twrp-3.2.3-0-oneplus3.img" and the command prompt window shows "waiting for device". My device is on, at the homescreen, doing nothing. The command prompt window stays like that until I boot into fastboot mode, where it then just shows the large list of commands quoted above.
Click to expand...
Click to collapse
Fastboot mode is meant to be used while phone is booted into fastboot mode
anotherxdauser said:
When in fastboot mode and using the "fastboot boot twrp-3.2.3-0-oneplus3.img" command, the window now says "cannot load 'twrp-3.2.3-0-oneplus3.img': No such file or directory". So I tried typing the exact file path (C:\adb\twrp... img), which has now allowed me to boot into the updated TWRP.
Click to expand...
Click to collapse
"no such file" means that you could have not copied the img file to the same folder as the adb binary (this is not the case when adb and fastboot binaries are installed with %PATH% variable added, then you can use these commands all over the filesystem).
anotherxdauser said:
Does this mean it's just booted into it, but not updated to it?
Click to expand...
Click to collapse
Fastboot boot command, which I have provided earlier is used to boot temporarily, one time an image you tell it to.
anotherxdauser said:
Just to say, I really appreciate the help with this.
Click to expand...
Click to collapse
Just kindly informing that there is a button on the lower-right hand corner for this

anotherxdauser said:
Whenever I've mentioned adb it's the dos/command prompt window.
Fastboot is that small menu where it shows whether the device bootloader is locked or not isn't it?
Click to expand...
Click to collapse
Both adb and fastboot are command prompt functions. They are both "bridge" tools used to communicate from computer to the phone.
The phone menu screen you are referring to is bootloader. Fastboot is one of the choices on that (bootloader) menu. It puts the phone in fastboot mode, which is specifically intended for fastboot commands (only mode fastboot command will work). The response will always be "waiting for device" if you try fastboot commands, and not in fastboot mode.
If the command is "fastboot . . . " you are issuing fastboot commands (not adb).
If the command is "adb . . . " you are issuing adb commands.
Again, they are both related, but different. Different requirements and usages for adb versus fastboot. It is important to understand the distinction, so you don't waste more time trying command in the wrong mode (which will never work).

[GUIDE] Unlock bootloader on 8.1

As you know, on 8.1 we still have ununlockable bootloader. But it's quite simple to fix, just flash 'old' bootloader
It's unofficial method
1) Go to fastboot bode (keep + button on reboot/boot your phone)
2) Use service firmware or download this https://vk.com/doc275347426_479517439 , open command promp (start.bat)
3) VERY IMPORTANT
you should know your platfotm. As I know, 2 GB (my phone) have 8917 processor, 3gb/32 have 8937. You can get your platform with this
Code:
fastboot getvar platform
4) I have 8917, so I type
Code:
fastboot flash aboot 8917_emmc_appsboot.mbn
fastboot flash abootbak 8917_emmc_appsboot.mbn
On 8937 type
Code:
fastboot flash aboot 8937_emmc_appsboot.mbn
fastboot flash abootbak 8937_emmc_appsboot.mbn
5) Reboot your phone, you should get 'device state unlocked' , if not, do like U did this on old bootloader from fastboot
6)Flash twrp as usual. In archive I already include this, you can flash it with
Code:
fastboot flash recovery twrp.img
And install magisk/SSu
Attention: if you wanna get full access for /data partition from twrp, you should flash patch with prevent autoencrypt. I did not do this, system access is enought for me.
But before you root your device, U have to erase data partition, coz root patch boot partition too, patched boot can not load stocky encrypted data. After data format you can flash magisk. When you boot phone, it will encrypt data partition and you get installed Magisk and ecrypted data
Original system/boot images, restore them with twrp https://mega.nz/#!ziJxCCqA!C0lG5hUcOGwl2ER0Mp342lfx5_DOIzalAi7RExR6nro

My phone is 8937 and device state remains locked after stage 5. And "if not, do like U did this on old bootloader from fastboot" means we should use some other adb codes? Such as?
Woohooo, the display has been turned upside down. How do I fix this?
---------- Post added at 03:24 PM ---------- Previous post was at 03:17 PM ----------
What the ??? Stock recovery is upside down, but fastboot is the right way. Is this supposed to happen?
---------- Post added at 03:45 PM ---------- Previous post was at 03:24 PM ----------
Hmmm, I think I'll pass on this method. I appreciate the effort, but too much weirdness happening with my phone.

igerup said:
My phone is 8937 and device state remains locked after stage 5. And "if not, do like U did this on old bootloader from fastboot" means we should use some other adb codes? Such as?
Woohooo, the display has been turned upside down. How do I fix this?
---------- Post added at 03:24 PM ---------- Previous post was at 03:17 PM ----------
What the ??? Stock recovery is upside down, but fastboot is the right way. Is this supposed to happen?
Click to expand...
Click to collapse
worked thanks

Display rotates only few seconds when it boot

Dreamject said:
Display rotates only few seconds when it boot
Click to expand...
Click to collapse
It doesn't bother me at all ? it worked perfectly, thanks for your work

Dreamject said:
As you know, on 8.1 we still have ununlockable bootloader. But it's quite simple to fix, just flash 'old' bootloader
It's unofficial method
1) Go to fastboot bode (keep + button on reboot/boot your phone)
2) Use service firmware or download this https://vk.com/doc275347426_479517439 , open command promp (start.bat)
3) VERY IMPORTANT
you should know your platfotm. As I know, 2 GB (my phone) have 8917 processor, 3gb/32 have 8937. You can get your platform with this
Code:
fastboot getvar platform
4) I have 8917, so I type
Code:
fastboot flash aboot 8917_emmc_appsboot.mbn
fastboot flash abootbak 8917_emmc_appsboot.mbn
On 8937 type
Code:
fastboot flash aboot 8937_emmc_appsboot.mbn
fastboot flash abootbak 8937_emmc_appsboot.mbn
5) Reboot your phone, you should get 'device state unlocked' , if not, do like U did this on old bootloader from fastboot
6)Flash twrp as usual. In archive I already include this, you can flash it with
Code:
fastboot flash recovery twrp.img
And install magisk/SSu
Attention: if you wanna get full access for /data partition from twrp, you should flash patch with prevent autoencrypt. I did not do this, system access is enought for me.
But before you root your device, U have to erase data partition, coz root patch boot partition too, patched boot can not load stocky encrypted data. After data format you can flash magisk. When you boot phone, it will encrypt data partition and you get installed Magisk and ecrypted data
Original system/boot images, restore them with twrp https://mega.nz/#!ziJxCCqA!C0lG5hUcOGwl2ER0Mp342lfx5_DOIzalAi7RExR6nro
Click to expand...
Click to collapse
dont work for me, than i do this:
1. do what you told
2. use unlock bootloader from asus website
3. repeat what you told
4. walaaa... my device unlocked, than i flash twrp and magisk
5. done, i have rooted device
:laugh::laugh::laugh:
thank you guys...

no no no ..... not work for me, and upside down the title!!!!!
I have no choice but to fix it with: xxx youtube................. /watch?v=s592QY56VjM
than restore back to oreo 8.1..........

tfstk said:
no no no ..... not work for me, and upside down the title!!!!!
I have no choice but to fix it with: xxx youtube................. /watch?v=s592QY56VjM
than restore back to oreo 8.1..........
Click to expand...
Click to collapse
if you screen rotated on thethe boot, it means you have old bl. You just needneed toto flashflash twrp, or unlock bl with fastboot

Dreamject said:
As you know, on 8.1 we still have ununlockable bootloader. But it's quite simple to fix, just flash 'old' bootloader
It's unofficial method
1) Go to fastboot bode (keep + button on reboot/boot your phone)
2) Use service firmware or download this https://vk.com/doc275347426_479517439 , open command promp (start.bat)
3) VERY IMPORTANT
you should know your platfotm. As I know, 2 GB (my phone) have 8917 processor, 3gb/32 have 8937. You can get your platform with this
Code:
fastboot getvar platform
4) I have 8917, so I type
Code:
fastboot flash aboot 8917_emmc_appsboot.mbn
fastboot flash abootbak 8917_emmc_appsboot.mbn
On 8937 type
Code:
fastboot flash aboot 8937_emmc_appsboot.mbn
fastboot flash abootbak 8937_emmc_appsboot.mbn
5) Reboot your phone, you should get 'device state unlocked' , if not, do like U did this on old bootloader from fastboot
6)Flash twrp as usual. In archive I already include this, you can flash it with
Code:
fastboot flash recovery twrp.img
And install magisk/SSu
Attention: if you wanna get full access for /data partition from twrp, you should flash patch with prevent autoencrypt. I did not do this, system access is enought for me.
But before you root your device, U have to erase data partition, coz root patch boot partition too, patched boot can not load stocky encrypted data. After data format you can flash magisk. When you boot phone, it will encrypt data partition and you get installed Magisk and ecrypted data
Original system/boot images, restore them with twrp https://mega.nz/#!ziJxCCqA!C0lG5hUcOGwl2ER0Mp342lfx5_DOIzalAi7RExR6nro
Click to expand...
Click to collapse
I've problem that if I mounted System partition in Any App,it will freeze my Systemui and can't do anything
Since 7.1.1 to 8.1 still have these problem

tony8077616 said:
I've problem that if I mounted System partition in Any App,it will freeze my Systemui and can't do anything
Since 7.1.1 to 8.1 still have these problem
Click to expand...
Click to collapse
DonT know.... Try magiskmagisk, system less stuff, change launcher, disable bloatware

Dreamject said:
As you know, on 8.1 we still have ununlockable bootloader. But it's quite simple to fix, just flash 'old' bootloader
It's unofficial method
1) Go to fastboot bode (keep + button on reboot/boot your phone)
2) Use service firmware or download this https://vk.com/doc275347426_479517439 , open command promp (start.bat)
3) VERY IMPORTANT
you should know your platfotm. As I know, 2 GB (my phone) have 8917 processor, 3gb/32 have 8937. You can get your platform with this
Code:
fastboot getvar platform
4) I have 8917, so I type
Code:
fastboot flash aboot 8917_emmc_appsboot.mbn
fastboot flash abootbak 8917_emmc_appsboot.mbn
On 8937 type
Code:
fastboot flash aboot 8937_emmc_appsboot.mbn
fastboot flash abootbak 8937_emmc_appsboot.mbn
5) Reboot your phone, you should get 'device state unlocked' , if not, do like U did this on old bootloader from fastboot
6)Flash twrp as usual. In archive I already include this, you can flash it with
Code:
fastboot flash recovery twrp.img
And install magisk/SSu
Attention: if you wanna get full access for /data partition from twrp, you should flash patch with prevent autoencrypt. I did not do this, system access is enought for me.
But before you root your device, U have to erase data partition, coz root patch boot partition too, patched boot can not load stocky encrypted data. After data format you can flash magisk. When you boot phone, it will encrypt data partition and you get installed Magisk and ecrypted data
Original system/boot images, restore them with twrp https://mega.nz/#!ziJxCCqA!C0lG5hUcOGwl2ER0Mp342lfx5_DOIzalAi7RExR6nro
Click to expand...
Click to collapse
Hi, thank to you I have unlocked my phone in 8.1.
But when I tried to downgrade to nougat, home and fingerprint botton won't work. I had tried relocking bootloader and lock again using nougat method, but still home button won't work.
Do you have any idea to fix home button so I can use nougat firmware in this device?

komtek said:
Hi, thank to you I have unlocked my phone in 8.1.
But when I tried to downgrade to nougat, home and fingerprint botton won't work. I had tried relocking bootloader and lock again using nougat method, but still home button won't work.
Do you have any idea to fix home button so I can use nougat firmware in this device?
Click to expand...
Click to collapse
You should flash service nougat

Dreamject said:
You should flash service nougat
Click to expand...
Click to collapse
I'm sorry, can you tell me what service nougat is? Did you mean play service, or other service?

komtek said:
I'm sorry, can you tell me what service nougat is? Did you mean play service, or other service?
Click to expand...
Click to collapse
you can find service fw at least on 4pda. Service fw contained more data than usual fw

Dreamject said:
you can find service fw at least on 4pda. Service fw contained more data than usual fw
Click to expand...
Click to collapse
Thanks to @Dreamject I have managed broken fingerprint sensor when I tried to downgrade to 7.1
Here is quick guide to fix broken fp sensor in 7.1:
(Prerequisites: adb driver installed on computer)
1. Download service firmware nougat v.232-AFT https://yadi.sk/d/IzR3ITht2IlHxw (source 4pda)
2. Extract firmware to root C://
3. Open flashall_AFT.bat
4. Go to fastboot mode and connect the phone to computer. (NOTE: YOU MUST ON 8.1 FIRMWARE UNLESS FP SENSOR WON'T FIXED)
5. Wait ~10 minutes until finished.

Mother Russia)

By the way, be careful, coz it contains as o remember service Oreo too.
If file name 14.2016 it's nougat, if 15.2016 it's Oreo

link is gone, pls fix the link

Bootloader ReLocked Problem same as WW-15.2016.1812.505,So contiue used these step

Dreamject said:
As you know, on 8.1 we still have ununlockable bootloader. But it's quite simple to fix, just flash 'old' bootloader
It's unofficial method
1) Go to fastboot bode (keep + button on reboot/boot your phone)
2) Use service firmware or download this https://vk.com/doc275347426_479517439 , open command promp (start.bat)
3) VERY IMPORTANT
you should know your platfotm. As I know, 2 GB (my phone) have 8917 processor, 3gb/32 have 8937. You can get your platform with this
Code:
fastboot getvar platform
4) I have 8917, so I type
Code:
fastboot flash aboot 8917_emmc_appsboot.mbn
fastboot flash abootbak 8917_emmc_appsboot.mbn
On 8937 type
Code:
fastboot flash aboot 8937_emmc_appsboot.mbn
fastboot flash abootbak 8937_emmc_appsboot.mbn
5) Reboot your phone, you should get 'device state unlocked' , if not, do like U did this on old bootloader from fastboot
6)Flash twrp as usual. In archive I already include this, you can flash it with
Code:
fastboot flash recovery twrp.img
And install magisk/SSu
Attention: if you wanna get full access for /data partition from twrp, you should flash patch with prevent autoencrypt. I did not do this, system access is enought for me.
But before you root your device, U have to erase data partition, coz root patch boot partition too, patched boot can not load stocky encrypted data. After data format you can flash magisk. When you boot phone, it will encrypt data partition and you get installed Magisk and ecrypted data
Original system/boot images, restore them with twrp https://mega.nz/#!ziJxCCqA!C0lG5hUcOGwl2ER0Mp342lfx5_DOIzalAi7RExR6nro
Click to expand...
Click to collapse
I've make a flashable which can used with ZF4 Max update ROM(script and binary based on WW-15.2016.1812.505,file is from OP post)
-Just flash it after stock ROM update

Fastboot Issue

When i try to boot into fastboot mode using power key and volume - key, it shows me a blank screen :crying::crying: . there is no bunny with fastboot logo. only black screen.anyone help me please.
Note: I am on pie with march update.

feroz mahmud said:
...there is no bunny with fastboot logo. only black screen....Note: I am on pie with march update.
Click to expand...
Click to collapse
Maybe you still get into fastboot mode, but screen is black due to corrupted splash partition? You can check that subj is in bootloader mode using "fastboot devices -l" from PC. If yes, you can reflash splash.img from 10.0.2.0 fastboot image.

Aerobatic said:
Maybe you still get into fastboot mode, but screen is black due to corrupted splash partition? You can check that subj is in bootloader mode using "fastboot devices -l" from PC. If yes, you can reflash splash.img from 10.0.2.0 fastboot image.
Click to expand...
Click to collapse
Will you please tell me the process of flashing splash? And where do i get this file?

feroz mahmud said:
Will you please tell me the process of flashing splash? And where do i get this file?
Click to expand...
Click to collapse
Same as all other flashing via fastboot.
The only official fastboot image for Mi A2 AO Pie available yet is v10.0.2.0 PDIMIFJ and can be found at http://en.miui.com/download-353.html or https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849.. Here in forum you can find hand-made variants of images for 10.0.3.0-10.0.7.0, but all these contain same image of splash partition as in official ROM (if any).
.TGZ and .TAR archives can be unpacked by 7z and many other programs.
Inside archive is directory called smth like "jasmine_global_images_V10.0.2.0.PDIMIFJ_9.0" containing the ready ROM image for fastboot flash.
Inside this directory there are several batch files, containing the same line for flashing splash partition:
Code:
fastboot flash splash %~dp0images\splash.img
Note that "splash.img" is foind in " \Images" subdirectory.
So, you will need:
1. Mi A2 with unlocked bootloader and critical partitions (search this forum on how to unlock) in bootloader mode, connected to USB 2.0 port in PC;
2. Working drivers and / ADB / fastboot installation.
3. "splash.img" copied into directory of working ADB / fastboot installation.
To check that requirement (1) and (2) are fulfilled, run CMD shell in directory of working ADB / fastboot installation and type
Code:
fastboot devices
If output list contains the only 1 string with ID of device (same as shown by "ADB devices -l" command in normal MTP file transfer mode), you are ready to type in commands:
Code:
fastboot flash splash .\splash.img
fastboot reboot bootloader
You are supposed to see the 'bunny' after phone reboots to bootloader mode once again. To reboot back to system just use "fastboot reboot"
If above is not helpful, bring phone to service

Aerobatic said:
Same as all other flashing via fastboot.
The only official fastboot image for Mi A2 AO Pie available yet is v10.0.2.0 PDIMIFJ and can be found at http://en.miui.com/download-353.html or https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849.. Here in forum you can find hand-made variants of images for 10.0.3.0-10.0.7.0, but all these contain same image of splash partition as in official ROM (if any).
.TGZ and .TAR archives can be unpacked by 7z and many other programs.
Inside archive is directory called smth like "jasmine_global_images_V10.0.2.0.PDIMIFJ_9.0" containing the ready ROM image for fastboot flash.
Inside this directory there are several batch files, containing the same line for flashing splash partition:
Code:
fastboot flash splash %~dp0images\splash.img
Note that "splash.img" is foind in " \Images" subdirectory.
Click to expand...
Click to collapse
thanks for you information. my device is locked. when i try to peform fastboot devices , it shows me a error saying application was unable to start correctly.

1. Search for guides how to install ADB drivers and use fastboot, and study these
2. Search here for guides how to unlock bootloader and critical of Mi A2
Nobody will move your fingers except you.

Aerobatic said:
1. Search for guides how to install ADB drivers and use fastboot, and study these
2. Search here for guides how to unlock bootloader and critical of Mi A2
Nobody will move your fingers except you.
Click to expand...
Click to collapse
thanks for your information.
My devices is locked(bootloader). and fastboot isn't showing up. now tell me how do i flash spalsh file?

1. Is phone working and the only problem is black screen in fastboot mode?
If phone is bricked, just bring it to service or somebody who knows what to do.
Following is what you could have already found in guides I was suggesting to find and study
2. Prepare everything for unlocking in phone:
2.1. Get "developer rights"
2.2 Allow "USB debugging" and "OEM unlocking" in developer options
3. Have you get acquainted with ADB drivers installation and ADB commands and fastboot commands?
Can you see result of "adb devices -l" command in CMD shell when phone is attached to USB-2.0 port with MTP file transfer enabled?
If no, just bring it to service or somebody who knows what to do.
4. Can you see result of "fastboot devices -l" command in CMD shell when phone is attached to USB-2.0 port in what is supposed to be bootloader mode with black screen?
If no, just bring it to service or somebody who knows what to do.
5.. If yes, and device ID is the same as in result of "adb devices -l" command
6. Unlock bootloader and critical (see guides here in Mi A2 threads), it takes 2 commands and 2 reboots
7. Reflash splash.img as stated above in my 1st message
Nobody here can repair your phone, - only you or service. So I won't write more here.

Aerobatic said:
1. Is phone working and the only problem is black screen in fastboot mode?
If phone is bricked, just bring it to service or somebody who knows what to do.
.
Click to expand...
Click to collapse
Can you help me with this? my phone is ok, when i run fastboot command it shows me "??????????? fastboot"

Restart pc or update adb and drivers.

How To Guide Orange State Warning Remover

To REMOVE the warning - Orange State Your device has been unlocked and can't be trusted Your device will boot in 5 seconds - on UNLOCKED RMX3312 & RMX3311
Install ADB DRIVERS & follow in POWERSHELL
adb devices
adb reboot fastboot
RMX3312 goes to FASTBOOTD mode
fastboot flash abl <drag & drop OrangeState-Warning_Remover.img>
fastboot reboot
P.S. : fastbootd != fastboot mode
P.P.S. : If in fastboot type
fastboot reboot fastboot
Now, UI looking similar to RECOVERY will be there instead of BOOTLOADER

Thank you! It's compatible with rmx3311?

Worked for me too on RMX3311

@Prajwal_Beast is it possible to put in a custom images?
I couldn't figure out what type of files are in the .img.

smashda said:
@Prajwal_Beast is it possible to put in a custom images?
I couldn't figure out what type of files are in the .img.
Click to expand...
Click to collapse
I don't think it's possible to put a custom image!