1) Does not boot to TWRP. FAILED (remote: Failed to load / authenticate boot image: Load Error)
2) The bootloader is unlocked and can not be unlocked. FAILED (remote: Flashing Unlock is not allowed
3) Therefore I can not flash images of any kind, nor use MiFlashTool
4) MiUnlock does not work (current account can not unlock this device)
5) "Corrupted device" appeared, now it only stays locked in the "Android One" logo.
6) This happened to accidentally block the bootloader after trying to install the beta of Pie (which as it says in the post, you can not point them with your finger, but when you try to put the command "flashing critical" it tells you that the device is locked with oem unlocked and everything breaks.)
{
"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"
}
Any suggestions? Is there something to do, or direct to the trash?
I think deep flash with test points is the cure. Check xda and Google you'll find the method, you'll have to disassemble your phone though.
if you can enter fastboot you should be able to enter EDL aswell. Did you try MiFlash in EDL?
windforce3425 said:
if you can enter fastboot you should be able to enter EDL aswell. Did you try MiFlash in EDL?
Click to expand...
Click to collapse
C:\Users\guzma>fastboot oem edl
< waiting for device >
...
FAILED (remote: Device is already locked!)
finished. total time: 0.030s
The only possibility to get into EDL would be with test points but even with that you have no guarantee it will actually work out. Also that would void your warranty. Have you tried contacting Xiaomi and try to explain them your problem?
I have the same issue. Device is stuck on android one logo overnight. No changes were made to the device.
I tried the miflash and i get same error Flashing is not allowed in lock state.
If i try and using Fastboot OEM Unlock i get the following:
C:\Tools\platform-tools>fastboot.exe oem unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.008s
If i use the fastboot that came with the mi unlock tool, i get the following error
C:\Users\Downloads\miflash_unlock_en_3.3.827.31>fastboot.exe oem unlock
argc is 2
Anyone have any suggestions?
Flash the rom by fastboot or flash stock image and then only boot tge twrp image.
This might be solve your problem.
And main tip keep your device charge if battery will totally drain then your device will not stand on his speakers.
I have that experience with my past device which has same problem.
The fix for this is flash rom stock with Mi Flash in EDL Mode (touch test points with two clips, battery and screen flex connected, and connect to PC (with qualcomm hs drivers).
In miflash appears "com##" and u can flash the rom.
u need a kit to dissamble it
AlvaroBenitez99 said:
The fix for this is flash rom stock with Mi Flash in EDL Mode (touch test points with two clips, battery and screen flex connected, and connect to PC (with qualcomm hs drivers).
In miflash appears "com##" and u can flash the rom.
u need a kit to dissamble it
Click to expand...
Click to collapse
Did you fix yours?
So if I can't get into Developer Mode to enable OEM unlocking, (Reason being device is stuck on Android One Bootup Logo) is my only option to try and get device into EDL mode in order to flash it?
Or can I use an EDL cable and will that get around me having to open up the device?
After having device sit as a paper weight for a few months, i broke down and ordered a phone repair kit. Opened device up and flashed via test point method. Worked Flawless. Time to enable OEM unlock so i don't have to open it up again. Thanks to community for all the help.
Thanks, it worked for me. My client Mi A2 now live it own life
I install jasmine__V10.0.8.0.PDIMIXM and after I set "fastboot oem lock" but Now my MI A2 Can't enter in OS.
I have this message on screen
"Your device has loaded a different operation system"
and another page says
"Your device software can'tbe checked for corruption. Plese lock the bootlader.
But when I check in fastboot I have bootloader locked.
Any suggestion to unlock ? I can't enter in OS.
Thanks
I had a similar issue and I solved it by entering fastboot mode and using the "fastboot flashing unlock_critical" method. After that I could flash the stock rom with MiFlash Tools.
Related
OK here is my problem,
I got a brand new Xiaomi Mi5 64GB and the first thing that I did was to connect it with Mi PC Suite to check for updates.
It found an update and started to update until it failed, after that the device couldn't normal boot or recovery boot (Vol+ and POWER went to a black screen with "mi logo" same as normal boot).
View attachment 3788573
I can only boot on fastboot mode, but can't do anything in the fastboot as BL is locked.
Official BL unlocking method can't work as device isn't linked to any Mi Account and MiFlashUnlock can't verify my device.
{
"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"
}
So my questions is, can I someway repair my phone with QPST or would you suggest another solution?
en.miui.com/thread-291785-1-1.html
wissou050987 said:
en.miui.com/thread-291785-1-1.html
Click to expand...
Click to collapse
in this guide have to boot into recovery, i CANT boot into recovery, got no recovery.
you have to flash with miflash tool booting into fastboot then
wissou050987 said:
you have to flash with miflash tool booting into fastboot then
Click to expand...
Click to collapse
MiFlash cant flash anything as bootloader is locked.
Try: http://en.miui.com/thread-291785-1-1.html
It works fine
tiflao said:
Try: http://en.miui.com/thread-291785-1-1.html
It works fine
Click to expand...
Click to collapse
Read OP again please.
1. I CAN'T boot into recovery.
2. I CAN'T boot EDL.
3. I CAN boot just into Fastboot, but Bootloader is Locked.
4. I CAN'T unlock BL via official methode as there is no linked Mi Account on Device.
I think that i need a hardware way to unlock BL.
Have you tried this method to see if it works?
http://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
VirusPlus said:
Read OP again please.
1. I CAN'T boot into recovery.
2. I CAN'T boot EDL.
3. I CAN boot just into Fastboot, but Bootloader is Locked.
4. I CAN'T unlock BL via official methode as there is no linked Mi Account on Device.
I think that i need a hardware way to unlock BL.
Click to expand...
Click to collapse
You CAN boot into recovery, don't be silly. Have you read the instructions?
Hold volume up and power button and a MI logo should came up, that's the recovery.
abyssq said:
You CAN boot into recovery, don't be silly. Have you read the instructions?
Hold volume up and power button and a MI logo should came up, that's the recovery.
Click to expand...
Click to collapse
Recovery was a black screen with a white phone, not "mi".
Phone is not detectable anyway if i normally or vol+ boot.
Im not a noob i know what recovery is, so i need answers with the facts that i mention before, no recovery, no edl, unlockable bl.
Im gonna send it to repair shop anyway but still my situation is a big problem that xiaomi should look into it. I get bricked via official update tool, and i cant unlock bl cause xiaomi's unlocking tool stupidly requires linked mi account on device to verify.
When you boot into fastboot and update in mipc suite, it doesn't work ?
I don't understand why official tool need unlock bootloader, it's insane from Xiaomi
rcd1030 said:
When you boot into fastboot and update in mipc suite, it doesn't work ?
I don't understand why official tool need unlock bootloader, it's insane from Xiaomi
Click to expand...
Click to collapse
Mi PC Suite doesn't recognize device in fastboot mode, it returns a screen to connect in normal mode first.
Only MiFlash can see the device in fastboot but it needs unlocked BL to flash the Official fastboot ROMs. Madness!
Aarff just, you're right
Just speculation but maybe can you reboot in recovery with adb commands ? (adb reboot recovery)
Or maybe download twrp, run shell from where it is saved and run
Code:
fastboot boot twrp.img[
?
VirusPlus said:
Recovery was a black screen with a white phone, not "mi".
Phone is not detectable anyway if i normally or vol+ boot.
Im not a noob i know what recovery is, so i need answers with the facts that i mention before, no recovery, no edl, unlockable bl.
Im gonna send it to repair shop anyway but still my situation is a big problem that xiaomi should look into it. I get bricked via official update tool, and i cant unlock bl cause xiaomi's unlocking tool stupidly requires linked mi account on device to verify.
Click to expand...
Click to collapse
Oh yes sorry, it's a phone, my bad.
Then the recovery works fine for you, just the PC doesn't recognise it, which is driver or windows problem, not your phone.
SpinoRex: Fastboot doesn't work because of the locked bootloader. Only option is the official recovery with chinese mi pc suite.
check this post : en.miui. com/thread-299790-1-1.html
You need Engineering Flash Cable
They are in the same situation ... solved?
Mi suite in chinese
You may try to use MI SUITE in Chinese. I was in your exact situation trying to remove a fake rom from my MI5, but with this I solved all the issues.
Just one advice: don't use a pre-loaded ROM, let the program to download it from the internet.
you can boot your device into edl mode with a special fastboot
just type "fastboot reboot" to go to the Edl mode and flash rom with miFlash
Helo Guy,
I've search all the xda forum and googling still no result.
I've tried lot of sollution (flash using pcsuite, miflash, fastboot command, etc) stil had no succed.
Really despeate trying to fix this phone for 3 days, really need help.
Problem :
I bught used Mi 3 and, use it normal. after reset it begin asking password
I dont have email and phone number from the person that i bught from
{
"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"
}
after that i reboot to recovery mode, tried to wipe All Data but failed, but succes to wipe cache and reboot
and it display other message in chinese language,
i've tried insert password and generate other message that i dont understand after that it reboot into recovery mode (could anyone translate it plz?)
exising condition :
1. can boot into recovery mode
2. can boot into fastboot
3. The phone still can do normal thing such as change volume, screenshoot, etc.
Solution that i have tried (no success) :
1. flash using mi pc suite.
succces download all filed (1.1gb in 3 hours doh), and then it says cannot continue because error
2. fastboot tips from khanmdsajid
running fastboot manually from command line
Error : FAILED (remote: Partition table doesn't exist)
3. fastboot tips By Sk.D in XDA forrm
running fastboot manually from command line
Succes running all command, but still request for password after reboot
4. fastboot tips using script from HarsimratSethi
running fastboot using miflash
Error : FAILED (remote: Partition table doesn't exist)
5. fastboot tips from varalex
running fastboot manually from command line
Really need enlightment guys..
Thanks Before, sory for my poor english.
anyone?
langithitam said:
anyone?
Click to expand...
Click to collapse
Why are you posting here in Mi 3's forum? Post in Redmi 3's forum to get support. Please move this thread.
lokesh.acm said:
Why are you posting here in Mi 3's forum? Post in Redmi 3's forum to get support. Please move this thread.
Click to expand...
Click to collapse
My Bad, my phone is a Mi 3 not a Redmi 3. So i post on the right forum..
I'm Chinese, the first image is saying, "To start android, please input password"
the second image, "your inputted password is correct, but the data recovery failed, data lost, to use your phone, reset to factory settings"
for the last image, the "fastboot oem edl"
should be "fastboot reboot-edl"
you can try it again
Hugo Tai 100 said:
I'm Chinese, the first image is saying, "To start android, please input password"
the second image, "your inputted password is correct, but the data recovery failed, data lost, to use your phone, reset to factory settings"
for the last image, the "fastboot oem edl"
should be "fastboot reboot-edl"
you can try it again
Click to expand...
Click to collapse
Hy Hugo thanks for the reply,
i've tried to run that command, "fastboot reboot-edl"
Seems that it doesn't recognized that option command.
langithitam said:
Hy Hugo thanks for the reply,
i've tried to run that command, "fastboot reboot-edl"
Seems that it doesn't recognized that option command.
Click to expand...
Click to collapse
account verification was included only in newer miui version
flash twrp install miui 7 or 6 then upgrade to miui 8 .
MIUI version 8 require new partition table may be thats why you cant flash older miui version like miui 5 you are flashing version 34 and version 34 in global version is miui 5
so solution is flash twrp flash miui version global version or miui v8 using miflash (but then again it will ask for phone verification in miui 8)
best sol. use miui 7 global / xiaomi.eu version or any custom rom like cyanogenmod aosp
Hello, Xiaomi MI3 doens't have Emergency Download Mode, you have to reboot to fastboot (using volume down and power). After that you have to use MiFlash 20151028 and download FASTBOOT Rom for ur xiaomi (idk TD-SCDMA or WCDMA version), and flash it via MiFlash. If it will not solve your problem, we will try other thing.
PS: If you can't download it (the MiFlash) I could post it here. Newer version of MiFlash will give errors on Mi3.
Hi, today i tried to install MIUI 10 following this video: https://www.youtube.com/watch?v=eD5ftq6lTKo
When i could installed it, i tried to re-lock the bootloader with this other video: https://www.youtube.com/watch?v=9C47rmEKkys
But when i reboot the phone, on screen was this message: The system is destroyed, press power button to shutdown.
I tried to unlock again the bootloader to install the system but i receive this message from cmd: FAILED (remote: Token Verify Failed, Reboot the device
)
I don´t know what to do, i tried with test points to flash with miflash, i tried with miflash unlock but i don´t have an account of xiaomi.
when i use this command: fastboot flashing unlock_critical i receive this message: Command not support: the display is not enabled'
Somebody help me :crying:
Flash stock ROM with mi flash
I tried that but miflash show this message: Mismatching image and device. Only have a success message when i flash the wayne rom but ends on 1 second but doesn't install the system.
On htcmania says because the drivers are wrong but i reinstalled from the tutorial ones, google drivers, and miflash drivers and always says the same.
Now i trying with EMMC dongle program(cracked) and it seems like it´s installing the system, but since yesterday, it looks last forever.
{
"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"
}
Well that program does not did anything, i discover that when the phone is on fastboot mode and plug off the battery, miflash make a process success but it last 24s and don´t do anything, maybe that could be useful for something.
I don´t know what more to do with my phone.
Click to expand...
Click to collapse
If ur bootloader is unlocked try
Fastboot reboot edl
Now try to flash with mi flash in this mode
Note: your phone will look like it's turned off (black screen) in this mode
---------- Post added at 02:35 AM ---------- Previous post was at 02:29 AM ----------
I noticed that you where trying to flash Wayne images in the photo that u attached? Do u own a mi A2 or a 6x?
If you convert your mi A2 to 6x you cannot relock your bootloader
And make sure to delete system update folder and change some Dev conf file to flash miui on your android one device
That command (Fastboot reboot edl) doesn't work, when i send it i get this error: Device is already locked!
The only way my phone can be on edl mode is by Test points, and the miflash says that my phone have a locked bootloader if i try to flash the system.
What is the output of this command
Fastboot oem unlock
hv2002 said:
What is the output of this command
Fastboot oem unlock
Click to expand...
Click to collapse
Araxielfenix said:
Click to expand...
Click to collapse
https://youtu.be/ypDU78c4w_Y
Hello, I've been having this problem for about 2 days, well I'll summarize what happened to save mine and your time.
One day I was working with my g5s plus normally (using pixel experience 9.0), the other day I blocked the phone screen normally, but after that it turned off by itself and it is no longer booting the system...
interestingly it normally goes into bootloader and recovery mode, but whenever I try to install a rom, either custom or stock, it always has the same behavior, I install the rom and start the system, it loads up to the motorola logo and it turns off, it's not like a bootloop, it just loads up to the motorola logo and simply turns off.
I've tried many ways to recover, nothing worked, I tried to pass the rom through rsd lite, through motorola manager and of course through adb, I even tried to install a custom rom through twrp, but that always happens.
recently I was passing his latest rom through fastboot adb, when I noticed that during the process two errors appeared in the terminal, does anyone have any idea what it could be? I will leave the images linked here.
1. at the beginning of the rom installation it displays this highlighted 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"
}
2. almost at the end of the installation it displays this same message...
I have been there
Flashing wrong stock firmware caused gpt error.
Best way to do that is this.
Install this to your pc and connect your device in fastboot mode.
Sometimes flashing second time with this tool helps.
If it doesn't help, flash firmware of your model firmware (written on back of your phone like XT****) then with rescue flash assistant tool try again to recover in fastboot mode.
If you want to automate and lazy to write use my flash.bat
Finally you achieved to boot the device but no imei or no 4G
1) Unlock oem lock
2) Flash Validus rom
3) Lock oem flash necessary files (You can use my oemlock.bat )
4) Back to stock with rescue and flash assistant.
By the way when rescue and smart assistant finished downloading your model's stock firmware, find where is it and copy it safe place
lynxrz said:
I have been there
Flashing wrong stock firmware caused gpt error.
Best way to do that is this.
Install this to your pc and connect your device in fastboot mode.
Sometimes flashing second time with this tool helps.
If it doesn't help, flash firmware of your model firmware (written on back of your phone like XT****) then with rescue flash assistant tool try again to recover in fastboot mode.
If you want to automate and lazy to write use my flash.bat
Finally you achieved to boot the device but no imei or no 4G
1) Unlock oem lock
2) Flash Validus rom
3) Lock oem flash necessary files (You can use my oemlock.bat )
4) Back to stock with rescue and flash assistant.
By the way when rescue and smart assistant finished downloading your model's stock firmware, find where is it and copy it safe place
Click to expand...
Click to collapse
Hello I've tried in all ways, I tried to restore the soft through RSDLite, from the lenovo software even by the ADB itself, but I wasn't successful, I think the problem is not hardware either.
ocod said:
Hello I've tried in all ways, I tried to restore the soft through RSDLite, from the lenovo software even by the ADB itself, but I wasn't successful, I think the problem is not hardware either.
Click to expand...
Click to collapse
First step:
Try to find gpt compatible firmware and flash it with fastboot.
Not Adb, not Rsdlite, not lenovo rescue asistant only with fastboot!
You will not get 'permission denied' error while flashing correct gpt partition table. If you find this firmware keep it, it could be correct firmware to go next step.
Examine my flash.bat file and don't flash all of them just these
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
I found it my compatible gpt firmware with downloading 30 GB+ stock firmware files then tried to flash every one of them in fastboot mode. Don't give up. I found the solution about a week. I'll check this post daily and try to help you step by step.
Hi!
I got this new Pixel 7 2 weeks ago, yesterday the battery went completly discharged and now the phone starts into Fastboot mode, with the Enter Reason being boot failure. Recovery mode and rescue mode both fail to load, and just send me back to the Fastboot Mode. I alredy tried a bunch of stuff to fix it, but the phone its still OEM lock so flashing via the Google flash tool its imposible, does anyone has any idea of what can i do to save it?
Did you try this too?
https://pixelrepair.withgoogle.com/carrier_selection
t-ryder said:
Did you try this too?
https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
{
"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"
}
yes, Rescue Mode fails to load, so it gives me Unable to connect the Phone
There's fastboot mode and fastbootD I guess. You can enter fastbootD from fastboot. Maybe I confuse stuff tho, since lately I got a lot of chaos in my head. DYOR.
Have you tried Pixel Flasher?
https://github.com/badabing2005/PixelFlasher/releases
t-ryder said:
There's fastboot mode and fastbootD I guess. You can enter fastbootD from fastboot. Maybe I confuse stuff tho, since lately I got a lot of chaos in my head. DYOR.
Have you tried Pixel Flasher?
https://github.com/badabing2005/PixelFlasher/releases
Click to expand...
Click to collapse
No, i am going to give it a go and update on results
t-ryder said:
There's fastboot mode and fastbootD I guess. You can enter fastbootD from fastboot. Maybe I confuse stuff tho, since lately I got a lot of chaos in my head. DYOR.
Have you tried Pixel Flasher?
https://github.com/badabing2005/PixelFlasher/releases
Click to expand...
Click to collapse
It failed, it gives me "Bootloader is locked, can't flash." and trying to unluck the bootloader with the fastboot commands gives me FAILED (remote: 'flashing unlock is not allowed')
And get into fastbootd and sideload a full OTA somehow?
https://developers.google.com/android/ota?hl=en
Or is adb disabled?
t-ryder said:
And get into fastbootd and sideload a full OTA somehow?
https://developers.google.com/android/ota?hl=en
Or is adb disabled?
Click to expand...
Click to collapse
adb its disabled and entering recovery mode also fails, the phone its pretty much new, so i didn't have time do much with it.
I've seen this before where people's phones have "died" when letting the battery run out. I haven't seen any successful methods to recover (not to say there isn't).
Since you're bootloader is locked and you don't have OEM Unlocking enabled you won't be able to flash anything via fastboot. If OEM Unlocking were enabled you would be able to use Android Flash Tool as that will unlock your bootloader during the process as long as you have OEM Unlocking enabled.
Maybe try to see if Pixel Flasher can get you into recovery mode to see if you can sideload an OTA, although given the circumstances I'm doubtful it will. By the way, you don't need USB Debugging enabled to sideload an OTA. Being in sideload mode enables a very limited set of ADB commands on Pixels, including adb sideload <imagename>.zip.
Good luck...
Lughnasadh said:
I've seen this before where people's phones have "died" when letting the battery run out. I haven't seen any successful methods to recover (not to say there isn't).
Since you're bootloader is locked and you don't have OEM Unlocking enabled you won't be able to flash anything via fastboot. If OEM Unlocking were enabled you would be able to use Android Flash Tool as that will unlock your bootloader during the process as long as you have OEM Unlocking enabled.
Maybe try to see if Pixel Flasher can get you into recovery mode to see if you can sideload an OTA, although given the circumstances I'm doubtful it will. By the way, you don't need USB Debugging enabled to sideload an OTA. Being in sideload mode enables a very limited set of ADB commands on Pixels, including adb sideload <imagename>.zip.
Good luck...
Click to expand...
Click to collapse
Even trying to get into recovery mode with Pixel Flasher fails.. looks like my only option its asking for warranty and i wanted to avoid that.
Have you tried issuing the command fastboot getvar all to see what slot you're on and what the status of your slots are? Maybe switching slots could get you a boot.
41rw4lk said:
Have you tried issuing the command fastboot getvar all to see what slot you're on and what the status of your slots are? Maybe switching slots could get you a boot.
Click to expand...
Click to collapse
Unfortunately their bootloader is locked so they won't be able to switch slots via fastboot commands. Even if they were able to switch slots they would then have to flash the OS to that slot before being able to boot into that slot since you can only boot into the slot where the OS was last flashed in this circumstance.
I can't get over the fact that you can't just flash an official image on a locked bootloader. I used to be a Moto fan and that was always the good thing about them, as long as it was officially signed, locked or not you could flash the same or updated firmware. Plus if it was qualcomm, when you bricked it would go into edl mode and you could blankflash your way back.
Yet a Google device, who also develops android, you're up a creek unless you unlock your bootloader.