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.
Related
Due to a number of reports of people bricking their devices, I have removed this tutorial.
For instructions to get your device unbricked, please read here.
I'm terribly sorry for the inconvenience.
Hello,
thanks for sharing, but do you also know a way back to wileyfox stock rom? I don't think a twrp backup holds all nand data. When flashing GM4G rom, you also flash ie. modem partition, and I don't think that this is covered by a twrp backup.
bye...DonQ
Seed has a TWRP patched for cm updater. I'm a seed user but I prefer crackling roms
DonQuichotte said:
Hello,
thanks for sharing, but do you also know a way back to wileyfox stock rom? I don't think a twrp backup holds all nand data. When flashing GM4G rom, you also flash ie. modem partition, and I don't think that this is covered by a twrp backup.
bye...DonQ
Click to expand...
Click to collapse
Flash the factory image.
[email protected] said:
Seed has a TWRP patched for cm updater. I'm a seed user but I prefer crackling roms
Click to expand...
Click to collapse
I can't find a link for the Seed TWRP patched for CM Updater. Can you share it?
seb5049 said:
I can't find a link for the Seed TWRP patched for CM Updater. Can you share it?
Click to expand...
Click to collapse
Yeah I would like to know too
VivaLaVent said:
Flash the factory image.
Click to expand...
Click to collapse
I'm not sure this is enough, cause with the GM4G rom some partitions (.img) get flashed, that are not in the swift factory rom...oem.img, devinfo.bin. I think about switching to seed, cause no more nigthlies and seed has official CM14.1 already. But there has to be a bullet-proof way to return to stock...just in case.
bye DonQ
twrp patched by Arvin Quilao
VivaLaVent said:
Yeah I would like to know too
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=457095661767122264 i use this and updated via cm updater twice with no problem....
[email protected] said:
https://www.androidfilehost.com/?fid=457095661767122264 i use this and updated via cm updater twice with no problem....
Click to expand...
Click to collapse
Okay so I'm guessing updating with CM updater does work, but the recovery you linked is not the latest version of TWRP.
Hello, I've tried to flash this rom General Mobile 4G (seed) and it finishes OK, but device does not restart ( brick but USB COM port detected), I've reinserted the battery and device does not turn on, googled a bit, and used qualcomm flash tool to unbrick my wileyfox.
What am I doing wrong here ?
I've also tried with GM_4G_7.0_NRD90R_FASTBOOT_STOCK_ROM_BY_TURKDEVS same problem device is bricked
Also I've tried from stock Cynogen OS (12.1-YOG4PAS33J) but same result device bricked
PS. downloaded files are ok, not corrupted....
Twrp version status...
VivaLaVent said:
Okay so I'm guessing updating with CM updater does work, but the recovery you linked is not the latest version of TWRP.
Click to expand...
Click to collapse
Yeahhh it isnt the latest i know. The latest is 3.0.2-1 but isnt patched for cm ota updates like that shared by me later. The dev stated the official version patched from twrp website will come later. Using it dnt create any prblm.
piromanneo said:
Hello, I've tried to flash this rom General Mobile 4G (seed) and it finishes OK, but device does not restart ( brick but USB COM port detected), I've reinserted the battery and device does not turn on, googled a bit, and used qualcomm flash tool to unbrick my wileyfox.
What am I doing wrong here ?
I've also tried with GM_4G_7.0_NRD90R_FASTBOOT_STOCK_ROM_BY_TURKDEVS same problem device is bricked
Also I've tried from stock Cynogen OS (12.1-YOG4PAS33J) but same result device bricked
PS. downloaded files are ok, not corrupted....
Click to expand...
Click to collapse
I'm having the same problem.
seb5049 said:
I'm having the same problem.
Click to expand...
Click to collapse
I'm starting to think I made an error, can anyone confirm they successfully used this method?
VivaLaVent said:
I'm starting to think I made an error, can anyone confirm they successfully used this method?
Click to expand...
Click to collapse
I was unsuccessful with your method. I even tried two times then I gave up and restored my backup with cm-13
How is it running on CM 14? Is there noticeable lag and such?
If you want CM14, try crDroid, it works great. I'm using it for two weeks now, no FC errors, good battery performance, no serious lags.
When I read the bricks of some users trying to flash a ROM that is meant for a clone with ALMOST the same hardware - I won't try this.
I am considering doing this update. But I have an issue. Since Android 6 has integrated sdcards, I had to reformat the sdcard on every update which is a pain in the ass. I using mixed mode. Is there any way to do an update which allows to reintegrate the sdcard without reformatting the sdcard?
piromanneo said:
Hello, I've tried to flash this rom General Mobile 4G (seed) and it finishes OK, but device does not restart ( brick but USB COM port detected), I've reinserted the battery and device does not turn on, googled a bit, and used qualcomm flash tool to unbrick my wileyfox.
What am I doing wrong here ?
I've also tried with GM_4G_7.0_NRD90R_FASTBOOT_STOCK_ROM_BY_TURKDEVS same problem device is bricked
Also I've tried from stock Cynogen OS (12.1-YOG4PAS33J) but same result device bricked
PS. downloaded files are ok, not corrupted....
Click to expand...
Click to collapse
I seem to have the same problem as you, device doesn't respond, no boot or whatever.
Could you link me to the solution you used to unbrick the device?
Due to a number of reports of people bricking their devices, I have removed this tutorial.
For instructions to get your device unbricked, please read here.
I'm terribly sorry for the inconvenience.
First of all, sorry for my englisch. From yesterday I have buy a oneplus 3. I have unlockt my bootloader and wanne flash twrp. From the.official site I get when I have flash it a black screen. 2e time I flash the modificated twrp 3.0.2-1.28. But up fine in twrp but ask for a pin???? Cancel this but can not make a backup etc. 3e time I flasht 3.0.2-19 from enst blue spark or.some dev, sorry for not nowing dev name. Again enter pin. Also has try to enble screen pin in patron and pin and type this pin or patron in twrp. Nothing!!! How can I fix this problem? Using Oxygen version 4.0 android 7.0
Someone can help me pleace.... Wanne have a working twrp.
With my shamu I never has this problem with encryption or decryption, never has enter a pin etc..
search ull find dont creat a thread hit cancel then format data or try new blu twrp v11
heavydread said:
search ull find dont creat a thread hit cancel then format data or try new blu twrp v11
Click to expand...
Click to collapse
And where can I find the v11?
Never mind find it: https://forum.xda-developers.com/devdb/project/dl/?id=22429
v11 still won't work if your /data partition is on ext4 fs. If you can, please wipe your internal storage and convert it to f2fs, then the v11 recovery would work fine for you. But if you can't do that, sadly, there is no solution apart from removing security from phone (Pin,Pattern,FP) and then try decrypting data.
It works, I can backup my data now
Maby a noob question but can I flash superuser.zip in twrp or must it with a command. With my n6 I flash su in twrp. Does this also work with oneplus 3???
All work
Delete this toppic pleace
abalam said:
Delete this toppic pleace
Click to expand...
Click to collapse
It's probably too late for that, but check the guide I've made: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Was it the somewhat same guide that you used to solve your problem?
dbabaev21 said:
It's probably too late for that, but check the guide I've made: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Was it the somewhat same guide that you used to solve your problem?
Click to expand...
Click to collapse
Tnx for that but google was my best friend. No I running f2fs, custom recovery v11 and root on 4.0 Running great. Was testing a custom rom 7.1.1 but root disappeared. Problem on N I read. Thia only is when I must flash root but read rom with build in root the root stays there. I'm satisfied with what I now turn. If the problems are solved and kernel source are released for N I give cutom ROMs a chance.
abalam said:
First of all, sorry for my englisch. From yesterday I have buy a oneplus 3. I have unlockt my bootloader and wanne flash twrp. From the.official site I get when I have flash it a black screen. 2e time I flash the modificated twrp 3.0.2-1.28. But up fine in twrp but ask for a pin???? Cancel this but can not make a backup etc. 3e time I flasht 3.0.2-19 from enst blue spark or.some dev, sorry for not nowing dev name. Again enter pin. Also has try to enble screen pin in patron and pin and type this pin or patron in twrp. Nothing!!! How can I fix this problem? Using Oxygen version 4.0 android 7.0
Someone can help me pleace.... Wanne have a working twrp.
With my shamu I never has this problem with encryption or decryption, never has enter a pin etc..
Click to expand...
Click to collapse
The only working recovery actually is latest TWRP (v11) from blu_spark.
Flash it via fastboot command.
EDIT: sorry for useless answering, just now I've seen that my method was already done.
Simone98RC said:
The only working recovery actually is latest TWRP (v11) from blu_spark.
Flash it via fastboot command.
EDIT: sorry for useless answering, just now I've seen that my method was already done.
Click to expand...
Click to collapse
Yeah, running v11 and running great man! Love this device to. Comming from N6 and is just flash and gooooo. This machine is a little bit searce for what you must flashing on what version beta but after a week, must say a now a lot more of this beast machine. Just running here Oxygen OS this there is more official the see voor N. Have root it etc and don't need more futures (yet [emoji12]) haha...
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)
[Official]TWRP 3.1.1-0 for MATE 8
Modified to work with Nougat firmwareTeam Win Recovery Project 3.1.1-0
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
WHY IS IT MODIFIED?
Like you know, the official TWRP here doesn't work on Huawei Mate 8 device, it's why I modified in order it works on our device. This one only works with Nougat firmware.
SUPPORTED DEVICES
Mate 8
DOWNLOAD
twrp-3.1.1-0-next.img - MD5: 82808bdc7ff1452ea15081f033c4f826
What's new in 3.1.1-0 (TeamWin - TWRP):
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
My changes:
Code:
TWRP 3.1.1-0
* modified to work on Nougat
* kernel updated from eRecovery (B581 firmware) for proper loop support
* native_package.xml has been added to device specific version from eRecovery (B581 firmware)
* Replaced system folder by the one of eRecovery (B581 firmware)
KNOWN ISSUES
Doesn't work with Marshmallow
Doesn't enable to correctly read the decrypted data - displaying 0 MB when you push the "Install" button - Only with decrypted data
CREDITS
TeamWin - TWRP
Franzyroy (me)
Version Information
Status: Official modified - beta version
Release Date: 2017-05-26
If you like that, hit the THANKS button below !
I can't say anything about this TWRP yet, I haven't tested it, so I do not know what it is worth ... but it is official.
I tried but it doesn't work for me with Nougat.
franzyroy said:
I tried but it doesn't work for me with Nougat.
Click to expand...
Click to collapse
Maybe it's only support for HTC? The twrp we have now (3.0.2) also good enough but only need to improve on the restore data part. As the path restore data broken but of course restore using twrp 3.0.3. Only problem with twrp 3.0.3 doesn't work well with data encryption.
Edit : Yeah. I tried it too. Doesn't work. Maybe it's for MM.
What a pc of junk waste of time to post its not 1985
franzyroy said:
I tried but it doesn't work for me with Nougat.
Click to expand...
Click to collapse
we defo need a port for nougat then... thx for testing
Sent from my Huawei Mate 8 NXT-AL10
dexz said:
Maybe it's only support for HTC? The twrp we have now (3.0.2) also good enough but only need to improve on the restore data part. As the path restore data broken but of course restore using twrp 3.0.3. Only problem with twrp 3.0.3 doesn't work well with data encryption.
Edit : Yeah. I tried it too. Doesn't work. Maybe it's for MM.
Click to expand...
Click to collapse
I checked inside, I confirm it's for MM . But it's really for our device.
c|nder said:
What a pc of junk waste of time to post its not 1985
Click to expand...
Click to collapse
???? WTF ¿¿¿ I would like to understand but I don't see!
jbmc83 said:
we defo need a port for nougat then... thx for testing
Click to expand...
Click to collapse
Maybe it could help us to have a stable version of Nougat.
Not working on MM, I couldn't boot onto recovery
Sent from my Nexus 6P using Tapatalk
M.Noury said:
Not working on MM, I couldn't boot onto recovery
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Really? It doesn't work on Marshmallow? What is this bazaar?
M.Noury said:
Not working on MM, I couldn't boot onto recovery
Click to expand...
Click to collapse
Now that's a surprise.
dexz said:
Now that's a surprise.
Click to expand...
Click to collapse
I made a report here.
franzyroy said:
I made a report here.
Click to expand...
Click to collapse
I think all we need is some dev to look into it. 1% of the report will be reply from the official but then again 1% is better than 0% right. :laugh:
I confirm, 3.1.0.0 hangs on boot.
dexz said:
I think all we need is some dev to look into it. 1% of the report will be reply from the official but then again 1% is better than 0% right. :laugh:
Click to expand...
Click to collapse
Yes I know but well, we must try.
paulcl said:
I confirm, 3.1.0.0 hangs on boot.
Click to expand...
Click to collapse
Unfortunately.
Well, already a good new for us, if I can say, the TWRP 3.1.0-0 doesn't work also for other models, like the Huawei Honor 8. It's not really a good info but at least, we aren't alone with this issue. So we can hope to have a fix nextly or later.
I have flashed TWRP 3.1.0.0 from the honor 8 thread. I managed to boot to recovery. The only thing that not working is data partition not able to format. Got an error unable to find crypto file or something. I know it's for honor 8 but just trying my luck :laugh:
dexz said:
I have flashed TWRP 3.1.0.0 from the honor 8 thread. I managed to boot to recovery. The only thing that not working is data partition not able to format. Got an error unable to find crypto file or something. I know it's for honor 8 but just trying my luck :laugh:
Click to expand...
Click to collapse
Seriously, this one? if it's like the official, I perhaps know the cause, I hope.
Edit:
I decompiled it. This is what I think is the cause, in the recovery.fstab file.
Code:
/data f2fs /dev/block/dm-0
Look into the frd-twrp by example and you'll see fully different. Already, your data isn't a f2fs partition.
franzyroy said:
Seriously, this one? if it's like the official, I perhaps know the cause, I hope.
Click to expand...
Click to collapse
Yes the one.
Edit:
I decompiled it. This is what I think is the cause, in the recovery.fstab file.
franzyroy said:
Look into the frd-twrp by example and you'll see fully different. Already, your data isn't a f2fs partition.
Click to expand...
Click to collapse
I have tried to change data partition to f2fs using twrp 3.0.2 then flashed twrp 3.1.0 and format data but it doesn't work too. Maybe you are right recovery.fstab need to modify?
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.