Link to app. - https://dbp.noobdev.io/downloads/
https://dbp.noobdev.io/files/9.2.0....atcherAndroid-9.2.0.r25.g0638efb-snapshot.apk
Official website. dpb.noobdev.io
Offcial thread -
https://forum.xda-developers.com/showthread.php?t=2447534
All the steps on how to use are on the official thread
All the credits goes to official developer chenxiaolong
Thanks to rom developers also
Status- stable
Its working and tested by me
U may encounter tz verification failed
For this use twrp to flash patched zip or u can edit updater script in patched zip file amd remove lines for verification of tz version (solved)
Will solve this asap
"asus.verify_trustzone() failed to read current TZ version: 2"
Getting above error on flashing.
I patched for installing in ext_sdcard.
aadi50 said:
"asus.verify_trustzone() failed to read current TZ version: 2"
Getting above error on flashing.
I patched for installing in ext_sdcard.
Click to expand...
Click to collapse
yes
I will solve this asap
aadi50 said:
"asus.verify_trustzone() failed to read current TZ version: 2"
Getting above error on flashing.
I patched for installing in ext_sdcard.
Click to expand...
Click to collapse
u can use twrp to flash the patched zip
Or just edit the updater script and remove lines verifying the tz
addy692 said:
u can use twrp to flash the patched zip
Or just edit the updater script and remove lines verifying the tz
Click to expand...
Click to collapse
So I removed line verifying tz and then patched zip and flashed from in-app and it flashed and then booted successfully.
aadi50 said:
So I removed line verifying tz and then patched zip and flashed from in-app and it flashed and then booted successfully.
Click to expand...
Click to collapse
I had solved that tz fail
It will be fixed in the new update of tha app hopefully
addy692 said:
I had solved that tz fail
It will be fixed in the new update of tha app hopefully
Click to expand...
Click to collapse
Ok. Good work. I will try.
Can you confirm if app sharing works or not?? I tried but it never worked.
Error
It's showing device's codename asus_zool_93 is not recognized...error
Kevin0916 said:
It's showing device's codename asus_zool_93 is not recognized...error
Click to expand...
Click to collapse
Ok i will add this on next update
And please let me more codenames used for this device
I wil add that
Kevin0916 said:
It's showing device's codename asus_zool_93 is not recognized...error
Click to expand...
Click to collapse
If u want to work thid now
Then change ur codename in buuld.prop
To Z00L
addy692 said:
If u want to work thid now
Then change ur codename in buuld.prop
To Z00L
Click to expand...
Click to collapse
ohhk...thanks
addy692 said:
If u want to work thid now
Then change ur codename in buuld.prop
To Z00L
Click to expand...
Click to collapse
I think i will wait for the update...becoz the ro.build.product is showing Z00L....
Kevin0916 said:
I think i will wait for the update...becoz the ro.build.product is showing Z00L....
Click to expand...
Click to collapse
Just change the value which is
Asus_Z00L_93 to ZOOL
Kevin0916 said:
I think i will wait for the update...becoz the ro.build.product is showing Z00L....
Click to expand...
Click to collapse
new update released
Try that may be tz failed is now solved
addy692 said:
new update released
Try that may be tz failed is now solved
Click to expand...
Click to collapse
Great.. Keep it up... It is solved. Out of excitement i tried to flash many roms, i flashed XOSP, RR, AICP, OCT_OS successfully. Getting error in bliss. See attached screenshot.
And one more thing to confirm?? I am unable to flash any patched rom through twrp recovery (using v3.1.0.0). Is it only me or is it a common error.
Im TWRP, error is something like "updater process ends with error 1".
aadi50 said:
Great.. Keep it up... It is solved. Out of excitement i tried to flash many roms, i flashed XOSP, RR, AICP, OCT_OS successfully. Getting error in bliss. See attached screenshot.
And one more thing to confirm?? I am unable to flash any patched rom through twrp recovery (using v3.1.0.0). Is it only me or is it a common error.
Im TWRP, error is something like "updater process ends with error 1".
Click to expand...
Click to collapse
thanks for testing app and reporting
I will solve both things asap
i recommend to use data slot
As using extsd slot will be slower due sd card write speed
addy692 said:
new update released
Try that may be tz failed is now solved
Click to expand...
Click to collapse
It's Working now...thanks mate
aadi50 said:
Ok. Good work. I will try.
Can you confirm if app sharing works or not?? I tried but it never worked.
Click to expand...
Click to collapse
no app sharing support was dropped
aadi50 said:
Great.. Keep it up... It is solved. Out of excitement i tried to flash many roms, i flashed XOSP, RR, AICP, OCT_OS successfully. Getting error in bliss. See attached screenshot.
And one more thing to confirm?? I am unable to flash any patched rom through twrp recovery (using v3.1.0.0). Is it only me or is it a common error.
Im TWRP, error is something like "updater process ends with error 1".
Click to expand...
Click to collapse
have u tried extsd card slot
And how much it takes to boot extsd card slot rom?
In my case its not booting up
addy692 said:
have u tried extsd card slot
And how much it takes to boot extsd card slot rom?
In my case its not booting up
Click to expand...
Click to collapse
Actually, i have tried ext-sd slot only. And it works fine.
I use more than 200+ user apps in primary rom, So I cant waste my internal storage on ROMs. So I Use Ext-slot only.
And I use Samsung 64GB Class 10 (80Mbps) and It works fine.
Flashing a Rom takes 7-10min (without gapps).
And even the booting time is rarely different. First boot may take more than 5-10min. But after that its always around 2-3min.
Sense OS took much time as its larger in size. Rest are almost as i described above.
Which ROM did u tried?? I would say try RR its the fastest in booting and flashing.
Related
I'm getting an error message when trying to install custom rom resurrection remix. The error is 'Your recovery is using new storage layout and rom is not'
How can install the rom then?
b2nengs said:
I'm getting an error message when trying to install custom rom resurrection remix. The error is 'Your recovery is using new storage layout and rom is not'
How can install the rom then?
Click to expand...
Click to collapse
download this one and flash it
https://www.androidfilehost.com/?fid=24052804347780159
onex master said:
download this one and flash it
]
Click to expand...
Click to collapse
It removed the error but now seems like it got stuck on 'Patching system image unconditionally'. How long should it take cause it has been hours now
b2nengs said:
It removed the error but now seems like it got stuck on 'Patching system image unconditionally'. How long should it take cause it has been hours now
Click to expand...
Click to collapse
That's weird...
Which recovery did u flash
Flash the latest one ..I thinks its 2.8.5.3
Have u made a clean flash I.e clear the cache and did a factory reset ?? Before flashing Are u using multirom??
onex master said:
download this one and flash it
Click to expand...
Click to collapse
onex master said:
That's weird...
Which recovery did u flash
Flash the latest one ..I thinks its 2.8.5.3
Have u made a clean flash I.e clear the cache and did a factory reset ?? Before flashing Are u using multirom??
Click to expand...
Click to collapse
I'm using twr2.8.5.3 big, if I try to wipe it gives an error message saying could not mount to find crypto footer and followed by other technical message
b2nengs said:
I'm using twr2.8.5.3 big, if I try to wipe it gives an error message saying could not mount to find crypto footer and followed by other technical message
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2683787
Read this thread ...you will find your way out of it
onex master said:
[]
Read this thread ...you will find your way out of it
Click to expand...
Click to collapse
Thanks a lot that worked out managed to wipe everything but still stuck at patching system image unconditionally
Have tried to flash using a pc tool but still it gives an error message saying can't find android-info text something
onex master said:
Read this thread ...you will find your way out of it
Click to expand...
Click to collapse
Thanks a lot that worked out managed to wipe everything, still stuck on the patching system image unconditionally error
b2nengs said:
Thanks a lot that worked out managed to wipe everything, still stuck on the patching system image unconditionally error
Click to expand...
Click to collapse
try downloading the rom zip file again or try some other rom
Hi there,
I wanted to install the latest image of Nethunter (found on build.nethunter.com/nightly) but when I install it with TWRP I keep getting the message : "Unpacking boot image failed" in the log screen.
What I did in order:
- Unlock fastboot mode
- Flash TWRP recovery (found on build.nethunter.com/twrp)
- Reboot on TWRP
- Install kernel ( kernel-nethunter-oneplus3-nougat-3.15.4-20170126-2226 )
- Install ROM ( nethunter-generic-armhf-kalifs-minimal-rolling-3.15.4-20170202-1604 )
- Reboot
It is when I install the rom that I get the error message "Unpacking boot image failed". Even if at the end it says "install completed - Success", it keep loading (with the nethunter loading screen) indefinitely...
I tried many differents versions of TWRP and even different builds of Nethunter, I found nothing on the net, so what should I do ?
Should I post an issue on the kali-nethunter github ?
Hope you have some ideas of what I can try...
However if you need any other information (log file ...), tell me what.
Aiscargeauh said:
Hi there,
I wanted to install the last image of Nethunter (found on build.nethunter.com/nightly) but when I install it with TWRP (found on build.nethunter.com/twrp) I keep getting the message : "Unpacking boot image failed" in the log screen.
I tried many differents versions of TWRP and even different builds of Nethunter, I found nothing on the net, so what should I do ?
Should I post an issue on the kali-nethunter github ?
Hope you have some ideas of what I can try...
However if you need any other information (log file ...), tell me what.
Click to expand...
Click to collapse
What ROM are you using?
Last time i installed it i was on OOS 3.2.2. You have to flash kernel and then the big file (generic nethunter.....)
Found that in https://forum.xda-developers.com/showpost.php?p=68451978&postcount=6
It worked perfectly but since 3.2.2 i havent touched it again so not sure what rom is compatible atm
fuarkgl3 said:
What ROM are you using?
Click to expand...
Click to collapse
I'm trying with the "nethunter-generic-armhf-kalifs-minimal-rolling-3.15.4-20170202-1604.zip"
Also tried with the full version, instead of minimal but same result.
Aiscargeauh said:
I'm trying with the "nethunter-generic-armhf-kalifs-minimal-rolling-3.15.4-20170202-1604.zip"
Also tried with the full version, instead of minimal but same result.
Click to expand...
Click to collapse
I mean version of OOS, not nethunter overlay. See my screenshot. You have to download one of the following kernels depending if you are on MM or nougat. Flash it before flashing the nethunter overlay
fuarkgl3 said:
I mean version of OOS, not nethunter overlay
Click to expand...
Click to collapse
I'm trying with the latest OTA version, so actually the 4.0.2.
I also installed the kernel before, I'm gonna edit my first post with informations on what I did.
Aiscargeauh said:
I'm trying with the latest OTA version, so actually the 4.0.2.
I also installed the kernel before, I'm gonna edit my first post with informations on what I did.
Click to expand...
Click to collapse
Ok i just read it. And it seems strange indeed. Will try to install it today since i use also oos 4.0.2 and will report back asap
Just out of curiosity what twrp are you using?
fuarkgl3 said:
Ok i just read it. And it seems strange indeed. Will try to install it today since i use also oos 4.0.2 and will report back asap
Just out of curiosity what twrp are you using?
Click to expand...
Click to collapse
Thank's for the support anyway
I'm using the TWRP provided by Nethunter on build.nethunter.com/twrp/oneplus/
Also tried with official 3.0.3 for the OnePlus 3 from twrp.me/devices/oneplusthree.html
Aiscargeauh said:
Thank's for the support anyway
I'm using the TWRP provided by Nethunter on build.nethunter.com/twrp/oneplus/
Also tried with official 3.0.3 for the OnePlus 3 from twrp.me/devices/oneplusthree.html
Click to expand...
Click to collapse
Got it working. Only problem is i dont find the option to enable OTG-USB lol
fuarkgl3 said:
Got it working. Only problem is i dont find the option to enable OTG-USB lol
Click to expand...
Click to collapse
And I'm here sitting with my error and my infinite boot, lol.
Can you please put the installation process you did ? With the files you used ?
I'm getting my phone to full-stock.
Aiscargeauh said:
Can you please put the installation process you did ? With the files you used ?
I'm getting my phone to full-stock.
Click to expand...
Click to collapse
Sure. Just give me time to post what i did, currently restoring my nandroid because something went wrong when updating metapackages, so im going to download full version instead of minimal and enable OGT-USB to check if wifite works. I will post the steps asap :good:
meanwhile..... how the **** do i enable usb-otg? i dont find the option in settings/storage/3dot
Good and bad news: OTG does not work (it worked for me on MM) but nethunter runs "well" ... it stucks while rebooting and some weird things more. It runs laggy as well...
Steps and config i have
-Experience ROM v10.1(oos 4.0.2 with some adds) and custom TWRP by blu_spark v14
1-Download these 2 files from https://build.nethunter.com/nightly/3.15.4-20170202-1604/
-kernel-nethunter-oneplus3-nougat-3.15.4-20170202-1604.zip
-nethunter-generic-arm64-kalifs-full-rolling-3.15.4-20170202-1604.zip
2-Reboot to recovery and install nethunter-generic-arm64.....
3-Not sure if you have to reboot and then install kernel but i flashed nethunter+kernel without rebooting to system
4-Reboot to system and open supersu, then open nethunter app and grant superuser permissions
5-Done.
I Dont really know why my external adapter or pendrive are not recognized, because it did in MM with same hardware lol. Maybe now only works with official usb-c adapter, who knows
I will try this when I can, but it is close to what I already did.
I will edit this post when done.
I seen that you used the arm64 version, perhaps the problem is that I use the armhf ?
Aiscargeauh said:
I will try this when I can, but it is close to what I already did.
I will edit this post when done.
I seen that you used the arm64 version, perhaps the problem is that I use the armhf ?
Click to expand...
Click to collapse
may be, but im not sure. Finally got USB-OTG working but it runs very laggy and dont find any network. So problem is nh build or oos 4.0.2
fuarkgl3 said:
may be, but im not sure. Finally got USB-OTG working but it runs very laggy and dont find any network. So problem is nh build or oos 4.0.2
Click to expand...
Click to collapse
Do you think flashing another ROM before flashing nh-generic will help ?
Aiscargeauh said:
Do you think flashing another ROM before flashing nh-generic will help ?
Click to expand...
Click to collapse
Dont think so. But latest build i installed NH i didnt use arm64 version but armhf. So maybe try what i did but using custom TWRP by blu_spark v14 and armhf.... im not sure
Tested with 2 antennas and result is the same in both (see SS)
FOR SOLUTION READ POST:
[SIZE="5"]https://forum.xda-developers.com/showpost.php?p=71007646&postcount=6[/SIZE]
Long time silent reader here. I always find solutions for my problems in xda-devs, until now.
Hope you guys can help me once again..
So, yesterday I messed up my OP3 and wiped all partitions on my phone.
I've tried many steps, trying to flash a flashable stock rom (the one with boot.img and system img) in fastboot, result= installation succeed, but getting blackscreen on boot.
Installing full OOS rom from adb sideload using stock recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Installing full OOS rom from adb sideload using TWRP recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Copy the rom to my phone, and installing the zip with TWRP, result failed (error=7)
So far these are my references:
https://forums.*neplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip
OnePlus3Oxygen_16_OTA_008_all_1606122244_e0cfc5ffc8bf411a.zip
oxygen-os-3.2.5-fastboot-flashable.zip
twrp 3.0.3
https://forum.xda-developers.com/showthread.[/CODE]php?t=2588979
Click to expand...
Click to collapse
applsaus said:
Long time silent reader here. I always find solutions for my problems in xda-devs, until now.
Hope you guys can help me once again..
So, yesterday I messed up my OP3 and wiped all partitions on my phone.
I've tried many steps, trying to flash a flashable stock rom (the one with boot.img and system img) in fastboot, result= installation succeed, but getting blackscreen on boot.
Installing full OOS rom from adb sideload using stock recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Installing full OOS rom from adb sideload using TWRP recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Copy the rom to my phone, and installing the zip with TWRP, result failed (error=7)
So far these are my references:
Click to expand...
Click to collapse
So twrp is working right?
Flash any rom say lineage os
Flash multirom by BitOBSessiOn
Flash multirom twrp
Flash oos as secondary rom
And then swap oos to primary rom
try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Ye sideboard gives me issues aswell, push the zip and manually flash it In twrp: "adb push romzipname /sdcard/", the file is now ib the folder /sdcard/.
Puddi_Puddin said:
Ye sideboard gives me issues aswell, push the zip and manually flash it In twrp: "adb push romzipname /sdcard/", the file is now ib the folder /sdcard/.
Click to expand...
Click to collapse
tried it with OOS 3.2.8 and OOS 4.0.2, both give me ERROR=7
abhi0502 said:
So twrp is working right?
Flash any rom say lineage os
Flash multirom by BitOBSessiOn
Flash multirom twrp
Flash oos as secondary rom
And then swap oos to primary rom
Click to expand...
Click to collapse
Working on it. Flashed lineage os, looks like working.
Still waiting on boot screen tho (15 mins & counting, hope it won't be bootloop)
hyperorb said:
try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
Good idea, I'll put ur idea for the next try
applsaus said:
tried it with OOS 3.2.8 and OOS 4.0.2, both give me ERROR=7
Working on it. Flashed lineage os, looks like working.
Still waiting on boot screen tho (15 mins & counting, hope it won't be bootloop)
Good idea, I'll put ur idea for the next try
Click to expand...
Click to collapse
Then it's a twrp issue. I'm currently in Bluspark v16 so
Error 7 in TWRP AFAIK is an issue with using an incompatible recovery, try the latest one 3.0.4-1 I think it is from this forum.
Puddi_Puddin said:
Then it's a twrp issue. I'm currently in Bluspark v16 so
Click to expand...
Click to collapse
ghostofcain said:
Error 7 in TWRP AFAIK is an issue with using an incompatible recovery, try the latest one 3.0.4-1 I think it is from this forum.
Click to expand...
Click to collapse
I flash twrp bluspark as @Puddi_Puddin suggested and flashing Freedom OS. After that, I restore my data using my last Nandroid backup, then the bootloop comes again. Tried it several times using TWRP Bluspark with different ROMs, still no luck. So I suggest, there's nothing I can do to restoring my phone's data.
I read across the XDA forums and Oneplus forums that some people had similar issues for me, and they suspected something's wrong about corrupted partition, not because twrp version. And I also had tried flashing a few ROM in the past using the same TWRP 3.03 version without any problems. Strange.
Anyway, problems solved, my phone's up and running.
CASE CLOSED.
Thanks XDA
P.S: MODS Please Lock/Close this thread
applsaus said:
Anyway, problems solved, my phone's up and running.
CASE CLOSED.
Thanks XDA
P.S: MODS Please Lock/Close this thread
Click to expand...
Click to collapse
And, what was the solution ?
Restarting from Zero I guess.
Donglip said:
And, what was the solution ?
Click to expand...
Click to collapse
This:
hyperorb said:
try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
emuandco said:
Restarting from Zero I guess.
Click to expand...
Click to collapse
Better than not starting at all, at least.
Ok, so I've recovered the necessary files from this thread :
https://forum.xda-developers.com/nova-plus/help/lineage-os-t3556105
Thank's to @Grarak and @Xelfmade.
Now I've downloaded the necessary sources from Lineage github and I've successfully build a development environnement
If I succeed in building a rom I will share it with you, be patient and wish me good luck: D
EDIT: I've successfuly builded a rom but I can't flash it :s
-I can flash the recovery.img but when I want to flash lineage.zip in cm recovery it's stuck at "Patching system image unconditionally".
Good luck for sure! Get mine this week in Canada and happy to do any testing as it's not my daily driver.
This thread is kind of unecessary..
Please do not make placeholder threads
I've successfuly builded a rom but I can't flash it :s
I can flash the recovery.img but when I want to flash lineage.zip in cm recovery it's stuck at "Patching system image unconditionally".
If someone have an idea, for the moment I will retest with lineage 14.1
bluesmoothie said:
I've successfuly builded a rom but I can't flash it :s
I can flash the recovery.img but when I want to flash lineage.zip in cm recovery it's stuck at "Patching system image unconditionally".
If someone have an idea, for the moment I will retest with lineage 14.1
Click to expand...
Click to collapse
Can you sent it to me?
Xelfmade said:
Can you sent it to me?
Click to expand...
Click to collapse
Yes I've uploaded it to : https://www.dropbox.com/sh/84smgyxf3uy7vee/AAA8rA_GsxKmph6iU_9o8b5sa?dl=0
bluesmoothie said:
Yes I've uploaded it to : https://www.dropbox.com/sh/84smgyxf3uy7vee/AAA8rA_GsxKmph6iU_9o8b5sa?dl=0
Click to expand...
Click to collapse
I thought it would be a fault by @Grarak..
He chooses "can" as codename for the nova, the official codename instead is hwcan.
TWRP can't deal with this..
Edit: but there are more things not right here..I wonder how he has got a booting build out of it?!
Xelfmade said:
I thought it would be a fault by @Grarak..
He chooses "can" as codename for the nova, the official codename instead is hwcan.
TWRP can't deal with this..
Edit: but there are more things not right here..I wonder how he has got a booting build out of it?!
Click to expand...
Click to collapse
But with the recovery.img compiled with it's not a problem and I can recompile with hwcan if it's the problem.
EDIT: I've tested with cm 14.1 but the build fail
bluesmoothie said:
But with the recovery.img compiled with it's not a problem and I can recompile with hwcan if it's the problem.
EDIT: I've tested with cm 14.1 but the build fail
Click to expand...
Click to collapse
Yeah, I tried to modify the zip for not checking the codename, but it doesn't work..I think it's not working, because his fstab isn't really right, at least the console says that it can't mount any partition..
Xelfmade said:
Yeah, I tried to modify the zip for not checking the codename, but it doesn't work..I think it's not working, because his fstab isn't really right, at least the console says that it can't mount any partition..
Click to expand...
Click to collapse
I think I can add your device repo for recovery
EDIT: I've fused the @Grarak device folder with your device folder, I've modified .mk files in consequence, it's building...
EDIT:Build fail
Sent from my HUAWEI CAN-L11 using XDA-Developers Legacy app
bluesmoothie said:
I think I can add your device repo for recovery
EDIT: I've fused the @Grarak device folder with your device folder, I've modified .mk files in consequence, it's building...
EDIT:Build fail
Click to expand...
Click to collapse
I don't understand what you wanna tell me..
Xelfmade said:
I don't understand what you wanna tell me..
Click to expand...
Click to collapse
Anyway, if you have an idea to make it functionnal i hear you
bluesmoothie said:
Anyway, if you have an idea to make it functionnal i hear you
Click to expand...
Click to collapse
First, let me gain official twrp support for the nova afterwords I'll take the time to make this happening somehow..
Xelfmade said:
First, let me gain official twrp support for the nova afterwords I'll take the time to make this happening somehow..
Click to expand...
Click to collapse
Ok, so I can't do anything ?
And you @Grarak can you help me ? I know the "problem" in the previous thread but you have build a working rom, your help can be precious
bluesmoothie said:
Ok, so I can't do anything ?
And you @Grarak can you help me ? I know the "problem" in the previous thread but you have build a working rom, your help can be precious
Click to expand...
Click to collapse
It's a liitle bit difficult to help, without sitting in front of the monitor where the error message is displayed on..
Btw: Is your nova still encrypted?
Xelfmade said:
It's a liitle bit difficult to help, without sitting in front of the monitor where the error message is displayed on..
Btw: Is your nova still encrypted?
Click to expand...
Click to collapse
Yes, after some researchs I can confirm that :
-In android 6 the device is encrypted by default but when the userdata is formated the device work and the partition rest unencrypted.
-In android 7 the device is encrypted by default and when the userdata is formated the device won't boot, the only solution is to reformat by the official recovery and, after that, the partition remain encrypted.
PS: I'm french, so what mean "btw" ?
EDIT: I've build the rom with cm 13.0 and the files of grarak, used to build his rom, so I don't know why the flash fails.
Can you build a twrp with 'can' for the device name, I think we can test that ?
bluesmoothie said:
Yes, after some researchs I can confirm that :
-In android 6 the device is encrypted by default but when the userdata is formated the device work and the partition rest unencrypted.
-In android 7 the device is encrypted by default and when the userdata is formated the device won't boot, the only solution is to reformat by the official recovery and, after that, the partition remain encrypted.
PS: I'm french, so what mean "btw" ?
EDIT: I've build the rom with cm 13.0 and the files of grarak, used to build his rom, so I don't know why the flash fails.
Can you build a twrp with 'can' for the device name, I think we can test that ?
Click to expand...
Click to collapse
Okay nice to know for a little later..just a little bad, that the encryption doesn't work anymore
Btw means "by the way"
That won't change much, I think..
I don't know what happened with this guy named Garrak, seems like a pretty weird situation... To bad for the Nova and all the community but he surely have his reasons.
I'm not a developer but I truly thank you all to try to build something good for this beautiful device.
As its my main phone, I can't flash anything everyday but if I can help in any ways, I'm here.
Thanks
I've found some other people's with the "Patching system image unconditionally" problem and a solution was to flash via Flashfire app but I have the error "This package is for can....." There is a trick to deactivate this verification ?
EDIT: I have tested to format system partition on f2fs format but not working too.
Anyone on the above rom having trouble with update?? I use the rom updater on the phone and it showed a new update for 8-12-18 I've downloaded the file twice with the same outcome, pops up an error that just says install error?? Any of the updates before that installed fine..
blake .l said:
Anyone on the above rom having trouble with update?? I use the rom updater on the phone and it showed a new update for 8-12-18 I've downloaded the file twice with the same outcome, pops up an error that just says install error?? Any of the updates before that installed fine..
Click to expand...
Click to collapse
Download and install with twrp. If that build has treble and the one you're using doesn't, you need to flash with twrp for it to change OEM to vendor which the installer cannot do in boot time. It can be dirty flashed if the keys are the same. (I.E. test key to test key. If its from the same source, it is the same)
Uzephi said:
Download and install with twrp. If that build has treble and the one you're using doesn't, you need to flash with twrp for it to change OEM to vendor which the installer cannot do in boot time. It can be dirty flashed if the keys are the same. (I.E. test key to test key. If its from the same source, it is the same)
Click to expand...
Click to collapse
I got the file downloaded but when I go into TWRP and try to install I get this error.
Error applying update: 7 (ErrorCode: :
kInstallDeviceOpenError)
Update process ended with ERROR: 1
blake .l said:
I got the file downloaded but when I go into TWRP and try to install I get this error.
Error applying update: 7 (ErrorCode: :
kInstallDeviceOpenError)
Update process ended with ERROR: 1
Click to expand...
Click to collapse
Try with https://androidfilehost.com/?fid=3700668719832238233
Uzephi said:
Try with https://androidfilehost.com/?fid=3700668719832238233
Click to expand...
Click to collapse
Worked like a charm, Thanks!!
crazy question, how do i install magisk now? I've tried it with the older twrp i was using and I've tried it with the newer version twrp you suggested and i get boot loop now. I tried with the lineage recovery and it fails?