Flashing hung up on boot.img - Razer Phone 2 Questions & Answers

Hello! I've been trying to root my old razer phone 2 and have been following THIS GUIDE that seems to have gotten plenty of interaction. I've unlocked the bootloader, and have gotten to the point to install the arter97 kernel. But when I use the command fastboot flash boot_b boot.img, I get hung up on it until it either fails or kicks itself off.
"C:\adb\platform-tools>fastboot flash boot_b C:\adb\platform-tools\boot.img
Warning: skip copying boot_b image avb footer (boot_b partition size: 0, boot_b image size: 30924800).
Sending 'boot_b' (30200 KB) FAILED (remote: 'GetVar Variable Not found')
fastboot: error: Command failed"
I've gotten 'GetVar Variable Not found' and 'Too many links'
At this point, I'm not sure what I'm doing wrong. The phone is Android 9. I have all the files downloaded and in the right place. I'm using a usb 2.0 slot. The only things I haven't tried is a usb hub, which I don't have, and trying on a different computer, which would be nice to do if my 10 year old laptop didn't decide to just never turn on anymore.
Would love peoples input on how I could fix this.

Related

BQ Aquaris M10 FHD failed image upload

Hi friends,
The app recommended by BQ "MTK Tool Flash" (SP_Flash_Tool_exe_Linux_v5.1612.00.100.zip) just didn't work for me on my Debian PC. There were always some excuses. So I tried some black command-line magic with fastboot and now I'm with a bricked device.
See ubuntu-android-installation-process-for-bq-aquaris-e4-5-and-e5 link I cannot post...
The good news is, I have installed the TWRP (twrp-3.1.1-0-freezerfhd.img) before I shot myself in the toe. So power + volume up gives me the comforting bluish screen of TWRP.
Question is, how can I bring the lovely device back to life? I wanted to flash official Android on it (which failed - 2.3.0_20170405-1553_bq_aquaris_m10_FHD_-FW.zip) and I'd like to complete that, but if it's a no go, I can go back to Ubuntu.
I have tried installing the image zip from twrp, but it said the image has invalid zip file format!
Thanks a lot for your help
Rob
failures
I've been struggling with this one. So I can switch to the bootloader mode and run fastboot commands. However, when I try to flash the system image I get some funny error:
Code:
sudo fastboot flash system ./system.img
target reported max download size of 134217728 bytes
erasing 'system'...
FAILED (remote: unknown command)
finished. total time: 0.002s
With the flash tool (after fixing all it's complaints) I'm stuck with a timeout on detecting the USB port (while fastboot works just fine)
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
And with TWRP as mentioned earlier:
Code:
Invalid zip file format
I read the stock rom can be adjusted somehow to allow TWRP to flash it but I'm quite like what...? Android kitchen doesn't list my device as supported.
progress
Aha! This got us further:
Code:
sudo fastboot flash system -u -S 1G ./system.img
Which means do not erase the partition upfront, and sparse the file at max 1 GB.
Code:
sudo fastboot flash userdata -u -S 1G ./userdata.img
sudo fastboot flash boot -u -S 1G ./boot.img
sudo fastboot reboot
Now device is "powered by ubuntu" and stuck there... not sure what's happening
S now I tried flashing some more exotic partitions and the device is completely dead. I hope BQ can help...
undead
Wow, so BQ contacted me right away with a hard reset procedure. The key bit of information I must have overlooked somewhere is that for the flash tool to detect the device, the device must be plugged in while it's off and while the tool is waiting. We're now "powered by android" and system is ready to use. Oh my... thanks BQ

TF701T - getting FAILED (remote: Unsupport Flash Unsparse System Image.)

I've just purchased an Asus Transformer TF701T from a friend at work. It was working perfectly and I was able to restore all my apps as I previously used a Nexus 2013. The pad was running with an older version of Android 4.4.2 so I decided Id like to flash the device to get a newer version but I was unable to unlock it via the Asus unlock tool as I when I ran it, I was getting an "unknown error occurred which may be a network connection issue. Please wait and try again later" message. I tried all the usual fixes, removing my Google account, unlocking the 2 factor authentication etc, but the same error persisted. I then read a few posts and hit upon the idea to flash the firmware via the Bootloader and followed the various guides and got things setup this evening. I am using the Minimal ADB and Fastboot drivers.
So I can get the tablet to the bootloader screen without issue, with the 3 icons RCK, Android and Wipe Data and it responds fine to fastboot commands, even reboot works. So I entered the following after getting the UL-K00C-WW-11.4.1.30-user.zip firmware 11.4.1.30 from the Asus website (it used to have WW 11.4.1.17) and unpacked to my ADB folder. These are the commands I used which are all successful:-
fastboot erase system, fastboot erase recovery, fastboot erase userdata, fastboot erase boot, fastboot erase misc, fastboot erase cache. So far so good!
However, the penultimate command fastboot -i 0x0B05 system blob results in the error in the subject (exact copy of the output below)
Now the tablet just comes up with the Asus logo and in red "Unrecoverable bootloader error (0x00000000)." and only changes if I force it into the bootloader again. I can move between the 3 options ok.
Is there any way of recovering from this? is the problem that the tablet is still locked? I'd really appreciate some help if possible, thanks in advance Martin
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash system blob
target reported max download size of 643825664 bytes
erasing 'system'...
OKAY [ 1.021s]
sending 'system' (1781 KB)...
OKAY [ 0.266s]
writing 'system'...
FAILED (remote: Unsupport Flash Unsparse System Image.)
finished. total time: 1.323s
I've managed to resolve it for anyone else that might read this....
Follow the guide here https://forum.xda-developers.com/tr...f701t-nvflash-unbrick-solutiontested-t3742848 and use the NvFlash TF701T Unbrick tool, you need to do a bit of prep but it worked for me
Big thanks to Mr.Bin for this fix.
Cheers and good luck
Martin
martinnut said:
I've just purchased an Asus Transformer TF701T from a friend at work. It was working perfectly and I was able to restore all my apps as I previously used a Nexus 2013. The pad was running with an older version of Android 4.4.2 so I decided Id like to flash the device to get a newer version but I was unable to unlock it via the Asus unlock tool as I when I ran it, I was getting an "unknown error occurred which may be a network connection issue. Please wait and try again later" message. I tried all the usual fixes, removing my Google account, unlocking the 2 factor authentication etc, but the same error persisted. I then read a few posts and hit upon the idea to flash the firmware via the Bootloader and followed the various guides and got things setup this evening. I am using the Minimal ADB and Fastboot drivers.
So I can get the tablet to the bootloader screen without issue, with the 3 icons RCK, Android and Wipe Data and it responds fine to fastboot commands, even reboot works. So I entered the following after getting the UL-K00C-WW-11.4.1.30-user.zip firmware 11.4.1.30 from the Asus website (it used to have WW 11.4.1.17) and unpacked to my ADB folder. These are the commands I used which are all successful:-
fastboot erase system, fastboot erase recovery, fastboot erase userdata, fastboot erase boot, fastboot erase misc, fastboot erase cache. So far so good!
However, the penultimate command fastboot -i 0x0B05 system blob results in the error in the subject (exact copy of the output below)
Now the tablet just comes up with the Asus logo and in red "Unrecoverable bootloader error (0x00000000)." and only changes if I force it into the bootloader again. I can move between the 3 options ok.
Is there any way of recovering from this? is the problem that the tablet is still locked? I'd really appreciate some help if possible, thanks in advance Martin
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash system blob
target reported max download size of 643825664 bytes
erasing 'system'...
OKAY [ 1.021s]
sending 'system' (1781 KB)...
OKAY [ 0.266s]
writing 'system'...
FAILED (remote: Unsupport Flash Unsparse System Image.)
finished. total time: 1.323s
Click to expand...
Click to collapse

Problem with on-boot password led to partial brick, need help [r13]

Hey guys,
I dun goofed when trying to do a routine backup.
First off, I'm trying to recover this without wiping, as I have some 2FA apps and other things that have secret keys that can't be recovered unless I can decrypt the darned thing
Rebooted into TWRP in order to do an image backup before I upgrade from arter97's kernel r13 to r14.
When TWRP comes up, it surprises me with a password prompt (instead of pattern unlock which is what it should be)
Reboot to system to remove encryption and then fix the password issue, greeted by "To start Android, enter your password" prompt, again instead of pattern unlock
Tried the numbers-to-pattern trick, no luck. Basically locked out of the phone now
Booted back into TWRP, while looking around for other options, accidentally chose "Slot A" which has gotten me stuck back on the old recovery
fastboot commands no longer work properly (see below)
Sometimes the commands hang, and I need to ctrl+c and re-run. I get very inconsistent results, as you'll see below
Code:
D:\adb>fastboot.exe boot twrp-3.2.1-0-cheryl.img
Sending 'boot.img' (23120 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
Trying to re-flash the kernel just hangs:
Code:
D:\adb>fastboot.exe flash boot arter97-kernel-r14-20200428.img
Tried switching to Windows Terminal/Powershell and got slightly different error:
Code:
PS D:\adb> .\fastboot.exe boot .\twrp-3.2.1-0-cheryl.img
Sending 'boot.img' (23120 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
PS D:\adb> .\fastboot.exe flash boot .\arter97-kernel-r14-20200428.img
Sending 'boot' (30176 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
PS D:\adb> .\fastboot.exe getvar all
getvar:all FAILED (Write to device failed (Unknown error))
Finished. Total time: 5.004s
PS D:\adb> .\fastboot.exe --set-active=a
PS D:\adb> .\fastboot.exe --set-active=b
fastboot: error: Device does not support slots
PS D:\adb> .\fastboot.exe --set-active=q
Slot q does not exist. supported slots are:
a
b
PS D:\adb> .\fastboot.exe --set-active=a
Setting current slot to 'a' FAILED (remote: 'Invalid Slot')
fastboot: error: Command failed
PS D:\adb> .\fastboot.exe --set-active=b
Setting current slot to 'b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm sure the TWRP image is still there in slot b, but I can't get it to switch back.
Update:
I tried running the `fastboot --set-active=b` on a different (older) system which did finally work and allowed me to switch back over to TWRP, but I'm still having that decryption issue.
Anyone know why the encryption would suddenly switch from pattern unlock to "password" and how I could fix it?
Edit: After doing some more research on here, it sounds like my phone may have OTA'd itself to MR3 which may be the cause for the password issue.
Got an idea that I hope will work, which is to use the factory MR2 image, and comment out the lines for wiping data. Maybe that will bring it back?

[ROM][UNOFFICIAL] LineageOS 17.1 for Xperia 10 II [OTA][SODP]

Lineage 17.1 for the Sony Xperia 10 II
Please note this is currently for the dual-sim model ONLY. When you need a single-sim variant leave a comment, so we can work an that...​
Code:
/*
* Disclaimer - your warranty may be void.
*
* I'm not responsible for bricked devices, dead OTGs or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Features
OTA updates - always delayed for 1 day (to prevent broken rollouts); when you want it immediately, checkout my GitLab pipelines
Increased volume steps to 25
Over-provisioned system image (580MiB), to allow install of OpenGApps and other stuff
Open Source (it is based on SODP, you can view all my patches and ci scripts here or here)
Package signature spoofing (needed by MicroG)
What does not work?
Stock camera app with wide and zoom cameras, you may use Open Camera to circumvent that.
Notification LED blinking - kernel driver bug (see here)
LiveDisplay
You tell me...
Download
There you have multiple options:
To get the complete package (both including the ota and imgparts; only needed for the initial setup) visit...
AndroidFileHost
GitLab (make sure to download the artifacts from the master branch)
To get ONLY the OTA package to update your system later on, visit (or open up the LineageOS Updater) ota.simonmicro.de - please note that only the last recent 14 days are accessible there.
Changelog
2021-02-28
Fixed wifi hotspot.
2020-12-18
Fixed cameras.
2020-11-27
Fixed ADB security.
2020-11-25
Added SELinux support.
2020-11-20
Added OpenGApps support.
2020-11-17
Initial release.
How to install your system
The following guide assumes, you have setup adb and fastboot already (make sure to always use the latest version of the toolkit, otherwise you'll may get problems during flashing) - for that take a look into the internet. Also you should already downloaded the complete package from above!
Unlock the bootloader - a "how to" is here...
Download the oem binaries from here, make sure to use exactly that version!
Boot into the bootloader (hold "Volume up + Insert the USB cable" until led lights blue) and then update the oem partition:
Code:
fastboot flash oem_a [EXTRACTED_OEM_IMAGE_FILE]
fastboot flash oem_b [EXTRACTED_OEM_IMAGE_FILE]
Flash now the Lineage recovery partition as well as the dtbo partition (they are inside the img folder of the complete package):
Code:
fastboot flash recovery [EXTRACTED_RECOVERY_IMAGE_FILE]
fastboot flash dtbo [EXTRACTED_DTBO_IMAGE_FILE]
Disable the verity checks for now, as your new recovery violates the Sony verity profiles of the Stock ROM:
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_system vbmeta_system.img
Okay, you are now ready to boot the first time into the Lineage recovery, unplug the phone NOW!
To boot into recovery: Hold "Volume down + Power" until it vibrates...
You should now be booted into the recovery. We now clean any old data from Sonys Stock ROM - this is just to make sure you have a really clean install: Choose the "Factory reset" option.
The phone is now clean and ready to accept the new system. You now can either install just the OTA package and be done or flash every .img from the full package manually - the coice is yours. When you plan to flash the images manually, make sure to include boot, system, product, vendor, vbmeta_system, as these are normally part of the OTA update (I extracted the payload.bin to verify this!). For the latter approach you may orient yourself on my flashall.sh. I'll choose the simpler OTA-sideload approach for now.
Select "Apply update -> Apply from ADB" (now make sure the adb server runs as root - may use adb kill-server && sudo adb start-server to fix that) and execute (the OTA zip is inside the ota subdir):
Code:
adb sideload [OTA_SYSTEM_UPDATE_ZIP_FILENAME]
Something went wrong - help!
(Step 7-8) When you now see a device corrupt error
Don't panic!
You messed up the verity disable step from before - try again.
Try to switch the current boot slot (get current fastboot getvar current-slot and set new fastboot --set-active=, you can choose between a and b) and retry disableing verity disable again!
When your device fails to boot too many times (and crashes) the current slot could also get marked as corrupt. To reset that counter you'll need to reflash the boot partition - to see what is going on, try fastboot getvar all and look out for something like a unbootable flag.
(Step 9) When you get Operation not permitted during flashing
This is commonly caused by relocking and then reunlocking the bootloader (yay - buggy firmware). You'll need to relock, restore (and boot) the device with Flashtool using Sonys original ROM and start from fresh.
(Step 10) When you get the kDownloadPayloadPubKeyVerificationError error
Well, that's caused by using an other recovery than the provided one, as I use my own private keys to sign the build the recovery must also know them. Using an other recovery than the one from
the img folder of the complete package will most likely not include them (and when they do - I am in big trouble), and therefore fail. But you are in luck: It seems that the recovery writes
the data to the currently inactive slot and then fails. You could simply switch the system slot like described above!
Want to install Magisk?
Install the Magisk zip like the OTA system update by using adb sideload [MAGISK_FILE_NAME].
Want to install OpenGApps?
Make sure to use the pico-variant, as the system partition is even with over-provisioning really small (as the installer extracts some more stuff on the first boot) - then install the OpenGApps zip like the OTA system update by using adb sideload [OPENGAPPS_FILE_NAME].
Credits
As much I would like, I can't do everything by myself. A huge thank you to...
@MartinX3 for the used local_manifests and his device tree from his LineageOS organization
...the team behind @sonyxperiadev, for their great work (and their kernel sources)!
XDA:DevDB Information
LineageOS 17.1 for pdx201, ROM for the Sony Xperia 10 II
Contributors
Simonmicro, MartinX3
Source Code: https://gitlab.simonmicro.de/android/lineage/lineage-pdx201
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Sony OEM Package
Based On: AOSP
Version Information
Status: Beta
Hey,
as you guys may have already noted, I have stopped the active development phase for this LOS port a while ago. This was caused by me just not having enough time to do everything and additionally maintain a LOS port.
Today I'll upload the last maintenance build to the OTA server and mirrors. Of course I somehow included a little bug, which causes the system to complain about "an internal problem", which seem to be caused by some interaction with the OpenGApps package installer. Now, it is a feature. I'll may post one more update, if I figure this one out.
Nevertheless, I'll shut down the OTA service at 2022-06-01 (see https://status.simonmicro.de) and will then archive all project data. It was a great time to learn many (new/nasty) things about Android and how everything works. I have to say "thank you" to everyone, who supported me and was on board with this project.
See you next time,
simonmicro
-> https://forum.xda-developers.com/t/...r-xperia-10-ii-ota-sodp.4191601/post-86352693 <-
Reserved
First
At last The guide, source code looks great! Will install, check it next
hmm, i flashed everything according to the instructions, but the system still looks the same as Sjll's ROM and there is no updater in settings>system. anyone else getting this?
EDIT: nevermind, all is well, i was on the wrong slot.. : / wish we wouldn't have to deal with this, TWRP+lineage+one slot was perfect. this is not about the ROM though, it's awesome.
bamdadkhan said:
hmm, i flashed everything according to the instructions, but the system still looks the same as Sjll's ROM and there is no updater in settings>system. anyone else getting this?
EDIT: nevermind, all is well, i was on the wrong slot.. : / wish we wouldn't have to deal with this, TWRP+lineage+one slot was perfect. this is not about the ROM though, it's awesome.
Click to expand...
Click to collapse
- you made my day. Now I know which ROM you used before
No serious: Did you follow the guide step-by-step or did you altered it in some way (maybe forgot to reboot after switching slots) - as it should normally flash both slots (when using ota), even when not you should be at least on the right slot after flashing?!
Simonmicro said:
- you made my day. Now I know which ROM you used before
No serious: Did you follow the guide step-by-step or did you altered it in some way (maybe forgot to reboot after switching slots) - as it should normally flash both slots (when using ota), even when not you should be at least on the right slot after flashing?!
Click to expand...
Click to collapse
lol it's easy to know when the ROM in question is the only available aside from yours xd
seriously: i followed all the steps to the letter. flashed the SW binaries on both oem_a and oem_b. really everything.
i have a theory though. i originally flashed your ROM when 'side b' had previously been set active. if this persists across reboots - i really don't know, this whole 'dual ROM' concept is new to me - then there's your answer: the lineage install script probably has a command to use 'side a' for flashing. is completed successfully, but then i went ahead and booted the 'side b', which still had Sjll's ROM on it.
bamdadkhan said:
lol it's easy to know when the ROM in question is the only available aside from yours xd
seriously: i followed all the steps to the letter. flashed the SW binaries on both oem_a and oem_b. really everything.
i have a theory though. i originally flashed your ROM when 'side b' had previously been set active. if this persists across reboots - i really don't know, this whole 'dual ROM' concept is new to me - then there's your answer: the lineage install script probably has a command to use 'side a' for flashing. is completed successfully, but then i went ahead and booted the 'side b', which still had Sjll's ROM on it.
Click to expand...
Click to collapse
Well, I also tested my guide to the letter - and there i saw on my device screen that the ota flashed on both partitions. Did you also used my recovery? When you did: Lets see if others also have that problem... :angel:
Simonmicro said:
Well, I also tested my guide to the letter - and there i saw on my device screen that the ota flashed on both partitions. Did you also used my recovery? When you did: Lets see if others also have that problem... :angel:
Click to expand...
Click to collapse
Great job, thank you. Can I install NikGapp? Or does it also cause bootlaps?
Thapsus-cz said:
Great job, thank you. Can I install NikGapp? Or does it also cause bootlaps?
Click to expand...
Click to collapse
On their website:
Code:
OpenGapps Team (for base package and providing Open Gapps)
Therefore is a really good chance that the installer has the same problems like OpenGApps - but I can't say that for sure, I guess you'll need to try it out (when is does bootloop / never starts, please send me a adb logcat -b all for further diagnostics).
Done till the step 9.
Tried the second way first (flashing images). Please see the log for this below.. Then tried OTA way. OTA way did with 0 exit status (it sent files) but when I boot device it writes "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds". How to fix?
Also when I load into recovery it writes this:
E: Failed to bind mount /mnt/staging/mulated/media/0 to /storage/emulated: NO such file or directory.
E: emulated failed to bind mount /mnt/stagingemulated/media/0 on /storage/meulated: No such file or directory.
Click to expand...
Click to collapse
See full log for flashing images:
sudo fastboot flash boot boot.img
sudo fastboot flash system system.img
sudo fastboot flash product product.img
sudo fastboot flash vendor vendor.img
sudo fastboot flash vbmeta_system vbmeta_system.img
[sudo] пароль для :
Sending 'boot_b' (65536 KB) OKAY [ 2.441s]
Writing 'boot_b' OKAY [ 0.358s]
Finished. Total time: 2.812s
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.722s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'product' (432072 KB) OKAY [ 16.440s]
Writing 'product' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vendor' (48084 KB) OKAY [ 1.725s]
Writing 'vendor' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vbmeta_system' (4 KB) OKAY [ 0.005s]
Writing 'vbmeta_system' OKAY [ 0.003s]
Finished. Total time: 0.016s
❯ sudo fastboot flash boot boot.img
sudo fastboot flash system system.img
sudo fastboot flash product product.img
sudo fastboot flash vendor vendor.img
sudo fastboot flash vbmeta_system vbmeta_system.img
❯ sudo fastboot flash boot boot.img
sudo fastboot flash dtbo dtbo.img
sudo fastboot flash product product.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash super_empty super_empty.img
sudo fastboot flash system system.img
sudo fastboot flash vbmeta vbmeta.img
sudo fastboot flash vbmeta_system vbmeta_system.img
sudo fastboot flash vendor vendor.img
Sending 'boot_b' (65536 KB) OKAY [ 2.438s]
Writing 'boot_b' OKAY [ 0.378s]
Finished. Total time: 2.831s
Sending 'dtbo' (8192 KB) OKAY [ 0.302s]
Writing 'dtbo' OKAY [ 0.046s]
Finished. Total time: 0.357s
Sending 'product' (432072 KB) OKAY [ 16.212s]
Writing 'product' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 3.699s]
Writing 'recovery' OKAY [ 0.557s]
Finished. Total time: 4.265s
Sending 'super_empty' (4 KB) OKAY [ 0.011s]
Writing 'super_empty' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.755s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vbmeta' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta' OKAY [ 0.003s]
Finished. Total time: 0.021s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_system' OKAY [ 0.004s]
Finished. Total time: 0.014s
Sending 'vendor' (48084 KB) OKAY [ 1.770s]
Writing 'vendor' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Click to expand...
Click to collapse
xdauserart said:
Done till the step 9.
Tried the second way first (flashing images). Please see the log for this below.. Then tried OTA way. OTA way did with 0 exit status (it sent files) but when I boot device it writes "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds". How to fix?
Also when I load into recovery it writes this:
See full log for flashing images:
Click to expand...
Click to collapse
I had the same problem yesterday with the same results. I struggled with it until morning. Eventually I downloaded the latest version of adb, flashed the stock rom again and started over. It was done in twenty minutes. Try the latest version of adb (I guess version 35 for Windows)
xdauserart said:
Done till the step 9.
Click to expand...
Click to collapse
...
Code:
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.722s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
This indicates you tried to use the bootloader (which also has fastboot support) to flash the images. I made sure to write the guide the way that it states you should use the fastbootd service of the recovery. I have the dumb feeling that many more will go your way and fail. Damn it.
Code:
E: Failed to bind mount /mnt/staging/mulated/media/0 to /storage/emulated: NO such file or directory.
E: emulated failed to bind mount /mnt/stagingemulated/media/0 on /storage/meulated: No such file or directory.
Is fine, as you just erased all data - this also kills the partion so it cant be mounted anymore (that's the errors). This is indeed intentional as the system is now forced to really start fresh!
xdauserart said:
Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds"
Click to expand...
Click to collapse
Did you tried the help of my guide? When you failed that and your device rebooted too many times (or it just could not boot and crashed too many times) you'll need to reflash the boot partition to reset the counter (and therefore the failure message).
Two PR to fix back triple cam. But front cam is still broken.
https://github.com/sonyxperiadev/device-sony-seine/pull/29
https://github.com/sonyxperiadev/device-sony-pdx201/pull/15
--------------EDIT-----------------
Switch to CAF powerhal, better performance we have.
https://github.com/sjllls/device-sony-common/commit/de3b2bbbc33130891263d9e81ea2178a0f6783c4
https://github.com/sjllls/device-sony-sepolicy/commit/72059258eb0ff2c854996a05a5a23a8b73b55459
--------------EDIT-----------------
Renmember to let users flash with latest platform-tools, or they could not boot because of logical partition is not resized.
https://developer.android.com/studio/releases/platform-tools
Simonmicro said:
On their website:
Code:
OpenGapps Team (for base package and providing Open Gapps)
Therefore is a really good chance that the installer has the same problems like OpenGApps - but I can't say that for sure, I guess you'll need to try it out (when is does bootloop / never starts, please send me a adb logcat -b all for further diagnostics).
Click to expand...
Click to collapse
I can confirm that Opengapps pico can now be installed without a bootloop. I'm at work and I don't have adb. I installed them directly as an update from the sd card using recovery. Everything works fine.
Can we get OpenGapps Nano support?
I know that OpenGapps pico are supported, but most people use the nano package as it contains some functions that aren't possible to obtain in any other way
so is that possible?
KriiXOne said:
I know that OpenGapps pico are supported, but most people use the nano package as it contains some functions that aren't possible to obtain in any other way
so is that possible?
Click to expand...
Click to collapse
As I already drastically over-provisioned the system partition, I guess it could be possible that the nano package already works: In that case try it for yourself! When it goes wrong you can just switch over to your slot used before flashing the bad OpenGApps zip. Please PN me about your result, so I could extend the guide!
Simonmicro said:
As I already drastically over-provisioned the system partition, I guess it could be possible that the nano package already works: In that case try it for yourself! When it goes wrong you can just switch over to your slot used before flashing the bad OpenGApps zip. Please PN me about your result, so I could extend the guide!
Click to expand...
Click to collapse
I'll try tomorrow after the math test that i'm studying for today, and will let ya know ^^'
Simonmicro said:
...
Did you tried the help of my guide? When you failed that and your device rebooted too many times (or it just could not boot and crashed too many times) you'll need to reflash the boot partition to reset the counter (and therefore the failure message).
Click to expand...
Click to collapse
Fixed it Just repeated the steps from the first one and used OTA on step 9. Thanks!

Error while flashing Mi A2 in EDL mode

Sorry, my English very bad. I have Mi A2 with bootloop. Bootloader locked. I tried to flash three different firmwares using MiFlash, but was getting one error. it 1st image.
Later it seems I changed my MiFlash version and got another error, this is the second image. What do these errors mean?
Me_gusta_98 said:
Sorry, my English very bad. I have Mi A2 with bootloop. Bootloader locked. I tried to flash three different firmwares using MiFlash, but was getting one error. it 1st image.
Later it seems I changed my MiFlash version and got another error, this is the second image. What do these errors mean?
Click to expand...
Click to collapse
Don't know what that means but 'ack' should refer to "android common kernels".
I found a few videos searching for "Android Ack count don't match". Maybe you could try their solutions / methods.
User699 said:
Don't know what that means but 'ack' should refer to "android common kernels".
I found a few videos searching for "Android Ack count don't match". Maybe you could try their solutions / methods.
Click to expand...
Click to collapse
I saw it, there Indians install the beta version of MiFlash and everything is fine. But the beta version does not work for me, it does not see the file "flash_all.bat"
Me_gusta_98 said:
I saw it, there Indians install the beta version of MiFlash and everything is fine. But the beta version does not work for me, it does not see the file "flash_all.bat"
Click to expand...
Click to collapse
Maybe try an older (beta) version. It could be a problem in the current release which didn't occur in prior releases.
I have the same problem with a brand new Mi A2
Stuck at the androidone bootlogo.
Entering fastboot works without problems.
Flashing results in this error: FAILED (remote: 'Error flashing partition : Write Protected')
No matter which slot is used.
Unlocking via fastboot tells me that everything is already unlocked.
Booting the twrp image from fastboot gets stuck at the twrp logo.
This also happens with the patched twrp_4pda version.
This [GUIDE] Flashing ROMs with TWRP black screen post seemed helpful and adb shell works.
But sending commands like twrp wipe cache results in:
TWRP does not appear to be running. Waiting for TWRP to start . . .
Code:
fastboot --set-active=b
fastboot flash boot_b twrp.img
fastboot --set-active=a
fastboot flash boot_a twrp.img
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
fastboot boot twrp.img
adb shell
twrp wipe cache
Entering EDL mode via fastboot works without problems.
I installed the qualcomm 9008 drivers (windows 10 driver signature verification had to be disabled) and the phone in edl mode appears.
Downloaded the Mi A2 global fastboot rom
I tried all miflash versions (2015 to 2018 and beta) ... they had various bugs
XiaoMiFlash.Config --> rename to XiaoMiFlash.exe.Config
generate "Log" folder
place rom files inside miflash folder ... avoid any long/special path names
In the end they all start flashing and fail with "no Binary dump" or "ACK count don't match".
I also tried a different PC, different USB cable and fastboot on linux.
Is there anything else that could be done or is time to consider a hardware failure (broken emmc ...?) ?
#### update ###
fastboot format userdata
.... works and writes something without error
fastboot format cache / fastboot erase cache
... FAILED (remote: 'Error flashing partition : Write Protected')
I was able to get into stock recovery (hold VolUp+Power --> "no command" --> hold again).
wipe data / factory reset --> getting stuck forever on "wiping data..." screen
Apply Update from ADB --> adb sideload miui.zip also gets stuck forever
calling fastboot -w results in:
Spoiler: error code
Erasing 'userdata' OKAY [ 0.081s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 4652023 4k blocks and 1163264 inodes
Filesystem UUID: 969bf7be-a1e1-11ec-9ff1-f15f995f2a7c
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (180 KB) OKAY [ 0.011s]
Writing 'userdata' OKAY [ 0.000s]
Erasing 'cache' OKAY [ 0.002s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 65536 4k blocks and 65536 inodes
Filesystem UUID: 96ab61ae-a1e1-11ec-aed9-d92ea3a1e9cc
Superblock backups stored on blocks:
32768
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'cache' (56 KB) FAILED (remote: 'Error: Last flash failed : Write Protected')
fastboot: error: Command failed

Categories

Resources