Related
i can't get pass through fastboot oem unlock. it always says:
FAILED (remote: Invalid key,unlock fail, error num: 7)
finished. total time: 0.226s
i entered the corrected unlock codes and already enable oem unlock and debug. help needed thanks
heatron said:
i can't get pass through fastboot oem unlock........
Click to expand...
Click to collapse
I don't have this device but, you should be able to obtain some member guidance within one of the following threads that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3790159
https://forum.xda-developers.com/showthread.php?t=3818187
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
I have the same problem,
I've got the key number from Huawei website, and I'm sure that I got it right, but it's wrong number, is not able to unlock the device
>fastboot oem unlock 3073A326123F9B05
FAILED (remote: Invalid key,unlock fail, error num: 7)
Finished. Total time: 0.235s
Unlock failed
heatron said:
i can't get pass through fastboot oem unlock. it always says:
FAILED (remote: Invalid key,unlock fail, error num: 7)
finished. total time: 0.226s
i entered the corrected unlock codes and already enable oem unlock and debug. help needed thanks
Click to expand...
Click to collapse
Same problem here. No solution found on the internet
Code from Ministry of Solutions works on my LDN-L21 !
But, on every reboot/boot you have to press Power button to continue or phone will continue boot after 5 sec.
Very ****ing Device, No rooting, unlocking, twrp, rom flashing, hate this device
hasnainmughal said:
Very ****ing Device, No rooting, unlocking, twrp, rom flashing, hate this device
Click to expand...
Click to collapse
Root and unlock could be done, twrp almost works. No custom rom yet, but no reason to hate LDN-L21.
Since Y6/Y7 (non)Prime 2018 has Android 8.0 -> support Project Treble +
we know that Y7 has ARM64v8 CPU and since many Treble check apps claim that our devices do not support seemless updates -> slot A only,
I assume that we can install custom ROMs in form of Generic System Image (GSI) made for Treble-supported devices!
For now, there are LineageOS 15.1 and Resurrection Remix 6, made by user phhusson.
- bootloader must be unlocked,
- boot.img remains stock (but patched with/for Magisk)
- recovery.img must remain stock, there are no TWRP or CWM for us.
- system.img can be flashed via fastboot mode (only way for now)
- must use stock erecovery to make clean install -> so backup all before, wipe data and do factory default!
It should (I say "should" because not tested yet) boot to custom OS (LOS or RR).
So, you can try, but I am not responsible for any damage!!! Choose GSI image for AMR64 A-only devices!!!
Lineage-phh-treble
or
Resurrection-Remix-phh-treble
adeii said:
Since Y6/Y7 (non)Prime 2018 has Android 8.0 -> support Project Treble +
we know that Y7 has ARM64v8 CPU and since many Treble check apps claim that our devices do not support seemless updates -> slot A only,
I assume that we can install custom ROMs in form of Generic System Image (GSI) made for Treble-supported devices!
For now, there are LineageOS 15.1 and Resurrection Remix 6, made by user phhusson.
- bootloader must be unlocked,
- boot.img remains stock (but patched with/for Magisk)
- recovery.img must remain stock, there are no TWRP or CWM for us.
- system.img can be flashed via fastboot mode (only way for now)
- must use stock erecovery to make clean install -> so backup all before, wipe data and do factory default!
It should (I say "should" because not tested yet) boot to custom OS (LOS or RR).
So, you can try, but I am not responsible for any damage!!! Choose GSI image for AMR64 A-only devices!!!
Lineage-phh-treble
or
Resurrection-Remix-phh-treble
Click to expand...
Click to collapse
Anyone tried. Bootloops for me, Still looking for a solution.
futuristicsam said:
Anyone tried. Bootloops for me, Still looking for a solution.
Click to expand...
Click to collapse
Did you tried factory reset after flashing system.img?
Custom roms (Lineage, RR, ..) have no /data encryption, also internal sd (/data/media/0), like stock rom does.
Maybe have to format /data as ext4, not f2fs ?
UPDATE:
Since we have 8.0 stock rom, we can flash Lineage 15.1 at most.
adeii said:
Did you tried factory reset after flashing system.img?
Custom roms (Lineage, RR, ..) have no /data encryption, also internal sd (/data/media/0), like stock rom does.
Maybe have to format /data as ext4, not f2fs ?
UPDATE:
Since we have 8.0 stock rom, we can flash Lineage 15.1 at most.
Click to expand...
Click to collapse
Thanks for the reply, I did factory reset but I'll try to format data partition today and see the results.
futuristicsam said:
Thanks for the reply, I did factory reset but I'll try to format data partition today and see the results.
Click to expand...
Click to collapse
Anything happen?
adeii said:
Anything happen?
Click to expand...
Click to collapse
Yeah, still bootloops, I almost thought the 8.1 version could work but nope.
futuristicsam said:
Yeah, still bootloops, I almost thought the 8.1 version could work but nope.
Click to expand...
Click to collapse
Sorry to read that. How did you format /data ? As F2FS or EXT4?
Just theory:
In /vendor, there are 2 fstab files that declare /data as f2fs and encrypted.
Maybe if remove encryption and remain as f2fs, it will work?
So, you could try to flash Force+Encryption_Dm+Verity+Disabler_HuaweiY7Prime2018.zip in twrp,
format(wipe) /data as f2fs,
flash gsi.img from twrp (flash image) or fastboot (fastboot flash system gsi.img)
I had this phone and it was a little tough to root it. However i did. First of all i used my friend's pc and his dongle to read bootloader code. I had a problem for unlocking it just like mentioned above. i resetted my mobile andgo developer option to enable the oem unlocking (internet is needed once to enable oem unlocking after a reset) and runned the command oem unlock xxxxxx again from minimal adb and it worked. NOTE unlocking bootloader is only difficult. after that everything is piece of cake. you can either use flash twrp recovery to flash magisk or super su zip or directly flash a patched boot image of stock rom patched by magisk. Once done reboot and install magisk app to get root access
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
DOWNLOAD: https://twrp.me/sony/sonyxperiaxa2ultra.html
BUGS:
If you have found a bug, please consider posting it to our github issues log and then I'll report to Dess_Troy. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[RECOVERY][discovery] TWRP Touch Recovery [OFFICIAL], ROM for the Sony XA2 Ultra
Contributors
LuK1337
Source Code: https://github.com/TeamWin
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2018-10-30
Last Updated 2020-06-25
Thank you for this. I was able to boot the recovery and install magisk on my device. Is there any way to make the recovery permanent or do we have to fastboot the recovery every time?
Aklenz07 said:
Thank you for this. I was able to boot the recovery and install magisk on my device. Is there any way to make the recovery permanent or do we have to fastboot the recovery every time?
Click to expand...
Click to collapse
Not yet. Thought I don't think it's worth to /install/ it anyway.
Error flash
Hi,
I installed LineageOS but when I want to flash the "recovery", I am in error...
"target reported max download size of 536870912 bytes
sending 'recovery' (57720 KB)...
OKAY [ 1.281s]
writing 'recovery'...
FAILED (remote: No such partition.)
finished. total time: 1.284s"
Why ?
GunnarZX said:
Hi,
I installed LineageOS but when I want to flash the "recovery", I am in error...
"target reported max download size of 536870912 bytes
sending 'recovery' (57720 KB)...
OKAY [ 1.281s]
writing 'recovery'...
FAILED (remote: No such partition.)
finished. total time: 1.284s"
Why ?
Click to expand...
Click to collapse
You don't flash it.
LuK1337 said:
You don't flash it.
Click to expand...
Click to collapse
Just boot only ?
GunnarZX said:
Just boot only ?
Click to expand...
Click to collapse
That's all you need.
Done
It messed up (bootloop) at first, but second time worked fine.
Messed up my Xperia XA2 ultra
Hi i tried to use twrp 3 to install lineage OS.
Unlocked bootloader.
Fastboot boot the twrp.img
Backed up the device
Installed lineage os 15.1 and got an error
So decided to roll back to stock os
Restored the backup files.
It failed to restore it: device in bootloop.
I tried to use sony flashtool got an error; usb debug off
Can anybody help me?
bsbrfb said:
Hi i tried to use twrp 3 to install lineage OS.
Unlocked bootloader.
Fastboot boot the twrp.img
Backed up the device
Installed lineage os 15.1 and got an error
So decided to roll back to stock os
Restored the backup files.
It failed to restore it: device in bootloop.
I tried to use sony flashtool got an error; usb debug off
Can anybody help me?
Click to expand...
Click to collapse
Restore phone with Sony flash tool
https://developer.sony.com/develop/open-devices/get-started/flash-tool/
Install Lineage properly
https://wiki.lineageos.org/devices/discovery/install
Hi
Will this work on H3223 ?
Can this h3223 be rooted
mchlbenner said:
Hi
Will this work on H3223 ?
Can this h3223 be rooted
Click to expand...
Click to collapse
Unsure about root... Yet... But if you are bootloader unlocked you should at least be able to boot to twrp...
mchlbenner said:
Hi
Will this work on H3223 ?
Can this h3223 be rooted
Click to expand...
Click to collapse
Yes it roots
appleknight said:
Yes it roots
Click to expand...
Click to collapse
Magisk, and patch n flash boot.img?
Sorry mate, i'm coming from a device where kernel and ramdisk were separate partitions...
EDIT: Yes. Exactly
Aklenz07 said:
Restore phone with Sony flash tool
How Do I unlock the device?
I get an error saying my device is locked
Click to expand...
Click to collapse
tournelhenry said:
Aklenz07 said:
Restore phone with Sony flash tool
How Do I unlock the device?
I get an error saying my device is locked
Click to expand...
Click to collapse
https://wiki.lineageos.org/devices/discovery/install it tells you how to unlock
Click to expand...
Click to collapse
bootloader enter your imei it will give a key following all instructions precisely. it tells you the rxact command to use for unlocking the bootloader. after its unlocked, open your command prompt in your adb /fastboot folder. then adb reboot bootloader. after reboot phone will be blank screen. you have to download twrp 3.3.0.0 .img its the most updated. do that before the adb thing. then after adb thing, when you are booted into bootloader.....fastboot boot twrpxxxxx.img
this will boot into recovery. make sure you have magisk 19.zip doenloaded to your phone. then just flash magisk from the recovery, after reboot install magisk apk. there you go. sorry all of this is not in order. ive done it so many times im skipping ahead. i can give a better detailed and precise instructions if needed, litterally walk you thru it, if you need it. but the instructions provided by all the download sites are great. its easy peasy. if you need bettrr instructions youre more than welcome to get in contact with me. [email protected]
---------- Post added at 09:37 PM ---------- Previous post was at 09:31 PM ----------
sorry about that ****ty message, this goddamn site is retarded on mobile. im not going thru all that **** again but yes it can be rooted and its easy, if you need some clear instructions you can hit me up at the email i provided in that ****ty short bus post i left.
---------- Post added at 09:49 PM ---------- Previous post was at 09:37 PM ----------
you can keep the stock rom fyi. and theres an updated android 9.0 pie stock rom floating around too. im using it, no problems. you have to use xperifirm and flashtool to flash it tho. its simple unless its your first time doing, after you do it once youll ask yourself why it seemed so hard to get to that point. also, fyi, this particular is almost brick proof not saying it cant be bricked because, i did, several times boot looped it, everything, **** right now i dont even have a stock recovery because of some errors i made learning how to do all of this, but its up and running, its not buggy, magisk works great, stock android 9.0 firmware, just no recovery, but good ole twrp works just fine when you boot it for recovery. great phone to learn how to do all of this on. like i said its almost brick proof.
Sony Xperia XA2 Ultra - ROOT and Stock Rom 9.0
enter 192_161_227_73 in ip address format with the ftp header ftp://
should make rooting a little easier, need unlocked bootloader
simple interactive root process
also contains android 9.0 stock for Sony Xperia XA2 Ultra H3223
thanks Luk1337 for your work.
A) I get a stuck boot on SONY white screen when trying to reboot after a boot to twrp using fastboot (swipe to allow modifications and nothing else). Fastboot boot to TWRP was after a clean installation of Android Pie.
B) I even made a TWRP backup of the Android Pie rom but restoring backup runs into same issue of stuck on SONY logo). (well if just a twrp boot to resulted in a stuck boot (as in A) rebooting after a twrp backup restore would not have a chance either but just mentioning)
I am guessing we need a disable verity to avoid this?
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
https://forum.xda-developers.com/showpost.php?p=77177197&postcount=3
Do we have a vbmeta.img for the XA2 Ultra? (from stock kernel) sorry if a noob question. Thanks.
mac231us said:
thanks Luk1337 for your work.
A) I get a stuck boot on SONY white screen when trying to reboot after a boot to twrp using fastboot (swipe to allow modifications and nothing else). Fastboot boot to TWRP was after a clean installation of Android Pie.
B) I even made a TWRP backup of the Android Pie rom but restoring backup runs into same issue of stuck on SONY logo). (well if just a twrp boot to resulted in a stuck boot (as in A) rebooting after a twrp backup restore would not have a chance either but just mentioning)
I am guessing we need a disable verity to avoid this?
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
https://forum.xda-developers.com/showpost.php?p=77177197&postcount=3
Do we have a vbmeta.img for the XA2 Ultra? (from stock kernel) sorry if a noob question. Thanks.
Click to expand...
Click to collapse
Flash magisk or something, it'll disable verity.
Also we don't have vbmeta partition.
Here is one thing you should know before proceeding: Android 10 has new fastbootd and the latest Android Platform Tool is required to get fastbootd support.
Download your version https://developer.android.com/studio/releases/platform-tools
Tested on -7 RETUS and it worked after few trial and error
You must unlock bootloader first (and your phone is wiped during process)
Extract boot.img from full ROM and patch with Magisk Manager, and copy the patched boot.img back to host computer
Now here are the steps:
Enter bootloader (power the phone off, press and hold volume down while power your phone back on, and you should see bootloader screen
Now connect your One Hyper to host computer and enter
Code:
fastboot reboot fastboot
You will see something looks like stock recovery but it has fastbootd on the top.
From there, you can flash patched boot.img as you used to.
Reboot when it's done
CTSProfile and BasicIntegrity false, any ideas?
Space_Dog said:
CTSProfile and BasicIntegrity false, any ideas?
Click to expand...
Click to collapse
It's probably the version. I have same situation
mingkee said:
Here is one thing you should know before proceeding: Android 10 has new fastbootd and the latest Android Platform Tool is required to get fastbootd support.
Download your version https://developer.android.com/studio/releases/platform-tools
Tested on -7 RETUS and it worked after few trial and error
You must unlock bootloader first (and your phone is wiped during process)
Extract boot.img from full ROM and patch with Magisk Manager, and copy the patched boot.img back to host computer
Now here are the steps:
Enter bootloader (power the phone off, press and hold volume down while power your phone back on, and you should see bootloader screen
Now connect your One Hyper to host computer and enter
Code:
fastboot reboot fastboot
You will see something looks like stock recovery but it has fastbootd on the top.
From there, you can flash patched boot.img as you used to.
Reboot when it's done
Click to expand...
Click to collapse
What is this FastbootD? Something new on Android 10, cause the Pixel 4 has it too...
AndroidManager2020 said:
What is this FastbootD? Something new on Android 10, cause the Pixel 4 has it too...
Click to expand...
Click to collapse
It's Android 10 way to flash boot, recovery, dtbo, vbmeta, and super
The interface is more like stock recovery with fastbootd on the top
mingkee said:
It's Android 10 way to flash boot, recovery, dtbo, vbmeta, and super
The interface is more like stock recovery with fastbootd on the top
Click to expand...
Click to collapse
I totally understand the concept but what different between regular fastboot, mfastboot, and fastbootD?
mingkee said:
Here is one thing you should know before proceeding: Android 10 has new fastbootd and the latest Android Platform Tool is required to get fastbootd support.
Download your version https://developer.android.com/studio/releases/platform-tools
Tested on -7 RETUS and it worked after few trial and error
You must unlock bootloader first (and your phone is wiped during process)
Extract boot.img from full ROM and patch with Magisk Manager, and copy the patched boot.img back to host computer
Now here are the steps:
Enter bootloader (power the phone off, press and hold volume down while power your phone back on, and you should see bootloader screen
Now connect your One Hyper to host computer and enter
Code:
fastboot reboot fastboot
You will see something looks like stock recovery but it has fastbootd on the top.
From there, you can flash patched boot.img as you used to.
Reboot when it's done
Click to expand...
Click to collapse
For the retail channel on my device, should be LARET which had (2) Builds, the latest being (XT2027-1_DEF_RETLA_10_QPFS30.103-12-5-2_subsidy-DEFAULT_regulatory-XT2027-1-SUTEL-DS_CFC.xml.zip) i'll change to RETAIL after i receie the device. I am worried about getting OTAs later then Brazil/LA Channels.. There are NO RETAIL Firmware Packages for the Retail Channel Device. I guess ill have to see what model it is, Purchased from Amazon, which is where I got my G8+ for a CHEAP $205.83 and as soon as i went to reorder a replacement, price jumped $75, like amazon knew i was going to reorder the same device. Then i came across the one hyper and for a few $$$$ more, specs and chipset are better, same exact specs as the Zoom and the Hyper ran me $314 and the Zoon is like $394.00 I Just need something new to keep me busy until the Edge+ is released....and currently also a Pixel 4 XL (Trying to trade for a LG V60 thinq with the Dual Screen. ) Pixel is 1 month old, 1.5 months at the most, OEM Box, OEM accessories ONLY EVER USED, a couple cases.
Been a Android user since 2010, never had an LG Android. Wait, i had the V40/V50 for under 12 hrs and hated it. it felt cheap and clunky.... But i feel in love with this V60. And i also have (2) Moto G7 aka River. My Moto Def should be here tuesday hopefully. See how quick i can brick this one Moto G8+ was bricked on day one but i pulled out of it using a brand new Levovo Upgrade Tool!
Magisk install
I cannot find on XDA if we can or cannot install Magisk on the XT2027-1 ( One Hyper )
I found a few other sites on the internet that say it can be installed
BUT I tend to err on the side of caution.
I do not want to nuke this phone.
Is this a possibility to install Magisk or not?
I use Viper4 Android and a few other apps like blockada and such
Finally, IF Magsik is installed, I cannot get OTA updates, correct?
Can I uninstall Magisk, update OTA, then reinstall Magisk?
Thank you all
jharkness316 said:
I cannot find on XDA if we can or cannot install Magisk on the XT2027-1 ( One Hyper )
I found a few other sites on the internet that say it can be installed
BUT I tend to err on the side of caution.
I do not want to nuke this phone.
Is this a possibility to install Magisk or not?
I use Viper4 Android and a few other apps like blockada and such
Finally, IF Magsik is installed, I cannot get OTA updates, correct?
Can I uninstall Magisk, update OTA, then reinstall Magisk?
Thank you all
Click to expand...
Click to collapse
Have run into issues......... Damn Windows update restarted computer in middle of night before I was to finish rooting.
I can get into bootloader and when I try to flash I am stuck in bootloop
I get the following errors:
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
Sending 'vbmeta_a' (4 KB) OKAY [ 0.016s]
Writing 'vbmeta_a' (bootloader) WARNING: vbmeta_a anti rollback downgrade, 0 vs 5
OKAY [ 0.000s]
Finished. Total time: 0.016s
Ideas on how to fix? This was flashing back the ORIGINAL stock rom
---------- Post added at 07:57 AM ---------- Previous post was at 07:11 AM ----------
FIXED Rescue and Smart Assistant from Lenovo fixed it
Got it fixed thanks to Rescue and Search program from Motorola
Would like to know since TWRP is not working with the One Hyper, is there a way that I can make a master rom backup via ADB or FASTBOOTD?
If so, can someone make a batch file or list all the things to backup this rom?
I would greatly appreciate it. Thank you
I have my Magisk installed on my Hyper and all is working well. I just got Moto trying to download and update a patch (assuming Google security update). It could not update obviously.
My question is how can I UNinstall magisk , all the modules, and then update my Hyper?
Now if I uninstall magisk I will lose root, correct?
This is the rom I am currently using........DEF_RETAIL_QPFS30.103-47-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC
jharkness316 said:
I have my Magisk installed on my Hyper and all is working well. I just got Moto trying to download and update a patch (assuming Google security update). It could not update obviously.
My question is how can I UNinstall magisk , all the modules, and then update my Hyper?
Now if I uninstall magisk I will lose root, correct?
This is the rom I am currently using........DEF_RETAIL_QPFS30.103-47-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Click to expand...
Click to collapse
in order to take updates you would need to restore the stock boot image with fastboot or magisk, and then update your device, then take the new boot image from the downloaded update and patch with magisk and then flash it to regain magisk root, you do not need to uninstall magisk or the modules but you will need to restore stock boot partitions to allow the device to not error out during the install process. This is how it has been in the past for magisk official guides can be found on magisk website here: https://topjohnwu.github.io/Magisk/ota.html
[deleted]
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
hey i can help ! which version of twrp are you trying to flash ?
lmaohelp said:
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
Click to expand...
Click to collapse
The update website isn't going to come back anytime soon. But if you just don't mind opening your device again(you need to access the test point), there's a fix. this method doesn't just need anything. even if your device is hard bricked, it can get you back running. This was described in a youtube video with working links based on a forum on xda.
link : click here
I got a similar problem recently but I flashed update.zip of emui 8 - > Bootlooped - > factory reset with twrp - > successfully booted but doesn't get past the setup screen. Fix : flashed a gsi treble image(based on android 10) - > working perfect except for camera and volte.
Venkata Lochan Nune said:
The update website isn't going to come back anytime soon. But if you just don't mind opening your device again(you need to access the test point), there's a fix. this method doesn't just need anything. even if your device is hard bricked, it can get you back running. This was described in a youtube video with working links based on a forum on xda.
link : click here
I got a similar problem recently but I flashed update.zip of emui 8 - > Bootlooped - > factory reset with twrp - > successfully booted but doesn't get past the setup screen. Fix : flashed a gsi treble image(based on android 10) - > working perfect except for camera and volte.
Click to expand...
Click to collapse
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
King_of_Android said:
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
Click to expand...
Click to collapse
My bad , I thought the update website to be huawei's official one(something like update.hicloud and all isn't it?). Well, thanks for the information but I still prefer gsi. It's buttery smooth .
And one more thing, if you follow the youtube video I mentioned, you don't need any gsi. You can get your device back on stock EMUI 5.
King_of_Android said:
hey i can help ! which version of twrp are you trying to flash ?
Click to expand...
Click to collapse
Hey I have a doubt... Will the recoveries we find in twrp official website / app work on EMUI 8? I wanted to try them but I'm afraid I might brick my device again. Getting it back is a hectic thing and I already had to face it thrice. LOL .
King_of_Android said:
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
Click to expand...
Click to collapse
Hi, thanks for trying to help! I am using the website to install the firmware but I am having problems with it currently, and I made a post about it, if you could help me with that it would be greatly appreciated.
lmaohelp said:
Hi, thanks for trying to help! I am using the website to install the firmware but I am having problems with it currently, and I made a post about it, if you could help me with that it would be greatly appreciated.
Click to expand...
Click to collapse
I tried using that website but I wasn't able to figure out how to use it. So just left it. Did you try the method which I described earlier?
Venkata Lochan Nune said:
I tried using that website but I wasn't able to figure out how to use it. So just left it. Did you try the method which I described earlier?
Click to expand...
Click to collapse
I haven't tried to use the method you posted yet, because it is a bit more lengthy and complicated. If the method I was using does not work I'll use the video and let you know how it goes. Thanks!
lmaohelp said:
I haven't tried to use the method you posted yet, because it is a bit more lengthy and complicated. If the method I was using does not work I'll use the video and let you know how it goes. Thanks!
Click to expand...
Click to collapse
Well, just clear these things:
Is your bootloader still unlocked?
Did you try using another recovery image instead of the one you are getting error for?
Venkata Lochan Nune said:
Well, just clear these things:
Is your bootloader still unlocked?
Did you try using another recovery image instead of the one you are getting error for?
Click to expand...
Click to collapse
My bootloader is still unlocked, yes. However, I did not try to flash another recovery image, as I was not sure where I could find one that worked. I forgot which image I used at first but it had worked the first time, so that was why I did not bother finding a different recovery. Do you have a suggestion for a recovery to install?
lmaohelp said:
My bootloader is still unlocked, yes. However, I did not try to flash another recovery image, as I was not sure where I could find one that worked. I forgot which image I used at first but it had worked the first time, so that was why I did not bother finding a different recovery. Do you have a suggestion for a recovery to install?
Click to expand...
Click to collapse
I'm attaching one that works with emui 8 try using it (Remember you have to flash it to recovery_ramdisk).
Well after reading your post 1 again, I think there's no such partition as recovery_ramdisk(because it will be there only from android 8). So find a recovery in google which works on hi6250 devices with emui 4. That should work. Update me with the result
lmaohelp said:
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
Click to expand...
Click to collapse
hi
can you boot into recovery (must be TWRP) at the moment? then try the following...click the link in post 3 and in youtube expand the info...then click the unbrick link and download the oeminfo.
on the phone (TWRP) recovery flash the oeminfo in to the oeminfo partion...reboot to erecovery and then download the stock rom....after this reboot into system
i had unbrick some huawei devices with this method and it helps e´very time
solong
speedson
speedson said:
hi
can you boot into recovery (must be TWRP) at the moment? then try the following...click the link in post 3 and in youtube expand the info...then click the unbrick link and download the oeminfo.
on the phone (TWRP) recovery flash the oeminfo in to the oeminfo partion...reboot to erecovery and then download the stock rom....after this reboot into system
i had unbrick some huawei devices with this method and it helps e´very time
solong
speedson
Click to expand...
Click to collapse
His problem us with twrp.
He can only access fastboot but isn't able to flash twrp...
Venkata Lochan Nune said:
Well after reading your post 1 again, I think there's no such partition as recovery_ramdisk(because it will be there only from android 8). So find a recovery in google which works on hi6250 devices with emui 4. That should work. Update me with the result
Click to expand...
Click to collapse
So I have tried many different recoveries, such as ones for EMUI 4 and 5 and flashing directly to recovery, which gave me an error "image verification failed", and flashing an EMUI 8 to ramdisk would give me the same error as before. I think the partitions on this device is really messed up lol. Also, when I type fastboot reboot recovery, it would just get stuck at the loading screen, so does that mean there is no working recovery installed?
lmaohelp said:
So I have tried many different recoveries, such as ones for EMUI 4 and 5 and flashing directly to recovery, which gave me an error "image verification failed", and flashing an EMUI 8 to ramdisk would give me the same error as before. I think the partitions on this device is really messed up lol. Also, when I type fastboot reboot recovery, it would just get stuck at the loading screen, so does that mean there is no working recovery installed?
Click to expand...
Click to collapse
Maybe yes. Did you try directly booting the image without flashing?
Code:
fastboot boot recovery.img
Venkata Lochan Nune said:
Maybe yes. Did you try directly booting the image without flashing?
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
Yup, I tried that as well, and it told me "invalid command"
lmaohelp said:
Yup, I tried that as well, and it told me "invalid command"
Click to expand...
Click to collapse
Well as you said, you partitions must have been really messed up. I have no other ideas except the test point method.
Are you trying anything else?
Ok we have some option that could help you...
Im read in the 4PDA (the russian XDA xD) forum that it should be possible to flash the oeminfo by fastboot command. So just download the HWOTA_BLN_Eng and expand it. Then go to 7 or 8 Folder and there you go to oeminfo folder. There you choose the right one for your Device and local area...for example BLN-L21 (Device) C432 (European Area)
Extract the file to your desktop and rename it to BLN-L21C432.img
--->be sure that you have the right Device driver installed and the right ADB driver for your device to<---
ok now Copy and Paste the BLN-L21C432.img to ADB folder and start command with admin rights
start the phone into fastboot mode
--->bootloader must be unlocked<---
in the command
fastboot flash oeminfo BLN-L21C432.img
wait for the result and it can not hurt to pray a bit in this moment...hihi
if this have success...you type in command
fastboot reboot
wait to the screen you can press 3 seconds Vol+ to go into erecovery....connect to wlan and it should work step by step like it should.
after download and recover the stock rom reboot and go again to erecover by press Vol+ for 3 seconds and now go to the second option...wipe data/factory reset and write yes+enter
in stock recovery wipe Data after that wipe Cache...reboot and wait that system boot the initial boot for first setup.
If this will not working...tell me what honor 6x you have and wich local area you are from and wich firmware you stock had before you doing wronng
good luck bro
solong
speedson
I have a new Pixel 4a, Android 12. I want to use lineage 19.1. I try already several days to flash TWRP, sunfish_twrp3.6.1-11 or sunfish_twrp11-test3. No success. Finally I write fastboot flash boot_a_twrp.img instead of fastboot boot twrp.img. It ended up with the screen of teamwin, hanging there. Now the pixel is not booting to android any more but each time to the incomplete teamwin screen. So I tried to flash the newest factory image. No success : "writing 'boot' failed (remote: Failed to write to partition Not Found)
I need help urgently. Thanks!
Henneranek said:
I have a new Pixel 4a, Android 12. I want to use lineage 19.1. I try already several days to flash TWRP, sunfish_twrp3.6.1-11 or sunfish_twrp11-test3. No success. Finally I write fastboot flash boot_a_twrp.img instead of fastboot boot twrp.img. It ended up with the screen of teamwin, hanging there. Now the pixel is not booting to android any more but each time to the incomplete teamwin screen. So I tried to flash the newest factory image. No success : "writing 'boot' failed (remote: Failed to write to partition Not Found)
I need help urgently. Thanks!
Click to expand...
Click to collapse
I don't think you're providing enough info. "I tried to flash the newest factory image" doesn't tell useful people what you did. I'm not useful, anyway.
I wouldn't use TWRP on the 4a. I'm using LOS recovery. You can follow the instructions (read the whole thing first) here: https://wiki.lineageos.org/devices/sunfish/install
That should allow you to do a clean install of LOS19.
Thank you for giving advice. I followed exactly your recommended web-site (Install LineageOS on sunfish, Temporarily booting a custom recovery using fastboot). From what I understand the first step is to install a recovery which in my case was sunfish_twrp3.6.1-11.img . I did not work. I also tried an older twrp.img. "fastboot flash boot twrp.img" did not work. I read and read, learned about 2 slots, without a deep understanding. Then I tried " fastboot flash boot_a_twrp.img". It seemed to work. But when I reboot into recovery it is stuck at the screen of teamwin (see attachment).
I thought to give up and do a factory reset. But there I got this: Failed to write to partition Not Found. What can I do now? Is there a way to do a factory reset to slot_b ?
If you try to help me please remember that I don't have enough knowledge to understand abbreviations.
Henneranek said:
Thank you for giving advice. I followed exactly your recommended web-site (Install LineageOS on sunfish, Temporarily booting a custom recovery using fastboot). From what I understand the first step is to install a recovery which in my case was sunfish_twrp3.6.1-11.img . I did not work. I also tried an older twrp.img. "fastboot flash boot twrp.img" did not work. I read and read, learned about 2 slots, without a deep understanding. Then I tried " fastboot flash boot_a_twrp.img". It seemed to work. But when I reboot into recovery it is stuck at the screen of teamwin (see attachment).
I thought to give up and do a factory reset. But there I got this: Failed to write to partition Not Found. What can I do now? Is there a way to do a factory reset to slot_b ?
If you try to help me please remember that I don't have enough knowledge to understand abbreviations.
Click to expand...
Click to collapse
if it goes into bootloader head over to the android flash tool and give that a try,,https://source.android.com/setup/contribute/flash
To hammered58 Thank you for this suggestion reg. android flash tool. This seems very complicated and I don' t understand some terms. I am a NOOB.
In my Pixel 4a the slot a is somehow obstructed. Can't I use slot b to do a factory reset?
Henneranek said:
To hammered58 Thank you for this suggestion reg. android flash tool. This seems very complicated and I don' t understand some terms. I am a NOOB.
In my Pixel 4a the slot a is somehow obstructed. Can't I use slot b to do a factory reset?
Click to expand...
Click to collapse
Its not complicated at all,, just put you phone in fastboot, which I know you have done before , go here (https://flash.android.com) and follow the on screen prompts, select any factory image and start.
Dear hammered58, I am so thankful to you! Thank you for encouraging me to use the Android Flash Tool. I was skeptical. To undo the pop-up blocker in Chrome was complicated for me. After some failures because I was not patient enough I finally succeeded.
Henneranek said:
Dear hammered58, I am so thankful to you! Thank you for encouraging me to use the Android Flash Tool. I was skeptical. To undo the pop-up blocker in Chrome was complicated for me. After some failures because I was not patient enough I finally succeeded.
Click to expand...
Click to collapse
Good to know it worked for you