Edit: Okay, maybe what I am saying isn't very clear. I'll recap:
I was on ArrowOS (Android 11) this morning and decided to switch to the beta version of ArrowOS, based on Android 12. What I did exactly is, installing the rom, then wiping cache/dalvik and then formatting data. I can boot into ArrowOS, it works fine. The problem is, when I boot into TWRP, there is no prompt for a password, and internal storage shows 0mb. The log says that the data partition cannot be mounted. I tried formatting data again, and the partition succeeds to mount (at least nothing says the opposite in the logs), but I have this error in the logs: "E:Unable to decrypt FBE device". Internal storage still at 0mb.
When I boot into ArrowOS after doing that, and then go back to TWRP after setting everything up, data partition fails to mount again. (when restarting device, TWRP says that there is no OS installed even though ArrowOS is installed and clearly working)
See original post.
Update: Definitely a ArrowOS bug with the Android 12 version. Reinstalled the Android 11 one, and TWRP works as it should.
No ArrowOs bug. The same thing happens on AOSP 12.
majster95 said:
No ArrowOs bug. The same thing happens on AOSP 12.
Click to expand...
Click to collapse
Okay. I tried reinstalling the ArrowOS beta and it does the same. I can't remember what I did for the internal storage to be decrypted so that I can reinstall the stable one.. can you help me, please? Stuck with "E:Enable to decrypt FBE device"
meirioon said:
Okay. I tried reinstalling the ArrowOS beta and it does the same. I can't remember what I did for the internal storage to be decrypted so that I can reinstall the stable one.. can you help me, please? Stuck with "E:Enable to decrypt FBE device"
Click to expand...
Click to collapse
Use adb sideload to revert back to stable.
majster95 said:
Use adb sideload to revert back to stable.
Click to expand...
Click to collapse
I've never heard of adb sideload before, I can see it in my TWRP. What am I supposed to do with it? It says "Starting ADB sideload feature..."
You must have installed adb drivers and adb on PC. When configured, connect phone to PC, enable adb sideload in TWRP and type in command line: adb sideload <path_to_file>. Or just copy Rom package on SDcard and flash.
majster95 said:
You must have installed adb drivers and adb on PC. When configured, connect phone to PC, enable adb sideload in TWRP and type in command line: adb sideload <path_to_file>. Or just copy Rom package on SDcard and flash.
Click to expand...
Click to collapse
I can't install the rom via SD card, I get an error. And I did exactly what you said with ADB sideload, it says: "Unable to find partition for path '/system_root'
Failed unmounting system"
I really can't remember what I did earlier to solve my problem.. I was able to plug my phone to my PC and copy the rom into my internal storage and then flash it but not anymore, on my PC it just shows "Internal storage" with no size at all
I managed to fix it again, yay! I'll stick to Android 11 for now. (I wiped all the partitions I could and then only I used ADB sideload to flash rom)
Well, I lied.. I'm now stuck on the boot animation of ArrowOS. Or maybe I have to wait a very long time before the first start because I installed the rom via ADB sideload? Doesn't seem normal, It's been ~5 minutes on this boot animation (I'll try installing another rom I guess)
Did you format data ?
majster95 said:
Did you format data ?
Click to expand...
Click to collapse
ADB sideload just failed, I retried with another ROM and it worked ; see my post on TWRP for sweet, you'll understand (you liked it)
I had the same problem but the problem was solved when using the external memory, maybe not the ideal solution but this method works fine anyway
bassemhemdan said:
I had the same problem but the problem was solved when using the external memory, maybe not the ideal solution but this method works fine anyway
Click to expand...
Click to collapse
It didn't for me.
meirioon said:
It didn't for me.
Click to expand...
Click to collapse
Use sd card, I think it will work fine
bassemhemdan said:
Use sd card, I think it will work fine
Click to expand...
Click to collapse
I used SD card, it failed
Is there a twrp made for a12 support?
I think a11 twrp doesn't gets the job done. May be wait for a12 twrp
aakashmaji16 said:
Is there a twrp made for a12 support?
I think a11 twrp doesn't gets the job done. May be wait for a12 twrp
Click to expand...
Click to collapse
Not yet, sadly
Related
Hey guys,
Today I attempted to root my HTC One. I successfully unlocked it and successfully flashed twrp 2.5 onto my phone. Without creating a backup and after flashing superuser and arhd 11.0 my phone would only boot into bootloader. Then I found I had trouble going back into recovery. I tried reflashing twrp and it worked and led me back into recovery. I was unable to find any of the ROMs I put into the internal memory and I get an error that says I am unable to mount data. I've tried flashing cwm recovery, which only lead to booting into bootloader, and then back to twrp which worked at first, but now I can't get either to work. I've been at this for hours. Hope any of you guys could help me out. Thanks in advance!
Also, I think my problem began by trying to flash arhd 11.0 from stock without doing a full wipe.
Update: Was able to get twrp to work again by clearing cache, but still unable to mount data.
This is an error i see inside twrp.
E : Unable to mount '/data'
E : Unable to recreate /data/media folder.
Updating partition details...
E : Unable to mount '/cache'
E : Unable to mount '/data'
E : Unable to mount internal storage.
E : Unable to mount /data/media during GUI startup
E : Unable to mount '/cache'
E: TWFunc : : Copy_Log -- Can't open destination
etc...
Click to expand...
Click to collapse
Update: SOLVED. Tried flashing Viper Rom and it worked great.
I believe that you install ARHD 11 from a 4.1 based rom, right? If that's the case, moving from 4.1 to 4.2 will mess up your data structure a bit. Because you have flashed arhd 11, all the rom files you had put earlier on 4.1 will be at other folder. My advice is you boot into twrp, open adb sideload (advance menu). On your computer use "adb sideload rom.zip" (rom.zip is the name of the rom you wanna flash). After it loaded the rom to the sd card, reboot to bootloader and you should see a file named sideloaded.zip. flash it. After finish, clear cache and reboot system.
or you can search in media/0
hope it helps
ryryzz said:
I believe that you install ARHD 11 from a 4.1 based rom, right? If that's the case, moving from 4.1 to 4.2 will mess up your data structure a bit. Because you have flashed arhd 11, all the rom files you had put earlier on 4.1 will be at other folder. My advice is you boot into twrp, open adb sideload (advance menu). On your computer use "adb sideload rom.zip" (rom.zip is the name of the rom you wanna flash). After it loaded the rom to the sd card, reboot to bootloader and you should see a file named sideloaded.zip. flash it. After finish, clear cache and reboot system.
or you can search in media/0
hope it helps
Click to expand...
Click to collapse
So I should sideload and flash a 4.1 based rom or a 4.2?
I've tried sideloading ARHD 11 and it brings me into the same bootloader loop. Could you send me a link to a ROM that may work?
Here's the steps I am taking if it helps;
1. fastboot erase cache
2. fastboot flash recovery twrp.img
3. go into recovery
4. adb sideload arhd11
5. reboot into recovery
6. flash sideload
7. reboot system
8. gives me a message saying my phone is not rooted would I like to install SuperSU now?
9. regardless of if i put 'do not install' or 'swipe to install' phone reboots into bootloader and I start over with the same problem
Click to expand...
Click to collapse
zasuncion said:
So I should sideload and flash a 4.1 based rom or a 4.2?
I've tried sideloading ARHD 11 and it brings me into the same bootloader loop. Could you send me a link to a ROM that may work?
Here's the steps I am taking if it helps;
Click to expand...
Click to collapse
Can you access recovery?
If yes, adb push name_of_rom.zip /sdcard/
rom will now be on your sdcard after the transfer. install it.
all roms using aroma installer crash sometimes, just keep trying.
edit: IF you can't find it, select install zip from sideload in recovery and command
adb sideload name_of_rom.zip
after the transfer it will begin to install automatically - you shouldn't need to reboot after a sideload.
redbull123 said:
Can you access recovery?
If yes, adb push name_of_rom.zip /sdcard/
rom will now be on your sdcard after the transfer. install it.
all roms using aroma installer crash sometimes, just keep trying.
Click to expand...
Click to collapse
Yes, I can access recovery. Just tried this. After flashing ARHD11 again I am still rebooting into bootloader.
Maybe it's just the ROM itself that I'm having trouble with? Could anyone direct me to one that will work for sure in my case?
Also after every flash, when I choose to reboot, twrp gives me a message saying my phone is not rooted and if I should install SuperSU. Should I say yes or not install? or is there a problem with flashing the ROM?
zasuncion said:
Yes, I can access recovery. Just tried this. After flashing ARHD11 again I am still rebooting into bootloader.
Maybe it's just the ROM itself that I'm having trouble with? Could anyone direct me to one that will work for sure in my case?
Also after every flash, when I choose to reboot, twrp gives me a message saying my phone is not rooted and if I should install SuperSU. Should I say yes or not install? or is there a problem with flashing the ROM?
Click to expand...
Click to collapse
So ARHD goes through and installs (as in gets to 100% in aroma) then reboots to bootloader?
Sent from my HTC One using xda premium
redbull123 said:
So ARHD goes through and installs (as in gets to 100% in aroma) then reboots to bootloader?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Yes. And the only way to get back into recovery from there is to reflash. I also can't use cwm, I can only use twrp. If that means anything.
Hey guys, I accidentley wiped my sdcard when I reunlocked the bootloader. I have a custom rom that was on previously but its stock in a loop. I tried to push another room using adb sideload but when i do I got * Cannot read 'sideload'. I dont know any other way i can connect the phone to computer to flash another rom. please help.
Thanks
Update:
I can push the rom but i get this error when trying to install "E: unable to mount 'data' "
p1mpin said:
Hey guys, I accidentley wiped my sdcard when I reunlocked the bootloader. I have a custom rom that was on previously but its stock in a loop. I tried to push another room using adb sideload but when i do I got * Cannot read 'sideload'. I dont know any other way i can connect the phone to computer to flash another rom. please help.
Thanks
Update:
I can push the rom but i get this error when trying to install "E: unable to mount 'data' "
Click to expand...
Click to collapse
when I had that problem, I ended up wiping everything and then rebooted to recovery and it finally worked.
p1mpin said:
Hey guys, I accidentley wiped my sdcard when I reunlocked the bootloader. I have a custom rom that was on previously but its stock in a loop. I tried to push another room using adb sideload but when i do I got * Cannot read 'sideload'. I dont know any other way i can connect the phone to computer to flash another rom. please help.
Thanks
Update:
I can push the rom but i get this error when trying to install "E: unable to mount 'data' "
Click to expand...
Click to collapse
Try what @JudgeFutta said. The error's most likely due to corrupt partitions.
p1mpin said:
Hey guys, I accidentley wiped my sdcard when I reunlocked the bootloader. I have a custom rom that was on previously but its stock in a loop. I tried to push another room using adb sideload but when i do I got * Cannot read 'sideload'. I dont know any other way i can connect the phone to computer to flash another rom. please help.
Thanks
Update:
I can push the rom but i get this error when trying to install "E: unable to mount 'data' "
Click to expand...
Click to collapse
Try to get in Recovery and from mount option mount system and then try it will work or try this
Make Sure HTC Drivers are installed and ADB is already working
1. Reboot into TWRP
2. in TWRP, Hit andvanced and find Sideload
3. Swipe to start Sideload
4. Open a CMD Prompt window and Change Directories to where your adb.exe is
5. type adb devices and it should show your device conntected and say sideload
6. Your ZIP file should already be in your adb folder
7. You are now ready to push the zip.....
8. type adb sideload nameofzip.zip
9. Wait until it says 100% and reboot back into recovery to flash the ROM
10. If hitting power does not make the screen come one, type adb reboot recovery
11. if adb reboot recovery does not work, hold power and volume down until it reboots to fastboot then go to recovery
ADB Push from Recovery - If Sideload Fails For You
adb push rom.zip /data/media/0/
Be sure u r in Recovery when using ADB Push command.
Thanks guys. What i found out is that i had a corrupt partition so I formated the sdcard since there was nothing on it and it worked. I pushed the rom through adb but i didnt do the sideload method. I have liquid smooth on it now but I want a sense rom. any suggestions for a good one?
p1mpin said:
Thanks guys. What i found out is that i had a corrupt partition so I formated the sdcard since there was nothing on it and it worked. I pushed the rom through adb but i didnt do the sideload method. I have liquid smooth on it now but I want a sense rom. any suggestions for a good one?
Click to expand...
Click to collapse
Why not try the best Sense rom available. http://forum.xda-developers.com/showthread.php?t=2502430
Gd luck
User420s said:
Why not try the best Sense rom available. http://forum.xda-developers.com/showthread.php?t=2502430
Gd luck
Click to expand...
Click to collapse
@p1mpin Can vouch for that ROM, it's amazing. Might also want to flash Kangaroo Kernel while you're at it. It'll give you great battery life.
Hello,
I have a problem and I hope this is the right place for help.
I try my best to explain everything.
So I tried to root my OnePlus 3T.
Everything was going good. I installed TWRP and was able to use it.
Next I wanted to flash no-verity-opt-encrypt-5.1.zip.
I messed something up and wiped all my cache and my data.
I didn't noticed it at this point, so I tried to install SuperSU.
I don't know, if it was successful, but I guess not.
Then I restarted my phone and I stuck in bootloading. It was an endless loading until, my battery was empty.
I charged my phone up and was able to start TWRP.
Now I have my OnePlus 3T without an OS installed.
I downloaded the OS from OnePlus and tried to put it on my connected phone with the ADB Sideload, but my phone can't install ADB Sideload. So I can't put the OS on my phone to install it.
I don't know what to do and how I can put my OS on my phone.
One Idear was to put it on a USB Stick which fits in my phone, but I don't know.
I hope, someone can help me.
Sorry for my bad english, btw.
Boot into twrp and connect the phone to your notebook. If you can copy the OOS Rom to your phone, just flash it.
If not, you have to use the unbrick guide, just follow it and your phone should be alright again.
Boot into TWRP recovery and connect op3t to PC and move os to internal memory. Flash os from TWRP....
Sent from my ONEPLUS A3003 using Tapatalk
faffaz said:
Boot into TWRP recovery and connect op3t to PC and move os to internal memory. Flash os from TWRP....
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Do EXACTLY as this guy said. I had the EXACT same problem. I was doing a root, accidentally wiped everything including the OS, and thought I was ****ed. A little while later I went to the OnePlus website, downloaded the latest available OS and copied it over to my phone's internal memory while it was booted into TWRP. I then flashed it via TWRP and was good as new. Don't panic and you should be fine.
If adb sideload is not working. Then you can follow this method. Download adb tools from Google. Then their is a option of push the rom in the adb tools. Just keep the phone connected to notebook in twrp mode and then via that software push the rom into the internal of phone. Then just flash manually. It's done. I did this, as the same thing happened with me some days ago.
Nicky Carts said:
Do EXACTLY as this guy said. I had the EXACT same problem. I was doing a root, accidentally wiped everything including the OS, and thought I was ****ed. A little while later I went to the OnePlus website, downloaded the latest available OS and copied it over to my phone's internal memory while it was booted into TWRP. I then flashed it via TWRP and was good as new. Don't panic and you should be fine.
Click to expand...
Click to collapse
It doesn't working. I don't have my phone's internal memory, when I click on my OP3T and I can't copy the OS just on my phone.
It said that this folder is empy.
Is there a way to get into my root folders on my pc?
Vaibhunk786 said:
If adb sideload is not working. Then you can follow this method. Download adb tools from Google. Then their is a option of push the rom in the adb tools. Just keep the phone connected to notebook in twrp mode and then via that software push the rom into the internal of phone. Then just flash manually. It's done. I did this, as the same thing happened with me some days ago.
Click to expand...
Click to collapse
Okay, connected my OP3T with my computer and started my cmd and went to the adb folder.
It found my device when I typed in: adb devices.
then I tried to sideload the OS but it said:
"loading: 'OnePlus3TOxygen.zp'
* cannot read 'OnePlus3TOxygen.zip' *
I don't know, what I did wrong.
Fun4Jan said:
Okay, connected my OP3T with my computer and started my cmd and went to the adb folder.
It found my device when I typed in: adb devices.
then I tried to sideload the OS but it said:
"loading: 'OnePlus3TOxygen.zp'
* cannot read 'OnePlus3TOxygen.zip' *
I don't know, what I did wrong.
Click to expand...
Click to collapse
Don't use cmd, I told you to use a software named adb tools. Easily available on google. Search it.. Then follow the procedure. Just make sure that your phone is booted into twrp.
It is really not as easy as everyone says to root your phone. I had to do tons of research and it took a long time and the community was not helpful over at OnePlus and it was hard to find much good information here. And that is strange considering my past experiences at XDA. But, this is what I came up with and I should probably write a thread:
Use this video to guide you with your common sense: https://www.youtube.com/watch?v=KZaajUEybNM
Do not use the links provided in the video; instead use these links. That video is for another OnePlus device; the techniques are good but the files are bad. Simple substitution is all that is necessary and you can easily follow the directions with some commons sense.
Use this version of TWRP: https://dl.twrp.me/oneplus3t/
Get SuperSu here: https://download.chainfire.eu/696/supersu/
Get Android Studio here: https://developer.android.com/studio/index.html#Other
I just got my device and this totally worked for me. I hope this fixes your problem.
Are you solve this problem now?
And my advice for u :
[pre]please don't use SuperSU,it is insecurity on new Android version.Maybe you can use phh's or LineageOS root zip.NOT AD!
[1]Reflash twrp with fastboot.
[2]Flash root zip what I said(mokee rom support inner root).
[3]Flash rom(maybe you can use Mokee or LineageOS or Slimrom or OxygenOS and so on)
[4]flash gapps with nano or pico.
If this not solve problem,please try to flash factory image with MsmDownloadTool.
I hope my advice can help you.
Fun4Jan said:
Okay, connected my OP3T with my computer and started my cmd and went to the adb folder.
It found my device when I typed in: adb devices.
then I tried to sideload the OS but it said:
"loading: 'OnePlus3TOxygen.zp'
* cannot read 'OnePlus3TOxygen.zip' *
I don't know, what I did wrong.
Click to expand...
Click to collapse
if you device is getting recognized when adb devices is typed
just do this CMD: adb push (drag and drop the file you want to push onto the cmd line) /sdcard/
Fun4Jan said:
It doesn't working. I don't have my phone's internal memory, when I click on my OP3T and I can't copy the OS just on my phone.
It said that this folder is empy.
Is there a way to get into my root folders on my pc?
Click to expand...
Click to collapse
When this happens, it means DATA partition is unmounted. You have to mount it in twrp. If you still can't see the internal storage with your pc then wipe everything, including internal storage and reboot into twrp and you should be able to see it this time.
M4CH0 said:
Are you solve this problem now?
And my advice for u :
[pre]please don't use SuperSU,it is insecurity on new Android version.Maybe you can use phh's or LineageOS root zip.NOT AD!
[1]Reflash twrp with fastboot.
[2]Flash root zip what I said(mokee rom support inner root).
[3]Flash rom(maybe you can use Mokee or LineageOS or Slimrom or OxygenOS and so on)
[4]flash gapps with nano or pico.
If this not solve problem,please try to flash factory image with MsmDownloadTool.
I hope my advice can help you.
Click to expand...
Click to collapse
Thanks for your help.
I must say, that I didn't tried it.
I downloaded the original Recovery from OnePlus and flashed it on my OP3t.
I went to the original recovery modus and used ADB sideload to install the normal OS.
Now it's not rooted but it works fine now.
Yeah that's really good.
Well, all of this started when i tried to install the MIUI EU rom by TWRP, the surprise will come when the phone didn't boot. I've tried this on January of this year.
I tried everything, change port, motherboard flex, usb cable, another PC but no works.
Today i found a folder on /dev/usb-ffs/fastboot and it's empty but the adb folder (/dev/usb-ffs/adb) contains three files (ep0, ep1 and ep2). I'm not a programmer but maybe that fastboot folder would have that files.
Reading the default.prop i found the "Redmi K30s Ultra" name on ro.product.model
All of this make me think on the posibility of my phone will never be recovered, the phone only boot on fastboot and twrp but don´t detect the PC maybe for the files which is needed to boot or recognized is lost.
The TWRP version is ( 3.5.2_10 by Master and the phone gets the E:Unable to decrypt data error)
This rom (muiu 13) can only be installed via fastboot method. You can't use twrp or update method...
zopostyle said:
This rom (muiu 13) can only be installed via fastboot method. You can't use twrp or update method...
Click to expand...
Click to collapse
zopostyle said:
This rom (muiu 13) can only be installed via fastboot method. You can't use twrp or update method...
Click to expand...
Click to collapse
I was talking about the Miui 12.5 update but it's good to know it
ZeroNoTime said:
Well, all of this started when i tried to install the MIUI EU rom by TWRP, the surprise will come when the phone didn't boot. I've tried this on January of this year.
I tried everything, change port, motherboard flex, usb cable, another PC but no works.
Today i found a folder on /dev/usb-ffs/fastboot and it's empty but the adb folder (/dev/usb-ffs/adb) contains three files (ep0, ep1 and ep2). I'm not a programmer but maybe that fastboot folder would have that files.
Reading the default.prop i found the "Redmi K30s Ultra" name on ro.product.model
All of this make me think on the posibility of my phone will never be recovered, the phone only boot on fastboot and twrp but don´t detect the PC maybe for the files which is needed to boot or recognized is lost.
The TWRP version is ( 3.5.2_10 by Master and the phone gets the E:Unable to decrypt data error)
Click to expand...
Click to collapse
I don't think there are any issues with the hardware
1. Are you sure that you have installed the correct drivers for the device in windows?
2. Have you tried using a different PC? Alternatively try to use Linux
3. Have you tried adb sideload method from TWRP? eg) adb sideload rom.zip
4. Have you tried simply formatting data from TWRP before attempting to boot?
Dobsgw said:
I don't think there are any issues with the hardware
1. Are you sure that you have installed the correct drivers for the device in windows?
2. Have you tried using a different PC? Alternatively try to use Linux
3. Have you tried adb sideload method from TWRP? eg) adb sideload rom.zip
Click to expand...
Click to collapse
Yep, i tried everything but doesn't work
I only have access to twrp and fastboot but the usb connection doesn't work
Dobsgw said:
4. Have you tried simply formatting data from TWRP before attempting to boot?
Click to expand...
Click to collapse
Yep but shows the message e: Unable to decrypt FBE device
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?