Related
I have an issue that I cannot for the life of me fix. Last night my wife’s phone received the OTA update and her phone would not restart after that. Total B.S. move on ASUS’s part not to pull that update knowing the issues people were having. But anyways, here’s the rundown. I can boot into bootloader mode but I cannot get into stock recovery. I can, through a certain method get into CWM recovery and I can see the external SD, but I get errors when I try to flash an update or another entire OS. I’ve tried to bypass signature verification also and still cannot get anything to install. ADB will not sideload because it does not find my device, but the method of getting into CWM recovery is done through ADB so I’m confused there. Never have I had such a tough time restoring a bricked device. Samsung, no problem. Huawei, no problem. This POS I’m about ready to throw in the pool and call it a day. Does anyone have any suggestions?
Try flashing CN version and dont forget to disable zip signature and format everything before flashing
Sent from my ASUS_Z00AD using Tapatalk
LiRi2000 said:
Try flashing CN version and dont forget to disable zip signature and format everything before flashing
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
The only way I can flash is through the CMW recovery and everything I try to flash says cant install this package over newer build. But there's nothing on the device as far as I can tell. Also says E: Error in /external_sd status 7
MikeyLee said:
The only way I can flash is through the CMW recovery and everything I try to flash says cant install this package over newer build. But there's nothing on the device as far as I can tell. Also says E: Error in /external_sd status 7
Click to expand...
Click to collapse
Open ROM archive with app (for example WinRAR),
navigate to META-INF\com\google\android
unpack updater-script
open unpacked updater-script with any text editor (I use Notepad++)
remove first line with "(!less_than_int..."
save file
put unpacked file back in archive overwriting it
put rom package on sdcard
flash it via recovery
btw, Updating IFWI takes a 10 or more minutes so wait and don't panic
I'll try that when I get home
MikeyLee said:
The only way I can flash is through the CMW recovery and everything I try to flash says cant install this package over newer build. But there's nothing on the device as far as I can tell. Also says E: Error in /external_sd status 7
Click to expand...
Click to collapse
Try and install twrp recovery through adb you can find how in the forum....if you can install it it will be much easier to flash a room.
Sent from my ASUS_Z00AD using Tapatalk
LiRi2000 said:
Try and install twrp recovery through adb you can find how in the forum....if you can install it it will be much easier to flash a room.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Nothing will flash through adb
meciu99 said:
Open ROM archive with app (for example WinRAR),
navigate to META-INF\com\google\android
unpack updater-script
open unpacked updater-script with any text editor (I use Notepad++)
remove first line with "(!less_than_int..."
save file
put unpacked file back in archive overwriting it
put rom package on sdcard
flash it via recovery
btw, Updating IFWI takes a 10 or more minutes so wait and don't panic
Click to expand...
Click to collapse
Still doesnt work. E: error in external sd blah blah blah, same as everything else.
@MikeyLee I had the same problem this morning, i spent a lot of time to fix this, i couldn't access the recovery, i tried to flash thetered recovery and do factory reset, flash again the rom, but nothing.
To fix the bootloop i just rebooted in fastboot mode, launced the adb from pc and format cache partition, thats all.
And the strange thing is that i didn't loose the data, Although I did the factory reset, that's mean maybe a corrupted cache partition that maked impossible to flash anything or do factory reset.
Sent from my ASUS_Z00AD using Tapatalk
Hank87 said:
@MikeyLee I had the same problem this morning, i spent a lot of time to fix this, i couldn't access the recovery, i tried to flash thetered recovery and do factory reset, flash again the rom, but nothing.
To fix the bootloop i just rebooted in fastboot mode, launced the adb from pc and format cache partition, thats all.
And the strange thing is that i didn't loose the data, Although I did the factory reset, that's mean maybe a corrupted cache partition that maked impossible to flash anything or do factory reset.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
I've wiped cache multiple times. What steps did you go through?
Use the adb fastboot, command "fastboot erase cache"
Sent from my ASUS_Z00AD using Tapatalk
You need the stock recovery as the same version of the firmware you're sideloading, flash the recovery through fastboot.
I was finally able to restore everything. Stock recovery, OS etc… Here’s what I did.
Using ADB and following the procedures here http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556 and using fastboot, flashed the recovery.img, boot.img and droidboot.img in that order. That gave me stock recovery back. Then I sideloaded with ADB the latest FULL firmware from here https://www.asus.com/support/Download/39/1/0/13/Lk0Sg1Ulh0Ph49Hl/32/
It was the only version that did not error out in some form or another. Everything is back to normal.
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Citroon said:
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Click to expand...
Click to collapse
It looks so simply but did you take a look to your rom zip? open with a zip explorer like winzip in /META-INF/com/google/android and here you must find this file
SubwayChamp said:
It looks so simply but did you take a look to your rom zip? open with a zip explorer like winzip in /META-INF/com/google/android and here you must find this file
Click to expand...
Click to collapse
it's not only with the roms, it's with everything
i've tried to flash new firmware, gapps and nothing works :/
well, what version of twrp do you use? try first with oficcial 3.0.2.0, bootloader unlocked? check usb debbugging and allow oem unlock in developer options, sometimes neccessary mount system or enable MTP in recovery
SubwayChamp said:
well, what version of twrp do you use? try first with oficcial 3.0.2.0, bootloader unlocked? check usb debbugging and allow oem unlock in developer options, sometimes neccessary mount system or enable MTP in recovery
Click to expand...
Click to collapse
im using the official 3.0.2.0, i currenly have no RoM installed so i can't boot into anything
Citroon said:
im using the official 3.0.2.0, i currenly have no RoM installed so i can't boot into anything
Click to expand...
Click to collapse
try first formatting data, wipe everything except where placed your rom zip (int or extSD), mount system and flash again
SubwayChamp said:
try first formatting data, wipe everything except where placed your rom zip (int or extSD), mount system and flash again
Click to expand...
Click to collapse
Tried that, still having the error:crying:
Citroon said:
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Click to expand...
Click to collapse
ok, go to format the data and then write YES, but u will lose your data, so, backup your files, and then restore them. should be working !!
StonebridgeGr said:
ok, go to format the data and then write YES, but u will lose your data, so, backup your files, and then restore them. should be working !!
Click to expand...
Click to collapse
Doesn't work either, this is really weird to me, i've been flashing for a few years now, and never encountered this issue before.
-also note that i'm not amazing at this
Citroon said:
Doesn't work either, this is really weird to me, i've been flashing for a few years now, and never encountered this issue before.
-also note that i'm not amazing at this
Click to expand...
Click to collapse
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
StonebridgeGr said:
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
Click to expand...
Click to collapse
i've tried about every RoM available.
I also want to note that i have flashed with this version of TWRP before (3.0.2.0)
StonebridgeGr said:
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
Click to expand...
Click to collapse
tried about every rom available, and other things just to see what would work and what wouldn't (nothing can flash)
im currently running 3.0.2.0 and have flashed with this version of TWRP before, but suddenly it stopped working
Citroon said:
Tried that, still having the error:crying:
Click to expand...
Click to collapse
Probably a bad flashing and you are needing repari partitions, for that I recommend start from beginning again:
- flash miui rom for fastboot (unpack zip rom in your adb folder for better performance, connect device to pc into mode fastboot, be sure device be recogniced typing; fastboot devices then right click mouse and execute like admin over "flash all".
- then to install rom you can flash again twrp via fastboot typing any place adb folder and placing file recovery.img this folder; fastboot flash recovery recovery.img
- then go to recovery with hardware keys and flash supersu v.2.79
SubwayChamp said:
Probably a bad flashing and you are needing repari partitions, for that I recommend start from beginning again:
- flash miui rom for fastboot (unpack zip rom in your adb folder for better performance, connect device to pc into mode fastboot, be sure device be recogniced typing; fastboot devices then right click mouse and execute like admin over "flash all".
- then to install rom you can flash again twrp via fastboot typing any place adb folder and placing file recovery.img this folder; fastboot flash recovery recovery.img
- then go to recovery with hardware keys and flash supersu v.2.79
Click to expand...
Click to collapse
oh boy, i guess im screwed for now then.
i only have access to a macbook for the next few days, tried installing fastboot on it but that's a complete nightmare
Citroon said:
oh boy, i guess im screwed for now then.
i only have access to a macbook for the next few days, tried installing fastboot on it but that's a complete nightmare
Click to expand...
Click to collapse
two things; I assume that trying to flash from extSD, if yes with file explorer of recovery copy to internal memory, maybe an issue to reading extSD, also you can to install a newer version of recovery 3.0.3.2 works sometimes for me and last here you have a reading page about install fastboot on mac (nightmare) http://www.stechguide.com/setup-adb-and-fastboot-on-mac-easy-step-by-step-guide/
SubwayChamp said:
two things; I assume that trying to flash from extSD, if yes with file explorer of recovery copy to internal memory, maybe an issue to reading extSD, also you can to install a newer version of recovery 3.0.3.2 works sometimes for me and last here you have a reading page about install fastboot on mac (nightmare) http://www.stechguide.com/setup-adb-and-fastboot-on-mac-easy-step-by-step-guide/
Click to expand...
Click to collapse
I finally got it working
I was so stubborn that I decided to install Windows Bootcamp on my mac
it was as simple as reinstalling TWRP and do a clean wipe, now i can install roms and all the other things as i please again.
-Thank you for your help!
I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Also it seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Is this why the flashing keeps failing and does anyone know what the problem could be?
Thanks!
bronderb said:
Go into your bootloader and format system, cache, and userdata (This will wipe EVERYTHING so be sure to backup). Then latest official flash stock rom and reboot. This should fix it. If this helped hit thanks!
Click to expand...
Click to collapse
Bootloader? There is no option in the bootloader to delete everything as far as I can see, do you mean in recovery? And if I wipe everything off the phone, how do I get the stock ROM onto the phone to flash it? When you say wipe userdata do you mean wipe internal storage or am I misunderstanding and you're telling me to wipe the usual dalvik, cache and data as you would for a normal clean flash?
bronderb said:
No, go into fastboot and plug into pc. Open cmd and type "fastboot format userdata" "fastboot format cache" "fastboot format system"
Click to expand...
Click to collapse
Okay, thanks, and then what? Do I flash TWRP then push the stock ROM to the phone and flash that? And exactly how do I do that?
bronderb said:
You just go into twrp (no need to reflash) then adb sideload oxygen os
Click to expand...
Click to collapse
Thank you, I am now running OOS, hopefully everything else will go smoothly now, planning to go back to FOS again
I didn't even have to use the fastboot commands to format, just sideloading the OOS file wiped everything anyway
Turns out the issue isn't actually fixed, "system" still appears unchecked in TWRP. Could the fact that I didn't actually format everything first have made a difference, given everything was wiped in the process anyway?
Looks like I'm going to be living the sideloading life...
Edit: Sideloading freedom OS failed, ended up having to restore from my TWRP backup. I don't know what I'm going to do, my main reason for using custom ROMs is installing a black theme, and OOS doesn't support Layers or Substratum fully so I can't stay on that
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
frickinjerms said:
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
Click to expand...
Click to collapse
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
evilkitty69 said:
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
Click to expand...
Click to collapse
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
tnsmani said:
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Click to expand...
Click to collapse
I was running 3.0.2-2 when the issue started, I updated to 3.0.3 and 3.1.0-0 but nothing changed. Thanks for the suggestion, I will give it a try
null0seven said:
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
Click to expand...
Click to collapse
Help! I attempted to do this and the process failed, I didn't manage to wipe data because "/data could not be mounted as device or resource is busy"
Edit: Device now has nothing but TWRP and fastboot, no OS, no ADB, no data, no internal storage
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
I managed to get hold of a few factory images and attempted to flash system.img through fastboot, resulting error was
"target reported max download size of 536,870,912 bytes" (system image is 3080 MB)
"invalid sparse file format at header magi"
null0seven said:
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
Click to expand...
Click to collapse
I reflashed the modified TWRP successfully. The second suggestion wouldn't have worked, given my phone has no internal storage
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
null0seven said:
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
Click to expand...
Click to collapse
The recovery was working at this point, the issue turned out to be the data partition, system was formatted to ext4 but I didn't realise data was in f2fs which caused the problem in the first place. I formatted to ext4 and everything worked, I was able to install paranoid android and everything worked...
...until I flashed the wrong firmware and now I've hard bricked it! I'm going to try the hard brick toolkit
Edit: After 12 hours of being an unresponsive brick, the phone suddenly booted, system doesn't work but it has recovery. Unfortunately I seem to be back to square one, if I try to flash something it appears to succeed but then the phone doesn't boot up into system
So I am now back to the original issue of system not mounting, in terminal if I type "mount /system" I get following error:
"mounting /dev/block/sde20 on /system failed: Device or resource is busy"
Anyone know how to solve this?
I formatted everything, reflashed recovery and tried to flash OOS, got following error:
Code:
[FONT="Courier New"]"This package is for OnePlus3 devices, this is a oneplus3t" (it isn't)
"Updater process ended with ERROR: 7
Error installing zip file /sdcard/OOS3.2.6.zip" [/FONT]
Issue was "solved" by flashing PA, GApps and the correct firmware
Hopefully that's the end of all this drama, thanks to everyone for their suggestions
Hi, I'm pretty new at rooting and I seem to have a similar error. I'm getting the "can't mount /system" error in TWRP. I am able to boot into OOS 4.1.3 and run the nandroid backup but, I keep getting the same error and am unable to select "system" when choosing the mount option in TWRP.
Do I need to have all partitions in f2fs? My system partition is in ext4. Is this what solved your issue?
It seems my phone is functional even with the error active but, I've been trying to get systemless SuperSU and MagiskHide working and I think that's what is preventing me from doing so.
I'm installing twrp but whenever i try to boot into twrp all my data is wiped and twrp is unable to mount it
"Could not mount /data and unable to find crypto footer"
I need to manually change the filesystem and then again change to ext4 for twrp to mount data.
Main issue is i want to use snapchat and for that i need to boot into OS, login into snapchat and then root in twrp
but again as soon as i boot into twrp my data partition is not mountable. I have flashed no_encrypt_no_verity.dm_ashyx to disable dm-verity.
Flashed various twrp version from 3.0 to 3.2
Also did a clean OS flash from odin but still no luck.
Any suggestion and help will be appreciated.
jfk999 said:
I'm installing twrp but whenever i try to boot into twrp all my data is wiped and twrp is unable to mount it
"Could not mount /data and unable to find crypto footer"
I need to manually change the filesystem and then again change to ext4 for twrp to mount data.
Main issue is i want to use snapchat and for that i need to boot into OS, login into snapchat and then root in twrp
but again as soon as i boot into twrp my data partition is not mountable. I have flashed no_encrypt_no_verity.dm_ashyx to disable dm-verity.
Flashed various twrp version from 3.0 to 3.2
Also did a clean OS flash from odin but still no luck.
Any suggestion and help will be appreciated.
Click to expand...
Click to collapse
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Baseminge said:
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Click to expand...
Click to collapse
Tried that too , same issue still.
It seems that data partition gets corrupted whenever i boot into twrp everytime.
No way out
jfk999 said:
I'm installing twrp but whenever i try to boot into twrp all my data is wiped and twrp is unable to mount it
"Could not mount /data and unable to find crypto footer"
I need to manually change the filesystem and then again change to ext4 for twrp to mount data.
Main issue is i want to use snapchat and for that i need to boot into OS, login into snapchat and then root in twrp
but again as soon as i boot into twrp my data partition is not mountable. I have flashed no_encrypt_no_verity.dm_ashyx to disable dm-verity.
Flashed various twrp version from 3.0 to 3.2
Also did a clean OS flash from odin but still no luck.
Any suggestion and help will be appreciated.
Click to expand...
Click to collapse
have you wiped data(TWRP/wipe data/type YES in the keyboard)?
and use superuser for root cause magisk can t mount data at the moment.
broky said:
have you wiped data(TWRP/wipe data/type YES in the keyboard)?
and use superuser for root cause magisk can t mount data at the moment.
Click to expand...
Click to collapse
As soon as i boot in twrp, data is not mountable. So I then go to
wipe-->adv wipe-->(select data partition)repair or change partition-->change partition format-->fat
TWRP then wipes it to fat filesytem,then i change it to ext4 (which is readable by OS)
then only data partition is mounted.
Afterwards I flash no-verity-no-encryption_ashyx and RMM patch
Boots normal to OS
Again boot to twrp i get error unable to mount /data
I had this issue in nougat but it used to happen only once.After flashing patch i used to not get this error repeated
jfk999 said:
As soon as i boot in twrp, data is not mountable. So I then go to
wipe-->adv wipe-->(select data partition)repair or change partition-->change partition format-->fat
TWRP then wipes it to fat filesytem,then i change it to ext4 (which is readable by OS)
then only data partition is mounted.
Afterwards I flash no-verity-no-encryption_ashyx and RMM patch
Boots normal to OS
Again boot to twrp i get error unable to mount /data
I had this issue in nougat but it used to happen only once.After flashing patch i used to not get this error repeated
Click to expand...
Click to collapse
Twrp/above factory reset on right side there is an option format data.
Press on this option and a keyboard rises.type YES and select format data.
After this check data partition,should be mounted.
After this flash SU zip and last Ashyx s patch.
Idonel this many times never had a problem even in Orsi.
Hope it works I can t think of something else.
broky said:
Twrp/above factory reset on right side there is an option format data.
Press on this option and a keyboard rises.type YES and select format data.
After this check data partition,should be mounted.
After this flash SU zip and last Ashyx s patch.
Idonel this many times never had a problem even in Orsi.
Hope it works I can t think of something else.
Click to expand...
Click to collapse
Which twrp version are you using?
Try...
The universal "no verity opt encrypt".
Magisk for the above, or safetynet evasion.
Backing up snapchat in /data/data/ and /sdcard/Android/data/, and load the backup. By PC or external sdcard, or load the backup later.
jfk999 said:
Which twrp version are you using?
Click to expand...
Click to collapse
look in 1:13
this is the step i mean:
format data/type:yes
https://www.youtube.com/watch?v=iOjnmGQ14fc&t=41s
broky said:
look in 1:13
this is the step i mean:
format data/type:yes
https://www.youtube.com/watch?v=iOjnmGQ14fc&t=41s
Click to expand...
Click to collapse
Tried it but still same issue.
Bryan48765 said:
Try...
The universal "no verity opt encrypt".
Magisk for the above, or safetynet evasion.
Backing up snapchat in /data/data/ and /sdcard/Android/data/, and load the backup. By PC or external sdcard, or load the backup later.
Click to expand...
Click to collapse
Tried the universal version for samsung and applied RMM patch, unfortunately same issue again.
I think that this has to do with SEpolicy. In nougat i used to get a small red warning at the edge of screen while booting to twrp. That time i did not face this
issue. Now I dont get any warning..boots into twrp with data partition corrupted.
I dont know, ive tried everything possible but no luck.
This is how I did and it works on my A320FL:
1. I installed Ashyx's version of TWRP via odin.
2. Boot into TWRP and "Format Data" from "Wipe" menu.
3. Flash SuperSu.
4. Flash Ashyx's patch.
5. Reboot phone(into recovery again).
6. Update TWRP with McFy's version.
jfk999 said:
Tried it but still same issue.[/QUO
I think I have the same issue.
May was your phone branded when you bought it?
Click to expand...
Click to collapse
Baseminge said:
jfk999 said:
Tried it but still same issue.[/QUO
I think I have the same issue.
May was your phone branded when you bought it?
Click to expand...
Click to collapse
I bought it from official store..Also i bought it jus few months after launch..
Which carrier are you using?
Click to expand...
Click to collapse
jfk999 said:
Baseminge said:
I bought it from official store..Also i bought it jus few months after launch..
Which carrier are you using?
Click to expand...
Click to collapse
So I think is something concerning the MM firmware that was not fixed with the N and O updates, 'cause I bought it very close to his launch too. I solved it by flashing a custom rom, so I think the problem was in official MM firmware or something went wrong in the OTA updates
Click to expand...
Click to collapse
Baseminge said:
jfk999 said:
So I think is something concerning the MM firmware that was not fixed with the N and O updates, 'cause I bought it very close to his launch too. I solved it by flashing a custom rom, so I think the problem was in official MM firmware or something went wrong in the OTA updates
Click to expand...
Click to collapse
Well ya..from MM to N, I did Odin update but from N to O i did ota update..since then im facing this issue..
But i still dont get it..i did a clean install and downloaded firmware from sammobile..yet this issue persist
Click to expand...
Click to collapse
jfk999 said:
Baseminge said:
Well ya..from MM to N, I did Odin update but from N to O i did ota update..since then im facing this issue..
But i still dont get it..i did a clean install and downloaded firmware from sammobile..yet this issue persist
Click to expand...
Click to collapse
At this point the only advice I can give you is to do a full wipe including "Internal Storage" (if you didn't) before flashing with Odin.
I really don't guess it will solve the problem on an official firmware, but there's no harm in trying
Click to expand...
Click to collapse
Still no luck...
At this point i have lost hopes
jfk999 said:
Still no luck...
At this point i have lost hopes
Click to expand...
Click to collapse
No matter what you try at this point you're data will always encrypt and will need to be formatted. TWRP will always reset.
This requires a whole different route and needs you to edit system files.
I'll get back to you with details.
---------- Post added at 11:25 PM ---------- Previous post was at 10:39 PM ----------
jfk999 said:
I'm installing twrp but whenever i try to boot into twrp all my data is wiped and twrp is unable to mount it
"Could not mount /data and unable to find crypto footer"
I need to manually change the filesystem and then again change to ext4 for twrp to mount data.
Main issue is i want to use snapchat and for that i need to boot into OS, login into snapchat and then root in twrp
but again as soon as i boot into twrp my data partition is not mountable. I have flashed no_encrypt_no_verity.dm_ashyx to disable dm-verity.
Flashed various twrp version from 3.0 to 3.2
Also did a clean OS flash from odin but still no luck.
Any suggestion and help will be appreciated.
Click to expand...
Click to collapse
This method requires intermediate knowledge of Windows and CMD commands....I've tried to simplify it and hope it is easy enough to go through
The files that need editing are the ramdisk fstab files.
Basically you are going to unpack boot.img, edit the files and repack it.
Here's how you do it:
In windows...From the firmware, open the AP file with WinRAR. Extract boot.img.lz4 and save it to your desktop
Go here https://github.com/lz4/lz4/releases/download/v1.8.2/lz4_v1_8_2_win64.zip
Extract it then just place your boot.img.lz4 to directory of lz4
Next open up cmd as admin and cd to the location where lz4.exe is located
In cmd type lz4.exe boot.img.lz4
This will unpack the lz4 file.
Now download http://www.mediafire.com/file/93a3f4bikaxh6tj/MTK_Extractor_V2.6.3.zip
Just open exe go to boot tab select the unpacked boot.img
This will extract the files you need and it will create folder called "initrd" and it will contain the contents of boot.img.
Make sure you have Notepad++ installed to edit the files.
Go to the MTK folder where your files have been extracted
Right click Fatah.goldfish and select open with Notepad++
Next find the phrase ",encryptable=userdata"
Delete it
Close the tab in Notepad++ and click to save
Back to MTK folder and right click fstab.ranchu. Open with Notepad++
Find the phrase ",quota,forceencrypt=/dev/block/vdd"
Delete it
Find the phrase ",encryptable=userdata"
Delete it
Close the tab in Notepad++ and click to save
Back to MTK folder and right click fstab.samsungexynos7880. Open with Notepad++
Find the phrase ",verify"
Delete it
Find the phrase ",forceencrypt=footer,quota"
Delete it.
Close the tab in Notepad++ and click to save
Next, go back to the MTK program and press the repack button
This will create your new boot.img file
Go back to the MTK folder. You should see your old boot.img file saved as "boot-old.img" and your new file as "boot.img"
Install 7-zip
Back to MTK right click your new boot.img. select 7-zip then select "add to archive"
This will open up another window. Simply select "tar" from the dropdown menu for "Archive format"
Press OK
This will create a new file "boot.tar"
Flash this via Odin with phone in Download mode
The boot will now be patched and you can set up TWRP as you need.
This whole process will need repeating if a new AP is flashed
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