Hello, i want to share my experience because it may me useful for others. I have also a question for you at the end of the story.
I rooted my MI A3 with magisk but without twrp back in 2019 following the guide posted on this forum. The phone had android 9 and I never did software updates. Once in a while a messagge appeared on the screen saying that my software was obsolete and that I needed to update but I always managed to dodge it.
Some days ago my phone started behaving strangly (eg: I turned the volume down to zero but it turned up by itself) so I decided to reboot it. Something went wrong and the phone rebooted in fastboot mode. I tried many things but the phone was only able to boot in fastboot mode.
I thought that maybe the problem was related to the software update that sometimes was popping on the screen. So, i connected the phone to my pc and executed some fastboot commands:
fastboot getvar current-slot (to know which partition was in use. It was B)
fastboot set_active A (to switch to the other partition)
fastboot reboot
The phone rebooted correctly but it was on android 10 (before the problem it was on android 9) and without root. Everything seemed working fine and all the data was safe (only one thing changed, the boot process require much more time now). So, I realized that the phone applied the system update by itself (without my consent).
Now my question. The phone works well for the moment but how can i check the status of the partition B? I suspect that it may be damaged.
Furthermore I would like to flash the stock firmware, clear all the data and unroot the phone. Can I proceed? Should I flash both partitions?
Thanks
Any suggestions?
Related
Hello, I've ran into some trouble with my nexus 9. After the last update my device seems to be bricked, just stuck on the white "google" logo during start up.
I'm trying to flash OEM android on my device and have been unsuccessful because my bootloader seems to be locked, and the only way I can find online is to do it through developer options which I cannot access now since my device is bricked. I've tried the fastboot command oem unlock and permission is denied. Prior to this I have not enabled developer option or usb debugging because I was ok with using stock software.
I can get into bootloader mode and access fastboot USB but I cannot flash my device due to bootloader being locked!
I've also tried Recovery -> wipe all data, and my device is still bricked afterwards!
Is there anything I can do at this point?
I've been running stock software the whole time! Never rooted / unlocked my device.
Forget about it.
Talk to the vendor (google / amazon / etc) the device is FUBAR
I am getting a new one, since there is no way to fix this.
period.
sorry for everyone affected, but google said, that there is no way to fix it.
damn..just called google and they said they will get back to me next week. this is pretty sad
doanb666 said:
Forget about it.
Talk to the vendor (google / amazon / etc) the device is FUBAR
I am getting a new one, since there is no way to fix this.
period.
sorry for everyone affected, but google said, that there is no way to fix it.
Click to expand...
Click to collapse
Ariadust said:
damn..just called google and they said they will get back to me next week. this is pretty sad
Click to expand...
Click to collapse
It seems, I have the same problem. I tried to wipe it several times, it is no use.
Maybe I am completely dumb, but could one not sideload from 5.1.1. to 5.0.2.?
adb sideload <>
is about the only thing that is working. I don't know, how ota-files are created.
Have you tried this?
http://forum.xda-developers.com/nex...-disabling-t2951312/post60702161#post60702161
Put Device in Fastboot mode:
Power and Volume down,
then in the bootloader, go to fastboot.
With the fastboot tool (google), type:
fastboot format cache
fastboot format:ext4 userdata
It fixed it for some users, because wiping the userdata is apparently different from a factory reset in the boot loader.
For me, it did not work out: I did not end in a boot loop but in a neverending boot sequence.
Trying to flash 5.1.1 on my N6; now stuck on colored dot bootloop. Tried fastboot format cache and fastboot format userdata; both fail because the bootloader is locked.
Google has completely ruined this. I've owned the Galaxy Nexus, Nexus 4, and Nexus 5, and I *never* had a single issue doing simple **** like this on those phones. Here, everything fails. All the time. This time it's failed hard enough, evidently, to cause a permanent brick. Thanks a lot, Google.
Guys, I installed the ROM Pixel Experience. This one:
https://forum.xda-developers.com/mi-pad-4/development/rom-pixelexperience-t3878616
I am having a huge issue with this rom. I installed it and it works fine, however, since it doesn't support USB, I decided to install the MIUI stock rom back. Well, in order to do that, you have to have the device in FASTBOOT mode.
When I go to the prompt and type fastboot devices, I get a result, showing that my computer can detect the device.
However, every time I am in FASTBOOT mode, after 30 seconds (exactly!) it reboots. So, I am afraid to start flashing it and then the device reboots and my installation gets corrupted.
Any ideas on how to solve this? I just need the FASTBOOT mode to last as long as necessary for me to install the older room back.
Can you explain what you mean by "Doesnt support USB"?
And the fastboot issue is definitely weird. That should not be happening. Does this happen when the device is plugged in only? What happens if the device is not plugged to the computer?
Hi guys been spending all night trying to figure out but seems nothing is working. HELP! I know i can get it to work.
So tried to root my A2017G previously but saw all the horror brick stories so ended up just doing the multiple OTA updates via SDCARD upgrade.zip and finally ended up with OREO BO3 version. running fine except for ridiculous battery meter levels playing up but just kept it charged most of the time.
1) at first I tried to check bootloader unlock status from fastboot. But somehow unable to as fastboot is not there! So i thought maybe fastboot is corrupt (stock recovery options ok / also power plus down gets stuck in FTM mode (easy to reboot with adb command) So unable to check bootloader (i am thinking its probably still locked)
2) so got latest version of TWRP 3.3 something and flashed it --> result in phone black screen but detectable (I assume in EDL mode.) '
3) Tried to flash Nougat B10 EDL with EDL tool (working now but after everything is ready to flash it says"" 13:02:38: {ERROR: WritePort:5164 Could not write to '\\.\COM8', Windows API WriteFile failed! Your device is probably *not* on this port, attempted 100 times""
4) MiFlash unable to read hello packet. But i tried pressing power and connecting quickly and suddenly starts flashing B10 nougat EDL ROM but doesnt complete with a "function: sahara_rx_data:237, unable to read packet header" error. Should I be using a stock rom with Meta-INF folder rather than the EDL version? Also should i be flashing OREO stock rom rather than nougat with MiFlash? or it doesnt matter?
5) tried the DFU tool initially qualcomm and com8 detected but says disconnected. (so its in EDL probably but somehow still disconnected?
So currently
1) trying to let the phone battery run out, though i doubt its any use as i probably bricked it installing twrp without unlock bootloader on OREO.
2) Also downloading Oreo stock rom to try and flash with miflash.
Any help or point to some discussion i missed would be helpful thanks. Just wanna get root and GPS tools running so I can let the kids catch some Pokemon without GOing outside.
Seems like the battery had to run out first. Then it started recharging . After about 5 mins I just pressed power button without up or down. Phone rebooted nicely back into Oreo. PhEW... Then i used a stock 2017g EDL for nougat B10 (7.1.1) and flashed with Miflash by going into proper EDL (used ADB reboot EDL command)
Ok some more small hiccups along the way but being able to access EDl i managed to flash TWRP 3.2.1 and then load it up and flash SuperSU for root.
Now to read the threads on how to get rid of the bootloader unlock screen as well as load in the battery saving scripts.
Hey community,
I have been running Poco F1 with twrp and PixelExperience for the last 2 years. Considering the past record of the OS and my experience with the OS, I decided recently to upgrade to the newer PE12 for Poco F1 (maintained by Lakshay Garg). It went smooth initially and after the last OTA update, the phone started behaving weirdly.
Long story short,
This morning the phone went into an automatic restart and is now stuck in a boot loop. It boots and reaches the "G" logo and reboots. However, the weird part is,
Code:
fastboot flash
and
Code:
fastboot boot
are not available, throwing errors. The device is visible in
Code:
adb devices
and
Code:
fastboot devices
. This problem occurs when the phone is not plugged in. Once plugged in, the phone runs fine and everything just works. TWRP is not accessible, as if it is not there anymore and the only recovery that I can reach is the pixel recovery which has no option to flash any custom recovery (newbie, so not sure if something like this should exists or not).
I've tried various threads here and wasn't able to find any solution. Let me know what commands/outputs you guys might need from the device to help me in this.
Thanks in advance. Hope this gets fixed soon.
tysonX5653 said:
Hey community,
I have been running Poco F1 with twrp and PixelExperience for the last 2 years. Considering the past record of the OS and my experience with the OS, I decided recently to upgrade to the newer PE12 for Poco F1 (maintained by Lakshay Garg). It went smooth initially and after the last OTA update, the phone started behaving weirdly.
Long story short,
This morning the phone went into an automatic restart and is now stuck in a boot loop. It boots and reaches the "G" logo and reboots. However, the weird part is,
Code:
fastboot flash
and
Code:
fastboot boot
are not available, throwing errors. The device is visible in
Code:
adb devices
and
Code:
fastboot devices
. This problem occurs when the phone is not plugged in. Once plugged in, the phone runs fine and everything just works. TWRP is not accessible, as if it is not there anymore and the only recovery that I can reach is the pixel recovery which has no option to flash any custom recovery (newbie, so not sure if something like this should exists or not).
I've tried various threads here and wasn't able to find any solution. Let me know what commands/outputs you guys might need from the device to help me in this.
Thanks in advance. Hope this gets fixed soon.
Click to expand...
Click to collapse
Seems to be a battery problem. How old is it? You may need to replace it.
However make sure you followed the clean install method before you come on a conclusion. Also try to not use any Magisk modules.
Best Clean Install method:
Backup all your data. All your data into Internal Storage will be lost during this process.
Download latest Official TWRP Recovery, Pixel Experience build.
Create one Folder and move all the files you downloaded there.
Reboot to Fastboot Mode
Connect your device to PC and Boot into to TWRP via ADB or Minimal ADB and Fastboot:
Code:
fastboot boot <recovery_filename>.img
Example:
Code:
fastboot boot C:\Users\Retrial\Desktop\twrp-3.6.1_9-0-beryllium.img
Select Wipe > Advanced Wipe -> Select Dalvik / ART Cache, System, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe.
Go back and select Wipe > Format Data > type yes
While you are in TWRP, transfer the Folder with the files you downloaded above.
Flash Pixel Experience ROM.
Flashing the ROM will replace TWRP with PE Recovery so OTA updates can be installed without problems since TWRP currently doesn't support decryption on A12 encypted ROMs - If you need in future to change ROM just fastboot boot to twrp via adb and flash img of twrp to recovery partition.
Done! Reboot to system.
Thanks, turns out that it was a battery problem after all. After battery replacement everything is working just fine. I also installed Awaken OS as Pixel Experience was removing the TWRP recovery each time I flashed it. Now as for my fastboot, initially it was not working; it was showing this error whenever I tried to flash TWRP recovery or any stock recovery:
Sending 'boot.img' (38640 KB) FAILED (Write to device failed (Cannot send after transport endpoint shutdown)) fastboot: error: Command failed
After this, the fastboot mode was diconnected and my phone was showing this Error:
Press any Key to Shut Down
It was resolved by running this bat file (as admin) :
https://bit.ly/31T2LcB
After running this file, there was no error and I was able to flash the twrp Recovery smoothly. So thanks for all the help really appreciate it.
tysonX5653 said:
Thanks, turns out that it was a battery problem after all. After battery replacement everything is working just fine. I also installed Awaken OS as Pixel Experience was removing the TWRP recovery each time I flashed it. Now as for my fastboot, initially it was not working; it was showing this error whenever I tried to flash TWRP recovery or any stock recovery:
Sending 'boot.img' (38640 KB) FAILED (Write to device failed (Cannot send after transport endpoint shutdown)) fastboot: error: Command failed
After this, the fastboot mode was diconnected and my phone was showing this Error:
Press any Key to Shut Down
It was resolved by running this bat file (as admin) :
https://bit.ly/31T2LcB
After running this file, there was no error and I was able to flash the twrp Recovery smoothly. So thanks for all the help really appreciate it.
Click to expand...
Click to collapse
Did you face the problem again?
I am using PE11 since last 2 years but suddenly i started facing the same problem. When plugged in, works fine. When I unplug it, works until screen is on and when I use power button to lock or unlock, phone goes into bootloop. I opend it in twrp where it can work as long as battery lasts, that's why I am not sure if it's a battery problem or something else
Hi there! I'm hoping someone on XDA Developers can help me sort out a root gone-wrong.
I did my best to follow the guide on XDA. I have an Umidigi A9 Pro with 6gb ram. I was successfully able to get the android tools on PC and was able to unlock the bootloader. I went to the Umidigi website to get the ROM. I think I *might* have grabbed the wrong one. Once I got this zip from the Umidigi website, I unzipped the folder and copied the boot.img that was in that root folder to the device. I then went into Magisk and patched the img. I then copied the patched img to my PC then use the commands on the XDA guide to flash the image to the device, the flash was successful (I think). However the device is now stuck in a boot loop. The device displays the Umidigi OEM logo and the android logo; underneath it says in small text:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
after 5 seconds the screen goes black and then comes back with the same screen. This happens continuously. I have tried holding the volume down, the power button, and several combinations of volume up, down, and power. Holding all buttons down makes the screen stay black, however while plugged into the PC the PC still makes the device connected and disconnected sounds off and on. Whenever I release the buttons, it goes right back to the loop. Windows PC plays the device connected and disconnected sound on and off. The command prompt is not able to affect the device. When I run "adb devices" it doesn't display the phone so it doesn't seem that windows is detecting the device.
ROM: https://community.umidigi.com/forum.php?mod=viewthread&tid=22236&extra=page=1
https://www.umidigi.com/page-Download.html
I'm hoping for some help on this one
Thank you!
It should be obvious that when being in a bootloop ADB cannot function: On Android side the ADB daemon gets started and after seconds closed, and this over and over again.
In the simplest explanation, a bootloop describes when your phone is stuck in a loop of rebooting. The term "bootloop" is just a more common way of saying "reboot loop."
Curious if you ever managed to get this figured out? I'm in essentially the same situation, though I was not attempting to flash a ROM. I successfully managed to get TWRP 3.5.2 installed and then I was trying to get Magisk installed.
My phone data was wiped, which honestly I didn't care about, however I must have done something wrong with the Magisk installation as now I have the rebooting issue.
I'm able to use ADB and have been trying to push a ROM to the sdcard folder of the internal storage. ADB says the file has successfully completed, but nothing is on the phone. I fixed the issue of the storage showing up as 0MB by changing from EX4 to EX2 and then changed it back to 4.
Really unsure of how to flash a ROM if I can't get the file to pushed to the phones internal memory though.
Zeidwinder said:
Curious if you ever managed to get this figured out? I'm in essentially the same situation, though I was not attempting to flash a ROM. I successfully managed to get TWRP 3.5.2 installed and then I was trying to get Magisk installed.
My phone data was wiped, which honestly I didn't care about, however I must have done something wrong with the Magisk installation as now I have the rebooting issue.
I'm able to use ADB and have been trying to push a ROM to the sdcard folder of the internal storage. ADB says the file has successfully completed, but nothing is on the phone. I fixed the issue of the storage showing up as 0MB by changing from EX4 to EX2 and then changed it back to 4.
Really unsure of how to flash a ROM if I can't get the file to pushed to the phones internal memory though.
Click to expand...
Click to collapse
I honestly haven't messed with it since. It was a very cheap extra android phone I had laying around. Once it got messed up I pretty much just put it in a drawer and said "maybe another day"