Related
[STOCK][C6602&C6603][4.2.2] Update to 10.3.A.0.423 [Rooted & XZDualRecovery][LB/UB]
Requirements:
Flashtool by @Androxyde
XZDualRecovery 2.5 BETA
Current FW version: 10.1.A.1.350, 10.1.A.1.434, 10.1.1.A.1.253 or 10.1.1.A.1.307 all can be updated!
Special features:
Superuser integrated in system, FULL root, no reboots when remounting /system RW!
XZDualRecovery 2.5 BETA (CWM 6.0.3.2 & TWRP 2.5.0.0) pre-installed;
Tailored FTF to minimize the chance of accidental system wiping!
No need to clear caches!
@shem2409 created a nice youtube video guide to assist you in your work, be sure to check this post for it! Thanks m8!
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
C6602: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6602: Download C6602.flashable.423.zip (Bittorrent: 686MB) and C6602_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6602.flashable.423.zip' on (the external) SDcard1;
Put 'C6602_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6602.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6602_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
C6603: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6603: Download C6603.flashable.423.zip (Bittorrent: 719MB) and C6603_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6603.flashable.423.zip' on (the external) SDcard1;
Put 'C6603_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6603.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6603_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
The first boot will be considerably slower and after a long wait at the boot animation you will see Android optimizing the apps on your phone.
After updating your NFC firmware and some update information has been displayed, all is done!
I have done this myself, using my own method and I have not found any problem yet, again! :fingers-crossed:
Enjoy! :victory:
Known XZDualRecovery Issues:
TWRP Usage warning: It seems TWRP 2.5.0.0 has issues with the internal storage, which seem related to the changes made to support encrypted storage volumes... This means the internal storage sometimes shows up almost empty (just folders) and no files. Try to use CWM when that happens.
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore a /system ONLY using any means you are familiar with so you can try again.
Root it using [Z][ROOT] DooMLoRD Easy Rooting Toolkit.
Install XZDualRecovery and then try to update again using TWRP. This time you can skip the FTF as it has already done it's job.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /tmp/XZDualRecovery, pack them up and send them to me.
Thank you
Flashable ROM Mutator:
Download AROMA ROM Mutator 0.14
This (former patch package) uses AROMA to create a user friendly menu to choose between updates to be installed.
If you want to switch from SuperSU (default in this ROM) to SuperUser (Be careful, SuperUser is incompatible with 4.2.2!) you can use this to make the change.
If you have the reboot problem when trying to remount /system writable, you can reinstall the superuser app of your preference, it's installation includes the latest patch.
If you are missing /system/bin/chargemon.stock and you want to be able to charge your phone while it's turned off.
Flash using one of the recoveries!
Version 0.13 and upwards is using AROMA 2.70B1 or better, the below warning can be ignored for now. Let me know how it performs!
AROMA Warning: AROMA currently works best in TWRP but even there it has some issues on the Z/ZL. It sometimes does not start up correctly or it has a 'sticky button' issue. It makes it a little less easy to use but this will be fixed in time. It is a combination problem caused by the new hardware and incompatibility with it and the fact the recoveries both have been updated considerably to work on the latest phones, causing issues with some functionality of AROMA.
If it hangs when trying to start, reboot your phone and try again.
If it has the sticky buttons, press the button again to activate.
You can avoid the sticky buttons by pressing them for about half a second (that means not too short and not too long). It will work, it's just showing a bug associated with the latest recoveries.
The Samsung S4, HTC One and One X and the Nexus 4 & 7 show the same issues. For them AROMA sometimes crashes, this is an issue i have not yet observed on the Z/ZL.
Thanks go to @Androxyde for the FTF creation, cheers m8!
nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Ya, I need manual install dual boot to access back to CWM/TWRP then just can install but the preinstall superuser root is not working at all.
Root working back by installing DooMLoRD Easy Rooting Toolkit (v15) - http://forum.xda-developers.com/showthread.php?t=2327472
Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?
Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.
Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.
Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.
zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
I got into the same problem, and cannot get out. Anyone has any advice?
please fix dead links
dopeee said:
nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.
Click to expand...
Click to collapse
I found out with the leak by doomlord that it would be possible to update, no need to wipe, the official update works even better
lysp said:
Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?
Click to expand...
Click to collapse
It's meant as an update process and not wiping anything will make the ROM treat your phone as one that just got updated
Faelz said:
Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.
Click to expand...
Click to collapse
Yes, you need a stock ROM before you can flash this, I would not recommend updating your phone from PAC...
bungknees said:
Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.
Click to expand...
Click to collapse
&
zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
&
chuazy said:
I got into the same problem, and cannot get out. Anyone has any advice?
Click to expand...
Click to collapse
I have modified the guide a bit as i should have done before i posted it...
Restore the kernel to anything other then the 4.2.2 one and then try to flash the update package, after flashing the update, re-flash the kernel.
I made one error in my guide: If someone is not using the correct version of XZDualRecovery (2.5 BETA) then you lose recovery when on the 4.2.2 kernel. The correct steps order to prevent this from happening are now in the OP.
please fix dead links
calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
+1
After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?
calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
buciupetru said:
Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.
Click to expand...
Click to collapse
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now
lethalfriend said:
After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?
Click to expand...
Click to collapse
No need: /data/media IS the 'new' location.
[NUT] said:
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now
Click to expand...
Click to collapse
thanks:good:efficient
[NUT] said:
No need: /data/media IS the 'new' location.
Click to expand...
Click to collapse
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location
lethalfriend said:
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location
Click to expand...
Click to collapse
Ooh... i now see what you mean... you are correct. I'll patch up the flashable package to do it automatically.
For you, use a file explorer to move the contents (skipping the 0 folder) of /data/media to /data/media/0/. Sorry man, i missed that completely on my phone
server stilll unreachable.
Hello and welcome to CM-13.0 Beta 1 !
first of all a BIG thank you to @Adrian DC wich had constributed also to this rom (he fixed the camera and helped me with the other stuffs )
Known bugs:
- sometimes the device will bootloop (only in starting phase )
USE THE FLASHABLE HOTFIX for that
- sometimes RIL may not start (on bootup)
if you encounter one of these bugs please press and hold vol+ and powerbutton to FORCE SHUTDOWN and then reboot again
Other "bug":
- selinux disabled until i patched it
Sourcecode can be found on my git:
github.com/sdtbarbarossa
How to install:
1. make sure your internal SDCard is formated to exfat (you can use Whiteneos TWRP to get that)
2. clean install the rom ( wipe cache & data & system ) [alternativeley dirtyflash.... but then dont report bugs!]
3. flash gapps (i use OPENGAPPS - ARM - 6.0 - PICO )
4. reboot
5. wait several times
Downloadlink:
https://www.dropbox.com/s/7tr42vcejk1u1js/cm-13.0-20160403-UNOFFICIAL-mint.zip?dl=0
link is up
Sent from my Xperia T using XDA Free mobile app
error executing updater binary in zip
SonyXperiakiasT said:
error executing updater binary in zip
Click to expand...
Click to collapse
Code:
ApplyParsedPerms: lsetfilecon of /system/lost+found to u:object_r:system_file:s0 failed: Operation not supported on transport endpoint
?
Got that myself, it doesn't work with TWRP 3, you need an older version, i used TWRP 2.8.6.0
(fix) flash it with philz_touch_6.12.8
Q: how do you install supersu? It doen't work from google apps and I tried to flash it from TWRP and I got a bootloop
For me installation works with TWRP from 12.1 kernel. After creation of dalvik files it never ended with "apps are starting". Killed the device (Vol+ & Power) and got never ending boot animation... tried to reinstall. Now got "Operation not supported on transport endpoint". Restored "boot" from last 12.1 nand backup, rebooted to (that funny colored) revovery, wiped again, reinstalled (BTW open_gapps-arm-6.0-pico-20160403 in queue) and now..... hey, I get a PIN screen! Wifi & Google sign in works without problem. Developer options, root access, adb shell, seems alright for now - good night and many thanks to SdtBarbarossa!
vladut.alecsandru said:
Q: how do you install supersu? It doen't work from google apps and I tried to flash it from TWRP and I got a bootloop
Click to expand...
Click to collapse
From Xperia M I know it's very tricky or nearly impossible... For me the "onboard solution" for root access is okay. (did not try yet if it really works...)
Actually you are right, I didn't enable the root access from developer options the first time.. but it works and you don't need supersu
But I had no service and after a reboot it started to bootloop again..
bootloop after a reboot
Reinstalled again.. and after each app install I rebooted to see what might cause the bootloop
For me at least, it started to bootloop after I installed and gave root access to titanium backup.
1. the bootloop is a known bug lile i said ( it is that the mediaserver dont start for a unknown reason... depending on the random queue of loading librarys )
atm i prefere everyone to reboot not often x)
bootloops should be solvable by hardboot ( vol+ and powerbutton )
then there are 2 cases:
1.lib a gets loaded before lib b => it boots
2.lib b gets loaded before lib a => it loops
there is nothing how i can controll that atm
2. if you habe trouble flashing the rom please send me a log
3. guys can it be that the no service bug only appears on first boot?
Sent from my Xperia T using XDA Free mobile app
Here's an example logcat for a boot-loop. All boot loops I got were ending with that "Waiting for service media.audio_policy..."
BTW In my case has nothing to do with Titanium Backup, it seems to be random
I'll probably test the rom today. Keep up the good work SdtBarbarossa.
mankokoma said:
Here's an example logcat for a boot-loop. All boot loops I got were ending with that "Waiting for service media.audio_policy..."
BTW In my case has nothing to do with Titanium Backup, it seems to be random
Click to expand...
Click to collapse
yes i know... thx for the log its the same i get... this bug is just as random as i explained above... hard to find the real reason
so except for the bootup problems ... how is the rom? any other problems?
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
... how is the rom? any other problems?
Click to expand...
Click to collapse
First impression's really good. Much snappier than 12.1 - expected. It was a little tricky to change the 'sdcard0' to vfat. As suggested I tried to do it with the 12.1-kernel-TWRP... first did a backup to ext-sd but after copying with TWRP-filemanager it crashed, automatically rebooted the 13-ROM, killed the dalvik and boot-looped At least sdcard0 data were transfered!
So restored kernel & data from nand backup and after successful boot, tried to format sdcard0, mentioned "corrupt" in settings-Storage&USB but ERROR occurred. So I tried with adb shell
Code:
newfs_msdos -F 32 /dev/block/mmcblk0p15
OR
Code:
mkfs.exfat /dev/block/mmcblk0p15
BOTH returned Errors (that's why I tried both) but can't remember which one was successful
In settings-Storage&USB still "corrupt", but after reboot (without problems) there was sdcard0 with 11 GB free - yeaaaah!
Pushed back all the Osmand Map Stuff and so on and now also
Camera does not complain any longer because of missing sdcard and takes photos.
GPS fix is fast and stable... That's all for now!
Ahh and yes, I can do phone calls & sms (aber das ist ja nebensächlich)
hi!
so tried last cm13 beta, thanks for your work first of all.
had same problems as @mankokoma trying to format the sdcard to vfat via WhiteNeos latest twrp (same problem I reported multiple times in the old thread if you remember), it simply does not work, sdcard stays in ext4.
then I did run the commands mankokoma suggested in adb and then I could see vfat for sdcard in twrp. but now in twrp sdcard is not accessible at all. it doesn't mount etc had to use usb otg to install cm13. and in twrp 3.0 provided with cm13, again sdcard is not accessible at all ;(
btw, I full wiped (system, cache, data and dalvik), and thanks to otg I installed cm13 beta. upon very first reboot, phone optimized all apps, but then got stuck at "Android is starting - Starting apps message" forever. I had to force shutdown and reboot, then it booted fine and could pass the wizard.
sim was detected fine.
but I see internal sdcard always damaged in settings. rebooted countless times, didn't fix the problem. and camera app FCs, probably because I don't have any sdcards available...
If I click on the sdcard damaged, and then configure and format, I get an error message, and it doesn't work.
so the rom is still not usable for me atm very sad because the rom seems very promising and so fast!
EDIT: settings do FC here when trying to enter developer settings so can't enable builtin root?!
seems that your issues are all because of the sdcard not formated to exfat... you can "revive" it by formatting to ext4 but then you can only use it in twrp... try again to format it to exfat
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
seems that your issues are all because of the sdcard not formated to exfat... you can "revive" it by formatting to ext4 but then you can only use it in twrp... try again to format it to exfat
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
yes but how?? please tell me how to do that... in twrp 3.0 it keeps giving errors...
and by the way in twrp I see file system for sdcard is already vfat now! :silly:
nvm! trying again and again in twrp I always got error messages but now in settings it seems it is recognized! great! and camera started to work now will test it wonderful!
ps: FC in developer settings is still there... how did you get root? with supersu?
EDIT: and recording videos does not seem to work?
hi
tnx for rom is very good
but in my device internal stroge is not work and im format it but this not work
please help me
hamidmf12 said:
hi
tnx for rom is very good
but in my device internal stroge is not work and im format it but this not work
please help me
Click to expand...
Click to collapse
Try this, it worked for me :
http://forum.xda-developers.com/showpost.php?p=65265674&postcount=10
AOSP 7.0 For Xperia Z5 DUAL (Abandoned currently)
Hello guys,
It takes a long time for Sony devs to add the support the dsds variant, but it's finally coming
Now I've built the AOSP 7.0 for Sony Xperia Z5 Dual.
Currently working:
*Dual Sim support
*GPS
*Bluetooth
*SMS
**Newly solved : SD card detection credits to @HaoZeke
Currently NOT working:
+Camera (Well, it's kinda work -- Sharp focus but inverted)
Current status: Broken
+Fingerprint(Sometimes doesn't work)
Supporting devices:
Currently tested on E6683, not sure about E6633.
Don't try it on other devices.
PLEASE PLEASE PLEASE back up you data ( including sd card) before flashing...
Boot.img
https://drive.google.com/file/d/0B_n...ew?usp=sharing
Credits to @HaoZeke
System.img
https://drive.google.com/open?id=0B5wyhen_cbdrTTRoc19OZW9HOWM
Userdata.img
https://drive.google.com/open?id=0B5wyhen_cbdrbW9GZGdMTmpVOWs
***UPDATE:
For recovery, download this and flash using fastboot. Then flash Gapps, and the device will be ready to use as daily driver.
(Credits to zacharias.maladroit)
http://forum.xda-developers.com/xperia-z5/development/twrp-3-0-2-cm-aosp-roms-t3373008
Procedure to get it working:
1. Unlock the bootloader
2. install adb and fastboot on your computer (Can be found easily on Google)
3. open the command windows
4, Type: fastboot -S 256M flash boot /replace with your own route/boot.img
5, Type: fastboot -S 256M flash system /replace with your own route/system.img
6, Type fastboot -S 256M flash userdata /replace with your own route/userdata.img
7, Type fastboot flash recovery /replace with your route/recovery3.0.2.img
8, Flash opengapps in the recovery
9, You're all set
****Make sure to do a full wipe before flashing the ROM.****
Please do not expect updates because I built the ROM only by exactly syncing the repo created by Sony dev. I'll update the ROM asap if there are any update in the official repo.
Sorry for bad English
Press the thanks button if you found it useful!
Credits: sonyxperiadev for all the effort on the ROM
@HaoZeke for making SD card detection work.
Great! I would definitely support this project! Keep up the goodwork!
Rom boots fine on E6633 but the sim cards don't work and camera doesn't even open.
mistercyko said:
Rom boots fine on E6633 but the sim cards don't work and camera doesn't even open.
Click to expand...
Click to collapse
For SIM Card I really don't have a clue.... It works well on my phone. I'm sorry that I can't help because I'm not a developer.
Camera can be opened by enabling the 23MP mode in settings -> extended settings -> disable the 8mp mode.
JerryLaiHMmmmmm said:
For SIM Card I really don't have a clue.... It works well on my phone. I'm sorry that I can't help because I'm not a developer.
Camera can be opened by enabling the 23MP mode in settings -> extended settings -> disable the 8mp mode.
Click to expand...
Click to collapse
You have E6633? and the sim card works?
Please tell me exactly the steps you sued to install it.
mistercyko said:
You have E6633? and the sim card works?
Please tell me exactly the steps you sued to install it.
Click to expand...
Click to collapse
I have a E6683, as stated in op.
The steps is full wipe-> install imgs by fastboot.
JerryLaiHMmmmmm said:
I have a E6683, as stated in op.
The steps is full wipe-> install imgs by fastboot.
Click to expand...
Click to collapse
Oh ok. Op said he wasnt sure about E6633 but it seems that sim support still doesn't work on it.
I have been dying to have aosp on my dual E6633 but all roms don't support dual sim e6633 .
JerryLaiHMmmmmm said:
Procedure to get it working:
1. Unlock the bootloader
2. install adb and fastboot on your computer (Can be found easily on Google)
3. open the command windows
4, Type: fastboot -S 256M flash boot /replace with your own route/boot.img
5, Type: fastboot -S 256M flash system /replace with your own route/system.img
6, Type fastboot -S 256M flash userdata /replace with your own route/userdata.img
7, Type fastboot flash recovery /replace with your route/recovery3.0.2.img
8, Flash opengapps in the recovery
9, You're all set
Click to expand...
Click to collapse
Just tried it on my E6683 DSDS
- did a clean format of all partitions
- flashed 4 imgs via fastboot
- booted nicely
- lost everything on my phone memory
- no SD card detected anywhere
- Camera does'nt even start
- SIM functions are OK
Thanks for the brilliant work... Have you perhaps asked one of the senior devs about the SD card thing...? That's the only thing keeping from jumping this as daily driver.....
HaoZeke said:
Thanks for the brilliant work... Have you perhaps asked one of the senior devs about the SD card thing...? That's the only thing keeping from jumping this as daily driver.....
Click to expand...
Click to collapse
Sorry everyone, but these days I'm really busy with my homework and tests... So I won't be able to update the rom that often.
But relax, I'll dig deeper into it later and I WON'T GIVE UP THIS ROM.
JerryLaiHMmmmmm said:
Sorry everyone, but these days I'm really busy with my homework and tests... So I won't be able to update the rom that often.
But relax, I'll dig deeper into it later and I WON'T GIVE UP THIS ROM.
Click to expand...
Click to collapse
Hey, I don't know if this is relevant but the SD card detection problem is because the precompiled kernel which is in the sony repos is built for the E6653 not E6683, which has it's kernel configuration set up here....
https://github.com/sonyxperiadev/device-sony-sumire/blob/master/aosp_e6683.mk
E6683 Kernel.
Hey I just compiled the kernel for the e6683 from source and updated the bootimage...
This fixes the SD Card issue...
Also, a word of warning; flashing userdata wipes the internal SD card as well....
https://drive.google.com/file/d/0B_nq_4gY-k85akpqTUJTR05Oc2M/view?usp=sharing
HaoZeke said:
Hey I just compiled the kernel for the e6683 from source and updated the bootimage...
This fixes the SD Card issue...
Also, a word of warning; flashing userdata wipes the internal SD card as well....
https://drive.google.com/file/d/0B_nq_4gY-k85akpqTUJTR05Oc2M/view?usp=sharing
Click to expand...
Click to collapse
Good work! Would you mind if I use this boot image as default in my OP?
JerryLaiHMmmmmm said:
Good work! Would you mind if I use this boot image as default in my OP?
Click to expand...
Click to collapse
Sure you can I'd be honored if you mention me there too
Thanks for the rom. Great work.
Both the sim cards work. Data Works. Wifi Works.
Camera opened the first time and was able to take photos. But never opens again.
I have rooted it. No problems there. Adaway does not work though. Cant update hosts file.
Most of the times the rom is butter smooth, but there is occasional stutter.
Bluetooth works. NFC works. Bluethooth audio works.
External SD card works. Thanks to @HaoZeke.
ganeshbiyer said:
Thanks for the rom. Great work.
Both the sim cards work. Data Works. Wifi Works.
Camera opened the first time and was able to take photos. But never opens again.
I have rooted it. No problems there. Adaway does not work though. Cant update hosts file.
Most of the times the rom is butter smooth, but there is occasional stutter.
Bluetooth works. NFC works. Bluethooth audio works.
External SD card works. Thanks to @HaoZeke.
Click to expand...
Click to collapse
The camera seems hit and miss. I read somewhere that the stock camera "jams" the device so don't use it. Usually and oddly, whatsapp's internal camera opens in a few tries...
Damn the camera! This is my daily driver.
Footej camera (front camera works)
is there any possibility of another update for this ROM in near future ???
chinmoy32 said:
is there any possibility of another update for this ROM in near future ???
Click to expand...
Click to collapse
Asking ETA is against the xda rule my friend.. Woww.. u got 12 thanks only for asking ETA ? :laugh:
Rajeev said:
Asking ETA is against the xda rule my friend.. Woww.. u got 12 thanks only for asking ETA ? :laugh:
Click to expand...
Click to collapse
welll................... to be honest I was not asking for ETA technically !! I was asking for yes or no type of answer , whether this is dead or alive !!!
as I am looking for nougat HAL to be more friendly to camera modifications and all.
- T W R P 3.2.3-0L [Labs Mod] -
The Swiss Army Knife TWRP Mod for the Axon 7
INTRODUCTION
This was a long term project that I have been using for a long time. I created some scripts to make it easier and faster to flash new roms and quickly restore the daily driver configuration after a testing session. For easier access I modified the TWRP interface to add direct access to the scripts. They had many problems but they were good to me since I created them and I knew how to used them well, but they were not ready for other users.
But the time has come and I have cleaned up most of the annoyances in the tools and in the UI. I have named it "Labs Mod" since it allows me to have my flashing lab on the go, making it extremely easy to switch to different configurations, or recover the daily driver configuration in a few minutes. I believe it is free of major bugs and now I can concentrate on adding new scripts, and more options to the current scripts.
FEATURES
On top of the latest improvements introduced in the official TWRP 3.2.3-0, this mod offers the following added features:
Full vendor partition support (mount, format, wipe, partition image flash, TWRP backup and restore).
Integrated Bootstack backup and restore.
Modem firmware image flash
Reboot to EDL
Button to enable device mapper verity (DM-Verity) enforcing
Button to disable the eMMC write protection (disemmcwp)
Backup/Restore internal storage to the TWRP Backup folder in the external SD. Ensure you have enough free space, free space check is not yet implemented.
EDL backup zip creation. Dual zip use since the resulting zip can be installed using TWRP from the phone or using MiFlash from the computer. It offers the following package creation options:
OS: Operating system (boot, vendor and system).
GPT: Partition table only.
CONFIG: Device config data (IMEI, SN, MAC, etc).
BOOTSTACK: Boot firmware without modem.
MINIMAL: Includes GPT+bootstack+modem+recovery.
EMERGENCY: Minimal + device config.
FULL: Minimal + OS.
FACTORY: Includes Full + config.
Integrated Treble PARTY tool for creating and removing the vendor partition. Vendor partition is required for Treble ROMs. Removal is required for flashing old non-treble roms.
Lockscreen security removal. Removes password, pattern, fingerprint, etc... (in case you forget your password or the security descriptor gets corrupted).
Google account binding removal (in case you want to wipe from within recovery and test with different google accounts).
Bootloader unlock message removal.
New! Expand OS partitions (Vendor and System) to fit the whole partition. Useful for expanding the GSI filesystem for having space for adding GApps or moving apps to system.
New! Deep Wipe function performs a low level wipe of the partition data, erasing the remaining the portions of the eMMC that stored the partition information.
REQUIREMENTS
You need an unlocked Axon 7
INSTALLATION
WARNING, THIS SOFTWARE COULD WIPE ALL THE DATA IN YOUR DEVICE, INCLUDING THE INTERNAL STORAGE.
IT REQUIRES TWRP CUSTOM RECOVERY IN AN UNLOCKED DEVICE, OTHERWISE YOUR DEVICE COULD BE BRICKED.
!!! Whatever you do, it is at your own risk !!!
Follow these steps:
1. Download the TWRP Labs Mod image to your External SD card.
2. Boot to TWRP and select the Install option in the main manu.
3. Tap on the install image button and select your external SD. select the image file you downloaded, select the recovery partition and confirm.
4. Reboot to recovery again to ensure the changes are applied properly.
DOWNLOAD
TWRP_3.2.3-0L_v1.3-Axon7-Labs_Mod.img Flavor of the mod using the official TWRP 3.2.3-0 Kernel binary (Quick boot even when using F2FS, full ADB support, NO B12 Oreo encryption). Use this if you do not plan on using device encryption. Please note that you won't be able to use any tool of this version if your device is encrypted.
TWRP_3.2.3-0L_v1.3.B12-Axon7-Labs_Mod.img Device encryption enabled flavor of the Labs mod. It use the 3.2.1-8 TWRP Kernel binary (Long boot when using F2FS, NO ADB support, B12 Oreo encryption). Use this one if you use device encryption. Please note that this flavor doesn't support adb interface.
NOTES
1. I do not have the time and expertise to dig into kernel hack so this is why I do not provide a unified kernel with fast F2FS boot, ADB and B12 encryption. Probably people developing kernels could help on this issue. It would be nice having a kernel with proper F2FS boot support, B12 encryption and ADB interface. Until then, there is no other way than having 2 flavors depending on the features we require.
SOURCES
C'mon, all of them are scripts!!! the sources are at glance. Use them in your projects but don't forget to give credit to the source !!!
CREDITS
@NFound for the recovery kernel binary supporting Oreo B12 encryption.
@someone755 for the keycheck binary I use in my scripts.
@Chainfire for the TWRP install script hacks.
I hope you enjoy it as much as I did creating and learning throughout the enlightenment journey.
Nice.
Any info on the scripts that are included?
voetbalremco said:
Nice.
Any info on the scripts that are included?
Click to expand...
Click to collapse
Well, all of them are Bourne shell scripts. Some of them are stupidly simple such as those in the Reboot menu, and others in the Advanced > Oki Labs menu are very elaborated, specially:
- PARTY tool: for creating and removing the vendor partition. I released it a few days ago as a separated tool that could well work in other devices.
- EDL backup: for creating EDL flashable backups of a configuration. This tool will probably require a full thread due to the concepts involved. The big feature is that the generated zip can be also flashed using any TWRP.
- Internal Storage Backup/Restore: TWRP doesn't offer a straightforward solution for backing up the internal storage, since it is excluded from the data backup, now it is possible to create a backup and restore the contents of the internal SD in case you want to mess up with the userdata partition. Now this script creates a set of files under the TWRP/backup folder. I am planning to add the possibility of having different backup folders, the same way the GUI treats the data partition.
That is looking very sweet!!!
I'm excited, nice work man!
This is just fantastic!
Well, the non b12 version can't decrypt my device, running los 15.1
also, the lab options did nothing, and when I pressed on PARTY the recovery froze on me.
Hmm.
nfsmw_gr said:
Well, the non b12 version can't decrypt my device, running los 15.1
also, the lab options did nothing, and when I pressed on PARTY the recovery froze on me.
Hmm.
Click to expand...
Click to collapse
Well, that's why in the OP I provide 2 flavors of the mod. If you require decrypt then you have to use the B12. PARTY will not work either if your device is encrypted and you are using the 3.2.3-0L. In your case, using device encryption, you have to use the 3.2.3-0L(B12). You will have all the functions except for ADB. PARTY will work fine too.
Oki said:
Well, that's why in the OP I provide 2 flavors of the mod. If you require decrypt then you have to use the B12. PARTY will not work either if your device is encrypted and you are using the 3.2.3-0L. In your case, using device encryption, you have to use the 3.2.3-0L(B12). You will have all the functions except for ADB. PARTY will work fine too.
Click to expand...
Click to collapse
Got it.
I thought the B12 version was for stock-based ROMs.
Okay I'll flash the other one once I get home, thanks.
nfsmw_gr said:
Got it.
I thought the B12 version was for stock-based ROMs.
Okay I'll flash the other one once I get home, thanks.
Click to expand...
Click to collapse
I'll clarify it a bit more to avoid any misunderstanding. Sorry about that.
Oki said:
I'll clarify it a bit more to avoid any misunderstanding. Sorry about that.
Click to expand...
Click to collapse
Thnx for this tool ! I'll test that this weekend.
It would be great if you'd make a small guide on this with a couple of situations / a possible indepth review with screens / what's possible and what's definitely not possible with this twrp tool.
Anyway seems very promising :good:
Sheesh...i have no external sd card
I have garde flashed your TWRP_3.2.3-0L (B12) -Axon7-Labs_Mod.img but this version says when starting in twrp that my password is wrong. the version 3.2.1.8 of nfound unlocks my password quite normal
Excellent Job! I can't wait to get back my Axon 7 from RMA Services. I'm just going to need sometime to get this running coming from stock MIflavor.
Found bug. Installed the ADB version (thanks Cthulu!), wanted to check the functionality.
Went into the Storage Backup and my phone froze. Rebooting from ADB worked.
EDIT: tried to reproduce the issue - same thing happened 2nd time.
EDIT2: It freezes at any option in Oki Labs
docentore said:
Found bug. Installed the ADB version (thanks Cthulu!), wanted to check the functionality.
Went into the Storage Backup and my phone froze. Rebooting from ADB worked.
EDIT: tried to reproduce the issue - same thing happened 2nd time.
EDIT2: It freezes at any option in Oki Labs
Click to expand...
Click to collapse
I can't duplicate the issue. Are you sure you downloaded it properly? Do you have an SD card? The backup requires an SD card with enough space. Checking for free space is in the todo list for this weekend.
raystef66 said:
Thnx for this tool ! I'll test that this weekend.
Anyway seems very promising :good:
Click to expand...
Click to collapse
Not good enough!
It is downloaded properly. SD card has more than 100gb free space.
As mentioned in edit it is any option that I used in Oki Labs menu that froze my phone
docentore said:
It is downloaded properly. SD card has more than 100gb free space.
As mentioned in edit it is any option that I used in Oki Labs menu that froze my phone
Click to expand...
Click to collapse
What option are you testing? the Storage Backup? What format are you using in your SDCard? Does it happen at the beginning or after a while? Is there any file under TWRP/BACKUPS/STORAGE in your Micro SD after the failure?
@Oki this is amazing. Thank you.
Is it possible to use the recently released kernel sources from los15 to solve the issue of needing two revisions?
DISCLAIMER
By using this ROM, you agree that the developer is not responsible for any physical damage caused to you or your device, or non-physical damage which includes but not limited to:
- broke up with gf due to missed phone calls
- got fired by bossku due to missed alarm
- drove your car into the sea due to faulty GPS
- got caught while traveling in Japan because your camera has no shutter sound
- got last place in kahoot quiz due to device lagging
- accidentally fried the egg due to device overheating
Continue to read this thread only if you agree.
Click to expand...
Click to collapse
LineageOS 14.1 for Samsung Galaxy Note N7000
Beware, you are about to enter a danger zone!
ABOUT
This is more of like a learning attempt, as I never build cm-14.1 for n7000 before. Besides that, I think that it might be useful if I can rework the device sources to make it more proper and organized. I hope this build with new security patch will benefit people who wants to stay on cm-14.1.
CREDITS
All my builds are fully based on works by @rINanDO, @bauner, @ChronoMonochrome, fourkbomb, numerous n7000, Exynos4 and LineageOS developers. Full credits goes to all the developers. I hope no one is being left out, please notify me if there is.
INSTALLATION
All my builds are emulated storage capable. Repartition is required to install my builds.
And also, please backup EFS partition and store in a dry, safe place.
The below instructions assumes that your device has TWRP IsoRec installed, and all your data will be destroyed in the process.
1. Choose your desired emulated storage partitioning configuration: - Android 9/10 capable: lanchon-repit-20170115-system=1.5G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip
- Android 7.1.2 capable: lanchon-repit-20170115-system=1G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip
* Emulated + Non-emulated Internal Storage: change the values of -sdcard=min+wipe to -sdcard=4G+wipe, where 4G is your desired non-emulated Internal Storage size.
The last option provides best compatibility, as non-emulated storage ROMs will work as intended on such partitioning, and emulated storage ROMs will detect the non-emulated storage as an SD Card.
This allows you to switch back-and-forth between emulated capable and non-emulated capable ROMs without repartitioning.2. Reboot into recovery. Flash emulated storage capable TWRP IsoRec (flash as Image to Recovery): i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img
3. Reboot recovery. Flash i9100-to-n7000 TWRP conversion: lanchon-twrp-patcher-20160417-n7000.zip
4. Reboot recovery. Flash the repartition script that you have chosen in Step 1.
5. Reboot recovery. Wipe /cache, /system, Non-emulated Storage. Then, run Format Data.
6. Proceed to flash my builds.
7. Flash ARM nano GAPPS and SU if desired.
8. Prepare a coffee or tea and sit back on your couch. Reboot system.
DOWNLOAD
Icedrive
XDA:DevDB Information
LineageOS 14.1, ROM for the Samsung Galaxy Note GT-N7000
Contributors
lee.wp14
Source Code: https://github.com/hikuii
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: TWRP 3.3.1-1 (Emulated Storage Compatible)
Based On: LineageOS
Version Information
Status: Testing
Created 2020-05-11
Last Updated 2020-05-26
LineageOS 14.1
LATEST BUILD
lineage-14.1-20200511-UNOFFICIAL-n7000
kernel-4c4d93693090e956abb234bca54368d46be42981
NOT WORKING/UNTESTED
- GPS/AGPS: untested
- DRM: untested
BUILD-SPECIFIC NOTES
- CPU Hotplug is disabled, please monitor battery usage.
- Thermal throttle for CPU is set to 1.2GHz at 69C, stop at 64C. Memory is 90C and stop at 85C.
INSTALLATION NOTES
- Nougat builds have DEXPREOPT disabled as it breaks the system on Exynos platform. Thus, first boot will take longer than usual.
CHANGELOG20200511
- Initial build.
Reserved
Thats great
plz help me i m stuck at flashing the script
Reboot recovery. Flash the repartition script that you have chosen in Step 1.
every time i flash the script Android 9/10 capable: lanchon-repit-20170115-system=1.5G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip
- Android 7.1.2 capable: lanchon-repit-20170115-system=1G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip
i try it the first didnt work also the second i mean i didnt try it together but i mean non of thes files working
there is an error says unable to mount all partions from sd card
same massege from memory card i tryied everything but didnt work man
installing from internal didnt work '
installing from memory card didnt work ???????????
Adham_android said:
plz help me i m stuck at flashing the script
Reboot recovery. Flash the repartition script that you have chosen in Step 1.
every time i flash the script Android 9/10 capable: lanchon-repit-20170115-system=1.5G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip
- Android 7.1.2 capable: lanchon-repit-20170115-system=1G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip
i try it the first didnt work also the second i mean i didnt try it together but i mean non of thes files working
there is an error says unable to mount all partions from sd card
same massege from memory card i tryied everything but didnt work man
installing from internal didnt work '
installing from memory card didnt work ???????????
Click to expand...
Click to collapse
Not sure what you mean by that error mentioned. Can you attach some pictures for reference?
lee.wp14 said:
Not sure what you mean by that error mentioned. Can you attach some pictures for reference?
Click to expand...
Click to collapse
https://b.top4top.io/p_1607stgxn1.jpg
Adham_android said:
https://b.top4top.io/p_1607stgxn1.jpg
Click to expand...
Click to collapse
The logs are pretty self-explanatory, repit requires you to run from /tmp. When the location of repit is to be unmounted during repartition, it will fail and require you to flash again from /tmp.
So you just copy the zip file to /tmp and flash from there.
lee.wp14 said:
The logs are pretty self-explanatory, repit requires you to run from /tmp. When the location of repit is to be unmounted during repartition, it will fail and require you to flash again from /tmp.
So you just copy the zip file to /tmp and flash from there.
Click to expand...
Click to collapse
i opend the file manager and go to /tmp and i found the script file there i didnt copy it so i try to install but didnt work the same massege appears ?
second question : tmp folder located in which storage exactly ?
Adham_android said:
i opend the file manager and go to /tmp and i found the script file there i didnt copy it so i try to install but didnt work the same massege appears ?
second question : tmp folder located in which storage exactly ?
Click to expand...
Click to collapse
Attach a picture of the error after you flash from /tmp.
Or maybe, manually unmount /sdcard1 and flash again from /tmp.
/tmp is not a storage, /tmp is a linux tmpfs, it is not a persistent storage. Think of it as a RAM.
You couldn't just update the assembly from bauner. Security patch. Or can your assembly be put on top of a bauner assembly?
Thanks for this ROM this is the most stable rom i have ever used and it gives me excellent performance much better than samsung own touchlagwiz on jellybean 4.1.1 the only issue i have encountered i the horrendrously bad battery life and overheating the phone gets so hot that you can boil a drop of water on it.
Sorry if I wasted your precious time.
Regards.
Even if it's an older version of Android, this one (LOS 14.1) might give the best experience of the currently maintained (2? ^^" ) N7000 ROMs.
Has anyone used this rom and the LineageOS 16.0 one also from lee.wp14? To have some feedback on responsiveness and RAM usage? To confirm of deny the above hypothesis.
tuxayo said:
Even if it's an older version of Android, this one (LOS 14.1) might give the best experience of the currently maintained (2? ^^" ) N7000 ROMs.
Has anyone used this rom and the LineageOS 16.0 one also from lee.wp14? To have some feedback on responsiveness and RAM usage? To confirm of deny the above hypothesis.
Click to expand...
Click to collapse
I used that Android 9 ROM but lot of times system ask to close or wait apps not responding, so I think it is too slow for daily usage (even with Lspeed and FDE.ai installed).
EDIT: Unfortunately it seems that it cannot install magisk in this ROM
and actually the Lineage 16 build with the LSpeed performance preset and trimming the partitions seems reasonably performant.