Database Develop

Xiaomi Mi 3 Ask Away- help thread.

[SIZE=+2]Welcome to
Questions Answers & Troubleshooting
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This thread has been created to assist owners of:[/SIZE]
[SIZE=+2]The Xiaomi Mi3[/SIZE]
There are no questions that are deemed insignificant
Helpful information for your device:
Full device specifications
ᴥAsk Awayᴥ​
Please feel free to ask anything related to your device.​

Hi, I am unable to find the required files to root my MI3. All the links that i find after googling don't have the correct files. My MIUI version is MIUI 6.6.3.0(KXDCNCF). Any help would be appreciated.

Whiskeyjack4855 said:
Hi, I am unable to find the required files to root my MI3. All the links that i find after googling don't have the correct files. My MIUI version is MIUI 6.6.3.0(KXDCNCF). Any help would be appreciated.
Click to expand...
Click to collapse
I used MIUI for about 30 minutes before moving to AOSP, but I thought it came already rooted...
All the same, you can install SuperSU, which is the best root manager. It's on the play store, or you can go to Recovery and flash the zip file in the first post here http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

I'm trying to install CWM on MIUI 7. But I'm unable to flash it using Updater. I've tried revision 8, revision 11 and revision 11 u1 by furniel... It just keeps saying something went wrong

Annoying sound from the ear piece
There will be an annoying sound from the ear piece of the device while booting up and while on a call. We all know that,but I would like to ask, is there any workaround for that? The sound really is a head ache causing thing with its low frequency noise

@sarathchandraj
I had the same issue, but the Rashr app helped me. Try it. Just download the recovery image, open Rashr, select "Recovery from storage" andthen select your recovery image. But if CWM is not necessary to you, use TWRP. CWM is buggy on Mi3.

Hi guys, I replaced my broken LCD with the new one recently. I am facing an issue. when replacing the LCD display, my lower charge port assembly was not coming out of the main body. I tried hard and in that process I slightly lifted the metallic part underneath the charging port. I thought that metallic thing is a part of main body. The metal is still with ribbon assembly firmly. not detached. But my loud (external, which is in the back)speaker is not working and also home and back button backlit are not glowing. menu button light works ok. speaker gives very faint sound though. What can be the reason. Speaker is ok I guess, as it was working well before replacement.
I know it's a software related issue forum but as you guys are having the same mobile, I think you all might have an idea about it.

please give QCN file

Hi
---------- Post added at 06:27 PM ---------- Previous post was at 06:21 PM ----------
Hi guys, I am in big problem. .. im using mi3 xiaomi and i just up to mokee 5.1 and its runing. The problem is i forget my gapps. So now im runing without a gapps. I cant flash either roots or even upgrade also. Can anyone help me.....please!!?

Hiii...i am unable to go back to miui 7 from cm 12.1. I have downloaded latest miui 7 build and renamed it "update.zip" and tried it to flash via stock recovery. Installation went fine but after restarting it's getting stuck on MI logo.... Please help.. Missing Miui...

Hello, after many years of running with Ivan's 4.4.4 AOSP I feel like it's time to move to something newer so I wanted to try and flash the 6.0.1 new one seeing as he released the final version. It has been few years since I last flashed a rom so I mostly forgot the procedure. Chcked few threads but overall I still have some confusion. If someone can clear up the doubts I'd be grateful.
Currently: MI3W with Ivan AOSP 4.4.4 and CWM
Here's what I was currently planning to do:
ttp://en.miui.com/thread-209941-1-1.html
Following this guide to merge the partitions and install TWRP.
Now for the questions:
1. Will the flash.bat merge the partions AND install TWRP too all at once? Will it overwrite my current CWM without any problem or do I need to install it separately?
2. Once the flashing there is done, how should I proceed to install the 6.0.1 ROM? Usual procedure? (load zip on SDCard,wipe all, and flash zip).
3. Will Ivan's ROM be Rooted/Have Gapps on default?
Thanks to whoever can solve these doubts for me.

unable to flash gapps
please help me friends, i am unable to flash gapps on cm13, mokee. i am able to flash the rom zip but after that when i flash gapps it gives me error insufficient space..

Hi my friend is having a problem with her Mi3. No custom ROM installed, it's updated to the latest version. After trying to update Hearthstone, and downloading 99%, the download failed with error 903. Looked around for a fix, saw a solution that required clearing data+cache and uninstalling updates of the Play Store app. Did that and now when trying to download the app the error that is returned is
java.lang.SecurityException: No permission to write to /storage/emulated/0/Android/obb/com.blizzard.wtcg.hearthstone/temp.main.1355705.com.blizzard.wtcg.hearthstone.obb:
Neither user 10050 nor current process has android.permission.WRITE_EXTERNAL_STORAGE.
at android.os.Parcel.readException(Parcel.java:1620)
at
android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:183)
at
android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:135)
at
android.content.ContentProviderProxy.insert(ContentProviderNative.java:476)
at
android.content.ContentResolver.insert(ContentResolver.java:1234)
at com.google.android.finsky.download.l.run(SourceFile:182)
at android.os Handler.handleCallback(handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:148)
at android.os.HandlerThread.run(HandlerThread.java:61)
Click to expand...
Click to collapse
Other apps (Zalora, pinterest) are installing fine. The phone has more than enough storage space to run the game, upwards of 3 GB
Any advice or assistance is appreciated.

hi, i'm not new to android, but it's been a few years after using windows phone, but i'm back to android for a while. why does everybody say you'll need a rooted phone to install a custom rom? i never had to root my phone to flash a custom rom.

Hi. I am returning to XDA after a long time. I am looking for a stable Custom Rom for my Mi3. What is the popular rom as of now for Mi3 ?

HELP NEEDED!!! Not able enter fastboot or recovery mode
I was trying to flash miui 8 developer ROM onto my mi3 device which didn't have any os installed.
After flashing the ROM, I selected "Bootloader" Option in "Reboot" menu in TWRP.
Now, phone neither switching on nor entering into either of fastboot or recovery modes.
Even if I connect my phone to charger no response like doesn't vibrate and screen never turns on.
If I connect the phone to my linux machine around 6 disks are mount.
Please help me find out what's wrong here, how do I get the phone back online.

vjsrinath said:
I was trying to flash miui 8 developer ROM onto my mi3 device which didn't have any os installed.
After flashing the ROM, I selected "Bootloader" Option in "Reboot" menu in TWRP.
Now, phone neither switching on nor entering into either of fastboot or recovery modes.
Even if I connect my phone to charger no response like doesn't vibrate and screen never turns on.
If I connect the phone to my linux machine around 6 disks are mount.
Please help me find out what's wrong here, how do I get the phone back online.
Click to expand...
Click to collapse
It happened to me like this when I was testing out my own kernel. Have you tried to flash a custom kernel? Try entering recovery mode by holding down the volume up and power button at the same time.
Sent from my Mi 4 using XDA Labs

@kaiz16, thanks for the reply.
After bit of googling i found that i hard bricked my phone.
Using some Qualcomm drivers and Mi Flash tool I was successfully able to recover my phone by installing stock recovery ROM.

Hello, i flashed twrp in my mi3 but i didn't unlock my bootloader so when i tried to flash lineage rom on my device it started showing error and because i wiped my data before that its not booting up its stuck on the mi logo so please help me what should i do in order to get it boot again
and is this firmware related issue is yes then where can i find the correct firmware for it ?

Sudhanshu7 said:
Hello, i flashed twrp in my mi3 but i didn't unlock my bootloader so when i tried to flash lineage rom on my device it started showing error and because i wiped my data before that its not booting up its stuck on the mi logo so please help me what should i do in order to get it boot again
and is this firmware related issue is yes then where can i find the correct firmware for it ?
Click to expand...
Click to collapse
Afaik cancro doesn't have it's boot loader locked. Try flashing twrp with adb and then you can install lineage os OR you could try fastbooting miui.

Root SM-t580

I try to root a Galaxy Tab 6A (SM-T580).
-I tried some CF-Autoroot images, but their is no image for the SM-T580.
-I tried also to install TWRP with no success. The device do not boot in Recovery Mode with the TWRP image.
The device runs on Marshmallow 6.0.1.
Can somebody help me please?

I too would love and greatly appreciate any help! It's a great tab for the money

hell2003 said:
I try to root a Galaxy Tab 6A (SM-T580).
-I tried some CF-Autoroot images, but their is no image for the SM-T580.
-I tried also to install TWRP with no success. The device do not boot in Recovery Mode with the TWRP image.
The device runs on Marshmallow 6.0.1.
Can somebody help me please?
Click to expand...
Click to collapse
You flashed custom recovery ? the bootloader is not locked?

I tried a twrp custom recovery image. But I cant start the recovery mode. I do not know the status of the bootloader. How can i check that?

http://forum.xda-developers.com/android/development/recovery-official-twrp-gtaxlwifi-galaxy-t3437666
@jcadduono did it !
Let's try

bws78 said:
http://forum.xda-developers.com/android/development/recovery-official-twrp-gtaxlwifi-galaxy-t3437666
@jcadduono did it !
Let's try
Click to expand...
Click to collapse
what do you guys think of my new shirt isn't it awesome
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bws78 said:
http://forum.xda-developers.com/android/development/recovery-official-twrp-gtaxlwifi-galaxy-t3437666
@jcadduono did it !
Let's try
Click to expand...
Click to collapse
Thank you very much, this works for me.

hell2003 said:
Thank you very much, this works for me.
Click to expand...
Click to collapse
don't thank me, thank @jcadduono in the official thread

Data partition encryption prevents root without a .zip rom
hell2003 said:
I try to root a Galaxy Tab 6A (SM-T580).
-I tried some CF-Autoroot images, but their is no image for the SM-T580.
-I tried also to install TWRP with no success. The device do not boot in Recovery Mode with the TWRP image.
The device runs on Marshmallow 6.0.1.
Can somebody help me please?
Click to expand...
Click to collapse
You can disable frp lock by removing your Google account. This will allow you to flash twrp with Odin.
Disable auto reboot in Odin before flashing twrp. After flashing twrp you can reboot into recovery by holding power and volume down to turn the device off. Then once it's off hold volume up home and power to reboot into twrp.
Now the only problem is you can't flash supersu.zip without formatting data first from the twrp wipe data main screen. This is because the data partition is unavailable due to encryption. Formatting data partition removes encryption and allows you to flash supersu, but now device won't boot after formatting data unless you flash a ROM from within twrp. Only problem is that there are no such Roms yet.
If anyone could create a stock or custom ROM that is a flashable zip you'd be the MAN!
Until then I don't think we'll be able to root our device.

Still no roms available?

Now the only problem is you can't flash supersu.zip without formatting data first from the twrp wipe data main screen. This is because the data partition is unavailable due to encryption. Formatting data partition removes encryption and allows you to flash supersu, but now device won't boot after formatting data unless you flash a ROM from within twrp. Only problem is that there are no such Roms yet.
Click to expand...
Click to collapse
Does this mean that if you just root the device that the data partition is encrypted and cant use it as if it was not rooted?
Tried this last night but got the Fap lock. Didnt know about the google bit.
I want to download my current rom and backup is this possible?
I havent done this stuff since the HTC HD2 days
Thanks.
Rob.

I've successfully bypassed the Google FRP Lock on SM-T580 and posted the instructions in [URL="https://forum.xda-developers.com/galaxy-tab/help/bypass-frp-sm-t580-2016-t3446958]this forum[/URL]. If you cant figure it out send me a message and I'll walk you through it

hi
only for root..
Can i use cf-autoroot?

abarth83 said:
hi
only for root..
Can i use cf-autoroot?
Click to expand...
Click to collapse
Hanyone tried it?

Instructions
kleptobismol said:
I've successfully bypassed the Google FRP Lock on SM-T580 and posted the instructions in [URL="https://forum.xda-developers.com/galaxy-tab/help/bypass-frp-sm-t580-2016-t3446958]this forum[/URL]. If you cant figure it out send me a message and I'll walk you through it
Click to expand...
Click to collapse
Hello, Can you repost instructions can't get page to load
This site can’t be reached
%22https’s server DNS address could not be found.
DNS_PROBE_FINISHED_NXDOMAIN
Thanks

ohiostater86 said:
Hello, Can you repost instructions can't get page to load
This site can’t be reached
%22https’s server DNS address could not be found.
DNS_PROBE_FINISHED_NXDOMAIN
Thanks
Click to expand...
Click to collapse
I was having the same problem, but i figured it out last night. Without OTG cable, Odin, SideSync, Realtek, or a PC. I'd been messing with it for 3 days, so Im not 100% sure of what everything said and i'm definitely not going to relock it to try an duplicate it, but if you've been all over youtube then you've seen methods that require a wifi connection, (I found it easiest to use my phone's wifi hotspot) you disconnect your hotspot or unplug your router immediately when it says checking for software update, which appears after clicking accept on the privacy policy. (Again it's easier to just turn off the hotspot than to unplug your router" When done correctly it souls say "couldn't sign in" and then the next screen will either ask you to set up time and date or it asks you to add a name to the tablet (can't remember which is first) then asks to set up a screen lock passcode or pattern (set up either one), after doing all this 100 times I noticed it asked me if i wanted to set up a IMAP/POP3 account to use within the Gmail app (which I'd been skipping) but for some reason it didn't give me this option every time. You have to be connected to the internet for the next part so if you haven't already go ahead and turn your hotspot back on or router and add any email address other than a Gmail (I used my yahoo account) then follow through with the setup into it takes you back to the very first screen you see when you turned on the tablet. Now just turn the tablet screen off and back on (just the screen, do not power down the tablet) put in your lockscreen password and now In the top right corner there should be a little yellow icon which lets you switch users (if you see this, you've got it beat) now create a new user signing into your Gmail and Samsung accounts (if you don't have one, create a new account) once you're done with that it will take you to the home screen, pull down the notification bar and go into settings (notice since you're on an added user you can't factory reset the device) find "Users", and then switch back to the owner profile, it then tells you that you still need to set up the tablet to continue. Once i clicked okay it now let me pull down the notification bar to access settings, but this time you're on the owners account so you can factory reset it, go to "Back up and Reset" and then go ahead and factory reset it again. If done correctly the FRP will no longer be on the tablet.

I rooted my T580 with this german howto:
https://www.android-hilfe.de/forum/...sm-t585-samsung-galaxy-tab-a-2016.788225.html
Root is ok now! But unlocking the LockScreen needs 5-10 seconds now. Has this sth to do with Knox 0x1 ?

Getting "Your device is corrupt" message and I want to start completely fresh.

Getting "Your device is corrupt" message and I want to start completely fresh.
I had setup a Nexus 6 a couple years back for someone who was mostly blind and I used tasker to let them do most things they needed by voice only.
It was working fine until a couple days ago when somehow the device upgraded from Lollipop to Android 7.0. The way I initially unlocked the phone and obtained root, I didn't think it would ever be able to upgrade unless I intervened but it finally happened seemingly on its own.
Anyway, it lost root and many of the tasker commands stopped working because of it so I tried to get it back by:
1) Using fastboot to flashe twrp-3.1.1-0-shamu.img to recovery
2) Booting into recovery and installing SuperSU with TWRP after I made a backup
After that, the phone booted back up normally but still didn't have root access so I restarted again but when I tried to get into recovery I got a "no command" message. I was finally able to get passed that by pressing volume down (I think) and it gave me the standard android factory reset, wipe cache, etc. options. I tried wiping the cache and then after reboot I got this message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And then it just disappears after a few seconds and the phone will not boot up.
Now though I can still get back into the bootloader menu with Power and Volume Down and even get back to the TWRP recovery where I tried restoring the backup I made before installing SuperSU but the same problem occurs.
I don't know what I've done wrong but I just want to start over. What do I need to do to wipe the phone completely and start over like it was brand new out of the box?

LaTropa64 said:
I had setup a Nexus 6 a couple years back for someone who was mostly blind and I used tasker to let them do most things they needed by voice only.
It was working fine until a couple days ago when somehow the device upgraded from Lollipop to Android 7.0. The way I initially unlocked the phone and obtained root, I didn't think it would ever be able to upgrade unless I intervened but it finally happened seemingly on its own.
Anyway, it lost root and many of the tasker commands stopped working because of it so I tried to get it back by:
1) Using fastboot to flashe twrp-3.1.1-0-shamu.img to recovery
2) Booting into recovery and installing SuperSU with TWRP after I made a backup
After that, the phone booted back up normally but still didn't have root access so I restarted again but when I tried to get into recovery I got a "no command" message. I was finally able to get passed that by pressing volume down (I think) and it gave me the standard android factory reset, wipe cache, etc. options. I tried wiping the cache and then after reboot I got this message:
And then it just disappears after a few seconds and the phone will not boot up.
Now though I can still get back into the bootloader menu with Power and Volume Down and even get back to the TWRP recovery where I tried restoring the backup I made before installing SuperSU but the same problem occurs.
I don't know what I've done wrong but I just want to start over. What do I need to do to wipe the phone completely and start over like it was brand new out of the box?
Click to expand...
Click to collapse
I'm not sure what to tell you, there's a lot of complication between these things but mostly seems like it'd include Re-flashing stock os 7.0 and obtaining root thru Android 7 without flashing any rom
Sent from my Z988 using Tapatalk
---------- Post added at 08:09 AM ---------- Previous post was at 08:08 AM ----------
And by complication I mean the whole concept of just starting over fresh
Sent from my Z988 using Tapatalk
---------- Post added at 08:09 AM ---------- Previous post was at 08:09 AM ----------
Good luck tho
Sent from my Z988 using Tapatalk

LaTropa64 said:
I don't know what I've done wrong but I just want to start over. What do I need to do to wipe the phone completely and start over like it was brand new out of the box?
Click to expand...
Click to collapse
Download a factory image from Google developer site. That site gives instructions to set-up your PC for fastboot (if you need it) and there is a flash all script in the download to handle the flash through fastboot. This thread will give you an overview. Using the flash all script will wipe the entire phone!
You can also fastboot flash each partition manually. If you use the -w flag, it will wipe all user data from the phone.
Be warned, the probability is you'll wipe the internal (user data) and if you want to try to back up first, you should be able to boot into TWRP and use ADB to do an a back up of user data to your PC using:
adb pull /path/to/files /home/[your username]/
E.G.
Windows:
adb pull /sdcard C:\Users\[your username]\Desktop
Linux:
adb pull /sdcard /home/[your username]/
You'll need administrator privileges on the PC to specify the output path.
---Edit---
You might look into the tasker beta to work with the newer nougat releases. I will say, all of my tasker profiles continued to work regardless of OS version with the exception of those relying on secure settings. Those I updated to use auto tools. There are other work around as well.

Follow what @ktmom says to get the device all straightened out firmware wise. As the device totally skipped Android 6 in doing its upgrade there could be undesired leftovers from the original install. Once you've installed the latest stock firmware from Google you can start over with your customizations, but be aware that installing TWRP, rooting the device, or both will cause the "device is corrupt" message you're seeing. That message will remain on every boot until a custom kernel which ignores dm-verity is installed.

In a few months, Galaxy S8 will get Bixby Voice so you could get one of them.
Sent from my Z988 using Tapatalk

Who in the hell would want to use Bixby?

Nexus 6 not turning on

Hello i bought a replacement screen for my phone about a month ago because everything was still working except the screen was broken from cracks. As i was about to replace the screen i noticed my phone is now not turning on at all even on charge. No red light, nothing. Is it possible the battery just needs to be replaced or is the phone completely dead?

Try charging it for a few hours on a low power charger like a computer USB port.
When the battery gets very depleted, it can have trouble taking a charge from a faster charger.

ktmom said:
Try charging it for a few hours on a low power charger like a computer USB port.
When the battery gets very depleted, it can have trouble taking a charge from a faster charger.
Click to expand...
Click to collapse
Hi, i tried to charge it using the PC but it didn't change anything. Would it be worth it getting a new battery to test if it still works?

I guess that's a decision you have to make. Is the expenses of the battery worth the risk that something else is wrong. It's possible the power button assembly has a problem. It's possible the USB port is worn, damaged or dirty.

Paperweight now? Having a different issue but potentially fatal??
My nexus 6 has been my faithful companion for many years, and now, though it is not my main phone, is used as my bedside companion for many uses. I boot it up one day and it gives some sort of "file encryption error" and then would not boot. I downloaded a fresh rom and adp to try to wipe it and just get it back to any working state, but nothing seems to work. What am I doing wrong?? (see photos attached)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

archos5005 said:
My nexus 6 has been my faithful companion for many years, and now, though it is not my main phone, is used as my bedside companion for many uses. I boot it up one day and it gives some sort of "file encryption error" and then would not boot. I downloaded a fresh rom and adp to try to wipe it and just get it back to any working state, but nothing seems to work. What am I doing wrong?? (see photos attached)
Click to expand...
Click to collapse
Let's start with some basics. It looks like the phone is stock (not bootloader unlocked).
What version was on the device before the problem?
Can you boot to recovery? (With the phone powered off, press and hold Volume Down, then press and hold Power)
Try sideloading an OTA the same as your current version. They are available on the Full OTA Images for Nexus and Pixel Devices page. The instructions there are solid.
If your not sure what was on the device, use the newest release.
Based on your photo, the device is not unlocked. You won't be able to Fastboot flash anything if you can't unlock it which requires the OEM unlocking to be enabled in developers options. Since you can't boot, you are stuck there.
It's quite possible the eemc has failed and the device is damaged.
BTW; your images are not showing up because the use of the IMG tag is wrong. There should not be anything inside the brackets with the tag (e.g. ="error"). The link does go between the opening and closing tags as you have it.
In the future, it also is a good idea to start your own thread, instead of burying a question inside a unrelated thread.

ktmom said:
What version was on the device before the problem?
pretty sure it is the latest (for that model) Android 7.1.1
Can you boot to recovery? (With the phone powered off, press and hold Volume Down, then press and hold Power)
I can get to the screen that shows the green android man lying with his compartment open. Is that recovery? It seems that everytime I try an option, it does not "do" anything. E.g., factory reset just won't let me do it. It just doesn't work [is this a symptom of emmc memory just being damaged? I know on PC's, a total reformat can isolate bad sectors...]
Try sideloading an OTA the same as your current version. They are available on the Full OTA Images for Nexus and Pixel Devices[/URL] page. The instructions there are solid.
I think I've followed that, (see the second picture) but again those commands don't seem to "do" what the commands usually should do. Like I need a tougher solution--willing to totally wipe everything and reformat and start anew, like a low level format.
Based on your photo, the device is not unlocked. You won't be able to Fastboot flash anything if you can't unlock it which requires the OEM unlocking to be enabled in developers options. Since you can't boot, you are stuck there.
It's quite possible the eemc has failed and the device is damaged.
I think I tried unlocking it, but same thing it didn't "work" either that, or I'm just doing it totally wrong [is it not the command "fastboot flashing unlock"??].
Click to expand...
Click to collapse
Thanks in advance. I just don't want to accept that it was working great one day and then turning it on the next day the flash memory is just TOTALLY bad, you know?

When a you boot to recovery, then get the "no command screen" press and hold Power then press and release Volume Up. If you can get to recovery, do a factory reset.
Unlocking the bootloader won't work unless you have already enabled OEM unlock in the developer options when booted to system. I said this earlier.
ADB won't work unless the kernel is booted. ADB only works when booted to recovery or fully booted to system.
Unless the bootloader is unlocked, Fastboot doesn't get you anything.
If you get to recovery and a factory reset doesn't solve your problems, do an OTA sideload using the link I gave you before.
Please Do Not bury your comments within the wipe of someone else's post. It makes it impossible to follow the conversation. Just respond below the quoted post.

Unofficial Evolution X for Pixel3/XL [09 October 2021]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Evolution X 5.9 for the Google Pixel3/XL [blueline] [crosshatch]
Code:
/*
* Your warranty is void. Or vaild, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modificiations, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/
Living, Breaking, Keep Evolving.
Pixel UI, customization and more, we are Evolution X!
- Team Evolution X -
@joeyhuab
@peaktogoo (Now RealAkito)
Reach us on Twitter! @EvolutionXROM
What are our features?
- Just flash and check "The Evolver"
You tell me
DO NOT FLASH GAPPS, ALREADY INCLUDED
First Time Install / Clean Flash
1. fastboot flash boot boot.img
2. fastboot erase userdata
3. Use volume keys and power button to select "Enter Recovery"
4 Select "Apply Update from ADB"
5. adb sideload EvolutionX_5.8_crosshatch-11-xxxx.zip
6. Reboot to System and #KeepEvolving
Update / Dirty Flash
1. Just skip the step "Wipe userdata"
Light Screenshots / Dark Screenshots /
Download blueline
Download crosshatch
Donate to me! / Official Chat / Device Support
Android OS version: 11.0_r46
Security patch level: October 2021
Build author: voidz777
Source code: https://github.com/Evolution-X
Kernel Source code: pixeldust-r
ROM Developer: joeyhuab

My favorite ROM! Thanks for bringing this back!

awesome, thanks so much for this. I was sad when this ROM was dropped a year or so ago.
if anyone wants signature spoofing, I've attached a magisk module that will grant that permission. I used the tools found here and credit goes to Kingslayer9988 and others:
Signature Spoofing on unsuported Android 11 (R) Roms
How to get Signature Spoofing working on Android 11 (R) Roms that have no support for Signature Spoofing? In my Case here I use a Samsung Galaxy S8 with an unofficial LineageOS 18.1 (Android 11) by stricted I use TWRP recovery but this should...
forum.xda-developers.com

Hello all- I've been trying to sideload this rom for the past half hour and get up to around 48% and get installation aborted.
Does anyone have any clues as to what I may be doing wrong ?
The boot.img flashed fine but the rom not so much.
Thank you for any help.
Cheers, LL

lamplighter13 said:
Hello all- I've been trying to sideload this rom for the past half hour and get up to around 48% and get installation aborted.
Does anyone have any clues as to what I may be doing wrong ?
The boot.img flashed fine but the rom not so much.
Thank you for any help.
Cheers, LL
Click to expand...
Click to collapse
Are you using updated platform-tools? (Adb and fastboot drivers)
Are you wiping data? I.e., fastboot erase userdata or fastboot -w
Are you coming from stock? Try flashing the most recent official Google update then try this one again.
Try those things, good luck

aleph.mercury said:
Are you using updated platform-tools? (Adb and fastboot drivers)
Are you wiping data? I.e., fastboot erase userdata or fastboot -w
Are you coming from stock? Try flashing the most recent official Google update then try this one again.
Try those things, good luck
Click to expand...
Click to collapse
Hello aleph..yes as far as I'm aware anyway but I will update everything thing to make sure.
I'll update and try again and report back.
Thanks again for your help !!
Cheers, LL

lamplighter13 said:
Hello all- I've been trying to sideload this rom for the past half hour and get up to around 48% and get installation aborted.
Does anyone have any clues as to what I may be doing wrong ?
The boot.img flashed fine but the rom not so much.
Thank you for any help.
Cheers, LL
Click to expand...
Click to collapse
Same thing happening with me.
It hung at 48% but then finally continued after a few minutes.
And completed the install fine. So, I am okay now.
I used the latest factory ROM.
crosshatch-rq3a.210605.005-factory-46501e19.zip
Am using the latest platform tools.
platform-tools_r31.0.2-windows
I tried fastboot erase userdata but it didn't find any such folder.
Probably because it got wiped by the -w from the stock image minutes earlier.

Flashing the Magisk-v23.0.apk created boot.img resulted in inability to control touch screen.
It does not register any touches.
Anyone seen this?
This is the first ROM I've flashed since last year with Android 10.
A hard reboot resulted in a weird, l long boot-loop and then it eventually got back to the login screen, but still does not register any screen touches.
EDIT:
Tried a factory reset and that didn't help either.
Still no touch screen. Bummer.
EDIT NUMBER TWO:
I'm having the same issue with PixelDust. So it's unlikely that my problem has anything to do with this ROM.
EDIT NUMBER THREE:
When you tell Magisk to patch the boot, make sure you tell it to patch the Evolution boot.img, not the stock boot.img. lol
All is well again.
I just forgot about that little step. Been such a long time.

I'm just an onlooker and not actually installing, but have you all tried installing factory 11 to both slots before starting the custom ROM install process? That has been a common issue with the custom ROM install on Pixel series phones.

Well, I'm not good at English, so I can't say much in detail, but boot.img specifies boot.img of evox.
I'm flushing boot.img to both slots.
fastboot flash --slot all boot 20210620boot.img
For root, copy the 20210620boot.img to your device and patch the copied 20210620boot.img with magiskmanager.
Then I'm flushing the patched boot.img to both slots.
fastboot flash --slot all boot magisk_boot.img
The progress displayed during the transfer of sideload stops at 47%, but there is no problem.
"1/2" displayed on the device becomes "2/2" and it will be completed after a while.

Everything working fine for me so far. I've restored all my apps and am still configuring settings and restoring data from previous ROM. Thank you for the cool ROM.

Nice work here, only one bug found so far which is the same bug as in lineage official and Google Camera/Night Sight mode.
It reads a value from the build.prop and only accepts numbers, but you have alpha.
This causes Google Camera to crash when using night sight and possibly other features.
ro.build.version.incremental needs to be numerical only. 1234567890 works but not easy to edit in rom.
I grabbed the main info from the official lineage thread, I don't take credit for the info.
razorloves found the fix.
The fix mentioned above doesn't fix the nightlight crash here.
I put together a quick and dirty Magisk module to overwrite the /system/build.prop with a numerical value for incremental which worked to overwrite but night sight still crashing google camera.
Hope a fix can be found because the rom is otherwise fantastic.
Last update if you go through and undo the updates for google camera/delete the installed apk and revert to older (I used June 9 apk) night sight works.
True final update. The Google Camera app included in the rom works fine, it was the latest update from the play store that breaks night sight.

Thank bro.. appreciate the rom

mix hide notch and setting rounded corner 22dp... is make google pixel 3 XL amazing!!!
btw any bug on google camera...
for The Google Camera app included in the rom works fine
BUT after update from playstore is crash every open camera..
if you have time may be can fix it?
Thanks before
stay safe and healthy

I can't figure out where the option is to open camera by double-clicking the power button.
Could someone point me in the right direction?
Also, is there an option to decrease squeeze sensitivity?
EDIT: I reflashed and now phone opens fine when double-clicking power button

Unfortunately it's impossible for me to fix the camera, but I believe our god razorloves will fix it.
Settings such as active edge can be found in settings → system → gestures.

voidz777 said:
Settings such as active edge can be found in settings → system → gestures.
Click to expand...
Click to collapse
Interesting.
It is pre-configured to open camera by double-clicking the power button from any screen.
But this does not work for me.
Does it work for anyone else?
I tried turning it off, rebooting, then turn it back on again.
But still does not work.
I am using the default camera that came with ROM.

Attached cat log.

CZ Eddie said:
Interesting.
It is pre-configured to open camera by double-clicking the power button from any screen.
But this does not work for me.
Does it work for anyone else?
I tried turning it off, rebooting, then turn it back on again.
But still does not work.
I am using the default camera that came with ROM.
Click to expand...
Click to collapse
to open camera by double-clicking the power button
work for me sir....
camera just crash if update from playstore,
solution for now uninstall update dan pure using stock camera this rom...

leaveNOW said:
to open camera by double-clicking the power button
work for me sir....
Click to expand...
Click to collapse
Only me then, huh. Okay thank you for responding.