Hello people. My device is not listed in DEVDB options, so I must have to create this thread instead a DEVDB project. If it is wrong, please advice me.
-----------------------------------------------------------------------------------
I'm creating this thread to give us more space to create a ROM for our device, like a step-by-step to things we have to do or not. I'll edit this thread with more details when I have more time, but for now, thats what we have done, and I think we need to do:
Root (Thanks to Chainfire)
Custom recovery (thanks to Shreps)
Choose a kitchen to manage the ROM
Discover kernel options
Choose apps to add/remove
A custom app to manage various phone settings, like kernel options, battery settings, and others
Edit build.prop to get right device management
Edit boot.img to have unsecure boot
Help me to add or remove things to the list above, to have a structured plan to build the whole ROM (boot, recovey, system), because last time I manage a ROM was a long time ago, I think about 2010 (was on Xperia X2), and was only for me (my "project" wasn't public). From that time for actual days, I don't manage/create nothing "solid" and structured anymore... And I'm sure all things have changed/updated/died/etc...
To help start familiar with new kitchens (the last was DSIXDA Kitchen), I have choose SuperR's Kitchen. I try to use it inside Cygwin, but it gives me an error while opening, I'm investigating this. So, I setup a virtual machine with Ubuntu in my house, and I have remote access to it from my work. In this VM, I setup the kitchen and (after a time to setup the right Java) it is running fine.
So, let's go, people. I'll edit this post as news are coming.
[UPDATE]What I have found:
If "Google Photos" is removed, then Gallery don't crop wallpapers, or adds a image to a contact;
Titanium Backup can't uninstall/integrate some apps and updates. It says "apk not found". I'm trying to use Link2SD;
SuperSU "lose" the configuration, forcing me to remove the apps I added, then run the app again. I'm looking for this
If you remove "Theme Center", you can't change wallpaper and Lenovo Home gives an error!
If you remove "Google App", "Now Launcher" gives errors about force close.
If you remove LenovoID, Settings force close when try to enter "accounts".
If we integrate "Google Play Services" and hard reset the phone, it force close at second stage of first registration.
romulocarlos said:
Hello people. My device is not listed in DEVDB options, so I must have to create this thread instead a DEVDB project. If it is wrong, please advice me.
-----------------------------------------------------------------------------------
I'm creating this thread to give us more space to create a ROM for our device, like a step-by-step to things we have to do or not. I'll edit this thread with more details when I have more time, but for now, thats what we have done, and I think we need to do:
Root (Thanks to Chainfire)
Custom recovery (thanks to Shreps)
Choose a kitchen to manage the ROM
Discover kernel options
Choose apps to add/remove
A custom app to manage various phone settings, like kernel options, battery settings, and others
Edit build.prop to get right device management
Edit boot.img to have unsecure boot
Help me to add or remove things to the list above, to have a structured plan to build the whole ROM (boot, recovey, system), because last time I manage a ROM was a long time ago, I think about 2010 (was on Xperia X2), and was only for me (my "project" wasn't public). From that time for actual days, I don't manage/create nothing "solid" and structured anymore... And I'm sure all things have changed/updated/died/etc...
To help start familiar with new kitchens (the last was DSIXDA Kitchen), I have choose SuperR's Kitchen. I try to use it inside Cygwin, but it gives me an error while opening, I'm investigating this. So, I setup a virtual machine with Ubuntu in my house, and I have remote access to it from my work. In this VM, I setup the kitchen and (after a time to setup the right Java) it is running fine.
So, let's go, people. I'll edit this post as news are coming.
Click to expand...
Click to collapse
nice thread
romulocarlos said:
Hello people. My device is not listed in DEVDB options, so I must have to create this thread instead a DEVDB project. If it is wrong, please advice me.
-----------------------------------------------------------------------------------
[*]Titanium Backup can't uninstall/integrate some apps and updates. It says "apk not found". I'm trying to use Link2SD;
Click to expand...
Click to collapse
I randomly found this thread and noted that you are facing this issue with TB being unable to uninstall some apps. I had the same issue with my device. If you are rooted, navigate to /Cust/Channel/Preinstalled/apps folder (sometimes the "channel" folder may not exist) from your file explorer, you will find the apks for the apps that TB fails to find apk for. Remove the APKs that you don't need and/or move them wherever you feel is right for them, all set
nandakalyan said:
I randomly found this thread and noted that you are facing this issue with TB being unable to uninstall some apps. I had the same issue with my device. If you are rooted, navigate to /Cust/Channel/Preinstalled/apps folder (sometimes the "channel" folder may not exist) from your file explorer, you will find the apks for the apps that TB fails to find apk for. Remove the APKs that you don't need and/or move them wherever you feel is right for them, all set
Click to expand...
Click to collapse
Yeah, I already see that folder. Seems TB can't handle with folders different from /system/app and /data/app
romulocarlos said:
Yeah, I already see that folder. Seems TB can't handle with folders different from /system/app and /data/app
Click to expand...
Click to collapse
Yes, that seems to be the case for LP and MM factory images that have this folder, it is a TB limitation even on my device, unless I am running CM or AOSP based ROMs hope the workaround helps
nandakalyan said:
Yes, that seems to be the case for LP and MM factory images that have this folder, it is a TB limitation even on my device, unless I am running CM or AOSP based ROMs hope the workaround helps
Click to expand...
Click to collapse
You have A6020 with CM??
romulocarlos said:
You have A6020 with CM??
Click to expand...
Click to collapse
No, I have an Honor 5x L-22, we have a CM build for our device but I chanced on this issue when I was running stock and wanted to get rid of all that bloat. So just sharing what I discovered
nandakalyan said:
No, I have an Honor 5x L-22, we have a CM build for our device but I chanced on this issue when I was running stock and wanted to get rid of all that bloat. So just sharing what I discovered
Click to expand...
Click to collapse
Ok!! Thanks!
Can you please tell me how the camera quality is..I'm planning on buying this mobile...so please let me know
sudheer4188 said:
Can you please tell me how the camera quality is..I'm planning on buying this mobile...so please let me know
Click to expand...
Click to collapse
It's not great but for the price is quite good
Did you see kernel source code from lenovo's website for Vibe K5?
lucasdeeiroz said:
Did you see kernel source code from lenovo's website for Vibe K5?
Click to expand...
Click to collapse
Yes
Sent from my Lenovo A6020l36 using XDA-Developers mobile app
romulocarlos said:
Hello people. My device is not listed in DEVDB options, so I must have to create this thread instead a DEVDB project. If it is wrong, please advice me.
-----------------------------------------------------------------------------------
I'm creating this thread to give us more space to create a ROM for our device, like a step-by-step to things we have to do or not. I'll edit this thread with more details when I have more time, but for now, thats what we have done, and I think we need to do:
Root (Thanks to Chainfire)
Custom recovery (thanks to Shreps)
Choose a kitchen to manage the ROM
Discover kernel options
Choose apps to add/remove
A custom app to manage various phone settings, like kernel options, battery settings, and others
Edit build.prop to get right device management
Edit boot.img to have unsecure boot
Help me to add or remove things to the list above, to have a structured plan to build the whole ROM (boot, recovey, system), because last time I manage a ROM was a long time ago, I think about 2010 (was on Xperia X2), and was only for me (my "project" wasn't public). From that time for actual days, I don't manage/create nothing "solid" and structured anymore... And I'm sure all things have changed/updated/died/etc...
To help start familiar with new kitchens (the last was DSIXDA Kitchen), I have choose SuperR's Kitchen. I try to use it inside Cygwin, but it gives me an error while opening, I'm investigating this. So, I setup a virtual machine with Ubuntu in my house, and I have remote access to it from my work. In this VM, I setup the kitchen and (after a time to setup the right Java) it is running fine.
So, let's go, people. I'll edit this post as news are coming.
[UPDATE]What I have found:
If "Google Photos" is removed, then Gallery don't crop wallpapers, or adds a image to a contact;
Titanium Backup can't uninstall/integrate some apps and updates. It says "apk not found". I'm trying to use Link2SD;
SuperSU "lose" the configuration, forcing me to remove the apps I added, then run the app again. I'm looking for this
If you remove "Theme Center", you can't change wallpaper and Lenovo Home gives an error!
If you remove "Google App", "Now Launcher" gives errors about force close.
If you remove LenovoID, Settings force close when try to enter "accounts".
If we integrate "Google Play Services" and hard reset the phone, it force close at second stage of first registration.
Click to expand...
Click to collapse
hey can you tell me how root it and install TWRP.. thanks
nayakdinesh said:
hey can you tell me how root it and install TWRP.. thanks
Click to expand...
Click to collapse
Please, do not quote OP. Here is the link for what you requested: http://forum.xda-developers.com/showthread.php?t=3391100
Enviado de meu pac_A6020 usando Tapatalk
is there any custom kernel for this phone which cn provide dt2w ...
heeeelpp
I need rom L35 and not of a40 , my phone is stuck in the screen lenovo without TWRP and without backup
jrfirmino said:
I need rom L35 and not of a40 , my phone is stuck in the screen lenovo without TWRP and without backup
Click to expand...
Click to collapse
Do not spam at XDA or you won't get any help. Search an appropriate thread to make your question AFTER reading all posts from there.
Here isn't the appropriate thread.
Why did the OP marked [kernel] if there's not a kernel available here? That's not fare.
louiscypherbr said:
Why did the OP marked [kernel] if there's not a kernel available here? That's not fare.
Click to expand...
Click to collapse
@romulocarlos
No kernel yet ?
louiscypherbr said:
Why did the OP marked [kernel] if there's not a kernel available here? That's not fare.
Click to expand...
Click to collapse
The original idea was build a kernel, too.
Hnk1 said:
@romulocarlos
No kernel yet ?
Click to expand...
Click to collapse
No. Now we have CM13, thanks to Shreps, so this thread is obsolete.
Related
Rom updated. Compiled from Cyanogenmode latest sources on April 29. All fixes (battery/audio/wifi) incorporated in code before compiling, so there is no need to decompile individual apps. Also, I have changed default network from WCDM to LTE/GSM, which means that your phone should connect to LTE/4G right on reboot.
CHANGES: Numerous ranging from improving network to better ram management. If you look at commits, they go between 4 days to 6 months old.
Remember, this is not a port or cooked up rom, it has been fully compiled from sources. Enjoy.
SOURCES: https://github.com/CyanogenMod/android/tree/jellybean
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Here is another CM10 rom for IONs with locked bootloaders. This one is based on original CM10 experimental build by Jenkins. So, it is a slightly different build from that of FXP based MrGezz's one.
Changes:
1. Rom completely rebuilt
2. All my patches (Wifi/Battery) included, so, no need to flash anything post installation
3. Google Analytics disabled
4. Newer Camera and Gallery included
5. Dock enabled in Settings (I think)
6. A few stock alarm, ringtones and notification sounds added
7. All apps re-signed with the same key to fix bootloop
BUGS: same as in all CM based roms
CREDIT: Cyanogen Team; MrGezz/Letama/Olivier for initial LB patch
INSTRUCTIONS:
Fresh Install (recommended)
1. Have JB latest Stock Kernel, Roger's Baseband in case of LT28i, Root and Recovery
2. Format System/Data/Cache in TWRP or Mount and Format the same in CWM
3. Install the ROM and Reboot. Nothing else is needed
If you are already on CM-10 by Mr.Gezz, you might be able to restore your Data partition. In this case, after
initial installation steps above:
1. Reboot, let the rom settle, then restart the phone and go to TWRP
2. Restore your previously backed up CM-10 rom: DATA ONLY!!! The only thing you might have different is if you had a different SU app, you now might have two. In this case, delete the one you are not going to use. Although, this method should work fine, the preferred way is always: Fresh Install
WARNING!!! Back up your rom prior to new install. As usual, I am not responsible for bricking your device, cold war, WW3 or total annexation of your country by mother Russia (which may happen anyway regardless of this install). If you dare to complain after this fair warning, I will forward your grievances to Mr. Putin.
P.S. I have not tested this version of the rom on the phone, but the original CM10 version by Jenkins works fine with LB patch. Also, I have confirmed that re-signing all system apps gets rid of bootloops when patched framework and settings apps are incorporated in the rom. But again, don't forget to back up your current rom.
XDA:DevDB Information
Cyanogen 10 for Locked Bootloaders, a ROM for the Sony Xperia Ion
Contributors
optimumpro
ROM OS Version: 4.1.x Jelly Bean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: JB Stock 4.1.2
Based On: Original CyanogenMod by Jenkins
Version Information
Status: Stable
Stable Release Date: 2014-03-21
Created 2014-03-21
Last Updated 2014-04-30
Just got it up and running. No problems to report..everything seems to be working so far.
The recent apps crash that I was experiencing with other CM based roms is not there in this rom. Thanks for this very light and speedy rom.
EDIT: you forgot to add the web browser or was that intentional?
imm1304 said:
Just got it up and running. No problems to report..everything seems to be working so far.
The recent apps crash that I was experiencing with other CM based roms is not there in this rom. Thanks for this very light and speedy rom.
EDIT: you forgot to add the web browser or was that intentional?
Click to expand...
Click to collapse
Yes, I did forget web browser. It is attached. Just transfer to system/app with correct permissions.
optimumpro said:
Yes, I did forget web browser. It is attached. Just transfer to system/app with correct permissions.
Click to expand...
Click to collapse
Thanks for the browser.
Had problems with the CM file manager. After transferring to system/app and changing permissions, the file manager force-closed. And from this point on, it FC'd every time I tried to launch it. And also started getting random calendar app FC toast when I wasnt trying to run the calendar app.
I re-flashed the rom and got this done with root explorer and now there are no FC's.
imm1304 said:
Thanks for the browser.
Had problems with the CM file manager. After transferring to system/app and changing permissions, the file manager force-closed. And from this point on, it FC'd every time I tried to launch it. And also started getting random calendar app FC toast when I wasnt trying to run the calendar app.
I re-flashed the rom and got this done with root explorer and now there are no FC's.
Click to expand...
Click to collapse
CM based roms are sensitive to tethering with system apps. You got to set permissions the right way.
optimumpro said:
2. All my patches (Wifi/Battery) included, so, no need to flash anything post installation
Click to expand...
Click to collapse
Does the web browser need to be installed?
optimumpro said:
3. Google Analytics disabled
Click to expand...
Click to collapse
I'm curious, how exactly do you disable Google Analytics?
EEngineer said:
Does the web browser need to be installed?
I'm curious, how exactly do you disable Google Analytics?
Click to expand...
Click to collapse
You do need to instal the original web browser unless you use something else. Google Analytics? You decompile an app, go to the corresponding XML file and change "true" to "false." Or if you want to delete it you delete several files...
optimumpro said:
Google Analytics? You decompile an app, go to the corresponding XML file and change "true" to "false." Or if you want to delete it you delete several files...
Click to expand...
Click to collapse
When you say "decompile" do you mean unzip the APK?
optimumpro said:
CM based roms are sensitive to tethering with system apps. You got to set permissions the right way.
Click to expand...
Click to collapse
For future reference, please tell me the right way to set permissions. Would rebooting into recovery and setting permissions this way be safer? I don't have a strong background in these things but I am happy to follow instructions.
Also, I installed xperia_launcher3.apk that I found on xda. Its a light 1MB launcher and sort of gives me best of both worlds in terms of sony appearance. Do you recommend making this a system app and removing trebuchet or will trebuchet just be sleeping while xperia launcher is running as the default?
EEngineer said:
When you say "decompile" do you mean unzip the APK?
Click to expand...
Click to collapse
No. There is a lot more to it. Just search xda on how to decompile an app.
imm1304 said:
For future reference, please tell me the right way to set permissions. Would rebooting into recovery and setting permissions this way be safer? I don't have a strong background in these things but I am happy to follow instructions.
Also, I installed xperia_launcher3.apk that I found on xda. Its a light 1MB launcher and sort of gives me best of both worlds in terms of sony appearance. Do you recommend making this a system app and removing trebuchet or will trebuchet just be sleeping while xperia launcher is running as the default?
Click to expand...
Click to collapse
Don't ever fix permissions on custom roms for locked bootloaders, you will never boot. With the new launcher installed, try to freez trebuchet, if everything works, then delete it. Yes, it makes sense to put the launcher in system with right permissions.
optimumpro said:
Don't ever fix permissions on custom roms for locked bootloaders, you will never boot. With the new launcher installed, try to freez trebuchet, if everything works, then delete it. Yes, it makes sense to put the launcher in system with right permissions.
Click to expand...
Click to collapse
thanks a lot for the guidance. I will keep that in mind about fixing permissions.. big no no.
imm1304 said:
Also, I installed xperia_launcher3.apk that I found on xda. Its a light 1MB launcher and sort of gives me best of both worlds in terms of sony appearance. Do you recommend making this a system app and removing trebuchet or will trebuchet just be sleeping while xperia launcher is running as the default?
Click to expand...
Click to collapse
Hi @imm1304, can you tell me the link to that xda forum where you got the xperia launcher? I'd like to read more on that and install on this rom...
intoxic8 said:
Hi @imm1304, can you tell me the link to that xda forum where you got the xperia launcher? I'd like to read more on that and install on this rom...
Click to expand...
Click to collapse
Here is the link: http://forum.xda-developers.com/showthread.php?t=2368506
imm1304 said:
Here is the link: http://forum.xda-developers.com/showthread.php?t=2368506
Click to expand...
Click to collapse
Thanks. is it stable on this rom? will give this a try later...
---------- Post added at 10:23 AM ---------- Previous post was at 10:20 AM ----------
optimumpro said:
P.S. I have not tested this version of the rom on the phone, but the original CM10 version by Jenkins works fine with LB patch. Also, I have confirmed that re-signing all system apps gets rid of bootloops when patched framework and settings apps are incorporated in the rom. But again, don't forget to back up your current rom.
Click to expand...
Click to collapse
just curious what rom are you using if not this?
---------- Post added at 10:42 AM ---------- Previous post was at 10:23 AM ----------
too bad the xperia launcher is no longer being updated...
I really want a cm rom but with the same look and feel of sony xperia launcher ui... that's why I always go back to stock based rom...
any good xperia launcher recommendation that will work on cm10?
intoxic8 said:
Thanks. is it stable on this rom? will give this a try later...
---------- Post added at 10:23 AM ---------- Previous post was at 10:20 AM ----------
Click to expand...
Click to collapse
this is stable .. i used it for a day. I added stock sony widgets from the same page and it all works as it should.
the one down side so far is that the unread counter is a separate app that isnt free. I didnt buy it.
[COLOR="Silver" said:
[/COLOR]
just curious what rom are you using if not this?
Click to expand...
Click to collapse
Slimbean by Olivier with my modifications. It is the lightest of all CM based roms, has more ram and has no google analytics at all.
optimumpro said:
Don't ever fix permissions on custom roms for locked bootloaders, you will never boot.
Click to expand...
Click to collapse
Then how do you fix permissions on a custom ROM? I've found that fixing permissions every few months fixes forced close (FC) problems.
EEngineer said:
Then how do you fix permissions on a custom ROM? I've found that fixing permissions every few months fixes forced close (FC) problems.
Click to expand...
Click to collapse
You can't fix permissions on a custom rom for locked bootloaders. If you don't install rougue apps, there is no need to fix permissions. If you experience f/cs, you should clear settings in individual apps. If that doesn't help, you could try to restore system partition of your rom (of course it needs to be backedup first).
~EDITED~
Q&A for [ROM] [Alpha] Unoffcial CM12 for d2tmo
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [Alpha] Unoffcial CM12 for d2tmo. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
CM12 for D2tmo
i installed CM12 but it does not detect my simcard PLZ help
Cant wait for new Lollipop roms!!!
Do you know if any time soon there will be a fix for mobile data?
thanks for effort
menace211 said:
Cant wait for new Lollipop roms!!!
Click to expand...
Click to collapse
Yeah, if they turn out like KitKat Roms I'm heading back to touchwiz jellybean, stock.
Liquidsmooth lollipop for S3
Hi,
Here are some builds for the S3, including the d2tmo. I've loaded the but had to go back to backup , there is a bug (black screen) with lollipop that i could not stay with it.
Sorry .. they did not allow me to put in the message an outside link to the downloads
Adam
fully functional work around to get lollipop on s3 d2tmo t999l
after doing a lot of research i have sucsesfully installed lollipop onto my s3 and got the camera to work with the camera for android app from the play store. the data also works the build i installed is the 12-20141125-unofficial-d2att after changing the script file to include d2tmo instead of the d2att. works great no real bugs except the time stamp on hangout mesages which is fixed by setting the time on the phone to network but turning of the reginal time set. thought this would be nice to share.
ps: stock camera and google camera still do not work but everything else does so this can be used as a daily driver links below to camera and build:
camera: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
build: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Added screen shots of apps used speed test and the edit that needs to be made to script file to make installable
lollipop for d2tmo install instructions
WHAT YOU NEED
the build location:
12-20141125-unofficial-d2att link: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
in the same link is superSU
also will need gapps 5.0 lollipop
"camera for android" ( stock camera and google camera DOES NOT work)
link: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
total commander
instructions to exit the updater-script file to make the build installable on your d2tmo
1. open the file in total commander
2. META-INF> COM>GOOGLE>ANDROID
3. open and edit the updater-script by long pressing the file choosing unpack+edit
4. change d2att to d2tmo in the first line P.s. theres two words change both
5. go back and the editing is done now just wipe everything and flash just like any other rom the boot up takes about 8 to 9mins so dont worry about it being stuck in a loop, it isn't
do not forget to download superSU from the same link as the build and have gapps 5.0 when you flash
flash in this order: rom, gapps, superSU
important things that do work :
4g YES
bluetooth with android wear YES
gps YES
camera for android YES( stock camera NO google camera NO)
wifi YES
flash light YES
time needs to be adjusted(settings > date & time > check atumatic date & time (use network-provided time) uncheck automatic time zone, select time zone to finish time set)
sound YES
dsp YES
security YES unlocks only with power button (home button will not unlock your phone takes some getting use to)
keyboard YES
what was used to set up my phone: philz recovery, rescripted 12-20141125-UNOFFICIAL-d2att, superSU beta app,gapps 5.0, latest modem from xda for d2tmo t999L
leonid002 said:
after doing a lot of research i have sucsesfully installed lollipop onto my s3 and got the camera to work with the camera for android app from the play store. the data also works the build i installed is the 12-20141125-unofficial-d2att after changing the script file to include d2tmo instead of the d2att. works great no real bugs except the time stamp on hangout mesages which is fixed by setting the time on the phone to network but turning of the reginal time set. thought this would be nice to share.
ps: stock camera and google camera still do not work but everything else does so this can be used as a daily driver links below to camera and build:
camera: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
build: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Click to expand...
Click to collapse
Is it possible that you could upload d2att rom with changed script?
leonid002 said:
after doing a lot of research i have sucsesfully installed lollipop onto my s3 and got the camera to work with the camera for android app from the play store. the data also works the build i installed is the 12-20141125-unofficial-d2att after changing the script file to include d2tmo instead of the d2att. works great no real bugs except the time stamp on hangout mesages which is fixed by setting the time on the phone to network but turning of the reginal time set. thought this would be nice to share.
ps: stock camera and google camera still do not work but everything else does so this can be used as a daily driver links below to camera and build:
camera: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
build: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Added screen shots of apps used speed test and the edit that needs to be made to script file to make installable
Click to expand...
Click to collapse
Wiwee said:
Is it possible that you could upload d2att rom with changed script?
Click to expand...
Click to collapse
it looks like the file is too big to upload, here are the steps to edit the file manually, if you follow these you wont screw up
1. open the file in total comander
2. META-INF> COM>GOOGLE>ANDROID
3. open and edit the updater-script by long pressing the file choosing unpack+edit
4. change d2att to d2tmo in the first line P.s. theres two words change both
5. go back and the editing is done now just wipe everything and flash just like any other rom the boot up takes about 8 to 9mins so dont worry about it being stuck in a loop, it isnt
do not forget to download superSU from the same link as the build and have gapps 5.0 when you flash
flash in this order: rom, gapps, superSU
Wiwee said:
Is it possible that you could upload d2att rom with changed script?
Click to expand...
Click to collapse
files not uploading still sorry
leonid002 said:
files not uploading still sorry
Click to expand...
Click to collapse
I have determined I am an idiot. I downloaded the rom and tried to change the stuff you have listed and no love. If you have a chance to get it uploaded ( mega.co.nz with a public link maybe.....) please share would love to give it a shot.
PHP:
alarmdude9 said:
I have determined I am an idiot. I downloaded the rom and tried to change the stuff you have listed and no love. If you have a chance to get it uploaded ( mega.co.nz with a public link maybe.....) please share would love to give it a shot.
Click to expand...
Click to collapse
I'll get right on it thanks for the response,did it not let you flash it and say it's not compatible?
leonid002 said:
PHP:
I'll get right on it thanks for the response
Click to expand...
Click to collapse
No thank you for trying to help idiots like me. that is correct says not compatable
alarmdude9 said:
No thank you for trying to help idiots like me.
Click to expand...
Click to collapse
I got it to work at 3 in the morning so if I forgot something I'm sorry in advanced it's halfway uploaded right now with the changes in the script. Hope this helps. I also flashed with Philz recovery if that makes any difference
leonid002 said:
I got it to work at 3 in the morning so if I forgot something I'm sorry in advanced it's halfway uploaded right now with the changes in the script. Hope this helps. I also flashed with Philz recovery if that makes any difference
Click to expand...
Click to collapse
No apologies needed at all. Don't know if one version of the recovery matters or not. I know it did way back in the days of the CLIQ but I'm hoping not this far along
leonid002 said:
after doing a lot of research i have sucsesfully installed lollipop onto my s3 and got the camera to work with the camera for android app from the play store. the data also works the build i installed is the 12-20141125-unofficial-d2att after changing the script file to include d2tmo instead of the d2att. works great no real bugs except the time stamp on hangout mesages which is fixed by setting the time on the phone to network but turning of the reginal time set. thought this would be nice to share.
ps: stock camera and google camera still do not work but everything else does so this can be used as a daily driver links below to camera and build:
camera: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
build: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Added screen shots of apps used speed test and the edit that needs to be made to script file to make installable
lollipop for d2tmo install instructions
WHAT YOU NEED
the build location:
12-20141125-unofficial-d2att link: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
in the same link is superSU
also will need gapps 5.0 lollipop
"camera for android" ( stock camera and google camera DOES NOT work)
link: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
total commander
instructions to exit the updater-script file to make the build installable on your d2tmo
1. open the file in total commander
2. META-INF> COM>GOOGLE>ANDROID
3. open and edit the updater-script by long pressing the file choosing unpack+edit
4. change d2att to d2tmo in the first line P.s. theres two words change both
5. go back and the editing is done now just wipe everything and flash just like any other rom the boot up takes about 8 to 9mins so dont worry about it being stuck in a loop, it isn't
do not forget to download superSU from the same link as the build and have gapps 5.0 when you flash
flash in this order: rom, gapps, superSU
Click to expand...
Click to collapse
alarmdude9 said:
No apologies needed at all. Don't know if one version of the recovery matters or not. I know it did way back in the days of the CLIQ but I'm hoping not this far along
Click to expand...
Click to collapse
https://mega.co.nz/#!8wdyVICK!ORYZsTOTdnXvgpEYVA6mJr9JbQJ0MCz_wFh8sA_xPNk
Try this I checked the file to make sure it was edited
leonid002 said:
https://mega.co.nz/#!8wdyVICK!ORYZsTOTdnXvgpEYVA6mJr9JbQJ0MCz_wFh8sA_xPNk
Try this I checked the file to make sure it was edited
Click to expand...
Click to collapse
awesome bringing it down now.
alarmdude9 said:
awesome bringing it down now.
Click to expand...
Click to collapse
so when you flash there should be a small error but it will continue flashing. let me know it goes
leonid002 said:
so when you flash there should be a small error but it will continue flashing. let me know it goes
Click to expand...
Click to collapse
Will do. Besides the camera everything else is working? Can't test it a lot tonight, just got called into work, but want to get it set up and a nandroid then play with it after work tomorrow.
alarmdude9 said:
Will do. Besides the camera everything else is working? Can't test it a lot tonight, just got called into work, but want to get it set up and a nandroid then play with it after work tomorrow.
Click to expand...
Click to collapse
when I first flashed the time for some reason was off but its pretty easy to fix, as for the camera install camera for android in the play store so you have some kind of working camera if that matters to you . everything else works perfectly a lot faster than the carbon ROM I had
Hi guys, I wanted to start a discussion on the benefits of rooting and any available tweaks/mods/apps people are using. Thanks
daveyp187 said:
Hi guys, I wanted to start a discussion on the benefits of rooting and any available tweaks/mods/apps people are using. Thanks
Click to expand...
Click to collapse
For me at least until my SW3 updates to Android 6 I see very little point in rooting my SW3... And as yet other than twrp and Kernel I don't feel there are enough mods etc or even Custom roms(if any) to even bother with rooting... On a phone there are huge benifits but a watch that relies on your phone for most everything I see no advantages yet...
I know what you mean, side loading apps is cool, and being able to change the DPI. Firefox and Google keyboard works well, cm cleaner works perfectly and helps uninstalling apps and es file manager is good for installing apps
Be honest. Do you really need a reason beside "it can be done"?
No lol, but I want tweaks
[NUMINIT] said:
Be honest. Do you really need a reason beside "it can be done"?
Click to expand...
Click to collapse
LOL I guess not. Andhopefull we will get Marshmallow soon and then will have a proper play!
Hopefully, it's been seen in the wild. Just need them to pull their fingers out.
So, while I agree that waiting to root until after 1.4 might be a good idea, here is what I did with root...
Direct wifi access with apps (mostly es File Explorer for on watch app install and uninstall)
Kernel experimenting and tweaking
Uninstall wear apps but keep host apps on phone
All done without a computer (after initial install and setup)
Run most terminal commands with a single tap (like changing dpi)
Sent from my SM-T810 using Tapatalk
currently i am running ubuntu in a chrooted environment on my watch (rooted device needed)
Link?
if this question was dedicated to me, my answer is:
I read posts about android and chrootet linux distros and used a similar technique to do this with my smartwatch 3. As soon as I am allowed to post a DEV-THREAD I will probably make a quick tutorial about it.
Looking forward to it. Not something I've looked at
[Custom Rom] Huawei Mate 8 - NXT-L29C432B582 - Custom System Update - ("V. 6")
I have merged my threads. Please look here:
https://forum.xda-developers.com/ma...mate-8-nxt-t3677961/post73901232#post73901232
ChinHon said:
[Custom Rom] Huawei Mate 8 - NXT-L29C432B582
- Custom System Update - ("V.6")
- EMUI 5.01 - Android 7 -
On TWRP backup basis.
This update replaces the [K-Rom-M8-V5].
Developed and tested on this device:
Huawei Mate 8 (NEXT)
Model number: Huawei NXT-L29
Build number: NXT-L29C432B582
- OTA updated.
- Without branding, with root and root access.
- TWRP recovery
Mods:
- Call Recorder
- KangVip Advanced settings
- Autostart administration in the phone manager (PM+)
- Viper 4 Android FX
- Obtaining OTA authorization
I couldn't test if this runs on Firmwares other regions.
I think the v6 is going on all regions on B582/592.
Quick guide for experienced users:
Please make a backup of your data with Huawei Backup and TWRP.
The Rom will be installed as if you wanted to restore a TWRP backup.
All your apps remain intact.
Conditions required:
- Firmware B582,
- TWRP recovery, (from download, or available from v5 )
- root is not necessary,
- OEM and FRP unlocked,
- USB Debugging on.
All required files are in the download folder.
You are familiar with the matter? Then let's go!
If available, uninstall these apps: SuperSu and Magisk.
A unroot is not necessary. Please do not download the downloads as "ZIP".
Installation:
1. Replace existing boot partition:
"2017-12-M8.B582.stock.kernel.boot"
copy in the TWRP backup directory to the ExtSd and restore.
2. Install update:
"2017-12-M8_B582_AdvS_Xposed_SystemUpdate"
also copy to the TWRP backup directory and restore."
3. Rooting:
- In TWRP mount Internal storage/ system,
- go to: Install, system/ k-rom/ set and install the SuperSU. zip.
- Reboot.
- After starting, take the BusyBox App from the download.
Then please use it to install its binaries.
- Install the PM+ app and bring the autostart administration to the phonemanager.
Iggnore the incompatibility warning.
Do not reboot between steps 1 to 3. Do not wipes before and after.
That's all. The installation is complete.
If Viper or Xposed have not been installed with it, this can be found in the
Advanced settings can be made up for.
Xposed is already active. In case the framework gets disabled,
in the Advanced settings. There's no way use other Xposed versions.
This also applies to SuperSU. They are not compatible with this system.
Both are optimized for this system.
Of course, you can also use Magisk to root later with the instructions
in the v5 thread. (loss of ota authorization)
Xposed does not run under magisk rooting together with the Advanced settings.
It must be used for a successful SafetyNet test, must be completely removed before rooting.
In the Kangvip Advanced settings do not use the Addblocker and "hide Activate NavBar".
Both works only on China Roms.
Hiding the NavBar can be done comfortably with the App "Tiles" from the playstore. (See v5)
In the K-Advanced Settings /tune cpu, some of the following are available.
Modifications of the computer performance possible. Those who need more power can do so.
Testing out the "Power save" options is useless. Did a lot of it.
The Huawei's own energy saving settings cannot be topped.
Good luck!
Thank you very much:
[KangVIP] (Advanced settings),
@Tecalote (SuperSU)
and Chainfire, Stephen (Stericson) + Jmz Software, Team Win RecoveryProject,
JRummy and Huawei Technologies Co., Ltd.
Hint:
Despite careful elaboration, I cannot guarantee that the execution of this manual will not cause any damage to the device or operating system and therefore I do not assume any liability for any damage or malfunction of the hardware and software! If you are still unsure, follow these steps: Follow the instructions only if you or your device is subject to any conditions (model number, Android version, etc.). Read the instructions carefully and completely, look up unknown terms. Check downloaded files for viruses. Make a backup of important settings and data. Do not follow the instructions if you do not know what you are doing.
These warnings must be logical. Please process my comments correctly.
Click to expand...
Click to collapse
you da man
Sent from my HUAWEI NXT-AL10 using Tapatalk
jbmc83 said:
you da man
Sent from my HUAWEI NXT-AL10 using Tapatalk
Click to expand...
Click to collapse
This rom is going really well. Especially Xposed. I haven't been able to get it that stable yet. I'm really glad I finally made it.
@jbmc83
I now have the link of the v2 you are looking for. Still interested?
ChinHon said:
@jbmc83
I now have the link of the v2 you are looking for. Still interested?
Click to expand...
Click to collapse
me
nikolas60 said:
me
Click to expand...
Click to collapse
Do you know what it's about? The link is for developers only.
ChinHon said:
@jbmc83
I now have the link of the v2 you are looking for. Still interested?
Click to expand...
Click to collapse
sure thing, lets have it that would be the HRT v2 right? would i be qualified for the link tho? im not a dev either
Sent from my HUAWEI NXT-AL10 using Tapatalk
Everyone who works on a rom is a developer!
Here the link friends.
https://pan.baidu.com/s/1bpJGYyb
It's not HRT. Should be better. Look closely at the zip, could have subdirectories.
ChinHon said:
Everyone who works on a rom is a developer!
Here the link friends.
https://pan.baidu.com/s/1bpJGYyb
It's not HRT. Should be better. Look closely at the zip, could have subdirectories.
Click to expand...
Click to collapse
ah yes, i remember that one! actually have it already, you had provided a link before still, thanks for your trouble!
apparently, there is a new chinese B593 out, although the full stock versions provided on firmware finder are not approved for installation, unfortunately... so they cant be flashed properly. still, nice to see development continuing
I'll continue, of course, because it's questionable whether we get oreo.
Has someone successfully installed my update on another region?
Please let us know.
ChinHon said:
I'll continue, of course, because it's questionable whether we get oreo.
Has someone successfully installed my update on another region?
Please let us know.
Click to expand...
Click to collapse
could get interesting next spring, maybe well have another shot at oreo then... still wondering what the heck @c|nder was up to with this thread here
https://forum.xda-developers.com/mate-8/orig-development/oreo-rom-1-0-mate-8-south-america-t3702767
jbmc83 said:
could get interesting next spring, maybe well have another shot at oreo then... still wondering what the heck @c|nder was up to with this thread here
https://forum.xda-developers.com/mate-8/orig-development/oreo-rom-1-0-mate-8-south-america-t3702767
Click to expand...
Click to collapse
How to make new roms when you can't get to the baidu downloads anymore?
ChinHon said:
How to make new roms when you can't get to the baidu downloads anymore?
Click to expand...
Click to collapse
question is rather: how to make new roms if there arent any new firmwares being developed officially?
Sent from my HUAWEI NXT-AL10 using Tapatalk
Yeah, that's an aspect too. Making a new rom after every update is somehow unproductive. Just because of the google patch? I only made my update because of the stable xposed. I only make new ones in the future if something fundamentally changes.
Any news about oreo guys?[emoji848]
.....
Wow this is great work, how about the data? Is it decrypted with this method?
(sorry for the noob question)
aaron13 said:
Wow this is great work, how about the data? Is it decrypted with this method?
(sorry for the noob question)
Click to expand...
Click to collapse
Thank you.
My rom is not encrypted. It also replaces only the boot and system partitions.
Since data remains unaffected, nothing changes. It remains as it was before installation.
ChinHon said:
Thank you.
My rom is not encrypted. It also replaces only the boot and system partitions.
Since data remains unaffected, nothing changes. It remains as it was before installation.
Click to expand...
Click to collapse
But it is rooted so titanium can be used?
aaron13 said:
But it is rooted so titanium can be used?
Click to expand...
Click to collapse
Yes!
Go with all my roms.
Custom ROM for Alcatel Idol 4S (6071W/6077X)
The build of the OS:
10.0.15254.603 (FCU)
Firmware version:
1052.16.09031.50700 (6071W)
1052.16.10011.51400 (6077X)
All 68 Languages Interface and 102 Languages Keyboard Input.
Phone is unlocked.
Root enabled.
Added BDS Menu (PWR&VOL+).
Added Windows Phone Boot Menu (PWR).
Added ADC-files from IDOL4S PRO (6077X).
Added packages acer.Service.AcerSystemService, Nokia.Executable_OEMServiceHost.Generic, Nokia.Service_NdtkSvc.Generic.
Added packages MS_TSHELL.MSN.MainOS (bcdedit, cmd, reg and other).
Added packages Microsoft.MS_WEH_LEDALERT.MainOS.
Added packages Microsoft.Graphics.DXTools, Microsoft.Phone.Test.BaseOS.TraceLog, Microsoft.Tools.AppVerifExt, Microsoft.Tools.DevToolSupport, Microsoft.Tools.HITMemTools, Microsoft.Tools.PerfMonExt.
Added Enterprise and other ppkg.
Added App and Dependencies (Framework).
Some other tweaks and other minor changes.
Instruction:
Install Qualcomm drivers on your PC.
Install QFIL (QPST) on your PC.
Install custom ROM on your device in the mode 9008/EDL using QFIL (QPST).
Select Port - Qualcomm HS-USB QDLoader 9008,
Select Build Type - Flat Build,
Select Programmer - Idol4S_PRO_WIN_NPRG7627.bin,
Select Flat Build - Folder with files from archive Custom ROM,
Load XML - rawprogram0.xml,
Press Download,
Download Succeed,
Finish Download.
Press the power button and turn on the device.
Wait for the update process.
Download:
IDOL4S_6071W_F1052.16.09031.50700_10.0.15254.603_Custom
IDOL4S_6077X_F1052.16.10011.51400_10.0.15254.603_Custom
Custom W10M ROM:
Microsoft Lumia 950 XL (Dual SIM)
Alcatel Idol 4S (6071W/6077X)
Xiaomi MI4 LTE
Acer Liquid M330
Archos 50 Cesium
Archos 40 Cesium /
BLU WinJr / Karbonn Titanium Wind W4 /
K-Touch E8 Win / HighScreen WinWin
HighScreen WinJoy
BLU Win HD LTE
Thanks for sharing this. I currently use T-Mobile in the US. Have you tested the ROM with the T-Mobile carrier and do the added ADC files affect anything while using T-Mobile (VoLTE, HD Voice, etc)?
I have partially been following another forum that was working to boot loader unlock the Idol 4s for Windows 10 mobile. I don't think this ROM was a result of that, but do you know of any other news?
nate0 said:
I currently use T-Mobile in the US. Have you tested the ROM with the T-Mobile carrier and do the added ADC files affect anything while using T-Mobile (VoLTE, HD Voice, etc)?
Click to expand...
Click to collapse
No, I have not tested it. I have IDOL4S Open from Microsoft.
You can mention that there is a provxml file to install Yandex.Search.appxbundle in the IDOL4S_6071W_F1052.16.09031.50700_Open_RTM_10.0.15 254.490_Custom ROM. It is not in the T-Mobile ROM though.
This is a useful scenario too for some of us who might want to Edit the registry on the IDOL 4s outside of the current changes in these ROMs. Mount the bin file save the edits and flash the changes. Do you know if making changes such as reg edits would require an altered or updated rawprogram0.xml? Thanks.
---------- Post added at 10:56 PM ---------- Previous post was at 10:54 PM ----------
kovalDN said:
No, I have not tested it. I have IDOL4S Open from Microsoft.
Click to expand...
Click to collapse
Ok. I can test it later and if issues occur I could possibly change out those ADC files for the T-Mobile files.
nate0 said:
You can mention that there is a provxml file to install Yandex.Search.appxbundle in the IDOL4S_6071W_F1052.16.09031.50700_Open_RTM_10.0.15 254.490_Custom ROM. It is not in the T-Mobile ROM though.
Click to expand...
Click to collapse
The following My Account T-Mobile USA, Hulu Plus, Uber, Captain Fellcraft VR, and Zombie VR apps have been removed in ROM. Left other VR-applications, but with the possibility of removal. Added app Yandex.Search.
nate0 said:
This is a useful scenario too for some of us who might want to Edit the registry on the IDOL 4s outside of the current changes in these ROMs. Mount the bin file save the edits and flash the changes. Do you know if making changes such as reg edits would require an altered or updated rawprogram0.xml? Thanks.
Click to expand...
Click to collapse
I don't know what you're trying to say. The layout of the sections does not change, the size of the sections does not change. Why should change rawprogram0.xml. Data in rawprogram0.xml is taken from GPT, these are rawprogram0.xml is best for this ROM.
nate0 said:
Ok. I can test it later and if issues occur I could possibly change out those ADC files for the T-Mobile files.
Click to expand...
Click to collapse
Replacement ADC only in ROM F1052.16.09031.50700_Open_RTM. ROM F1050.14.08011.53400_TMOUS_Retail is initial, this replacement was not made.
kovalDN said:
The following My Account T-Mobile USA, Hulu Plus, Uber, Captain Fellcraft VR, and Zombie VR apps have been removed in ROM. Left other VR-applications, but with the possibility of removal. Added app Yandex.Search.
Click to expand...
Click to collapse
Ok Thanks.
kovalDN said:
I don't know what you're trying to say. The layout of the sections does not change, the size of the sections does not change. Why should change rawprogram0.xml. Data in rawprogram0.xml is taken from GPT, these are rawprogram0.xml is best for this ROM.
Click to expand...
Click to collapse
Sorry my fault. It has been a while since working with qc loaders and program xml files. For some reason I was thinking rawprogram0.xml contained the space used by the partitions not the whole partition size.
kovalDN said:
Replacement ADC only in ROM F1052.16.09031.50700_Open_RTM. ROM F1050.14.08011.53400_TMOUS_Retail is initial, this replacement was not made.
Click to expand...
Click to collapse
Thanks.
@kovalDN
I am having an issue on the custom ROMs being able to sign in with my Microsoft account while setting up the phone. It either locks up/freezes the set up process, or fails. I think it fails while checking account info and it never pulls the backups to restore. Ultimately the account will be signed in but can only move forward after skipping the step entirely to be able to set up the rest of the phone.
Is this just me or have you noticed an issue?
nate0 said:
@kovalDN
I am having an issue on the custom ROMs being able to sign in with my Microsoft account while setting up the phone. It either locks up/freezes the set up process, or fails. I think it fails while checking account info and it never pulls the backups to restore. Ultimately the account will be signed in but can only move forward after skipping the step entirely to be able to set up the rest of the phone.
Is this just me or have you noticed an issue?
Click to expand...
Click to collapse
It's not a bug, but a feature Only in custom ROM F1050.14.08011.53400_TMOUS_Retail. Associated with reset protection packets. They are in this firmware test. So it will be with the official ROM F1050.14.08011.53400_TMOUS_Retail, if you update it above 15063.2.
kovalDN said:
It's not a bug, but a feature Only in custom ROM F1050.14.08011.53400_TMOUS_Retail. Associated with reset protection packets. They are in this firmware test. So it will be with the official ROM F1050.14.08011.53400_TMOUS_Retail, if you update it above 15063.2.
Click to expand...
Click to collapse
What is being tested exactly?
I need to be able to restore a backup on the IDOL 4s. If I can't then certain apps don't function at all.
nate0 said:
What is being tested exactly?
Click to expand...
Click to collapse
Ask the Alcatel.
nate0 said:
I need to be able to restore a backup on the IDOL 4s. If I can't then certain apps don't function at all.
Click to expand...
Click to collapse
kovalDN said:
So it will be with the official ROM F1050.14.08011.53400_TMOUS_Retail, if you update it above 15063.2.
Click to expand...
Click to collapse
On the versions above 15063.2 reset protection is activated automatically by logging into your account, with no choice of disabling it. And in this firmware of packets of protection against reset in MainOS is not present.
kovalDN said:
Ask the Alcatel.
On the versions above 15063.2 reset protection is activated automatically by logging into your account, with no choice of disabling it. And in this firmware of packets of protection against reset in MainOS is not present.
Click to expand...
Click to collapse
Got it understood.
I am curious why are you using this older TMO firmware?
nate0 said:
I am curious why are you using this older TMO firmware?
Click to expand...
Click to collapse
I'm not using it I use F1052.16.09031.50700_Open_RTM.
kovalDN said:
ROM F1050.14.08011.53400_TMOUS_Retail is initial
Click to expand...
Click to collapse
kovalDN said:
I'm not using it I use F1052.16.09031.50700_Open_RTM.
Click to expand...
Click to collapse
I'm sorry I did not word that so you understood. I meant why is your custom ROM set as an older firmware? The fw revision of the T-Mobile firmware is older than the official production one on most phones. I am assuming you used this version to customize a ROM for some reason.
nate0 said:
I meant why is your custom ROM set as an older firmware? The fw revision of the T-Mobile firmware is older than the official production one on most phones. I am assuming you used this version to customize a ROM for some reason.
Click to expand...
Click to collapse
In the last official ROMs is there a BDS Menu and Mass Storage mode? The question is rhetorical
kovalDN said:
In the last official ROMs is there a BDS Menu and Mass Storage mode? The question is rhetorical
Click to expand...
Click to collapse
Well yes of course! One would have their work cut out for them if they did not have to manually build those items into a ROM on their own. Was hoping maybe you had plans to incorporate those items into an updated or different firmware if possible. One that would allow restoring of a backup, and had reset protections bugs fixed . No worries about that though, was only wishful thinking.
nate0 said:
Well yes of course! One would have their work cut out for them if they did not have to manually build those items into a ROM on their own. Was hoping maybe you had plans to incorporate those items into an updated or different firmware if possible. One that would allow restoring of a backup, and had reset protections bugs fixed . No worries about that though, was only wishful thinking.
Click to expand...
Click to collapse
This is already included in the custom ROM IDOL4S_6071W_F1052.16.09031.50700_Open_RTM_10.0.15254.490.
kovalDN said:
This is already included in the custom ROM IDOL4S_6071W_F1052.16.09031.50700_Open_RTM_10.0.15254.490.
Click to expand...
Click to collapse
Ok I will try it out again. I thought I tried to restore a backup on Both ROMs and failed to with the same bug.
For some reason on the Open market Custom ROM the ndtk packages are not active after flashed or not working. Maybe it is just me but I can't edit the registry, enable Interop services or full file system access from Interop Tools until I send the packages again even though they are there. Plus I have to make other changes to it as well for T-mobile nvi settings.
nate0 said:
I thought I tried to restore a backup on Both ROMs and failed to with the same bug.
Click to expand...
Click to collapse
The Open market Custom ROM should not have this error with backup recovery.
nate0 said:
For some reason on the Open market Custom ROM the ndtk packages are not active after flashed or not working. Maybe it is just me but I can't edit the registry, enable Interop services or full file system access from Interop Tools until I send the packages again even though they are there.
Click to expand...
Click to collapse
Again download a Open market Custom ROM, 16.07.2018 it was updated, this error was eliminated.
kovalDN said:
Again download a Open market Custom ROM, 16.07.2018 it was updated, this error was eliminated.
Click to expand...
Click to collapse
Ah ok that explains it. I had no idea you corrected this...
New Issues on Idol 4S using custom ROM
Installed TMOUS version of this custom ROM (Thank you OP for your efforts!) on August 8 and was delighted to uninstall the remaining VR apps. As nate0 posted earlier, I couldn't sign in during the initial setup, and was not able to restore earlier backups as expected. Phone is TMOUS retail locked (so far - longtime TMO customer awaiting billing cycles on this phone for unlock code).
Since then M$ has updated the OS build to 10.0.15254.527. Things keep breaking faster than I can keep track of - and not sure which are a function of 1) the custom ROM, 2) the Idol 4S, or 3) Microsoft desire to chase us away. New issues include:
Amazon - crashes at launch
Microsoft Wallet (v. 2.3.17311.0) - allowed me to scan 1 loyalty card successfully, then refuses to recognize/scan codes,
"CameraAccessDenied" error message
Flashlight (v. 4.0.0.0 Sakariya) - no longer can turn led on/off (Flashlight XT still works fine)
People (v. 10.2.2001.1000) - live tile stopped working after about a week, can't get it to work at all anymore
Translator (v. 4.8.7.0) - live tile works for about 1 day, then remove, disable/enable to restore function for another day
Microsoft Store - (v. 11807.1001.13.0) - live tile works for about 1 day, then same as Translator
My Library this morning shows about 1/3 of my apps that were listed last week ???