Okay guys, I'm in full panic mode. I was just getting ready to reinstall my X with Lineage OS. I had CM 13.0 up until now. I've backuped everything, then powered off my phone (simple, normal power down).
After that I was trying to get into TWRP (I had 2.x.x.x installed), but VolDown+Power got me in a boot loop. The OnePlus Logo flashes, phone vibrates short then reset and it flashes/vibrates again. I tried booting normally, that doesn't work either.
The only thing I can do is get into fastboot, but I can't flash anything! The phone says it's locked (though I unlocked it before I put CM 13.0 on it)
Code:
c:\Android>fastboot flash recovery twrp-3.1.1-1-onyx.img
target reported max download size of 536870912 bytes
sending 'recovery' (16002 KB)...
OKAY [ 0.505s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.509s
c:\Android>fastboot oem unlock
...
FAILED (remote: oem unlock is disabled)
finished. total time: 0.005s
c:\Android>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.010s]
finished. total time: 0.011s
Help! I can't boot my phone and I can't flash anything either. Is there anything I can do or missed?
After 2 hours of trying everything I found I'm now at a point where I could install the original (?) recovery via the MSM DownloadTool 2.0.2. Now I have a recovery which looks like stock... I can "Install from local" and "Install from USB". Tried the latter and I get the "adb sideload" mode. Tried to upload the latest Lineage OS Nightly through this sideload, but it fails after 47%.
If possible Flashing oos 3 might help or there's unbricking guide for opx you might want to see
intoxicated.mad said:
If possible Flashing oos 3 might help or there's unbricking guide for opx you might want to see
Click to expand...
Click to collapse
Thanks! That was actually the solution: the stock recovery can only flash OOS, it seems. I flashed OOS 3.1.4, then enabled oem unlock, flashed TWRP and Lineage.
Still no idea why my phone wouldn't boot after powering it off or why my bootloader was locked in the first place.
Anyway you got out of trouble ??
I have the exact same problem, only I am running Sultan's ROM. Unfortunately, my phone is not backed up, because I wasn't going to install a new rom or anything. Is there any way to restore my phone without losing data. I downloaded the MsmDownloadTool V2.0, and am wondering if I could replace the stock recovery.img in there with the one for my ROM, or would this not work?
Ok, so I tried replacing the recovery.img, and it didn't work, so I used the original one from the tool and dirty flashed OOS 3.1.4. All my original files and apps are still there, but none of them will open, except for google apps, which I assume came in the OOS ROM (Google Play works but says 'download pending' if I try to download an app). Unfortunately, this mix of software doesn't let me enable developer options in the settings (when I tap the build number nothing happens) so I can't use ADB to make a backup. I think the only way to get things working is to do a clean install OxygenOS, which would lose all my files. I'll think I'll try to use a file manager to copy the contents of the internal storage to a USB device, then do a full clean install.
Also, in this weird state of software, only the back button works, the home and recent apps keys don't, so if I do something in Chrome, I need to restart the phone to do something else
drunken_m said:
Thanks! That was actually the solution: the stock recovery can only flash OOS, it seems. I flashed OOS 3.1.4, then enabled oem unlock, flashed TWRP and Lineage.
Still no idea why my phone wouldn't boot after powering it off or why my bootloader was locked in the first place.
Click to expand...
Click to collapse
I also faced that issue too and it happens when you have installed custom rom or recovery without first unlocking the bootloader. Do It Now If you haven't
Actually the bootloader was already unlocked (I needed that to install CM in the first place), but I think I accidentally re-locked it when I tried to remove root (to install a banking app).
As I wrote I already fixed the issue by installing the original bootloader/recovery and OOS over a serial link, then unlocked the bootloader again and installed the latest TWRP And Lineage. So all is fine now.
adamantiumXT said:
Ok, so I tried replacing the recovery.img, and it didn't work, so I used the original one from the tool and dirty flashed OOS 3.1.4. All my original files and apps are still there, but none of them will open, except for google apps, which I assume came in the OOS ROM (Google Play works but says 'download pending' if I try to download an app). Unfortunately, this mix of software doesn't let me enable developer options in the settings (when I tap the build number nothing happens) so I can't use ADB to make a backup. I think the only way to get things working is to do a clean install OxygenOS, which would lose all my files. I'll think I'll try to use a file manager to copy the contents of the internal storage to a USB device, then do a full clean install.
Also, in this weird state of software, only the back button works, the home and recent apps keys don't, so if I do something in Chrome, I need to restart the phone to do something else
Click to expand...
Click to collapse
Rule #1 of flashing: always have a backup ready.
If you have TWRP installed and can get into recovery you can pull your files via ADB. After that I'd also recommend a clean install (full wipe).
drunken_m said:
Rule #1 of flashing: always have a backup ready.
If you have TWRP installed and can get into recovery you can pull your files via ADB. After that I'd also recommend a clean install (full wipe).
Click to expand...
Click to collapse
I have to agree, but I wasn't flashing when the phone decided to brick itself , so I didn't have a recent backup. In the bricked state I could only access fastboot mode, not recovery . I ended up copying what I could from the internal storage partition (which basically had everything I needed anyway), then clean installing a new ROM, and restoring my files.
For anyone else who gets into the same situation, I recommend that you make sure to not turn on WiFi or mobile data after you dirty flash OxygenOS, and remove your Google account. This will mean that Google's backup of your phone and apps (if you turned that feature on) will be of your working setup. As I tried to use Google Play in the messed up system, Google decided to replace my backup with the bad config so I couldn't restore in the new ROM - although looking at the Google Drive app now, the good setup is backed up, only I have no way to restore it
Maybe I have the same problem, not sure. I can't boot the phone. Holding vol down + power only makes the phone reboot over and over until I let go. It turns off afterwards, never enters recovery mode. I can access fastboot mode, but my bootloader is locked so I can't flash anything. Any suggestions?
Related
First of, I'm running Cyanogenmod 12.1 on my Z2.
On the install it vanished my TWRP Recovery, so I decided to reflash it using their app - this was unsucessfull. I thought I would flash it the next day using adb, so I didn't mind.
However in the next hours I needed to reboot the phone - resulting in the Sony logo and nothing more. So I bootet into the CM recovery and tried to reflash the CyanDelta zip - this failed and resulted in "footer is wrong - signature verification failed - Installation aborted". The next thing I tried was flashing a zip by adb recovery sideload - this failed as well and resulted in "protocol fault (no status)".
This was when I tried to boot into the bootloader using the recovery menu entry. The screen got black, the LED lighted up blue and nothing happened forever. The same thing occours when I try to boot into the bootloader by hardware keys (hold VolUp and insert MicroUSB cable).
So, in short:
I can't boot android
I can't install zips by CM recovery
I can't boot into the bootloader [EDIT: I can.]
I can't install nandroid backups since the CM recovery doesn't offer that
Any idea?
If the phone's LED lights up blue it means that you are in fastboot mode (AKA the bootloader) . It is normal for the screen to be black. I suggest that you download a stock FTF and flash it using the windows flashtool application. Your phone is fine. Good luck.
the_crevis said:
If the phone's LED lights up blue it means that you are in fastboot mode (AKA the bootloader) . It is normal for the screen to be black. I suggest that you download a stock FTF and flash it using the windows flashtool application. Your phone is fine. Good luck.
Click to expand...
Click to collapse
Ah, I feel dumb now. I might be damaged from the informational Nexus bootloader.
So, I tried to flash a new recovery - fastboot flash twrp-2.8.6.0-sirius.img - which succeded, but it still boots the CM Recovery. Buh.
Seems like something is overriding the recovery on boot. So lets erase everything:
Code:
fastboot erase system
fastboot erase userdata
fastboot erase recovery
fastboot flash twrp-2.8.6.0-sirius.img
Aaaand - still CM Recovery.
I also tried to flash a stock image as you suggested, however:
Code:
fastboot flash system system.sin
sending 'system' (1800183 KB)...
FAILED (remote: data too large)
finished. total time: 0.002s
No worries, I came from a nexus 4 and it confused me as well at first. Try exacting http://forum.xda-developers.com/xperia-z2/development/kernel-m5-kernel-t2858912 and flashing the boot image via fastboot. That should give you a working recovery.
As I said, flashing a recovery by fastboot results in the CM Recovery.
I just tried to wipe my device using the CM Recovery, it told me it was unable to mount /data - my guess? The filesystem is ****ed up.
EDIT: I got it. Seems like TWRP needs some custom stuff to work (which is provided by CM). Flashing philz worked fine and allowed me to sideload a proper ROM. Everything fine now
EDIT: ALSO, use usb 2.0 ports to flash stuff, usb 3.0 is not working 100 percent yet.
EDIT, 14 Mar 2016: Kingroot got me to root and now I have twrp installed, http://www.kingroot.net/ .
I have a Sprint prepaid Moto E 2015 LTE, XT1526. I did the motorola bootloader unlock, that went fine.
The phone works and is activated on RingPlus, when it boots, I get the Red Warning, Bootloader unlocked, when normally booting.
When I try to flash a recovery to the phone (all that I could find here on XDA), I get this response:
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>fastboot devices
TA0XXXXXXX fastboot (edited to take out SN)
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (12916 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.015s
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>adb kill-server
I've tried everything, and am providing as much info as I can, in case anyone seeing something that is 'new' or 'different' about my phone.
Double check and be sure you're attempting to flash the TWRP for the Moto E 2015 LTE "Surnia", not "Otus" (which is the Moto E 2015 3G). iirc, I used Squid's TWRP from here: http://forum.xda-developers.com/moto-e-2015/development/twrp-squid-twrp-recovery-moto-e-lte-t3137649 . If 3.0.0 doesn't work, try 2.8.7.
You should also try changing USB ports. I ran into a similar issue where I wasn't able to flash things when I plug into my most often used USB port. I suspect that the contacts got worn from how often I used it, so I tried another USB port and it worked fine.
I have done same procedure as yours and meet same problem yesterday.
I flashed twrp recovery with following command,
fastboot boot recovery.img
instead of
fastboot flash recovery recovery.img
here are the post which I followed.
http://www.xda-developers.com/how-to-root-the-moto-e-2015-and-unlock-the-bootloader-xda-tv/
http://forum.xda-developers.com/moto-e-2015/orig-development/twrp-moto-e-2015-recovery-t3049726
faheyd said:
When I try to flash a recovery to the phone (all that I could find here on XDA), I get this response:
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>fastboot devices
TA0XXXXXXX fastboot (edited to take out SN)
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (12916 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.015s
Click to expand...
Click to collapse
Thanks, but not working:
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>fastboot boot recovery.img
downloading 'boot.img'...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.009s
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>
You can get rid of the warning by method in post 2 of this link
http://forum.xda-developers.com/moto-e-2015/general/guide-unlock-bootloader-moto-e-2015-t3045748
Q1:How to remove the unlocked bootloader message?
Then, flash the twrp recovery again. Make sure you have right recovery.img. here is the one I used.
http://forum.xda-developers.com/devdb/project/?id=8591#downloads
llaalways said:
You can get rid of the warning by method in post 2 of this link
http://forum.xda-developers.com/moto-e-2015/general/guide-unlock-bootloader-moto-e-2015-t3045748
Q1:How to remove the unlocked bootloader message?
Then, flash the twrp recovery again. Make sure you have right recovery.img. here is the one I used.
http://forum.xda-developers.com/devdb/project/?id=8591#downloads
Click to expand...
Click to collapse
I know that, does not help. I've tried that recovery, one from cyanogenmod also, the recovery img is not the problem. Thanks anyway.
go to phone options and turn on USB debugging and when you go to flash it..
- turn off phone.
- hold volume down and power to get to boot loader screen..
Leave it there and connect to PC.
It should be showing you the bootloader screen.. you know what that is right ?
Then open "Minimal ADB and Fastboot" install folder..
Right click empty folder space while holding shift key down..
Select open cmd window here..
type in either,
fastboot devices
or
mfastboot devices
and make sure it says your device is listed
then paste into cmd window..
mfastboot flash recovery recovery.img
make sure your new recovery file has that name and is copied to that fastboot folder.
that should be it..
xpmule said:
go to phone options and turn on USB debugging and when you go to flash it..
- turn off phone.
- hold volume down and power to get to boot loader screen..
Leave it there and connect to PC.
It should be showing you the bootloader screen.. you know what that is right ?
Then open "Minimal ADB and Fastboot" install folder..
Right click empty folder space while holding shift key down..
Select open cmd window here..
type in either,
fastboot devices
or
mfastboot devices
and make sure it says your device is listed
then paste into cmd window..
mfastboot flash recovery recovery.img
make sure your new recovery file has that name and is copied to that fastboot folder.
that should be it..
Click to expand...
Click to collapse
As stated in my OP, I've done all that, but I'll do it again, please look at my pics and post, you'll see I've done all that already:
S:\Phones\Moto_E-2015-2ndGen-XT1526\mfastboot-v2>mfastboot devices
TA00000000 fastboot (edited to change serial number)
S:\Phones\Moto_E-2015-2ndGen-XT1526\mfastboot-v2>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (12916 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.007s
S:\Phones\Moto_E-2015-2ndGen-XT1526\mfastboot-v2>
Can a DEV please help ? If I need to go back to stock I'll be glad to do it and then unlock the bootloader again, however, I've posted in two diff forums trying to get someone to tell me the correct SPRINT img to bring back to stock, no answers.
XT1526_SURNIA_USC_5.0.2_LXI22.50-29.1_cid9_subsidy-DEFAULT_CFC.xml
XT1526_SURNIA_REPW_5.0.2_LXI22.50-56-1.1_cid6_subsidy-REPUB_CFC.xml
XT1526_SURNIA_BOOST_5.0.2_LXI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml
I think it's the boost, but it doesn't have the SPRINT label on it, like my phone.
You just said,
"Can a DEV please help ? If I need to go back to stock I'll be glad to do it and then unlock the bootloader again"
So why would you say that ?
Did you relock your bootloader ?
Maybe that is why you are having a problem ?
I never have relocked mine eh..
And i have had no problem flashing TWRP from Squid.. all his various updates overwriting the old one.
I have flashed a bunch of stock retail recoveries too and all of those worked fine too.
I am curious did you try and load recovery after to see if it actually changed or not ?
EDIT:
Can i ask you exactly what Custom Recovery you are trying to install ?
And did you verify the MD5 hash ?
I always do *if it's available..
xpmule said:
You just said,
"Can a DEV please help ? If I need to go back to stock I'll be glad to do it and then unlock the bootloader again"
So why would you say that ? On other models of phones it has solved a problem of this nature.
Did you relock your bootloader ? Of course not, if you had read the post, you would see that.
Maybe that is why you are having a problem ? No
I never have relocked mine eh.. Good for you, that doesn't help me.
And i have had no problem flashing TWRP from Squid.. all his various updates overwriting the old one.
I have flashed a bunch of stock retail recoveries too and all of those worked fine too. Good for you, that doesn't help me.
I am curious did you try and load recovery after to see if it actually changed or not ? I did, I get an icon with something that says no cmd,
EDIT:
Can i ask you exactly what Custom Recovery you are trying to install ? Surnia and CM's recovery, no difference.
And did you verify the MD5 hash ? Yes.
I always do *if it's available..
Click to expand...
Click to collapse
I've done all those things and tried to post as much info in my OP. Is there a Dev that can help me?
I've now tried to go back to stock in an effort to unlock this biatch using XT1526_SURNIA_BOOST_5.0.2_LXI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml, and it wont let me do that either. It's not letting me write to the GPT partition. This leads me to believe my phone is NOT unlocked, even though the bootloader shows UNLOCKED BOOTLOADER. Anyone know an answer?
I noticed something a while back when I attempted to flash recovery on a different phone (nexus 6) but failed. I tried a bunch of stuff to no avail. The solution was to simply get a new set of platform tools because mine was too old. Doesn't hurt to try.
Snorbro said:
I noticed something a while back when I attempted to flash recovery on a different phone (nexus 6) but failed. I tried a bunch of stuff to no avail. The solution was to simply get a new set of platform tools because mine was too old. Doesn't hurt to try.
Click to expand...
Click to collapse
Thank you for trying. I just found a post, (and now I can't find it), but the guy went through what I did, and then he used KingRoot, http://www.kingroot.net/ , and it worked.
So, I tried it too, and magic, it worked. I now have root and TWRP installed.
I could have sworn I tried KingRoot, but it must have been on another phone I had.
Are you sure your recovery file is called recovery.img and not twrp.xxx.img? If not you need to rename it
Another problem I had, I was using a USB 3.0 port on my computer. This is a not the way. Using a USB 2.0 port works on flashing stuff.
Hi faheyd, I also have XT1526 on android 5.0.2, but kingroot fails. I was told not to update OS to keep it working in India.
Doess ur phone run on 5.1?
Does USB debugging needs to be activated?
drshreenivaas said:
Hi faheyd, I also have XT1526 on android 5.0.2, but kingroot fails. I was told not to update OS to keep it working in India.
Doess ur phone run on 5.1?
Does USB debugging needs to be activated?
Click to expand...
Click to collapse
I have no idea, hopefully someone that knows will step in and help.
I upgraded my OnePlus X today with the community build OxygenOS 3.1.0 using TWRP. There was an error saying that my device was not "OnePlus" but "ONE". So I edited the updater-script and replaced the word "OnePlus" by "ONE" in getprop line and successfully installed the ROM.
Then I connected my phone to PC, enabled OEM unlock and USB debugging, booted into fastboot and typed -
Code:
fastboot oem unlock
It said Okay, done...but there was not action on the phone screen. It stayed in Fastboot mode. I rebooted the phone and it was the same as before. I thought it was okay and continued with the process by booting into fastboot again and flashing TWRP with the command -
Code:
fastboot flash recovery twrp-3.0.2-0-onyx.img
It was successful. Then something weird happened when I typed -
Code:
fastboot boot twrp-3.0.2-0-onyx.img
The output was downloading image, okay. Then booting and the error FAILED(remote: dtb not found).
I tried manually entering the recovery mode, first by volume down + power button and then by advanced reboot menu -> recovery. All that happens is that it stays stuck in Oneplus Logo screen with powered by android written at bottom. I am able to boot into the OS.
I am sure that the image file is not corrupted as I have used the same before a couple of times. Still I tried flashing Stock recovery and a few other image files of the same version of TWRP. The same error comes up every time. Flashing is successful but booting is not. What should I do?
flash this recovery https://dl.dropboxusercontent.com/u/10404978/t/opx_oos3_recovery.img. If it didn't help, try this http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Is my recovery or bootloader corrupt?
I tried this code -
Code:
fastboot oem device-info
Output was -
...
(bootloader) Device tampered : false
(bootloader) Device unlocked : true
(bootloader) Charger screen enabled : false
(bootloader) Display panel :
(bootloader) console_enabled : 0
(bootloader) exec_console_unconsole : 0
OKAY [0.017s]
finished. total time : 0.018s
The problem is when I type -
Code:
fastboot oem unlock
Nothing pops up on my phone.
Maybe the reason is that I had a rooted version of OxygenOS 2.2.2 with TWRP but when I flashed the community build of OxygenOS 3.1.0 somehow TWRP was missing...
What should I do now? I am back at 2.2.2 now as the beta build didn't suit me. This error still persists. The first link above was stock recovery which did work. But I need TWRP back...
....................
Sorry to bother. Issue solved. It was already unlocked and this time flashing and booting in the image worked idk why...
arunmohan16 said:
flash this recovery https://dl.dropboxusercontent.com/u/10404978/t/opx_oos3_recovery.img. If it didn't help, try this http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Click to expand...
Click to collapse
Thank you dude, i have been looking for this all day
I got exactly the same problem, i tested lot of recovery without any luck.
I installed the one from the dropbox, now i got the stock recovery, but, i can do anything, from SDCard or Sideload, the installation of CM13 or Oxygen 3 failed.
Any suggestions ? 4h i tested everything i got in mind to try to fix it.
Thanks
tirlibibi said:
I got exactly the same problem, i tested lot of recovery without any luck.
I installed the one from the dropbox, now i got the stock recovery, but, i can do anything, from SDCard or Sideload, the installation of CM13 or Oxygen 3 failed.
Any suggestions ? 4h i tested everything i got in mind to try to fix it.
Thanks
Click to expand...
Click to collapse
This guide will help you. http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 Use this mini tool, http://forum.xda-developers.com/showpost.php?p=64344611&postcount=4
EDIT:
In my way of trying to apply to warranty and flashing the stock package into the phone and Windows being Windows, I had problems using the batch script, it stopped for long time and didn't do nothing forcing me to restart the phone and restart the batch, until I uninstalled the driver and make Windows reinstall it automatically (manage devices) and it finally flashed it all, actually I flashed the package three times just to be sure lol. So, in the end I wanted to turn off the friggin phone because I was very done with it (what a PITA it has been) and wanted to apply for my warranty so as there is no command in fastboot to shutdown the phone I didn't know how to shut it down so I tried pressing Power button and releasing it the moment the screen goes off but I think I didn't do it right or the phone can't be shutdown that way (this is most probably the answer), well the phone rebooted and by the grace of Zeus it booted for the first time into MIUI and now is waiting for me to configure the phone, none of the times I flashed this packaged into the phone it booted into MIUI, never, and just when I want to turn the phone this thing boots, I don't know if I'm going to venture into flashing anything again being the phone how it is but goddamnit it was a real PITA, I had to use my old Redmi Note 3.
So, tl;dr: Flashed stock package, phone booted finally, all is OK for now.
====================================================================================================
====================================================================================================
Sooo, I was having problems with flashing stuff on this phone but I solved them and I was able to flash HavocOS, it was OK and I could use my phone kinda well (some reboots but nothing serious, or so I thought). So, until 12 hours ago my phone was having problems with the File Manager (I used FX app and also the stock one), it hanged and didn't respond and made the phone reboot itself a couple times, that was weird, actually the whole time I used this ROM I was having problems with my files, it used to took long time to read some files and I was thinking that maybe my SD was bad but apparently it's not. So, after the second reboot I was able to finally open the file manager but navigating through the SDCard was buggy and the app didn't show me any file (it show me an empty list) so I rebooted my phone manually (this time wasn't done by the phone itself) and now is when the phone never passed from the Havoc logo, I waited something close to 30 min and nothing, rebooted and waited 10 min and nothing, it still hanged on the logo, went into recovery to wipe everything and re-flash all and after doing all that and tried to boot to system my phone was booting to recovery and didn't past that, tried installing stock (flash_all script) and then installing recovery and everything again and nothing, it booted to recovery always. So there is when I realized I couldn't change anything in the slot A (at least to what boot refers), I can't install TWRP nor OrangeFox, I can do it in slot B, and even if I boot into recovery on slot B I can flash the zip installer, change the slot and try to boot to recovery from slot A but it boots to the bootloader, and yes, TWRP didn't output any error when flashing the installer.
Yes, the script flashes everything OK, well not everything, system and vendor partitions (A and B) I had to flash them manually because it gave me some errors with the script (reading errors, and yes I compared checksums so it was super weird) but in the end supposedly the stock ROM must have been installed, which I couldn't try because even after flashing everything on the script the phone was booting to bootloader, I didn't give importance to this because before I was able to flash and boot HavocOS I did the same thing because my phone was bootlooping into fastboot: I ran the script, flashed manually those images because it gave me the same errors, tried to boot to system and the phone booted to bootloader, didn't give a sheat, flashed OrangeFox recovery, ROM, recovery installer, GApps, nofde patch and then I was able to boot to HavocOS. But now this time I tried to install TWRP with fastboot command but it didn't worked, fastboot doesn't throw any errors while flashing, it reported:
Sending 'boot_a' (39780 KB) OKAY [ 1.042s]
Writing 'boot_a' OKAY [ 0.208s]
Finished. Total time: 1.263s
But if I try to boot into recovery it sends me to fastboot/bootloader, if I do this in the slot B I can successfully boot into recovery and, as I said, if I flash the installer, change the slot and reboot to recovery, my phone reboots to fastboot.
This has happened to someone else?
Does anybody knows of any solution?
I still have warranty (phone has less than 3 months) so I probably can flash the stock package and lock my bootloader so I can get my phone checked as probably it is a hardware failure, probably and hopefully .
Oh, and also I have to add that the recovery was also lagging sometimes (OrangeFox). Sometimes when I was looking into files on the SD, also when I pressed the "reboot system" button it hanged for half a minute and the it proceeded to reboot, and also once when I was flashing the nofde patch the phone also hanged and rebooted into recovery by itself. So this indicates that maybe is a hardware thing right? Because there is no way that the recovery could have gotten corrupted or something just out of the blue.
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
RthurPendragon said:
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
Click to expand...
Click to collapse
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Jhon_Locke said:
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Click to expand...
Click to collapse
In my case, I wiped system and installed Evolution X ROM (OSS version) with Custom Recovery (SHRP) Then when I want to reboot into recovery again to flash Magisk, There's no recovery... It always opens with fastboot mode. I tried flashing recovery.zip from slot b. Still no result.
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Iamdchandan said:
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Click to expand...
Click to collapse
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Iamdchandan said:
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Click to expand...
Click to collapse
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
garylawwd said:
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
Click to expand...
Click to collapse
First if all reboot into fastboot mode then connect with pc then type command " fastboot flashing unlock" enter now again forcefully reboot into fastboot mode then type next command "fastboot flashing_critical unlock" now bootloader unlock.
Again reboot into fastboot mode then type command "fastboot getvar current-slot"
Now change current active slot and then type command " fastboot erase boot" . Now finally flashed twrp latest (3.4) for Android 10 with command "fastboot flash boot twrp.img" now it flash successfully then type command "fastboot reboot" and then press volume up then hit enter and it return in fastboot mode then i have again change slot and repeat all process with that slot but it again stuck in fastboot mode. After all i have changed twrp version but again same thing repeat so I flashed stock Android 10 through Mi flash and lock bootloader.
That's all whole process.
If do something wrong please help me to figure out.
Waiting for your reply ?.
Love
try sharp recovery
Sami Devo said:
try sharp recovery
Click to expand...
Click to collapse
I don't know installation process of sharp recovery.
Iamdchandan said:
I don't know installation process of sharp recovery.
Click to expand...
Click to collapse
install on the other slot... dont flash it on running rom slot... if rom running A.. chng it to B. then flash to B.. then goto recovery flash the sharp zip when sharp opens..then again chng slot to A.. running rom slot..
okk ur phn boots.
Hi all,
The story is that I had Linage flashed, but it said it was time to update the firmware, so I tried to do that.
I booted in twrp and flashed the most recent firmware. I had plenty of power on the battery. But after it finished it booted into a classic miui interface. From here it only got worse. It asked for my password which I entered several times, but it was incorrect.
What I tried was to clear the storage. But I get the same error when it boots - it boots into miui, then shortly after a google load screen and then it reboots.
I tried downloading the mi flash tool. But when I connect the phone and locate the file, the screen has just one line in the corner saying something like "press any key to reboot".
With the adb command it doesn't seem like there is actually made a connection.
I do not really care which OS you suggest I install, as long as it at least can get it up and running again.
------------------
I just got it into fastboot and it goes fine with fastboot devices where I can see that it is connected, but when I enter fastboot flash recovery twrp.img then the phone reboots with an error code in the cmd window saying:
"FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed"
Any suggestions to what I can do? Can it be the twrp image that is causing the issue?
twrp-3.3.0-0-beryllium.img 30.3mb
kitkat87 said:
Hi all,
The story is that I had Linage flashed, but it said it was time to update the firmware, so I tried to do that.
I booted in twrp and flashed the most recent firmware. I had plenty of power on the battery. But after it finished it booted into a classic miui interface. From here it only got worse. It asked for my password which I entered several times, but it was incorrect.
What I tried was to clear the storage. But I get the same error when it boots - it boots into miui, then shortly after a google load screen and then it reboots.
I tried downloading the mi flash tool. But when I connect the phone and locate the file, the screen has just one line in the corner saying something like "press any key to reboot".
With the adb command it doesn't seem like there is actually made a connection.
Any suggestions to what I can do?
I do not really care wchich OS you suggest I install, as long as it at least can get it up and running again.
Click to expand...
Click to collapse
This will work with any Android 10 custom ROM
If you want to stay unencrypted, you have to use dfe (disable force encryption). I have never used it, but if you want it try to get one without magisk.
1. 11.0.6 is the latest firmware. You can download it from here:https://xiaomifirmwareupdater.com/firmware/beryllium/
2. You have to format your internal storage.
3. Steps: go to recovery (press back when it asks for password)->wipe->format data (it will ask you to type "yes")-> wipe system, data, internal storage,cache, davlik cache
Copy firmware,rom, gapps, dfe into your internal storage, flash firmware (most ROMs include vendor but flash full firmware just to be sure), ROM, gapps, dfe and reboot.
sotosgolf said:
This will work with any Android 10 custom ROM
If you want to stay unencrypted, you have to use dfe (disable force encryption). I have never used it, but if you want it try to get one without magisk.
1. 11.0.6 is the latest firmware. You can download it from here:https://xiaomifirmwareupdater.com/firmware/beryllium/
2. You have to format your internal storage.
3. Steps: go to recovery (press back when it asks for password)->wipe->format data (it will ask you to type "yes")-> wipe system, data, internal storage,cache, davlik cache
Copy firmware,rom, gapps, dfe into your internal storage, flash firmware (most ROMs include vendor but flash full firmware just to be sure), ROM, gapps, dfe and reboot.
Click to expand...
Click to collapse
is it fastboot flash file link which you have provided above?
hondraopranav said:
is it fastboot flash file link which you have provided above?
Click to expand...
Click to collapse
Twrp!
You flash firmware as a normal zip.
I understand that twrp works for you.
If it doesn't, flash twrp through fastboot and then proceed as i mention above
Thanks for your replies.
The problem I have is that fastboot does not really seem to work.
When I try to do a fastboot command I get the error that goes:
"Sending 'recovery' (31068 KB) FAILED (Write todevice failed (Unknown error))
fastboot:error: Command failed"
Also, I just tried the Mi unlock tool and it seems that it cannot create a connection with the usb cable - so could that be the reason that I cannot flash it?
kitkat87 said:
Thanks for your replies.
The problem I have is that fastboot does not really seem to work.
When I try to do a fastboot command I get the error that goes:
"Sending 'recovery' (31068 KB) FAILED (Write todevice failed (Unknown error))
fastboot:error: Command failed"
Also, I just tried the Mi unlock tool and it seems that it cannot create a connection with the usb cable - so could that be the reason that I cannot flash it?
Click to expand...
Click to collapse
Download twrp for poco f1 from the official twrp site.
When everything is ready and you have pressed flash, THEN boot into fastboot and connect the cable
Edit: you also might have relocked your bootloader. If what I mention above doesn't work, unlock your bootloader again with the unlock file Xiaomi originally sent you.
sotosgolf said:
Download twrp for poco f1 from the official twrp site.
When everything is ready and you have pressed flash, THEN boot into fastboot and connect the cable
Edit: you also might have relocked your bootloader. If what I mention above doesn't work, unlock your bootloader again with the unlock file Xiaomi originally sent you.
Click to expand...
Click to collapse
The phone doesn't boot into a system, and currently as I load fastboot whenever the connection to the computer is made it goes to a screen saying 'press any key to turn off'.
I did notice, though, that after I from recovery wipe all data, then in the first boot it encrypts the phone. But it never manages to get the OS up and running.
------
Just downloaded the latest twrp from the official site. And when I tried to flash it I got the same error
"Sending 'recovery' (31068 KB) FAILED (Write todevice failed (Unknown error))
fastboot:error: Command failed"
kitkat87 said:
I did notice, though, that after I from recovery wipe all data, then in the first boot it encrypts the phone. But it never manages to get the OS up and running.
Click to expand...
Click to collapse
Let's get this straight m8,
Can you boot into recovery ("up"+"power")?
Yes or No?
Thanks for your replies.
sotosgolf said:
This will work with any Android 10 custom ROM
If you want to stay unencrypted, you have to use dfe (disable force encryption). I have never used it, but if you want it try to get one without magisk.
1. 11.0.6 is the latest firmware. You can download it from here:
2. You have to format your internal storage.
3. Steps: go to recovery (press back when it asks for password)->wipe->format data (it will ask you to type "yes")-> wipe system, data, internal storage,cache, davlik cache
Copy firmware,rom, gapps, dfe into your internal storage, flash firmware (most ROMs include vendor but flash full firmware just to be sure), ROM, gapps, dfe and reboot.
Click to expand...
Click to collapse
HI mate,
I wanna check how long did it take to install Android 10 on your poco?
Cuz I installed the rom for more than 30 minutes after reboot and it is not over by follow your steps.
Idk what's the problem with my poco.
------------------------------------------------------------
New update:
Finally, I completed flash the rom, and Idk what's the problem, lol
I can boot into both fastboot and recovery. The recovery is Mi-recovery 3.0. Though, in recovery it doesn't seem that I can get any connection with it.
-----------
update
Currently, when I do anything beyond fastboot devices I get the screen reading "press any key to shutdown"
sotosgolf said:
Let's get this straight m8,
Can you boot into recovery ("up"+"power")?
Yes or No?
Click to expand...
Click to collapse
I can boot into mi-recovery 3.0 but no twrp or other custom recovery.
kitkat87 said:
I can boot into mi-recovery 3.0 but no twrp or other custom recovery.
Click to expand...
Click to collapse
You most likely had your bootloader re-locked. You have to unlock it again
sorry for the late reply.
I downloaded MiFlashPro, and apparently I could flash miui 11. So far, so good. But as I tried to flash or even boot into twrp I got the same command as I used to.
Can the issue be because I maybe don't have the latest drivers installed?
kitkat87 said:
I can boot into both fastboot and recovery. The recovery is Mi-recovery 3.0. Though, in recovery it doesn't seem that I can get any connection with it.
-----------
update
Currently, when I do anything beyond fastboot devices I get the screen reading "press any key to shutdown"
Click to expand...
Click to collapse
Do you have all the drivers installed on your pc ?
ADB and Fasboot drivers. And try using usb 2.0 ports. Mi tools have issues with usb 3.0 ports. And You should be on an Intel processor. You can also try twrp 3.3.1 beta by @Reignz.