insufficient storage space gapps - ZTE Axon 7 Questions & Answers

Hi,
I got the message that I have insufficient storage space in /system when I want to install Google apps for Android pie the stock version.
I know that a workaround is to install a smaller package that is not What I Want.
I also tried reboot to recovery.
What's going on.
Thanks

boot in twrp and go to delete / extended delete / and there makirst you system memory and press then change size and swipe

Chris axon 7 said:
boot in twrp and go to delete / extended delete / and there makirst you system memory and press then change size and swipe
Click to expand...
Click to collapse
Thank you so much.
I did not find 'extended delete' nor 'makirst'.
But i think you meant 'advanced wipe' and 'resize'.
I tried that and it worked!

But i think you meant 'advanced wipe' and 'resize'.
I tried that and it worked!
Yes that i mean it

Related

my magic cant stop rebooting!!!

sorry for disturbing all of you
but i really have no solution to deal with it
after flashing the rom CyanogenMod 5.0.8-final Stable/Fast 2.1
my magic reboots and it cant stop
wt happened to my phone?
please help me............
well wrong section but it will be moved.
anyway... can you boot to recovery?
if so put another rom on the sd card.( try this http://forum.xda-developers.com/showthread.php?t=654284)
follow the steps, wipe, flash and come back to here to say if it worked
good luck
thx a lot
but i wonder if my steps are correct
could you please tell me the steps briefly?
Partition SD Card:
1. Use Cursor's or Amon Ra's recoveries to partition SD card.
2. When phone is off, press Home and Power buttons at the same time to start into recovery.
3. Select Partition sdcard.
4. Select Partition SD.
5. Press Home to confirm.
6. Use trackball to select minimum swap-size of 64 MB (I use 96 MB).
7. Press Home to set swap-size.
8. Press Home to set Ext-size of 512 MB. FAT32-size will be the remainder of the sd card.
9. Press Home to confirm and partition.
10. Press Home to confirm.
11. Exit.
Install ROM:
1. Download the cooked ROM
2. Save the ROM to sd card
3. Wipe data/factory reset
4. Wipe Dalvik-cache
5. Wipe SD:ext partition
6. Flash ROM
7. Reboot
8. Let the rom take its time.
9. Open AutoKiller, click Menu, select/click Presets, select/click Optimal.
10. Open SupSetup and activate JIT.
11. Open TasKiller and set SupSetup and AutoKiller to ignore (not sure if this matters, but I don't want TasKiller to shutdown these 2 apps)
12. Configure phone settings, set up accounts, sync, etc.
13. Reboot.
i cant fastboot the files to my phone...
i typed the command in cmd and it told me that it cannot be executed
nathanysh said:
i cant fastboot the files to my phone...
i typed the command in cmd and it told me that it cannot be executed
Click to expand...
Click to collapse
do you have android SDK at all ? at some folder extracted? if so , you have to either cmd to that folder and then run fastboot command, or put it in path of windows, and then you can call it from any folder...
nathanysh said:
sorry for disturbing all of you
but i really have no solution to deal with it
after flashing the rom CyanogenMod 5.0.8-final Stable/Fast 2.1
my magic reboots and it cant stop
wt happened to my phone?
please help me............
Click to expand...
Click to collapse
Reboot into recovery and wipe everything then reflash your rom.
sike89 said:
well wrong section but it will be moved.
anyway... can you boot to recovery?
if so put another rom on the sd card.( try this http://forum.xda-developers.com/showthread.php?t=654284)
follow the steps, wipe, flash and come back to here to say if it worked
good luck
Click to expand...
Click to collapse
I'll take care of it and move it to General.

[Q] I could use a hand...

okay, so im really new to this. i want to get rid of all the crap bloatware that my droid 2 comes with and i was checking out the vanilla rom. ive never installed a rom so if anyone of you could link me to a video or a complete idiot proof walkthrough for the new vanilla rom i would greatly appreciate it. im android stupid!
How about read? there are step by step instructions on the roms page, just follow them:
http://forum.xda-developers.com/showthread.php?t=823473
Angdroid said:
Install Insctructions:
Installing ROM:
This Method works for all supported devices.
It is suggested you follow all the steps even if you are coming from previous Fission ROM. If you do not want to perform all wipe steps then at least wipe system.
Pre-Installation Tasks:
You must have root. You can use our One Click Root in this THREAD.
You must have Koush's Bootstrap program for your device. Download from Market or check HERE.
Select the ROM for your device (Droid2, Droid2 WE, DroidX or Droid Pro)
Download and place ROM on SD Card
Open Bootstrap
Tap "Bootstrap Recovery"
Tap "Allow" if asked to grant SU Persmission
Tap "OK' on "Success" screen
Tap "Reboot Recovery"
You will be booted into Recovery
Use Volume up/down keys to navigate through menu. Press Camera button to Confirm selection. Power button to back up to last menu.
Create Backup - "backup and restore" then select what you want to do
Back out to main menu
Wipe Cache
Wipe Data
Mount System - Screen will read "UNMOUNT /SYSTEM" when mounted
Mount Data - Screen will read "UNMOUNT /DATA" when mounted
Back out to Manin Menu
Install Zip From SD Card
Choose Zip From SD Card
Select your ROM
Yes - Install
Wipe Cache
Wipe Data
Reboot
Back into Android
Perform a Factory Reset
Open App Draw
Tap Settings
Tap Privacy
Tap Factory Reset
Tap Reset Phone
Tap Erase Everything
Your phone will now be rebooted, perform factory reset and then reboot itself when completed.
Activate phone when prompted.
Enjoy!
Installing Updates and Add Ons:
Open Bootstrap
Tap "Bootstrap Recovery" - if you have not installed yet on new ROM
Tap "Allow" if asked to grant SU Persmission - If you have not granted it SU permission
Tap "OK' on "Success" screen - if you have not installed yet on new ROM
Tap "Reboot Recovery"
You will be booted into Recovery
Use Volume up/down keys to navigate through menu. Press Camera button to Confirm selection. Power button to back up to last menu.
Mount System - Screen will read "UNMOUNT /SYSTEM" when mounted
Back out to Manin Menu
Install Zip From SD Card
Choose Zip From SD Card
Select your Zip File
Yes - Install
Reboot
If you are installing more than one update zip then please remember to mount system before installing new file.
Click to expand...
Click to collapse
thank you sir!
steveringer08 said:
thank you sir!
Click to expand...
Click to collapse
Can I close this?
Yes, sir you may
steveringer08 said:
Yes, sir you may
Click to expand...
Click to collapse
Thanks Glad the problem was solved!

Phone not bootup

Guyz plz help me I accidentally delete build.prob file and after that my phone not bootup samsung galaxy grand logo shows and the screen goes blank nothing work. I try flashing stock firmware again but problem remain same. HELP PLZ.....!!!!
Try From Recovery Mode
sumit227 said:
Guyz plz help me I accidentally delete build.prob file and after that my phone not bootup samsung galaxy grand logo shows and the screen goes blank nothing work. I try flashing stock firmware again but problem remain same. HELP PLZ.....!!!!
Click to expand...
Click to collapse
It seems like you have root access & afcource unlock bootloader
Use custom recovery mode ex. CWM to find that file exist or not using cwm file manager link below...
http://forum.xda-developers.com/showthread.php?t=1646108
Let me know if file exist or not.... This app is free and you have full access to file system
Good Luck
I installed aroma file manager and navigate to system folder but the folder is empty.
sumit227 said:
Guyz plz help me I accidentally delete build.prob file and after that my phone not bootup samsung galaxy grand logo shows and the screen goes blank nothing work. I try flashing stock firmware again but problem remain same. HELP PLZ.....!!!!
Click to expand...
Click to collapse
sumit227 said:
I installed aroma file manager and navigate to system folder but the folder is empty.
Click to expand...
Click to collapse
The /system folder is empty because you didn't mount it in recovery.
1. Unzip and copy this build.prop to your phone's internal memory - View attachment build.zip
(This is from I9082XXUBMK3, it will work with other 4.2.2 firmware too but would display the info of K3)
2. Boot into recovery. Go to Mounts and storage>Mount /system
3. Install aroma file manager.zip
4. Go to /sdcard and copy the build.prop file
5. Go back to /system and scroll down to check if you can see all the folders now (also check if build.prop is there)
6. If build.prop is not there then paste the one you just copied
7. Select the build.prop file, go to options and select Change Permission
8. Set the following permissions:
User - Read Write
Group - Read
Others - Read​9. Exit aroma and clear cache/dalvik then reboot.
iceyhotguy said:
The /system folder is empty because you didn't mount it in recovery.
1. Unzip and copy this build.prop to your phone's internal memory - View attachment 2543835
(This is from I9082XXUBMK3, it will work with other 4.2.2 firmware too but would display the info of K3)
2. Boot into recovery. Go to Mounts and storage>Mount /system
3. Install aroma file manager.zip
4. Go to /sdcard and copy the build.prop file
5. Go back to /system and scroll down to check if you can see all the folders now (also check if build.prop is there)
6. If build.prop is not there then paste the one you just copied
7. Select the build.prop file, go to options and select Change Permission
8. Set the following permissions:
User - Read Write
Group - Read
Others - Read​9. Exit aroma and clear cache/dalvik then reboot.
Click to expand...
Click to collapse
Thanks man by pushing build.prop to system folder atleast my phone starts but after 1-2 min my phone freezes nothing works.
sumit227 said:
Thanks man by pushing build.prop to system folder atleast my phone starts but after 1-2 min my phone freezes nothing works.
Click to expand...
Click to collapse
I can't check what other system modifications you did that is making your phone misbehave.
Backup your data and try to do a clean flash. Wipe your data, cache, dalvik, then go to Mounts and storage and Format /system before flashing the firmware/ROM.
iceyhotguy said:
I can't check what other system modifications you did that is making your phone misbehave.
Backup your data and try to do a clean flash. Wipe your data, cache, dalvik, then go to Mounts and storage and Format /system before flashing the firmware/ROM.
Click to expand...
Click to collapse
After flashing stock firmware again my phone working again.
Thanks bro for helping me... :good:

[Q] how to recover data from a phone that will not boot

I have jamal2367's [AOSP] official 4.4.2 - S4 Google Edition ROM installed (final R1.2) a SGH-1337M.
The other day it started getting stuck on boot; the blue, red, yellow, green circles just continually go in and out without anything else happening. I have booted into CWM Recovery (v6.0.4.4) and done a wipe cache partition and wipe dalvik cache but it did not help.
Can anyone provide advice/steps on how to copy the data (mostly pics and WhatsApp history) off this phone? SMS history would also be nice but not necessary.
toggly said:
I have jamal2367's [AOSP] official 4.4.2 - S4 Google Edition ROM installed (final R1.2) a SGH-1337M.
The other day it started getting stuck on boot; the blue, red, yellow, green circles just continually go in and out without anything else happening. I have booted into CWM Recovery (v6.0.4.4) and done a wipe cache partition and wipe dalvik cache but it did not help.
Can anyone provide advice/steps on how to copy the data (mostly pics and WhatsApp history) off this phone? SMS history would also be nice but not necessary.
Click to expand...
Click to collapse
I would make a backup in your recovery and then flash the rom you had installed. See if that helps.
Edit: You didn't try to update. I changed my comment saying you had tried.
1. Download Aroma File Manager
2. Put a external sd into your phone.
3. Boot into the custom recovery and flash the Aroma file.
4. It will boot into a file browser and you can copy all the files from internal to your external.
ps it's possible that your custom recovery already has a filemanager build in. Then all these steps are obsolete.
I boot into AROMA Filemanager but I can't see anything on the internal SD card (see attachment).
Any ideas? Does that folder icon mean the "sdcard" folder is encrypted?
toggly said:
I boot into AROMA Filemanager but I can't see anything on the internal SD card (see attachment).
Any ideas? Does that folder icon mean the "sdcard" folder is encrypted?
Click to expand...
Click to collapse
Is it encrypted? Then probably it won't work. In that case just reflash the rom you are on without wiping.
toggly said:
Does that folder icon mean the "sdcard" folder is encrypted?
Click to expand...
Click to collapse
Lennyz1988 said:
Is it encrypted? Then probably it won't work. In that case just reflash the rom you are on without wiping.
Click to expand...
Click to collapse
I don't know, that's why I am asking what that icon means?
You say CWM is working, so you can just adb pull everything you need. Applications usually save data in a directory under /data/data or /sdcard/Android/data.
You should find the directories you want with adb shell, then you can adb pull them, then if you reflash your rom you can adb push them back into the same locations. Also, depending where they are saved, your pictures will most likely not be deleted when you reflash your rom. Better safe than sorry though.
If you don't have adb you'll have to download the binary, or you can install the entire Android SDK. Which operating system do you use?
toggly said:
I don't know, that's why I am asking what that icon means?
Click to expand...
Click to collapse
The icons means that it's symlinked. If it's not encrypted then you should find the data. It can be in an other place then where you are looking. Try looking in /data/media or some other maps in /data
Or just flash the rom you are currently on without wiping.
soldier9599 said:
You say CWM is working, so you can just adb pull everything you need. Applications usually save data in a directory under /data/data or /sdcard/Android/data.
You should find the directories you want with adb shell, then you can adb pull them, then if you reflash your rom you can adb push them back into the same locations. Also, depending where they are saved, your pictures will most likely not be deleted when you reflash your rom. Better safe than sorry though.
If you don't have adb you'll have to download the binary, or you can install the entire Android SDK. Which operating system do you use?
Click to expand...
Click to collapse
Adb won't work unless he already has authorized adb when his device was booted.
toggly said:
I boot into AROMA Filemanager but I can't see anything on the internal SD card (see attachment).
Any ideas? Does that folder icon mean the "sdcard" folder is encrypted?
Click to expand...
Click to collapse
You need to mount partitions to see the contents.. Go to Aroma File Manager Settings and check the option "Moumt automatically partition on boot".. then restart your recovery and flash again the Aroma File Manager
Lennyz1988 said:
Adb won't work unless he already has authorized adb when his device was booted.
Click to expand...
Click to collapse
I've had devices where the first thing I did with them was unlock bootloader, fastboot flash recovery, and then go into recovery and adb sideload, all without booting the system.
peppe130 said:
You need to mount partitions to see the contents.. Go to Aroma File Manager Settings and check the option "Moumt automatically partition on boot".. then restart your recovery and flash again the Aroma File Manager
Click to expand...
Click to collapse
That did the trick, thanks!!
Nothing
soldier9599 said:
I've had devices where the first thing I did with them was unlock bootloader, fastboot flash recovery, and then go into recovery and adb sideload, all without booting the system.
Click to expand...
Click to collapse
Yes and I believe that. But from version 4.2.2 android forces rsa encryption. So you need to boot into your rom and enable it. Unless the custom rom/kernel has disabled it, but I haven't seen any that have.

Dual/Multi Boot Possible on Verizon Note 4 [LP/MM]

I have looked around and haven't seen anyone mention this so I thought I would post about it since I've been using it and thought it was cool. I hope others find this useful.
The thread I'm talking about: http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211
The original thread quoted by @aukhan: http://forum.xda-developers.com/showthread.php?t=2447534
All credit goes to the original developers for this tool.
Thanks to @aukhan, @rlorange, @chenxialong, and other contributors.
Download the first .apk (Dual Boot Patcher). That is the only app that you should need to complete the process. A video guide is posted by @aukhan here: https://www.youtube.com/watch?v=h_i3GW_s-VE&spfreload=10
That is the best walkthrough I've seen.
Since it was requested, I've made a video walkthrough of this process: https://youtu.be/5VzYED1hhUA
Basically you patch all of the .zip files that you would have flashed normally and then you flash them to a new ROM slot. If there are more questions that the video doesn't answer I'll be happy to answer them or post a better walkthrough if needed.
It should be noted that to switch back and forth you'll need to install the Dual Boot Patcher apk on both ROMs. This does not affect TWRP Recovery.
I have run this with JasmineROM as the primary and CM13 as the secondary as well as CM13 as primary and JasmineROM as Secondary. I currently have this set-up to try different ROMs without needing to completely wipe my phone and deal with backups/restores. I also use it to use CM13 as my primary while having stock options (S-Pen, Car BT, and other Samsung stuff) available in a quick reboot.
Edit:
More Specific Instructions:
1) Download all .zip files that you would flash if you were going to flash the ROM normally (ex. CM13, Gapps, SuperSu, XPosed, datafixes, kernels, etc)
2) Download the Dual Boot Patcher apk: https://snapshots.noobdev.io/ and install it on your phone
3) Open ES File Explorer or another Root Explorer app and navigate to /sdcard/MultiBoot
4) Create a folder labeled "dual" in that directory (now there is a folder /sdcard/MultiBoot/dual)
5) Open Dual Boot Patcher app and tap the three lines in the upper left then select "Patch Zip File"
6) Tap the plus button and find each of the .zip files that you will be flashing. After selecting one make sure to change "Partition Configuration" to "Secondary"
7) A file browser will now open. Navigate to /sdcard/MultiBoot/dual and save the patched zip file there.
8) You may now repeat steps 6 and 7 to add the rest of the zip files
9) Tap the check mark in the upper right to "Patch" all of the .zip files
10) Tap the three lines in the upper left again and select ROMs
11) Tap the phone icon in the lower right and push okay
12) Tap the plus button in the lower right and navigate to the /sdcard/MultiBoot/dual folder. Select the main ROM (CM13, Kyubi, JasmineROM, etc) and tap "keep location"
13) Repeat step 12 until all zips are added in the order you want them flashed (the order is important). If you mess up swipe the one that's wrong to the right to remove it from the list
14) Tap the check mark in the upper right. A console should appear and it should virtually flash the ROM as you would expect in TWRP
15) Once it says "x/x completed" in cyan text and it has stopped you can just tap the back arrow in the upper left
16) If you go back to the ROMs page there should now be a "Secondary" ROM. To test it out you'll need to select it and then reboot the phone.
17) Once it has booted and you are past the setup you'll need to enable "unknown sources" in the menu and install Dual Boot Patcher. Once it's installed, open it. It should find the two ROMs and you'll be able to select Primary from the ROMs menu and reboot back
Edit 2:
This process can be done using any of the partition configurations listed when patching a Zip file. Secondary and Multi Slots go to the System partition, data slot goes to internal storage, and Extsd slot goes to the External SD card. I recommend not using the Multi Slots since more than two ROMs is a lot on the system partition.
If you have problems make sure to set the kernel and update the ramdisk before flashing and that the files are in the right folder typed exactly as it says in the prompt when patching the file.
I have noticed many problems when using a non-Touchwiz ROM as stock and trying to dual boot to a Touchwiz ROM. I have had bootloop situations when trying to dual boot to Kyubi or PaulPizz from CM13, but with PaulPizz as primary I have no issues switching back and forth.
In the event of a bootloop you can recover your primary ROM by entering TWRP, tapping install, selecting image in the bottom right corner, navigating to the /sdcard/MultiBoot/primary folder, and selecting the "boot.img" file. This will return your phone back to the primary ROM.
Edit 3: Video Tutorial: https://youtu.be/5VzYED1hhUA
If it is too blurry I can make another one, but I think you can see what you need to just fine. I hope it helps. I also forgot to mention that if you later want to flash anything to the ROM that you're "dual booting" into then all you have to do is patch the zip files and flash them like before except you're flashing to a slot that already has a ROM now.
Edit 4: I have now tested this on Marshmallow with success. I still recommend using a Touchwiz ROM as primary and you'll need to have a kernel that's permissive. I'm using Emotion, but I think Oscar's kernel should work as well. I have PaulPizzRom.VRU2CPF3.r-2 installed as primary with the CPF3 modem and Emotion kernel and CM13 as secondary (pretty much my daily driver at this point). Everything has been working so far.
Isn't there a kernel patch requirement for this to work?
Just tried it and working great for me. Jasmine primary, cm13 secondary. Definitely easier than messing with twrp to test roms. Thanks for the info!
jal3223 said:
Isn't there a kernel patch requirement for this to work?
Click to expand...
Click to collapse
I didn't need one to get this to work. You may be thinking of Multisystem, which is different and requires both ROMs to run the same kernel.
As far as I can tell this method boots each ROM with its own kernel. CM13 and JasmineROM both use a version of the Multisystem kernel, but I just checked and they are running different kernels.
I'll probably try the PaulPizz or Kyubi ROMs since I've been having some freeze issues with JasmineROM and see if the others work just as well.
shadeau said:
I didn't need one to get this to work. You may be thinking of Multisystem, which is different and requires both ROMs to run the same kernel.
As far as I can tell this method boots each ROM with its own kernel. CM13 and JasmineROM both use a version of the Multisystem kernel, but I just checked and they are running different kernels.
I'll probably try the PaulPizz or Kyubi ROMs since I've been having some freeze issues with JasmineROM and see if the others work just as well.
Click to expand...
Click to collapse
Awesome, thanks! I'm definitely going to give it a try.
I cannot seem to get it to recognize the path with the patched ROM file. none of the storage paths on my device show as "sdcard", they are either sdcard0 or ExtSdCard.
Even though the folder structure is created on the Internal storage, the DualBoot app does not recognize it.
EDIT: Nevermind, I realized I do not need that app. I just patched the ROM and then added it in the Patcher app mentioned above. The added the patched ROM to it and it shows up in the ROMs menu
EDIT2: This is just not working, I try and apply the ROM for dual boot/swap, however it fails to complete the configuration. I am on a rooted stock phone..could that be the issue?
jal3223 said:
Awesome, thanks! I'm definitely going to give it a try.
Click to expand...
Click to collapse
I just wanted to give an update and say I tried Kyubi ROM the other day and got it to boot just fine. I had one time where I needed to pull the battery, but then it rebooted to Kyubi and ran normally. I don't know if that was just bad luck or something else. I'm planning on trying PaulPizz's ROM today.
ssb13 said:
I cannot seem to get it to recognize the path with the patched ROM file. none of the storage paths on my device show as "sdcard", they are either sdcard0 or ExtSdCard.
Even though the folder structure is created on the Internal storage, the DualBoot app does not recognize it.
EDIT: Nevermind, I realized I do not need that app. I just patched the ROM and then added it in the Patcher app mentioned above. The added the patched ROM to it and it shows up in the ROMs menu
EDIT2: This is just not working, I try and apply the ROM for dual boot/swap, however it fails to complete the configuration. I am on a rooted stock phone..could that be the issue?
Click to expand...
Click to collapse
I added some better instructions in the OP. Can you tell me what step you're having problems with? JasmineROM is pretty close to stock so I assumed this would work just as well on the PaulPizz or stock ROM, but I personally haven't tried on either yet.
shadeau said:
I just wanted to give an update and say I tried Kyubi ROM the other day and got it to boot just fine. I had one time where I needed to pull the battery, but then it rebooted to Kyubi and ran normally. I don't know if that was just bad luck or something else. I'm planning on trying PaulPizz's ROM today.
I added some better instructions in the OP. Can you tell me what step you're having problems with? JasmineROM is pretty close to stock so I assumed this would work just as well on the PaulPizz or stock ROM, but I personally haven't tried on either yet.
Click to expand...
Click to collapse
I'll give it a try with the more specific steps. I think part of my issue was all the videos and other walk-throughs are with older versions of the software. I was also trying to use the other Dual Boot app that is in the other posts....that is where I had the path name issue.
I was finally able to get CM13 on the list of ROMs, however it would fail to switch to it....but that was using the Win32 app to patch it. I'll try it all with the phone app.
ssb13 said:
I'll give it a try with the more specific steps. I think part of my issue was all the videos and other walk-throughs are with older versions of the software. I was also trying to use the other Dual Boot app that is in the other posts....that is where I had the path name issue.
I was finally able to get CM13 on the list of ROMs, however it would fail to switch to it....but that was using the Win32 app to patch it. I'll try it all with the phone app.
Click to expand...
Click to collapse
I followed it to the T and here was my result...(screenshot attached)
EDIT: Added log file. Seems like perhaps it is either permissions, path, and or space issues.
ssb13 said:
I followed it to the T and here was my result...(screenshot attached)
EDIT: Added log file. Seems like perhaps it is either permissions, path, and or space issues.
Click to expand...
Click to collapse
I'll have to look at it tomorrow when I have time. You said you were on stock. What exactly are you running on your phone? What are the firmware version and the kernel? Also, how much free space is on your internal storage and are you using an SD card?
shadeau said:
I'll have to look at it tomorrow when I have time. You said you were on stock. What exactly are you running on your phone? What are the firmware version and the kernel? Also, how much free space is on your internal storage and are you using an SD card?
Click to expand...
Click to collapse
14gb free. About 40gb free on SD card.
Stock 5.1.1 bpa1.
Xceed kernel
Sent from my SM-N910V using Tapatalk
ssb13 said:
14gb free. About 40gb free on SD card.
Stock 5.1.1 bpa1.
Xceed kernel View attachment 3739482
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Try deleting all of the patched zip files and starting over. In the ROMs menu tap the three dots on the primary ROM and scroll down to the bottom. Update the ramdisk and set the kernel then reboot. Make a new folder in the sdcard/MultiBoot folder labeled "data-slot-1" all lowercase. Patch your .zip files and instead of selecting secondary select "Data Slot" and when it asks you what slot name, type "1". After tapping continue, navigate to the sdcard/MultiBoot/data-slot-1 folder and save the .zip files there. After the first time you should be able to select "1 (Data Slot)" for partition configuration instead of manually assigning one for subsequent .zips. Once you're done patching the files go back to the ROMs page and add a ROM then the .zips (selecting keep location like before) and see if that works.
The dual slot saves all ROM data to your system partition which could be pretty full even if your internal storage shows plenty of space. Since all apps are still on the system partition regardless of which slot you pick it may be good to look at how much free space is left before flashing. You can see how much space is left by tapping "Free Space" underneath the "Patch Zip File" button. The /system directory is your system partition.
shadeau said:
Try deleting all of the patched zip files and starting over. In the ROMs menu tap the three dots on the primary ROM and scroll down to the bottom. Update the ramdisk and set the kernel then reboot. Make a new folder in the sdcard/MultiBoot folder labeled "data-slot-1" all lowercase. Patch your .zip files and instead of selecting secondary select "Data Slot" and when it asks you what slot name, type "1". After tapping continue, navigate to the sdcard/MultiBoot/data-slot-1 folder and save the .zip files there. After the first time you should be able to select "1 (Data Slot)" for partition configuration instead of manually assigning one for subsequent .zips. Once you're done patching the files go back to the ROMs page and add a ROM then the .zips (selecting keep location like before) and see if that works.
The dual slot saves all ROM data to your system partition which could be pretty full even if your internal storage shows plenty of space. Since all apps are still on the system partition regardless of which slot you pick it may be good to look at how much free space is left before flashing. You can see how much space is left by tapping "Free Space" underneath the "Patch Zip File" button. The /system directory is your system partition.
Click to expand...
Click to collapse
Thank, I will try this method. I did check and the /raw/system partition is full. Should it be?
ssb13 said:
Thank, I will try this method. I did check and the /raw/system partition is full. Should it be?
Click to expand...
Click to collapse
My system partition says "Total size: 3.94 GiB, Free: 569.43 MiB" and that's with CM13 on Primary and PaulPizz on Secondary with Kyubi on data-slot-1. I haven't booted Kyubi yet so that may decrease my free space even further, but if your system partition is already full I don't think you'll be able to flash anything. You might try looking for big files in the /system directory. Also check to see if there are any files in /system/multiboot/dual and delete them. Do you have a lot of apps installed?
shadeau said:
My system partition says "Total size: 3.94 GiB, Free: 569.43 MiB" and that's with CM13 on Primary and PaulPizz on Secondary with Kyubi on data-slot-1. I haven't booted Kyubi yet so that may decrease my free space even further, but if your system partition is already full I don't think you'll be able to flash anything. You might try looking for big files in the /system directory. Also check to see if there are any files in /system/multiboot/dual and delete them. Do you have a lot of apps installed?
Click to expand...
Click to collapse
Mine says 56K free. Maybe I should revert to my nandroid which is pre-dualboot attempts and see. However I am on stock , rooted. Not even ROM, just the a rooted converter retail to DE. So perhaps the stock uses more system space.
ssb13 said:
Mine says 56K free. Maybe I should revert to my nandroid which is pre-dualboot attempts and see. However I am on stock , rooted. Not even ROM, just the a rooted converter retail to DE. So perhaps the stock uses more system space.
Click to expand...
Click to collapse
That might be a good option. If I tap the three dots for each of my ROMs the PaulPizz (essentially stock) lists a system size of 2.09 GiB, which is half the size of the system partition. You might want to check yours and see what it lists as the system size.
You might also just try using the data-slot-1 and see if it works before the nandroid revert.
shadeau said:
That might be a good option. If I tap the three dots for each of my ROMs the PaulPizz (essentially stock) lists a system size of 2.09 GiB, which is half the size of the system partition. You might want to check yours and see what it lists as the system size.
You might also just try using the data-slot-1 and see if it works before the nandroid revert.
Click to expand...
Click to collapse
Using data-slot-1 I received an exit code of 0 and a 2/2 completed!!!
I cannot reboot now because I am waiting for a phone call, but when I do I'll report in. :highfive:
ssb13 said:
Using data-slot-1 I received an exit code of 0 and a 2/2 completed!!!
I cannot reboot now because I am waiting for a phone call, but when I do I'll report in. :highfive:
Click to expand...
Click to collapse
So that did work. Now I have a follow up question. Say I flash a ROM, like CM13 and GAPPS...but when I boot a bunch of apps keep FC'ing and they keep relaunching, like the SetupWizard...basically I'm stuck clicking OK on all the messsages and they just keep coming back.
My question...am I stuck? How can I flip back to booting to my primary ROM? can I delete the files from the data-slot-1 folder? Any thoughts?
ssb13 said:
So that did work. Now I have a follow up question. Say I flash a ROM, like CM13 and GAPPS...but when I boot a bunch of apps keep FC'ing and they keep relaunching, like the SetupWizard...basically I'm stuck clicking OK on all the messsages and they just keep coming back.
My question...am I stuck? How can I flip back to booting to my primary ROM? can I delete the files from the data-slot-1 folder? Any thoughts?
Click to expand...
Click to collapse
It's actually pretty easy to revert back with TWRP. I was going to add this to the OP when I had time: Boot to recovery and tap install, then select image in the bottom right and navigate to /system/MultiBoot/Primary and select the boot.img, then flash it to the boot partition. That will let you boot to the primary ROM.
shadeau said:
It's actually pretty easy to revert back with TWRP. I was going to add this to the OP when I had time: Boot to recovery and tap install, then select image in the bottom right and navigate to /system/MultiBoot/Primary and select the boot.img, then flash it to the boot partition. That will let you boot to the primary ROM.
Click to expand...
Click to collapse
Thanks.

Categories

Resources