Database Users

[HOWTO] Remove Journaling from EXT4 Partitions

Hello Community!
First off, the original thread - http://forum.xda-developers.com/showthread.php?t=851407
I wanted to bring this to everyone's attention. I have seen many requests for converting all partitions to EXT2 as it is faster than EXT4. So far the only way to do this is with Z4 modded kernels. Well Hardcore over in the i9000 forums (<3 their development section) posted a method a achieve the next best thing - EXT4 with no journaling! I have yet to test this out, but I will be doing so tonight and posting results. I plan on trying this with ULF (which has been confirmed to work) and ttabbal's all EXT4 Dragon Rom (TW Beta Section). The process just simply removes journaling from EXT4 partitions, so it's as fast or faster than EXT2 but with all the added benefits of being EXT4.
Thought some people might find this useful... enjoy!
Update - I can confirm this works with ULF. I was able to remove journaling from all three partitions no problem following the instructions below. I had no data loss or FC's upon reboot. Below are Hardcore's instructions from the original thread - link posted at the top. I in no way helped in this, just merely sharing what I found. All props go to Hardcore.
hardcore said:
WARNING: This procedure is risky and may result in loss of data.
This is a follow up to findings made in this thread: http://forum.xda-developers.com/showthread.php?t=819580
Many people have been asking for an ext2 lagfix. You can get something similar but (arguably) better: ext4 with no journaling. Ext4 no-journal performs as fast or faster than ext2 because of performance improvements made in ext4.
Quadrant comparison for ext4 /data-only lagfix:
ext4 scores about 1500, ext4 no-journal scores about 1650.
This should work with existing kernels that support ext4 lagfixes. It's tested on a ULFK kernel (SpeedMod).
WARNING: Turning off journaling makes your data more susceptible to getting corrupted, although the risk is small.
Disclaimer: No promises that this will work for you, or that it won't corrupt your data. Try this at your own risk.
Step 0: You start off by applying an ext4 lagfix. If you are already using an ext4 lagfix, you can skip this step.
For ULFK kernels, this is either:
- "Voodoo" ext4 /data
- No-RFS advanced ext4
After the lagfix has been successfully applied and your phone is up and running properly, then you can proceed to convert the ext4 partitions.
Step 1: Make a backup of your data, using CWM (recommended). If anything goes wrong, you can restore the backup later.
Step 2: Download the tune2fs file attached to this post (works for FROYO roms only), and copy it to /data as /data/tune2fs:
adb push tune2fs /sdcard/
adb shell
# su
# cp /sdcard/tune2fs /data/
Procedure if your kernel has ro.debuggable enabled:
Step 3: If your kernel has ro.debuggable enabled, then boot your phone into recovery mode. Then run adb in root mode:
adb root
(wait for adbd to restart)
adb shell
Copy tune2fs to the /tmp folder.
# cp /data/tune2fs /tmp/
If you don't have ro.debuggable enabled, "adb root" will give you an error. Go to Step 3A in the next section.
Step 4: Now in ADB shell, find out which partitions are ext4:
# mount | grep ext4
mount | grep ext4
/dev/block/mmcblk0p2 on /data type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
/dev/block/stl10 on /dbdata type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
/dev/block/stl11 on /cache type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
In this example, the 3 partitions are:
/dev/block/mmcblk0p2 (/data)
/dev/block/stl10 (/dbdata)
/dev/block/stl11 (/cache)
Repeat Steps 5 to 9 for every partition you want to remove the journal from.
The next steps show the procedure for /dev/block/mmcblk0p2 (/data).
Step 5: Unmount the partition:
umount partition_mount_point
for example:
# umount /data
Step 6: Check if there is a journal:
# /tmp/tune2fs -l /dev/block/mmcblk0p2 | grep features
You should see something like this:
Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
You should see "has_journal" in the features. It means this partition has a journal.
Step 7: Fsck the partition:
# e2fsck -f /dev/block/mmcblk0p2
Step 8: Remove the journal:
# /tmp/tune2fs -O ^has_journal /dev/block/mmcblk0p2
(this is a capital "O"!)
Step 9: Check if the journal was removed:
# /tmp/tune2fs -l /dev/block/mmcblk0p2 | grep features
You should see something like this:
Filesystem features: ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
You should see "has_journal" is NOT there.
Done for this partition.
Step 10: After you've remove the journal from all the partitions you wanted to, shutdown the phone by pressing the power button.
DONE. You only need to do this procedure once and it'll "stick" until the next time you re-format the partition.
--------------------------------------------------
Procedure if you don't have ro.debuggable enabled:
Step 3A: If you kernel does not have ro.debuggable enabled, then you can try doing this using normal adb with su while the phone is running. But this is much more risky.
To lower the risk, do this right after booting, wait for the Media Scan to complete.
adb shell
# su
Step 4A: Now in ADB shell, find out which partitions are ext4:
# mount | grep ext4
mount | grep ext4
/dev/block/mmcblk0p2 on /data type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
/dev/block/stl10 on /dbdata type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
/dev/block/stl11 on /cache type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
In this example, the 3 partitions are:
/dev/block/mmcblk0p2 (/data)
/dev/block/stl10 (/dbdata)
/dev/block/stl11 (/cache)
Repeat Steps 5A to 8A for every partition you want to remove the journal from.
The next steps show the procedure for /dev/block/mmcblk0p2 (/data).
Step 5A: Check if there is a journal:
# /data/tune2fs -l /dev/block/mmcblk0p2 | grep features
You should see something like this:
Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
You should see "has_journal" in the features. It means this partition has a journal.
Step 6A: Fsck the partition:
# e2fsck -f /dev/block/mmcblk0p2
WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.
Do you really want to continue (y/n)?
Answer yes.
Step 7A: Remove the journal:
# /data/tune2fs -O ^has_journal /dev/block/mmcblk0p2
(this is a capital "O"!)
Step 8A: Check if the journal was removed:
# /data/tune2fs -l /dev/block/mmcblk0p2 | grep features
You should see something like this:
Filesystem features: ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
You should see "has_journal" is NOT there.
Done for this partition.
Step 9A: After you've remove the journal from all the partitions you wanted to, shutdown the phone by pressing the power button. Reboot the phone and hope everything works.
DONE. You only need to do this procedure once and it'll "stick" until the next time you re-format the partition.
Click to expand...
Click to collapse

This is a lagfix for a lagfix? A metalagfix?
Sent from my SGH-T959 using XDA App

Super saiyan lagfix

grennis said:
This is a lagfix for a lagfix? A metalagfix?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
This simply takes an existing ext4 lagfix and optimizes performance at the slight expense of reliability.

I'm more interested in this magical dragron rom you speak of. I cant seem to find it. Do you have a link?

wildklymr said:
I'm more interested in this magical dragron rom you speak of. I cant seem to find it. Do you have a link?
Click to expand...
Click to collapse
It's listed in the donators section of ~tw~'s forums.

This really sounds like a great idea. Is there any way you, or a dev could possibly turn the whole process into a CWM flashable .zip?

This is probably the best thing that's happened to my phone... Its flying...!!!

How good is this one compared to JFS overkill?

Idk, that seems like a lot of work for someone who's lazy like myself

djquick said:
Idk, that seems like a lot of work for someone who's lazy like myself
Click to expand...
Click to collapse
no it's not that much work and I'm a total newbie... ran into some newbie minor issues (kept typing 'unmount' instead of 'umount' lol and had to use chmod on the file tune2fs) but otherwise quite painless...
and now onto testing it for the day or two until the next rom release ...

djquick said:
Idk, that seems like a lot of work for someone who's lazy like myself
Click to expand...
Click to collapse
Sonnislav said:
no it's not that much work and I'm a total newbie... ran into some newbie minor issues (kept typing 'unmount' instead of 'umount' lol and had to use chmod on the file tune2fs) but otherwise quite painless...
and now onto testing it for the day or two until the next rom release ...
Click to expand...
Click to collapse
It looks like a lot of work but in actuality is quite simple. Many of the steps are just verification steps so you can see that it worked. Been rocking this for 2 full days and I must say the improvement is quite noticeable.
Bignjuicyjc said:
This really sounds like a great idea. Is there any way you, or a dev could possibly turn the whole process into a CWM flashable .zip?
Click to expand...
Click to collapse
I would love to pack this into a zip for everyone, but I'm afraid I don't have much technical "know-how" when it comes to stuff like that. Maybe if this peaks some interest one of these more bonafied devs could provide that for everyone.

So, After doing some reading of the thread in the I9000 Dev forum, I decided to go ahead and give this a try. I removed the journaling from all three Ext4 partitions. The process was rather painless and smooth.
I'll report back a little later after I've had some time to test it out.

I was only able to remove the journaling from /data(/dev/block/mmcblk0p2)... I typed "mount | grep ext4.. It only displayed the /data/ partition.. If the other partitions dont show, does it mean the other partitions dont have journaling?... But wouldnt they still show...? Im on obsidionv5... With eugene b oc 1125 kernel.. Im getting around 1700 in quadrant
Sms vibrant black body glove
Rom-macnutR2 kernel #53
Latest cwm
Black Htc G1
Sparksmod1.7
Latest radio death spl
Oc kernel 617mhz jit enabled ram hack

Are you sure you have an ext4 file system on the other partitions?

diazf09 said:
I was only able to remove the journaling from /data(/dev/block/mmcblk0p2)... I typed "mount | grep ext4.. It only displayed the /data/ partition.. If the other partitions dont show, does it mean the other partitions dont have journaling?... But wouldnt they still show...? Im on obsidionv5... With eugene b oc 1125 kernel.. Im getting around 1700 in quadrant
Click to expand...
Click to collapse
well I am using r12 with 1125 kernel... also I went into the lagix options from the recovery menu and chose the 'No-RFS advanced ext4' ... my procedure was pretty much a mirror of the example... if you only saw /data then it sounds like you chose the 'voodoo' lagfix from ULF...
btw I am not seeing an improvement on battery life after almost a full day... it does seem a bit more responsive...

diazf09 said:
I was only able to remove the journaling from /data(/dev/block/mmcblk0p2)... I typed "mount | grep ext4.. It only displayed the /data/ partition.. If the other partitions dont show, does it mean the other partitions dont have journaling?... But wouldnt they still show...? Im on obsidionv5... With eugene b oc 1125 kernel.. Im getting around 1700 in quadrant
Sms vibrant black body glove
Rom-macnutR2 kernel #53
Latest cwm
Black Htc G1
Sparksmod1.7
Latest radio death spl
Oc kernel 617mhz jit enabled ram hack
Click to expand...
Click to collapse
gawd...i'm prolly gonna get laughed out of the forums for this one. but, umm, what key on the keyboard is the symbol between 'mount' and 'grep'?

Button key above 'enter' using shift...
Sent from my GT-I9000 using XDA App

What's the point / advantage in running unjournaled EXT4 when you can already run EXT2 this way (minus the extra work)?

It is quite stupid to remove journal from FS just for a higher score,
then put your data in danger!

[INFO] SCH-i815 specific information (Verizon Galaxy Tab 7.7) [01/22/13]

If anyone is like me and owns a Verizon variant of the Galaxy Tab 7.7 (SCH-i815) then you have probably noticed that there is little information for users here that is easily available to refer to that is specific to our variant. This post is meant to house information for reference and I in no way claim to be the originator of this info, all props go to the creators themselves (please let me know any missing info so as to credit the proper people).
Please also let me know of any corrections that need to be made. If anyone feels this should be in the development forums, please don't recommend it to be moved, I am not a developer.
PLEASE BE ADVISED THAT ALL INSTRUCTIONS AND FILES HERE ARE FOR THE VERIZON GALAXY TAB 7.7 LTE SCH-i815 ONLY AND THAT YOU USE THIS INFORMATION AT YOUR OWN RISK.
If you have a different variant, do not flash any files below or you risk bricking your device .
As a general rule, DON'T ACCEPT OTA UPDATES IF YOU'RE ON A CUSTOM OR MODIFIED ROM. They will probably fail to install and remove root access.
SCH-i815 OFFICIAL FIRMWARE(S)
None available at the moment (probably never tbh)​*BE CAREFUL! No known official firmware exists to return to stock! Don't bork your Tab!
Tired of waiting for Samsung's LP10 ICS Update? Brave souls can flash electron73's modified ICS LP10 update
Please read everything in the following link below before flashing to avoid issues!
​http://forum.xda-developers.com/showthread.php?t=1932597​
*CWM Flashable ICS LP10 update by electron73 @ http://forum.xda-developers.com/showthread.php?t=1932597.
*ICS LP10 made available from system dumps by asenduk @ http://forum.xda-developers.com/showpost.php?p=32605284&postcount=46
Already on the latest ICS update and worried about losing root through the Verizon LP11 OTA update? Brave souls can flash electron73's modified ICS LP11 update
Please read everything in the following link below before flashing to avoid issues!
​http://forum.xda-developers.com/showthread.php?t=2111799​
STOCK FILES
Please be careful with stock files here and only use them if you know what you are doing.
Honeycomb FD01
Recovery:
FD01 ODIN flashable tar file: FD01_recovery.tar
FD01 Img File: FD01_recovery.img​
Ice Cream Sandwich LP10
Recovery:
LP10 ODIN flashable tar file: *Placeholder*
LP10 Img File: LP10 Recovery *Please note: This recovery will no longer accept unsigned files*
LTE Modem:
LP10 ODIN flashable bin file: LP10 Modem
Kernel:
LP10 ODIN flashable tar file: *Placeholder*
LP10 zImage File: LP10 Stock Kernel​
*Honeycomb FD01 recovery img pulled by electron73 @ http://forum.xda-developers.com/showpost.php?p=27376275&postcount=7.
*Honeycomb FD01 recovery tar compiled Gilbot.
*ICS LP10 recovery img pulled by asenduk @ http://forum.xda-developers.com/showpost.php?p=32605284&postcount=46
*ICS LP10 Recovery tar compiled by
ROOT METHOD(S)
For 3.2 Honeycomb FD01 builds and earlier:
1. Download and install LATEST SAMSUNG KIES (or stand-alone USB drivers if you can find them)
2. Transfer Root.zip to the EXTERNAL CARD on Galaxy Tab 7.7
3. Turn off the Galaxy Tab 7.7
4. Enter Recovery
- Hold Volume UP button + Power Button
- When TAB turns ON, RELEASE POWER BUTTON (Keep Holding Volume UP Button)
- Will Enter Recovery
5. Select install update from EXTERNAL Storage
6. Look for the file root.zip and select it with power button
7. When Finish, REBOOT. You're done​*Original guide written by Jade Eyed Wolf @ http://forum.xda-developers.com/showpost.php?p=21584547&postcount=1.
*Root.zip repackaged by Locerra.
​
For Ice Cream Sandwich LP10:
Easiest Root Method, please note this method no longer works with the LP11 OTA update !:
1.Install & Root with Chainfire's ExynosAbuse APK: http://forum.xda-developers.com/showthread.php?t=2050297​
Alternate Root Method, :
1. Download and install LATEST SAMSUNG KIES (or stand-alone USB drivers if you can find them)
2. Transfer Root_SuperSU.0.96.Only-signed.zip to the EXTERNAL CARD on Galaxy Tab 7.7
3. Turn off the Galaxy Tab 7.7
4. Enter Stock 3e Recovery
- Hold Volume UP button + Power Button
- When TAB turns ON, RELEASE POWER BUTTON (Keep Holding Volume UP Button)
- Will Enter Recovery
5. Select install update from EXTERNAL Storage
6. Look for the file root.zip and select it with power button
7. When Finish, REBOOT. You're done​*Original guide written by Jade Eyed Wolf @ http://forum.xda-developers.com/showpost.php?p=21584547&postcount=1.
*Source and Special Thanks to [email protected] Original Post, Chainfire and Entropy512 for Root.
​
UNROOT METHOD(S)
For 3.2 Honeycomb FD01 builds and earlier:
Gingerbreak:
1. Download and install the Gingerbreak APK on your tab: http://forum.xda-developers.com/showthread.php?t=1044765
2. Make sure you have an SD card in your tab and have USB debugging enabled.
3. Select UnRoot device Warning: Do not select Root device!
4. If successful, device will reboot and you will be unrooted !​*Gingerbreak APK by Chainfire @ http://forum.xda-developers.com/showthread.php?t=1044765.
*Gingerbreak exploit by The Android Exploid Crew @ http://c-skills.blogspot.com/2011/04/yummy-yummy-gingerbreak.html.​
CUSTOM RECOVERIES
ClockwordMod Recovery 6.0.2.3:
ODIN flashable CWM 6.0.2.3 TAR file: http://goo.im/devs/ohanar/i815/clockworkmod/cwm-6.0.2.3-i815.tar
Installation Instructions for stock FD01 users with stock 3e recovery:
Gain root access following the steps above.
Disable any lockscreen security you have.
While in the Stock ROM after enabling root access, navigate to the /system folder with a root-enabled file explorer app and mount R/W.
Locate the file "recovery-from.boot.p" and rename it to "recovery-from.boot.p.bak" then power down your tab, Do Not reboot or let the tab boot into your stock rom!
Boot into download mode by pressing and holding power + volume down
Press Volume up to continue into download mode and connect your tab to your pc
Load up ODIN and flash the 6.0.2.3 tar file via PDA
Reboot, you should now have persistent CWM 6.0.2.3
*CWM 6.0.2.3 ported for the SCH-i815 by Locerra @ http://forum.xda-developers.com/showthread.php?t=1542897.
Team Win Recovery Project 2.3.1.0:
ODIN flashable TWRP 2.3.1.0 TAR file: http://d-h.st/An9
Installation Instructions for stock FD01 users with stock 3e recovery:
Gain root access.
While in the Stock ROM after enabling root access, navigate to the /system folder with a root-enabled file explorer app and mount R/W.
Locate the file "recovery-from.boot.p" and rename it to "recovery-from.boot.p.bak" then power down your tab, Do Not reboot or let the tab boot into your stock rom!
Boot into download mode by pressing and holding power + volume down
Press Volume up to continue into download mode and connect your tab to your pc
Load up ODIN and flash the TWRP 2.3.1.0 tar file via PDA
Reboot, you should now have a persistent TWRP 2.3.1.0 recovery
*TWRP 2.3.1.0 by Dees_Troy @ http://forum.xda-developers.com/showpost.php?p=29639970&postcount=1.​
STOCK Honeycomb 3.2 CWM NANDROID
If you failed to make a backup of your Stock ROM, plop this sucker where your nandroids are held and flash. Be advised, this will not revert any Modem/Radio or recovery files changed if you updated to ICS
http://multiupload.biz/hnk4gmktgmhz/GTab7.7 sch-i815 stock cwm_MultiUpload.biz.7z.html​
Original Stock CWM Nandroid provided by nicduim @ http://forum.xda-developers.com/showpost.php?p=25763778&postcount=51.
CUSTOM ROM OPTIONS
CyanogenMod 9: http://forum.xda-developers.com/showpost.php?p=23528257&postcount=1
CyanogenMod 10: http://forum.xda-developers.com/showpost.php?p=29827849&postcount=1
CyanogenMod 10.1: http://forum.xda-developers.com/showthread.php?t=2053415
Paranoid Android: http://forum.xda-developers.com/showthread.php?t=1838391
Ice Cream Sandwich LP10 Update: http://forum.xda-developers.com/showthread.php?t=1932597​
PARTITION INFORMATION
lrwxrwxrwx root root 2012-09-08 13:24 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-09-08 13:24 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-09-08 13:24 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-09-08 13:24 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-09-08 13:24 HIDDEN -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-09-08 13:24 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-09-08 13:24 LTE -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-09-08 13:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-09-08 13:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-09-08 13:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-09-08 13:24 SBL2 -> /dev/block/mmcblk0p3​
INTERNAL HARDWARE INFO
Our Galaxy Tab 7.7 hardware:
1.4GHz dual-core Samsung Exynos 4210 processor
Samsung K3PE7E700B-XXC1 2x 4Gb LP DDR2 DRAM (1GB)
Samsung KLMAG4FEJA-A003 16GB flash storage chip
7.7" 1280 x 800 HD Super AMOLED+
3MP rear-facing camera
2MP front-facing camera
3.7V, 5,100 mAh Li-Ion battery (SP397281A)
Atmel MXT768E touchscreen controller
iM144 CEM 0D14
Samsung CMC22000 LTE baseband processor (CMC2000 PBU674.00S-1 C1134 ARM)
Samsung K4X51323PK MDDR2 512Mb mobile DRAM
Yamaha YMU823-P audio CODEC (YMU823-P 1144NAJB)
Samsung K5L2866ATE NOR based MCP
Silicon Image 9234BT HDMI chip (9234BT PCW832D 10K2143)
VIA Telecom CBP7.1C EVDO platform (CBP1.1C 114804 TAIWAN 2MB1405061)
FCI FC7785 19EA
6323R 1193AF PH 1141
Avago ACFM-7109 PCS/Cellular Band FBAR Quadplexer (ACFM-7109 FI135295075)
CSR SiRFstarIV GSD4t GSP IC (SiRF GSD4T 9600B C K138AH14)
8903CE TI203 ITHK +
Fairchild FDMC510P P-Channel PowerTrench MOSFET (PC2HK FDMC 510P)
Invensense MPU-3050M 3-axis gyroscope (MPU-3050M D1Y797-J1 EI 1153 K)
Maxim MAX8997 power-management IC for Samsung’s Exynos 4210 (MAX8997 EWW 1203 5VAZ)
Maxim MAX8996 Dual PWM Step-Down Converter (MAX8996 EWZ 5FYBY 132)
FCI FC7851 17BY
Avago A5013 K1141 DK089
A50H 11B22B1A10
CSR 8811 Bluetooth IC (8811 A06U K14BAM23)​
LINKS
Official Verizon Wireless Software Update Support Page: http://www.verizonwireless.com/galaxytab7.7support
[HOW-TO]Create Custom ODIN Images for Backup/Restore: http://forum.xda-developers.com/showthread.php?t=1082288​
OUTDATED INFO, FOR REFERENCE
OUTDATED: ODIN flashable CWM 5.0.2.7 TAR file: *http://www.mediafire.com/?045y0s12yamm2u8
This version of CWM was not built for the SCH-i815 and therefore can fail the check for SCH-i815!!​OUTDATED: Heimdall CWM 5.0.2.7 recovery image: *http://www.mediafire.com/?bl2aykukw6camap
This version of CWM was not built for the SCH-i815 and therefore can fail the check for SCH-i815!!
sudo heimdall flash --recovery recovery.img​*The P6800 International Galaxy Tab 7.7 has the same partition layout has the Verizon LTE variant and the flashable "OUTDATED" CWM above works, although it will fail the SCH-i815 check. You've been warned. "OUTDATED" CWM 5.0.2.7 Ported by ezynow @ http://forum.xda-developers.com/member.php?u=3940374
FAQs
Q: I obtained a Verizon Galaxy Tab 7.7 without a contract and have a 4G LTE phone with a compatible microSIM, can I swap the microSIM from my phone into the Tab and get service? What about Phone calls and SMS/MMS Text?
A: Yes and No. You can place your microSIM in the Tab and data will work. You can't, however, make or receive phone calls and SMS/MMS text as it has been disabled by Verizon. The APK files don't exist and simply using a file explorer to install them from the P6800 won't work. You will receive endless Force Closes and soft reboots if you do. There is no known way to enable Phone and SMS text at this time.​
Q: Does the 64gb MiscroSDXC card work in the SCH-i815?
A: Yep. Make sure to format it in the Tab before loading it with files. It is possible to format the card with an NTFS filesystem, for more info: http://forum.xda-developers.com/showthread.php?t=1665491​
Q:I have CWM installed and am Rooted on stock rom but I want to return my recovery to Stock in preparation for an OTA update, how can i do this?
A: Please check out electron73's awesome guide to revert back: http://forum.xda-developers.com/showpost.php?p=27376275&postcount=7. This guide is for trying to update from build FA02 to FD01. Not sure if this will work in any other situation.​
Q: I updated my Tab to ICS and don't have service with Verizon (I plan to use it as WiFi), How can i stop this annoying "SIM not inserted" notification?
A:There are a couple things you can do to stop this annoyance:
1. Insert a Verizon LTE SIM and allow it to activate if you have service with Verizon or allow it to fail activation if you have no service with Verizon. You can then turn off mobile data in Settings>Data. Leave the SIM in your tab to avoid the annoyance.
2. If you have no Verizon LTE SIM, put your tab in Airplane mode, then enable WiFi in Settings>WiFi. You should also be able to turn off mobile data in Settings>Data.​

CHANGES TO OP:
01/22/2013:
-Added electron73's modified LP11 OTA update link.
-Added warning to Root methods for the new LP11 update. They no longer work. Don't accept OTA updates unless you want to lose root access.​
01/13/2013:
-Added Chainfire's ExynosAbuse APK root method for LP10 ICS ​
12/19/2012:
-Added LP10 Stock Kernel
-Added LP10 Modem
-Updated CWM version link
-Cleaned up OP by Hiding sections
-CM 10.1 thread link added to custom ROMs ​
10/19/2012:
-Added TWRP 2.3.1.0 odin flashable tar file, thread link and credits (will remove if blessings are not given).
-Moved old, outdated CWM info to the bottom of thread (files are useless). ​
10/11/2012:
-Updated electron73's ICS LP10 CWM-Flashable ROM links
-Fixed Honeycomb Root link
-Added Ice Cream Sandwich Root link and guide
-Minor notations & changes to sections to include newly available ICS information
-Added LP10 recovery link along with warning
-Added Q to FAQS​
10/10/2012:
-Added electron73's ICS LP10 CWM-Flashable ROM link​
10/09/2012:
-Added Themes/Apps section
-Added Pimp My Rom to Themes/Apps
-Added link to Paranoid Android under Custom Rom Options
-Added Placeholders for Stock ICS Files
-Changed Stock Files Thread layout
-Added Partition Information​
09/22/2012:
-Added Gingerbreak UnRoot method (Honeycomb)​
09/08/2012:
-Updated CWM recovery references and links
-Added ODIN Flashable FD01 3e recovery tar file​
08/09/2012:
-Updated CWM recovery references and links
-Added CyanogenMod references and links​
07/27/2012:
-Slight recovery installation guide change​
07/13/2012:
-Added Internal Hardware Information for reference​
07/12/2012:
-Uploaded+Added Stock FD01 Recovery img
-Updated SCH-i815 CWM Recovery files
-Added SCH-i815 CWM installation instructions to enable permanent custom recovery
-Added disclaimer and updated CWM Instructions to include disabling lockscreen security and a warning not to boot into the stock rom during the process​

Chainfire said:
By request. FYI.
P6800 (3G)
mmcblk0p1 EFS DO NOT TOUCH
mmcblk0p2 BOOTLOADER DO NOT TOUCH
mmcblk0p3 BOOTLOADER DO NOT TOUCH
mmcblk0p4 param
mmcblk0p5 kernel
mmcblk0p6 recovery
mmcblk0p7 cache
mmcblk0p8 modem/radio
mmcblk0p9 system
mmcblk0p10 data
mmcblk0p11 hidden/preload
P6810 (Wi-Fi)
mmcblk0p1 EFS DO NOT TOUCH
mmcblk0p2 BOOTLOADER DO NOT TOUCH
mmcblk0p3 BOOTLOADER DO NOT TOUCH
mmcblk0p4 param
mmcblk0p5 kernel
mmcblk0p6 recovery
mmcblk0p7 cache
mmcblk0p8 system
mmcblk0p9 data
mmcblk0p10 hidden/preload
Click to expand...
Click to collapse
i815 (4GLTE)
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p9 /system ext4 rw,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data
=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data
=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=o
rdered 0 0
/dev/block/mmcblk0p11 /preinstall ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023, group_id=1023,default_permission,allow_other 0 0
tmpfs /mnt/sdcard/extStorages tmpfs ro,relatime,mode=755,gid=1000 0 0
/dev/block/vold/179:17 /mnt/sdcard/extStorages/SdCard vfat rw,dirsync,nosuid,nodev,noexec,
relatime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,code
page=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

Thanks for giving the i815 some love. I like having one stop and maybe others can add to it so this becomes the go-to thread.

rayjr13 said:
i815 (4GLTE)
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p9 /system ext4 rw,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data
=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data
=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=o
rdered 0 0
/dev/block/mmcblk0p11 /preinstall ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023, group_id=1023,default_permission,allow_other 0 0
tmpfs /mnt/sdcard/extStorages tmpfs ro,relatime,mode=755,gid=1000 0 0
/dev/block/vold/179:17 /mnt/sdcard/extStorages/SdCard vfat rw,dirsync,nosuid,nodev,noexec,
relatime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,code
page=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Click to expand...
Click to collapse
This is the i815 partition layout, right?
caseyatbt said:
Thanks for giving the i815 some love. I like having one stop and maybe others can add to it so this becomes the go-to thread.
Click to expand...
Click to collapse
Thanks.
A lot of the info I find here pertains specifically to the 6800/6810 as they are the more widely used devices, so I decided to try and create a thread to find i815 specific info for future reference for myself or anyone else who owns an i815.
I'd love for anyone to help add to it as well!

Outgoing calls on the Verizon Tab 7.7
Using Groove IP (available on the market), I am able to make outgoing calls but not incoming calls. Hope this helps.

With so many threads on the P6800/P6810 it would nice to have this thread stickied so one doesn't have to search around for the few i815 threads.
electron73's recovery post is *extremely* helpful and works (first-hand personal experience).

Gilbot said:
This is the i815 partition layout, right?
Click to expand...
Click to collapse
yes /mount run from terminal emulator on my i815 hoping someone else could confirm the same on theirs.

aximtreo said:
Using Groove IP (available on the market), I am able to make outgoing calls but not incoming calls. Hope this helps.
Click to expand...
Click to collapse
for incoming calls make sure to enable gtalk as an endpoint in google voice settings ( web site )

Can anyone savvy enough who has a linux/UNIX box create an Odin flashable tar file from the Stock FD01 image i posted above that electron73 pulled?
It would be a great help for anyone who wants to flash the stock recovery through Odin.

Enter your password?
Not sure what happened. I flashed CWM after doing: "recovery-from.boot.p" and rename it to "recovery-from.boot.p.bak" then power down your tab.
Flashed CWM using PC Odin pda with auto reboot, f. reset time. Got PASS.
CWM loaded up but rebooting to stock resulting in a screen stating to "enter your password".
I used adb to restore the file by removing the .bak from the file name. Rebooting into recovery shows Android systen recovery <3e>
The message at the bottom says:
E:failed to mount /data (invalid argument)
#manual mode#
any suggestions on getting booted back to stock ROM. I thought tar from above only flashed the recovery partition any reason why it wouldn't boot back into stock? Or any idea what to enter for the password?
thanks

rayjr13 said:
Not sure what happened. I flashed CWM after doing: "recovery-from.boot.p" and rename it to "recovery-from.boot.p.bak" then power down your tab.
Flashed CWM using PC Odin pda with auto reboot, f. reset time. Got PASS.
CWM loaded up but rebooting to stock resulting in a screen stating to "enter your password".
I used adb to restore the file by removing the .bak from the file name. Rebooting into recovery shows Android systen recovery
The message at the bottom says:
E:failed to mount /data (invalid argument)
#manual mode#
any suggestions on getting booted back to stock ROM. I thought tar from above only flashed the recovery partition any reason why it wouldn't boot back into stock? Or any idea what to enter for the password?
thanks
Click to expand...
Click to collapse
I'm not sure why it would ask for a password. Are you basically getting a passworded lock screen when booting into the stock rom? Maybe the tab needs to have an unsecure lockscreen before attempting this.
At this point I would try to use electron73's FD01 files to get you back into the stock rom and restore stock recovery (you will lose root but should still keep all your apps and settings, etc..) Please take your time and know that based on the information I know, this might work, but know you're taking a risk. Please make sure you are only performing these procedures over your stock rooted rom.
-First load up an external microSD card with the "SCH-I815_FA02c_To_FD01.1.zip" file electron73 hosted here : http://www.mywo.org:88/XDA/sch-i815/index.php. Hopefully you can do this on a PC or push it if you're able to use ADB. Don't flash this file yet, just have it on the external SD card and have the card in your tab.
Make sure your external microSD card is in the tab with the "SCH-I815_FA02c_To_FD01.1.zip" file before you flash with Odin.
-Boot into download mode, load up Odin and Flash CWM again, without auto reboot checked. Once you get a green PASS with Odin, disconnect the tab and hold power until it powers down, but be ready to immediately hold power and volume up to boot into CWM once the tab turns off. Do not let it boot into the stock rom.
-At this point you should be booted in CWM. Using CWM, flash the "SCH-I815_FA02c_To_FD01.1.zip" on the external card. It will take a few minutes. This will basically re-flash the FD01 update onto your tab (except for the baseband), including the stock e3 recovery. The baseband shouldn't be needed at this point if you did the FD01 OTA update anyways.
-Reboot
You should now have stock 3e recovery and should be able to boot into the stock rom. You will not have root access. You can re-root your tab to gain root.​

Will this work for the SCH-I800 for VZW? I'm rooted but CWM is V5.0.0.8 isnt working. I get hung up when trying to recover or add a rom.

tr2ride said:
for incoming calls make sure to enable gtalk as an endpoint in google voice settings ( web site )
Click to expand...
Click to collapse
aximtreo said:
Using Groove IP (available on the market), I am able to make outgoing calls but not incoming calls. Hope this helps.
Click to expand...
Click to collapse
I use google voice app to initiate incoming calls and csip with pbx and ipkall to receive the calls. Works great with gvoice Forwarding. Incoming voice sounds great but apparently outgoing voice isn't picked up well. I may try gtalk for incoming call receipt to see how quality compares . Also thinking about Bluetooth headset to see if its the mic. Haven't tried video Skype to confirm a baseline voice quality of the device.

One question sorry I just want to make sure. I bricked my tab by trying to instal the p6800 Rom. I used the Rom to go back to stock by using the nano droid image. I noticed that I can't update to FD02. It gave the update notice but when I click update it restarts but gives me an error takes me back to the nano droid screen. Will flashing this Rom with Odin help me or am I missing something. I have rooted the tab and I just want to make sur this will help. Can anyone help. Sorry for the question. I found how to unbork but it was for a for a different decide. Any suggestions?
Sent from my HTC Sensation 4G using xda app-developers app

dperez0426 said:
One question sorry I just want to make sure. I bricked my tab by trying to instal the p6800 Rom. I used the Rom to go back to stock by using the nano droid image. I noticed that I can't update to FD02. It gave the update notice but when I click update it restarts but gives me an error takes me back to the nano droid screen. Will flashing this Rom with Odin help me or am I missing something. I have rooted the tab and I just want to make sur this will help. Can anyone help. Sorry for the question. I found how to unbork but it was for a for a different decide. Any suggestions?
Sent from my HTC Sensation 4G using xda app-developers app
Click to expand...
Click to collapse
please confirm you have an I815. I'm confused because afaik the I815 latest is FD01. When I check my device it says no new updates.

Yes I have the I815. There's should be an update I received the noticed on Friday thinking it was ICS but when clicked install it took me to Nano droid screen. So I decided to restore it again. But once I connected to the internet it gave me the message again. I tried to update and once again it took me back to the nanadroid. It seem it can't find a drive. I think m drive not even sure what that means. So any ideas on how to receive the updates?
Sent from my HTC Sensation 4G using xda app-developers app

what is nano droid? Is that your recovery? What Baseband kernel and build does it say you have in about?

Nano droid is whe you press the power button off and the volume up. Once the galaxy tab logo appears release the power button ans continue holdind the volume button up and should take you there. I'm not sure what kernel version I have I don't have my tab till later in the evening.
Sent from my HTC Sensation 4G using xda app-developers app

I guess I have the latest update but don't understand why I get an update notification. Once I click update it doesn't show up again so I'm baffled. I'll do a restore one more time to show you what it does.
Sent from my HTC Sensation 4G using xda app-developers app

[4.5.2013][UTIL][Win]Android Ultimate Toolbox Pro - The Ultimate Android Utility

{
"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"
}
I present you Android Ultimate Toolbox Pro, the ultimate Android utility! As the name says, it's a toolbox-like program that offers many features that make the usually not-so-easy tasks easier.
Caution! This program is not foolproof! Do not try to outsmart it by playing tricks, because you may result with an expensive brick in the worst case!
Requirements
Microsoft .NET Framework 4 (Client Profile is also needed)
Java JDK and JRE and Android SDK
Key features
Update.zip creator
Update.zip signer
Flash kernels
Flash recovery images
Flash upate.zip
Flash system images
Flash data images
Flash splash images
Install APKs (system and user)
Uninstall APKs (system and user)
Unpack APKs
Repack APKs
Sign APKs
Deodex APKs, Jars (both computer and device)
Zip-align APKs
Check MD5 sums
File manager
Root checker
Root your device
Unroot device
Logger (logcat and dmesg)
Rebooter (normal reboot, reboot in recovery, reboot in bootloader, reboot from fastboot)
Backup manager
Backup/restore apps NEW!!
Device ID configurator (device name, build number, Android version)
Unlock bootloader
Lock bootloader
Wipe (system, data, cache, boot, recovery)
And much more to come!
Note: make sure to read the help topics before using Android Ultimate Toolbox Pro.
Download
(If you don't see the download button, click here)
(If you don't see the changelog button, click here)
Latest version: 1.2.0.0
Credits
fdespotovski - icon
RegawMod - AndroidLib library
Google - aapt and zipalign binaries
Ryszard Wiśniewski (brut.alll) and Connor Tumbleson - apktool
Creators of smali and baksmali - smali and baksmali binaries
Martin Gagne - loading circle
cdesai - help
Rebellos - help
Zoran Despotovski - tester
Special thanks goes to my supporters bigrammy, imilleson and DeepUnknown. Thanks guys, you're awesome!
Error reporting
If you want to report a misbehavior of Android Ultimate Toolbox Pro, just fill out this form and I'll take a look at it and fix it as soon as possible.
Before posting a question in this thread:
-please search if the question is already posted and answered
-read all of the help topics
trust me, you'll save both yours and mine time.
Feedback is always appreciated.

What's new?
Code:
v1.0.0.0 [14.09.2012]
Initial release
v1.0.1.0 [24.10.2012]
-Bug fixes
-Performance improvements
-The program doesn’t need the Visual Basic Power Pack anymore
-New feature: Restart Android services (accessible in Settings)
-New setting: enable/disable grid in file manager
v1.0.2.0 [21.11.2012]
-Bug fixes
-Added ‘Check all’ and ‘Uncheck all’ buttons in the Backup configurator window
-New in Update Creator: the text dialogs for file and directory locations and permissions suggest common values
-New in Update Creator: the text dialog for the file location has a check box to set the same location for the next files
-Added buttons for the video review and changelog in the main menu
-Small under-the-hood improvements
v1.1.0.0 [22.01.2013]
-Added ‘Unpack APKs’ feature
-Added ‘Repack APKs’ feature
-Added ‘Sign APKs’ feature
-Added ‘Deodex APKs / Jars’ feature
-Added ‘Zip-align APKs’ feature
-Reorganized the main window
-Added binaries: apktool, smali, baksmali, aapt, zipalign, signapk
-New settings: delete unsigned APKs after signing, sign APKs after repacking, ask for framework dependencies, custom framework location (needed for deodexing), use custom framework for unpacking APKs, zip-align APKs after deodexing
-Usability and performance improvements, bug fixes
-...
v1.1.1.0 [09.02.2013]
-Fixed bug related to unpacking APKs
-Improved the APK uninstallation feature, now you can uninstall more than one APKs at once
-New feature: Update manager, displays latest version and changelog when an update is available
-Updated AndroidLib library to 1.5.1.0
-Updated apktool binary to 1.5.2
-Performance improvements
v1.1.1.1 [09.03.2013]
-Reverted AndroidLib library to 1.3.0.0 because of broken features with version 1.5.1.0 (fixed Update.zip creator and Backup/Restore features)
v1.2.0.0 [4.5.2013]
-Added features: backup and restore apps
-Added 'Size' column to the 'Update entries' list in the Update creator
-Bug fixes

Reserved...

nice tool may come in handy, will this work on non nexus devices because when i installed on bottom left corner it says only for nexus devices, i have an lg device

Very good , thank you very much

hsingh1993 said:
nice tool may come in handy, will this work on non nexus devices because when i installed on bottom left corner it says only for nexus devices, i have an lg device
Click to expand...
Click to collapse
Yes, it will. Only the functions for bootloader unlocking and locking are for Nexus devices, but the others are universal.
kinghunki said:
Very good , thank you very much
Click to expand...
Click to collapse
I'm glad you like it.
Sent from my HTC EVO 3D X515m using xda app-developers app

Will this work for htc devices which doesn't have s- off?
Sent from my HTC One X using xda premium

timlambo said:
Will this work for htc devices which doesn't have s- off?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes, but not all features will work. For instance, you won't be able to flash system, data, kernel, recovery and splash images, which require a bootloader that supports fastboot commands (which indeed is a S-OFF bootloader). If you are on unlocked S-ON bootloader (HTC Unlock), then they should also work.

despotovski01 said:
Yes, it will. Only the functions for bootloader unlocking and locking are for Nexus devices, but the others are universal.
I'm glad you like it.
Sent from my HTC EVO 3D X515m using xda app-developers app
Click to expand...
Click to collapse
thanks great tools now i can remove system app whenever i want and can customize my rom a little.

I recently tried this app, and seems that has very useful functions, thanks.
I have a problem with backup future though. My device(U8800) has a difference about recovery and boot images. Has a seperate fat32 partition which mounted as .cust_backup, in which are the recovery.img, boot.img and some other system files.
So, the app cannot backup recovery and boot. Only backup system and data. The approach used on CMW recovery for my device, is to just copy and compress all this partition which is less that 200MB.
Can you implement support for this in the app?
Here is the mounts of my device:
Code:
[email protected]:/ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p12 /system ext4 rw,relatime,user_xattr,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p13 /data ext4 rw,relatime,user_xattr,barrier=1,nomblk_io_subm
it,data=ordered 0 0
/dev/block/mmcblk0p6 /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,no
mblk_io_submit,data=ordered 0 0
/dev/block/mmcblk0p14 /HWUserData vfat rw,relatime,uid=1000,gid=1015,fmask=0002,
dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,u
tf8,errors=remount-ro 0 0
/dev/block/mmcblk0p1 /.cust_backup vfat ro,relatime,fmask=0000,dmask=0000,allow_
utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
0 0
/dev/block/vold/179:14 /mnt/sdcard1 vfat rw,nosuid,nodev,noexec,relatime,uid=100
0,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso88
59-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/foursqwifi.aithanasakis-1 vfat ro,dirsync,nosuid,nodev
,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shor
tname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.mobappbox.pyramidrun-1 vfat ro,dirsync,nosuid,node
v,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,sho
rtname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.svox.classic.langpack.ell_grc_fem-1 vfat ro,dirsyn
c,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=
iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/taxy.kwd-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1
000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf
8,errors=remount-ro 0 0
/dev/block/dm-4 /mnt/asec/gr.digitalblast.drivesafe-1 vfat ro,dirsync,nosuid,nod
ev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,sh
ortname=mixed,utf8,errors=remount-ro 0 0
thanks in advance.

despotovski01 said:
After months of hard work, I present you the ultimate Android utility, Android Ultimate Toolbox Pro! As the name says, it's a toolbox-like program that offers many features that make the usually not-so-easy tasks easier.
Caution! This program is not foolproof! Don't try to outsmart it by playing tricks, or you may result with an expensive brick in the worst case!
Requirements
Microsoft .NET Framework 4 (Client Profile is also needed)
Java JDK and JRE and Android SDK (for signing update.zip files)
Visual Basic Power Packs 10 - download here
Key features
Update.zip creator
Update.zip signer
Flash kernels
Flash recovery images
Flash upate.zip
Flash system images
Flash data images
Flash splash images
Install APKs (system and user)
Uninstall APKs (system and user)
Check MD5 sums
File manager
Root checker
Root your device
Unroot device
Logger (logcat and dmesg)
Rebooter (normal reboot, reboot in recovery, reboot in bootloader, reboot from fastboot)
Backup manager
Device ID configurator (device name, build number, Android version)
Unlock bootloader
Lock bootloader
Wipe (system, data, cache, boot, recovery)
And much more to come!
Note: make sure to read the help topics before using Android Ultimate Toolbox Pro.
Download
(If you don't see the download button, click here)
Latest version: 1.0.0.0​
Credits
fdespotovski - icon
RegawMod - AndroidLib library
cdesai - help
Rebellos - help
Zoran Despotovski - tester
Error reporting
If you want to report a misbehavior of Android Ultimate Toolbox Pro, just fill out this form and I'll take a look at it and fix it as soon as possible.
Before posting a question in this thread:
-please search if the question is already posted and answered
-read all of the help topics
trust me, you'll save both yours and mine time.
Feedback is always appreciated.
Video coming soon!
Click to expand...
Click to collapse
excellent work !

dancer_69 said:
I recently tried this app, and seems that has very useful functions, thanks.
I have a problem with backup future though. My device(U8800) has a difference about recovery and boot images. Has a seperate fat32 partition which mounted as .cust_backup, in which are the recovery.img, boot.img and some other system files.
So, the app cannot backup recovery and boot. Only backup system and data. The approach used on CMW recovery for my device, is to just copy and compress all this partition which is less that 200MB.
Can you implement support for this in the app?
Here is the mounts of my device:
thanks in advance.
Click to expand...
Click to collapse
Hi, mate,
First off, thanks for using my new program. I'm looking forward to adding support for your devce, but first I need to know how do you flash and backup recovery and boot images? Do you just flash that combined partition, or you flash the boot and recovery images seperately?
Sent from my HTC EVO 3D X515m using xda app-developers app

The backup is, as I mentioned, the folder Image(which contains the system files) from .cust_backup partition. The device has a special pink screen in which the pc loads this partition and I just replace the recovery.img with the custom one. Same and with boot.img can happens, but usually, for custom roms, is contained on update.zip.

dancer_69 said:
The backup is, as I mentioned, the folder Image(which contains the system files) from .cust_backup partition. The device has a special pink screen in which the pc loads this partition and I just replace the recovery.img with the custom one. Same and with boot.img can happens, but usually, for custom roms, is contained on update.zip.
Click to expand...
Click to collapse
OK, I will see what I can do with that.

So, what do you think about this program? Is it OK? Should I change anything?

Excellent will take a look as soon as my pc is operational thank you

Is it possible to root Galaxy Nexus running on 4.1 JB with FIDO network???

Cool to see more and more people developing using my library AndroidLib

I was wondering when using this app of yours, what state should the phone/tablet/device be in? ie: recovery, phone on but screen off, phone on and screen on etc etc. And I was wondering also how you are able to make it so that the app can root all sorts of different devices.

ashqmallik said:
Is it possible to root Galaxy Nexus running on 4.1 JB with FIDO network???
Click to expand...
Click to collapse
Theoretically it should be a cinch to root the GNex via this utility as long as you have set up your Android SDK properly. Your bootloader should be unlocked (If not use Feature #20 to do so). Subsequent rooting and then pushing a custom recovery via adb should be very simple.
DISCLAIMER: I have not used this utility to Unlock and Root my GNex. I am only going by the universal methods and assumptions regarding recent Samsung devices. I did use the method given in my signature.

[vision][fried emmc] Booting CM 7.2 from SD card

Hi there,
I just found catherall's thread on [how to boot CM 7.1 from the external SD card][0] on a Desire Z/G2 with the infamously fried eMMC.
I used his instructions to boot CM 7.2 (the last stable version for the Vision); since the above thread ends with a dangling question on how to update the system to be booted, I thought I'd document my efforts.
anonymousthing said:
anybody know what system.img format he is using?
Click to expand...
Click to collapse
It's just an ext4 file system:
Code:
$ file system.img
system.img: Linux rev 1.0 ext4 filesystem data, UUID=b4db3ed8-7d52-46a0-85fb-46fb67c5e837 (needs journal recovery) (extents) (huge files)
$ adb shell
~ # mount | grep system
/dev/block/loop0 on /tmp/boot.img-ramdisk/system type ext4 (rw,nodev,noatime,nodiratime,nouser_xattr,commit=19,barrier=0,data=ordered)
Disclaimer: On the original image, `file` actually identifies the FS as a `mounted or unclean` ext2; it's definitely an ext4 with journaling, though. Accordingly a `mount -t ext2` will fail with a `wrong fs type`.
You can create a new one with
Code:
$ dd if=/dev/zero of=system.img bs=4k count=64000
$ /sbin/mkfs.ext4 system.img
# mount -o loop -t ext4 system.img /media/new_sys
anonymousthing said:
I have tried making my own system.img from the rom but it does not work
Click to expand...
Click to collapse
This is potentially due to missing binaries:
Code:
$ diff -r /media/orig_sys update-cm-7.1.0-vision-signed/system | head -n 5
Only in /media/orig_sys/bin: cat
Only in /media/orig_sys/bin: cmp
Only in /media/orig_sys/bin: date
Only in /media/orig_sys/bin: dd
Only in /media/orig_sys/bin: dmesg
If you download a version of CM, at least the `toolbox` and the `busybox` binaries will be missing from the `system/bin` and `system/xbin` directories respectively. I couldn't be bothered to check for up-to-date versions but just copied the ones provided by catherall before copying over the new CM version:
Code:
# cp -r /media/orig_sys/bin /media/orig_sys/xbin /media/new_sys
# cp -r cm-7.2.0-vision/system/* /media/new_sys
This will obviously update all the files that come with CM 7.2 and just keep what's not included in the box.
While you're at it, you might want to add up-to-date gapps:
Code:
# cp -r gapps-gb-20131214-signed/system/* /media/new_sys
This gives you a booting CM 7.2. Just replace the `system.img` that comes with catherall's `.zip` with the one you just created and off you go
Unpleasant issue: Booting from SD seems to require a specifically prepared kernel, so the `boot.img` that comes with a different ROM/CM version won't work. So until someone finds out how to prepare a kernel for booting from SD, you will have to continue to boot the one provided by catherall. However, the WIFI driver has not been compiled into the kernel but lives in a separate kernel module in `/system/lib/modules/bcm4329.ko`. Which we (by copying over the `/system` dir from the CM 7.2 build) replaced with a version incompatible with the old kernel we have to boot. So if you intend to boot through `fastboot` and use WIFI (and why wouldn't you? ;P), we will have to put the old kernel module back:
Code:
# cp /media/orig_sys/lib/modules/bcm4329.ko /media/new_sys/lib/modules/
Weirdly enough, in the CM 7.2 version I downloaded, the permissions for the `dhcpd-run-hooks` script were broken, so I at least needed to fix those too:
Code:
# chmod 550 /media/new_sys/etc/dhcpd/dhcpd-run-hooks
So, `umount` your pristine new `system.img`, move it to your SD card and boot into CM 7.2.
HTH
D.
PS I naively tried to create a larger 1 GB `data.img`, copying over the content from the existing one, but the phone didn't boot with that one. I might have made a mistake (was rather late at that point -.- and I didn't investigate any further), but it seems like the size of the partitions may be hardcoded somewhere. If someone has any additional information, please let me know Thx!
PPS If anyone ([MENTION]@catherall[/MENTION]? ;P) knows anything about the kernel issue, I'd be highly interested
PPPS After creating this account (to be fair, I've been profiting from this community since the old Windows Mobile days), I was informed that as an account noob, I obviously didn't have anything to contribute to this community and was ordered to place my undoubtedly profane question (which certainly had been answered may times before, I was only too lazy/dumb to search) outside the elite developer forums [/rage]. Maybe one of the Mods can stitch the [original thread][0] and this st0pid workaround back together again? :/ Thanks!
[0]: http://forum.xda-developers.com/showthread.php?t=1572924

I was able to successfully build TWRP for my Galaxy Tab a 9.7 SM-P555 BUT

Hi,
So, as I said in the title, I have a Samsung Galaxy Tab a 9.7 SM-5555 device running on the official Android 7.1 (P555XXU1CQL3) by Samsung, and I also have the kernel's source code for that same stock firmware (P555XXU1CQL3), I got it from opensource.samsung.com.
So since I'm new to this field, I thought that the best thing I can do to learn before trying to build a lineage ROM, is to build a fresh up-to-date TWRP for my tablet (I am aware of twrp_3.0.2-1_SM-P555_mm_15816.tar and it's working fine, I just wanna build an updated version myself, cuz why not right?)
So I used the shallow clone twrp omni 7.1, since I'm only building the recovery image (it has arm-eabi-4.8 compiler btw).
my BoardConfig.mk is inheriting device/samsung/msm8916-common/BoardConfigCommon.mk, and I had to delete some things from BoardConfigCommon cuz they are not necessary (I think ).
At this point I got everything setup, the device tree + the kernel, after I run the make cmd : make clean && make -j64 recoveryimage
It build successfully until 99%, and then it says the recovery image is too large, which is true, since my BOARD_RECOVERYIMAGE_PARTITION_SIZE := 15728640 - I got it from my tablet, while the out/../recovery.img is 16.7MB.
After some research, I find out that the kernel is using CONFIG_KERNEL_LZ4=y to compress/decompress things, so I tried several things like: LZMA, GZIP, CONFIG_KERNEL_XZ, and the build passes if I use any of them , I get an image between 13MB <=recovery.img <=15MB.
Now it's time to flash it right, so I use Odin v3.14.1 since it's working great for the already made twrp_3.0.2-1_SM-P555_mm_15816.tar and because if I boot my tablet in Download mode adb reboot bootloader, ADB and fastboot can't detect my device anymore, so I used Odin.
Now I flashed the recovery successfully, without auto reboot, and then I jump to recovery mode to find the Odin label at the top left (just like in download mode) but the screen is in black & shows the Samsung Galaxy logo and nothing happens. It feels like it doesn't even read the recovery, no crashes, no nothing, I'm not sure if it reads or not, since I can't debug it anw, it doesn't show in adb devices nor fastboot.
At this point I spent a lot of time trying to build this recovery but It just doesn't boot, I double checked my twrp.fstab :
#mount point fstype device [device2]
/boot emmc /dev/block/bootdevice/by-name/boot
/recovery emmc /dev/block/bootdevice/by-name/recovery flags=display="Recovery";backup=1
/data ext4 /dev/block/bootdevice/by-name/userdata flags=fsflags=rw,discard,nosuid,nodev,noatime,nodiratime,inline_xattr,inline_data; encryptable=/dev/block/bootdevice/by-name/encrypt
/cache ext4 /dev/block/bootdevice/by-name/cache
/system ext4 /dev/block/bootdevice/by-name/system
#/misc emmc /dev/block/bootdevice/by-name/fota
/efs ext4 /dev/block/bootdevice/by-name/efs flags=backup=1;display=EFS
#/efs1 emmc /dev/block/bootdevice/by-name/modemst1 flags=backup=1;subpartitionof=/efs1
#/efs2 emmc /dev/block/bootdevice/by-name/modemst2 flags=backup=1;subpartitionof=/efs1
/firmware-modem vfat /dev/block/bootdevice/by-name/modem flags=backup=1;display="Modem"
/firmware vfat /dev/block/bootdevice/by-name/apnhlos flags=backup=1;display="Firmware"
/external_sd auto /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="Micro SDcard";storage;wipeingui;removable
/usb-otg auto /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable
I don't think it's the problem, or is it?
I would really really love to hear any ideas, suggestions, I spent quite some time trying to figure this out and this is not the ending I was hoping for XD.
Any help is greatly appreciated,
Thanks in advance & stay safe

I faced a similar issue. you are probably using kernel from stock android and building TWRP using android 10.
You can compile the twrp from the link below, mine is able to boot but have some partition issues which I will work on later once the ROM is finalised.
TWRP

Same issue here, did anyone found a fix or proper TRWP?