Database Users

TWRP flashing issue error code 70

Hey guys i've just done full wipe and succesfuly flashed ROM but I can't flash gapps. Everytime it says : "Insufficient storage space available in System partition (blabla)" . I have about 12gb left so the free space isn't an issue I think.

System partition is not the main storage area.
I think you can check either through TWrp or through Drives application what consumes the space of system partition.

RASTAVIPER said:
System partition is not the main storage area.
I think you can check either through TWrp or through Drives application what consumes the space of system partition.
Click to expand...
Click to collapse
I am having same issue.
But I have flashed only the rom.
/system
/Data
/Cache
all were formatted before. I am still getting the same issue.

xeltos said:
I am having same issue.
But I have flashed only the rom.
/system
/Data
/Cache
all were formatted before. I am still getting the same issue.
Click to expand...
Click to collapse
If you are trying to flash Stock package of PA Gapps the size is 437MB.
Your system partition is too small. It will not fit.
Try flashing the smaller Full Modular(366MB), Mini Modular(~232MB) or Micro Modular(~182MB) Gaaps
{
"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"
}
You can then install any missing Google apps you desire from Google Play . They will be installed as user apps instead of system apps.

I did this:
1. Install newest TWRP app
2. Download CM-12.1-20151101-UNOFFICIAL-maguro.zip (or newer) to your device
3. Download open_gapps-arm-5.1-pico-20151104.zip (or newer) to your device
4. Run TWRP
5. Wipe and factory reset
6. Install CM-12.1-20151101-UNOFFICIAL-maguro.zip
7. Install open_gapps-arm-5.1-pico-20151104.zip
8. Reboot
Voila

the reason for that you trying to install all Gaps package which is not possible for your device according to space calculation
To fix this problem do these steps
1-create text file and name it ( gaps-config)
2-add these lines
Exclude Books
Exclude Chrome
Exclude CloudPrint
Exclude Docs
Exclude Earth
Exclude ExchangeGoogle
Exclude Slides
Exclude Sheets
Exclude NewsWidget
Exclude PlayGames
Exclude Keep
Exclude Hangouts
Exclude Fitness
then save the text file in the same gaps.zip file directory
3-now flash the gaps and done..
note you can exclude more aps or include other as you want as long as you had the space requirements .
i just downloaded only one Gaps package which is the full package , and then i customize which app to include or exclude and here is my review related to this error ( skip to 13 minute )

[Stock][SGP312][5.1.1][PreRooted]10.7.A.0.222 VMo_AR

Model : SGP312
Android: 5.1.1
Market: Argentina
Build : 1273-3687_10.7.A.0.222_R2E
Included:
- UPDATE-SuperSU-v2.46.zip
- TabZ-lockeddualrecovery2.21.flashable.zip from @Nut with fix for /system not mounted in recovery
Installation (you must be on rooted rom with custom recovery installed)
- Make an nandroid backup
- Wipe cache and dalvik cache
- Flash this zip from recovery and you're done
Download :
https://mega.nz/#!dFN2lIyA!gLb6wy4pdTluYyMNwMQFyK6NS5myauzZiOmcpI-hKHA
Edit :
- Unable to mount /system with TWRP /CWM after upgrading to 5.1.1 ..... until some dev fixed it (Nut is informed of the issue), use this terminal command in TWRP before flashing any zip :
mount -rw /system
Edit2 : new zip uploaded with fixed recovery ( /system is mounted now, nandroid backup/restore and flashing zip are working fine)

Screenshot :
{
"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"
}

Stagefright vulnerability is not fully fixed

I keep getting "unfortunately phone has stopped" I click "OK" 2 seconds later, error returns. Have I flashed the wrong version?

I have the 32gb wifi version, which I believe is the SGP312 model. Any ideas why I might be getting the "phone" error?
Thanks in advance.

Rassilon7 said:
I have the 32gb wifi version, which I believe is the SGP312 model. Any ideas why I might be getting the "phone" error?
Thanks in advance.
Click to expand...
Click to collapse
did u wipe cache and davilk cache ?

Yes, both were wiped. I was coming from 4.4.4, do you think that could affect?

Rassilon7 said:
Yes, both were wiped. I was coming from 4.4.4, do you think that could affect?
Click to expand...
Click to collapse
Hi, try do do a wull wipe then and if its still not working, try to install 5.02 build first

New prerooted zip uploaded with fixed recovery.

I dirty flashed this over 5.0.2 wiping cache only and all is fine. Also updated xposed to 5.1.1 version. Thanks a lot!

Ok

dr_derqami said:
And I have twrp problem like your previous build. Could you kindly tell or provide us the fix for it? Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=62728367&postcount=6203

ibis69 said:
Model : SGP312
Android: 5.1.1
Market: Argentina
Build : 1273-3687_10.7.A.0.222_R2E
Included:
- UPDATE-SuperSU-v2.46.zip
- TabZ-lockeddualrecovery2.21.flashable.zip from @Nut with fix for /system not mounted in recovery
*** CUT ***
Edit2 : new zip uploaded with fixed recovery ( /system is mounted now, nandroid backup/restore and flashing zip are working fine)
Click to expand...
Click to collapse
Big thanks for this, ibis!
I only installed it today, so I'm a bit late to the game hehe.
I dirty flashed it over stock KK and I had no problems at all.
You did a great job, and I wish I could thank you more for it - I'm going to hit "Thanks" on all of your posts

rooted z3c "secure" wipe /data before sending in reapir

Hi I finally decided to send my z3c D5803 in for repair.
I want to remove any sensitive data from the device.
It runs on rooted Android 5.1.1 and has TWRP 2.8.7.0 installed. Over the time I installed a lot of xposed modules and tweaked a lot of settings. So I really want to keep my exact system image.
I have several Questions for every step:
1. Which partitions should I backup
{
"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"
}
According to What should I back up in TWRP?
`The default backup options in TWRP are system, data, and boot`
1.1 Is `Kernel Image` the same as boot ?
1.2. I just go with the defualt settings ?
2. My first simple idea was to remove the external SDcard after the backup from step 1 and perform a "factory reset" using TWRP:
2.1 root and TWRP is preserved ?
3. When the phone is back from repair I just boot in recovery and recover only the /data partition from the inserted SDcard ?
3.1
Is wiping /data enough to remove all sensitive data ( password manager app) [ SdCard removed of course ] ?
What about XPOSED Modules that maybe contain sensitive data ?
4. I guess the TWRP factory reset does not secure erase data ?
4.1 Does anyone know the method that TWRP uses to remove the data from the /data partition?
-> I read about encrypt the phone but a lot of discussions say that you have to unroot before and I guess this would destroy my whole plan of just erasing the /data partition ?
4.1 Does anybody know and tested method to add a additional layer of security.
I found this:
Normal erasing via TWRP should be enough. But if you want to erase all of your data on the phone then you need to execute the TRIM command on your flash storage.
You can do this on TWRP by following the steps:
– Mount the /system partition
– Go to Advanced and then Terminal Command
– Execute the command to TRIM /system partition:
fstrim -v /system
– Execute the command to TRIM /data partition:
fstrim -v /data
– Execute the command to TRIM /cache partition:
fstrim -v /cache
When you delete data from your storage, the actual data is not cleaned but the link to the internal blocks (where the actual data is stored) is made as invalid or the block is made as dirty.
TRIM command is designed specifically for flash storage. When you execute TRIM command on flash storage, it cleans all the data of all the blocks.
NOTE:
But you need to be careful, as the TRIM actually erases block by block and flash storage has limited erase and write cycles.
Click to expand...
Click to collapse

Well personally it doesn't really matter but backup Data,System and Boot(kernel image) and if you really want to remove everything transfer pictures to your computer and wipe internal storage
And when you backup everything will be kept and when you wipe everything will be wiped including password managers and etc,and when you restore it back everything will be as you left it with everything on your device as before.

E:Failed to clear BCB message

After I tried to install custom rom. I got this message.
Supprted API: 3
E:Failed to clear BCB message: failed to open /dev/block/bootdevice/by-name/misc: No such file or directory
Can someone help me?

beam2546 said:
After I tried to install custom rom. I got this message.
Supprted API: 3
E:Failed to clear BCB message: failed to open /dev/block/bootdevice/by-name/misc: No such file or directory
Can someone help me?
Click to expand...
Click to collapse
sounds like it needs a factory restore (partition layout broken?) via QPST and the latest fastboot image.
fastboot boot twrp.img and copy all your valuable data first.
edit: you could try
Code:
fastboot flash misc tissot_images_V9.6.4.0.ODHMIFE_8.0\images\misc.img
first. though not sure if it works. "No such file or directory" usually means the partition is gone.

meltbanana said:
sounds like it needs a factory restore (partition layout broken?) via QPST and the latest fastboot image.
fastboot boot twrp.img and copy all your valuable data first.
edit: you could try
Code:
fastboot flash misc tissot_images_V9.6.4.0.ODHMIFE_8.0\images\misc.img
first. though not sure if it works. "No such file or directory" usually means the partition is gone.
Click to expand...
Click to collapse
This solution worked for me. worth a try. Thx!:good::good::good:

This solution worked for me. worth a try. Thx!
Can you tell me the step bro,please:good:

beam2546 said:
After I tried to install custom rom. I got this message.
Supprted API: 3
E:Failed to clear BCB message: failed to open /dev/block/bootdevice/by-name/misc: No such file or directory
Can someone help me?
Click to expand...
Click to collapse
mrniceash said:
This solution worked for me. worth a try. Thx!:good::good::good:
Click to expand...
Click to collapse
please tell me the step bro

meltbanana said:
sounds like it needs a factory restore (partition layout broken?) via QPST and the latest fastboot image.
fastboot boot twrp.img and copy all your valuable data first.
edit: you could try
Code:
fastboot flash misc tissot_images_V9.6.4.0.ODHMIFE_8.0\images\misc.img
first. though not sure if it works. "No such file or directory" usually means the partition is gone.
Click to expand...
Click to collapse
{
"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"
}

[GUIDE] System partition too small? Installing Android 12, GApps & large GSIs on Pixel 2!

SPECIAL THANKS TO
@Lunarixus on XDA
I wouldn't have figured out how to maneuver the pixel 2 XL partition table without him.​
!!!WARNING PLEASE READ!!!!
This tutorial only applies to Walleye (regular 2). There's another tutorial for Taimen (2 XL). Please join the telegram group if you can! ​Google Pixel Development Group.​​ALSO, this only increases system partition on slot B. If you want to flash GSIs, make sure you are on the correct slot with this command:​​fastboot --set-active=b​​REQUIREMENTS:
Walleye with unlocked bootloader.
Updated adb & fastboot binaries.
GNU parted for ARM64. Get it here: https://guidedflame.dev/parted
Custom recovery for Walleye with adb support.
STEPS:
1. Enable USB Debugging​
2. Reboot into fastboot mode​adb reboot bootloader​
3. Boot into the recovery (format data if it is stuck on splash screen)​fastboot boot path/to/recovery.img ​(optional) you can flash TWRP permanently if you wish. fastboot flash boot_a path/to/recovery.img and fastboot flash boot_b path/to/recovery.img DO NOT FLASH TWRP. JUST BOOT TO IT.​
4. In TWRP...​
If it asks you to decrypt your data, do it.
If it asks you to swipe for RW permissions on system partition, do it.
Unmount all partitions. Click on Mount, then un-tick everything.
5. Back to your PC. Copy parted to /sbin.​adb push path/to/parted /sbin​
6. Enter shell mode.​adb shell​
7. Change permissions of parted.​chmod 777 /sbin/parted​
8. It's time to use parted!​​We mainly use 3 commands. Here's how they work.​
rm x - Removes partition number x. For example: rm 13
Click to expand...
Click to collapse
mkpart name fstype startUNIT finishUNIT - Makes a partition where fstype is the type of filesystem (like ext4), start is the beginning of the partition, and finish is the end of the partition. UNIT is the unit for the start and finish arguments (like KB, MB, B, or s) For example: mkpart system_a ext4 32KB 1000KB
Click to expand...
Click to collapse
name x part_name - Names partition number x and gives it part_name as a label. For example: name 14 userdata
Click to expand...
Click to collapse
In your terminal (still in shell mode), type parted /dev/block/sda
It should greet you with a welcome screen. Type p free, and save what you get in a screenshot or text file (on windows you can copy and paste in notepad, or use Snipping Tool, since it's installed by default). THIS IS VERY IMPORTANT IF YOU GET STUCK!!!!
{
"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"
}
​
We have to delete all partitions starting from the bottom until system_b. Make sure to keep the screenshot or text file you saved earlier from p free, because we are gonna need it to recreate the deleted partitions later. YOUR PARTITION SCHEME MIGHT BE DIFFERENT THAN THIS. Make sure to STOP after system_b is removed.
rm 45
rm 44
rm 43
Once you are done, it's time to recreate those partitions. We do it in the proper order now, starting from system_b. Refer to the screenshot or text file you saved earlier. We will increase the partition size to 3GB to be able to boot most GSIs, including Android 12. If it says that the partition isn't aligned, type Ignore.
mkpart system_b ext2 4073MB 7173MB
mkpart padding1 7173MB 7179MB
mkpart userdata ext4 7179MB 62400MB (if you have 128GB Walleye, do mkpart userdata ext4 7179MB 126300MB)
Check your partitioning with p free and compare with your screenshot/text file. It should be similar, with some extra free spaces.
Time to name the partitions.
name 43 system_b
name 44 padding1
name 45 userdata
Check your partitioning again with p free. It should show the named partitions. If everything looks good to you, leave parted.
quit
9. Exit shell mode.
exit​
10. Reboot into fastboot mode
adb reboot bootloader​
11. Format all the partitions we made
fastboot erase system_b​fastboot erase padding1​fastboot erase userdata​fastboot format:ext2 system_b​fastboot format:ext4 userdata​​And that's all!
NOTICE: At this point, the partitions should repopulate themselves on the next boot. If they don't, flash latest Android 11 stock ROM (And flash it using flash-all.bat for windows/flash-all.sh for linux).
Flashing the stock ROM won't undo your partitioning. You will keep your 3GB system partition!
Click to expand...
Click to collapse
You can start immediately flashing GSIs/Android 12. If you're stuck on splash screen, that means the partitions didn't repopulate correctly. Follow the advice above!
If you have any questions, or accidentally brick your device, join the telegram group for direct support, or ask here in the XDA thread.

Thanks for your help on the Telegram group man. I just skipped Step 11 and did fastboot -w so I completed the process without any errors.

always type wrong,so crazy its code,