hi i unlocked bootloader and installed lineage 17 from stevesames tutorial
had some issues but got it done after a while
i cannot install gapps
not sure if im using the correct commands im kinda nooby lol but even lineage the apps i install say not rooted etc
trying to install twrc gets these errors
Code:
PS C:\Users\djlee\Downloads\platform-tools_r30.0.5-windows\platform-tools> fastboot devices
MBHEGU9PEY7DI74P fastboot
PS C:\Users\djlee\Downloads\platform-tools_r30.0.5-windows\platform-tools> fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (15636 KB)...
OKAY [ 4.668s]
writing 'recovery'...
FAILED (remote: Only system partition can be flashed)
finished. total time: 4.680s
Trying to install gapps i get
Code:
PS C:\Users\djlee\Downloads\platform-tools_r30.0.5-windows\platform-tools> fastboot -u flash zip C:\Users\djlee\Downloads/open_gapps-arm-10.0-nano-20210213.zip
target reported max download size of 134217728 bytes
Invalid sparse file format at header magi
any help is greatly appreciated thanks
No-one has ever reported being able to, so you can forget about flashing GApps, Magisk, etc.
However, these versions of LineageOS 16 https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/ are built with both root AND signature spoofing, so you can install MicroG (https://microg.org/) and Aurora Store (https://gitlab.com/AuroraOSS/AuroraStore) instead of Big Brother's ever-spying GApps.
Related
I recently installed TWRP recovery on my phone and unlocked the bootloader. However, I did not read that after this you can not install OTA updates, and I would like to be able to download them. So my question is how to effectively upload Stock Recovery on my phone? I downloaded my ROM and extracted the file RECOVERY.IMG from it and tried to upload it through ADB, but during the flash it appears to me in CMD:
"C:\minimal>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (35396 KB)...
OKAY [ 0.774s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.784s"
What can I do in this case? Will anyone help me? Thank you.
the recovery partition on oreo isn't called recovery! it's called ramdisk, BTW can you upload the recovery image please?
Hi All.
Today i flashed TWRP on my phone Huawei P10 (europe version)
This works great so far so good.
I downloaded on this site and section:
1
VTR-L09C432E1R1P9B157 (9.0.1.157) the files:
update_full_VTR-L09_hw_eu.zip
update.zip
i cleaned cache/dalvik and i done a clean on internal storage.
then i say install :
HuRUpdater_0.3
boot no go...
then i install VTR-L09_hw_eu.zip
update.zip
but got allot of errors but i boots anyway....
It boots into PIE and touchscreen is not at correct place (its 3mm off) and i have no services with my provider (simcart not working)
when i take a closer look what software its running its:
model VKY
BUILD NR: LGRP2-OVS 9.0.1.163
EMUI 9.0.1
BASEBAND: 21C30B323S006C000
So its not VTR but i have PIE VKY... and i think the VKY got a different chipset for service provider then the VTR.
But my question is:
what am i doing wrong? do i need other flash file? can someone please point me to the good direction.
Regards.
Tim
Oke i discovered maybe the problem. I think its not flashing at all.. and the VKY is a wrong downloaded img from erecovery (i tryed that also) he connected thru wifi before and downloaded a img from huawei site.
When i flash update i got these msg:
installing zip file /external_sd/update/update.zip
no digest file found
script succeeded /data
script succeeded false
write radio image
check_write_data_to_partition,write data error
update_huawei_pkg_from_ota_zip update package from zip failed
E: unknown command errno
E: unknown command subproccesresult
updater ended with error 9
error installing zip file
updating partition details
...done.
update: and i hope someone would help me..
I have now TWRP only.
But for some reason i cant install the images i download. So i dont get a OS installed.
Can please someone help me
regards, Tim
is it possible that this is the problem:
c:\Users\Tim\Desktop\w>fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (32034 KB)...
OKAY [ 0.693s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.705s
c:\Users\Tim\Desktop\w>fastboot flash recovery_ramdisk twrp.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32034 KB)...
OKAY [ 0.695s]
writing 'recovery_ramdisk'...
OKAY [ 0.301s]
finished. total time: 1.001s
Only recovery_ramdisk gives me TWRP not like the tutorials tell me todo (recovery)
Whenever i try to flash something to boot or recovery partition i get the following error:
Code:
:~/Desktop/New Folder/amonet$ fastboot flash boot boot.img
target reported max download size of 134217728 bytes
sending 'boot' (4676 KB)...
OKAY [ 0.230s]
writing 'boot'...
FAILED (remote:
Checksum Error.)
finished. total time: 0.382s
It is a false checksum error as i have downloaded it multiple times and flashed it to other devices of the same model.
Shamrock3six said:
Whenever i try to flash something to boot or recovery partition i get the following error:
It is a false checksum error as i have downloaded it multiple times and flashed it to other devices of the same model.
Click to expand...
Click to collapse
Just try with SP Flash Tool for Windows and Linux (any distributions).
https://spflashtool.com/
AmznUser444 Dev said:
Just try with SP Flash Tool for Windows and Linux (any distributions).
https://spflashtool.com/
Click to expand...
Click to collapse
What? Completely inappropriate suggestion for all but the most advanced tinkerers. Tossing into a (real) fire would be easier.
So... I tried to unlock/root my Redmi Note 11 (SPES), and something went wrong. So now I am trying to fix it, restore to the stock ROM to try again.
How I broke it:
1. Unlocked the bootloader.
2. Installed probably the wrong TWRP (I installed twrp-3.6.2-12.1-21.06.22.img from https://razaoinfo.dl.sourceforge.ne...ld/Recovery-Spes/twrp-3.6.2-12.1-21.06.22.img )
3. I tried flashing said img using fastboot (fastboot flash recovery_a <img>, followed by fastboot flash recovery_b <img>, then fastboot boot <img>
4. Got into TWRP, flashed Magisk.
5. Got into ROM. Everything seems to work, I have root. Next day, I realize my bluetooth is not working.
Next day, I tried flashing another TWRP that I found linked in this forum (twrp-3.6.2_12-0-spes-Jabiyeff.img, downloaded from https://forum.xda-developers.com/t/...-redmi-note-11-and-how-do-i-flash-it.4466177/ post #4).
6. After flashing, ROM no longer boots, and just sends me to fastboot.
7. I checked again with fastboot, and.. it seems the recovery partition isn't there?
Code:
C:\adb2>fastboot.exe devices
ff23ad4 fastboot
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.902s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.909s
C:\adb2>fastboot.exe flash recovery_a twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery_a' (131072 KB)...
OKAY [ 2.828s]
writing 'recovery_a'...
FAILED (remote: (recovery_a_b) No such partition)
finished. total time: 2.835s
C:\adb2>fastboot.exe flash recovery_b twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery_b' (131072 KB)...
OKAY [ 2.805s]
writing 'recovery_b'...
FAILED (remote: (recovery_b_b) No such partition)
finished. total time: 2.812s
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.849s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.857s
C:\adb2>fastboot.exe boot twrp-3.6.2_12-0-spes-Jabiyeff.img #NOTE: Here I changed the active partition in this TWRP from B to A.
downloading 'boot.img'...
OKAY [ 2.790s]
booting...
OKAY [ 0.367s]
finished. total time: 3.159s
C:\adb2>fastboot.exe devices
ff23ad4 fastboot
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.933s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.946s
C:\adb2>fastboot.exe flash recovery_a twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery_a' (131072 KB)...
OKAY [ 2.899s]
writing 'recovery_a'...
FAILED (remote: No such file or directory)
finished. total time: 2.918s
C:\adb2>fastboot.exe flash recovery_b twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery_b' (131072 KB)...
OKAY [ 2.931s]
writing 'recovery_b'...
FAILED (remote: No such file or directory)
finished. total time: 2.943s
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.874s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.887s
So, I wonder if I should be concerned about not finding a recovery/recovery_a/recovery_b partition (I am pretty sure recovery_a/b where there when I flashed TWRP the first time).
So, I am following now this guide to install the stock ROM: https://xiaomistockrom.com/xiaomi-redmi-note-11
Am I on the right path? I want to check before proceeding, because... right now I have fast boot and can boot into TWRP using it, but if I do things incorrectly from now on, I could brick the device. So I wanted to ask for advice on what I am doing first here.
TIA.
It's fairly difficult to hard brick a device. Most of the time you'll just end up soft bricking your device which is easy to fix as long as you can access bootloader mode. If you want to fully restore your device to default, you can download your stock rom (fastboot version) and flash using miflash.
Also yes, the guide you linked is correct.
Thanks, I managed to solve it.
The fastboot issue went away some time afterwards, and I could boot normally into the ROM, but... my bluetooth stopped working (which is really strange considering I only flashed the recovery partition). I tried flashing the bluetooth partition from the stock ROM's, but that didn't fix it.
So I tried flashing the stock ROM, following the previously linked guide (and that guide, not the guides that came bundled in the downloaded ROM, that one was for a different device, not a Xiaomi phone at all, weird!).
And now, I have bluetooth again. Thanks goodness for Migrate, I should be able to restore the rest of the device swiftly now.
I've got to unbrick my phone, I think.
I can't boot into system or recovery cause my phone is bricked.
What should I do?
When I start fastboot and try to flash twrp, ther comes this message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery 4_twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.532s]
writing 'recovery'...
FAILED (remote: This partition doesn't exist)
finished. total time: 1.563s
This is an a/b device , use fastboot flash boot instead of fastboot flash recovery