Today I got my new Xiaomi 3S (4G, 3GB RAM, 32GB ROM) played around with it a little bit and disabled all Google Apps to be found on the phone Except Google Services that couldn't be disabled.
Connected it via WLAN and got promptly OTA offered. I didn't wrote down the MIUI and Android builds but remember manufacturing date August 2016, MIUI was version 7 something.
After the updates where downloaded I was asked to reboot the device what I confirmed and the updates where installed. Now the phone is stuck with a black screen and white "MI Powered By Android" on it.
Nothing changed since 3 hours now. Any idea what to do?
Phone can't even be turned off/does not recognize hardware button presses.
This is a known issue, disabling google apps causes issues . You should now try following this guide http://en.miui.com/thread-327861-1-1.html
timbohobbs said:
This is a known issue, disabling google apps causes issues . You should now try following this guide http://en.miui.com/thread-327861-1-1.html
Click to expand...
Click to collapse
Thanks a lot for your reply, tried it already yesterday while the Phone was in endless boot queue without luck, hence the non working buttons update.
But today after the battery was emptied over night I got into the recovery mode menu!
Just a question before I go ahead to follow the step by step guide:
Though I read this thread/vote I'm non the smarter. If I want to go google free, Xiaomi Global or Xiaomi EU ROM?
I'd also use XPosed framework with XPrivacy again. IMUI seems nice, is CM 13 the only alternative for non google/XPosed/Xprivacy then?
I currently have a 3s prime but it's a present for my son so haven't flashed anything, just take ota's. I have read quite a bit though and you should maybe just check the rom threads for roms with separate gapps packages, that way you could remove what you want prior to flashing. Don't know about xposed but again, ask in the rom threads. [emoji106]
Update: No success, when going into recovery mode (pushing volume up and power button) and choose download mode the phone will just reboot into endless boot-loop.
For people with the same problem (after disabling google apps) maybe they can get their device back to work with this http://en.miui.com/thread-378963-1-1.html
The only Way to get you phone back is to use a Deep Flash Cable i think
I was able to solve the problem by installing a fastboot-rom. Pressing power button and volume + for around 20 seconds got me into recovery menu.
Than I was just following a guide to install an original MIUI rom on devices with locked bootloader.
well to get to download mode you can enter "fastboot oem edl" without the "" and you will go to edl from fastboot mode. HOPE THIS HELPS
timbohobbs said:
This is a known issue, disabling google apps causes issues . You should now try following this guide http://en.miui.com/thread-327861-1-1.html
Click to expand...
Click to collapse
Now I know why my phone went into a bootloop. Won't disable any Google apps anymore.
Disabling any apps in MIUI8 will cause the phone cannot reboot... you can format everything through a recovery (have to flash manually because it doesn't come with recovery), or flash a new ROM through fastboot mode (if you have unlocked your bootloader), or send back to service center to claim warranty (if there is any service center in your area), or throw it and buy a new one
abhi0005 said:
well to get to download mode you can enter "fastboot oem edl" without the "" and you will go to edl from fastboot mode. HOPE THIS HELPS
Click to expand...
Click to collapse
I have same problem but in my case developer option is locked so oem is off and thus port COM10 is not being shown in Miflash, also fastboot oem edl says device is locked, oem edl is not allowed. In my case 3s prime went into bootloop while Iwas using youtube. Please help!!
Related
A friend of mine gave me this phone after unexpected self shutdown. The phone was in a boot loop. At this point where I am right now I think I tried everything I can. I have read various guides and tutorials how to bring this phone back to life and nothing works for me. I suppose that there is some damage on mainboard but till I losse this phone I want to be sure. So the situation looks like this. Since the bootloader in locked and there is no working OS I am not able to unlock the bootloader. (If I am wrong here tell me please because I can't find a solution "how to unlock bootloader without having working OS"). The only metode to flash this phone in this state is to use QFIL. Flashing through fastboot fails everytime - booloader locked -> no *.img flashing. So I have 4 various versions of stock ROM for this phone and after flashing via QFIL the phone doesn't boot. It end with 3 possible ways. 1'st way - clasic bootloop. 2'nd way - frozen on loading screen. 3'rd way - black screen with blue LED, USB diagnostics state, 9006 port opened, no chance to flash because of closed QD port 9008. After this I have to erase every single one of the partitions made through flashing. Then I am able again to flash with QFIL.
I have no idea where is the problem here or what am I doing wrong. I tested the internal memory with a partitioning program in search of bad sectors -> 100% OK. Filled the whole memory with zero's and then formated it. It didn't help. Are every of my stock ROMs broken or is this phone realy damaged? Dear XDA community help me please! I have no clue what can I still try.
Tried ZUI QPST image or CM one?
ankurpandeyvns said:
Tried ZUI QPST image or CM one?
Click to expand...
Click to collapse
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?
kotex said:
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?
Click to expand...
Click to collapse
I just recommend you downloading this https://drive.google.com/open?id=0B7zm16vLHfdBVi1lWlMwelBBdXc . It's ZUI 2.0.49 for qfil, hope it works for you.
kotex said:
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?
Click to expand...
Click to collapse
Download the CM QFIL image from my video. It should work.
ankurpandeyvns said:
Download the CM QFIL image from my video. It should work.
Click to expand...
Click to collapse
Already tried your copy. To be honest tried it many times in every way I could. The phone is now sitting for over 3h frozen on loading screen. It is never going to boot or tell me that this is normal... Ereased the whole internal memory by delting every existing partition and then flashed it via QFIL. Also tried to format the whole memory in ext4. Same result. Like I said the phone is laying right now for over 3h on the same CYANOGEN screen with some graphical artifacts.
Borja Viera said:
I just recommend you downloading this https://drive.google.com/open?id=0B7zm16vLHfdBVi1lWlMwelBBdXc . It's ZUI 2.0.49 for qfil, hope it works for you.
Click to expand...
Click to collapse
OMG This room booted normaly. Thank you some much my friend! You made my day. It is a step forward. However all connections aren't working. I can't find "OEM unlocking" under Developer Options. I want to unlock the Bootloader as soon as possible so I will be able to put TWRP recovery and then flash it with any available CustomROM
kotex said:
Already tried your copy. To be honest tried it many times in every way I could. The phone is now sitting for over 3h frozen on loading screen. It is never going to boot or tell me that this is normal... Ereased the whole internal memory by delting every existing partition and then flashed it via QFIL. Also tried to format the whole memory in ext4. Same result. Like I said the phone is laying right now for over 3h on the same CYANOGEN screen with some graphical artifacts.
Click to expand...
Click to collapse
What's the result after flashing ZUI 2.5.330 image?
ankurpandeyvns said:
What's the result after flashing ZUI 2.5.330 image?
Click to expand...
Click to collapse
Many hours frozen on black screen with blue led. 9008 QD port blocked. 9006 USB Diagnostics port opened. No chance to flash until all partitions are erased and the port is reset. Otherwise I need to try getting to the 9008 port by puting the USB cable while holding the "Vol Up" button and then flash it agin with QFIL.
kotex said:
Many hours frozen on black screen with blue led. 9008 QD port blocked. 9006 USB Diagnostics port opened. No chance to flash until all partitions are erased and the port is reset. Otherwise I need to try getting to the 9008 port by puting the USB cable while holding the "Vol Up" button and then flash it agin with QFIL.
Click to expand...
Click to collapse
Got successful in flashing?
ankurpandeyvns said:
Got successful in flashing?
Click to expand...
Click to collapse
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?
kotex said:
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?
Click to expand...
Click to collapse
If you're still in warranty, the best bet will be to get it replaced. Because it seems like a serious issue in the hardware.
kotex said:
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?
Click to expand...
Click to collapse
Do you have any telegram account, we could make things faster if we communicate that way.
ankurpandeyvns said:
If you're still in warranty, the best bet will be to get it replaced. Because it seems like a serious issue in the hardware.
Click to expand...
Click to collapse
Asked my firend about it. The phone is like 1 month old. He was making some pictures and the phone suddenly died and got to boot loop. He bought it new on ebay. Shipped from China. He already made some research about the warranty before he gave it to me. He made some calls and emails to customer service here in Germany and they told him that he has to send the phone back to China. No warranty in Germany. It is not worth to send it back to China because of duty tax on the way to China. They send him this phone on some special shipping method to avoid this taxes and stay with profitable shipping price. But if you need to send it back they won;t help you at all. And the dispatch price is a no-go.
Since I have decent experience with electronics and flashing various smartphones he gave it to me with a though that I will be able to bring it back to life.
I already said when I started this topic that I suppose that this phone has some damage on the mainboard because of the weird behaviour. I just want to be sure about that and try everything I can before I tell him that he wasted his money by buying this phone.
I want to thank you for your support! If you have some ideas what could I still try I will gladly listen.
kotex said:
Asked my firend about it. The phone is like 1 month old. He was making some pictures and the phone suddenly died and got to boot loop. He bought it new on ebay. Shipped from China. He already made some research about the warranty before he gave it to me. He made some calls and emails to customer service here in Germany and they told him that he has to send the phone back to China. No warranty in Germany. It is not worth to send it back to China because of duty tax on the way to China. They send him this phone on some special shipping method to avoid this taxes and stay with profitable shipping price. But if you need to send it back they won;t help you at all. And the dispatch price is a no-go.
Since I have decent experience with electronics and flashing various smartphones he gave it to me with a though that I will be able to bring it back to life.
I already said when I started this topic that I suppose that this phone has some damage on the mainboard because of the weird behaviour. I just want to be sure about that and try everything I can before I tell him that he wasted his money by buying this phone.
I want to thank you for your support! If you have some ideas what could I still try I will gladly listen.
Click to expand...
Click to collapse
If you have telegram, drop a message @ankurpandeyvns
Hello XDA
As title say, I 'm going share my experience in this thread.
History
I purchased this device almost 8 month back.Purchased from a local store.Was very smooth and i was satisfied with the performance.Battery was good.Got regular update and these updates are from google,so why not install it,right?Then this Android N came,and i was so happy.7.0.0 was good.Then the nightmare 7.1.2 came.Phone started to lag continuously,Battery drained too much.But I was like Okay.May be this will fixed in new update.Then suddenly one day my phone was stuck.Not booting.Stucked at Google.I understood that phone already booted and fingerprint was too working but it showed nothing on display just black light.I was afraid as i didn't purchase it from Google Play or any authorized seller.So no warranty or chance of having replacement.So I started searching about this issue and found not only me many people are facing this.But there are no proper guideline or solving this issue.Tried everything and ended up with Locked Bootloader Irony!
Journey
As i never try to mess with my phone because it was Nexus 5x! So i never touch OEM or try to unlock the bootloader.So i tried to access stock recovery,But Alas! in recovery Volume up and down wasn't working.So I couldn't wipe or factory reset.So Now ended up with :
1.Locked Bootloader
2.Locked OEM
3.Recovery Stuck
Googled and found many solutions but none of them came to solve my issue.So i thought why not flash stock rom.But HOW! Cause fastboot only work with unlocked bootloader.And you can't unlock bootloader when your OEM is locked and you can't unlock it with fastboot.It can be only unlocked from developer option only.GOD!
Now I have only 2 options left:
1.Fastboot mod where no functions working
2.Download Mod (This will save you)
Now fastboot option is out and only download mod option is available.So what can i do with Download Mod?
LGUP TOOL helped me.Downloaded a tot file for Global version (LGH791) and flashed it and stucked at google logo and in recovery too.But next time i flashed the same file in a different way.Ok here it is:
1.Drivers are important here.I'm using windows 10.I have adb and fastboot and Lg drivers.Workplace okay.
2.Opened device manager and change the com port of Android phone 3 to 41. Port Changed!
3.Connected my phone to pc using 3rd party cable (Careful here,try to use original cable.) and entered into download mod and.
4.Opened LGUP Tool ,checked REFURBISHED mod,checked BIN file and select the tot file downloaded before.And quicky close it.(No need to click start)
5.Then again opened lg tool and click start.(BIN Checked and it showed the previously selected tot file).No need add anything new this time,just open and click START.
6.Rebooted and again stucked at Google screen.But wait! recovery is working.Pressing and holding volume up button for a while then a android logo with red cross inside will come up.Now holding power button and volume down button at the same time,Recovery will show and menu is working.Great!
7.Now Wiped cache and factory reset.And after that selected Apply update from Adb sideload
8.My device was connected to pc from the beginning,right? Now i downloaded a file previously called bullhead-ota-opp2.170420.019-c449d2bb.zip from Google Nexus 5x OTA update page.
9.In Adb folder,copied the file and named it ota.zip.Opened a command prompt using shift+right click in the folder.Phone was on Adb sideload mode.Typing this command adb sideload ota.zip
10.This took more than 8-9 minutes to finish.After flashing and phone rebooted.WOW
11.Couldn't believe my eyes.The OTA update was about Android O.I quickly enabled the developer menu and made oem unlcocked and usb debugging on.Boot into bootloader and unlock bootloader with this command fastboot flashing unlock
12.Now bootloader is unlocked and i flashed TWRP recovery for future need.
13.Rebooted the phone and after using for 1 minute the phone freezed again
14.This is the end of the story for today.
Planning
I'm thinking the OTA update was the problem.Now I'm downloading 6.0.1 version.And will do a clean install.Let's see what happens next.
Any kind of help is appreciated.If you think there is something i'm missing here then please suggest.
And Thanks to XDA.I got all these helps from here.Will update the post tomorrow.
You downloaded Android O Developer Preview. Final OTAs are here:
https://developers.google.com/android/ota
Just try flashing newest Factory Image via fastboot, but don't forget to flash TWRP back:
https://developers.google.com/android/images
TBH I NEVER thought this phone will be dead by hardware failure all of a sudden, I dont mind another few hundreds bucks but the problem now is the fking data within it.
Cant even pass google logo if you choose Recovery Mode
GG LG, well played
I have a 16gb variant dead....same issue like urs .....can i use the same lgh791 tot file?... in fastboot it says lgh791 16gb
usefully
usefully
I STRONGLY recommend that the original post is corrected to change "Download mod" to "Download mode" in all of its four occurences.
Same for one ocurrence of "Fastboot mod".
It is horribly confusing as it is, as calling them "mod" implies some modification you have to apply to the phone (be it software or hardware).
same of my expirience, flash 4CoreOreo..
my nexus 5x now is fully working
the_uker said:
I STRONGLY recommend that the original post is corrected to change "Download mod" to "Download mode" in all of its four occurences.
Same for one ocurrence of "Fastboot mod".
It is horribly confusing as it is, as calling them "mod" implies some modification you have to apply to the phone (be it software or hardware).
Click to expand...
Click to collapse
I suppose that makes sense. Then again, when an instruction is telling you to boot into download mod.....using common sense I'm gonna understand that's a typo and they meant download mode. But you're right, for some folks that may be a bit of a challenge. Common sense isn't as common as it was when I was young.
And the links?
I'm brazilian and i'm having a hard time to find the links to download stuff. Mine is dead and bootloader blocked. The tutorial seems to work but i can't understand well
Interesting. Thanks
**EDIT**: Had to send the phone back as the bootloader was locked and nothing was flashing. I believe they EDL flashed it and all is good now. Unlocked the bootloader on the new one just in case this happens again, I will be able to fix
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
BACKSTORY:
Okay, so I recently updated to MiUI 12 and it wasn't great. My apps were crashing all the time and the general stability was not good. (this was around a week ago)
Then earlier today, my device just went into the boot screen (the colourful MiUI one) and stayed there for over 30 mins.
I forcefully restarted my phone using the volume buttons and it would go into the first "Mi powered by android" screen and then back into the colourful MiUI screen.
Then it would stay in the MiUI screen for a minute or so, and then restart itself, continually repeating the process.
At this stage, I had no custom recovery, had not tried to tinker with the phone (other than disabling some default apps through FastbootTools), and everything was fine until MiUI 12 came.
WHAT I DID:
I was able to access the default XiaoMi recovery (3.0?) and tried to wipe the data and restart, but nothing would change.
I tried to use the MiPC Suite after selecting in recovery, but it would recognise my device, even after updating to latest version.
I tried to use FastBootTools, but that would also not recognise my device.
I tried to use XiaoMiTool V2 (by Francesco Tescari), and that did recognise my device. I selected "my device is bricked" option and it did its thing, downloading and trying to sideload something. And then on the device, it got stuck at 4.99% with a message "You won't be able to turn on your device if you try to reboot it", and on the XiaoMiTool, the progress was at around 400% and said -70 seconds remaining, and around 40000MB / 3000 MB or something along those lines. Basically, **** was ****ed.
So I just let it sit there for a bit and then the XiaoMiTool V2 gave and error, "miui sideload failed adb execution exception adb sideload exited with status 1"
I had 3 options,
"Retry step"
"Go back to previous step"
"Cancel and abort"
I tried to search what the error was, but all of the results came from years ago, for different devices. So I clicked "Cancel and abort", only for the device to remain unchanged (4.99%, You won't be able to turn on your device if you try to reboot it), while the XiaoMiTool V2 went back to the start screen.
So I tried it again, the "my device is bricked option", and went through the same steps, and now it is stuck at "Pushing file to the device via ADB, ..., Starting MIUI sideload procedure".
Now I am stuck. My phone screen just says
"4.99%, You won't be able to turn on your device if you try to reboot it"
and my XiaoMiTool is stuck on the beginning sideload procedure.
Closing
If you managed to read this far, thanks, even if you don't have a solution. I appreciate anything that could help with this situation.
U could use the official tool by xiaomi and install your stock miui 12 rom, it's called miflash
Idk about downgrade if u wanted to flash miui 11 i heard there is some problems related to that so, always try official xiaomi tools first before trying other stuff
Ps : if it doesn't detect ur device in miflash there is a button called update or install driver I don't remember exactly press it and u should be fine
Badis st said:
U could use the official tool by xiaomi and install your stock miui 12 rom, it's called miflash
Idk about downgrade if u wanted to flash miui 11 i heard there is some problems related to that so, always try official xiaomi tools first before trying other stuff
Ps : if it doesn't detect ur device in miflash there is a button called update or install driver I don't remember exactly press it and u should be fine
Click to expand...
Click to collapse
I tried to install the drivers, and it says it was successful, but it still does not recognise my device in fastboot mode. However, it does seem to recognise my device in the default recovery, when selecting the "Connect with MiAssistant", which prompts to use the Mi PC Suite.
Any other ways to help it recognise in fastboot mode?
coolboy328509 said:
I tried to install the drivers, and it says it was successful, but it still does not recognise my device in fastboot mode. However, it does seem to recognise my device in the default recovery, when selecting the "Connect with MiAssistant", which prompts to use the Mi PC Suite.
Any other ways to help it recognise in fastboot mode?
Click to expand...
Click to collapse
Try another computer and another USB port...
The solution will benunder fastboot. You have to unclock your bootloader and flash a custom twrp or flash a stock rom using miflash
Hi, can you give any updates? I think i'm on the same boat. I have a Xiaomi Redmi Note 9 pro
EdoDT99 said:
Hi, can you give any updates? I think i'm on the same boat. I have a Xiaomi Redmi Note 9 pro
Click to expand...
Click to collapse
this is totally the wrong thread for ur device
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Is there anyone on the platform who knows on this issue?
Or it's just a platform of Ads?
oooooof, sounds like a harsh brick from some sort of malware downloaded into the device or your kids diddled with some kernel settings somehow
is your device running on qualcomm snapdragon? i have the fix for it in this site
but first try the update option on the recovery, might fix something
arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
found some fix on a russian website, gonna translate it:
im gonna make a warning there off-script of the russian website, this is NOT guaranteed to work. if it doesnt, send it off for repairs.
what do you need to do this:
1 - fully charge the phone
2 - a working usb cable
3 - a computer with wifi on it (i can tell you have it since you likely posted it on the computer)
4 -you should have Mi flash pro
5 - a recovery image on chinese (WARNING: 1.9 GB, BE PATIENT)
6 - actually working braincells and hands ( you guaranteedly have em)
THE STEPS:
1 - Load in mi flash pro and register in it under your name (not always under your name)
2 - press recovery
3 - you should see a lightning bolt icon along with the IMEI of your device
4 - type in the path of the firmware
even if your device shows your system has been destroyed you can still boot into recovery.
5 - in your device boot into recovery
6 - you see connect with mi assistant? choose that option and confirm it
your device should direct you to connect the usb from your computer to your device
7 - After you setup everything you should see your device, if not, press refresh device, then you should see the flash button, press it
8 - and there begins the magic - wait 5-10 mins for the firmware to initialise, DO NOT DISCONNECT THE USB FROM YOUR DEVICE AT THIS POINT, IF YOU DO, YOU WILL SCREW IT UP AND HAVE TO DO IT ALL OVER AGAIN!
if you dont screw up and your device actually boots congratualtions! the power of xi jing ping has restored your phone to normal with a small drawback - its all in chinese
worry not, it doesnt end here:
9 - Unlock the bootloader AKA Unlock OEM (This is important, because otherwise you will brick yourself again and will have to do it all over again)
10 - boot your device into fast boot and flash the global firmware onto your device (the global firmware can be found on the same xiaomiui website you got the chinese firmware from)
i hope this lengthy guide helps
arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
crud, i forgot the critical part:
it doesnt boot you to the average xiaomi screen, its the A1 model
at this point you need to use the ADB to flash the chinese firmware and unlock the bootloader on the chinese firmware, then flash the global one
though you can still use the same method i typed above
How's the progress so far?
Lamntox said:
oooooof, sounds like a harsh brick from some sort of malware downloaded into the device or your kids diddled with some kernel settings somehow
is your device running on qualcomm snapdragon? i have the fix for it in this site
but first try the update option on the recovery, might fix something
Click to expand...
Click to collapse
I tried recovery also try to format the disc with recovery mode(power on + Volume up ) but then it stuck on the formatting disc... line
arshad4u said:
I tried recovery also try to format the disc with recovery mode(power on + Volume up ) but then it stuck on the formatting disc... line
Click to expand...
Click to collapse
Yup, the device is probs bricked
Have you tried the other methods i described?
arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
Hi i dont have that kind of a problem!
my problem is when i try to do oem unlock it says error 0x1002 and idk what to do (i have same phone btw) i tried anything but nothing works!
Hello...
I am looking for a working way to root my SM-T555
The device is running android 7.1.1;
base ver. "T555XXU1CQHA";
build ver. "NMF26X.T555XXU1CRG1";
Samsung experience 8.5;
Android security patch August 2017.
So far, the several attempts I made using every T55X related software I found in this website have been unsuccessful.
It would seem that the rooting software available is for "Marshmallow only", thus not Nougat specific,
though I read some comments stating that the TWRP made for MM worked on Nougat too and, after that, Magisk would/could do the job...
So I gave it a try but, after installing the recovery, my tablet got stuck every time: refused to boot normally
and if I turned it off, long pressing the power key, I couldn't turn it on again as if it was bricked.
Every time I had to re-start it in download mode and re-flash the original stock rom with Odin in order to have it working again.
On top of that, the "OEM unlock" key is not present in the developer mode list: none of the "date changing tricks" I found around the web seems to fit this model.
I am inclined to believe this "might" be the mother of my problems in rooting the device though, supposedly, the patches were not for Nougat, anyway...
The developer options page, once activated, can only be "turned off" ("greyed out") but cannot be deactivated;
while, on other devices, if you turn it off the page usually disappears after rebooting then you have to tap 7 times the build version, again, in order to make it appear.
I never had problems in rooting any of the phones and tablets I have /had, including an SM-T819 running Nougat 7.1.1,
thanks to the great job done by the coders in this community to whom I would like to express my appreciation for what they do for the benefit of us all.
But this thing seems to reject everything I throw at it and it's been the most stubborn "phone like object" I ever fought with.
So far I am the one loosing the fight... I wish some of you guys could give me the means to defeat it.
Thanks in advance to whoever may be available to help me out.
Flash TWRP, then install Magisk in TWRP.
V0latyle said:
Flash TWRP, then install Magisk in TWRP.
Click to expand...
Click to collapse
thanks for your reply.
maybe my post was too long and boring so you didn't read it all
Of course I already tried the solutions posted in the page you suggested but they did not work.
not the autoroot files, not the recovery, etc...
I quote: "after installing the recovery, my tablet got stuck every time: refused to boot normally
and if I turned it off, long pressing the power key, I couldn't turn it on again as if it was bricked.
Every time I had to re-start it in download mode and re-flash the original stock rom with Odin in order to have it working again."
If there is a TWRP file specific for my Nougat version available I'd be happy to give it a shot
endlessquest said:
thanks for your reply.
maybe my post was too long and boring so you didn't read it all
Of course I already tried the solutions posted in the page you suggested but they did not work.
not the autoroot files, not the recovery, etc...
I quote: "after installing the recovery, my tablet got stuck every time: refused to boot normally
and if I turned it off, long pressing the power key, I couldn't turn it on again as if it was bricked.
Every time I had to re-start it in download mode and re-flash the original stock rom with Odin in order to have it working again."
If there is a TWRP file specific for my Nougat version available I'd be happy to give it a shot
Click to expand...
Click to collapse
Did you follow a guide when flashing TWRP? Did you unlock your bootloader?
You need to be clear and concise in your posts as yo what you did and how.
V0latyle said:
Did you follow a guide when flashing TWRP? Did you unlock your bootloader?
You need to be clear and concise in your posts as yo what you did and how.
Click to expand...
Click to collapse
of course I did follow the guide by the book. also, the recovery appears to be installed properly, Odin showing a nice green PASS sign, but it doesn't work anyway
now about unlocking the bootloader, as I mentioned in my first post:
"the "OEM unlock" key is not present in the developer mode list: none of the "date changing tricks" I found around the web seems to fit this model.
I am inclined to believe this "might" be the mother of my problems in rooting the device"
every time I had to re install the system, so there clock want back to zero. Maybe I should be waiting for the allotted number of days to pass on order for the OEM unlock key to appear...
but before my first attempt to root the device, almost one month was past and the OEM unlock key wasn't there, notwithstanding...
I hope there was a chance that the bootloader was already unlocked...
to be concise (schematic):
tablet in download mode
untick auto reboot in Odin
AP loaded with "smt550_cf-autoroot.tar"
flash with Odin, OK, green sign PASS
reboot manually home+volume down+power,
then switch to volume up when screen becomes black
the Samsung logo appears and stays there indefinitely
So I turn the device off, long pressing the power key
then I try and turn on the tablet but does not turn on anymore,
not even pressing the power button for 30 second
then I press home+volume down+power again
to enter download mode and reinstall stock rom
(the same happens with
sm-t550_p550_p555_cf-autoroot.tar
or twrp_3.0.2-1_sm-t550_mm_7816.tar,
I also tried
twrp_3.1.1-1_sm-t355_251117
remark: none of them mentions T555 nougat)
Put your tablet in Download Mode and take a picture of the text at the upper left of the screen.
V0latyle said:
Put your tablet in Download Mode and take a picture of the text at the upper left of the screen.
Click to expand...
Click to collapse
What process did you follow to unlock your bootloader?
Stop trying to use Autoroot. Let's figure out what we need to do to get TWRP on your device. Once we do that, you can flash Magisk in TWRP for root.
Please read this guide, sections 1 through 4 (don't worry about the GSI stuff) and tell me what you have or have not done.
ok, I wasn't able to do this:
Unlock Bootloader
Enable Developer Options and turn on OEM Unlocking
OEM Unlocking is missing in the list, as I mentioned in my previous posts
I tried the date change trick but it didn't work
endlessquest said:
ok, I wasn't able to do this:
Unlock Bootloader
Enable Developer Options and turn on OEM Unlocking
OEM Unlocking is missing in the list, as I mentioned in my previous posts
I tried the date change trick but it didn't work
Click to expand...
Click to collapse
This is the first step. You cannot flash custom or modified images if the bootloader is locked.
Connect to the Internet and check for updates in system options, then check Developer Options again.
I did that step too, several times:
the system found an update available
the first times I cancelled the download
then I downloaded the update without installing it
then I tried and installed it
no result at all the attempts: the OEM Unlock key does not appear in developer options
endlessquest said:
I did that step too, several times:
the system found an update available
the first times I cancelled the download
then I downloaded the update without installing it
then I tried and installed it
no result at all the attempts: the OEM Unlock key does not appear in developer options
Click to expand...
Click to collapse
Has it ever appeared before?
V0latyle said:
Has it ever appeared before?
Click to expand...
Click to collapse
it is the first time I work on this specific device, so I couldn't tell: so far I couldn't find the OEM unlock option in the list
it never happened before on any of the several devices I have rooted in my life,
included another Samsung tablet SM-T819 running Nougat 7.1.1: the option was right there and all I had to do is tick it.
I used fastboot for other brands
I wish there was a way to use fastboot to unlock the bootloader on Samsung
if there is any I don't know it
adb is working, but when I give the "adb reboot fastboot" command, the tablet enters the download mode and fastboot does not see the tablet anymore from the computer
endlessquest said:
it is the first time I work on this specific device, so I couldn't tell: so far I couldn't find the OEM unlock option in the list
it never happened before on any of the several devices I have rooted in my life,
included another Samsung tablet SM-T819 running Nougat 7.1.1: the option was right there and all I had to do is tick it.
I used fastboot for other brands
I wish there was a way to use fastboot to unlock the bootloader on Samsung
if there is any I don't know it
adb is working, but when I give the "adb reboot fastboot" command, the tablet enters the download mode and fastboot does not see the tablet anymore from the computer
Click to expand...
Click to collapse
Samsung devices do not have a fastboot mode.
Since this is a Snapdragon device, it probably cannot be unlocked, especially if it was marketed in the US.
Only Exynos and international Snapdragon devices can be unlocked, unfortunately.
V0latyle said:
Samsung devices do not have a fastboot mode.
Since this is a Snapdragon device, it probably cannot be unlocked, especially if it was marketed in the US.
Only Exynos and international Snapdragon devices can be unlocked, unfortunately.
Click to expand...
Click to collapse
actually I am in Rome, Italy so I am quite positive it was marketed here...
is there a way to know for sure whether or not it is international?
the Samsung SM-T819 I am writing from has a snapdragon chip
but I had no problem unlocking/rooting it,
I bought both the devices here in Rome
now that's a mystery...
endlessquest said:
actually I am in Rome, Italy so I am quite positive it was marketed here...
is there a way to know for sure whether or not it is international?
Click to expand...
Click to collapse
Usually the model number is a good indication with phones - the G908U vs G908N for example, but I don't see that being the case here
Have you tried signing into a Samsung or Google account on the device before checking for updates and looking for OEM Unlocking?
V0latyle said:
Usually the model number is a good indication with phones - the G908U vs G908N for example, but I don't see that being the case here
Have you tried signing into a Samsung or Google account on the device before checking for updates and looking for OEM Unlocking?
Click to expand...
Click to collapse
I did that too...
on a freshly installed rom:
I connected the internet thru wireless
signed into my Google account
completed the tablet configuration, etc
then I went and enable the developer options
no OEM Unlocking yet again...
endlessquest said:
I did that too...
on a freshly installed rom:
I connected the internet thru wireless
signed into my Google account
completed the tablet configuration, etc
then I went and enable the developer options
no OEM Unlocking yet again...
Click to expand...
Click to collapse
You manually checked for an update too?
Did you try disconnecting from the Internet, disabling network time, and manually setting the time ahead 1 week?