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
Related
Hi,
i tried to flash the latest NostromoPop 2.2.2 ROM whith twrp 2.8.5.0, but unfortunately i get the following error message:
Can't install this package on top of incompatible data. Please try another package or run a factory reset
E:error executing updater binary in zip '/sdcard/2015-12-31 rom.zip'
I already did a factory reset from the bootloader, but it doesn't change anything.
The mini 2 is unlocked, HBOOT 3.19.0.0000 and the following original ROM is running: Build 2.19.206.4, it is an o2 Germany branded one.
thanks a lot.
Robert
groni said:
Hi,
i tried to flash the latest NostromoPop 2.2.2 ROM whith twrp 2.8.5.0, but unfortunately i get the following error message:
Can't install this package on top of incompatible data. Please try another package or run a factory reset
E:error executing updater binary in zip '/sdcard/2015-12-31 rom.zip'
I already did a factory reset from the bootloader, but it doesn't change anything.
The mini 2 is unlocked, HBOOT 3.19.0.0000 and the following original ROM is running: Build 2.19.206.4, it is an o2 Germany branded one.
thanks a lot.
Robert
Click to expand...
Click to collapse
dont use sdcard.
also try clearing cache and dalvik.
kativiti said:
dont use sdcard.
also try clearing cache and dalvik.
Click to expand...
Click to collapse
Thank you, i will have a try.
But if i check the location of the file in my explorer at my pc, it is saved under internal and not under the second folder named "SD-Card"...
UPDATE> i tried to install it from sd external, but (what a surprise) it does not work. i will try to push it via adb to the device. But another question. Do i have to wipe anything else than dalvik and cache?
Thank you
groni said:
Thank you, i will have a try.
But if i check the location of the file in my explorer at my pc, it is saved under internal and not under the second folder named "SD-Card"...
UPDATE> i tried to install it from sd external, but (what a surprise) it does not work. i will try to push it via adb to the device. But another question. Do i have to wipe anything else than dalvik and cache?
Thank you
Click to expand...
Click to collapse
i dont usually do it but since you having problems, i would.
groni said:
Thank you, i will have a try.
But if i check the location of the file in my explorer at my pc, it is saved under internal and not under the second folder named "SD-Card"...
UPDATE> i tried to install it from sd external, but (what a surprise) it does not work. i will try to push it via adb to the device. But another question. Do i have to wipe anything else than dalvik and cache?
Thank you
Click to expand...
Click to collapse
i only installed it about 2 days ago perfectly so it isnt anything wrong with the ROM itself. It may be a bad download? Try to re-download it. Also try wiping cache, data and system? (Wont wipe the storage)
DarkExistence said:
i only installed it about 2 days ago perfectly so it isnt anything wrong with the ROM itself. It may be a bad download? Try to re-download it. Also try wiping cache, data and system? (Wont wipe the storage)
Click to expand...
Click to collapse
Thank you, DarkExistence . I don't think it is a bad download because I already tried it with the rom dated 25th of dec and 31st of dec. Also I checked the md5 sum after the transfer onto the smartphone. In which folder did you place the .zip File?
I am a little bit careful in wiping to much partitions, because if the installation fails after wiping the data Partition i'll have a problem.
BR
groni said:
Thank you, DarkExistence . I don't think it is a bad download because I already tried it with the rom dated 25th of dec and 31st of dec. Also I checked the md5 sum after the transfer onto the smartphone. In which folder did you place the .zip File?
I am a little bit careful in wiping to much partitions, because if the installation fails after wiping the data Partition i'll have a problem.
BR
Click to expand...
Click to collapse
clean cache dalvik and system.
you can fix partitions with TWRP
flash rom.
Hello.
I'm having issues TWRP backups. Maybe I was undone system. I need a friend using the honor 7 PLK-L01 system backup of your phone by then compressed .zip TWRP.roi nk.len up for me to use. My machine is now no longer on the operating system.
*Help me.
thank you
There are many ways to bring your phone to life. But I can suggest this;
- Extract boot(if necessary) and recovery .imgs from a full rom(which one you want) via http://forum.xda-developers.com/showthread.php?t=2433454
- Flash them by adb commands
- Put the update.app file in your sd card and start the update by 3 button way
Another suggestion is more simple; use Multi-Tool to flash the stock recovery and that's it.
memht said:
There are many ways to bring your phone to life. But I can suggest this;
- Extract boot(if necessary) and recovery .imgs from a full rom(which one you want) via http://forum.xda-developers.com/showthread.php?t=2433454
- Flash them by adb commands
- Put the update.app file in your sd card and start the update by 3 button way
Another suggestion is more simple; use Multi-Tool to flash the stock recovery and that's it.
Click to expand...
Click to collapse
Thank.
multi tool can use the phone while I was hanging not. and restore them in any way.
memht said:
There are many ways to bring your phone to life. But I can suggest this;
- Extract boot(if necessary) and recovery .imgs from a full rom(which one you want) via http://forum.xda-developers.com/showthread.php?t=2433454
- Flash them by adb commands
- Put the update.app file in your sd card and start the update by 3 button way
Another suggestion is more simple; use Multi-Tool to flash the stock recovery and that's it.
Click to expand...
Click to collapse
after restore I saw this line
"MD5 failed to match on ... / ... twrp / backups /............./.........../ system.ext4.win001"
do not know why?
hotboymen2026 said:
after restore I saw this line
"MD5 failed to match on ... / ... twrp / backups /............./.........../ system.ext4.win001"
do not know why?
Click to expand...
Click to collapse
I don't know actually but md5 errors are usually harmless. But if your recovery is working, just do fresh installation.
memht said:
I don't know actually but md5 errors are usually harmless. But if your recovery is working, just do fresh installation.
Click to expand...
Click to collapse
Do not really undersand. I've manually restore your backup files, but only running to 99%. and restore fail.
Errors are displayed MD5 "system.ext4.win001"
hotboymen2026 said:
Do not really undersand. I've manually restore your backup files, but only running to 99%. and restore fail.
Errors are displayed MD5 "system.ext4.win001"
Click to expand...
Click to collapse
Actually I am really confused.. What is your phone's condition right now? And what do you want to do?
memht said:
Actually I am really confused.. What is your phone's condition right now? And what do you want to do?
Click to expand...
Click to collapse
Status phone rom I'm wrong. logo only lead to hang on is TWRP, connect PC and Fastboot. but when I rom stock (PLK-L01 C432B270) is successful but unable to reboot the operating system. H7 is due to the security, it's hard to be rescued. I also put it into the service center (not the local machine), they also confused with my H7. I need to find ways to revive it, no matter how well!
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
Hi,
is anybody able to get encryption working on MI8 under xiaomi.eu Rom?
I tried several times with "old" Android O and new Android P Roms from Xiaomi.eu, but after "encryption" my data partition was useless and I've to format my phone completely.
I'm on the newest 'unofficial' recovery-TWRP-3.2.3-0918-XIAOMI8-CN-wzsx150.zip and on xiaomi.eu 8.9.20.
Thanks
hi!
you need to edit vendor/etc/fstab.com
in the file there is "encryptable=ice", you need to change that to "fileencryption=ice"
but you need to format data after that, i dont think it will work if you dont
t0mas_ said:
hi!
you need to edit ventor/etc/fstab.com
in the file there is "encryptable=ice", you need to change that to "fileencryption=ice"
but you need to format data after that, i dont think it will work if you dont
Click to expand...
Click to collapse
interesting... next time i've to do a clean flash, 'll try to encrypt the device. Hope it works.
t0mas_ said:
hi!
you need to edit ventor/etc/fstab.com
in the file there is "encryptable=ice", you need to change that to "fileencryption=ice"
but you need to format data after that, i dont think it will work if you dont
Click to expand...
Click to collapse
Hi t0mas,
I don't have ventor on the phone but I've found vendor, can you confirm whether it was a typo or not?
As for the file itselft, I found a resemblence named fstab.qcom in /vendor/etc/.
Fyi I'm on Mi 8 8.9.24 Xiaomi.eu ROM. In order to search for the file mentioned in your post, I went through TWRP and mounted Data, Cache, System, Vendor and Persist.
Thanks for your assistance
Hi
Does it work this way?
Gunshin82 said:
Hi t0mas,
I don't have ventor on the phone but I've found vendor, can you confirm whether it was a typo or not?
As for the file itselft, I found a resemblence named fstab.qcom in /vendor/etc/.
Fyi I'm on Mi 8 8.9.24 Xiaomi.eu ROM. In order to search for the file mentioned in your post, I went through TWRP and mounted Data, Cache, System, Vendor and Persist.
Thanks for your assistance
Click to expand...
Click to collapse
oh sorry about that, of course it is a typo. i ment /vendor/etc/fstab.qcom
edit:also roccected my original post to avoid confusion
t0mas_ said:
oh sorry about that, of course it is a typo. i ment /vendor/etc/fstab.qcom
edit:also roccected my original post to avoid confusion
Click to expand...
Click to collapse
SpiderSGS6 said:
Hi
Does it work this way?
Click to expand...
Click to collapse
Thanks, I'll give it a try and let you know if everything worked out fine.
---------- Post added at 01:32 PM ---------- Previous post was at 12:51 PM ----------
t0mas_ said:
hi!
you need to edit vendor/etc/fstab.com
in the file there is "encryptable=ice", you need to change that to "fileencryption=ice"
but you need to format data after that, i dont think it will work if you dont
Click to expand...
Click to collapse
So in TWRP, I've renamed the fstab.qcom to old_fstab.qcom_old and copied the modified file to /vendor/etc and did a data wipe. I've rebooted the phone to system but it goes to TWRP splash screen and stays there. If I reboot the phone again, it just reboots to TWRP splash screen so my phone is pretty much stuck.
did you set correct permissions? another thing I did is flash magisk. other than that it should work as far as I know...
t0mas_ said:
did you set correct permissions? another thing I did is flash magisk. other than that it should work as far as I know...
Click to expand...
Click to collapse
My phone isn't rooted.
Right now, I can't do anything, even tried to connect it via adb but it doesn't list when I type the command adb devices
Gunshin82 said:
My phone isn't rooted.
Right now, I can't do anything, even tried to connect it via adb but it doesn't list when I type the command adb devices
Click to expand...
Click to collapse
and you did format userdata?
try starting with that. format, not wipe. you have to type in "yes" to confirm. internal sd will be wiped.
flash rom again. adb pull the file, edit it, insert it it attached zip and flash that. download latest magisk and flash that. if that doesnt work, i have no idea, sorry
I can't do any of that because the phone doesn't go in the TWRP menus, it stays at the splash screen.
I've managed to access the phone via adb but I can't access /vendor/etc/. I'm trying to put back the original file in place but when I do adb shell ls /vendor/, the only thing I see is compatibility_matrix.xml, lib64 and manifest.xml.
I'm also looking at the option of flashing the vendor partition with an image file but I can't seem to find the chinese ROM for v8.9.24
---------- Post added at 03:21 PM ---------- Previous post was at 03:07 PM ----------
t0mas_ said:
and you did format userdata?
try starting with that. format, not wipe. you have to type in "yes" to confirm. internal sd will be wiped.
flash rom again. adb pull the file, edit it, insert it it attached zip and flash that. download latest magisk and flash that. if that doesnt work, i have no idea, sorry
Click to expand...
Click to collapse
I can't because it doesn't go into the TWRP menu, I'm stuck at the blue splash screen.
I've managed to connect to the phone via adb but can't seem to access /vendor/etc/. When I do adb shell ls /vendor/ the only thing I see are compatibility_matrix.xml, lib64 and manifest.xml
**double post, sorry for that, I didn't see that my post went to the second page**
Gunshin82 said:
I can't do any of that because the phone doesn't go in the TWRP menus, it stays at the splash screen.
I've managed to access the phone via adb but I can't access /vendor/etc/. I'm trying to put back the original file in place but when I do adb shell ls /vendor/, the only thing I see is compatibility_matrix.xml, lib64 and manifest.xml.
I'm also looking at the option of flashing the vendor partition with an image file but I can't seem to find the chinese ROM for v8.9.24
Click to expand...
Click to collapse
now you lost me a bit. twrp splash or xiaomi splash screen?
if twrp, you are accessing twrp system from adb, which is separate from phone. you can try to boot in fastboot and format cache. still you did you format or wipe data before that happened? that is important.
edit: you can also format userdata from fastboot
t0mas_ said:
now you lost me a bit. twrp splash or xiaomi splash screen?
if twrp, you are accessing twrp system from adb, which is separate from phone. you can try to boot in fastboot and format cache. still you did you format or wipe data before that happened? that is important.
edit: you can also format userdata from fastboot
Click to expand...
Click to collapse
Yes, TWRP and that's where I'm accessing adb.
Not sure how to format cache in fastboot, I'll look it up
Here are the steps that I did:
1-Copy the file fstab.qcom
2-Modify the copy
3-Boot in TWRP
4-Renamed original fstab.qcom in /vendor/etc to old_fstab.qcom_old
5-Copied the modified fstab.qcom file to /vendor/etc
6-Wipe Data
7-Reboot to system
Since then, I can only reboot to TWRP splash screen or fastboot
Gunshin82 said:
Yes, TWRP and that's where I'm accessing adb.
Not sure how to format cache in fastboot, I'll look it up
Here are the steps that I did:
1-Copy the file fstab.qcom
2-Modify the copy
3-Boot in TWRP
4-Renamed original fstab.qcom in /vendor/etc to old_fstab.qcom_old
5-Copied the modified fstab.qcom file to /vendor/etc
6-Wipe Data
7-Reboot to system
Since then, I can only reboot to TWRP splash screen or fastboot
Click to expand...
Click to collapse
as far as i can tell, you did 2 things wrong
1 is you didnt format data
2 didnt set permissions
maybe 3 that backup file.
do this
fastboot format cache
try to reboot into twrp, be sure it doesnt get to booting into system
if this works, backup your sd and format userdata
if that doesnt work, boot into bootloader again
format cache again just to be shure
fastboot format userdata
this should get you to twrp. there you can flash eu again and try to boot. as far as i know eu contains vendor, so you should be fine.
if this doesnt work, the next thing i would try is to fastboot flash stock rom. be sure not to lock bootloader! in this case you might end up with a hard brick.
I'm editing my answer because it crossed your response.
So I'm guessing that Wipe Data isn't the same as format data... As for the permissions, I don't see anything regarding this, can you give me more details?
So I did a format cache and then rebooted and went directly to TWRP but it remains on the splash screen so can't access the menu.
Next step, I'll try to format the userdata as suggested and flash eu rom
maybe reflashing twrp would also help
t0mas_ said:
maybe reflashing twrp would also help
Click to expand...
Click to collapse
I'm able to access the TWRP menu. Right now I'm copying the ROM from Xiaomi.eu. I tried sideloading it but it couldn't read the file for some reason. Transfer just finish, I'll flash the rom via TWRP and get back to you after. Thanks for you help on this!!
Gunshin82 said:
I'm able to access the TWRP menu. Right now I'm copying the ROM from Xiaomi.eu. I tried sideloading it but it couldn't read the file for some reason. Transfer just finish, I'll flash the rom via TWRP and get back to you after. Thanks for you help on this!!
Click to expand...
Click to collapse
no problem, im glad you got it working.
Ok so ROM installation is done and I've pulled the fstab.qcom from vendor/etc and it's back with the encryptable variable. Phone reboots in system without any problems, just need to reconfigure everything, good thing I backed up.
I'll still need to encrypt the phone. You've mentioned the steps that I did wrong. Could we go through the proper steps for this?
Sent from my MI 8 using Tapatalk
Gunshin82 said:
Ok so ROM installation is done and I've pulled the fstab.qcom from vendor/etc and it's back with the encryptable variable. Phone reboots in system without any problems, just need to reconfigure everything, good thing I backed up.
I'll still need to encrypt the phone. You've mentioned the steps that I did wrong. Could we go through the proper steps for this?
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
dont restore the phone yet
edit file
put it in the zip i posted on prevoius page
go in recovery
format userdata->confirm with typing in yes
flash zip
i allways flashed magisk also, not sure if this is necesarry
if you just flash without formatting, you will probably break stuff again
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?