I've got my POCO F3 global for 4 months or so and unlocked the bootloader to install a custom ROM.
Since then I've installed Pixel Extended (stayed with it for 2 months or so) and then installed crDroid. I experienced a lot of random reboots since then which I thought could be a rom install problem or something like that so I clean flashed arrow OS but the device wouldn't boot up at all. So I downloaded fastboot stock V12.5.2.0.RKHMIXM GLOBAL (which is as of now the latest stable for Global version) but the device would always bootloop and eventually go to fastboot mode. I tried reflashing it several times and even flashing a previous version of the GLOBAL V12.0.2.0.RKHMIXM and it just doesn't boot the system up - it just bootloops and eventually falls into fastboot mode. I've learned that when I have just flashed it, I'm even able to go POWER + VOL(+) to go to Mi recovery (and even tried to wipe all data from there hoping it would make a difference). But if I let it try boot the system, after it goes to fastboot mode once, I can never access the recovery again.
I'm currently able to boot TWRP, and flash any ROM on top of this non booting stock image and sometimes it does boot up the first time but if I try to flash anything on top of it like opengapps it just fails to boot up ever again. I must say that even after I flash crDroid, it bootloops a lot of time before crDroid logo appears.
So my problem is that for the last 3 weeks or so I'm not able to boot up stock flashed on fastboot and if I flash any custom ROM on top of it it is completely bugged out (random reboots, can't flash gapps, bootloops 10 times before loading the ROM when restarting the phone). I don't know if I somehow messed up any partitions or if there's any problem with my actual hardware that may be causing this. By the way I've been using TWRP-3.5.1-alioth-Nebrassy-2 for flashing and latest platform tools for adb and fastboot (31.0.3). And also, I've been using the usb c cable that came with the device connected to a usb 2.0 hub.
I have the impression that if I'm able to flash stock appropriately and boot it up it might fix the problem but I could be wrong. Also, it's the first time that I flash an A/B device which sometimes gets me confused about the slots.
I've been flashing my android devices since 2010 (Motorola Quench was my first android device) and I've always had to read the forums but I never encountered a problem I couldn't just fix it by returrning to stock or wiping it.
Welcome to the forum mate.
Did you flash the Global Fastboot Stock ROM using Mi Flash? I'd recommend it, instead of using the .BAT files directly.
After it's done, it should automatically boot you into System.
dreamytom said:
Welcome to the forum mate.
Did you flash the Global Fastboot Stock ROM using Mi Flash? I'd recommend it, instead of using the .BAT files directly.
After it's done, it should automatically boot you into System.
Click to expand...
Click to collapse
Thank you for a prompt response, @dreamytom
I think I've used that but of course I'll try it again. I'm downloading MiFlash20210226 (latest as of now).
Should I check clean all before flashing it?
chrisparkerrr said:
Thank you for a prompt response, @dreamytom
I think I've used that but of course I'll try it again. I'm downloading MiFlash20210226 (latest as of now).
Should I check clean all before flashing it?
Click to expand...
Click to collapse
Just dont select flash and lock...
I reflashed it using MiFlash the first time and it gave me a crclist flash error.
I proceeded and removed the following 2 lines from flash_all.bat file
fastboot %* flash crclist %~dp0images\crclist.txt || @echo "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @echo "Flash sparsecrclist
I've seen this trick before on other forums and I've never seen it gone badly so I'm trying again without those lines
Rstment ^m^ said:
Just dont select flash and lock...
Click to expand...
Click to collapse
oh, that lesson I learned the hard way in the past. thanks for reminding me of that
After flashing, I got an error on FlashDone step but all previous images seems to be successfully flashed.
It rebooted several times until it ended up on fastboot mode again.
Here's the tail of the log
[1:38:59 PM 9d3839f8]:info1:$fastboot -s devicename set_active a ||
[1:38:59 PM 9d3839f8]:info2:Setting current slot to 'a' OKAY [ 0.008s]
[1:38:59 PM 9d3839f8]:info2:Finished. Total time: 0.010s
[1:38:59 PM 9d3839f8]:info1:$fastboot -s devicename reboot ||
[1:38:59 PM 9d3839f8]:info2:Rebooting OKAY [ 0.000s]
[1:38:59 PM 9d3839f8]:info2:Finished. Total time: 0.000s
[1:38:59 PM 9d3839f8]:begin FlashDone
[1:38:59 PM 9d3839f8]:errMsg is null
[1:38:59 PM 9d3839f8]:begin checkPoint
[1:38:59 PM 9d3839f8]:error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done
[1:38:59 PM 9d3839f8]:process exit.
[1:39:00 PM 9d3839f8]:flashSuccess False
[1:39:00 PM 9d3839f8]:isFactory False CheckCPUID False
[1:39:00 PM 9d3839f8]:before:flashSuccess is False set IsUpdate:True set IsDone True
[1:39:00 PM 9d3839f8]:after:flashSuccess is False set IsUpdate:false set IsDone true
chrisparkerrr said:
Thank you for a prompt response, @dreamytom
I think I've used that but of course I'll try it again. I'm downloading MiFlash20210226 (latest as of now).
Should I check clean all before flashing it?
Click to expand...
Click to collapse
Yes definitely check "Clean All" before Flashing.
The default checkmark "Clean All and Lock" will lock your bootloader (which you probably don't want happening).
Let us know how it goes.
dreamytom said:
Yes definitely check "Clean All" before Flashing.
The default checkmark "Clean All and Lock" will lock your bootloader (which you probably don't want happening).
Let us know how it goes.
Click to expand...
Click to collapse
It bootloops 5 or 6 times until it lands on fastboot mode again
(flashing V12.5.2.0.RKHMIXM Global version)
I'm able to enter the MIUI recovery though
chrisparkerrr said:
After flashing, I got an error on FlashDone step but all previous images seems to be successfully flashed.
It rebooted several times until it ended up on fastboot mode again.
Here's the tail of the log
[1:38:59 PM 9d3839f8]:info1:$fastboot -s devicename set_active a ||
[1:38:59 PM 9d3839f8]:info2:Setting current slot to 'a' OKAY [ 0.008s]
[1:38:59 PM 9d3839f8]:info2:Finished. Total time: 0.010s
[1:38:59 PM 9d3839f8]:info1:$fastboot -s devicename reboot ||
[1:38:59 PM 9d3839f8]:info2:Rebooting OKAY [ 0.000s]
[1:38:59 PM 9d3839f8]:info2:Finished. Total time: 0.000s
[1:38:59 PM 9d3839f8]:begin FlashDone
[1:38:59 PM 9d3839f8]:errMsg is null
[1:38:59 PM 9d3839f8]:begin checkPoint
[1:38:59 PM 9d3839f8]:error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done
[1:38:59 PM 9d3839f8]:process exit.
[1:39:00 PM 9d3839f8]:flashSuccess False
[1:39:00 PM 9d3839f8]:isFactory False CheckCPUID False
[1:39:00 PM 9d3839f8]:before:flashSuccess is False set IsUpdate:True set IsDone True
[1:39:00 PM 9d3839f8]:after:flashSuccess is False set IsUpdate:false set IsDone true
Click to expand...
Click to collapse
Try the following:
- Disconnect phone from PC and reboot Fastboot Mode (with POWER + Volume Down)
- Close & Re-open Mi Flash
- Connect phone to PC
- Go into Mi Flash's Configuration page:
Remove the text in the picture:
https://www.thecustomdroid.com/wp-content/uploads/2018/01/Fix-Mi-Flash-Tool-Not-Catch-CheckPoint-Error.jpg
- Check "Clean All" in bottom right corner
- Flash
dreamytom said:
Try the following:
- Disconnect phone from PC and reboot Fastboot Mode (with POWER + Volume Down)
- Close & Re-open Mi Flash
- Connect phone to PC
- Go into Mi Flash's Configuration page:
Remove the text in the picture:
https://www.thecustomdroid.com/wp-content/uploads/2018/01/Fix-Mi-Flash-Tool-Not-Catch-CheckPoint-Error.jpg
- Check "Clean All" in bottom right corner
- Flash
Click to expand...
Click to collapse
Now I get a success message on MiFlash but it bootlooped 7 times until it got to fastboot mode again :/
I'm going to flash again with these configs
{
"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"
}
Trying to see if I get more detailed logs or something..
chrisparkerrr said:
Now I get a success message on MiFlash but it bootlooped 7 times until it got to fastboot mode again :/
Click to expand...
Click to collapse
Add the lines into the .BAT script again, that you've removed. This time, try flashing with "Erase All" and "Verbose" enabled in the Mi Flash Configuration-page.
You can also try "check MD5 before Flash" to see if perhaps the ROM is corrupt.
Leave the "CheckPoint" argument removed, that argument is unnecessary.
Keep in mind that you have to disconnect your phone, reboot Fastboot Mode, and re-connect phone to PC.
This is because Fastboot Mode stops receiving any input after an initiated Flash and will result in an error. It may also error out, if you reboot Fastboot Mode while it's already plugged into your PC, for some reason.
dreamytom said:
Add the lines into the .BAT script again, that you've removed. This time, try flashing with "Erase All" and "Verbose" enabled in the Mi Flash Configuration-page.
You can also try "check MD5 before Flash" to see if perhaps the ROM is corrupt.
Leave the "CheckPoint" argument removed, that argument is unnecessary.
Keep in mind that you have to disconnect your phone, reboot Fastboot Mode, and connect phone to PC again.
This is because Fastboot Mode stops receiving any input after an initiated Flash and will result in an error.
Click to expand...
Click to collapse
Will do and report back.
dreamytom said:
Add the lines into the .BAT script again, that you've removed. This time, try flashing with "Erase All" and "Verbose" enabled in the Mi Flash Configuration-page.
You can also try "check MD5 before Flash" to see if perhaps the ROM is corrupt.
Leave the "CheckPoint" argument removed, that argument is unnecessary.
Keep in mind that you have to disconnect your phone, reboot Fastboot Mode, and re-connect phone to PC.
This is because Fastboot Mode stops receiving any input after an initiated Flash and will result in an error. It may also error out, if you reboot Fastboot Mode while it's already plugged into your PC, for some reason.
Click to expand...
Click to collapse
MD5 validation succeeded, put back the CheckPoint argument and checked Verbose and EraseAll.
I just noticed that when I check EraseAll and click OK, next time I open the Configuration menu the EraseAll checkbox is unchecked. I checked it the first time anyways and procceeded with flashing.
This is the tail log:
[2:19:17 PM 9d3839f8]:info2:Sending sparse 'super' 1/9 (722352 KB) OKAY [ 17.075s]
[2:19:17 PM 9d3839f8]:info2:Writing 'super' OKAY [ 0.000s]
[2:19:54 PM 9d3839f8]:info2:Sending sparse 'super' 2/9 (785380 KB) OKAY [ 36.804s]
[2:19:54 PM 9d3839f8]:info2:Writing 'super' OKAY [ 0.000s]
[2:20:31 PM 9d3839f8]:info2:Sending sparse 'super' 3/9 (720896 KB) OKAY [ 37.195s]
[2:20:31 PM 9d3839f8]:info2:Writing 'super' OKAY [ 0.000s]
[2:21:06 PM 9d3839f8]:info2:Sending sparse 'super' 4/9 (766564 KB) OKAY [ 34.844s]
[2:21:06 PM 9d3839f8]:info2:Writing 'super' OKAY [ 0.001s]
[2:21:43 PM 9d3839f8]:info2:Sending sparse 'super' 5/9 (744476 KB) OKAY [ 37.345s]
[2:21:43 PM 9d3839f8]:info2:Writing 'super' OKAY [ 0.000s]
[2:22:20 PM 9d3839f8]:info2:Sending sparse 'super' 6/9 (768840 KB) OKAY [ 36.824s]
[2:22:20 PM 9d3839f8]:info2:Writing 'super' OKAY [ 0.001s]
[2:22:57 PM 9d3839f8]:info2:Sending sparse 'super' 7/9 (727352 KB) FAILED (remote: 'failed to check sparse crc')
[2:22:57 PM 9d3839f8]:info2:fastboot: error: Command failed
[2:22:57 PM 9d3839f8]:info1:"Flash super error"
[2:22:57 PM 9d3839f8]:begin FlashDone
[2:22:57 PM 9d3839f8]:error:Sending sparse 'super' 7/9 (727352 KB) FAILED (remote: 'failed to check sparse crc')
[2:22:57 PM 9d3839f8]:process exit.
[2:22:57 PM 9d3839f8]:flashSuccess False
[2:22:57 PM 9d3839f8]:isFactory False CheckCPUID False
[2:22:57 PM 9d3839f8]:before:flashSuccess is False set IsUpdate:True set IsDone True
[2:22:57 PM 9d3839f8]:after:flashSuccess is False set IsUpdate:false set IsDone true
This is what was failing before I removed the
fastboot %* flash crclist %~dp0images\crclist.txt || @echo "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @echo "Flash sparsecrclist
lines.
chrisparkerrr said:
...
[2:22:57 PM 9d3839f8]:info2:Sending sparse 'super' 7/9 (727352 KB) FAILED (remote: 'failed to check sparse crc')
[2:22:57 PM 9d3839f8]:info2:fastboot: error: Command failed
[2:22:57 PM 9d3839f8]:info1:"Flash super error"
[2:22:57 PM 9d3839f8]:begin FlashDone
[2:22:57 PM 9d3839f8]:error:Sending sparse 'super' 7/9 (727352 KB) FAILED (remote: 'failed to check sparse crc')
[2:22:57 PM 9d3839f8]rocess exit.
[2:22:57 PM 9d3839f8]:flashSuccess False
[2:22:57 PM 9d3839f8]:isFactory False CheckCPUID False
[2:22:57 PM 9d3839f8]:before:flashSuccess is False set IsUpdate:True set IsDone True
[2:22:57 PM 9d3839f8]:after:flashSuccess is False set IsUpdate:false set IsDone true
[/ICODE]
This is what was failing before I removed the
fastboot %* flash crclist %~dp0images\crclist.txt || @echo "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @echo "Flash sparsecrclist
lines.
Click to expand...
Click to collapse
I've seen the error "Failed to check Sparse CRC" quite a few times and had it myself.
Try Rebooting your PC and switching the USB port. You can also try changing the cable.
That doesn't sound like it'd do much, but a dude I've chatted with from here, and myself had this error, and we both succeeded in flashing our ROMs by doing the above. ^
Also make sure the path to your ROM doesn't contain spaces. Mi Flash is stubborn.
I just temporarily put the ROM folder in C:/
Try flashing with this tool.
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
www.xiaomitool.com
While you have your phone connected to the PC, Select my device is bricked, Choose your phone model from it's list. It will download the stock ROM on itself and flash it. I had gone through the same problem a few months ago when i had the k20 pro. This tool got it sorted out. Give it a try. Goodluck.
dreamytom said:
I've seen the error "Failed to check Sparse CRC" quite a few times and had it myself.
Try Rebooting your PC and switching the USB port. You can also try changing the cable.
That doesn't sound like it'd do much, but a dude I've chatted with from here, and myself had this error, and we both succeeded in flashing our ROMs by doing the above. ^
Also make sure the path to your ROM doesn't contain spaces. Mi Flash is stubborn.
I just temporarily put the ROM folder in C:/
Click to expand...
Click to collapse
Created a folder for the image at C:\mi\ even though my previous folder didn't have any spaces.
Changed the cable and the port (I was using a USB C dock + USB A dongle and now it's directly in the back of my computer)
Result is the same 'failed to check sparse crc'
I'll try different combinations of ports and cables to see if the outcome changes and report back.
Animesh Singh said:
Try flashing with this tool.
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
www.xiaomitool.com
While you have your phone connected to the PC, Select my device is bricked, Choose your phone model from it's list. It will download the stock ROM on itself and flash it. I had gone through the same problem a few months ago when i had the k20 pro. This tool got it sorted out. Give it a try. Goodluck.
Click to expand...
Click to collapse
Thank you for replying.
I got this tool installed and even tried it in the past weeks. It downloaded the fastboot ROM again but I had the same problems as mentioned above. I'll try it again soon.
chrisparkerrr said:
Created a folder for the image at C:\mi\ even though my previous folder didn't have any spaces.
Changed the cable and the port (I was using a USB C dock + USB A dongle and now it's directly in the back of my computer)
Result is the same 'failed to check sparse crc'
I'll try different combinations of ports and cables to see if the outcome changes and report back.
Click to expand...
Click to collapse
That sucks. Try EU ROM (or if you're not in the EU, your specific region), instead of Global.
I don't know how on earth that would make a difference, but just to see...
Related
NOTE: Bootloader should be unlocked for this method to work. Root not required.
1) Download the factory image relevant to your Galaxy Nexus from the below page.
https://developers.google.com/android/nexus/images#takju
2) Unzip the .tgz file and keep it under, say C:/
3) Edit the "flash-all.bat" and remove the "-w" parameter from "fastboot -w update image-takju-jwr66v.zip"
4) Delete "userdata.img" from "image-takju-jwr66v.zip".
5) Copy fastboot.exe file into the “takju-jwr66v” directory.
6) Reboot and keep the phone in fastboot mode. [ a) Turn on USB Debugging b) Turn off your Phone c) Hold down Volume UP + Volume Down + Power buttons ]
7) Issue the command "flash-all.bat".
8) Wait for the process to finish, and then the Galaxy Nexus will reboot upgraded with stock Android 4.3
9) Cheers and enjoy !!!
Logs below for even better understanding
=========================================
C:\gn4life\takju-jwr66v-factory-c2ef855e\takju-jwr66v>dir
Volume in drive C is OSDisk
Volume Serial Number is C49E-94F0
Directory of C:\gn4life\takju-jwr66v-factory-c2ef855e\takju-jwr66v
07/24/2013 11:25 PM <DIR> .
07/24/2013 11:25 PM <DIR> ..
05/07/2010 11:48 AM 578,611 adb.exe
05/07/2010 11:48 AM 96,256 AdbWinApi.dll
05/07/2010 11:48 AM 60,928 AdbWinUsbApi.dll
07/12/2013 03:56 AM 2,363,392 bootloader-maguro-primemd04.img
05/07/2010 11:48 AM 336,613 fastboot.exe
07/24/2013 11:08 PM 953 flash-all.bat
07/12/2013 03:56 AM 956 flash-all.bat.bak
07/12/2013 03:56 AM 827 flash-all.sh
07/12/2013 03:56 AM 785 flash-base.sh
07/24/2013 11:09 PM 295,614,131 image-takju-jwr66v.zip
07/12/2013 03:56 AM 12,583,168 radio-maguro-i9250xxlj1.img
11 File(s) 311,636,620 bytes
2 Dir(s) 7,925,932,032 bytes free
C:\gn4life\takju-jwr66v-factory-c2ef855e\takju-jwr66v>
C:\gn4life\takju-jwr66v-factory-c2ef855e\takju-jwr66v>flash-all.bat
sending 'bootloader' (2308 KB)... OKAY [ 0.314s]
writing 'bootloader'... OKAY [ 1.478s]
finished. total time: 1.793s
rebooting into bootloader... OKAY [ 0.006s]
finished. total time: 0.006s
< waiting for device >
sending 'radio' (12288 KB)... OKAY [ 1.675s]
writing 'radio'... OKAY [ 1.856s]
finished. total time: 3.532s
rebooting into bootloader... OKAY [ 0.007s]
finished. total time: 0.007s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: 0149BDCB0D012016
--------------------------------------------
checking product... OKAY [ 0.006s]
checking version-bootloader... OKAY [ 0.008s]
checking version-baseband... OKAY [ 0.007s]
sending 'boot' (4376 KB)... OKAY [ 0.709s]
writing 'boot'... OKAY [ 0.506s]
sending 'recovery' (4924 KB)... OKAY [ 0.662s]
writing 'recovery'... OKAY [ 0.689s]
sending 'system' (479244 KB)... OKAY [ 65.013s]
writing 'system'... OKAY [ 48.280s]
rebooting...
finished. total time: 115.913s
Press any key to exit...
So it's not just my bootloader that got slower. Yours also made you <waiting for device> each time the process rebooted the bootloader. It never happened before.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
beekay201 said:
So it's not just my bootloader that got slower. Yours also made you <waiting for device> each time the process rebooted the bootloader. It never happened before.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
yessssssssssss worked for me
Caused a bootloop for me and when I tried to reboot in recovery I got red triangle and Android. Didn't give any error messages.
Am just going to do full wipe now and retry.
Worked like a charm
Did what the post said and got 4.3 without losing any data.
Thanks!
Color me suspicious, but I bet there's a good reason that the -w is there...
flash successful without losing data.. but camera lag still exist on my gnex, and vitamio got multiple crash after rebooting. Anybody got the same experience?
I did get a bootloop by this method until I flashed by loosing data
omegagt said:
I did get a bootloop by this method until I flashed by loosing data
Click to expand...
Click to collapse
your gnex must be unlock to do this flashing process, maybe that's why you get the bootloop
banditnich said:
your gnex must be unlock to do this flashing process, maybe that's why you get the bootloop
Click to expand...
Click to collapse
I have updated my original post with this info. Thanks...
theillustratedlife said:
Color me suspicious, but I bet there's a good reason that the -w is there...
Click to expand...
Click to collapse
Got bootloop so I did full wipe and lost all data but all works fine.
omegagt said:
I did get a bootloop by this method until I flashed by loosing data
Click to expand...
Click to collapse
Same.
banditnich said:
your gnex must be unlock to do this flashing process, maybe that's why you get the bootloop
Click to expand...
Click to collapse
My GNex hasn't even been carrier locked(they don't do that in Belgium) and my bootloader has been unlocked since I got this phone.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
sui785 said:
Got bootloop so I did full wipe and lost all data but all works fine.
Same.
My GNex hasn't even been carrier locked(they don't do that in Belgium) and my bootloader has been unlocked since I got this phone.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Unlock refers to the bootloader not to carrier locking.
banditnich said:
flash successful without losing data.. but camera lag still exist on my gnex, and vitamio got multiple crash after rebooting. Anybody got the same experience?
Click to expand...
Click to collapse
Mine is still lagging when screen rotates, but if you deactivate screen rotation it works just fine.
I updated my UNLOCKED takju like this, and it seems to work ok:
- Download and unpack takju-jwr66v-factory-c2ef855e.tgz to some folder (gives you a subfolder called takju-jwr66v)
- Unpack file image-takju-jwr66v.zip (found in folder above, gives you files boot.img, recovery.img, system.img ..)
- Connect phone, make sure to activate debugging first
- Check with command adb devices , this should show you an id for your phone
Something like this:
List of devices attached
0149C25E0A011009 device
Go to folder takju-jwr66v and issue commands below
- fastboot flash bootloader bootloader-maguro-primemd04.img
- fastboot reboot-bootloader
- fastboot flash radio radio-maguro-i9250xxlj1.img
- fastboot reboot-bootloader
Go to folder image-takju-jwr66v
- fastboot flash boot boot.img
- fastboot flash recovery recovery.img
- fastboot flash system system.img
- fastboot reboot
DO NOT flash userdata.img !!
Gryph Lionheart said:
Mine is still lagging when screen rotates, but if you deactivate screen rotation it works just fine.
Click to expand...
Click to collapse
So I'm not the only one with the lagging camera bug, well camera work fine too with screen rotation disabled on 4.2.2.
Camera bug supposed to be fix in 4.3... maybe must do clean flash will do the trick...
But I'm too lazy to do backup and restore all apps and data on my phone right now, and already used to using another camera apps lately so the bug doesn't bother me that much to do clean flash all over again.
banditnich said:
So I'm not the only one with the lagging camera bug, well camera work fine too with screen rotation disabled on 4.2.2.
Camera bug supposed to be fix in 4.3... maybe must do clean flash will do the trick...
But I'm too lazy to do backup and restore all apps and data on my phone right now, and already used to using another camera apps lately so the bug doesn't bother me that much to do clean flash all over again.
Click to expand...
Click to collapse
Everything is working fine for me. No bugs.
This isn't working for me.
I typed in adb reboot bootloader to get into fast boot.
Then I ran the flash-all.bat file and it said "AdbWinApi.dll" not found. After adding this .dll to the folder a command shell opens with "waiting for device". Already turned on USB debugging and connected it to PC.
One issue though is that even though USB debugging is on, I can still connect to the phone as a media device and see all my files. I think you're not supposed to be able to access the phone's file while USB debugging is on.
So basically all the bat file does is has it stuck on "waiting for device." Although in fastboot if I type in "fastboot devices" it shows something like "X57U31581759 fastboot".
------------- Update ------------
So after watching a few youtube videos I found the problem: bad original instructions.
First the phone is to be on ANDROID, connected to the computer with USB debugging on. You can check to see if the device is connected using: adb devices
Then click the .bat file and it'll say "waiting for devices". Then I use another command shell and typed in : adb reboot bootloader to get into fastboot. This makes the .bat file work successfully.
If you start the procedure already rebooted into fastboot like steps 6 & 7 suggests, you'll be stuck on "waiting for devices" all day. Basically step 7 should be done before step 6.
Something wrong then, because I use flash-all.sh directly from fastboot, never had such an issue.
beekay201 said:
Something wrong then, because I use flash-all.sh directly from fastboot, never had such an issue.
Click to expand...
Click to collapse
Mine too, never had such issue. The flash all bat file executed from fastboot and its working flawlessly.
Sent from my Galaxy Nexus using Tapatalk 4
Didn't work for me either... Got bootloop... I had to wipe everything.
Hi all.
Here Android N for Swift
Needed files here -> https://secure.wlfx.tech
Latest = DP2
Manual:
Unlock bootloader
Install TWRP
Install OEM
Download OEM oem.img
Enter commands into fastboot
Code:
fastboot -i 0x2970 erase oem
Code:
fastboot -i 0x2970 flash oem oem.img
Download files from here (Only System and Boot)
Flash files
Code:
fastboot flash boot boot.img
Code:
fastboot flash system system.img
Reboot into TWRP
Make wipe data & wipe cache
Reboot phone
All works fine.
Sorry for my bad english and russian site server.
FindYanot said:
Hi all.
Here Android N for Swift
Needed files here -> https://secure.wlfx.tech/ANDROIDN
Manual:
Wipe data
Bot into fastboot
Use this commands:
fastboot flash boot boot.img
fastboot flash oem oem.img
fastboot flash system system.img
All works fine.
Sorry for my bad english and russian site server.
Click to expand...
Click to collapse
IFlashed. Works fine so far. Gapps are included in preview. Many thanks
FindYanot said:
Hi all.
Here Android N for Swift
Needed files here -> https://secure.wlfx.tech
Manual:
Wipe data
Bot into fastboot
Use this commands:
fastboot flash boot boot.img
fastboot flash oem oem.img
fastboot flash system system.img
All works fine.
Sorry for my bad english and russian site server.
Click to expand...
Click to collapse
Just curious. Does it have root? I am going to flash if in an hour or 2
---------- Post added at 05:55 AM ---------- Previous post was at 05:33 AM ----------
yasteellutch said:
Just curious. Does it have root? I am going to flash if in an hour or 2
Click to expand...
Click to collapse
Does it have OTA?
---------- Post added at 06:32 AM ---------- Previous post was at 05:55 AM ----------
yasteellutch said:
Just curious. Does it have root? I am going to flash if in an hour or 2
---------- Post added at 05:55 AM ---------- Previous post was at 05:33 AM ----------
Does it have OTA?
Click to expand...
Click to collapse
I am having an issue flashing. I flash using TWRP and when I reboot it says "No OS Installed". Also when I tried via fastboot. Is there any thing I am missing?
No root and OTA.
Before flashing via fastboot wipe data through twrp.
mermigas said:
No root and OTA.
Before flashing via fastboot wipe data through twrp.
Click to expand...
Click to collapse
Could you upload a screenshot?
mermigas said:
No root and OTA.
Before flashing via fastboot wipe data through twrp.
Click to expand...
Click to collapse
I did exactly that and still stuck in boot
http://4pda.ru/forum/index.php?showtopic=730213&st=120#entry47858392
Use Google translate to see instructions
Phew! some development on the Crackling!
:good:
Very impressed... TWRP method didn't wrk, fastboot worked fine! thankyou for bringing it here too, my Russian is non existent
My 1st impressions:
Very good, I haven't encountered any major issues..... I'll keep testing
Well, I just installed on my trusty Wileyfox Swift.
Overall I'm impressed, however the sensors are not working- gyro/ accelerometer/ proximity. There is some conflict with libraries when starting a game.
With a few more updates (fingers crossed) I can see myself using it as a daily driver
Everything else works and works really well. The phone seems a lot faster, the SDcard was formatted (haven't tested using an app from it but games are out of the question anyway), dual-window will be neat and is fine at the moment.
There is a lot to like here with few issues.
PS: After reading a bit from the older threads on XDA and from 4pda.ru , it seems the sensor issue is connected to the bridge to enable Android One roms with FindYanot's oem image on our crackling. Really impressive thus far. I wonder if we can flash General Mobile 4G firmware with QFIL?
I've tried this firmware on my phone and I'd like to share both experience and expressions.
Main laptop is MacBook Air, so it was quite hard to find working fastboot, adb ot GUI utilities.
Finally, I've installed them with command:
Code:
bash <(curl -s https://raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)
Then I tried to unlock the bootloader and flash images:
Code:
Sergeys-MacBook-Air:tools cleversokol$ adb devices
List of devices attached
adb server is out of date. killing...
adb I 4550 408520 usb_osx.cpp:259] Found vid=2970 pid=2282 serial=bf2ecad9
adb I 4550 408520 usb_osx.cpp:259]
* daemon started successfully *
bf2ecad9 unauthorized
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
As you can see, I had failed unlocking the bootloader and I did not install TWRP. Also, without TWRP I had not done wipe.
Code:
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.002s
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (18457 KB)...
OKAY [ 0.667s]
writing 'boot'...
OKAY [ 1.835s]
finished. total time: 2.502s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash oem oem.img
target reported max download size of 268435456 bytes
sending 'oem' (6128 KB)...
OKAY [ 0.224s]
writing 'oem'...
OKAY [ 0.734s]
finished. total time: 0.958s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 1.131s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.011s]
writing 'system'...
OKAY [ 21.393s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.789s]
writing 'system'...
OKAY [ 20.547s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.854s]
writing 'system'...
OKAY [ 20.591s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.522s]
writing 'system'...
OKAY [ 20.518s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.106s]
writing 'system'...
OKAY [ 21.263s]
sending sparse 'system' (23028 KB)...
OKAY [ 0.978s]
writing 'system'...
OKAY [ 1.729s]
finished. total time: 165.433s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.001s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
< waiting for any device >
After flashing this three images I got a brick. Phone showed Wileyfox logo once and turned off. After ejecting/inserting battery, it responsed (once) to Power button, but showed only logo and turned off again.
Eject/insert battery again and pressing Power + VolDown took me to some menu. From it I've reached fastboot menu.
With windows-laptop and WileyFox Tool utility I pressed Check bootloader status button. Phone restarted and I got Android N boot animation. Then restarted again and finally I'm in Android N First Setup Utility.
Working:
— screen, touchscreen, brightness ajustment (manual)
— mic, speaker
— charging
— GPS
— 4G
— Wi-Fi
— camera (video does not work)
— night mode
— multi-window mode
Not working:
— sensors
— some apps show library mismatch
Also, Power + VolDown button now does not take me to recovery menu. It shows android with red exclamation point. I think it's not right.
cleversokol said:
I've tried this firmware on my phone and I'd like to share both experience and expressions.
Main laptop is MacBook Air, so it was quite hard to find working fastboot, adb ot GUI utilities.
Finally, I've installed them with command:
Code:
bash <(curl -s https://raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)
Then I tried to unlock the bootloader and flash images:
Code:
Sergeys-MacBook-Air:tools cleversokol$ adb devices
List of devices attached
adb server is out of date. killing...
adb I 4550 408520 usb_osx.cpp:259] Found vid=2970 pid=2282 serial=bf2ecad9
adb I 4550 408520 usb_osx.cpp:259]
* daemon started successfully *
bf2ecad9 unauthorized
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
As you can see, I had failed unlocking the bootloader and I did not install TWRP. Also, without TWRP I had not done wipe.
Code:
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.002s
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (18457 KB)...
OKAY [ 0.667s]
writing 'boot'...
OKAY [ 1.835s]
finished. total time: 2.502s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash oem oem.img
target reported max download size of 268435456 bytes
sending 'oem' (6128 KB)...
OKAY [ 0.224s]
writing 'oem'...
OKAY [ 0.734s]
finished. total time: 0.958s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 1.131s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.011s]
writing 'system'...
OKAY [ 21.393s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.789s]
writing 'system'...
OKAY [ 20.547s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.854s]
writing 'system'...
OKAY [ 20.591s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.522s]
writing 'system'...
OKAY [ 20.518s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.106s]
writing 'system'...
OKAY [ 21.263s]
sending sparse 'system' (23028 KB)...
OKAY [ 0.978s]
writing 'system'...
OKAY [ 1.729s]
finished. total time: 165.433s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.001s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
< waiting for any device >
After flashing this three images I got a brick. Phone showed Wileyfox logo once and turned off. After ejecting/inserting battery, it responsed (once) to Power button, but showed only logo and turned off again.
Eject/insert battery again and pressing Power + VolDown took me to some menu. From it I've reached fastboot menu.
With windows-laptop and WileyFox Tool utility I pressed Check bootloader status button. Phone restarted and I got Android N boot animation. Then restarted again and finally I'm in Android N First Setup Utility.
Working:
— screen, touchscreen, brightness ajustment (manual)
— mic, speaker
— charging
— GPS
— 4G
— Wi-Fi
— camera (video does not work)
— night mode
— multi-window mode
Not working:
— sensors
— some apps show library mismatch
Also, Power + VolDown button now does not take me to recovery menu. It shows android with red exclamation point. I think it's not right.
Click to expand...
Click to collapse
I've had the opposite experience. Fastboot works without fail on Mac and Linux. Windows- not so much with the Swift.
Flash TWRP manually - fastboot flash recovery your_recovery_image.img (replace with the file name for TWRP)
You've just installed the patched oem.img (to allow code name "seed" images) along with boot and system. Can't boot to recovery if you don't have one
Steer away from flashing other files from the Android One stock image (it will be even messier hardbrick and you would have to follow the instructions from the other thread).
If you want to return to stock COS, follow the instructions from these awesome people : http://forum.cyanogenmod.org/topic/118287-manual-flashing-of-stock-cyanogenos/
PS: For some reason, unlocking the bootloader for me worked with: fastboot oem unlock-go
but not with:
fastboot -i 0x2970 oem unlock-go
Locking with: fastboot oem lock-go , worked as expected
Can I use this TWRP? I did not found Wileyfox Swift among supported devices.
cleversokol said:
Can I use this TWRP? I did not found Wileyfox Swift among supported devices.
Click to expand...
Click to collapse
I believe this is the one I've used.
In case the Windows tool for Wileyfox works for you (I'm missing some C# utilities on mine and can't deal with it atm), you can add TWRP from there as well.
PS: I used it only to install initially this preview. I haven't used it after.
Sucessfully installed TWRP3.0 (CM13-nightly-recovery did not work for me. Keep getting image of Android with red exclamation mark), wiped cache, data and installed CM13-nightly + GAPPS Mini. Booted into CM, did basic setup. After that I wanted to re-lock the bootloader.
With
Code:
fastboot oem lock-go
it worked, but after this command I got brick-phone again.
Only replacing the battery + re-unlocking the device helped to restore it.
Is there a way to keep device working with locked bootloader?
Lock the bootloader only if you'll be using stock signed images of CyanogenOS. That is in case you will have to return the device due to hardware fault- dead pixels, non functioning microphones/ speakers, etc. Another reason as of why you might want to relock, is to ensure that you'll be using CyanogenOS recovery and no problems with future OTAs (no guarantee there as encrypted devices had problems with first official update but things are looking nice for future official OTAs).
If you want to use custom recovery- TWRP/CMRecovery by itself or along with CyanogenMod13 or any other custom ROM- do not lock the bootloader.
These are your options Keep the bootloader unlocked unless you have the need/ desire to return it to true stock.
I tried to install it again and it doesn't work. I flashed stock and unlocked my bootloader. I managed to flash OEM and BOOT but it doesn't want to flash the system partition at all. I tried everything. I tried 4pda method too. Am I missing something?
yasteellutch said:
I tried to install it again and it doesn't work. I flashed stock and unlocked my bootloader. I managed to flash OEM and BOOT but it doesn't want to flash the system partition at all. I tried everything. I tried 4pda method too. Am I missing something?
Click to expand...
Click to collapse
System img is big and post propably your fastboot installer cannot handle it.
Try this fastboot installer
http://forum.xda-developers.com/showthread.php?t=2588979
This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio
---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------
yasteellutch said:
This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio
Click to expand...
Click to collapse
It keeps on saying sending sparse system img(0kb)
yasteellutch said:
This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio
---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------
It keeps on saying sending sparse system img(0kb)
Click to expand...
Click to collapse
Just try this
http://androidhost.org/P2XKs
unzip to your root directory - copy Android N images to this directory and give it a try.
mermigas said:
Just try this
http://androidhost.org/P2XKs
unzip to your root directory - copy Android N images to this directory and give it a try.
Click to expand...
Click to collapse
This is what I get
Okay, I've seen similar problems to mine but none of the suggested solutions seem to work out the problem. This seems to be the recommended solution, but it's not getting me anywhere:
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
My bootloader is unlocked. I unlocked it the second I got the phone to save pain down the road. I've now hit the fork. It's an unlocked phone, not Verizon, I'm not sure what the original carrier was, it was second-hand and under no warranty. I'm on Android 10 Marlin, I updated it to the latest about a month ago. I got up to do some laundry last night and came back to a spontaneously dead phone. For detail, I was transferring a movie to my phone via USB to internal storage so I could watch it later. No idea what happened while I was up, but the phone was in the exact same position as when I left. Developer options were on, USB debugging was on.
What I have now is this: It will enter fastboot. When I prompt it to boot to recovery, it shuts down, or it will go to the unlocked bootloader warning screen, allow me to pause/continue booting, at which point it will either go directly to black, or briefly show the Google bootloader and then shut off. When I leave it on a charge, either trickle or full, it will sometimes loop through the unlocked bootloader warning, flicking that screen on and off, but sometimes it's just off. I never see the charging battery screen. I've left it to charge for hours.
Sometimes windows acknowledges a USB device is connected and that it's android, but at no point can I access storage. When working through a command line prompt, acknowledges that the device is there, but trying to flash anything fails immediately. Here is a sample of some of my results.
When trying the flash-all solution:
PHP:
Sending 'bootloader_b' (32480 KB) OKAY [ 1.779s]
Writing 'bootloader_b' FAILED (remote: 'Verify bootloader image failed on production device.')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.040s]
Finished. Total time: 0.044s
The device goes black. I'll bring it back up to fastboot and the command line spits this out:
PHP:
< waiting for any device >
Sending 'radio_b' (57156 KB) OKAY [ 3.785s]
Writing 'radio_b' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.199s]
Finished. Total time: 0.207s
Using fastboot to try and boot factory bootloader, it says it's worked but then the phone again just goes to black and does nothing:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot boot bootloader-marlin-8996-012001-1908071822.img
< waiting for any device >
creating boot image...
creating boot image - 33261568 bytes
Sending 'boot.img' (32482 KB) OKAY [ 2.100s]
Booting OKAY [ 0.531s]
Finished. Total time: 2.944s
Flashing that factory bootloader, seems successful, again, back to black screen and nothing until going back to fastboot:
PHP:
>> PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot boot bootloader-marlin-8996-012001-1908071822.img
>> < waiting for any device >
>> creating boot image...
>> creating boot image - 33261568 bytes
>> Sending 'boot.img' (32482 KB) OKAY [ 2.100s]
>> Booting OKAY [ 0.531s]
>> Finished. Total time: 2.944s
And finally, trying to push an update image over fastboot:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot update image-marlin-qp1a.191005.007.a3.zip
--------------------------------------------
Bootloader Version...: N/A
Baseband Version.....: N/A
Serial Number........: HT6AD0202367
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.044s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'N/A'.
Update requires '8996-012001-1908071822'.
fastboot: error: requirements not met!
I am wondering if locking the bootloader would give this thing what it wants and let me boot into recovery, but I have a terrible feeling it would just further lock me out of saving this phone. Does anyone have any insight? Is this a shot motherboard? Sorry, I know my problem has a ton of commonalities with a lot of other people's but it seems for all my searching, reading and Googling that it's idiosyncratic to the point of every solution not working for me. Thank you so much.
Edit: For interest, I just saw the screen throw up an odd block of static, for lack of a better term. In the bottom right corner, it took up a little more than 1/4 of the screen. It looked lik there was cut off text at the top, too little showing to read. It disappeared before I could take a picture with a spare phone. It lasted maybe 5 seconds and then it was gone. It's on USB charge, not sitting on fastboot right now.
ekjean said:
Okay, I've seen similar problems to mine but none of the suggested solutions seem to work out the problem. This seems to be the recommended solution, but it's not getting me anywhere:
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
My bootloader is unlocked. I unlocked it the second I got the phone to save pain down the road. I've now hit the fork. It's an unlocked phone, not Verizon, I'm not sure what the original carrier was, it was second-hand and under no warranty. I'm on Android 10 Marlin, I updated it to the latest about a month ago. I got up to do some laundry last night and came back to a spontaneously dead phone. For detail, I was transferring a movie to my phone via USB to internal storage so I could watch it later. No idea what happened while I was up, but the phone was in the exact same position as when I left. Developer options were on, USB debugging was on.
What I have now is this: It will enter fastboot. When I prompt it to boot to recovery, it shuts down, or it will go to the unlocked bootloader warning screen, allow me to pause/continue booting, at which point it will either go directly to black, or briefly show the Google bootloader and then shut off. When I leave it on a charge, either trickle or full, it will sometimes loop through the unlocked bootloader warning, flicking that screen on and off, but sometimes it's just off. I never see the charging battery screen. I've left it to charge for hours.
Sometimes windows acknowledges a USB device is connected and that it's android, but at no point can I access storage. When working through a command line prompt, acknowledges that the device is there, but trying to flash anything fails immediately. Here is a sample of some of my results.
When trying the flash-all solution:
PHP:
Sending 'bootloader_b' (32480 KB) OKAY [ 1.779s]
Writing 'bootloader_b' FAILED (remote: 'Verify bootloader image failed on production device.')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.040s]
Finished. Total time: 0.044s
The device goes black. I'll bring it back up to fastboot and the command line spits this out:
PHP:
< waiting for any device >
Sending 'radio_b' (57156 KB) OKAY [ 3.785s]
Writing 'radio_b' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.199s]
Finished. Total time: 0.207s
Using fastboot to try and boot factory bootloader, it says it's worked but then the phone again just goes to black and does nothing:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot boot bootloader-marlin-8996-012001-1908071822.img
< waiting for any device >
creating boot image...
creating boot image - 33261568 bytes
Sending 'boot.img' (32482 KB) OKAY [ 2.100s]
Booting OKAY [ 0.531s]
Finished. Total time: 2.944s
Flashing that factory bootloader, seems successful, again, back to black screen and nothing until going back to fastboot:
PHP:
>> PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot boot bootloader-marlin-8996-012001-1908071822.img
>> < waiting for any device >
>> creating boot image...
>> creating boot image - 33261568 bytes
>> Sending 'boot.img' (32482 KB) OKAY [ 2.100s]
>> Booting OKAY [ 0.531s]
>> Finished. Total time: 2.944s
And finally, trying to push an update image over fastboot:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot update image-marlin-qp1a.191005.007.a3.zip
--------------------------------------------
Bootloader Version...: N/A
Baseband Version.....: N/A
Serial Number........: HT6AD0202367
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.044s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'N/A'.
Update requires '8996-012001-1908071822'.
fastboot: error: requirements not met!
I am wondering if locking the bootloader would give this thing what it wants and let me boot into recovery, but I have a terrible feeling it would just further lock me out of saving this phone. Does anyone have any insight? Is this a shot motherboard? Sorry, I know my problem has a ton of commonalities with a lot of other people's but it seems for all my searching, reading and Googling that it's idiosyncratic to the point of every solution not working for me. Thank you so much.
Edit: For interest, I just saw the screen throw up an odd block of static, for lack of a better term. In the bottom right corner, it took up a little more than 1/4 of the screen. It looked lik there was cut off text at the top, too little showing to read. It disappeared before I could take a picture with a spare phone. It lasted maybe 5 seconds and then it was gone. It's on USB charge, not sitting on fastboot right now.
Click to expand...
Click to collapse
First, do not repeat do not lock your boot loader.
Second, try this:
- Make sure you have the latest SDK Platform-tools installed on your computer r29.0.5.
There is a link for it in the guide below (Prerequisites c.).
- Make sure you plug the USB into a non charging USB port.
- Extract the boot.img (#6 in the guide brlow) from the Factory image you are currently using and flash it:
fastboot flash boot --slot all boot.img
or
fastboot flash boot boot.img --slot all
Guide
Homeboy76 said:
First, do not repeat do not lock your boot loader.
Second, try this:
- Make sure you have the latest SDK Platform-tools installed on your computer r29.0.5.
There is a link for it in the guide below (Prerequisites c.).
- Make sure you plug the USB into a non charging USB port.
- Extract the boot.img (#6 in the guide brlow) from the Factory image you are currently using and flash it:
fastboot flash boot --slot all boot.img
or
fastboot flash boot boot.img --slot all
Guide
Click to expand...
Click to collapse
Thank you thank you thank you for lending a hand. And for confirming that my temptation to lock the bootloader is a bad idea.
I have three ports on my laptop, I'm not sure any are non-charging. I'm selecting one that it wasn't attached to when the file transfer apparently went wrong.
Here goes nothing. I updated SDK tools last night during all this to be sure everything was kosher.
Unfortunately this was my result from all USB ports, testing both formats of the command:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.846s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.873s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 0.936s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 0.864s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.827s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.821s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.939s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3>
ekjean said:
Thank you thank you thank you for lending a hand. And for confirming that my temptation to lock the bootloader is a bad idea.
I have three ports on my laptop, I'm not sure any are non-charging. I'm selecting one that it wasn't attached to when the file transfer apparently went wrong.
Here goes nothing. I updated SDK tools last night during all this to be sure everything was kosher.
Unfortunately this was my result from all USB ports, testing both formats of the command:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.846s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.873s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 0.936s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 0.864s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.827s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.821s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.939s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3>
Click to expand...
Click to collapse
Are you using SDK Platform-tools r29.0.5?
Why? When you extract it it creates a Platform-tools folder.
Put this folder in PS C:\ so you have a
PS C:\Platform-tools folder.
Not: PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3>
That folder set up may be causing the to many links
error.
Then put the boot.img in the Platform-tools folder and do #6 in the guide.
Homeboy76 said:
Are you using SDK Platform-tools r29.0.5?
Why? When you extract it it creates a Platform-tools folder.
Put this folder in PS C:\ so you have a
PS C:\Platform-tools folder.
Not: PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3>
That folder set up may be causing the to many links
error.
Then put the boot.img in the Platform-tools folder and do #6 in the guide.
Click to expand...
Click to collapse
I was still working from the soft-bricked guide, where I had a copy of fastboot/platform tools pasted to everthing else. Not a problem at all to move Platform tools to C:/ Thank you!
I have noticed that what I have is r29.0.6. Should I roll it back? Assuming I should have the newest, I get the same result...
PHP:
PS C:\platform-tools> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 1.729s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\platform-tools> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.788s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\platform-tools>
ekjean said:
I was still working from the soft-bricked guide, where I had a copy of fastboot/platform tools pasted to everthing else. Not a problem at all to move Platform tools to C:/ Thank you!
I have noticed that what I have is r29.0.6. Should I roll it back? Assuming I should have the newest, I get the same result...
PHP:
PS C:\platform-tools> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 1.729s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\platform-tools> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.788s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\platform-tools>
Click to expand...
Click to collapse
No, do not roll back you have the latest version.
At this point I really don't know what will fix the problem but here are three long shots that might help/work:
1. Try fastboot flash boot boot.img. If that works. Do fastboot flash boot boot.img --slot other.
2. Download the latest Pixel or Pixel XL OTA image (which ever phone you have) and sideload it.
3. Do a Factory Reset. Settings => System => Advanced => Reset options => Erase all data (factory reset)
Good luck.
If none of them work, it could be a hardwear problem. Pixel/Pixel XL are failing because of age or manufacturing. I don't know which.
Homeboy76 said:
No, do not roll back you have the latest version.
At this point I really don't know what will fix the problem but hear are three long shots that might help/work:
1. Try fastboot flash boot boot.img. If that works. Do fastboot flash boot boot.img --slot other.
2. Download the latest Pixel or Pixel XL OTA image (which ever phone you have) and sideload it.
3. Do a Factory Reset. Settings => System => Advanced => Reset options => Erase all data (factory reset)
Good luck.
If none of them work, it could be a hardwear problem. Pixel/Pixel XL are failing because of age or manufacturing. I don't know which.
Click to expand...
Click to collapse
Sadly, anything that requires ADB/recovery is cut off to me, and so is anything that requires the actual OS interface, so accessing settings and factory resetting is out, and so is sideloading. All I can work from is fastboot.
The final option you had gave me another write failure. Thank you for working with me on this - this is my favorite phone I've ever had, and it may be time to eulogize it. I appreciate all you ran me through. <3
ekjean said:
Sadly, anything that requires ADB/recovery is cut off to me, and so is anything that requires the actual OS interface, so accessing settings and factory resetting is out, and so is sideloading. All I can work from is fastboot.
The final option you had gave me another write failure. Thank you for working with me on this - this is my favorite phone I've ever had, and it may be time to eulogize it. I appreciate all you ran me through. <3
Click to expand...
Click to collapse
RIP Pixel/Pixel XL!
hey bruh, try to cooling it in the freezer, my pixel xl turned on that way, give it a shot
@mateodiaz802 said:
hey bruh, try to cooling it in the freezer, my pixel xl turned on that way, give it a shot
Click to expand...
Click to collapse
Maybe I will! Did it stay on?
it will stay on the enough time to recover your data
@mateodiaz802 said:
hey bruh, try to cooling it in the freezer, my pixel xl turned on that way, give it a shot
Click to expand...
Click to collapse
I'm afraid in my case this was the death blow. Let out a few buzzes when attempting to power into fastboot, flashed a red light at the top and then nothing. She was euthanized by freezer around 5PM, 3/2/20, went quietly into that good night surrounded by friends and family at home. RIP Pixel.
did you cover the phone holes like the charging port and aux jack? I forgot to mention because I thought it was obvious
@mateodiaz802 said:
did you cover the phone holes like the charging port and aux jack? I forgot to mention because I thought it was obvious
Click to expand...
Click to collapse
I wrapped 'er in plastic wrap before putting it in. So it would've been covered. Oh well, stuff happens. Funny thing, I tried it again just to see. It started vibrating and hasn't stopped. XD
i covered the holes with tape, it's more effective, also you should try booting it with "start" optino from the bootloader
EDIT3 - Thanks everyone - fixed, the main confusion was MIUI fastboot not recognising my phone. I had previously installed Andorid Composite ADB Interface from device manager on my PC but for some reason it dissapeared.
Reinstalled from disk, used MiFlash with stock ROM below and no longer got error below. Accidentally did "Clean all and lock" but it seems like you don't have to wait 7 days again. Logged into MIUI via developer options >MIUI unlock, was able to unlock immediately from MIUI fastboot again.
Then redid everything:
Followed guide here - https://forum.xda-developers.com/t/rom-11-0-0-alioth-aliothin-arrowos-11-0-official-weekly.4279481/
Rebooted to MIUI fastboot (not Arrow Recovery fastboot)
fastboot boot twrp.img (named my twrp alpha image this)
I tried pushing twrp image to install to ramdisk (so twrp was permanent recovery) but I get error "unable to decrypt FBE device" so I skipped that (kept Arrow OS recovery)
adb push magisk-v23.0.zip /storage
installed zip, reboot
Was able too boot (got a weird lockup/restart but all good after)
Immediately recognised it was already rooted when it got to google pay setup
---------------
Trying to reset Poco F3 to stock (but keep bootloader unlocked).
I currently have ArrowOS (I can boot, but I can't root it) and ArrowOS Recovery but I think I have messed up my partitions.
Steps:
From Arrow OS Recovery > Fastboot
Running MiFlash, I am patching global unzipped fastboot from tar:
alioth_global_images_V12.5.1.0.RKHMIXM_20210517.0000.00_11.0_global
https://xiaomifirmwareupdater.com/miui/alioth/stable/V12.5.1.0.RKHMIXM/
I am getting below error, is there anything else I can do to try to restore to stock or fix partitions?
Can I sideload the firmware somehow?
EDIT - I have also tried from MIUI fastboot but it does not see my devices.
EDIT2 - It shows up as Android in device manager, if I install usb_drivers (Andorid Composite ADB interface) it fixes it so I can use MIUI fastboot now.
{
"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"
}
log file:
Code:
[6:19:58 PM ddcb8276]:MiFlash 2018.11.15.0
[6:19:58 PM ddcb8276]:Thread id:15 Thread name:ddcb8276
[6:19:58 PM ddcb8276]:image path:C:\Content\IDM\_poco_f3_setup\tgz\alioth_global_images_V12.5.1.0.RKHMIXM_20210517.0000.00_11.0_global
[6:19:58 PM ddcb8276]:env android path:"C:\MiFlash20181115\Source\ThirdParty\Google\Android"
[6:19:58 PM ddcb8276]:script :C:\Content\IDM\_poco_f3_setup\tgz\alioth_global_images_V12.5.1.0.RKHMIXM_20210517.0000.00_11.0_global\flash_all.bat
[6:19:59 PM ddcb8276]:physical Memory Usage:3846144 Byte
[6:19:59 PM ddcb8276]:start process id 12196 name cmd
[6:19:59 PM ddcb8276]:info:$fastboot -s ddcb8276 getvar product 2>&1 | findstr /r /c:"^product: *alioth" || echo Missmatching image and device
[6:19:59 PM ddcb8276]:info:product: alioth
[6:19:59 PM ddcb8276]:info:$fastboot -s ddcb8276 getvar product 2>&1 | findstr /r /c:"^product: *alioth" || exit /B 1
[6:19:59 PM ddcb8276]:info:product: alioth
[6:19:59 PM ddcb8276]:info:$if exist C:\Content\IDM\_poco_f3_setup\tgz\alioth_global_images_V12.5.1.0.RKHMIXM_20210517.0000.00_11.0_global\images\anti_version.txt (for /F "delims==" %a in (C:\Content\IDM\_poco_f3_setup\tgz\alioth_global_images_V12.5.1.0.RKHMIXM_20210517.0000.00_11.0_global\images\anti_version.txt) do (set CURRENT_ANTI_VER=%a ) )
[6:19:59 PM ddcb8276]:info:$(set CURRENT_ANTI_VER=1 )
[6:19:59 PM ddcb8276]:info:$if [1] EQU [] set CURRENT_ANTI_VER=0
[6:19:59 PM ddcb8276]:info:$for /F "tokens=2 delims=: " %i in ('fastboot -s ddcb8276 getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
[6:19:59 PM ddcb8276]:info:$if [] EQU [] set version=0
[6:19:59 PM ddcb8276]:info:$set anticheck="antirollback check pass"
[6:19:59 PM ddcb8276]:info:$if 0 GTR 1 set anticheck="Current device antirollback version is greater than this pakcage"
[6:19:59 PM ddcb8276]:info:$echo "antirollback check pass" | findstr /r /c:"pass" ||
[6:19:59 PM ddcb8276]:info:"antirollback check pass"
[6:19:59 PM ddcb8276]:info:$fastboot -s ddcb8276 erase boot_ab ||
[6:19:59 PM ddcb8276]:err:erasing 'boot_ab'...
[6:19:59 PM ddcb8276]:err:FAILED (remote: Partition doesn't exist)
[6:19:59 PM ddcb8276]:err:finished. total time: 0.001s
[6:19:59 PM ddcb8276]:info:"Erase boot_ab error"
[6:19:59 PM ddcb8276]:error:FAILED (remote: Partition doesn't exist)
[6:19:59 PM ddcb8276]:process exit.
[6:19:59 PM ddcb8276]:flashSuccess False
[6:19:59 PM ddcb8276]:isFactory False CheckCPUID False
[6:19:59 PM ddcb8276]:before:flashSuccess is False set IsUpdate:True set IsDone True
[6:19:59 PM ddcb8276]:after:flashSuccess is False set IsUpdate:false set IsDone true
I suggest flashing xiaomi.eu rom first.boot it once and after try miflash again.
try mi flash tool 2017.4.25 version u also dont need to remove arb lines in that version.
Hi @redsky0 ,
Thank you for mentioning that you succeeded getting this working,
I'm facing the same issue on my Xiaomi Mi 11, (getting an Error erasing boot_ab, partition doesn't exist)
The phone is correctly booting, and it show that the bootload is unlocked, but when I try to flash a TWRP bootloader, I'm getting an error (FAILED (remote: No such file or directory)
I tried to flash global rom and also chinese rom without success
I saw that you mentioned Android Composite ADB Interface, Should I see it as a device?
Thanks
arkontos said:
Hi @redsky0 ,
Thank you for mentioning that you succeeded getting this working,
I'm facing the same issue on my Xiaomi Mi 11, (getting an Error erasing boot_ab, partition doesn't exist)
The phone is correctly booting, and it show that the bootload is unlocked, but when I try to flash a TWRP bootloader, I'm getting an error (FAILED (remote: No such file or directory)
I tried to flash global rom and also chinese rom without success
I saw that you mentioned Android Composite ADB Interface, Should I see it as a device?
Thanks
Click to expand...
Click to collapse
I think I saw the error you are getting. Could you tell me in detail of what happened?
You have unlocked bootloader and running stock . you are trying to do TWRP through fastboot right ?
AKASHPAUL said:
I think I saw the error you are getting. Could you tell me in detail of what happened?
You have unlocked bootloader and running stock . you are trying to do TWRP through fastboot right ?
Click to expand...
Click to collapse
Thanks for the replay,
Yes, current state is as you described:
Bootloader unlocked, with stock rom,
I'm trying to run/install twrp through fastboot and couldn't work
I also tried to reflash a stock rom (saw it in some threads) using the miFlash tool, and it didn't work
arkontos said:
Thanks for the replay,
Yes, current state is as you described:
Bootloader unlocked, with stock rom,
I'm trying to run/install twrp through fastboot and couldn't work
I also tried to reflash a stock rom (saw it in some threads) using the miFlash tool, and it didn't work
Click to expand...
Click to collapse
in terminal write this - "fastboot devices"
check if your device is showing
arkontos said:
Hi @redsky0 ,
Thank you for mentioning that you succeeded getting this working,
I'm facing the same issue on my Xiaomi Mi 11, (getting an Error erasing boot_ab, partition doesn't exist)
The phone is correctly booting, and it show that the bootload is unlocked, but when I try to flash a TWRP bootloader, I'm getting an error (FAILED (remote: No such file or directory)
I tried to flash global rom and also chinese rom without success
I saw that you mentioned Android Composite ADB Interface, Should I see it as a device?
Thanks
Click to expand...
Click to collapse
If you're in MIUI fastboot (stock, i.e. not some custom OS recovery) I believe you should be able to run adb commands when connected to PC by USB.
My issue was that the Android Composite ADB Interface driver (I had previously installed) for some reason stopped working so I fixed in Device Manager (menu -> install from disk, pointed to drivers to reinstall).
For the actual issue, my approach was just to go back to stock and start again. I was able to boot to TWRP to perform root but like I mentioned, I couldn't get the TWRP custom recovery to stay permanently. The root worked though.
Thanks @redsky0 for your help
@AKASHPAUL This is what I can see from a terminal:
Code:
#> adb devices
List of devices attached
23615bcc device
#> adb reboot fastboot
#> fastboot devices
23615bcc fastboot
#> fastboot boot twrp.img
Sending 'boot.img' (129320 KB) OKAY [ 3.703s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
I also tried from a Windows, getting the same result
arkontos said:
Thanks @redsky0 for your help
@AKASHPAUL This is what I can see from a terminal:
Code:
#> adb devices
List of devices attached
23615bcc device
#> adb reboot fastboot
#> fastboot devices
23615bcc fastboot
#> fastboot boot twrp.img
Sending 'boot.img' (129320 KB) OKAY [ 3.703s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
I also tried from a Windows, getting the same result
Click to expand...
Click to collapse
don't go into fastboot from adb.
switch off the phone and press volume down + power button then try and update
AKASHPAUL said:
don't go into fastboot from adb.
switch off the phone and press volume down + power button then try and update
Click to expand...
Click to collapse
Worked!!!
Really sorry, now I feel my question was a dumb one
Many thanks @AKASHPAUL you saved my day
arkontos said:
Worked!!!
Really sorry, now I feel my question was a dumb one
Many thanks @AKASHPAUL you saved my day
Click to expand...
Click to collapse
Your question wasn't a dumb one.
It should've worked on your method too but sadly it doesn't work. I did the same mistake too. Then I booted manually to fastboot and it worked.
Cheers
AKASHPAUL said:
don't go into fastboot from adb.
switch off the phone and press volume down + power button then try and update
Click to expand...
Click to collapse
Thanks mate , saved my day , + i don't know why there's 2 types of fastboot in the device it make me confused .
arkontos said:
Thanks @redsky0 for your help
@AKASHPAUL This is what I can see from a terminal:
Code:
#> adb devices
List of devices attached
23615bcc device
#> adb reboot fastboot
#> fastboot devices
23615bcc fastboot
#> fastboot boot twrp.img
Sending 'boot.img' (129320 KB) OKAY [ 3.703s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
I also tried from a Windows, getting the same result
Click to expand...
Click to collapse
I have the same issue as u see in screenshot but iam trying this from pixel experience recovery fastboot mode
What did i do wrong ?
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
I am using a Redmi Note 8 (2021) and wanted to flash lineageOS. So I unlocked the bootloader via my mi account, booted into fastboot mode (usb-debugging was of course enabled) and tried to flash twrp to recovery using the cmd-window via platform-tools.
This didn't work because when I typed:
./fastboot flash recovery twrp.img
I got the reply:
Sending 'recovery' (65536 KB) OKAY [ 1.743s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I therefore started googling and found a threat on xda where someone had solved the problem by replacing 'recovery' with 'boot':
./fastboot flash boot twrp.img
What I got was:
Sending 'boot_a' (65536 KB) OKAY [ 1.818s]
Writing 'boot_a' OKAY [ 0.827s]
Finished. Total time: 2.681s
After that my phone was bricked. I cannot enter recovery mode anymore and even fastboot mode appears a bit different (I don't see the bunny anymore, all I see is the word 'fastboot' in orange letters on a black screen). When I enter fastboot mode, the device is detected by my computer - the only sign that still gives me an inch of hope. When I'm not in fastboot mode my phone keeps vibrating and then turning of, then suddenly it vibrates again and turns on, the logo 'redmi' appears and then it suddenly turns off again - and it just keeps repeating this procedure.
I downloaded the mi flash tool and tried to flash the Xiaomi ROM, but that didn't work either - after about five minutes of waiting I get an error. I tried different versions of MIUI but keep getting errors. When I try to flash the Xiaomi ROM via cmd-window, as suggested here ( https://www.droidwin.com/unbrick-redmi-note-8-fastboot-commands/ ) I get this:
fastboot flash xbl xbl.elf
Sending 'xbl' (3449 KB) OKAY [ 0.105s]
Writing 'xbl' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Is there anything left for me to do or should I give up and save money for a new phone? I am also wondering why the command-window keeps talking about 'boot_a'. Is there a 'boot-b' also? And should I write something onto it? When I try to boot the twrp.img by typing:
fastboot boot twrp.img
I get:
Sending 'boot.img' (65536 KB) OKAY [ 1.592s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
I would be very, very grateful for help
Norah1838 said:
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
Click to expand...
Click to collapse
Use this tool:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
First off: don't go punching in commands you don't understand.
You literally flashed an incompatible image to your boot_a.
You could try and set the active partition to b using: fastboot --set-active=b.
Other option, if you have the firmware image for your boot partition, flash that image to boot_a.
you only need to flash the original boot.img from firmware lol it's so easy