Database Users

[n80xx] CyanogenMod 10.2 Dual Boot

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For anyone interested, below are the steps for getting your device dual-booting with CyanogenMod 10.2.
Why?
I don't want to erase native firmware and want to give a try to CyanogenMod
I want to have both native and CM, because I like native Samsung S-Pen apps, but want to have more fresh Android too
I like experimenting - it's cool!
The Idea
Our Android device has 2 boot partitions - for normal boot, and to boot into recovery. If I want to boot CyanogenMod, I need to place its boot image instead one of those boot partitions. E.g. if I want to have both native firmware and cyanogen - then obviously I need to replace recovery partition. However I can do the backup of recovery and restore it later if needed.
But, I also need to place cyanogen system and data partitions somewhere. Putting it on the external sdcard makes CM working really slow, repartitioning internal memory might be good idea, but it is not so easy and is not necessary for experimenting. Thus I've created 2 image files and put it to native data partition (mmcblk0p12) to media folder, e.g. into internal sdcard, then changed cyanogen boot image to mount those image files on boot as system and data partitions.
Prerequisites:
Rooted Samsung Galaxy Note 10.1 2012 Edition
2GB of free disk space at internal sdcard
Recovery partition backup, because we are going to replace it with CyanogenMod boot image
Clear understanding of what you are doing, because you potentially can break your device
Downloads:
CM 10.2 boot image
CM 10.2 data partition image
CM 10.2 system partition image
Steps
This manual suggests that you are going to do the recovery backup to external sdcard and has native firmware which means that recovery partition is mmcblk0p6, data partition is mmcblk0p12 and internal sdcard is /mnt/sdcard folder (otherwise you need to change the commands appropriately and might need to fix cyanogen boot image too).
Download 3 files by the links above and upload to internal sdcard of your device. Connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to external sdcard to create recovery backup
cd /mnt/extSdCard
dd if=/dev/block/mmcblk0p6 of=./recovery.img
# go to internal sdcard folder
cd /mnt/sdcard
# unpack partition images - each is 1Gb of disk space
gunzip ./system.img.gz
gunzip ./data.img.gz
# write CM boot image to recovery partition
dd if=./cyanogen.img of=/dev/block/mmcblk0p6
# finish
exit
exit
Now you can reboot your device into recovery mode and see CyanogenMod booting.
Restoring native recovery:
If you got tired from CyanogenMod and/or would like to take back your recovery, please use the backup you've done before. Lets say it is placed on your external sdcard, then connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to the folder with recovery backup
cd /mnt/extSdCard
# write recovery image over recovery partition
dd if=./recovery.img of=/dev/block/mmcblk0p6
Please let me know If I missed anything in my steps.
P.S. What I've changed in Cyanogen boot.img to make it using img files instead of partitions in form of patch: View attachment cyanogen_boot_img.patch. It is also necessary to create /host folder in initrd folder tree.

wow!!
it's really hard to be done xD
i thought it will be as easy as it was on my old Galaxy S2
all what i needed to do is to restart the phone and press home to boot to second Rom
i hope it's going to be easier soon
and thank you for you efforts toward our device Development

MoNsTeRmUk said:
wow!!
it's really hard to be done xD
Click to expand...
Click to collapse
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps

X-Stranger said:
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps
Click to expand...
Click to collapse
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support

MoNsTeRmUk said:
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support
Click to expand...
Click to collapse
Thanks for kind words Actually you don't need to have the computer to change ROM, you can type commands from terminal emulator directly from Android. I'm also thinking about creating small Android app which can be installed to each ROM and will be able to switch boot partition within one click.

Thanks for this superb work. Can't download last file ?
Please if can make someone flashable zip it would be great I am a noob but I want try this thanks again
Sent from my GT-N8000 using Tapatalk HD

other roms
Can I do this this with another rom

maro_X said:
Can I do this this with another rom
Click to expand...
Click to collapse
It is possible, but your another rom must be specially modified for this.
What rom are you talking about exactly?

Multi-boot solution
I've tired of writing images to boot partition every time I want to switch between native firmware and Cyanogen, so decided to compose a little program that I was talking before. So let me introduce you N8xx Boot Manager!
The idea:
You put your boot images files to some folder on your sdcard, lets say to /mnt/extSdCard/images/boot
And recovery boot images to /mnt/extSdCard/images/recovery
Now you run Boot Manager and select what you want to boot as normal boot or as recovery
As soon as you selected it, the application asks you if you would like to write this image to the appropriate partition (boot or recovery)
After successful writing it will ask you for booting from that partition, e.g. propose to reboot into your another rom or recovery
For sure all the settings like path where to keep images and boot/recovery partition names can be fixed appropriately to your device at the Settings tab
For sure the application requires root permissions, e.g. your device must be rooted. You can also check this from Settings tab
The application file: View attachment bootmanager-1.0.apk - feel free to install it to your device and use posting me bug reports
P.S. The only thing I've forgotten - the button to create native boot image file backup You still need to do it manually, sorry Hopefully in next release, if there be people interested in N8xx Boot Manager
P.P.S. Generally this program can be used for any device - just put correct images and correct boot partition names
P.P.P.S. Why N8xx and not N8xxx or N80xx? Because I've missed one symbol when typed application name in Android Studio and was too lazy to change that later :laugh:

N80xx Boot Manager
Updated version of N80xx Boot Manager: View attachment bootmanager-1.1.apk
Changelog:
Fixed application name
Fixed images path detection when no settings were changes
Added "Backup boot partiton" and "Backup recovery partition" buttons
Thus, now to install CM 10.2 as dual boot you don't need to go to ADB or terminal - just upload 3 img files to your device proper locations, installl boot manager apk, create stock boot/recovery partitions backup, then select what you want to boot and boot to that rom!
P.S. Going to update first post of this thread with steps based on Boot Manager, just would be nice if someone confirm that it works.

swamimahesh said:
Can't download last file
Click to expand...
Click to collapse
Re-uploaded.

I love u man
Finally alittle love for our device :crying:

Do I have to reinstall apps when booting to cm?
edit: I dont really understand the first step when you extract data and system.img. Can you explain more clearly the procedure?
edit2: did anyone do this dualboot successfully?

data.img.gz
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:

I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk

netj said:
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:
Click to expand...
Click to collapse
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment data.img.gz and let me know if it works for you.

muop_92 said:
I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk
Click to expand...
Click to collapse
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.

X-Stranger said:
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.
Click to expand...
Click to collapse
Where is /mnt ? I saw in my device only /storage/extSdCard
Sent from my GT-I8160 using Tapatalk 2

muop_92 said:
Where is /mnt ? I saw in my device only /storage/extSdCard
Click to expand...
Click to collapse
It's the same. External sdcard is available on both these paths as far as I know. You can change it otherwise in application settings tab.

Ok !
X-Stranger said:
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment 2519204 and let me know if it works for you.
Click to expand...
Click to collapse
Hi,
It's Ok !
Thanks !
I have just modify the paths :
dd if=/dev/mmcblk0p6 of=./recovery.img --> dd if=/dev/block/mmcblk0p6 of=./recovery.img
dd if=./cyanogen.img of=/dev/mmcblk0p6 --> dd if=./cyanogen.img of=/dev/block/mmcblk0p6
:good:

[3/31] Fix for KitKat Update Failing - Without ROOTING

WARNING: IF YOU ARE NOT GOING TO START FROM STEP 1 AND FOLLOW EACH STEP EXACTLY HOW I HAVE WROTE IT THEN YOU WILL FAIL. THIS METHOD WORKS IF YOU CAN FOLLOW THE DIRECTIONS.
IF YOU DID NOT RESTORE YOUR PHONE AND FOLLOW EACH STEP EXACTLY HOW I LISTED BELOW THEN DO NOT SAY THIS DOESN'T WORK FOR YOU.
Step 1. Follow @evilpotatoman 's guide below to restore your phone to MJ5 FIRST
Guide:
1) Download and install Heimdall from here for windows. You'll need this and this to avoid missing .dll file errors
2) Download the following files:
MI9_fix.img.ext4
sec_csc.zip
2400258.zip
​Put sec_csc.zip and 2400258.zip on your external SD card
3) Download and install the MJ5 partitions. Use Odin to flash these files (match the file names with the different upload slots)AP_N900AUCUBMJ5.zip​BL_N900AUCUBMJ5.zip​CP_N900AUCUBMJ5.zip​HLTE_USA_ATT_32G.pit​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4) Now is the time to use Heimdall.
Reboot into Download Mode once Odin finishes.
Install the vcredist packages downloaded from step 1.
unzip the heimdall .zip file to c:/
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"
from the dropdown, select MSM8960
click the "install driver" button.
you should see a success message
5) Navigate on your computer to c:/Heimdall Suite/ and open heimdall-frontend.exe.
IMPORTANT -- Go to the Utilities tab and click the "Detect" button
Go to the Flash tab on Heimdall, click Browse and select the HLTE_USA_ATT_32G.pit file downloaded from step 3
Click the 'add' button, then next to 'partition name' select system from the dropdown.
click the Browse button underneath the dropdown, and select the MI9_fix.img.ext4 image you downloaded from step 2.
6) Click Start. ***I usually check the 'No Reboot' box to prepare for booting into recovery
7) Heimdall and your Note will report a bad flash at around 95% -- but don't worry -- your system.img got uploaded Reboot directly into recovery mode.
8) Once in recovery, select "Choose update from external" in the recovery, and select the sec_csc.zip you downloaded earlier (did you remember to put that file on your external SD card?). This will install the CSC files and run the preload checkin so you don't FC all over the place
9) IMPORTANT--After flashing the sec_csc, the Note will reboot.
Try to catch it in time to reboot BACK into recovery
Once in recovery, select "Choose update from external" in the recovery, and select the 2400258.zip you downloaded earlier.
END OF MJ5 RESTORE GUIDE - CONTINUE BELOW
Step 2. YOU ARE NOW ON MJ5 BE SURE TO DOWNLOAD AND INSTALL THE NB4 OTA UPDATE BEFORE CONTINUING!!!
Step 3. When you're finished the restore guide to MJ5 and updated to NB4 then delete any other files used from the restore guide so you don't mix them up and download the following 2 files:
1- Miata KitKat Fix v1
2- KitKat Ota Zip​Step 4. Extract the Miata_KK_Fix_1.0.zip to the root of your BOTH your phone storage and your sd card. (make sure they are not in any folders!!!)
Step 5. Once both files in the Miata_KK_Fix_1.0.zip are extracted and copied to both your phone and the sd card... then reboot the phone.
VERY IMPORTANT TO REBOOT NOW
Step 6. Pick one of the follow options...
(Option A) - Wipes phone - I recommend this method
1. Rename 2400258.zip to update.zip and copy to EXTERNAL STORAGE (aka sd card)
UNPLUG USB CABLE BEFORE CONTINUING
2. Reboot into RECOVERY MODE (volume up + home) and select "Apply Update from external storage" and select your update.zip
3. It should start the update process and finish successfully! Enjoy!​
If you made it this far and it fails or gives you an error then you did something wrong. Start from step 1 restoring your phone to MJ5
(Option B) - Doesn't wipe phone
1. You are going to need an ADB Side loader and it can be found here.
2. Extract to directory C:\Mini-SDK
3. Rename 2400258.zip to update. (DO NOT NAME UPDATE.ZIP, JUST "update".)
4. Place "UPDATE" into the same folder as your ADB C:\Mini-SDK
5. Hold shift and right click in the folder to "Open command window here"
6. Reboot your phone into RECOVERY MODE (volume up + home)
7. Select "Apply update from ADB"
8. Plug phone into usb on PC
9. In your command window type "adb sideload update" without quotes and enjoy!​
If you made it this far and it fails or gives you an error then you did something wrong. Start from step 1 restoring your phone to MJ5
(Option C) - Untested
1. Settings, General, About, Software Update, Check for updates...
2. Download and install update​
If you made it this far and it fails or gives you an error then you did something wrong. Start from step 1 restoring your phone to MJ5
Thanks @opsmgr3774 for the donation!
Thanks @Ciberious42 and @evilpotatoman and anyone else I forgot.

Q&A​
1. Is this safe?
Yes it's using the same exploit from Root De La Vega to run a script that replaces the bad file that is stopping the OTA from installing.
What the script does:
Code:
mount -o rw,remount /system
rm /system/bin/mobicore-presetup.sh
cp /sdcard/mobicore-presetup.sh /system/bin
rm /sdcard/rldv.sh
2. It doesn't work for me!!!
Try it again from the very beginning and read step by step, slowly. Make sure you didn't miss anything! Download the files again also.

mazdamiata210 said:
Reserved
Click to expand...
Click to collapse
Im sure people would be a little more willing to try this is there was a little more info here.
What are these files fixing when flashed, how do i know that these good/ok files to flash that will not brick my device? Because you said it should work. Not nit picking or even saying that it doesnt work. BUT more info on what this is would be beneficial to everyone.

the2rrell said:
Im sure people would be a little more willing to try this is there was a little more info here.
What are these files fixing when flashed, how do i know that these good/ok files to flash that will not brick my device? Because you said it should work. Not nit picking or even saying that it doesnt work. BUT more info on what this is would be beneficial to everyone.
Click to expand...
Click to collapse
Well you're not flashing anything that isn't safe considering they're all the same files from different threads (that are safe) except for the script file in the miata fix zip that I made.

mazdamiata210 said:
Well you're not flashing anything that isn't safe considering they're all the same files from different threads (that are safe) except for the script file in the miata fix zip that I made.
Click to expand...
Click to collapse
Yes i understand have used the Evilpotato mans process. I was reffering to the miata Fix. Just want to know what we are flashing. I am not a dev i dont know how to look at a file and see if it will work/harm a phone.

the2rrell said:
Yes i understand have used the Evilpotato mans process. I was reffering to the miata Fix. Just want to know what we are flashing. I am not a dev i dont know how to look at a file and see if it will work/harm a phone.
Click to expand...
Click to collapse
It can't harm anything do not worry. If you followed this guide exactly it will work. Worst case scenario is that you will have to start over again. All it does is copy the missing file back onto the phone so it no longer fails at 27% it's a simple 3 line script you can open it in notepad and see what it's doing if you like.

I hope that posting this is not bad form, as I don't mean to sound skeptical of the OP....
Has anyone tried this method and had success?

TeldenW said:
I hope that posting this is not bad form, as I don't mean to sound skeptical of the OP....
Has anyone tried this method and had success?
Click to expand...
Click to collapse
Yes! Me! Lol it's completely safe

This fix is failing. Error appears that the device is not using NB4 update.

mazdamiata210 said:
It can't harm anything do not worry. If you followed this guide exactly it will work. Worst case scenario is that you will have to start over again. All it does is copy the missing file back onto the phone so it no longer fails at 27% it's a simple 3 line script you can open it in notepad and see what it's doing if you like.
Click to expand...
Click to collapse
thats all that i think most people will need to know just add that to the OP. the more info the better. if it will help people with the update then hey people need to be here testing/using this method.

TheChefSLC said:
This fix is failing. Error appears that the device is not using NB4 update.
Click to expand...
Click to collapse
Whoops I forgot to mention to take the ota update for nb4 before continuing! Sorry I'm running on 0 sleep... Try it again and after the mj5 restore update to nb4... then continue from step 2

mazdamiata210 said:
Whoops I forgot to mention to take the ota update for nb4 before continuing! Sorry I'm running on 0 sleep... Try it again and after the mj5 restore update to nb4... then continue from step 2
Click to expand...
Click to collapse
Indeed
after MJ5 restore, I was able to run the RDLV script in order to replace the system file needed, Then I ran the OTA update from recovery for NB4, Upon reboot, I was then able to install the KK update NC2

TheChefSLC said:
Indeed
after MJ5 restore, I was able to run the RDLV script in order to replace the system file needed, Then I ran the OTA update from recovery for NB4, Upon reboot, I was then able to install the KK update NC2
Click to expand...
Click to collapse
How do you run the script?

opsmgr3774 said:
How do you run the script?
Click to expand...
Click to collapse
It is part of the OP, the RDLV.sh file that you copy to the root of the internal storage. This is a script file that will replace the other .sh file on your system partition.

opsmgr3774 said:
How do you run the script?
Click to expand...
Click to collapse
When you finish the mj5 restore and update to nb4... As long as the miata fix files are on your internal memory and you reboot the script will run

mazdamiata210 said:
When you finish the mj5 restore and update to nb4... As long as the miata fix files are on your internal memory and you reboot the script will run
Click to expand...
Click to collapse
Thank you. I had done everything but the nb4 update and it failed so I of course panicked, then noticed TheChefSLC said they "ran" the script and wondered if I had missed a step. It's all squared away and fully updated now. It worked. Hooray.

This deserves a news page recommendation
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

I am getting a temporary error when trying to download the miata_kitkat fix. new link please
EDIT...It is working now. THanks

I can confirm this works. I just did it and I am now on 4.4.2 NC2. Thanks!!

This worked for me...
But I did have to use "(Option B) - Doesn't wipe phone", Option A did not work.
Now to wait for root...

[Guide][ROM][UPDATE]Running N8010XXUDNE4 on GT-N8013

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Always do a backup!!​For GT-N8013 Tablets​
N8010XXUDNE4!! /N8013/ GT-N8010 WiFi Only ROM​Download>>> N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.zip
Download>>> UPDATE-SuperSU-v2.01.zip for Root
Installing ROM
Requires a Factory Reset (Wipe) Thanks to @pre4speed
1. Unzip N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.zip
2. Install N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5 with included Odin 3.07
3. Skip through setup (WiFi won't work Yet)
4. Get back in download mod, and install philz_touch_6.41.6-n8013.tar.md5 ,openrecovery-twrp-2.7.1.0-gt-n8000.tar or N8013-CWM-Touch-6.0.3.6.tar.md5 (Your Choice)
5. Copy GT-N8013-KK-WiFi-Fix.zip, Stock-GT-N8000-leaked-KK-Boot.img-CWR-installer.zip and UPDATE-SuperSU-v2.01.zip to your sdcard
6. Reboot phone into recovery( Hold [power][volume-up] button until in recovery) Install Stock-GT-N8000-leaked-KK-Boot.img-CWR-installer.zip,GT-N8013-KK-WiFi-Fix.zip to fix WiFi
7. Install UPDATE-SuperSU-v2.01.zip to get root Thanks to @pre4speed
8. Reboot and you should have Wifi
9. Recommend doing a backup after you complete setting up your phone, before applying any add-ons
Files In download zip
**********************************************************************************************************************************************************************************************************************
N8000XXUDNE4!! /N8013/ GT-N8010 NON WiFi ROM​This is NON Wifi Tablet N8000 ROM
WARNING!! N8000/N8010/N8012 this Contains the GT-N8013 Bootloader​Download>>> N8000XXUDNE4_N8000OXADNE4_GT-N8013.tar.zip
Mega Link >>> N8000XXUDNE4_N8000OXADNE4_GT-N8013.tar.zip
Contains all files needed for GT-N8013
GT-N8013-KK-WiFi-Fix.zip........................................... .......................WiFi Work Around Fix.. Install this last after installing root
N8000XXUDNE4_N8000OXADNE4_GT-N8013.tar.md5................................Offic ial KK Firmware with Leaked Boot.img and JB bootloader files
N8013.pit .................................................. .....................................Only need if you want to reformat phone
Odin307.zip....................................... ...............................................Odi n
Recovery's You choose the one you want, Install with Odin
N8013-CWM-Touch-6.0.3.6.tar.md5................................... ..................CWM Recovery
openrecovery-twrp-2.7.0.0-gt-n8013.tar......................................... .....TWRP Recovery
philz_touch_6.41.6-n8013.tar.md5..................................... ...................Philz CWM touch recovery with eztra stuff
SystemUI_Remove_Signal_Icons_Official_KK_CWR_insta ller.zip...................Removes No Signal Circle from task bar
UPDATE-SuperSU-v1.94.zip......................................... ........................Used to Root and Give Root access to files
WiFi_Only_Remove_Phone_Service_N8013_Custom_Recovery_Installer.zip.... Removes phone apps...suppose to save battery from tablet not searching for towers Use Updated attached below
********************************************************************************************************************************************************************************************************
Running N8000XXUDNE4 on GT-N8013​Only tested on GT-N8013 Tablet​
Unzip N8000XXUDNE4_N8000OXADNE4_GT-N8013.tar.zip with 7-zip
Install with Odin and Skip through the settings then boot back to Download mode and install:
Install Custom Recovery
I used philz_touch_6.41.6-n8013.tar.md5
Install with Recovery UPDATE-SuperSU-v1.94.zip to get Root
SuperSU Home Page
ROOT GUIDE OFFICIAL STOCKROM N8000XXUDNE4 KitKat (4.4.2)
Install this for wifi fix
GT-N8013-KK-WiFi-Fix.zip
Removing Data Signal From Task Bar
SystemUI_Remove_Signal_Icons_Official_KK_CWR_installer.zip
Only removes No Data (Circle Icon)
Manually Unpacking Official Firmware
Download For Official KitKat Firmware
N8000XXUDNE4_N8000OXADNE4_DBT
Unzip N8000XXUDNE4_N8000OXADNE4_DBT.zip with 7-zip
Unzip N8000XXUDNE4_N8000OXADNE4_N8000XXUDNE1.tar.md5
Remove modem.bin,sboot.bin, boot.img and tz.img,
Use Boot.img from Leaked KK
I Used TAR_MD5_PACKAGER to repack the rest of the files and the leaked KK boot.img
Fix Screen Mirroring KitKat official 4.4.2 GT-N8013 by vickoc
Removing Phone Service
Phone apps removed should fix battery drain issue ( phone searching for towers)
SecPhone.apk ( Removes Cell Search Activity)
SecPhone.odex ( Removes Cell Search Activity)
SecMms_Tablet_Upgrade.apk
SecMms_Tablet_Upgrade.odex
SecTelephonyProvider.apk
SecTelephonyProvider.odex
Stk.apk
Stk.odex
Stop cell tower search battery usage
Install with Your Custom Recovery
WiFi_Only_Remove_Phone_Service_N8013_Custom_Recovery_Installer.zip
You can use Disable Application to disable (Freeze)any apps temporary not wanted to see in app Drawer
You can also use ADB to disable (Freeze)any other apps temporary not wanted to see in app Drawer
Code:
C:\Users\carl>adb shell
[email protected]:/ $ su
su
[email protected]:/ # pm list packages
pm list packages
package:com.sec.android.app.ringtoneBR
package:com.sec.android.app.phoneutil
package:com.android.defcontainer
package:com.samsung.android.scloud.quota
package:com.sec.android.gallery3d
package:com.android.phone
package:com.sec.android.fotaclient
package:com.sec.android.motions.settings.panningtutorial
package:com.fmm.dm
package:android.googleSearch.googleSearchWidget
package:com.sec.android.app.bluetoothtest
package:com.android.bluetooth
package:com.android.providers.calendar
package:com.vlingo.midas
package:com.sec.android.widgetapp.notificationwidget
package:com.sec.factory
package:com.samsung.android.app.divx
package:com.samsung.android.scloud.sync
package:com.android.browser
package:com.sec.android.allshare.service.fileshare
package:com.samsung.pickuptutorial
package:com.sec.android.app.snotebook
package:com.smartapp.appfreezer
package:com.android.providers.downloads.ui
package:com.gd.mobicore.pa
package:com.android.documentsui
package:com.android.vpndialogs
package:com.peel.app
package:com.android.providers.media
package:com.sec.android.widgetapp.at.yahoostock.stockclock
package:com.sec.android.app.lcdtest
package:com.sec.android.nearby.mediaserver
package:com.sec.android.widgetapp.analogclocksimple
package:com.siso.app.generic
package:com.sec.android.cloudagent
package:com.google.android.setupwizard
package:com.samsung.sec.sketch
package:com.sec.android.widgetapp.favoriteswidget
package:com.monotype.android.font.samsungsans
package:com.hu1.wallpaper.aurora2
package:com.android.settings
package:com.sec.android.service.cm
package:com.sec.pcw
package:com.google.android.street
package:air.com.adobe.pstouch.oem1
package:com.sec.android.widgetapp.webmanual
package:com.google.android.googlequicksearchbox
package:mobi.xperiacle.mwappsmanager
package:com.android.exchange
package:com.sec.app.samsungprintservice
package:com.sec.android.providers.tasks
package:com.google.android.backuptransport
package:com.sec.android.gesturepad
package:com.samsung.groupcast
package:com.sec.allsharecastplayer
package:com.wssyncmldm
package:com.google.android.apps.maps
package:com.android.wallpapercropper
package:com.sec.android.app.FileShareClient
package:com.android.providers.settings
package:com.sec.msc.learninghub
package:com.sec.android.app.mobileprint
package:com.sec.android.provider.snote
package:com.google.android.apps.docs
package:com.android.providers.downloads
package:com.smlds
package:net.woostudio.sqliteeditor
package:com.android.phasebeam
package:com.sec.android.fwupgrade
package:com.sec.android.app.wallpaperchooser
package:com.tgrape.android.radar
package:com.sec.android.widgetapp.at.hero.accuweather
package:com.google.android.videos
package:com.sec.bcservice
package:com.monotype.android.font.cooljazz
package:com.sec.android.app.popupuireceiver
package:com.android.inputdevices
package:com.orange.authentication.simcard.permission
package:com.sec.android.provider.logsprovider
package:com.sec.android.app.popupcalculator
package:com.google.android.configupdater
package:com.sec.enterprise.mdm.vpn
package:com.sec.android.app.FileShareServer
package:com.samsung.topicwall
package:com.sec.android.app.sysscope
package:com.samsung.music
package:com.sec.android.band
package:com.sec.android.app.samsungapps
package:android
package:com.android.providers.contacts
package:com.acrodea.crayonphysics
package:com.sec.android.app.servicemodeapp
package:com.epson.mobilephone.samsungprintservice
package:com.google.android.apps.uploader
package:com.android.externalstorage
package:com.sec.android.widgetapp.SPlannerAppWidget
package:com.android.providers.applications
package:com.samsung.android.sdk.spenv10
package:com.samsung.android.scloud.proxy.contacts
package:com.siriusapplications.quickboot
package:com.google.android.apps.plus
package:com.android.vending
package:com.sec.android.app.mt
package:com.sec.android.providers.downloads
package:com.sec.android.drmpopup
package:com.android.keychain
package:com.sec.android.widgetapp.at.hero.accuweather.widget
package:eu.chainfire.supersu
package:com.sec.android.mmapp
package:com.google.android.apps.magazines
package:com.wsomacp
package:com.samsung.klmsagent
package:com.sec.android.app.music
package:com.sec.android.app.minimode.res
package:com.google.android.gsf
package:com.android.keyguard
package:com.sec.android.widgetapp.ap.yahoonews
package:com.monotype.android.font.chococooky
package:com.android.shell
package:com.sec.usbsettings
package:com.google.android.syncadapters.contacts
package:com.fixmo.isa
package:com.samsung.scrc.idi.server
package:com.sec.phone
package:com.sec.android.app.wfdbroker
package:com.fmm.ds
package:com.android.providers.partnerbookmarks
package:com.android.contacts
package:com.sec.android.app.gamehub
package:com.samsung.everglades.video
package:com.siso.photoWall
package:com.android.htmlviewer
package:com.dama.paperartist
package:com.sec.android.app.parser
package:com.google.android.gsf.login
package:com.sec.android.inputmethod
package:com.sec.android.daemonapp.ap.accuweather
package:com.sec.android.directconnect
package:com.sec.android.widgetapp.dualclockanalog
package:com.android.calendar
package:com.sec.android.daemonapp.ap.yahoostock.stockclock
package:com.sec.android.provider.badge
package:com.samsung.SMT
package:com.sec.android.app.selftestmode
package:com.sec.android.app.factorymode
package:com.samsung.android.scloud.backup
package:com.android.sharedstoragebackup
package:com.adobe.air
package:com.sec.android.allshare.service.controlshare
package:com.google.android.marvin.talkback
package:com.android.certinstaller
package:com.siso.app.genericprintservice
package:com.monotype.android.font.rosemary
package:com.sec.spp.push
package:com.google.android.gms
package:com.sec.android.app.launcher
package:com.samsung.shareshot
package:com.android.dreams.phototable
package:com.sec.android.app.worldclock
package:com.sec.android.allshare.service.mediashare
package:org.simalliance.openmobileapi.service
package:com.dropbox.android
package:com.sec.enterprise.knox.attestation
package:air.SQLEditor
package:com.sec.android.app.SecSetupWizard
package:com.hp.android.printservice
package:com.sec.enterprise.mdm.services.simpin
package:com.sec.spen.flashannotate
package:com.sec.android.SamsungDrmProvider
package:com.sec.android.app.sns3
package:com.sec.android.providers.security
package:com.google.android.music
package:com.visionobjects.resourcemanager
package:com.android.wallpaper.livepicker
package:com.sec.android.directshare
package:com.sec.automation
package:com.diotek.mini_penmemo
package:com.android.packageinstaller
package:com.sec.app.RilErrorNotifier
package:com.sec.pcw.device
package:com.samsung.helphub
package:com.sec.android.app.wlantest
package:com.android.noisefield
package:com.android.email
package:com.sec.spen.flashannotatesvc
package:com.sec.android.app.FlashBarService
package:com.android.location.fused
package:com.android.backupconfirm
package:com.sec.android.widgetapp.programmonitorwidget
package:com.wssnps
package:com.android.musicfx
package:com.google.android.apps.books
package:com.sec.android.daemonapp.ap.yahoonews
package:com.android.soundrecorder
package:com.samsung.clipboardsaveservice
package:com.lifevibes.trimapp
package:com.sec.android.app.SPenKeeper
package:com.google.android.partnersetup
package:com.sec.tcpdumpservice
package:com.sec.android.app.GlanceView
package:com.android.proxyhandler
package:com.sec.msc.nts.android.proxy
package:com.sec.android.app.ve
package:com.sec.android.app.camera
package:com.sec.android.preloadinstaller
package:com.google.android.feedback
package:com.sec.dsm.phone
package:com.sec.phone.fake
package:com.sec.android.app.keyguard
package:com.google.android.talk
package:com.samsung.android.scloud.proxy.snote
package:com.sec.smartcard.manager
package:com.sec.android.app.myfiles
package:com.sec.chaton
package:com.android.providers.userdictionary
package:com.samsung.android.scloud.proxy.calendar
package:com.samsung.android.providers.context
package:com.sec.android.widgetapp.digitalclock
package:com.osp.app.signin
package:com.sec.android.Preconfig
package:com.android.pacprocessor
package:com.sec.android.cloudagent.dropboxoobe
package:com.samsung.android.scloud.auth
package:com.samsung.videohub
package:com.samsung.android.mdm
package:com.sec.android.app.mediasync
package:com.sec.android.app.controlpanel
package:com.android.printspooler
package:com.google.android.syncadapters.calendar
package:com.LocalFota
package:com.samsung.android.scloud.proxy.browser
package:com.samsung.android.MtpApplication
package:com.android.dreams.basic
package:com.google.android.play.games
package:com.sec.android.app.clockpackage
package:com.sec.android.app.personalization
package:com.android.systemui
package:com.samsung.sec.android.application.csc
package:com.infraware.polarisoffice5tablet
package:com.samsung.android.livewallpaper.deepsea
package:com.sec.android.app.videoplayer
package:com.sec.android.app.DataCreate
package:com.sec.android.app.SuggestionService
package:com.speedsoftware.sqleditor
package:com.google.android.gm
package:com.sec.android.widgetapp.dualclockdigital
package:com.estrongs.android.pop
package:com.samsung.android.livewallpaper.luminousdots
package:com.henry.sqliteqa_litte
package:com.android.chrome
package:com.sec.android.Kies
package:com.sec.dsm.system
package:com.sec.knox.seandroid
package:com.sec.android.contextaware
package:com.sec.esdk.elm
[email protected]:/ # pm disable com.android.phone
pm disable com.android.phone
Package com.android.phone new state: disabled
[email protected]:/ #
Install Attached SecPhone.apk_Official_KK_CWR_installer.zip if you want phone app back

Failed on my N8010.
Checked GT-N8013-KK-WiFi-Fix.zip and cannot understand how it worked. What's the function of the files which are put into /data?
And if this doesn't work on N8010, is there another way I can try?

This worked for me
Smart-X said:
Failed on my N8010.
Checked GT-N8013-KK-WiFi-Fix.zip and cannot understand how it worked. What's the function of the files which are put into /data?
And if this doesn't work on N8010, is there another way I can try?
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showpost.php?p=53065121&postcount=77 (just ignore the Tip)
I tried in on a N8010 and this worked for me, but I think it's essentially the same. I assume the only difference is that the boot.img from the leaked ROM is inlcuded in the tar in this guide and not in a flashable zip as in the guide from the other thread.
Also did you check, if one of your files was corrupted. If so, just redownload and retry

Smart-X said:
Failed on my N8010.
Checked GT-N8013-KK-WiFi-Fix.zip and cannot understand how it worked. What's the function of the files which are put into /data?
And if this doesn't work on N8010, is there another way I can try?
Click to expand...
Click to collapse
The /data files some how fix the IP address issue.
Did you root your phone yet? it may have to be rooted to copy to your userdata partition
When you install the ROM did you have to set it up? If you did not then you did not install on a clean system and that may cause issues.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Yes I Wiped almost everything before installing the ROM.
And yes I had to set it up at the first boot after installation.
And yes I root my phone with SuperSU 1.99r3.
So those files fix the IP address issue.
Can they be used on N8010 too?
Anyway I'll try it again later.

Smart-X said:
Yes I Wiped almost everything before installing the ROM.
And yes I had to set it up at the first boot after installation.
And yes I root my phone with SuperSU 1.99r3.
So those files fix the IP address issue.
Can they be used on N8010 too?
Anyway I'll try it again later.
Click to expand...
Click to collapse
did you install the leaked boot.img? I had to install it to get wifi going, it would not work with the Official KK boot.img
I do not know about 8010, sorry

carl1961 said:
did you install the leaked boot.img? I had to install it to get wifi going, it would not work with the Official KK boot.img
I do not know about 8010, sorry
Click to expand...
Click to collapse
I failed yesterday with installing both the leaked boot.img and GT-N8013-KK-WiFi-Fix.zip.
I'll try the whole installation again When I got my N8010 later today.
Thanks for your answers.

Just installed and it works great! Now I don't have to wait!

Update OP
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Please simplify post.
First, Thank you so much. In the words of the song Thrift Shop "This is freakin awsome!"
There is a lot of stuff going on in the OP. I haven't flashed in a while so I am rusty. This is what I am seeing:
Mega Link has all of the files that I need.
Install ROM using Odin (skip through settings and boot back to Download mode)
Use Odin to install Custom Recovery
Use recovery to install wifi fix, wifi only remove phone service and systemUI remove system icons
Finish.
What about the other files in zip? Do i need them? (N8013 pit), (CWM Touch), (Open Recovery)
Can I use Mobile Odin?
I just want to get it right before I flash this awesomeness.

carl1961 said:
Install with Odin and Skip through the settings then boot back to Download mode and install:
Click to expand...
Click to collapse
I'm not very familiar with using odin. Which files are we putting into odin and where do I put them in? Also, is the PIT file required?

TimDotThomas said:
First, Thank you so much. In the words of the song Thrift Shop "This is freakin awsome!"
There is a lot of stuff going on in the OP. I haven't flashed in a while so I am rusty. This is what I am seeing:
Mega Link has all of the files that I need.
Install ROM using Odin (skip through settings and boot back to Download mode)
Use Odin to install Custom Recovery
Use recovery to install wifi fix, wifi only remove phone service and systemUI remove system icons
Finish.
What about the other files in zip? Do i need them? (N8013 pit), (CWM Touch), (Open Recovery)
Can I use Mobile Odin?
I just want to get it right before I flash this awesomeness.
Click to expand...
Click to collapse
GT-N8013-KK-WiFi-Fix.zip..................................................................WiFi Work Around Fix.. Install this last after installing root
N8000XXUDNE4_N8000OXADNE4_GT-N8013.tar.md5................................Official KK Firmware with Leaked Boot.img and JB bootloader files
N8013.pit .......................................................................................Only need if you want to reformat phone
Odin307.zip......................................................................................Odin
Recovery's You choose the one you want, Install with Odin
N8013-CWM-Touch-6.0.3.6.tar.md5.....................................................CWM Recovery
openrecovery-twrp-2.7.0.0-gt-n8013.tar..............................................TWRP Recovery
philz_touch_6.41.6-n8013.tar.md5........................................................Philz CWM touch recovery with eztra stuff
SystemUI_Remove_Signal_Icons_Official_KK_CWR_installer.zip...................Removes No Signal Circle from task bar
UPDATE-SuperSU-v1.94.zip.................................................................Used to Root and Give Root access to files
WiFi_Only_Remove_Phone_Service_N8013_Custom_Recovery_Installer.zip.... Removes phone apps...suppost to save battery from tablet not searching for towers

link6155 said:
I'm not very familiar with using odin. Which files are we putting into odin and where do I put them in? Also, is the PIT file required?
Click to expand...
Click to collapse
N8000XXUDNE4_N8000OXADNE4_GT-N8013.tar.md5 Install this with Odin, Click on (PDA) and select file to install, All install here
N8013.pit Only need if you want to reformat phone
Install Recovery with Odin ( Only need one of these)
N8013-CWM-Touch-6.0.3.6.tar.md5
openrecovery-twrp-2.7.0.0-gt-n8013.tar
philz_touch_6.41.6-n8013.tar.md5
All these you copy to SD card and install with Recovery
SystemUI_Remove_Signal_Icons_Official_KK_CWR_installer.zip
UPDATE-SuperSU-v1.94.zip
WiFi_Only_Remove_Phone_Service_N8013_Custom_Recovery_Installer.zip

carl1961 said:
N8000XXUDNE4_N8000OXADNE4_GT-N8013.tar.md5 Install this with Odin, Click on (PDA) and select file to install, All install here
N8013.pit Only need if you want to reformat phone
Install Recovery with Odin ( Only need one of these)
N8013-CWM-Touch-6.0.3.6.tar.md5
openrecovery-twrp-2.7.0.0-gt-n8013.tar
philz_touch_6.41.6-n8013.tar.md5
All these you copy to SD card and install with Recovery
SystemUI_Remove_Signal_Icons_Official_KK_CWR_installer.zip
UPDATE-SuperSU-v1.94.zip
WiFi_Only_Remove_Phone_Service_N8013_Custom_Recovery_Installer.zip
Click to expand...
Click to collapse
Install (recovery) one at a time starting with SuperSu or can this recovery do multiple flashes?

TimDotThomas said:
Install (recovery) one at a time starting with SuperSu or can this recovery do multiple flashes?
Click to expand...
Click to collapse
I would install one at a time say root then what ever other's, and then I would do a reboot then install wifi fix last after a reboot with root working

Cool. Now in my haste I did not click re-partition. Is that a problem? Should I reflash?
Sent from my Nexus 5 using XDA Free mobile app

TimDotThomas said:
Cool. Now in my haste I did not click re-partition. Is that a problem? Should I reflash?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
no you do not check that
if you install the pit file it will auto check

Working on my N8013
Just installed this and it's working fine for the most part

Warning
I decided to do a factory reset. BIG MISTAKE! I think I bricked my device. It is force closing in another language. When I flash the ROM again, it still does not work. It is getting late. Tomorrow I will flash stock ROM and then reflash this new one. Hope that works. Any suggestions?

TimDotThomas said:
I decided to do a factory reset. BIG MISTAKE! I think I bricked my device. It is force closing in another language. When I flash the ROM again, it still does not work. It is getting late. Tomorrow I will flash stock ROM and then reflash this new one. Hope that works. Any suggestions?
Click to expand...
Click to collapse
Before installing do a factory reset then use the pit file with install, repatriation should be checked like picture on op.
Sent from my GT-N8000 using XDA Premium 4 mobile app

Optimized Boot Image (Ramdisk/Kernel) for 6.0.1 Boost Desire 626s

***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY***
CLEAR/DELETE DALVIK-CACHE FOLDER FROM "/data/dalvik-cache" IN ROOT EXPLORER OR TWRP AFTER INSTALLING BOOT IMAGE TO ALLOW SYSTEM TO ADJUST
##FLASH THE LATEST SUPERSU ZIP BELOW##
P.S. I NOTICE IT IS NO LONGER SYSTEM-LESS MODE. SO WE CAN TRIM THE SUPERSU SYSTEM-LESS CONTENT FROM THE RAMDISK.
Tweaked the contents of the boot image to allow for faster boot and better runtime performance. I use it as my daily driver. App performance is snappier. Only for the Boost Desire 626s. Unzip and flash with Flashify, TWRP, or your choice of image flasher. I also added some optimization scripts to supplement the boot image. Run them with Smanager, Root Explorer or in the terminal. Also here is a zip 601626SPIEFIX.zip that when flashed in TWRP recovery will allow the system to run non-pie executables and it works great. You'll be able to run custom binaries without any issue or error. All zips in this thread are the latest.
If you have ISSUES WITH DATA SPEEDS in certain areas, especially if you tether, GO INTO THE DIALER and DIAL *#*#4636#*#* then ACCESS PHONE INFORMATION and SELECT CDMA auto (PRL) UNDER SET PREFERRED NETWORK TYPE. LTE seems to be problematic in certain areas with speeds dropping to 150kbps and with this solution you'll be getting about 600 to 700kbps so at least it'll be a gain until you get into an area with better LTE coverage. In a good coverage area, I get download speeds of up to 5 to 7 mbps with LTE on, but in bad areas, CDMA works better. If you want to tether with a wireless third party solution make sure to run in a terminal window or adb shell as root : pm disable com.htc.tetheringguard
DOWNLOAD BOOT IMAGE: http://forum.xda-developers.com/attachment.php?attachmentid=3917986&d=1477604429
DOWNLOAD SUPERSU BETA: https://download.chainfire.eu/1009/SuperSU/SR2-SuperSU-v2.78-SR2-20161029143931.zip?retrieve_file=1
DOWNLOAD SCRIPTS: http://forum.xda-developers.com/attachment.php?attachmentid=3863279&d=1472880351
DOWNLOAD PIE FIX: http://forum.xda-developers.com/attachment.php?attachmentid=3844539&d=1471383163
DOWNLOAD BOOT IMAGE TOOL : http://forum.xda-developers.com/attachment.php?attachmentid=3917995&d=1477605263
DOWNLOAD HTC DRIVERS AND MINIMAL ADB + FASTBOOT: http://forum.xda-developers.com/attachment.php?attachmentid=3868562&d=1473328405
ANDBLOCKDEV.sh from scripts zip will speed up file input and output speeds, its contents have been incorporated into the boot image so the scripts files are for your own archival.
The zip DESIRE626SIMGTOOL.zip contains the android image kitchen and the 6.0.1 Boost Desire 626S boot image contents already extracted into two folders split_img and ramdisk with recent modifications. Enjoy!
http://www.vysor.io/ is a great tool to control your android device from a computer within chrome. You should try it out.
I provided a zip named HTCDrivers.zip containing the installation for both fastboot and adb drivers for the Boost Desire 626S, and minimal adb and fastboot. This will help you connect your device up with Vysor.
COPY the FILES; fastboot.exe, adb.exe, AdbWinUsbApi.dll and AdbWinApi.dll FROM - C:\Program Files (x86)\Minimal ADB and Fastboot - TO - C:\Windows\System32 - AND - C:\Windows\SysWOW64
Once you have installed the drivers for HTC devices,
and copied the minimal adb and fastboot files specified above to both system folders, you should be able to run adb commands without a problem by just opening a command prompt as administrator,
and RUNNING the command:
adb devices
- to start the adb server. This will allow connection with Vysor.
##########
For those who prefer nightbreed813's 6.0.1 slim rom version, I uploaded 601VPNDIALOGSFIX.zip to fix the issue with authorizing VPN clients, but first YOU HAVE TO CREATE /system/priv-app/VpnDialogs in Root Explorer or any other root filesystem browser, then reboot to TWRP recovery and flash the zip.
DOWNLOAD VPNFIX : http://forum.xda-developers.com/attachment.php?attachmentid=3860930&d=1472669879
##########
Also, you can get your MSL/SPC security code easily.........
Use the info in this thread to get your MSL/SPC security code so you can write new values to NV entries in the modem. Some values are locked but you can change the BC config for both LTE and CDMA so that would at least be helpful.
INFO HERE: http://forum.xda-developers.com/spri...k-sim-t3314755
##########
Android settings can be changed in the terminal for three namespaces; system, global and secure.
In the terminal run:
settings list system
settings list global
settings list secure
For each namespace all associated settings and their values will be listed. To change a setting type:
settings put system setting_name_here value_here
settings put global setting_name_here value_here
settings put secure setting_name_here value_here
##########
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Look now has working VPN......
***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY***

anthonykb said:
Tweaked the contents of the boot image to allow for faster boot and better runtime performance. I use it as my daily driver. App performance is snappier. Only for the Boost Desire 626s. Unzip and flash with Flashify, TWRP, or your choice of image flasher. I also added some optimization scripts to supplement the boot image. Run them with Smanager, Root Explorer or in the terminal. Also here is a zip 601626SPIEFIX.zip that when flashed in TWRP recovery will allow the system to run non-pie executables and it works great. You'll be able to run custom binaries without any issue or error. All zips in this thread are the latest.
Click to expand...
Click to collapse
Will this run on the Metro Variant?

As far as I know no but you can try in case it might.
Enter these commands in a new terminal window:
cd /dev/block/platform/soc.0/7824900.sdhci/by-name
dd if=boot of=/sdcard/backup.img
The backup boot image can be flashed from the sdcard in TWRP recovery if the device fails to boot into the system after flashing the boot image contained in the zip in the attachments.

Is there anyway you would be able to make one for the metro Variant if i upload my boot image?

MetroPCS Boot Image
GotHeart said:
Is there anyway you would be able to make one for the metro Variant if i upload my boot image?
Click to expand...
Click to collapse
Did you try unzipping the boot image and flashing it already? I don't think it could work that way. I would do it if I had the metro version myself.

anthonykb said:
Did you try unzipping the boot image and flashing it already? I don't think it could work that way. I would do it if I had the metro version myself.
Click to expand...
Click to collapse
Thats what im saying.if i upload my metro boot image would you be able to optimize it like you did before with the boost Variant?

GotHeart said:
Thats what im saying.if i upload my metro boot image would you be able to optimize it like you did before with the boost Variant?
Click to expand...
Click to collapse
I meant so you tried the boost version and it wouldn't boot?

anthonykb said:
I meant so you tried the boost version and it wouldn't boot?
Click to expand...
Click to collapse
No i havent tried it yet

GotHeart said:
No i havent tried it yet
Click to expand...
Click to collapse
Backup your kernel boot image to your sdcard and flash the boost version just to make sure.
cd /dev/block/platform/soc.0/7824900.sdhci/by-name
dd if=boot of=/sdcard/backup.img
Then unzip the 601bootimg.zip file with Zarchiver in the Play Store and flash the extracted boot image.

anthonykb said:
Backup your kernel boot image to your sdcard and flash the boost version just to make sure.
Click to expand...
Click to collapse
Okay ill do it now and let you know

The phone booted but it corrupted my sdcard,so i lost everything i had on there.

GotHeart said:
The phone booted but it corrupted my sdcard,so i lost everything i had on there.
Click to expand...
Click to collapse
Flash back the backed up boot image in TWRP and see if the sdcard mounts right. The mount point contained in the boost boot image is probably wrong for the the sdcard/emmc in the metropcs phone.

I did but my sdcard got corrupted so i was forced to format it.

GotHeart said:
I did but my sdcard got corrupted so i was forced to format it.
Click to expand...
Click to collapse
I'm so sorry the process turned out to be a dud for you I have the boost model myself. Hope you can recover your files with one of those forensic data recovery tools.

anthonykb said:
I'm so sorry the process turned out to be a dud for you I have the boost model myself. Hope you can recover your files with one of those forensic data recovery tools.
Click to expand...
Click to collapse
Its nothing important lol.any chance you can share what you did or how?

Use the Android Image Kitchen by osm0sis
GotHeart said:
Its nothing important lol.any chance you can share what you did or how?
Click to expand...
Click to collapse
Use the tool at the link below to unpack the image, make your modifications, and repack the image contents (The ramdisk and split_img folders.) It's available for Windows, Linux and Android. It's a simple process expect for knowing what you'd need to do to the image.
http://forum.xda-developers.com/showthread.php?t=2073775

anthonykb said:
Use the tool at the link below to unpack the image, make your modifications, and repack the image contents (The ramdisk and split_img folders.) It's available for Windows, Linux and Android. It's a simple process expect for knowing what you'd need to do to the image.
http://forum.xda-developers.com/showthread.php?t=2073775
Click to expand...
Click to collapse
My mistake i was in a hurry when i typed that last reply.
Im aware of how to unpack/repack boot images and i appreciate the link,but i was wondering what modifications that were made.if youd prefer not to share,i can upload my boot image if youd like to make the modifications yourself.im just trying to make this compatible with the metro version.

The same modifications done for the Boost Desire 626S might not work well for the MetroPCS version so upload the image you backed up yesterday as an attachment in a reply post and I'll work on it.

Thanks a ton!

MetroPCS Boot Image
GotHeart said:
Thanks a ton!
Click to expand...
Click to collapse
Run busybox top in the terminal on your phone and post some screenshots so I can see what might need to be done. We want to see what processes would be the culprit behind bogging down precious processor time and reducing the snappiness of the device in reacting to realtime input and handling current requests.

V570KL WiFi error fix [need testers]

Hello, I think I found what is the issue with WiFi - Vendor configs don't change WiFi Country code but they do change region and that causes the WiFi error. I was able to unpack the .RAW file to a normal folder and then the system.ISO where I was able to edit the build.prop and vendor props.
I prepared a few methods on how to edit the ROM to make WiFi work:
A) Changed the country code in the build.prop to a chosen country [you won't be able to use WiFi abroad of that country].
B) Edited all the vendor props to change WiFi country code to according countries [should work everywhere].
C) Removed the country code line from build.prop files [may work everywhere or nowhere]. -checked more files in the system and came to conclusion that this method won't work
The edited ROM will have to be flashed using Qualcomm flashing tool as there's no way to repack it to .RAW file.
For testers:
Before flashing copy all your files as they will be removed. Also mind the fact that I don't know if this will work or brick your device [if it does brick it then you can flash an unedited ROM to fix it].
Tutorial how to build your ROM:
1. Go to: https://drive.google.com/open?id=1Iph9eTL6dU_x_LAOt7Z9PN7KbwCAHACn
2. Download V570KL.rar
3. Go to Done2 folder and download system folder and IMG_EXTRACTOR_3.1 software from there. [For extractor software you'll have to download Java and Python]
4. Go to main folder and then go to Patch folder and go to Method C folder and download the folder with your country name [if it's not there contact me].
5. Locate your downloaded files and place them into one folder for easier work on them.
6. Unpack V570KL.rar
7. Copy build.prop file from country name folder and replace the build.prop in system folder with it.
PATCHING system.IMG
8. Open Img_Extractor [you need Python and Java for it to work], choose system.IMG and select Repack option. Now locate the edited system file. When it's selected check the byte number if it's the same as the one that system.IMG in V570KL folder has. If it's the same click Repack and wait till it does it's thing. [If the number is not the same edit it to the same number].
9. Replace the system.IMG in V570KL folder with our patched .IMG file.
PATCHING recovery.IMG
10. Reopen Img_Extractor software and choose recovery.IMG option.
11. Locate recovery.img [it's in V570KL folder].
12. Unpack the file, after unpacking locate the unpacked folder and go to initrd folder that's inside of it and there replace default.prop with default.prop located in country patch folder.
13. Go back to Img_Extractor and repack recovery.IMG
PATCHING ROM
14. Prepare edited system.IMG and recovery.IMG
15. Open V570KL folder and paste our patched IMGs in there [replace the old ones or remove them].
16. Our ROM is now ready.
*note - Img_Extractor has to be run with Admin rights to properly unpack/repack the files.
Flashing Tutorial:
QFIL flashing won't be possible as I couldn't get the needed Firehose file for it to work. There is however a Firehose file for V520KL [Asus Zenfone V] which might work but it's pretty risky to do.
A much safer method then will be to flash V570KL ENG rom first with Asus Flashing tool and on this rom we'll be able to unlock bootloader [open path to flashing edited roms].
There's also the VZW Repair Tool that could help us flash the phone, after the phone is detected the software will download OG Verizon ROM that can be replaced [in our case with the ENG ROM], after it's installed we will be able to flash the edited one.
Flashing tutorial downloads:
Asus Flashing Tool - https://www.asusflashtool.com/ [download version 2.0.1 and put your phone into recovery before connecting it to PC]
VZW Repair Tool - https://drive.google.com/drive/folders/15KAGi4XeKf8lwuJ46XO5LZ1mZLM7f5V1
V570KL ENG ROM - https://drive.google.com/open?id=1cizBJWHG1oDduMcImWAE_jSsbfQ5TJi6
Built ROM downloads:
MethodA - UA + camera2api + removed verizon features - https://drive.google.com/drive/folders/1g7jbq2UxQC1XFzqCUjfCa1XIVq23Vs14
MethodB - universal* + camera2api + removed verizon features - https://drive.google.com/drive/folders/1OYNjKjV8H2mhRpdyROgLCM7AeIxj0emw
MethodC - universal - not releasing
MethodC2 - universal + camera2api + removed verizon apps and features - not releasing
universal* - may not work in Ukraine and Russia as there were no vendor files for those countries in the system, however there was a file called EUCommon that may make it work

Update: I found a secret menu using this code in the dialer app which let's you turn OEM mode on [it should enable bootloader unlocking!].
Code: *#*#759#*#*

Hi friend, I have this phone. I will be glad to work together, I could not do everything according to your instructions. I guess I don't understand English well. I will be happy to work with you with the help of a team viewer. Please contact me

I edited the ROM but I don't know how to flash it, previous flashing methods for this model don't work anymore because of Asus disabling the only flashing tool with V570KL model, V2 doesn't support this model. I also thought of replacing the .RAW files in Verizon repair tool but I don't know if that would work, can't check that.
Anyway I added ENG rom link.

Hello!
So I just bought this phone online so my son could use Daydream. I'm not on Verizon and the plan was to just use WiFi. Well... I have the WiFi problem. I have worked though multiple other methods to try and find a fix and nothing has worked. I'm at the point where I'm about to try OP's method. Because of the possibility of bricking the device, wanted to check in first to see if anyone has continued to work on the problem or if there are any new developments. Once I make the decision to attempt, I will check in and after to let you know what happens.
Thanks!
Rk

Anyone know how to fix wifi issue on my v570kl without breaking it? I'm from ukraine.

Hi! I need your help solving WiFi problem for V570KL for country "UA". I downloaded your rar file from Google Drive along the path "Asus/Patch/Full_MethodA [Ukraine]/UA [Ukraine]/V570KL_edited.rar".
What do I do next? As I understand it, I need to launch the Asus Flash Tool, enter the phone in the recovery and connect the cable to the computer, then select the V570KL_edited.rar file and start flashing. I am asking for your help.

Well, I know this is a dead thread, still I'm coming here quite interested into recovering an investment in this phone I bought on Amazon, based in the replies of the questions of the product, saying it's unlocked... and surprise! As I placed a Movistar (VE) SIM on it for using, I found that I'm unable to use WiFi.
I've been following this steps for days (since Dec. 26, in fact) and everything has been dead end over dead end.
I can say that I've been looking for an stand-alone/offline version of AFT 1.0.0.72 with no success. I keep getting the error of 'Failed to download the version control file via FTP'.
I'm using 3 computers for this: a W7 32-bit notebook, a W10 64-bit desktop and a W11 64-bit laptop. I'm saying this, because... well, for some reason I've noticed about AFT v2:
In W7, it opens but doesn't recognize the phone battery
In W10, it doesn't even open
In W11, it goes smoothly and read phone battery
I'll add it is crucial AFT v2 reading phone battery (that means, phone turning on normally) because otherwise it doesn't do anything at all.
Anyway, when I tried flashing with AFT v2, it was a dead end because it did nothing (that was after program sending the phone into recovery mode). I tried to manually sideload it with 'adb sideload <filename>' with no success, getting an error message saying it can't read the file.
I opened the .zip files... surprise, .RAW files inside! I've used adb sideload before in Huawei phones, and I know the usual is to see .img files, so... I guess I need to decompress (somehow) the .RAW file. I'll take a look in that later.
Still, I want to attempt first the path suggested of VZWSUATool, just to see if I can somehow force it to install the ENG .RAW software. Right now I'm using the W11 64-bit laptop, but if compatibility problems arise, I'll jump back to W7 32-bit notebook.
Update 1 - 21:48 VET / 2023-01-03
Maybe VZWSUATool is another dead end. I've tried it first on the W11 64-bit laptop and it doesn't even starts (there are 2 library errors). I went back to W7 32-bit laptop, and... turned on normally does nothing, so I went into 'How to Repair...', put the phone into Fastboot but and after passing the FRP question, the "Unsupported device" window came up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update 2 - 22:19 VET / 2023-01-03
I decided to throw a risky attempt, basically crossing fingers at this point. I know the (sort of) equivalent model to our V570KL is ZS571KL. In AFT 1.0.0.45, the only option "close" to it is ZS570KL. Yeah, I was attempting something a bit absurd, but had not much to lose.
Another failed atttempt.
(Note: It was in Blue = Connected when it started)
Update 3 - 22:45 VET / 2023-01-03
Okay, apparently I'm heading into a new clue this time. Using the W11 64-bit laptop, I decided to force-choosing the .RAW file, and selected 'V570KL_all_VZW_user_V3.8.1.raw'
It recognized the file, rebooted into recovery, and this time recovery DID something. It was a failure, but what does surprise me is the file being, eh... succesfully sideloaded.
I'll try to sideload .RAW file 'V570KL_all_WW_eng_T3.0.6.raw' and see what happens.
Update 4 - 22:53 VET / 2023-01-03
Okay, I'll continue my attempts tomorrow. For now, with ASUS Zenfone Fash Tool V2.0.1.0, in the W11 64-bit Laptop (the only one in where it's working as it should, apparently) is giving the same error as in Update 3 for VZW .raw file, and WW .raw file does, ehm... nothing. I don't know what I'm skipping, I'll re-download the file and see what happens tomorrow after arriving home from work.

SlenderPL said:
Update: I found a secret menu using this code in the dialer app which let's you turn OEM mode on [it should enable bootloader unlocking!].
Code: *#*#759#*#*
Click to expand...
Click to collapse
After giving up for today, I decided to try this path, and...at least using standard unlocking methods, phone doesn't seem to understand what's happening, haha
ASUS guys really wanted to make this the most impossible, don't they?

Pedreo1997 said:
Well, I know this is a dead thread, still I'm coming here quite interested into recovering an investment in this phone I bought on Amazon, based in the replies of the questions of the product, saying it's unlocked... and surprise! As I placed a Movistar (VE) SIM on it for using, I found that I'm unable to use WiFi.
I've been following this steps for days (since Dec. 26, in fact) and everything has been dead end over dead end.
I can say that I've been looking for an stand-alone/offline version of AFT 1.0.0.72 with no success. I keep getting the error of 'Failed to download the version control file via FTP'.
I'm using 3 computers for this: a W7 32-bit notebook, a W10 64-bit desktop and a W11 64-bit laptop. I'm saying this, because... well, for some reason I've noticed about AFT v2:
In W7, it opens but doesn't recognize the phone battery
In W10, it doesn't even open
In W11, it goes smoothly and read phone battery
I'll add it is crucial AFT v2 reading phone battery (that means, phone turning on normally) because otherwise it doesn't do anything at all.
Anyway, when I tried flashing with AFT v2, it was a dead end because it did nothing (that was after program sending the phone into recovery mode). I tried to manually sideload it with 'adb sideload <filename>' with no success, getting an error message saying it can't read the file.
I opened the .zip files... surprise, .RAW files inside! I've used adb sideload before in Huawei phones, and I know the usual is to see .img files, so... I guess I need to decompress (somehow) the .RAW file. I'll take a look in that later.
Still, I want to attempt first the path suggested of VZWSUATool, just to see if I can somehow force it to install the ENG .RAW software. Right now I'm using the W11 64-bit laptop, but if compatibility problems arise, I'll jump back to W7 32-bit notebook.
Update 1 - 21:48 VET / 2023-01-03
Maybe VZWSUATool is another dead end. I've tried it first on the W11 64-bit laptop and it doesn't even starts (there are 2 library errors). I went back to W7 32-bit laptop, and... turned on normally does nothing, so I went into 'How to Repair...', put the phone into Fastboot but and after passing the FRP question, the "Unsupported device" window came up.
Update 2 - 22:19 VET / 2023-01-03
I decided to throw a risky attempt, basically crossing fingers at this point. I know the (sort of) equivalent model to our V570KL is ZS571KL. In AFT 1.0.0.45, the only option "close" to it is ZS570KL. Yeah, I was attempting something a bit absurd, but had not much to lose.
Another failed atttempt.
(Note: It was in Blue = Connected when it started)
Update 3 - 22:45 VET / 2023-01-03
Okay, apparently I'm heading into a new clue this time. Using the W11 64-bit laptop, I decided to force-choosing the .RAW file, and selected 'V570KL_all_VZW_user_V3.8.1.raw'
It recognized the file, rebooted into recovery, and this time recovery DID something. It was a failure, but what does surprise me is the file being, eh... succesfully sideloaded.
I'll try to sideload .RAW file 'V570KL_all_WW_eng_T3.0.6.raw' and see what happens.
Update 4 - 22:53 VET / 2023-01-03
Okay, I'll continue my attempts tomorrow. For now, with ASUS Zenfone Fash Tool V2.0.1.0, in the W11 64-bit Laptop (the only one in where it's working as it should, apparently) is giving the same error as in Update 3 for VZW .raw file, and WW .raw file does, ehm... nothing. I don't know what I'm skipping, I'll re-download the file and see what happens tomorrow after arriving home from work.
Click to expand...
Click to collapse
Update 5 - 16:40 VET / 2023-01-07
I took a break for a couple days for returning to this hell, and... let's see the progress so far:
* ASUS Zenfone Flash Tool V2.0.1.0 is doing nothing to help.
* I investigated there is a way to flash manually (using fastboot) the whole system, so it should be helpful, I think.
* Using a tool our friend SlenderPL left in the GDrive folder 'Asus Tool (RC4)', I unpacked the whole .RAW file. That was at first thinking into creating a .zip file to attempt another way to flash the ROM, but then I did found apparently it has more success chances trying to flash the stock rom, file by file, using 'fastboot flash' command, file by file. However, of course I need the tree, the .xml, the .bat file that tells me the order of how flashing it. It doesn't exist.
Right now I have a folder with the whole .RAW totally unpacked.
* I tried to force flashing, entering into Recovery, and then using sideload, writing:
adb sideload V570KL_all_WW_eng_T3.0.3.raw
Click to expand...
Click to collapse
of course, after placing the .raw file in the same folder of platform-tools on the computer. The phone did read the file, but again I got an error 'E:signature verification failed'.
Let's see whay newer idea I get...

Hello, I am the owner of 5 gadgets of this model and I want to solve the issue with Wi-Fi. For a year now I have been studying different options and trying to do the same. The last idea remains, but advice is needed. What if you remove the cover, find the pins for direct connection of the memory to the PC and simply replace the files in the hdd editor to work Wi-Fi?

wivelt said:
Hello, I am the owner of 5 gadgets of this model and I want to solve the issue with Wi-Fi. For a year now I have been studying different options and trying to do the same. The last idea remains, but advice is needed. What if you remove the cover, find the pins for direct connection of the memory to the PC and simply replace the files in the hdd editor to work Wi-Fi?
Click to expand...
Click to collapse
I think it's on the edge of fantasy. Try to do it, and if it works, write a detailed guide. I will be extremely grateful!