Database Develop

I uploaded 32bit recovery to 64bit version. How fix!

Hi.
By mistake I upload 32bit recovery to my 64 bit desire.
Factory Reset and Recovery don't work.
How can I fix this.
Please help me guys.

Don't worry, you will be fine. You need to boot into Fastboot and from the computer run
Code:
fastboot oem lock
and install the proper update for your phone. Do you have a RUU for your phone? If not, where are you and what is your carrier? Based on that I may have the right file for you.
nasiono said:
Hi.
By mistake I upload 32bit recovery to my 64 bit desire.
Factory Reset and Recovery don't work.
How can I fix this.
Please help me guys.
Click to expand...
Click to collapse

Thanks for help.
I from Poland.
I only unlock bootloader .
Smartphone was buyed in ERA center.
Sorry but i'm noob.
android 4.4.3
version: htc sense
software version: 1.14.118.1
level htc sdk api
compilation version 1.14.118.1 CL383628 release keys

No need to be sorry! From what you told me I imagine you are with T-Mobile. If you are with Orange let me know and I will see if I have the file you need. If you are with T-Mobile do this:
1. Get this file https://mega.co.nz/#!yFRFBQxS!84jrZOLXKCvamxSGTcHNIuGeL3onkk7mZrK5kzjAmQU
2. Boot into Fastboot mode
3. From the PC run
Code:
fastboot devices
and you should see a reference for your phone.
4. From the PC run
Code:
fastboot oem lock
5. Execute the file you downloaded in step 1 Do this:
5.1. Rename it to 0PCVIMG.zip [That is a zero on the first character]
5.2. Place it on the your SD card [on the root of the card]
5.3. Reboot to HBoot and it will automatically install.
6. This step is optional, but I would recommend it. Unlock the bootloader, install TWRP, install root, do a TWRP backup. OPS...BETTER NOT... I THINK WE'RE STILL WAITING FOR A RECOVERY FOR YOU PHONE. I would just unlock the bootloader and this way when a recovery comes out for your phone you will be all set.
7. You should be happy now... let us know.
Remember, be patient... some of these steps take time... even booting for the first time takes a long time.
nasiono said:
Thanks for help.
I from Poland.
I only unlock bootloader .
Smartphone was buyed in ERA center.
Sorry but i'm noob.
android 4.4.3
version: htc sense
software version: 1.14.118.1
level htc sdk api
compilation version 1.14.118.1 CL383628 release keys
Click to expand...
Click to collapse

Thanks again.
I don't know how install this. Do I have to put this file in sd-card and run HBOT ?
Or install it in another way?

Sorry, I thought it was a .exe file; it's not, it's a zip file. Do this:
1. Rename it to 0PCVIMG.zip [That is a zero on the first character]
2. Place it on the your SD card [on the root of the card]
3. Reboot to HBoot and it will automatically install.
Let us know how you made out.
nasiono said:
Thanks again.
I don't know how install this. Do I have to put this file in sd-card and run HBOT ?
Or install it in another way?
Click to expand...
Click to collapse

Now i want root . Haw i can do this.
Regards.

***** FORGET IT - YOU DO NOT HAVE RECOVERY YET *******
nasiono, the last sentence on the previous post reads: "Let us know how you made out." Did you do that? No. Also, in the last post, if you look at the lower right corner, there is a button that says Thanks! which you should hit, specially considering that in order to get the file that I shared with you costed me $15 or something like that.
ah... well... here you go... you better bring me a chicken or pig for me to roast for the weekend...
Download http://download.chainfire.eu/641/Sup...erSU-v2.40.zip and store it on the SD card, reboot to recovery, select install, select the file UPDATE-SuperSU-v2.40.zip and you should be all set.
nasiono said:
Now i want root . Haw i can do this.
Regards.
Click to expand...
Click to collapse

Need help tooo
jdmedeiros said:
***** FORGET IT - YOU DO NOT HAVE RECOVERY YET *******
nasiono, the last sentence on the previous post reads: "Let us know how you made out." Did you do that? No. Also, in the last post, if you look at the lower right corner, there is a button that says Thanks! which you should hit, specially considering that in order to get the file that I shared with you costed me $15 or something like that.
ah... well... here you go... you better bring me a chicken or pig for me to roast for the weekend...
Download http://download.chainfire.eu/641/Sup...erSU-v2.40.zip and store it on the SD card, reboot to recovery, select install, select the file UPDATE-SuperSU-v2.40.zip and you should be all set.
Click to expand...
Click to collapse
I have version 1.08.401.1 64bit but same problem since i flashed 32bit recovery . Have any one RUU or something for EU-64BIT 1.08.401.1????

"jdmedeiros" You helped me I appreciate, thank you very much.
I unlock the bootloader but when I try to "apply from sd card" smartphon immediately has reboot.
I returned to the starting point. How to root phone?

You're on a 64 bit device... you need to do this: http://forum.xda-developers.com/desire-510/development/root-root-htc-desire-510-t3002722
nasiono said:
"jdmedeiros" You helped me I appreciate, thank you very much.
I unlock the bootloader but when I try to "apply from sd card" smartphon immediately has reboot.
I returned to the starting point. How to root phone?
Click to expand...
Click to collapse

I put file " HTC-Desire-510-64bit-Root.img" in adb folder .
Next I run command "fastboot flash boot HTC-Desire-510-64bit-Root.img" everything OK.
1. Now i run "recovery".
2. Press Vol up +power button
3. Press "apply from sd"
Then smartphon is reboting to normal system.
How can I install supersu.zip ?

From the Play Store, as it says on the OP "Install SuperSU from Play Store. Select cancel everytime it asks to update. It WON'T work".
nasiono said:
I put file " HTC-Desire-510-64bit-Root.img" in adb folder .
Next I run command "fastboot flash boot HTC-Desire-510-64bit-Root.img" everything OK.
1. Now i run "recovery".
2. Press Vol up +power button
3. Press "apply from sd"
Then smartphon is reboting to normal system.
How can I install supersu.zip ?
Click to expand...
Click to collapse

I have two more question.
How do backup android with my aps , and recovery it after.
How install all my aps on sd card.

Hi.
I have this same problems.
Please again upload file from post http://forum.xda-developers.com/showpost.php?p=58805575&postcount=4 :
1. Get this file h t t p s://mega.nz /#!yFRFBQxS!84jrZOLXKCvamxSGTcHNIuGeL3onkk7mZrK5kzjAmQU (file is not longer avaiable ).

TWRP shows strange folder names (crypted?!)

hi,
I bought a new Huawei P10 lite phone, unlocked the bootloader, installed TWRP and with this I installed SuperSU via microSD card.
Everything worked fine, until now. Now I want to backup my current modified stock ROM, but TWRP failes.
I got the problem very fast: TWRP can read all files and folders on the microSD car, but not in the internal storage folder.
The file structure is like the following:
acct
boot
cache
config
data
...
etc
external_sd <-- the microSD card
mnt
...
sbin
sdcard
storage
...
Click to expand...
Click to collapse
Everything can be read by TWRP, except the sdcard folder.
Here he only shows strange names (crypted I guess):
something like:
2h8P9lGY8I1A884LMsBjaA
2u+nb0LdBNopRSa5LehsvB
75aTrCvYkWG+R+lrcRz6WA
DcwYkwSKokq8Rm5lYc4YYC
...
Click to expand...
Click to collapse
This strange folders occure within TWRP itself and also if I mount the storage to the computer via TWRP.
I also can not modify, delete or add anything in this cryted folder.
So what am I doing wrong? Why is this crypted and can not be read?
During my research I found this post on reddit with the same problem. But the solution is not clear to me and also not working.
Thanks for any help
greetings
Christopher
PS.: Here some specific information about the phone:
brand new Huawei P10 lite
model WAS-LX1A
build nr. WAS-LX1AC432B102
no updates avaible, checked twice
EMUI 5.1 with Android 7.0
TWRP v3.1.0-2 from here (named "TWRP_P10_Lite_Beta.img")

Hey
It's because your files are encrypted due to forceecnryption and dm-varity in the kernel you can try formating the data to see if it removes the encryption from the data.
My infos may not be correct you can read more about dm-varity and forceecnryption in the internet

aburezk said:
Hey
It's because your files are encrypted due to forceecnryption and dm-varity in the kernel you can try formating the data to see if it removes the encryption from the data.
My infos may not be correct you can read more about dm-varity and forceecnryption in the internet
Click to expand...
Click to collapse
Ok, thanks a lot. This was helful so far.
From what I read, I now must flash a new "boot.img" in order to disable force encryption. But where do I get such a file for my Huawei P10 lite (WAS-LX1A)? I did not found one. Maybe the phone is too new? Or am I just blind?
greetings

christopher2007 said:
Ok, thanks a lot. This was helful so far.
From what I read, I now must flash a new "boot.img" in order to disable force encryption. But where do I get such a file for my Huawei P10 lite (WAS-LX1A)? I did not found one. Maybe the phone is too new? Or am I just blind?
greetings
Click to expand...
Click to collapse
you can't find it anywhere

aburezk said:
you can't find it anywhere
Click to expand...
Click to collapse
Ok, so too new ... damn. That is very bad.

christopher2007 said:
Ok, so too new ... damn. That is very bad.
Click to expand...
Click to collapse
I managed to disable force encryption on my device
Download this and flash it
Backup your data and wipe data from twrp
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/

I tryed no-verity-opt-encrypt-6.0.zip but now do not start anymore... I have restore boot and system but none... what can I do? I think i will sell this p10 lite...

simona70 said:
I tryed no-verity-opt-encrypt-6.0.zip but now do not start anymore... I have restore boot and system but none... what can I do? I think i will sell this p10 lite...
Click to expand...
Click to collapse
i had the same issue by using no-verity-opt-encrypt-6.0.zip. The phone was brick after that.
Do you know your Build of your Phone ? If yes you can download the right Update.app from Huawei and extract the BOOT.IMG, RECOVERY.IMG and the SYSTEM.IMG (Maybe CUST.IMG) and restore it in the fastboot Mode. After that it started again to the UI.
If you dont know the Build of your Phone there will be some Fastboot oem commands to get it (i dont have them in my mind right now).
I flashed the ZIPs in TWRP after that with an external SD card witch arent crypted names...

ChipCollector said:
i had the same issue by using no-verity-opt-encrypt-6.0.zip. The phone was brick after that.
Do you know your Build of your Phone ? If yes you can download the right Update.app from Huawei and extract the BOOT.IMG, RECOVERY.IMG and the SYSTEM.IMG (Maybe CUST.IMG) and restore it in the fastboot Mode. After that it started again to the UI.
If you dont know the Build of your Phone there will be some Fastboot oem commands to get it (i dont have them in my mind right now).
I flashed the ZIPs in TWRP after that with an external SD card witch arent crypted names...
Click to expand...
Click to collapse
I solved using "update_data_full_public.zip" and clearing /data, after restoring previuos boot.img and system.img .
My phone was WAS-LX1AC432B102 4gb EMUI5.1 Android 7.0. I had bricked before and the only way to unbrick was to use "Warsaw-L21_C432B182_EU_SERVICE_androidhost.ru"
I do not trust to install data into a phone i can't backup and restore with TWRP... there is another way to make /data not crypted?

Exist the hope one day TWRP read also crypted /data or it is better search another phone?

ChipCollector said:
i had the same issue by using no-verity-opt-encrypt-6.0.zip. The phone was brick after that.
Do you know your Build of your Phone ? If yes you can download the right Update.app from Huawei and extract the BOOT.IMG, RECOVERY.IMG and the SYSTEM.IMG (Maybe CUST.IMG) and restore it in the fastboot Mode. After that it started again to the UI.
If you dont know the Build of your Phone there will be some Fastboot oem commands to get it (i dont have them in my mind right now).
I flashed the ZIPs in TWRP after that with an external SD card witch arent crypted names...
Click to expand...
Click to collapse
Hey, I am having the exact same problem, my phone is soft bricked after no-verity-opt-encrypt-6.0.zip. (https://forum.xda-developers.com/p10/help/stuck-device-booting-flashing-rom-t3713503).
I know the build of my phone, and I downloaded the update.app and extracted it to boot.img, recovery.img, system.img, but how exactly can I restore it in the fastboot mode. What commands?

fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
---------- Post added at 04:35 PM ---------- Previous post was at 04:32 PM ----------
Anymore I think P10lite is a lost cause. I sell to my mother. I bought a xiaomi redmi note 4 global. Never again a Huawei. What a disappointment.

You'll sale your phone to your? Mother? To your mother?
Anyway the same story is on redmi note and all xiaomi
Phones
All the Chinese are difficult to modify.
I was have all Nexus thru 2011 very easy phones but the Chinese... My...

I have a doubt, I have bundled it when trying to install root on my device and I ended up in bootloop what I did was install a (official) rom which when entering the internal files, the folders were with strange names appear, so you recommend removing the credentials (decrypt), to be able to install root? My Device is Xiaomi mi A2

Bro did you find a solution..I am having same problem help

Had my phone bricked two days ago after a failed Motorola system update. Decided do ditch it and go with LineageOS, wich I got working after a few failed install attempts. When I tried to acess my internal storage, I had only those randomly named folders. Deleted them all, but couldn´t write to my storage after. Even tried a camera app, and it said that couldn´t work without a sdcard.
SOLUTION: boot recovery on TWRP > Wipe > Advanced Wipe> select ONLY internal storage > swipe to wipe :good:
Rebooted after internal storage wipe and everything is fine now. It seems all the install attempts made some sort of mess.

chimeralounge said:
Had my phone bricked two days ago after a failed Motorola system update. Decided do ditch it and go with LineageOS, wich I got working after a few failed install attempts. When I tried to acess my internal storage, I had only those randomly named folders. Deleted them all, but couldn´t write to my storage after. Even tried a camera app, and it said that couldn´t work without a sdcard.
SOLUTION: boot recovery on TWRP > Wipe > Advanced Wipe> select ONLY internal storage > swipe to wipe :good:
Rebooted after internal storage wipe and everything is fine now. It seems all the install attempts made some sort of mess.
Click to expand...
Click to collapse
Legend. This fixed the same issue we were facing on the t510 Samsung tablet. Saved us a lot of trouble. Thanks for this.

memz180 said:
Legend. This fixed the same issue we were facing on the t510 Samsung tablet. Saved us a lot of trouble. Thanks for this.
Click to expand...
Click to collapse
-----------
Cool, glad to help! In fact, this issue happened to me once again a few weeks back, when LegacyOS updated. I had this "f*** here we go again" moment, but before wiping, I decided to use TWRP > Advanced > Fix Content. Not only I got the system working again, but *all my data was intact*. System updates are messing file tables, apparently.
I want to marry TWRP.

chimeralounge said:
Had my phone bricked two days ago after a failed Motorola system update. Decided do ditch it and go with LineageOS, wich I got working after a few failed install attempts. When I tried to acess my internal storage, I had only those randomly named folders. Deleted them all, but couldn´t write to my storage after. Even tried a camera app, and it said that couldn´t work without a sdcard.
SOLUTION: boot recovery on TWRP > Wipe > Advanced Wipe> select ONLY internal storage > swipe to wipe :good:
Rebooted after internal storage wipe and everything is fine now. It seems all the install attempts made some sort of mess.
Click to expand...
Click to collapse
God bless you! i've struggle with this s]+t for hours!

what worked for me is installing siankatabg-twrp , now i can see names fine
after that i changed back to official version (which was missy before) and still fine !!!!!!!!
then installed orange fox (which was missy before) and still fine !!!!!!!!
WTH !!!!!!!!!!!!
so i think best shot (if u dont have siankatabg-twrp) is installing codeworkx (Lineage recovery) make sure all good then go back to ur favorite.
lemme know if its works

Cannot mount system, vendor, product after wiping like advised on Eliterom install

Hello! I was following the guide of wiping everything except internal storage and sdcard like the guide said. However now i only see TWRP folder on the /sdcard when trying to flash zip. How do i transfer files, or is there some fastboot file to flash or a guide which i can use to bring my device back alive? Fastboot and TWRP boots, but i cannot access some partitions. Thank you
Edit: Already tried to flash the boot.img that was on the EliteROM v4 zip, however the Product, Vendor, Version, Cust and Data versions are still messed up. I need help on repartinioning advice.

Also now i managed to flash system.imgi, but the partitions need to be resized probably to be used. How is the repartitioning possible the easiest way?

That's very wrong. You only needed to wipe system, data and cache,

sniperlife:D said:
That's very wrong. You only needed to wipe system, data and cache,
Click to expand...
Click to collapse
Hassanmirzans guide says " Wipe Everything in wipe section (dont wipe sdcard) and Format Data & Change FileSystem to f2fs otherwise phone wont boot,,, and reboot twrp and follow next steps,,," which is what i did.
Do you have any more tips? Currently i cannot even use the update.app method at all.
Edit: I just did try the update.zip method, and it says "Software install failed! The update package does not exist. Please download the package again." My computer recognizes the phone as Huawei honor 9p lite now, and i have checked that the UPDATE.APP is under dload folder. Tried with internal storage as well as external sd already.
Edit2: was corrupt UPDATE.APP, now it says "Software install failed! Incompabile package . Please download the package again." Or something similar, do i need to reflash OEM info or something to make my device Honor 5C again?

I solved this because of przemas2468 at modaco. He had posted the OEMinfo file if you manage to mess up your device, which can be found from here: http://www.mediafire.com/file/fn2pv4uucjh63xo/oeminfo_b100_c432.zip

onnz423 said:
I solved this because of przemas2468 at modaco. He had posted the OEMinfo file if you manage to mess up your device, which can be found from here: http://www.mediafire.com/file/fn2pv4uucjh63xo/oeminfo_b100_c432.zip
Click to expand...
Click to collapse
What was your version and model? We have some oeminfo file that may save you from such situations

shashank1320 said:
What was your version and model? We have some oeminfo file that may save you from such situations
Click to expand...
Click to collapse
Thanks man, however i already got the OEMINFO file, and will upload it into a mirror soon. Apperantly it is not possible on XDA to lock thread.

onnz423 said:
Thanks man, however i already got the OEMINFO file, and will upload it into a mirror soon. Apperantly it is not possible on XDA to lock thread.
Click to expand...
Click to collapse
Share the link i will update to my repository and anyone can use. Its locked and a common thread for all models.

shashank1320 said:
Share the link i will update to my repository and anyone can use. Its locked and a common thread for all models.
Click to expand...
Click to collapse
Here you go: https://mega.nz/#!QTZV2YJA!nZASaoDeTiGAx1bwNOu_pnTcGLiraGCqOXMwPkvffj8
This at least worked for NEM-L21. The UPDATE.APP process would not succeed without this file.

onnz423 said:
Here you go: https://mega.nz/#!QTZV2YJA!nZASaoDeTiGAx1bwNOu_pnTcGLiraGCqOXMwPkvffj8
This at least worked for NEM-L21. The UPDATE.APP process would not succeed without this file.
Click to expand...
Click to collapse
Thanks for sharing this. I will update the repository thread asap

I might need some assistance. (EVA-L19)

After unlocking the bootloader, installing TWRP recovery and rooting my phone with SuperSU (v2.82), I was preparing to install a custom ROM (more specifically the Resurrection Remix 7.1.2.) all in all, things ended up going out of hand and I accidentally deleted my internal storage, losing every single bit of my existing ROM, not to mention the RR ROM file as well. Now when I try to wipe, I can't, it usually says "Failed to mount '/data' (Device or resource busy) and "Unable to mount storage".
I tried using ADB sideload but to no success, only the same message. What I can understand is that the previous data is gone, I tried changing the format of data, system and cache to FAT & exFAT but it still did not resolve my issue.
I'm out of options here, I don't want to have to give up this phone because of my stupidity.
I also tried flashing the LineageOS 14.1 ROM to see if anything was different, here is what it said:
Installing zip file '/sideload.package.zip'
Target: HUAWEI/EVA-L09/HWEVA:7.0/HUAWEIEVA-L09/C432B361:user/release-keys
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
detected filesystem exfat for /dev/block/bootdevice/by-name/userdata
mount: failed to mount /dev/block/bootdevice/by-name/userdata at /data: Device or resource busy
unmount of /data failed; no such volume
Patching system image unconditionally...
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Script succeeded: result was [1.000000]
Although it said succeeded it clearly did not work and I am sitting without a ROM. I'm not smart when it comes to these things please help a guy out.
(Is there a way to going back to completely stock EMUI 5.0?)
Cheers.

EMUI 5.01 requires encryption, which you obviously removed.
Search for DC Unlocker, it can probably fix it for 25 Euros

zgfg said:
EMUI 5.01 requires encryption, which you obviously removed.
Search for DC Unlocker, it can probably fix it for 25 Euros
Click to expand...
Click to collapse
I know this is awkward to ask and all, but how exactly do I go about this, I'm pretty lost and I have minimal experience with this stuff..

I never had to use it but here is their portal (with download info, prices, instructions, etc)
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
If you search on XDA or search on Google for eg XDA Huawei DC Unlocker you will find threads with first hands experience (I've seen them several tines but didn't save to Favorites)

zgfg said:
I never had to use it but here is their portal (with download info, prices, instructions, etc)
If you search on XDA or search on Google for eg XDA Huawei DC Unlocker you will find threads with first hands experience (I've seen them several tines but didn't save to Favorites)
Click to expand...
Click to collapse
I'm terribly sorry for being THIS stupid. As I'm looking into this even more, I'm conflicted about the credit amount I need, been scrolling through the list and I can't really find my problem involving firmware I suppose.

People usually buy for 15 Euros. It may help you, Chrome will automatically translate from German
https://www.android-hilfe.de/forum/...-wiederherstellung-mit-dc-phoenix.818669.html

I'm not educated about DC Unlocker but that is NOT neccesary here. You can easily repair the /data partition by flashing the stock recovery via fastboot, formatting data with that stock recovery and then flashing TWRP again. After that TWRP should be able to read the data partition again.
You can easily go back to stock completely and even restore your bootloader by doing a "rollback" to Android 6. (dload method). After that you can normally upgrade from there though EMUI to the latest version of stock.

christopherpfister said:
I'm not educated about DC Unlocker but that is NOT neccesary here. You can easily repair the /data partition by flashing the stock recovery via fastboot, formatting data with that stock recovery and then flashing TWRP again. After that TWRP should be able to read the data partition again.
You can easily go back to stock completely and even restore your bootloader by doing a "rollback" to Android 6. (dload method). After that you can normally upgrade from there though EMUI to the latest version of stock.
Click to expand...
Click to collapse
I've tried using eRecovery to format the data but to no success, I can't even use the touch screen for some reason, (I know about the volume keys, but when it comes to selecting the Wi-Fi, there is no success whatsoever). If you do know a fix for this, could you possibly walk me through this?

Hexagonal said:
I've tried using eRecovery to format the data but to no success, I can't even use the touch screen for some reason, (I know about the volume keys, but when it comes to selecting the Wi-Fi, there is no success whatsoever). If you do know a fix for this, could you possibly walk me through this?
Click to expand...
Click to collapse
UPDATE: I flashed the stock recovery image and it showed me the wipe cache partition and factory data and system reset, I tried both, only the cache one succeeded, the other one failed. I saw a post that directed you to flash boot.img, recovery.img, recovery2.img and then system.img, I did that, but I couldn't boot into my phone - the good thing is however! That I can use my touchscreen in the recovery now.
Obviously the second time booting into EMUI recovery it prompts me to 'Download latest version and recovery', I try to connect to my Wi-Fi, seems okay but then it suddenly fails. More specifically it says 'Getting package info failed'. Save me please :crying:

So this "erecovery" never worked in any way for me (the one which offers you to download the latest version).
Instead you need the normal recovery you already used. Formatting failed for me the first time too, try it again and then it will try to format "low-level" which worked for me.
Go directly into fastboot from that, flash TWRP and go directly into TWRP.
After that should be able to use /data in TWRP. As soon as you are able to start TWRP without any error messages (like "Device busy" or something) go to Wipe and then format data.
Important: check which partition type you have! For EMUI you need "f2fs" and for lineage you need "ext4". You can see and change that in TWRP under Wipe -> "change or repair filesystem".
If you have any more questions, just ask.

christopherpfister said:
So this "erecovery" never worked in any way for me (the one which offers you to download the latest version).
Instead you need the normal recovery you already used. Formatting failed for me the first time too, try it again and then it will try to format "low-level" which worked for me.
Go directly into fastboot from that, flash TWRP and go directly into TWRP.
After that should be able to use /data in TWRP. As soon as you are able to start TWRP without any error messages (like "Device busy" or something) go to Wipe and then format data.
Important: check which partition type you have! For EMUI you need "f2fs" and for lineage you need "ext4". You can see and change that in TWRP under Wipe -> "change or repair filesystem".
If you have any more questions, just ask.
Click to expand...
Click to collapse
So what you're saying is, as soon as I get my data sorted and my partition set to the right one I should be able to install the custom ROM. I could use data and even formatted it, tried installing Lineage but I must've had the storage on the wrong type, now I'm back with the same issue, I'll try to fix it and post my results here. Thank you!

Hexagonal said:
So what you're saying is, as soon as I get my data sorted and my partition set to the right one I should be able to install the custom ROM. I could use data and even formatted it, tried installing Lineage but I must've had the storage on the wrong type, now I'm back with the same issue, I'll try to fix it and post my results here. Thank you!
Click to expand...
Click to collapse
Update: It did NOT work, tried flashing LineageOS through ADB sideload, it was going fine before the bar completely filled up around 50% of the way done, it said 'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Help me, I'm begging you, at the moment I don't have an access to a microSD that has the capacity to hold the stock files to do the dload method, therefore this is my only hope.

Hexagonal said:
Update: It did NOT work, tried flashing LineageOS through ADB sideload, it was going fine before the bar completely filled up around 50% of the way done, it said 'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Help me, I'm begging you, at the moment I don't have an access to a microSD that has the capacity to hold the stock files to do the dload method, therefore this is my only hope.
Click to expand...
Click to collapse
Whats the error? Why doesn't it work? What happens when you try to boot?

christopherpfister said:
Whats the error? Why doesn't it work? What happens when you try to boot?
Click to expand...
Click to collapse
That's what I'm trying to figure out, when I try to boot in it's just stuck on a boot loop. Unfortunate..

Remember that you have to what *a while* for the first boot. Only if you see no change after 5-8 minutes or so something is definitely wrong.
Have you checked in TWRP if your /data partition is ext4?

christopherpfister said:
Whats the error? Why doesn't it work? What happens when you try to boot?
Click to expand...
Click to collapse
christopherpfister said:
Remember that you have to what *a while* for the first boot. Only if you see no change after 5-8 minutes or so something is definitely wrong.
Have you checked in TWRP if your /data partition is ext4?
Click to expand...
Click to collapse
I know, but it was flashing the Huawei logo and the unlocked bootloader warning continuously. It was set on EXT4 but as I was saying, it said script succeeded at 50%.

Hexagonal said:
'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Click to expand...
Click to collapse
That just said that /system partition is ext4. That is default even for stock I believe. You need to check for /data.

christopherpfister said:
That just said that /system partition is ext4. That is default even for stock I believe. You need to check for /data.
Click to expand...
Click to collapse
I deliberately set the data partition to EXT4 before installing

Hexagonal said:
I deliberately set the data partition to EXT4 before installing
Click to expand...
Click to collapse
Can you check in TWRP if it actually says /data is ext4?
Which lineage are you trying to install? Don't you need a vendor.zip for some of them?

/data is indeed on EXT4, and I was installing the one that was on the room section.

Question I might have bricked my phone, I need help

I am just new to this flashing custom roms or firmware and twrp also. And dumb enough to not back it up.
I wanted to install arrow os in my phone. When I was about to wipe data, cache and dalvik, I accidentally checked metadata also and wiped. Then problems created more problems.
problems right now:
I cant put a file in my storage
Internal Storage is just blank on my pc
No OS
TWRP on both slots
please help me i really needed help and knowledge about it
I hope the attachment helps
EDIT--
Solutions to my problems:
WHEN you softbrick your phone and you only have fastboot and nothing else
Thanks to this guy..
SOLUTION: download your original firmware but choose the fastboot one and not recovery after download just unzip. Double click flash_all.bat and its back to square one.
WHEN you dont know how to flash or the file you have is .img
SOLUTION: find a guide in xda because apparently you can install a .img file in "fastbootd" mode
the guides here: https://forum.xda-developers.com/t/...sues-all-without-any-custom-recovery.4337099/
COMMENT: not the usual thats what on top of youtube search.
WHEN you see errors in twrp/orangefox recovery you might get panic and search for solution.
COMMENT: try to find and use a solution that doesnt delete something first. In my experience it got bricked even more.
Thanks to the people who commented back on my post and helping me get to know what to do next.

Try putting the stock ROM on a SD card or usb (if you have a dongle).

georg3_ said:
Try putting the stock ROM on a SD card or usb (if you have a dongle).
Click to expand...
Click to collapse
SD card that you put on beside the sim? if yes
Do I download stock ROM in official website? Cus I dont have 1 right now
then flashing it there by using twrp? is that how its gonna run? because i really dont wanna assume and create another problem

Try flashing this stock ROM (global) from a SD card, in TWRP. It's a recovery package, so you can install it as any zip.
Also, can you boot into fastboot/bootloader from TWRP?

Plus, where did you get the ArrowOS image? There are no builds, official or not.

georg3_ said:
Plus, where did you get the ArrowOS image? There are no builds, official or not.
Click to expand...
Click to collapse
I found it here
It is made my myst33d and it is a beta build
im getting a sd card right now to test it out
And yes I still can go to fastboot/bootloader from twrp

I cant seem to find my file in twrp... even in file manager
the file is int .tgz must I change it to .zip?

raikiro1 said:
I cant seem to find my file in twrp... even in file manager
Click to expand...
Click to collapse
Is the twrp detecting your sd card？try click on the Install image and change to install zip

can you sideload?

I can now see it, I think I reflashed twrp, now I can, but I cant install because of failed to mount system_root and I have done change file system of data to Ext4. when it resets it comes back to f2fs
edit: change file system of data to Ext4 failed
edit2: thank you guys really for commenting back and helping me
is no verity affecting it? cus I am not able to install it now

you should format data and put the arrow build in it, maybe it will work

J6idot said:
you should format data and put the arrow build in it, maybe it will work
Click to expand...
Click to collapse
I have changed the data to Ext4, fomarted, wiped again the data,dalvik and cache
I have a Redmi Note 10S Rosemary from xiaomiupdater but I still cannot install the rom cus there is a error " Error installing zip file /sdcard1/thefile."
I tried to install no verity opt encrypt but failed and says updater process ended with ERROR: 1
Error installing zip file "sdcard1/thefile"

raikiro1 said:
I cant seem to find my file in twrp... even in file manager
the file is int .tgz must I change it to .zip?
Click to expand...
Click to collapse
Must change it to zip.
EDIT: Extract the file, there's a zip or img inside.

raikiro1 said:
I have changed the data to Ext4, fomarted, wiped again the data,dalvik and cache
I have a Redmi Note 10S Rosemary from xiaomiupdater but I still cannot install the rom cus there is a error " Error installing zip file /sdcard1/thefile."
I tried to install no verity opt encrypt but failed and says updater process ended with ERROR: 1
Error installing zip file "sdcard1/thefile"
Click to expand...
Click to collapse
Try to sideload it, maybe it'll work.

georg3_ said:
Must change it to zip.
Click to expand...
Click to collapse
Should have said "extract the file, there's a zip or img inside", don't change the file extension.

Update: I found the guide how to sideload ... just change the Ext4 to F2fs
[Tutorial] TWRP ADB Sideloading
Alternative solution: OTG usb flash drive - With one of these, you can store a ROM zip safely, and still format ‘userdata’ to f2fs or EXT4. TWRP ADB Sideloading Requirements: Mac | Linux | Windows PC / Laptop and TWRP Custom Recovery Moto G...
forum.xda-developers.com
and I was able to sideload it and then got MIUI finally
what worried me is there were still errors like system_root, vendor and product... and its running fine now I guess but im back on track to make it to arrow OS.... I hope no mistakes this time like deleting metadata.
Thank you all who replied to this post , I really do. Thank you

raikiro1 said:
Update: I found the guide how to sideload ... just change the Ext4 to F2fs
[Tutorial] TWRP ADB Sideloading
Alternative solution: OTG usb flash drive - With one of these, you can store a ROM zip safely, and still format ‘userdata’ to f2fs or EXT4. TWRP ADB Sideloading Requirements: Mac | Linux | Windows PC / Laptop and TWRP Custom Recovery Moto G...
forum.xda-developers.com
and I was able to sideload it and then got MIUI finally
what worried me is there were still errors like system_root, vendor and product... and its running fine now I guess but im back on track to make it to arrow OS.... I hope no mistakes this time like deleting metadata.
Thank you all who replied to this post , I really do. Thank you
Click to expand...
Click to collapse
no problem next time installing, stick to sideloading, less room for error

I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update

raikiro1 said:
I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update
Click to expand...
Click to collapse
A12 shouldn't be a problem.
Probably you should flash another vbmeta.img.
OR
I don't know if there is an .img twrp around, but if there is you can:
Code:
fastboot boot {recovery.img}
and then [Advanced]>[Install Recovery Ramdisk].

raikiro1 said:
I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update
Click to expand...
Click to collapse
what vbmeta are you using?