Database Info

[HELP] Rom error status 0: installation aborted - htc sensation

Hello!
I've problem with my htc sensation. I've been using custom roms for a few months, I tested roms like Venom, Revolution, Cyagnogenmod.
Mine last was: [Android 4.4.4] CyanogenMod 11 with 3.0.16 kernel [July 1, 2014]
Today i wanted to install: [3.4Kernel] CM-11 Android 4.4.4 [Stable v2.0][30 June]
I made full wipe (except sdcard), tried to install new rom and i got error:
{
"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"
}
MD5:
Info:
Bootloader:
I've tried different roms, different sdcards, still te same result.
I made full wipe, so my htc does not run...
What should I do?
Thank you for the replies!

what version of 4ext recovery do you have? install the latest 1.0.0.6 rc3

I also had that problem at first but after updating that $ext recovery touch to the latest version, it worked like magic.

Thanks for the reply!
But how can I install new recovery tool without turning my phone on?
I don't know the method, could you share me a link to the tutorial?

NoooX said:
Thanks for the reply!
But how can I install new recovery tool without turning my phone on?
I don't know the method, could you share me a link to the tutorial?
Click to expand...
Click to collapse
here is the latest version
http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
extract the recovery.img
place it in your adb/fastboot folder
boot your device to the bootloader and select fastboot
connect it to the pc
open a cmd in the adb/fastboot folder and type
fastboot flash recovery recovery.img
fastboot reboot bootloader

rzr86 said:
here is the latest version
extract the recovery.img
Click to expand...
Click to collapse
I get error:
Unknown file format when i try to extract by 7zip or ICS/JB/EXT4 unpacker

NoooX said:
I get error:
Unknown file format when i try to extract by 7zip or ICS/JB/EXT4 unpacker
Click to expand...
Click to collapse
extract it with winrar

rzr86 said:
extract it with winrar
Click to expand...
Click to collapse
Still the same, it looks like archive is damaged...

NoooX said:
Still the same, it looks like archive is damaged...
Click to expand...
Click to collapse
i didn't have any problem
nevermind
here is the recovery.img

You might want to install "4EXT Recovery Updater" app. It's free and maybe easier to use than flashing it via pc.
You should always check the OP, they usually state if there is a brand new version of recovery required to flash that rom.

LxMaD said:
You might want to install "4EXT Recovery Updater" app. It's free and maybe easier to use than flashing it via pc.
You should always check the OP, they usually state if there is a brand new version of recovery required to flash that rom.
Click to expand...
Click to collapse
Or buy an "4EXT Recovery Control". It has much more features:laugh:

I'm an amateur and bricked my Poco X3 (Surya)

Hi everyone, first of all, sorry for my bad english.
As the rules state, I've already lurked through some of the threads on the site but I'm not really sure on how to proceed or which one to follow, as many of them goes through different processes.
I was trying various different ROMs and installing them with no problems untill I went to AncientOs, which made my WIFI unusable and the System UI unstable, so I decided to move to DotOs and there's when the problem started. I'm not really sure on where did I go wrong, but after many attemps and messing with things I don't properly know, I ended with my device booting to Fastboot mode and an error message everytime I try to install a new ROM:
Code:
Failed to mount '/vendor' (Invalid argument)
If I go to the wipe tab, the Vendor and the system options are missing.
Thanks in advance for the help, feel free to tell me if I'm missing some important details about the problem

try to flash the stock miui rom through mi flash tool

aymen peter said:
try to flash the stock miui rom through mi flash tool
Click to expand...
Click to collapse
Thank you mate, I did flashed Stock via fastboot method and it really fixed it, I'll be more careful next time

it happens to everyone , no worries.
just revert to stock & flash again till you get it right.

aymen peter said:
try to flash the stock miui rom through mi flash tool
Click to expand...
Click to collapse
I'm currently on arrow OS 11 right now, how to revert back to MIUI?

Sandymikdad said:
I'm currently on arrow OS 11 right now, how to revert back to MIUI?
Click to expand...
Click to collapse
Flash MIUI in fastboot mode
No idea why you want to go back though. ArrowOS is stable, bug free for me and has a good battery life

Noter2017 said:
Flash MIUI in fastboot mode
No idea why you want to go back though. ArrowOS is stable, bug free for me and has a good battery life
Click to expand...
Click to collapse
Thank you.
Im just curious about the internal storage. After format data and re flash the rom, then I restore the apps+data with swiftbackup, i found the system taking huge amount of storage around 19GB. Is it something wrong or just normal?
{
"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"
}

Sandymikdad said:
Thank you.
Im just curious about the internal storage. After format data and re flash the rom, then I restore the apps+data with swiftbackup, i found the system taking huge amount of storage around 19GB. Is it something wrong or just normal?View attachment 5340329
Click to expand...
Click to collapse
It's perfectly fine.
19 - 20 GB is what Android 11 takes. Probably it's even more in MIUI because of all the pre-installed apps

[SOLVED] Poco X3 NFC (surya) Stuck in Bootloop After ArrowOS Update

As the title reads, My Poco X3 has gotten stuck in a bootloop after an attempted ArrowOS update. I think it's the May update, and from other posts on this forum, it seems this is a not a one-off issue. I tried updating my phone by downloading the latest ArrowOS update and firmware for the PocoX3 (firmware from Xiaomi firmware updater) through TWRP (Unofficial) by @mauronofrio.
But this put me into a bootloop of sorts that would boot straight into fastboot. I then booted into TWRP, and it spat out a bunch of errors (Mind you these are not the exact errors I got):
Code:
E: Unable to update logical partition: /odm
E: Failed to mount '/vendor'
E: Unable to decrypt FBE device
...
E: Failed to mount /tmp/com.android.resolv.apex to loop device /dev/block/loop16
E: Unable to open loop device: /dev/block/loopNUM
I then tried to wipe everything with TWRP, no change. Then I try to make a fresh install by using the fastboot version of the latest version of MIUI. Now, the phone is in an actual bootloop. I reinstall TWRP and boot into it, and luckily there are less errors, but there are still the ones about the /odm partition and being unable to decrypt the FBE device, whatever that is.
I'm out of ideas for this, any ideas as to why my phone is doing this?
PS: Here's an image of the errors my phone gives me:
{
"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"
}

insdedm said:
As the title reads, My Poco X3 has gotten stuck in a bootloop after an attempted ArrowOS update. I think it's the May update, and from other posts on this forum, it seems this is a not a one-off issue. I tried updating my phone by downloading the latest ArrowOS update and firmware for the PocoX3 (firmware from Xiaomi firmware updater) through TWRP (Unofficial) by @mauronofrio.
But this put me into a bootloop of sorts that would boot straight into fastboot. I then booted into TWRP, and it spat out a bunch of errors (Mind you these are not the exact errors I got):
Code:
E: Unable to update logical partition: /odm
E: Failed to mount '/vendor'
E: Unable to decrypt FBE device
...
E: Failed to mount /tmp/com.android.resolv.apex to loop device /dev/block/loop16
E: Unable to open loop device: /dev/block/loopNUM
I then tried to wipe everything with TWRP, no change. Then I try to make a fresh install by using the fastboot version of the latest version of MIUI. Now, the phone is in an actual bootloop. I reinstall TWRP and boot into it, and luckily there are less errors, but there are still the ones about the /odm partition and being unable to decrypt the FBE device, whatever that is.
I'm out of ideas for this, any ideas as to why my phone is doing this?
PS: Here's an image of the errors my phone gives me:
View attachment 5334047
Click to expand...
Click to collapse
Flash the fastboot ROM from here:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
You need the fastboot ROM which is 4.9 GB.
Flash it using the latest flash tool from here:
Download Xiaomi Flash Tool 20210226 - Official Tool
Download the Official and Tested version of Xiaomi Flash Tool, i.e., Xiaomi Flash Tool 20210226 which allows you to Flash Stock Firmware on Xiaomi Devices.
xiaomiflashtool.com
After the phone reboots, set it up and use it for a few minutes to see if everything works and report back here

Noter2017 said:
Flash the fastboot ROM from here:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
You need the fastboot ROM which is 4.9 GB.
Flash it using the latest flash tool from here:
Download Xiaomi Flash Tool 20210226 - Official Tool
Download the Official and Tested version of Xiaomi Flash Tool, i.e., Xiaomi Flash Tool 20210226 which allows you to Flash Stock Firmware on Xiaomi Devices.
xiaomiflashtool.com
After the phone reboots, set it up and use it for a few minutes to see if everything works and report back here
Click to expand...
Click to collapse
Thanks a lot!
I had heard of this xiaomi flash tool but I was suspicious of it as I couldn't find anyone linking it in XDA.
I've installed it and used it to flash MIUI to get back to stock, and luckily this time it worked!
On a slightly unrelated note, do you have any idea why that update to ArrowOS broke my phone? I'm curious on what happened, if it was a user error on my part or the devs fault somehow.

disable dm verity must be installed before updating.

Question MSN Error: FirehoseCheckRSP Failed; error 258 / Downloading Super.img failed

This is for the Global version of the Oneplus 9 and i'm attempting to fix my qualcomm crashdump mode error. Fastboot and Recovery load fine. Tried flashing lineage and the stock os with errors using fastboot/adb
I have the Qualcomm drivers install (multiple different sources, rebooted computer into unsigned drivers mode) and have tried the Global and Indian MSN version.
{
"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"
}
Any suggestions or resolutions to this error? I've tried checksum off and Firehose Lite but get a wrong device/version error

Use msmtool for oneplus 9 pro, it works for me really

Download the Indian 9 Pro firmware, click use lite firehose. For some reason that MSM doesn't check device params and all the others do. Then you will have to grab the appropriate downgrade package for your device from the pinned post and flash that with the local upgrade tool to get back to the correct 9 firmware.
Also, make sure you have the right drivers installed.
Qualcomm_QDLoader_HS-USB_Driver_64bit_Setup.zip | by Explaining Android for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com

EtherealRemnant said:
Download the Indian 9 Pro firmware, click use lite firehose. For some reason that MSM doesn't check device params and all the others do. Then you will have to grab the appropriate downgrade package for your device from the pinned post and flash that with the local upgrade tool to get back to the correct 9 firmware.
Also, make sure you have the right drivers installed.
Qualcomm_QDLoader_HS-USB_Driver_64bit_Setup.zip | by Explaining Android for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
Thank you for the response. I downloaded the Indian Version for Onplus 9 Pro and am still having the same issues. I installed the drivers you linked above also.
Any other suggestions? Will eventually give it a try on a different computer. Also tried 2 other cables (USB-A) that did not detect the device even.

Motafota said:
Thank you for the response. I downloaded the Indian Version for Onplus 9 Pro and am still having the same issues. I installed the drivers you linked above also.
Any other suggestions? Will eventually give it a try on a different computer. Also tried 2 other cables (USB-A) that did not detect the device even.View attachment 5631329
Click to expand...
Click to collapse
This may be a hardware issue, see if you can use another computer to confirm but if it's the same situation, you may have to contact OnePlus about warranty service.

Doogee N20 - Some phones are just hard to modify

After finally unlocking the bootloader, installed TWRP 3.6.0 and rotted with Magisk v23.0. Lets find a custom ROM that suits this phone - WRONG!
I have tried many types of ROM and so far it ends in soft brick. Need advise if you have any. My aim is to install a basic custom ROM , install pico or nano GAPP, and only install like 4 apps on it. phone, sms, navigation, music player etc.
I have tried the following ROM:
Phhusson-treble AOSP andriod version 9, 11 & 12.
GSI arm64 ab ROM
a so call stock ROM
I also tried installing the vendor.img as described here
I would like to use LineageOS but there doesn't seem to be one for this phone
I am now resorting to installing the stock firmware to make the phone work again, instruction here
If anyone has sucessfully rooted this phone using a basic ROM and GAPP please share how you did it and where your download was.

Why did phhuson fail ? That's the basic gsi, every other gsi are build on top of that. If that doesn't work, nothing will.

Fytdyh said:
Why did phhuson fail ? That's the basic gsi, every other gsi are build on top of that. If that doesn't work, nothing will.
Click to expand...
Click to collapse
I install - system-arm64 –ab
I did some research that the Doogee n20 is a arm64 and a+b .... Unless I got the wrong information.
I suspect there maybe some stock firmware files that needs to be installed as well to make it work properly.
A post said it needs vendor.img, I might try sourcing another copy.
Follow up - I got it un-bricked with the stock firmware (android 9) (link in my original post) .... Back to square one .

jackjack1885 said:
I install - system-arm64 –ab
I did some research that the Doogee n20 is a arm64 and a+b .... Unless I got the wrong information.
I suspect there maybe some stock firmware files that needs to be installed as well to make it work properly.
A post said it needs vendor.img, I might try sourcing another copy.
Follow up - I got it un-bricked with the stock firmware (android 9) (link in my original post) .... Back to square one .
Click to expand...
Click to collapse
Search treble info, it will tell you exactly any treble related information.

Fytdyh said:
Search treble info, it will tell you exactly any treble related information.
Click to expand...
Click to collapse
Many thanks, didn't do that step.
Did it now, it shows it needs system-arm64-ab
I got the right one. Not sure about the VNDK 28.0 doesn't really say on the webpage.
{
"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"
}
Tried android 9 (the phones original version) 11, and 12..... No luck.

follow advices from this https://forum.xda-developers.com/t/doogee-n20-twrp.4136331/
and this https://forum.xda-developers.com/t/...loop-after-any-custom-rom-doogee-n20.4357313/

Hey man, did you get it fixed?
Actually this device is A-only, but you should use Gsis A/B.
Most Phh based Gsi works almost perfectly for me.
You can try this:
- Download and install Twrp 3.6.1 here
- Download LineageOS 18.1 (lir) here Choose "arm64 bvZ" version
- Download stock rom here or Y9Plus variant here
- Extract the Gsi, and the vendor image from the stock rom
- I restarted in Twrp, go to wipe and select system, data, cache...
- Go install and flash the Gsi as system image, and vendor as vendor image
-reboot

AtS17 said:
Hey man, did you get it fixed?
Actually this device is A-only, but you should use Gsis A/B.
Most Phh based Gsi works almost perfectly for me.
You can try this:
- Download and install Twrp 3.6.1 here
- Download LineageOS 18.1 (lir) here Choose "arm64 bvZ" version
- Download stock rom here or Y9Plus variant here
- Extract the Gsi, and the vendor image from the stock rom
- I restarted in Twrp, go to wipe and select system, data, cache...
- Go install and flash the Gsi as system image, and vendor as vendor image
-reboot
Click to expand...
Click to collapse
Thanks for the links!
Are you able to add this old firmware please? https://cloud.mail.ru/public/mCzU/5PX4cKPfH
I can't download it, i found it on 4pda (Mod Action: Link removed)
I'm trying to delete the red "TEE key not write" message.