I did a clean install of 9.5.10 and fastboot boot command seems to be not working anymore..it did work for me in previous versions..anyone facing the issue?
Related
I'm having a bit of trouble erasing the recovery off my Verizon HTC M8. Yes, I am Unlocked/S-OFF.
My trouble is when I reboot into fastboot I can erase/flash every partition on my phone EXCEPT the recovery...it says remote failed? I'm just trying to get a fresh install of TWRP. I can flash twrp just fine via fastboot but I was wondering if anyone else has had this problem.
I can flash my GF's G3 via fastboot erase recovery the fastboot flash twrp.img but my phone el-borko.
Any ideas?
Is anyone experience bootloops on random occasions with android 10 ROMs?
Things work great, played with tons of stuff and when android 10 ROMs appeared I jump to them. With android 9 firmware and android 10 custom ROMs I had no issues except the HEVC issues which were common before they fix this.
So after a while Xiaomi release android 10(miui) and I've put the firmware only and clean flash custom ROMs but after a few weeks I've experience some hard reboots. Random without any reason, bam hard reboot and when it occured it was bootlooping without a stop.
So Xiaomi image(unlocked), rom load and bam again restart, sometimes it booted properly but most of the times the boot loop never stopped UNLESS I force restart faster than the rom logo and enter twrp and shut it off and leave it a few seconds then boot it up ...after that it was working fine until the next boot loop that might occur same day or a few days later
One time it bootloop I enter to twrp fast and it boot looped even in TWRP!!!
This is weird, so let's fastboot the phone and clean everything up. Using Mi flashtool I tried to flash MIUI, after 30+ minutes nothing..it was trying to flash. Oh well. I force restart and enter fastboot and tried again..it finished with error but seemed to flash MIUI properly, clean flash custom ROMs but the issue remains
Anyone have similar experience? After some search some other Xiaomi users have similar issues and use an app called "wakelock" ..I'll see how this goes
P.S. If issue remains I'll fastboot the phone manually(without the mi flashtool), that would be my last resort - Sorry for the long post
P.S.2 usually the bootloop starts when I'm stop using my phone and press the power button to turn off display, it never happened when the phone is on idle
EDIT: Wakelock didn't save anything, got bootloop once again ..tonight I'm gonna try fastboot manual ..hoping for a fix(if it still keeps messing around I'd go back to android 9 where I had no issues at all)
So Xiaomi flash tool failed me if you read my original post, didn't want to risk it again, so I backup up everything and went the old way, it seems the bootloop is fixed, my proximity issues are also fixed(proximity sensor worked on short calls but on long calls the screen remained black - cleaned it as some suggested but the issue was there, now it seems that it's also fixed!!)
So if you have weird behavior just use CMD with fastboot style and write the following(one at a time, or you can create a batch file(bat file) but I strongly recommend that you do it one after another and seek for "success" after each command):
fastboot erase boot
fastboot flash crclist crclist.txt
fastboot flash sparsecrclist sparsecrclist.txt
fastboot flash xbl_ab xbl.img
fastboot flash xbl_config_ab xbl_config.img
fastboot flash abl_ab abl.img
fastboot flash tz_ab tz.img
fastboot flash hyp_ab hyp.img
fastboot flash devcfg_ab devcfg.img
fastboot flash storsec_ab storsec.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib_ab cmnlib.img
fastboot flash cmnlib64_ab cmnlib64.img
fastboot flash modem modem.img
fastboot flash dsp dsp.img
fastboot flash keymaster_ab keymaster.img
fastboot flash logo logo.img
fastboot flash misc misc.img
fastboot flash aop_ab aop.img
fastboot flash qupfw_ab qupfw.img
fastboot flash ImageFv imagefv.elf
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase sec
fastboot flash cust cust.img
fastboot flash boot boot.img
fastboot reboot
P.S. This WILL ERASE your internal data but won't lock bootloader, so back up your photos and files before
Requirements:
1) ADB Installer v1.4.3 (or any adb installer you prefer)
2) Fastboot MIUI rom, I've use "polaris_global_images_V11.0.4.0.QDGMIXM_20200325.0000.00_10.0_global_82f39e53fd"
Ran "fastboot flash boot twrp.img" instead of "fastboot boot twrp.img"
When trying install TWRP for the first time on a new (to me) Pixel 3, after unlocking the bootloader I ran "fastboot flash boot twrp.img" instead of "fastboot boot twrp.img". Can still enter the bootloader, but anything else gives a black screen.
What is the best method to recover from this? I still have access while in the bootloader through fastboot. Should I reflash stock google images or is something else better to recover? If I should reflash the stock google images what is the best method to do so?
Yes after reading more I realize this was the wrong thing to do. "fastboot boot twrp.img" was not working so I figured to try flashing instead, but afterwards realized that was obviously wrong.
Thanks for any help.
OK, It looks that I am soft bricked and a factory image reset is the only way to recover.
The steps I've seen mostly commonly referenced are to run the following
Code:
fastboot erase system_a
fastboot erase system_b
fastboot erase boot_a
fastboot erase boot_b
fastboot reboot-bootloader
flash-all.bat (using the factory images)
The issue seems to be that Android 10 which was on the phone doesn't work with fastboot erase. Is it necessary to run this or is it OK to go straight to flash-all.bat? (BTW I finally figured out that my issue above was TRWP doesn't support android 10 yet, but the guides I saw were older and didn't mention that. )
twfry said:
When trying install TWRP for the first time on a new (to me) Pixel 3, after unlocking the bootloader I ran "fastboot flash boot twrp.img" instead of "fastboot boot twrp.img". Can still enter the bootloader, but anything else gives a black screen.
What is the best method to recover from this? I still have access while in the bootloader through fastboot. Should I reflash stock google images or is something else better to recover? If I should reflash the stock google images what is the best method to do so?
Yes after reading more I realize this was the wrong thing to do. "fastboot boot twrp.img" was not working so I figured to try flashing instead, but afterwards realized that was obviously wrong.
Thanks for any help.
Click to expand...
Click to collapse
First things first. TWRP does not work at all on a Pixel with Android 10. Flash-all should be all you need to do to recover from your issue.
sliding_billy said:
First things first. TWRP does not work at all on a Pixel with Android 10. Flash-all should be all you need to do to recover from your issue.
Click to expand...
Click to collapse
The 3 top guides from google all had steps for android 9 apparently and so I didn't catch that 10 is different..... flash-all.sh worked and we're back. Thanks!
I've been trying to get custom ROMs to work but they don't boot correctly. The bootloader is unlocked and USB debugging is enabled. I'm using fastboot version 30.0.5. first I successfully flashed a stock ROM, following this tutorial and using the latest upload here. It flashes without any errors and boots fine. After that I tried to install havoc-os and ResurrectionRemix. Both of them flashed without any errors, but when I tried to boot them they just showed the splash screen for a few seconds then went to the bootloader. I've tried using the --disable-verification option with fastboot when flashing vbmeta.img. When I run fastboot -w, it gives the warning
Code:
Erase successful, but not automatically formatting.
File system type raw not supported.
Any idea how I can fix this?
lukkk said:
I've been trying to get custom ROMs to work but they don't boot correctly. The bootloader is unlocked and USB debugging is enabled. I'm using fastboot version 30.0.5. first I successfully flashed a stock ROM, following this tutorial and using the latest upload here. It flashes without any errors and boots fine. After that I tried to install havoc-os and ResurrectionRemix. Both of them flashed without any errors, but when I tried to boot them they just showed the splash screen for a few seconds then went to the bootloader. I've tried using the --disable-verification option with fastboot when flashing vbmeta.img. When I run fastboot -w, it gives the warning
Code:
Erase successful, but not automatically formatting.
File system type raw not supported.
Any idea how I can fix this?
Click to expand...
Click to collapse
Was the stock rom Android 11 but any chance?
I've recently switched to FerenOS(Unbuntu) tried flashing a spare device but I've run into a block. I've searched extensively but can't find what I need.
Whenever I flashed a stock image on Windows 10, I followed these commands:
fastboot --slot=all flash bootloader bootloader.img
fastboot reboot bootloader
fastboot --slot=all flash radio radio.img
fastboot reboot bootloader
fastboot --slot=(current) --skip-reboot update image.zip
Everything goes good up until flashing the image. The phone stays in fastboot and fails to reboot into fastbootd and start the update with the error "FAILED (remote: Partition system not found)"
I'm able to get to fastbootd by going into recovery and typing adb reboot fastboot. But even trying to sideload from adb doesn't work. It says "adb: command failed to read: success"
My adb is up to date but I can't figure this out. Maybe I'm using the wrong commands? Any help would be appreciated.
Nevermind, it's been solved and the phone unbricked