So i try to use the DSU Loader found in Developer Options to flash a GSI, but i forget to unlock the OEM and turn on the usb debug.
After installing a DSU and rebooting, the phone will attempt to boot the GSI but it shows "Your device is corrupt" and will no longer boot.
That said, the phone boot to fastboot mode automatically. But all the options under fastboot is not working, i can't get into the recovery mode and my laptop can't identify my phone when i connect to it.
Is there anyone know how i can fix it?
{
"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"
}
I had the same problem and flashed the boot.img on it and it was fixed.
If that doesn't work you can follow this guide to restore the system (needs to be in fastbootd mode): https://www.droidwin.com/unbrick-nothing-phone-1-flash-stock-firmware-via-fastboot-commands/
misecia said:
I had the same problem and flashed the boot.img on it and it was fixed.
If that doesn't work you can follow this guide to restore the system (needs to be in fastbootd mode): https://www.droidwin.com/unbrick-nothing-phone-1-flash-stock-firmware-via-fastboot-commands/
Click to expand...
Click to collapse
Thanks mate
But you can do it even you haven't enable OEM unlock and USB debug before the phone get bricked?
-
i have the same problem.. only fastboot commands work, anything i do just reboots the phone back to same menu . cant enter fastbootd. i can flash all partitions apart from product..system and some other. these i get error on. i got the bootloader unlocked but thats about it. i also did DU in dev mode then corrupt device.. anyone got a fix for this??
xera3k said:
i have the same problem.. only fastboot commands work, anything i do just reboots the phone back to same menu . cant enter fastbootd. i can flash all partitions apart from product..system and some other. these i get error on. i got the bootloader unlocked but thats about it. i also did DU in dev mode then corrupt device.. anyone got a fix for this??
Click to expand...
Click to collapse
Do you have the latest android platform tools? Try different cables, different ports?
Yes this is a problem on the phone. . Vi tried Windows and Linux , i can send commmands but only Flash some partitions and dont have or cant access bootloader or fastbootd.. so im stuck :/
xera3k said:
Yes this is a problem on the phone. . Vi tried Windows and Linux , i can send commmands but only Flash some partitions and dont have or cant access bootloader or fastbootd.. so im stuck :/
Click to expand...
Click to collapse
Idk if its because of that but you have typo in that command, should be bootloader instead boodloader
What if have you tried to boot into another slot fastboot --active-slot
layz1319 said:
What if have you tried to boot into another slot fastboot --active-slot
Click to expand...
Click to collapse
What command would i use ?
xera3k said:
What command would i use ?
Click to expand...
Click to collapse
So you may want to use fastboot getvar current-slot to get what slot you are currently using. Then use fastboot --active-slot=(the opposite slot you are using) eg.fastboot --active-slot=a / fastboot --active-slot=b. Lastly, fastboot reboot
Ps. Sometimes fastboot --active-slot=a/b may not work so you can try with fastboot --active-slot= other to boot into non current slot. Anyway wish you all the best
layz1319 said:
So you may want to use fastboot getvar current-slot to get what slot you are currently using. Then use fastboot --active-slot=(the opposite slot you are using) eg.fastboot --active-slot=a / fastboot --active-slot=b. Lastly, fastboot reboot
Ps. Sometimes fastboot --active-slot=a/b may not work so you can try with fastboot --active-slot= other to boot into non current slot. Anyway wish you all the best
Click to expand...
Click to collapse
I also am having this issue and tried what you suggested and got this.
Any ideas on how to fix?
Eventually I was able to change the active slot but sadly still looping.
yquitumadbro said:
View attachment 5677361
Eventually I was able to change the active slot but sadly still looping.
Click to expand...
Click to collapse
Try to change it again. I solved with that.
Good evening, I have the same problem after using the DSU Loader, the mobile is stuck like the screenshot in the first post above. I've tried everything but can't unlock anything. Can someone help me ?
If your PC isn't detecting your device while in Fastboot mode, you don't have the correct drivers installed. This may help.
Never try to install non-factory software on a locked bootloader!
Since you didn't enable OEM unlocking, it's unlikely that you'll be able to recover your device. Still, focus on the driver issue for now and we can go from there. Do you have ADB Platform Tools installed?
I installed GSI directly from the smartphone, I don't think I used unofficial software. The pc recognizes the mobile phone in fastboot and I also tried with ADB platform tool, but every time I get the message of device blocked
Dominicus.1 said:
I installed GSI directly from the smartphone, I don't think I used unofficial software. The pc recognizes the mobile phone in fastboot and I also tried with ADB platform tool, but every time I get the message of device blocked
View attachment 5681643
Click to expand...
Click to collapse
ADB commands do not work in fastboot.
fastboot devices should show the device when connected in fastboot mode.
Try fastboot flashing unlock to unlock the bootloader, which will make recovering your device much easier.
I tried everything, Windows never found my device inn fastboot but i plugged om a Linux then voila. Everything works
xera3k said:
I tried everything, Windows never found my device inn fastboot but i plugged om a Linux then voila. Everything works
Click to expand...
Click to collapse
U can't do anything if u r OEM tab is off and you soft bricked and not booting to system.
If unr able to boot in recovery using fastboot menu there do format data it will boot to system
Related
Dear developers and other users!
I have been looking for same issues but I was unable to find answer for my problem.
About a year ago I unlocked and rooted my nexus 7 tablet to use special apps on it.
Today I tried to unroot and lock my device. On my laptop the program(Nexus Root Toolkit) said it was successful so I just needed to reboot the tablet.
After rebooting it stopped on the Google screen with a "Booting failed" text on the top left corner like that:
{
"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"
}
I think I have uninstalled android from the device but I can't Intsall a new one because recovery mode doesn't work and Android is not going to boot.
I can only use Bootloader. Bootloader looks like that:
Once I started my tablet it started in bootloader mode but every other startup fails on Google screen.
Please help me to use my tablet as before without root.
What should I do and how should I do that to get it work again?
Any help would be highly appreciated
Download a factory image from here https://developers.google.com/android/nexus/images and follow this guide to flash it http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Sent from my GT-I8190 using Tapatalk
Carlyle_f said:
Download a factory image from here https://developers.google.com/android/nexus/images and follow this guide to flash it http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Sent from my GT-I8190 using Tapatalk
Click to expand...
Click to collapse
Thank you but I have one big problem... I wouldn't have any trouble if I could run the android os on my tablet BUT after starting up it fails to boot so I can't enable usb debugging which I need for pusshong the new firmware. I wouldn't have any problem if II could be able to access my android setting :/
But I will give a chance for everything.( I need to make my device work befora july 2 because I want to use it on my holiday )
Eurioin said:
Thank you but I have one big problem... I wouldn't have any trouble if I could run the android os on my tablet BUT after starting up it fails to boot so I can't enable usb debugging which I need for pusshong the new firmware. I wouldn't have any problem if II could be able to access my android setting :/
But I will give a chance for everything.( I need to make my device work befora july 2 because I want to use it on my holiday )
Click to expand...
Click to collapse
You don't use USB debugging or adb in fastboot to flash the factory image. Follow the link and read the instructions carefully.
#stayparanoid
Pirateghost said:
You don't use USB debugging or adb in fastboot to flash the factory image. Follow the link and read the instructions carefully.
#stayparanoid
Click to expand...
Click to collapse
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Eurioin said:
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Click to expand...
Click to collapse
Fix your drivers then. Fastboot is the surefire way to fix your issue.
#stayparanoid
Eurioin said:
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Click to expand...
Click to collapse
Its much easier on a Linux machine. All you need to do is open terminal and type "sudo apt-get install android-tools-adb android-tools-fastboot" and hit enter. Then extract the .tar file and double click "flash-all.sh" and choose run in terminal. Absolutely no driver headaches.
If you have access to a Linux machine (mint/ubuntu) or if you can dualboot Linux, this will really help
Sent from my GT-I8190 using Tapatalk
I too have this same issue...
Exception is my Nexus is locked... everytime I try to unlock it, it tries to reboot and never comes back on...
What am I doing wrong?
Thanks for everyone I successfully made my tablet work by flashing a stock android 4.4.2
The solution:
1. I connected to my father's laptop (with Win7 on it and mine had Win8.1 so you MUSN'T try fixing on Win8.1 because of the drivers) because my laptop detected the device as undefined USB component and my father's laptop showed the tablet as Nexus 7.
2. I found a working adb&fastboot here
3. After the download is done unip the file and run RUN ME.bat and type fastboot for help
*If needed after running the RUN ME.bat file type
fastboot oem unlock
Click to expand...
Click to collapse
(this will unlock your bootloader which is necessarry
for the following steps)
4. After reconnecting my device and booting to bootloader mode and downloaded the new firmware (unzipped into the fastboot folder) type fastboot
fastboot update image-nakasi-kot49h (this was the firmware that I needed to "update")
Click to expand...
Click to collapse
5. After the fastboot started working and flashing the new OS (it takes about 5 or 10 minuntes) the tablet will restart and starts optimizing all te apps that you had before (that happened in my case).
6. If you want you can lock your bootloader by giving the fastboot this command:
fastboot oem lock
Click to expand...
Click to collapse
And now I am using Android 4.4.4 on my nexus 7 tablet
Eurioin said:
Thanks for everyone I successfully made my tablet work by flashing a stock android 4.4.2
The solution:
1. I connected to my father's laptop (with Win7 on it and mine had Win8.1 so you MUSN'T try fixing on Win8.1 because of the drivers) because my laptop detected the device as undefined USB component and my father's laptop showed the tablet as Nexus 7.
2. I found a working adb&fastboot here
3. After the download is done unip the file and run RUN ME.bat and type fastboot for help
*If needed after running the RUN ME.bat file type (this will unlock your bootloader which is necessarry
for the following steps)
4. After reconnecting my device and booting to bootloader mode and downloaded the new firmware (unzipped into the fastboot folder) type fastboot
5. After the fastboot started working and flashing the new OS (it takes about 5 or 10 minuntes) the tablet will restart and starts optimizing all te apps that you had before (that happened in my case).
6. If you want you can lock your bootloader by giving the fastboot this command:
And now I am using Android 4.4.4 on my nexus 7 tablet
Click to expand...
Click to collapse
I was hopeful that this would work for me.... I am using a win 8.1 machine and the downloaded fastboot and adb seemed to work fine.
I go to do a fastboot unlock and I get the following:
(bootloader) erasing userdata...
(bootloader) erasing userdata done...
(bootloader) erasing cache...
(bootloader) erasing cache done...
(bootloader) unlocking....
FAILED (remote: (Unknown error code))
finshed. total time: 7.902s
So..... Anyone ? The tablet does ask if I want to Unlock the Bootloader... I select yes and hit the power button to select... yet the tablet goes back to the android screen... The top of the screen says Unlocking now...... yet it doesn't...
Please help...
Please help I can Open my OPT
Ahmed Shawky said:
Please help I can Open my OPT
Click to expand...
Click to collapse
Please I ned any help
My mobile not open
I can not Unlock the boatloader
Huh. There is no information on your post. What do you think XDA is? Can't help until you tell your situation.
Nobody can solve your problem until you explain what happened.
Sent from my ONE A2003 using Tapatalk
Please elaborate on what happened to your phone. Till then check these links out for a possible fix:
http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967
http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
http://forum.xda-developers.com/oneplus-2/general/guide-to-stock-t3341130
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
I have similar problem, so maybe not generating new threat...
I got OP2 from friend. He used Oxygen 2.x (don't know exactly) and decided to flash some custom ROM. And something went wrong
He brought me today his phone and:
- fastboot works,
- device is locked and impossible tu unlock (FAILED (remote: oem unlock is disabled))
- after 2 hours of work I got stock recovery working (using some Chinese Qualcomm recovery tool).
But: I can't unlock BL, I can't flash anything via fastboot (because ->locked), ADB doesn't work too (cant push any file to devices).
When turning on phone it's in bootloop, but I can enter fastboot or stock recovery.
I tried almost all solutions from her and OP forums, but everything false because of locked BL.
ANY ideas? My short knowledge ends here There is probably no any data in device (no system, userdata etc.).
I don't have USB-C pendrive / cable so I cant flash anything from stock recovery. If I'll get USB-C pendrive will it be possible to flash stock ROM with stock recovery?
Does it show up in fastboot devices?
Sent from my Nexus 7 using Tapatalk
Try first-aid for oneplus 2. It's worked for me twice before. It's on XDA but I don't have a link. Search for it. I'm pretty sure it'll work.
EggZenBeanz said:
Does it show up in fastboot devices?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes, It shows. But not much possible to do because of locked BL.
McCullyCullen said:
Try first-aid for oneplus 2. It's worked for me twice before. It's on XDA but I don't have a link. Search for it. I'm pretty sure it'll work.
Click to expand...
Click to collapse
I tried but with no success. All this tools works flashing .img's from fastboot. It's useless for me...
Have you tried the fastboot oem unlock using the device id as part of the command string?
Sent from my ONE A2003 using Tapatalk
No. How to do this?
vonski said:
Yes, It shows. But not much possible to do because of locked BL.
I tried but with no success. All this tools works flashing .img's from fastboot. It's useless for me...
Click to expand...
Click to collapse
try this...... "fastboot -i 0x2a70 oem unlock-go"
worked for me
Thank, but :
C:\Android_sdk\sdk\platform-tools>fastboot -i 0x2a70 oem unlock-go
...
FAILED (remote: oem unlock is disabled)
finished. total time: 0.007s
Same...
It sounds like the ability to unlock the bootloader is disabled in developer options. I think, but I'm only guessing.
{
"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"
}
Sent from my ONE A2003 using Tapatalk
Yes, but I can't boot to system (probably memory is empty- no data) and switch OEM Unlock.
I've got only fastboot and stock recovery.
do any of these help you? I guess you could say your phone is hard bricked due to not booting to OS and not having TWRP recovery?
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
I used this tutorial but I can't get device correctly installed as Qualcomm. I'll try on other pc.
Tapatalk @ OnePlus X
vonski said:
I have similar problem, so maybe not generating new threat...
I got OP2 from friend. He used Oxygen 2.x (don't know exactly) and decided to flash some custom ROM. And something went wrong
He brought me today his phone and:
- fastboot works,
- device is locked and impossible tu unlock (FAILED (remote: oem unlock is disabled))
- after 2 hours of work I got stock recovery working (using some Chinese Qualcomm recovery tool).
But: I can't unlock BL, I can't flash anything via fastboot (because ->locked), ADB doesn't work too (cant push any file to devices).
When turning on phone it's in bootloop, but I can enter fastboot or stock recovery.
I tried almost all solutions from her and OP forums, but everything false because of locked BL.
ANY ideas? My short knowledge ends here There is probably no any data in device (no system, userdata etc.).
I don't have USB-C pendrive / cable so I cant flash anything from stock recovery. If I'll get USB-C pendrive will it be possible to flash stock ROM with stock recovery?
Click to expand...
Click to collapse
Fastboot this, it will DELETE EVERYTHING(no exceptions) (maybe except firmware) and install seraph08's cm13.
https://s.basketbuild.com/devs/Seraph08/oneplus2/fastboot img files
or flash stock OOS2.x official via stock recovery(if MTP or ADB works in stock recovery)
No idea about USB OTG, try dont buy. Might work in TWRP, dont think itll work on stock
or try the soft brick recovery on his basketbuild or other various available threads
Edit: you said fastboot works and then you said it doesnt work, confirm.
I used other PC and other tool including system.bin and userdata.bin. And it finally worked. Unbricked
I wanted to reinstall the stock rom (B360). I booted into TWRP and for some reason I wiped System, Dalvik cache, cache and internal memory (I dont know why I did that). Then I installed the Firmware but it failed probably because my frp was locked and I didnt know about it. Then I rebooted and now I cant boot to the system. When I boot into TWRP it just hangs on the TWRP logo and doesnt go on, eRecovery doesn't work. I can boot into fastboot. Its says that phone is unlocked but frp is locked. I hope that there's a way to unbrick my phone without dc-phoenix
DeathBell said:
I wanted to reinstall the stock rom (B360). I booted into TWRP and for some reason I wiped System, Dalvik cache, cache and internal memory (I dont know why I did that). Then I installed the Firmware but it failed probably because my frp was locked and I didnt know about it. Then I rebooted and now I cant boot to the system. When I boot into TWRP it just hangs on the TWRP logo and doesnt go on, eRecovery doesn't work. I can boot into fastboot. Its says that phone is unlocked but frp is locked. I hope that there's a way to unbrick my phone without dc-phoenix
Click to expand...
Click to collapse
Install the stock recovery and then stock ROM. (You can install the stock recovery when your phone is in bootloader mode and you install it by the cmd in Windows)
Tiagohsoares said:
Install the stock recovery and then stock ROM. (You can install the stock recovery when your phone is in bootloader mode and you install it by the cmd in Windows)
Click to expand...
Click to collapse
Sorry for the late reply. Whenever I try to flash the stock recovery it says FAILED (remote: Command not allowed):crying:. I tried both fastboot flash recovery_ramdisk and fastboot flash recovery, neither of them worked.
After doing some more research (like 3+ hours) I think that the error can't be easily fixed:crying:. Some solutions that I've found that may work all involve either disabling USB debugging and then rebooting and re-enabling it or somthing like that which I can't do since I can't boot into the system or relocking and then unlocking my bootloader which I also can't do without dc-phoenix since my frp is locked. Also I don't know if the dload method will work as I can't access the sd card when I plug my phone to the PC. It may be possible to push files there using adb but I'm not sure if it will work even when I get the right files to my sd card. So unless you guys don't have a better solution, I'm probably going to buy the HCU + DC-Phoenix 3 day licens for 20€ (still a lot better then changing my motherboard for 100+€). Also here's the adb window with the error.
{
"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"
}
Edit: I'm not going to buy DC-Phoenix until somebody says that there's no way to fix my device without it. It's so unfortunate that I probably can't fix my phone for free even when things like fastboot, charging and adb are working and bootloader is unlocked.
DeathBell said:
After doing some more research (like 3+ hours) I think that the error can't be easily fixed:crying:. Some solutions that I've found that may work all involve either disabling USB debugging and then rebooting and re-enabling it or somthing like that which I can't do since I can't boot into the system or relocking and then unlocking my bootloader which I also can't do without dc-phoenix since my frp is locked. Also I don't know if the dload method will work as I can't access the sd card when I plug my phone to the PC. It may be possible to push files there using adb but I'm not sure if it will work even when I get the right files to my sd card. So unless you guys don't have a better solution, I'm probably going to buy the HCU + DC-Phoenix 3 day licens for 20€ (still a lot better then changing my motherboard for 100+€). Also here's the adb window with the error.
Edit: I'm not going to buy DC-Phoenix until somebody says that there's no way to fix my device without it. It's so unfortunate that I probably can't fix my phone for free even when things like fastboot, charging and adb are working and bootloader is unlocked.
Click to expand...
Click to collapse
It seems that you need just to perform FRP unlock with HCU client.... After that you can flash twrp, etc....
Also you can try method from @vovan1982
"Small manual: removing frp lock.
If you have frp_lock and have not TWRP. Download in FF (FirmwareFinder) third file of firmware (example: update_full_WAS-L21_hw_ru.zip), unpack. Run DCPhoenix small update.app, and when DC Phoenix open back_door, detach usb-cable. On PC run cmd.exe and flash this frp.img"
Good luck!
Alexxxx1 said:
It seems that you need just to perform FRP unlock with HCU client.... After that you can flash twrp, etc....
Also you can try method from @vovan1982
"Small manual: removing frp lock.
If you have frp_lock and have not TWRP. Download in FF (FirmwareFinder) third file of firmware (example: update_full_WAS-L21_hw_ru.zip), unpack. Run DCPhoenix small update.app, and when DC Phoenix open back_door, detach usb-cable. On PC run cmd.exe and flash this frp.img"
Good luck!
Click to expand...
Click to collapse
I fixed my phone using the 1th method in dc-phoenix already :laugh:, the HCU frp thing didnt work because my device model wasn't supported. And I didn't know where to flash the frp.img file. But now my device is working great:fingers-crossed:.
if someone read this or newers, watch this video: it works for frp lock
i tried to follow every guide but no help. tried flashing back to factory still nothing. first when booting from twrp it would say no OS. i finally got that to go away but now it just keeps booting into android power loop. tried erasing all data nothing helps. it also tells me software is corrupted. can someone help plzzz
dumberthandumb said:
i tried to follow every guide but no help. tried flashing back to factory still nothing. first when booting from twrp it would say no OS. i finally got that to go away but now it just keeps booting into android power loop. tried erasing all data nothing helps. it also tells me software is corrupted. can someone help plzzz
Click to expand...
Click to collapse
go into fastboot mode and do.... fastboot -w
Tech_Savvy said:
go into fastboot mode and do.... fastboot -w
Click to expand...
Click to collapse
I did that and it didn’t work
dumberthandumb said:
I did that and it didn’t work
Click to expand...
Click to collapse
Make sure you have unlocked the bootloader AND unlocked critical partitions, then flash the latest factory image found on essentials support page. DO NOT flash TWRP or anything like that.
Nick80835 said:
Make sure you have unlocked the bootloader AND unlocked critical partitions, then flash the latest factory image found on essentials support page. DO NOT flash TWRP or anything like that.
Click to expand...
Click to collapse
How do I unlock critical partitions? Also I have already flashed TWRP. If I try to push the factory image without TWRP it tells me not enough space.
I suspect you need to change the slot that's loading... I had a similar thing recently. .. Try going into fastboot and typing "fastboot --set-active=slot" where slot is "a" or "b", depending on where you flashed TWRP (you need to load the opposite slot).
If that doesn't work, flash the original boot file in fastboot and keep everything crossed...!
nstirton said:
I suspect you need to change the slot that's loading... I had a similar thing recently. .. Try going into fastboot and typing "fastboot --set-active=slot" where slot is "a" or "b", depending on where you flashed TWRP (you need to load the opposite slot).
If that doesn't work, flash the original boot file in fastboot and keep everything crossed...!
Click to expand...
Click to collapse
My slot b has been fleshed with TWRP and a with the original os. I still can’t get it to boot. Is there anyways that I can just flash everything back to factory setting? I don’t care about personal data. I even tried flashing both slots with the os and still no luck
flash OTA via adb sideload , it will fix your issue
Just do the fastboot flashall from the Essential download page and start over. I flashed the october update the other day and my phone has been running so much better since then.
galakanokis said:
Just do the fastboot flashall from the Essential download page and start over. I flashed the october update the other day and my phone has been running so much better since then.
Click to expand...
Click to collapse
Flash all? How do I get to that? I have tried doing a side load through TWRP but nothing helped
dumberthandumb said:
Flash all? How do I get to that? I have tried doing a side load through TWRP but nothing helped
Click to expand...
Click to collapse
Instructions are on the Essential website where you can grab the downloads. Basically download the fastboot image, unzip it and run the flashall script inside the unzip. Easier if your fastboot path is setup properly. It will flash stock to both slots and away you go.
You NEED to unlock critical partitions to flash all of them.
galakanokis said:
Instructions are on the Essential website where you can grab the downloads. Basically download the fastboot image, unzip it and run the flashall script inside the unzip. Easier if your fastboot path is setup properly. It will flash stock to both slots and away you go.
Click to expand...
Click to collapse
Flash all? How do I do this?
dumberthandumb said:
Flash all? How do I do this?
Click to expand...
Click to collapse
https://www.essential.com/developer/current-builds
galakanokis said:
Instructions are on the Essential website where you can grab the downloads. Basically download the fastboot image, unzip it and run the flashall script inside the unzip. Easier if your fastboot path is setup properly. It will flash stock to both slots and away you go.
Click to expand...
Click to collapse
I tried doing that it flashes and everything but it till wont boot up, its still stuck on the essential logo.
when i try to go into recovery mode it says no command
dumberthandumb said:
I tried doing that it flashes and everything but it till wont boot up, its still stuck on the essential logo.
when i try to go into recovery mode it says no command
Click to expand...
Click to collapse
You can see it flash both slots and all the images? Should be able to get a screen grab of it.
If your environment is setup correctly and you say it flashes I can't be of much help unfortunately.
dumberthandumb said:
I tried doing that it flashes and everything but it till wont boot up, its still stuck on the essential logo.
when i try to go into recovery mode it says no command
Click to expand...
Click to collapse
Seems you don't know how to boot into recovery,when you see this Android guy you need to press volume up and power.
Hi, can someone help me with this problem?
{
"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"
}
galakanokis said:
You can see it flash both slots and all the images? Should be able to get a screen grab of it.
If your environment is setup correctly and you say it flashes I can't be of much help unfortunately.
Click to expand...
Click to collapse
Thank you I finally got it to work, Apparently only my boot loader was unlocked and I did not have critical partitions unlocked, ones I unlocked critical partitions the flash I was able to go through
Thank you everyone for your help
nibera said:
Hi, can someone help me with this problem?
View attachment 4612857
Click to expand...
Click to collapse
Do you have creitical partitions unlocked ?
Hi,
I've installed an ota update and the device didn't boot... it is stuck in a bootloop....
When i try to flash via fastboot, it appears an error saying that the device is locked ant cennot erase...
via fastboot oem unlock i get the error message: Remote: oem unlock is not allowed
via MiUnlocker the unlock gets to de 50% and gives an error and on its logs it says: Remote: oem unlock is not allowed
I tryed to flash TWRP with command fastboot flash recovery but the error is the same: remote: partition flashing is not allowed
Can anyone help me please??
I'm stuck on the bootloop i can't go to setting - developer - allow oem unlock option!!
Have you tried doing a Factory Reset from stock recovery?
This is a strange behavior, even if an OTA update corrupted the system for some reason, the phone should boot from the original slot.
Have you tried switching slots manually from fastboot ?
Parnas72 said:
This is a strange behavior, even if an OTA update corrupted the system for some reason, the phone should boot from the original slot.
Have you tried switching slots manually from fastboot ?
Click to expand...
Click to collapse
How can i do that?
Hello!
I've faced the exact same problem yesterday.
You need to force the phone to boot in EDL mode by opening the back cover and short circuit 2 pins as shown in THIS video.
After you have the phone in EDL and being detected by your PC (you need the correct drivers, you may get them on THIS thread by @CosmicDan), you may use MiFlash Tool to flash official PIE Rom, access developer options and enable oem unlock to be able to unlock your phone again.
If you wish to revert to Oreo, please use THIS guide.
Cheers!
Tepig said:
Have you tried doing a Factory Reset from stock recovery?
Click to expand...
Click to collapse
No recovery.. i get this:
{
"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"
}
Typhus_ said:
Hello!
I've faced the exact same problem yesterday.
You need to force the phone to boot in EDL mode by opening the back cover and short circuit 2 pins as shown in THIS video.
After you have the phone in EDL and being detected by your PC (you need the correct drivers, you may get them on THIS thread by @CosmicDan), you may use MiFlash Tool to flash official PIE Rom, access developer options and enable oem unlock to be able to unlock your phone again.
If you wish to revert to Oreo, please use THIS guide.
Cheers!
Click to expand...
Click to collapse
Obrigado!
I'll try it now!!
xistolas said:
No recovery.. i get this:
Click to expand...
Click to collapse
Actually you have a recovery. You need to long press the power button and, afterwards (not at the same time), press the volume + button. You'll see that all options will appear.
xistolas said:
How can i do that?
Click to expand...
Click to collapse
fastboot getvar current-slot
to show the current slot,
fastboot --set_active=a or fastboot --set_active=b
to change it.
xistolas said:
Obrigado!
I'll try it now!!
Click to expand...
Click to collapse
get into fastboot mode
hot boot twrp using fastboot command
copy efs backup to twrp backup folder and restore
then go into bootloader mode
flash the firmware using miflash
---------- Post added at 09:27 PM ---------- Previous post was at 09:23 PM ----------
akashavel said:
get into fastboot mode
hot boot twrp using fastboot command
copy efs backup to twrp backup folder and restore
then go into bootloader mode
flash the firmware using miflash
Click to expand...
Click to collapse
follow from step 6 to end in below link
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624