Hi, I'm new here. I did some searching and couldn't find any answers regarding my problem exactly. I'm using TWRP to update my Nexus 7 2013 (flo). I have been successful in the past - as recently as yesterday. Something happened along the way and now I only get an error when attempting to flash ROMs.
I have been trying Lineage 16 and 17.1. I did do the repartition, but I get the same error on both ROMs:
Installing zip file '/sdcard/Download/lineage-17.1-20200803-UNOFFICIAL-flo.zip'
Checking fir Digest file...
Warning: No file_contexts
Target: google/razor/flo:6.0.1/MOB30X/3036618:user/release-keys
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Error installing zip file /sdcard/Download/lineage-17.1-20200803-UNOFFICIAL-flo.zip'
Updating partition details...
...done
I have tried to edit the text to eliminate the "asserts" - no help. I downgraded TWRP one version, no help. What else can I do. I'm pretty much a noob when it comes to this, and I'm willing to "hold hands" to get a solution if there is one. Thanks!
ericdudeus said:
....I have tried to edit the text to eliminate the "asserts" - no help. I downgraded TWRP one version, no help. What else can I do. I'm pretty much a noob when it comes to this, and I'm willing to "hold hands" to get a solution if there is one. Thanks!
Click to expand...
Click to collapse
In TWRP go Advanced Wipe and wipe system/data/cache/dalvik before installing the ROM.
If it still does not work and you wish to investigate it, please 'install' this zip in twrp, find 'logs.tgz' in the root of internal storage and post it here.
If you just want this ROM installed ASAP then do:
RESTOCK (select repartition to original factory layout)
CROSS
:fingers-crossed:
Thank you! I actually started over - completely wiped the tablet, repartitioned it, flashed the ROM, and Gapps, and it's fully functioning again. It just didn't like something in the process before, I guess.
k23m said:
In TWRP go Advanced Wipe and wipe system/data/cache/dalvik before installing the ROM.
If it still does not work and you wish to investigate it, please 'install' this zip in twrp, find 'logs.tgz' in the root of internal storage and post it here.
If you just want this ROM installed ASAP then do:
RESTOCK (select repartition to original factory layout)
CROSS
:fingers-crossed:
Click to expand...
Click to collapse
Hi,
i have too this problem.
I wipe everything, flashed the repartitioning zip and still havoc 3.3 cannot be flashed. What i have to do? thanks
The solution for me was to just completely wipe the storage - everything, and start over. Once wiped, I repartitioned, flashed the ROM (I used Resurrection Remix), and then GApps. The tablet seems to be fully functional at this point, but it's showing its age.
Good luck!
ericdudeus said:
The solution for me was to just completely wipe the storage - everything, and start over. Once wiped, I repartitioned, flashed the ROM (I used Resurrection Remix), and then GApps. The tablet seems to be fully functional at this point, but it's showing its age.
Good luck!
Click to expand...
Click to collapse
It's tell me E: eroor creating fstab
k23m said:
In TWRP go Advanced Wipe and wipe system/data/cache/dalvik before installing the ROM.
If it still does not work and you wish to investigate it, please 'install' this zip in twrp, find 'logs.tgz' in the root of internal storage and post it here.
If you just want this ROM installed ASAP then do:
RESTOCK (select repartition to original factory layout)
CROSS
:fingers-crossed:
Click to expand...
Click to collapse
I ran the logging zip. My log.tgz is here: https://abar.duckdns.org/s/aywJagDNJDxfiyL
thrilway said:
I ran the logging zip. My log.tgz is here: https://abar.duckdns.org/s/aywJagDNJDxfiyL
Click to expand...
Click to collapse
OK, the relevant error is...
Code:
erasing 18342 blocks
BLKDISCARD ioctl failed: Invalid argument
failed to execute command [erase 4,223772,228864,229950,243200]
new data receiver is still available after executing all commands.
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7
It seems your eMMC hardware version is <4.4
But RESTOCK should work.
Thanks, but I'm running a linux desktop, so I can't really run RESTOCK. Is there a guide somewhere to run the commands in RESTOCK manually?
EDIT
I've reviewed your logs. For the custom ROM to work you need repartition. Install sysrepart-max.zip then reboot and now install the ROM. If gapps are needed, use pico.
It worked! Thanks
k23m said:
In TWRP go Advanced Wipe and wipe system/data/cache/dalvik before installing the ROM.
If it still does not work and you wish to investigate it, please 'install' this zip in twrp, find 'logs.tgz' in the root of internal storage and post it here.
If you just want this ROM installed ASAP then do:
RESTOCK (select repartition to original factory layout)
CROSS
:fingers-crossed:
Click to expand...
Click to collapse
Thank you so much! It worked perfectly. In the beginning it didn't work, I just reboot the device after wiping system/data/cache/dalvik, then tried again to install the ROM, Now my device has the new ROM working without problem.
Getting error 70 in twrp when installing Opengapps (pico) even BitGapps
Hi, I have the Error 7 Problem with my Nexus 10 Using newest TWRP Recovery and trying to install Lineage 17.1 unoffical. Generated the logs.tgz file - which you will find encllosed. Hope anyone could help.
Thanks a lot in advance!
BlackVoltage said:
Hi, I have the Error 7 Problem with my Nexus 10 Using newest TWRP Recovery and trying to install Lineage 17.1 unoffical. Generated the logs.tgz file - which you will find encllosed. Hope anyone could help.
Thanks a lot in advance!
Click to expand...
Click to collapse
This is a Nexus 7 forum, not Error 7 forum, lol.
The error indicates a too small 'system' partition and you need to enlarge it. You will find a solution on Nexus 10 'manta' forum.
Ok thanks - I did not see that at first. My fault. Do you know a special Error 7 Nexus 10 Forum? Or am I just right here?
[ROM][LineageOS][17.1][UNOFFICIAL][Nexus10]
LineageOS lineage-17.1-20230404-UNOFFICIAL-manta.zip Known issues: - Pls disable "Adaptive brightness" in display settings -> sensor service problems. - GPS is not working and has been disabled completely - NFC is not working and has been...
forum.xda-developers.com
Related
Hello,
i just unlocked bootloader and installed twrp and it all went fine..
until i wanted to fully wipe my device, i did this via twrp.
after 20Minuts, nothing happend, the bar was still white and gray (not even a little bit blue)
and it kept stuck on ''twrp formatting data using make_ext4fs function''.
i knew this wasn't a good idea, but i decided to turn off my phone,
and now, everytime when i turn it on on the normal way it just redirrects me to TeamWin in a bootloop.
even if i want to go to recovery mode i keep stuck in that bootloop, so there is nothing i can do right now, i only can stick at Fastboot Mode but nothing else,
Is there any way to fix this problem?
Using ASUS ZENFONE 2 551ML
I hope you did a backup of your system before? Otherwise just download the latest full image:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.174-user.zip
place it on your internal sdcard (via adb push) and then flash it normally with TWRP. Please note that the procedure can take up to 30 minutes, where the formatting is the procedure taking the longest time...
TheSSJ said:
I hope you did a backup of your system before? Otherwise just download the latest full image:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.174-user.zip
place it on your internal sdcard (via adb push) and then flash it normally with TWRP. Please note that the procedure can take up to 30 minutes, where the formatting is the procedure taking the longest time...
Click to expand...
Click to collapse
How to he flash stock rom by twrp?
Download and flash this via twrp http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526
Make sure you flash Supersu before you flash the rom.
mr_gourav2000 said:
How to he flash stock rom by twrp?
Click to expand...
Click to collapse
It's all written there...adb push on the phone, flash the zip normally via twrp, wait and done
TheSSJ said:
It's all written there...adb push on the phone, flash the zip normally via twrp, wait and done
Click to expand...
Click to collapse
but i cant use twrp on my phone because its stuck in bootloop, or what do you mean? (english not my main language)
please give me some proper step by step instructions, i would really apreciate that!
thanks anyway your awesome!
Man, I misread your post, sorry...I thought you could boot only into twrp
If you still have fastboot, why not flashing twrp 2.8.x.x?
Code:
Fastboot flash recovery nameofrecovery.img
Fastboot reboot recovery
Otherwise you could flash stock system with this guide: http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
It's a lot to read
wow, that is something really helpfull, there is still hope to revive my phone
i'll let you know how it turnt out xd
thanks alot!!
i fixed recovery mode, so thats already one step further. Oefff @TheSSJ thanks for the help.
But now i get some other problems, when i try to wipe my phone i get the error like ''unable to mount /data'' and ''unable to wipe dalvik''
and all other kinds of these errors, i get the same problem when i was installing rom. isn't there anything or a way to fully wipe all this **** so i can install a fresh rom.
i flashed custom rom and this is error log i get. its all full written down.
E: could not mount /data and unable to find crypto footer.
E: unable to mount /data
E: unable to recreate /data/media folder.
updating partition details...
E: unable to mount /data
... done
E: unable to mount storage.
E: unable to mount /data/media during GUI startup
Full SELinux support is present.
E: unable to mount /data/media/twrp. twrps when trying to read settings file.
E:unable to mount /data
MTP enabled
E: unable to mount /data
E: unable to mount /data
E: unable to mount /data
Installing external_sd/UL-Z00A-WW-2.20.40.174-user.zip ...
Checking for MD5 file...
Skipping MD5 check: no MD5 File found
Device image SKU:
OTA image SKU: WW
assert failed: getprop ("ro.build.asus.sku") == ''WW''
E: Error executing updater binary in zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Error flashing zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Updating Partition Details...
E:unable to mount /data
... done
E: unable to mount storage.
Failed
Seems you don't have a WW image installed, do you have a CN Software? Then you need another Software of course
what do you mean with ww & cn software?
sorry but im new in this.. but im really interested so can you please explain a little bit?
how can i get this other software! thanks!!!
Where did you buy your Phone? what does the packaging state? WW, CN, TW, etc? These 2 letters must be written in uppercase somewhere, then we will know which software to flash, there is a check where your phone's software is compared to the zip you are trying to flash:
assert failed: getprop ("ro.build.asus.sku") == ''WW''
Which TWRP did you flash?
ohhh yes, i do have CN software Probably, as it is buyed from china.
Where can i find this other type software?
thanks!
colldor200 said:
ohhh yes, i do have CN software Probably, as it is buyed from china.
Where can i find this other type software?
thanks!
Click to expand...
Click to collapse
There you go: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-CN-2.20.40.159-user.zip
I think flashing will still fail though...but pls try first,maybe it'll work
i tryed it, i get the same error :/
Update: i changed from CN to WW.
Because of this i reflashed to twrp 3.0 and it works properly and now wiping shows no problem anymore.
I also got the WW ota zip but dont know how to install that.
Anyway, i tryed to install xaosp rom (even if my ota is still CN)
And it showed no problems at all!
BUT when i tryed to startup my phone it sticks with the asus logo and wont go any further, not a bootloop, it just sticks at the asus logo.
We are Always getting more and more steps further into fixing my phone, thanks for that @TheSSJ were almost there ?
colldor200 said:
Update: i changed from CN to WW.
Because of this i reflashed to twrp 3.0 and it works properly and now wiping shows no problem anymore.
I also got the WW ota zip but dont know how to install that.
Anyway, i tryed to install xaosp rom (even if my ota is still CN)
And it showed no problems at all!
BUT when i tryed to startup my phone it sticks with the asus logo and wont go any further, not a bootloop, it just sticks at the asus logo.
We are Always getting more and more steps further into fixing my phone, thanks for that @TheSSJ were almost there
Click to expand...
Click to collapse
You could try flashing cm13 first and then xosp:
First wipe data/cache
Then flash cm13
Boot up and hope that it works
Reboot to recovery
Wipe data/cache
Flash xosp and maybe a kernel that fits (FlareM?)
Boot to system again
You could try flashing cm13 first and then xosp:
First wipe data/cache
Then flash cm13
Boot up and hope that it works
Reboot to recovery
Wipe data/cache
Flash xosp and maybe a kernel that fits (FlareM?)
Boot to system again
Click to expand...
Click to collapse
sorry for the kinda late answer, but yes i followed your instructions, and it works completely, after cm13 i also immediately installed gapps.
i skipped xaosp im fine with cm13
Thanks alot @TheSSJ for all the help my phone is fully fixed now and even working faster then before its like super fast.
thanks again your great!
Hey all,
I'm having some trouble trying to update firmware packages through TWRP (and any ROM other than xiaomi.eu). I'm trying to flash this rom and I've downloaded both the ROM and the firmware as linked on the page. When I try to flash both through TWRP, the script succeeds but returns a value of 1. I'm assuming that means it failed, shouldn't it return 0 on success?
After flashing I've tried to boot to system, but it loops through the boot animation and a TWRP "Open Recovery Script" screen. Not too sure what that means. I'm running TWRP version 3.2.0-0.
I didn't have any of these problems with my Mi 5. Not too sure what I'm doing wrong. Can anyone guide me in the right direction?
Thanks
JaredG_ said:
Hey all,
I'm having some trouble trying to update firmware packages through TWRP (and any ROM other than xiaomi.eu). I'm trying to flash this rom and I've downloaded both the ROM and the firmware as linked on the page. When I try to flash both through TWRP, the script succeeds but returns a value of 1. I'm assuming that means it failed, shouldn't it return 0 on success?
After flashing I've tried to boot to system, but it loops through the boot animation and a TWRP "Open Recovery Script" screen. Not too sure what that means. I'm running TWRP version 3.2.0-0.
I didn't have any of these problems with my Mi 5. Not too sure what I'm doing wrong. Can anyone guide me in the right direction?
Thanks
Click to expand...
Click to collapse
Did you format data and type yes in TWRP?
For a lot of ROM changes you need to format the whole data partition not just wipe it.
Dobsgw said:
Did you format data and type yes in TWRP?
For a lot of ROM changes you need to format the whole data partition not just wipe it.
Click to expand...
Click to collapse
Yes I have.
I'm not too sure if I'm supposed to be rebooting to system afterwards. It's rebooting into MIUI 9 which sets up the internal storage and lets me copy the firmware updates onto the device through TWRP, but I'm still getting that 'return 1' and boot loop issue.
JaredG_ said:
Yes I have.
I'm not too sure if I'm supposed to be rebooting to system afterwards. It's rebooting into MIUI 9 which sets up the internal storage and lets me copy the firmware updates onto the device through TWRP, but I'm still getting that 'return 1' and boot loop issue.
Click to expand...
Click to collapse
Flash the firmware, then the ROM, then gapps if you use it.
Then format data and reboot.
That should get things working for you.
Then after that if you're flashing the same ROM you wont need to do a format of data you can just wipe it and keep internal storage
Dobsgw said:
Flash the firmware, then the ROM, then gapps if you use it.
Then format data and reboot.
That should get things working for you.
Then after that if you're flashing the same ROM you wont need to do a format of data you can just wipe it and keep internal storage
Click to expand...
Click to collapse
I can't seem to update the firmware. I'm definitely doing something wrong it's never taken me this long on any of my devices.
Trying to flash the Mi 6 Global 7.11.2 firmware gives this log in TWRP:
package_extract_file took 00s
...
SetMetadataFn took 00s
RunProgramFn took 00s
script succeeded: result was [1.000000]
Updating partition details...
...done
Click to expand...
Click to collapse
Then trying to flash the ROM afterwards gives me error 7. Where am I going wrong with the firmware update?
I bet at the end of all this it's going to be just a simple mistake haha :/
JaredG_ said:
I can't seem to update the firmware. I'm definitely doing something wrong it's never taken me this long on any of my devices.
Trying to flash the Mi 6 Global 7.11.2 firmware gives this log in TWRP:
Then trying to flash the ROM afterwards gives me error 7. Where am I going wrong with the firmware update?
I bet at the end of all this it's going to be just a simple mistake haha :/
Click to expand...
Click to collapse
Its not your fault.
Error 7 is common. It means the zip is looking for the device name and getting the wrong one. Probably looking for "Sagit" or something and TWRP is saying "this is a Mi 6"
Scripts follow exact logic haha.
So my recommendation is to copy the RR zip to PC.
Use 7zip to extract just the updater script from the meta-inf file.
Then use notepad++ to delete the very top few lines which are about checking device type.
Then copy it back to the zip and flash it.
It won't check what device it is flashing on and will flash regardless.
That's fine as you know its the correct device.
Seems like the firmware package is flashing fine.
You can also go to the LineageOS 15 thread and download the firmware package I made from the latest miui firmware. Its on the OP by NisseCool.
Dobsgw said:
Its not your fault.
Error 7 is common. It means the zip is looking for the device name and getting the wrong one. Probably looking for "Sagit" or something and TWRP is saying "this is a Mi 6"
Scripts follow exact logic haha.
So my recommendation is to copy the RR zip to PC.
Use 7zip to extract just the updater script from the meta-inf file.
Then use notepad++ to delete the very top few lines which are about checking device type.
Then copy it back to the zip and flash it.
It won't check what device it is flashing on and will flash regardless.
That's fine as you know its the correct device.
Seems like the firmware package is flashing fine.
You can also go to the LineageOS 15 thread and download the firmware package I made from the latest miui firmware. Its on the OP by NisseCool.
Click to expand...
Click to collapse
I'm not convinced that the firmware is flashing correctly. This is the error message from trying to flash the ROM:
Can't install this package on top of incompatible data. Pleas try another package or run a factory reset
Updater process ended with ERROR: 7
Click to expand...
Click to collapse
This was after I flashed the firmware package that you put together from the LineageOS 15.0 thread and after formatting data and rebooting into MIUI. Flashing the firmware gave the same log output as my previous post.
I had a look at the updater script, and it's definitely passing the first assert statements. This is the line with the error message:
HTML:
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
This is killing me
EDIT: Disregard my comment about the firmware not updating. I had a look at the firmware update script and from the TWRP log it seems like it is flashing fine.
Fixed.
Firmware was flashing fine. I need to learn to properly read instructions.
I had formatted data through the interface where you need to type 'yes', but I didn't do an advanced wipe and tick data (I swear I had done it already)
Silly mistakes. Learn to read instructions, kids haha
Thank you for your help
JaredG_ said:
Fixed.
Firmware was flashing fine. I need to learn to properly read instructions.
I had formatted data through the interface where you need to type 'yes', but I didn't do an advanced wipe and tick data (I swear I had done it already)
Silly mistakes. Learn to read instructions, kids haha
Thank you for your help
Click to expand...
Click to collapse
That's really strange. Format should do the same as wipe just more effective.
Glad it's all working!
Anyone know how to bring that partition back? I was trying to do some stuff with opengapps but then now I cant even get it back to EXT4
exile1ck said:
Anyone know how to bring that partition back? I was trying to do some stuff with opengapps but then now I cant even get it back to EXT4
Click to expand...
Click to collapse
Sure. Flash a full factory image leaving the flash-all script alone (allow it to wipe the device). If that does not complete successfully, you will get valuable information when it fails. Keep that error message. You can then manually format the partition(s) and try again.
v12xke said:
Sure. Flash a full factory image leaving the flash-all script alone (allow it to wipe the device). If that does not complete successfully, you will get valuable information when it fails. Keep that error message. You can then manually format the partition(s) and try again.
Click to expand...
Click to collapse
Actually, that is what I did yesterday and somehow I was able to go from custom rom to the original pixel rom without any issues. I was trying to install opengapps into a custom rom but the Storage partition didnt have enough space(got error 70).
Last night I managed to get my bootloader unlocked using this method. Awesome, but now I'm stuck on the 11g firmware and I can't even update magisk correctly. I found the unofficial lineage 16 for the European model but that can only be installed from European firmware. I flashed the latest European pie kdz and found that I could no longer enter the bootloader (even though it's still unlocked). I've tried installing twrp but as of now there is only a semi-persistant version which doesn't really do anything for me. So for now I'm stuck, any ideas?
i am using the 10th release of lineageos 16 for the persistant twrp.
edit: also, i installed it from canadian pie (20a) and it worked fine.
Thanks! I'll give that a shot tonight
Pouchon514 said:
i am using the 10th release of lineageos 16 for the persistant twrp.
edit: also, i installed it from canadian pie (20a) and it worked fine.
Click to expand...
Click to collapse
I can't seem to be able to send files to my phone while in twrp. Did I flash something wrong?
I did install canadian pie but can't access bootloader from this version
TJzuo said:
I can't seem to be able to send files to my phone while in twrp. Did I flash something wrong?
I did install canadian pie but can't access bootloader from this version
Click to expand...
Click to collapse
PM and ULM models seem to have issues with pie not loading bootloader.
Sticking to oreo seems to fix this issue. But lineage being installed over oreo shouldnt cause a big issue.
loonycgb2 said:
PM and ULM models seem to have issues with pie not loading bootloader.
Sticking to oreo seems to fix this issue. But lineage being installed over oreo shouldnt cause a big issue.
Click to expand...
Click to collapse
I can't send files to twrp from my computer, so I don't have a way to flash it (even on oreo which loads the bootloader fine)
TJzuo said:
I can't send files to twrp from my computer, so I don't have a way to flash it (even on oreo which loads the bootloader fine)
Click to expand...
Click to collapse
Did you try adb push? When you are in twrp open openshell:
adb push .\file name /sdcard/"destination" (with out quotes) or you might have to format data to access internal storage.
Running GSI LOS 16. Will update after running it for few hours.
sinkoo1979 said:
Did you try adb push? When you are in twrp open openshell:
adb push .\file name /sdcard/"destination" (with out quotes) or you might have to format data to access internal storage.
Running GSI LOS 16. Will update after running it for few hours.
Click to expand...
Click to collapse
Just got around to messing with this thing again, I can't seem to access adb sideload from twrp:
"Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Unknown error 150)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Unknown error 150)
... done
Unable to mount storage
Failed to mount '/data' (Unknown error 150)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Starting ADB sideload feature..."
It fails several seconds later. So far there's no way for me to push the file using adb. Any other suggestions?
TJzuo said:
Just got around to messing with this thing again, I can't seem to access adb sideload from twrp:
"Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Unknown error 150)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Unknown error 150)
... done
Unable to mount storage
Failed to mount '/data' (Unknown error 150)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Starting ADB sideload feature..."
It fails several seconds later. So far there's no way for me to push the file using adb. Any other suggestions?
Click to expand...
Click to collapse
Did you format the data first? if you didn't, go to wipe select format and type yes and after that reboot to recovery.
sinkoo1979 said:
Did you format the data first? if you didn't, go to wipe select format and type yes and after that reboot to recovery.
Click to expand...
Click to collapse
YOU sir, are an absolute life saver. I feel dumb that it was such a simple fix. I was able to copy over the file! But trying to install it failed for some unknown reason. Thanks again!
TJzuo said:
YOU sir, are an absolute life saver. I feel dumb that it was such a simple fix. I was able to copy over the file! But trying to install it failed for some unknown reason. Thanks again!
Click to expand...
Click to collapse
What rom are you trying to flash?
sinkoo1979 said:
What rom are you trying to flash?
Click to expand...
Click to collapse
Unofficial lineage 16 for the european model. If you've got a better one that's be awesome!
TJzuo said:
Unofficial lineage 16 for the european model. If you've got a better one that's be awesome!
Click to expand...
Click to collapse
GSI lineage 16 works good.
sinkoo1979 said:
GSI lineage 16 works good.
Click to expand...
Click to collapse
Awesome to hear! Do you happen to have a link?
TJzuo said:
Awesome to hear! Do you happen to have a link?
Click to expand...
Click to collapse
search treble xda on google search
sinkoo1979 said:
search treble xda on google search
Click to expand...
Click to collapse
Found it, I downloaded a file called "lineage-16.0-20190910-UNOFFICIAL-treble_arm64_bvN.img.xz" and extracted it. I tried installing the img as a system image, no dice. Not sure what to do from here...
TJzuo said:
Found it, I downloaded a file called "lineage-16.0-20190910-UNOFFICIAL-treble_arm64_bvN.img.xz" and extracted it. I tried installing the img as a system image, no dice. Not sure what to do from here...
Click to expand...
Click to collapse
What kind of message are you getting?
flashing gsi:
flash gsi as system
reboot to recovery
go to wipe and repair and resize the system
flash gapps
flash magisk (optional)
reboot
sinkoo1979 said:
What kind of message are you getting?
flashing gsi:
flash gsi as system
reboot to recovery
go to wipe and repair and resize the system
flash gapps
flash magisk (optional)
reboot
Click to expand...
Click to collapse
looks like I'm stuck in bootloop. I managed to flash everything successfully without any errors but couldn't actually boot into the system. Do I need to flash a rom as well as a system image?
TJzuo said:
looks like I'm stuck in bootloop. I managed to flash everything successfully without any errors but couldn't actually boot into the system. Do I need to flash a rom as well as a system image?
Click to expand...
Click to collapse
Yes, flash the system img that you get from zip in system partition. That is all you flash in GSI no zip for system.
sinkoo1979 said:
Yes, flash the system img that you get from zip in system partition. That is all you flash in GSI no zip for system.
Click to expand...
Click to collapse
I must not have the right image file then, I can keep looking. What site did you get yours from?
I'm facing some permissions problems and thus being unable to install Paranoid Android Q5. I was using MIUI 12 (Xiaomi.EU).
The steps I took to change the ROM:
Formated data (errors started right away) then I did the usual wipes (cache, dalvik, data)
Whenever I try to wipe or format data I get error messages like: Error opening /data/XXX (Operation not permitted).
System is always mounted read-only no matter what I try and after I install any ROM many of these error messages pop up.
Orange Fox gives some error about key.
Flashing of the ROM suceeds, but system cannot boot, loading screen forever.
Can anyone point me some directions?
Thanks in advance and sorry about any possible bad grammar.
[ ]s
;-)
Mount system, vendor and data manually and then try. If fails then try with pitchblack recovery.
Pavello said:
Mount system, vendor and data manually and then try. If fails then try with pitchblack recovery.
Click to expand...
Click to collapse
Well , i have the same problem..and used pitch black also
Any update on this?
I still had those problems. I don't know if it is a problem with the TWRP or something similar. Is there any progress to solve this problem? I wanted to try the pixel experience betas with Android 11 but because of this problem with the TWRP I have not succeeded (in case I have Android 10 under MIUI 12.0.3 and RN8 Ginkgo model and obviously unlocked bootloader)
jordyx20 said:
I still had those problems. I don't know if it is a problem with the TWRP or something similar. Is there any progress to solve this problem? I wanted to try the pixel experience betas with Android 11 but because of this problem with the TWRP I have not succeeded (in case I have Android 10 under MIUI 12.0.3 and RN8 Ginkgo model and obviously unlocked bootloader)
Click to expand...
Click to collapse
i gusse thats a problem in miui12.0.3
i was using pixel experience 10 then i flash miui 12.0.3 in fastboot when i tryd to flash orange fox i had the same problem
so i gusse u can downgred to miui 11 and flash twrp and it will work
I solved this by downgrading to 12.0.1
jordyx20 said:
I still had those problems. I don't know if it is a problem with the TWRP or something similar. Is there any progress to solve this problem? I wanted to try the pixel experience betas with Android 11 but because of this problem with the TWRP I have not succeeded (in case I have Android 10 under MIUI 12.0.3 and RN8 Ginkgo model and obviously unlocked bootloader)
Click to expand...
Click to collapse
Format data ..(backup first if u need ) .. the boot to recovery again ... Should decrypt the data ... Worked for me ...
I am having this exact problem.
Under internal storage (sdcard) I see a bunch of hashed folders I cannot open.
Format data returns a multitude of "Error opening '/data/somefolder/asdf/asdf' (Operation not permitted) and marks the wipe as Failed. The attempted formatting also mentions "E:Error making /sdcard/Fox directory: Required key not available." "Failed to unmount '/data' (Device or resource busy)
I can wipe anything except Data. I also tried downgrading to 12.0.1 firmware but it does not fix it for me.
The ROM can be booted into, and magisk managed to be installed, but no google apps were installed.
Dibbo Sarker said:
Format data ..(backup first if u need ) .. the boot to recovery again ... Should decrypt the data ... Worked for me ...
Click to expand...
Click to collapse
I tried this, but no luck on my side.
Recovery download link on description. Only for Note 8/8T.
I flashed it with fastboot and works fine!
A problem like this was the one I had since TWRP had the device encrypted but it did not inform me and it did not give me any sign that I had to write a password (password that I have no idea what it is).
What I did so that it did not give me an error was to install Orangefox and while there delete everything and install a file of these that I got from google.
I had to try one by one and restart to see if it asked me for a password in orangefox, luckily one worked and it no longer asked me to decrypt the files and I could install the rom and gapps normally
jonatasgabriel76 said:
Recovery download link on description. Only for Note 8/8T.
I flashed it with fastboot and works fine!
Click to expand...
Click to collapse
Thank youuuuuuuu! You have rescued my phone!
jonatasgabriel76 said:
Recovery download link on description. Only for Note 8/8T.
I flashed it with fastboot and works fine!
Click to expand...
Click to collapse
THANK YOU!
Why is my orange fox is not showing Vendor, System Etc ? How can i fix this ? I really need to wipe those as well..
Jona'san - sama said:
Why is my orange fox is not showing Vendor, System Etc ? I really need to wipe those as well..
Click to expand...
Click to collapse
if you need to do something to system or vendor go to ofox menu/mount and choose what partition to mount
Jona'san - sama said:
I really need to wipe those as well..
Click to expand...
Click to collapse
if you want to flash a rom = yes
loopypalm said:
if you need to do something to system or vendor go to ofox menu/mount and choose what partition to mount
if you want to flash a rom = yes
Click to expand...
Click to collapse
Can't wipe it still, I already try the Mount > ✓ Vendor ✓ System.. but in formatting it say's "Cant Mount the....blah..blah.."
I try to uncheck the "Mount System vendor, system as read-only" from the settings of mount.. but for some reason, if you go back to Mount options again, you can't check the system, vendor now
loopypalm said:
if you need to do something to system or vendor go to ofox menu/mount and choose what partition to mount
if you want to flash a rom = yes
Click to expand...
Click to collapse
Yes, I need it to flash a ROM
try this it worked
Had the same issue.
1. I installed twrp via ADB
2. Restarted to recovery mode into twrp
3. Installed the latest OrangeFox and restarted into recovery again.
4. It asked me for a password which is the pin I set then proceeded to format data.
5. After formatting data I restarted again to recovery.
Then I was able to install custom roms.
I am using derpfest Android 12 on my Poco x3 pro. I want to install magisk.zip through orange fox recovery installed on my phone. But I am not getting storage data on recovery, only a fox folder is there. Can somebody tell me is it a glitch or any Android 12 restrictions or something.