Related
Cheers Everyone,
First off, thanks for opening this thread.
I've recently rooted my kindle and was very pleasantly surprised when I noticed a very familiar linux-like file system underneath. Now I'm eager to learn more.
Let me start from what I know (or think I know )
For custom bootloaders, the goto seems to be firefirefire
for recovery mini-os which is recommended? CWMR or TWRP
I hate to ask because I see it all over the forums, but the responses are all over the place. It looks like TWRP had a gui, and easier for backup/restore, but maybe CWMR... performs better?
Ok, let me get to the main questions, understanding android itself.
this all started when I discovered $adb shell
ok, when you install a new ROM it wipes /system from the devise and copies the /system from the zip, also it seems to append to the /data (assuming your rom zip came with applications). Does installing a rom do anything else? I see this file in my zip /META-INF/com/google/android/updater-script and update-binary. Does one of those automatically get run when you use the recovery loader to install a new ROM? Ok, looking at the contents of the file, it seems like it is the script run to install the ROM, it does lots of things like sets up simlinks, and sets permissions.
$ df
Filesystem Size Used Free Blksize
/dev 223M 32K 223M 4096
/mnt/asec 223M 0K 223M 4096
/mnt/obb 223M 0K 223M 4096
/system 503M 296M 207M 4096
/data 1G 76M 1G 4096
/dropbox 4M 1M 3M 1024
/cache 251M 4M 247M 4096
/mnt/sdcard 5G 15M 4G 4096
/mnt/secure/asec: Permission denied
$ echo $PATH
/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
Now for some questions:
using adb shell, how do I get root permissions? Infact, what user am I when first start it? what editors are available? (vi?pico?ed? where?)
I looked around after installing modaco rom and I'm surprised to see some files like: TICameraCameraProperties.xml in /system/etc. it's full of camera stuff, i'm surprised to find that on my kindle since there is no camera on the devise. So my question is, with these custom rooms, are extra files littered all about, assuming they were used for other devices and just never removed when ported for the kindle? I'm surprised since modaco is based on stock 6.3.... maybe amazon added it in preparation for the next kindle?
Help me understand what's in the partitions
first, why don't I see /boot or /recovery?
next,
/dev ok, this is for the hardware, but why so big? seems like we could get by with just a few megs
/mnt/asec secure files? any example of this being used? Again, that's alotta space...
/mnt/obb no idea what this is... luv to make it smaller
/system os
/data apps and user files
/dropbox dropbox for what?
/cache assuming swap and paging
Another question, I assume when switching roms from diff android versions, like GB, HC, ICS, you need to wipe and install/reinstall your apps (in /data) since they will need versions specific to the android version you are running? or is each future android version assumed to be backwards compatible...?
Anyone who's taken a look "under the covers" probably has similar questions and I hope one of our more experiences brothers can shed some light on the above questions.
Many thanks to everyone who contributes,
Paul
To get root permissions for adb, type "adb root". If you're in adb shell just type "su". As far as editors go, none that I'm aware of. For that, your best bet would be to get the source. If it's just Android you are interested in then you can get the source from the Android website. If it's the Kindle Fire specifically then you should check out JackpotClavin's tutorial for building cm9 from source. Get your build environment set up, download the source, and then you'll have free reign to edit a huge majority of the files. Just be sure to have +-40Gb to use as your workspace.
The tutorial can be found here
http://forum.xda-developers.com/showthread.php?p=20844007
Depending on your level of programming experience, the rest should be easy to figure out on your own.
Sent from my Amazon Kindle Fire using xda premium
Thanks, I appreciate it! I'll take a look at tutorial in the morning.
Any word on those partition sizes? Seems like lots of wasted space, probably could shave off a half gig to add to /mnt/sdcard... Do you know if those partitions I mention ever fill up?
I don't mess with partitions at all. I've had bad experiences with it in the past so I tend to stay at a safe distance.
User eldarerathis has modded the bootloader to support dual-boot on the Fire so I would check with his thread first. http://forum.xda-developers.com/showthread.php?p=23634393
He seems to have a pretty good understanding of the separate partitions. You'll need a few more posts before you can post in that thread though.
Sent from my Amazon Kindle Fire using xda premium
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
PIMPUP_ICS_MALATA T8
DISCLAIMER NOTE
ITS NOT MY RESPONSIBILITY FOR DAMAGE WILL CAUSED FLASHING THIS ROM
HTML:
features
all cm9 twaeks ,screenshots,lockscreen widgets,theme,dsp,developers option
superbass beats with autovolume and working dsp manager
supercharger script
ntfs driver support
cifs support
walkman player with working youtube tweaks
floatting touchscreen
brightness & backlight stage improve
large battery levels over 3 days to wifi sleep
deep sleep without sod
3g and wifi support for most networks
latest gapps inverted with gmail.4.2 pinch to zoom and slice to delete
chrome browser working with flashplayer
DOWNLOADS
download nvflash:http://www.mediafire.com/?n513xv6dr28ppmw
download rom :http://www.mediafire.com/download.php?fl4dwihc172jztv
download gapps inverted:http://www.mediafire.com/download.php?fl4dwihc172jztv
INSTRUCTIONS
FIRST MUST GO TO OTA 20110524 FROM MALATA SITE AND DO DATA FACTORY RESET/WIPE CACHE
GO APX MODE AND RUN NVFLASH
GO CWM 5.5.0.4 DO DATA FACTORY RESET
FLASH PIMPUP 16 ROM AND REBOOT
CHECK IF GTALK APP HAVE BEEN INSTALL AND
REBOOT TO CWM 5.5.0.4 AND FLASH GAPPS
GO ADVANCE AND FIX PERMISSIONS REBOOT
MUST HAVE A COPY OF FAT32.IMG TO THE ROOT OF SD CARD
OPEN TERMINAL TYPE SU TO GET PERMISSION
TAKE MOUNT 1 COMMAND FROM ATTACHMENT AND PASTE TO TERMINAL
WAIT UNTILL MESSAGE THAT : ... bytes transferred in ..... secs AND PASTE MOUNT 2 COMMAND
NOW YOU HAVE UNLOCK YOUR INTERNAL MEMMORY
DONE!!!
{
"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"
}
[/IMG]
[/IMG]
IF YOU LIKE MY JOB BUY ME A BEER
[/CENTER]
STEP 2
WARNING!
MAKE BACKUP FROM CWM BEFORE PROCCED
pimpup edition
new pimpup 7 update
Download from here
http://www.mediafire.com/?31toc9d0mybzzh3
Changelog
Added supercharger
Added ips matrix settings
Added 0db noise text when plug headset
And other usefuell things...
New invert gapps include new gmail 4.2 with pinch to zoom and swipe to delete
Make a backup before procced with tittanium app
To install will do fully wipe and will loose all apk!!!!
To install must do
Download from here
http://www.mediafire.com/?ywow63lwivf4i18
1 copy new gapps to sd card
2 go cwm mount system and format system
3 do data factory reset
4 flash new pimpup rom
5 boot first time and check if talk app has been installed
6 reboot to cwm and flash new gapps
7 wipe dalvik cache
Done
New dark theme with ics color its something that worth
The difficult was talk apk so proceed step by step otherwise will loose talk apk
Have fun!!!
Pimpup
download from here
http://www.mediafire.com/?24cymzxexec9kwd
changelog
the most amazing pimp script added
superbassbeats
float touchscreen
wifi and 3g devices support
if 3g doesnt work return to ote and make wipe data cache
first boot takes longer
wifi user turn off data
update 1.5
download from here
http://www.mediafire.com/?zwj1tfypabfubss
changelog
added new overclocking script
added original latest walkman player from sony with you tube tweaks
update 1.4
download from here
http://www.mediafire.com/?cz6x3y9x3lkad6c
changelog
added latest ics browser
added new kernel modules
ntfs support!!!
cifs support
sound improved
wifi improved
fingerprint improved
added latest busybox
added google music player for usb play
apollo removed
compitible with more games ie gameloft
update fix 1.3
download from here
http://www.mediafire.com/?6i2kuwyk2dnv2y6
changelog
cpu sleeper.apk added
http://forum.xda-developers.com/showthread.php?t=1745132
this is earlier kernel(than drh kernel) based to this tweak but for reason does not work properbly
enable service and boot this will fix sleep and rotate bug
work perfect with init.d tweaks i have added
added new build.prop as stand alone rom
if you want right mount after enable memmory i have attachment
right voldstab
unrar and
with root explorer paste at etc and give rw permission
reboot
not overheat fix
try it the pure aosp built in with cm9 tweaks
last fix
the main system has update with better comands
the plus of kernel built is that commands is straight from boot
whyberg did it an gave us that tweks you will receive from update
the update use half daemons so the steps should be from the begining
first rom then update
plus
no sleep reboots
wifi steady
wifi & 3g both working
With download mode
fast !!! Very Fast!!!!and stable
Best perfomance
dont use supercharger or root apps will wipe dalvik cache
you will receive phone error take backup before update
neuro friend should take update
kernel and rom are same
same problems same solves
have fun[/COLOR]
the third step is unlock memmory
ihave add two txt at attachment files for mount sdcard
you must have a copy of real-fat32.img from nvflash folder to the root of sdcard
open terminal type su
copy paste comands
and reboot
And all this is done, I needed a customized mode ADB on a PC connected to the tablet PC, tablet inserted into MicroSD card, and file real_fat32.img, abandoned to the root of MicroSD (see attach). So:
1. Enters the ADB (I have Win XP, I went through Start -> Run -> Cmd)
2. Run ADB - consistently serving team "ADB devices" (get the code connected device - it will not need, just confirmation. Device is connected), and "ADB shell" - to turn on the console.
3. Serve command "mount", the screen falls list mounted devices, the end will be a line like / dev/block/vold/179: 9 / mnt / microsd ..... (In fact, we need only the inscription / mnt / microsd)
4. Write the command "dd if = / mnt/microsd/real_fat32.img of = / dev/block/mmcblk0p7" (this command overwrites the disk image to 4.77 GB while a malfunctioning device / dev/block/mmcblk0p7. So we are making the proper recording of the file system on the device sdcard, which after flash unfortunately incorrect. And a self-memory sdcard becomes 4.77 GB. Dubbing lasts for some time, with no message is not displayed, but you must wait for the final completion message recording. come out on the screen something like: ... bytes transferred in ..... secs (....... bytes / sec))
5. Sdcard install command - mount-t vfat / dev/block/mmcblk0p7 / mnt / sdcard
6. Reboot your tablet.
And it's all
PS If you suddenly reboot internal memory again not read correctly - download tablet mode CWM, look in the engineering menu "format emmc" (not to be confused with the sdcard - in the engineering menu sdcard - this card MicroSD, and emmc - internal memory), and then check that the internal memory is available - consistently perform in the engineering menu command "mount emmc" and "unmount emmc" - both teams have performed well
Step 3 post taken from 4pda/forum assistant07 author
Thanks for that.. one rom and one update in two days.. Great !
I've been trying it and except for the low memory space, this is very great ! I wil install the update as soon as it is downloaded but even without update, the rom was work quite nicely..
I've just finished downloading and installing your update.. Nice... The tablet now wake up much faster from the sleeping mode.. And it seems it boot faster as well.. Good update... Well done, really happy with it...
Does 3G and camera work?
cociuba said:
Does 3G and camera work?
Click to expand...
Click to collapse
No camera
No hdmi
No mic
All others work great
cociuba said:
Does 3G and camera work?
Click to expand...
Click to collapse
I never use the 3G, so i dont know if it is working.. But the camera isnt.. But to be honest, I never really used the camera on this tablet. The quality of it isnt great.... So, it wasnt a no-go for me not to have it working.. And the same goes for 3G. I'm always using wifi to connect on internet.
Honestly, i tried all he different roms that's been going on that site in the recent years, and before any ICS rom came out, i never kept any of them. After playing a little bit with them, i'd always reverted back to the stock version. There was always something i didnt like, something that bothered me... It was either the status bar, the display, the orientation problem..
But since geowolf1000 shared with us this new CM9 rom, i havent even thought once about reverted back to the old stock rom.
In my opinion, if the camera not working isnt a problem for me, just give it a try, you may like it...
The only drawback that may refrain you from flashing that rom, maybe, for the moment, the limited memory space allocated to new apps. there is only 250 Mb....
So, if you want to install large apps, it will be full quite quickly. And this is, in my opinion, the only drawback of that rom.
But like i said in another post, if you only use your tablet to surf internet, to go on youtube, read your mails, watch movies, maybe read comics, books or magazines, that rom will be a delight to use, promise.
On mine, I've install the following apps : Adobe Flash Player, Better Keyboard, Google Currents, Digi Clock widget, Dropbox, Facebook, Freecell, Maps + Street View, Mx Player and its codec, Perfect Viewer and its PDF plugin, Adobe Photoshop Touch, Solid Explorer, Wallbase, Wifiwidget and Youtube app...
And so far, I've used 200 MB and i've got 52 MB free....
i think now download problem has been fix
update with new fix
when start only once turn off and turn on wifi anf signal change color
Do anybody has downloaded stock ROM for our devices?
It seems file:
ht*p://112.5.164.225/tablePC/T8_nvflash_emmc_WCDMA_20110524.rar
on malzata.com download page is offline/deleted.
kedziu said:
Do anybody has downloaded stock ROM for our devices?
It seems file:
ht*p://112.5.164.225/tablePC/T8_nvflash_emmc_WCDMA_20110524.rar
on malzata.com download page is offline/deleted.
Click to expand...
Click to collapse
Hope this helps :
https://dl.dropbox.com/u/33159207/T8_nvflash_emmc_WCDMA_20110524.rar
dont hezitate to post bug
The reboots remain?
Cociuba the 3g working?
Did you download from 3g?
I am to 2ond day with 3d update and all working smoothlie
If reboots remain go to advance of wifi menu and trigger never of wifi sleep mode
It reboot every some times like wifi scan interval
Trigger never so at sleep time and that will disable scan
I hope that update been usefull
Thanks
I've just have a question :
Where can we find real_fat32.img ? is it the same one as the real_fat32.img in the T8_nvflash_emmc_WCDMA_20110524.rar archive or is it another one ?
obeguin said:
I've just have a question :
Where can we find real_fat32.img ? is it the same one as the real_fat32.img in the T8_nvflash_emmc_WCDMA_20110524.rar archive or is it another one ?
Click to expand...
Click to collapse
Yes is rhe same
I am still fighting with flashing new ROM..
i have'nt problems with AOSP 4.0.4 ics rom for malata t8(smba_9701)mcc expect problem with META-INF - the same what had obeguin member. After change META-INF flashing was OK and system also works perfect.
Now i am trying to flash NEURA rom and i have problems during the installation process. I will try to describe as detailed as i can.
go APX
nv flash T8_nvflash_emmc_WCDMA_20110524 (download_EMMC_512)
start the system and do 'privacy options' - 'factory data reset' (system is rebooting..)
go APX
nv flash xdownload.WIFI (i have version 3G but with 512MB memory, xdownload.3G - is not working with my tablet)
go recovery 5.5.0.4 and wipe cache partition
--Wiping cache...
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p4
Cache wipe compleate.
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
reboot recovery 5.5.0.4
install zip from sdcard - choose zip from sdcard - cm9-20120610-u«UNOFFICIAL.zip
-- Instaling
E:cant mount /cache/recovery/last_install
E:filed to open last_install: no such file or directory
Finding update packege..
opening update package..
instaling update
install from sdcard complete.
all process take 20sec (realy fast)
next gapps-ics-20120317-signed.zip
wipe data
--wiping data..
formating /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p6
formating /cache..
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p4
formating /sd-ext
formating /sdcard/.android_secure..
data wipe complete.
reboot and stack on nvidia splash screen...
could anybody tell me where i am making fault?
kedziu said:
I am still fighting with flashing new ROM..
i have'nt problems with AOSP 4.0.4 ics rom for malata t8(smba_9701)mcc expect problem with META-INF - the same what had obeguin member. After change META-INF flashing was OK and system also works perfect.
Now i am trying to flash NEURA rom and i have problems during the installation process. I will try to describe as detailed as i can.
go APX
nv flash T8_nvflash_emmc_WCDMA_20110524 (download_EMMC_512)
start the system and do 'privacy options' - 'factory data reset' (system is rebooting..)
go APX
nv flash xdownload.WIFI (i have version 3G but with 512MB memory, xdownload.3G - is not working with my tablet)
go recovery 5.5.0.4 and wipe cache partition
--Wiping cache...
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p4
Cache wipe compleate.
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
reboot recovery 5.5.0.4
install zip from sdcard - choose zip from sdcard - cm9-20120610-u«UNOFFICIAL.zip
-- Instaling
E:cant mount /cache/recovery/last_install
E:filed to open last_install: no such file or directory
Finding update packege..
opening update package..
instaling update
install from sdcard complete.
all process take 20sec (realy fast)
next gapps-ics-20120317-signed.zip
wipe data
--wiping data..
formating /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p6
formating /cache..
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p4
formating /sd-ext
formating /sdcard/.android_secure..
data wipe complete.
reboot and stack on nvidia splash screen...
could anybody tell me where i am making fault?
Click to expand...
Click to collapse
download again from here
http://www.mediafire.com/?dyjec4wzyskivsd
geowolf1000 said:
the third step is unlock memmory
And all this is done, I needed a customized mode ADB on a PC connected to the tablet PC, tablet inserted into MicroSD card, and file real_fat32.img, abandoned to the root of MicroSD (see attach). So:
1. Enters the ADB (I have Win XP, I went through Start -> Run -> Cmd)
2. Run ADB - consistently serving team "ADB devices" (get the code connected device - it will not need, just confirmation. Device is connected), and "ADB shell" - to turn on the console.
3. Serve command "mount", the screen falls list mounted devices, the end will be a line like / dev/block/vold/179: 9 / mnt / microsd ..... (In fact, we need only the inscription / mnt / microsd)
4. Write the command "dd if = / mnt/microsd/real_fat32.img of = / dev/block/mmcblk0p7" (this command overwrites the disk image to 4.77 GB while a malfunctioning device / dev/block/mmcblk0p7. So we are making the proper recording of the file system on the device sdcard, which after flash unfortunately incorrect. And a self-memory sdcard becomes 4.77 GB. Dubbing lasts for some time, with no message is not displayed, but you must wait for the final completion message recording. come out on the screen something like: ... bytes transferred in ..... secs (....... bytes / sec))
5. Sdcard install command - mount-t vfat / dev/block/mmcblk0p7 / mnt / sdcard
6. Reboot your tablet.
And it's all
PS If you suddenly reboot internal memory again not read correctly - download tablet mode CWM, look in the engineering menu "format emmc" (not to be confused with the sdcard - in the engineering menu sdcard - this card MicroSD, and emmc - internal memory), and then check that the internal memory is available - consistently perform in the engineering menu command "mount emmc" and "unmount emmc" - both teams have performed well
Click to expand...
Click to collapse
Ok, i managed to install ADB and used ADB.
I install real_fat32.img onto my SD card. And then, to the root of the internal memory - recognized asSD card on the malata -
then, I run the following command :
mount
dd if=/mnt/microsd/real_fat32.img of=/dev/block/mmcblk0p7
mount -t vfat /dev/block/mmcblk0p7 /mnt/sdcard
reboot
I didnt see any differences.. I even rebooted in recovery mode, Format emmc and still, no differences...
I mean, the internal memory is still recognized as SD card, and vice versa.. And still only have 250 MB for my apps..
What was it supposed to do ?
You have nvflash whyberg kernel
Download from 1page again and nvflash neuro kernel
Neuro kernel has 1.9 capacity
Follow step again
geo I've followed yours instruction and everythink is working fine. thanks!
I am wondering if we can add mounting sdcard to initr.d?
now I need to type in console:
mount -t vfat /dev/block/mmcblk0p7 /mnt/sdcard
every time I boot android.
kedziu said:
geo I've followed yours instruction and everythink is working fine. thanks!
I am wondering if we can add mounting sdcard to initr.d?
now I need to type in console:
mount -t vfat /dev/block/mmcblk0p7 /mnt/sdcard
every time I boot android.
Click to expand...
Click to collapse
Ooooooohhhhhh.. It goes back to normal, each time you reboot the tablet ?
Maybe that's why it wasnt working then. Because each time, I was trying to reboot the tablet but when i checked my memory, it wasnt working. There was always a problem.. I never checked my memory before reboot.. Only after rebooting and i couldnt understand why it was working...
So, tonight i'll check what happen before rebooting...
And to run the command at each reboot.. I think there may be a solution but I havent try it...
But on google play, there is an app call smanager ( it stands for Script manager ) and it is an applictaion to execute scripts at boot..
So, i think it should be possible to run the command at boot...
save line below in text file, no file extension
mount -t vfat /dev/block/mmcblk0p7 /mnt/sdcard
use play store app: "smanager" free, to run script on boot + su
Click to expand...
Click to collapse
But I havent try yet, but i will try it tonight...
smanager is working fine
you need to create text file with lines:
#!/system/bin/sh
mount -t vfat /dev/block/mmcblk0p7 /mnt/sdcard
save and get permisions to execute.
in smanager you have to give attributes boot and su.
Just for know
Last update can be stand alone rom
Nothing change and don't need to do it again
If ever need to update again only last after kernel,now you know my rom .
You can restore
Ok
{
"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.
All of TWRP 3.x source is public. You can compile it on your own. This guide isn't going to be a step-by-step, word-for-word type of guide. If you're not familiar with basic Linux commands and/or building in AOSP then you probably won't be able to do this.
You can currently use Omni 6.0, Omni 7.1, Omni 8.1, Omni 9.0, CM 13.0, CM 14.1, CM 15.1, LineageOS 16.0 source code. Omni 9.0 is recommended for now unless your device has a super partition.
If you are using CM/LineageOS, you'll need to place TWRP in the LineageOS/bootable/recovery-twrp folder and set RECOVERY_VARIANT := twrp in your BoardConfig.mk file. TWRP source code can be found here:
https://github.com/TeamWin/android_bootable_recovery (NOTE: The location for the latest TWRP source code has changed!)
Select the newest branch available. This step is not necessary with Omni because Omni already includes TWRP source by default, however, if you are using an older version of Omni, you will probably want to pull from the latest branch (the latest branch will compile successfully in older build trees)
If you are only interested in building TWRP, you may want to try working with a smaller tree. You can try using this manifest. It should work in most cases but there may be some situations where you will need more repos in your tree than this manifest provides:
https://github.com/minimal-manifest-twrp
*BEFORE YOU COMPILE*
Note: If you add or change any flags, you will need to make clean or make clobber before recompiling or your flag changes will not be picked up.
Now that you have the source code, you'll need to set or change a few build flags for your device(s). Find the BoardConfig.mk for your device. The BoardConfig.mk is in your devices/manufacturer/codename folder (e.g. devices/lge/hammerhead/BoardConfig.mk).
Your board config will need to include architecture and platform settings. Usually these are already included if you're using device configs that someone else created, but if you created your own, you may need to add them. Without them, recovery may seg fault during startup and you'll just see the teamwin curtain flash on the screen over and over.
We usually put all of our flags at the bottom of the BoardConfig.mk under a heading of #twrp For all devices you'll need to tell TWRP what theme to use. This TW_THEME flag replaces the older DEVICE_RESOLUTION flag. TWRP now uses scaling to stretch any theme to fit the screen resolution. There are currently 5 settings which are: portrait_hdpi, portrait_mdpi, landscape_hdpi, landscape_mdpi, and watch_mdpi. For portrait, you should probably select the hdpi theme for resolutions of 720x1280 and higher. For landscape devices, use the hdpi theme for 1280x720 or higher.
TW_THEME := portrait_hdpi
Note that themes do not rotate 90 degrees and there currently is no option to rotate a theme. If you find that the touchscreen is rotated relative to the screen, then you can use some flags (discussed later in this guide) to rotate the touch input to match the screen's orientation.
In addition to the resolution, we have the following build flags:
RECOVERY_SDCARD_ON_DATA := true -- this enables proper handling of /data/media on devices that have this folder for storage (most Honeycomb and devices that originally shipped with ICS like Galaxy Nexus) This flag is not required for these types of devices though. If you do not define this flag and also do not include any references to /sdcard, /internal_sd, /internal_sdcard, or /emmc in your fstab, then we will automatically assume that the device is using emulated storage.
BOARD_HAS_NO_REAL_SDCARD := true -- disables things like sdcard partitioning and may save you some space if TWRP isn't fitting in your recovery patition
TW_NO_BATT_PERCENT := true -- disables the display of the battery percentage for devices that don't support it properly
TW_CUSTOM_POWER_BUTTON := 107 -- custom maps the power button for the lockscreen
TW_NO_REBOOT_BOOTLOADER := true -- removes the reboot bootloader button from the reboot menu
TW_NO_REBOOT_RECOVERY := true -- removes the reboot recovery button from the reboot menu
RECOVERY_TOUCHSCREEN_SWAP_XY := true -- swaps the mapping of touches between the X and Y axis
RECOVERY_TOUCHSCREEN_FLIP_Y := true -- flips y axis touchscreen values
RECOVERY_TOUCHSCREEN_FLIP_X := true -- flips x axis touchscreen values
TWRP_EVENT_LOGGING := true -- enables touch event logging to help debug touchscreen issues (don't leave this on for a release - it will fill up your logfile very quickly)
BOARD_HAS_FLIPPED_SCREEN := true -- flips the screen upside down for screens that were mounted upside-down
There are other build flags which you can locate by scanning the Android.mk files in the recovery source. Most of the other build flags are not often used and thus I won't document them all here.
*RECOVERY.FSTAB*
TWRP 2.5 and higher supports some new recovery.fstab features that you can use to extend TWRP's backup/restore capabilities. You do not have to add fstab flags as most partitions are handled automatically.
Note that TWRP only supports v2 fstabs in version 3.2.0 and higher. You will still need to use the "old" format of fstab for older TWRP (example of that format is below), and even TWRP 3.2.0 still supports the v1 format in addition to the v2 format. To maximize TWRP's compatibility with your build tree, you can create a twrp.fstab and use PRODUCT_COPY_FILES to place the file in /etc/twrp.fstab When TWRP boots, if it finds a twrp.fstab in the ramdisk it will rename /etc/recovery.fstab to /etc/recovery.fstab.bak and then rename /etc/twrp.fstab to /etc/recovery.fstab. Effectively this will "replace" the fstab 2 file that your device files are providing with the TWRP fstab allowing you to maintain compatibility within your device files and with other recoveries.
Code:
PRODUCT_COPY_FILES += device/lge/hammerhead/twrp.fstab:recovery/root/etc/twrp.fstab
The fstab in TWRP can contain some "flags" for each partition listed in the fstab.
Here's a sample TWRP fstab for the Galaxy S4 that we will use for reference:
Code:
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system
/data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata length=-16384
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery
/efs ext4 /dev/block/platform/msm_sdcc.1/by-name/efs flags=display="EFS";backup=1
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="Micro SDcard";storage;wipeingui;removable
/usb-otg vfat /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable
/preload ext4 /dev/block/platform/msm_sdcc.1/by-name/hidden flags=display="Preload";wipeingui;backup=1
/modem ext4 /dev/block/platform/msm_sdcc.1/by-name/apnhlos
/mdm emmc /dev/block/platform/msm_sdcc.1/by-name/mdm
Flags are added to the end of the partition listing in the fstab separated by white space (spaces or tabs are fine). The flags affect only that partition but not any of the others. Flags are separated by semicolons. If your display name is going to have a space, you must surround the display name with quotes.
Code:
/external_sd vfat /dev/block/mmcblk1p1 flags=display="Micro SDcard";storage;wipeingui;removable
The flags for this partition give it a display name of "Micro SDcard" which is displayed to the user. wipeingui makes this partition available for wiping in the advanced wipe menu. The removable flag indicates that sometimes this partition may not be present preventing mounting errors from being displayed during startup. Here is a full list of flags:
removable -- indicates that the partition may not be present preventing mounting errors from being displayed during boot
storage -- indicates that the partition can be used as storage which makes the partition available as storage for backup, restore, zip installs, etc.
settingsstorage -- only one partition should be set as settings storage, this partition is used as the location for storing TWRP's settings file
canbewiped -- indicates that the partition can be wiped by the back-end system, but may not be listed in the GUI for wiping by the user
userrmrf -- overrides the normal format type of wiping and only allows the partition to be wiped using the rm -rf command
backup= -- must be succeeded by the equals sign, so backup=1 or backup=0, 1 indicates that the partition can be listed in the backup/restore list while 0 ensures that this partition will not show up in the backup list.
wipeingui -- makes the partition show up in the GUI to allow the user to select it for wiping in the advanced wipe menu
wipeduringfactoryreset -- the partition will be wiped during a factory reset
ignoreblkid -- blkid is used to determine what file system is in use by TWRP, this flag will cause TWRP to skip/ignore the results of blkid and use the file system specified in the fstab only
retainlayoutversion -- causes TWRP to retain the .layoutversion file in /data on devices like Sony Xperia S which sort of uses /data/media but still has a separate /sdcard partition
symlink= -- causes TWRP to run an additional mount command when mounting the partition, generally used with /data/media to create /sdcard
display= -- sets a display name for the partition for listing in the GUI
storagename= -- sets a storage name for the partition for listing in the GUI storage list
backupname= -- sets a backup name for the partition for listing in the GUI backup/restore list
length= -- usually used to reserve empty space at the end of the /data partition for storing the decryption key when Android's full device encryption is present, not setting this may lead to the inability to encrypt the device
canencryptbackup= -- 1 or 0 to enable/disable, makes TWRP encrypt the backup of this partition if the user chooses encryption (only applies to tar backups, not images)
userdataencryptbackup= -- 1 or 0 to enable/disable, makes TWRP encrypt only the userdata portion of this partition, certain subfuldes like /data/app would not be encrypted to save time
subpartitionof= -- must be succeeded by the equals sign and the path of the partition it is a subpartition of. A subpartition is treated as "part" of the main partition so for instance, TWRP automatically makes /datadata a subpartition of /data. This means that /datadata will not show up in the GUI listings, but /datadata would be wiped, backed up, restored, mounted, and unmounted anytime those operations are performed on /data. A good example of the use of subpartitions is the 3x efs partitions on the LG Optimus G:
Code:
/efs1 emmc /dev/block/mmcblk0p12 flags=backup=1;display=EFS
/efs2 emmc /dev/block/mmcblk0p13 flags=backup=1;subpartitionof=/efs1
/efs3 emmc /dev/block/mmcblk0p14 flags=backup=1;subpartitionof=/efs1
This lumps all 3 partitions into a single "EFS" entry in the TWRP GUI allowing all three to be backed up and restored together under a single entry.
As of TWRP 3.2.0, TWRP now supports a version 2 fstab like those that have been found in Android devices for years. Yes, I know we're really slow to adopt this one, but I also saw no major advantage to v2 and the v2 fstab was being used in regular Android as well as recovery and I didn't want full ROM builds crashing or doing other weird things because of TWRP flags being present in the fstab. Version 2 fstab support is automatic. You don’t need to add any build flags. The regular version 1 fstab format is also still valid and it’s possible to use both v1 and v2 types in the same fstab. TWRP 3.2.0 also supports using wildcards via the asterisk in v1 format which can be useful for USB OTG and micro SD cards with multiple partitions. Note also that v2 fstab formats haven’t been extensively tested so developers should test their v2 fstabs before shipping to users (you should always be testing anyway!).
This is a v1 fstab line with a wildcard intended for a USB OTG drive. All partitions should show up in the list of available storage devices when the user plugs in a drive:
Code:
/usb-otg vfat /dev/block/sda* flags=removable;storage;display=USB-OTG
This line is straight from the v2 fstab for the same device and also should work. In this case the kernel will notify us that new devices have been added or removed via uevents:
Code:
/devices/soc.0/f9200000.ssusb/f9200000.dwc3/xhci-hcd.0.auto/usb* auto auto defaults voldmanaged=usb:auto
In addition to the v2 fstab, you can include /etc/twrp.flags which uses the v1 fstab format. The twrp.flags file can be used to supplement the v2 fstab with TWRP flags, additional partitions not included in the v2 fstab, and to override settings in the v2 fstab. For example, I have a Huawei device with the following stock v2 fstab present as /etc/recovery.fstab
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1 wait,verify
/dev/block/bootdevice/by-name/cust /cust ext4 ro,barrier=1 wait,verify
/devices/hi_mci.1/mmc_host/mmc1/* auto auto defaults voldmanaged=sdcard:auto,noemulatedsd
/devices/hisi-usb-otg/usb1/* auto auto defaults voldmanaged=usbotg:auto
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,forceencrypt=footer,check
/dev/block/bootdevice/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,data=ordered wait,check
/dev/block/bootdevice/by-name/splash2 /splash2 ext4 rw,nosuid,nodev,noatime,data=ordered,context=u:object_r:splash2_data_file:s0 wait,check
/dev/block/bootdevice/by-name/secure_storage /sec_storage ext4 rw,nosuid,nodev,noatime,discard,auto_da_alloc,mblk_io_submit,data=journal,context=u:object_r:teecd_data_file:s0 wait,check
In addition I have also included this in /etc/twrp.flags:
Code:
/boot emmc /dev/block/platform/hi_mci.0/by-name/boot
/recovery emmc /dev/block/platform/hi_mci.0/by-name/recovery flags=backup=1
/cust ext4 /dev/block/platform/hi_mci.0/by-name/cust flags=display="Cust";backup=1
/misc emmc /dev/block/platform/hi_mci.0/by-name/misc
/oeminfo emmc /dev/block/platform/hi_mci.0/by-name/oeminfo flags=display="OEMinfo";backup=1
/data f2fs /dev/block/dm-0
/system_image emmc /dev/block/platform/hi_mci.0/by-name/system
The first 2 lines in twrp.flags adds the boot and recovery partitions which were not present at all in the v2 fstab. The /cust line in the twrp.flags file is added to tell TWRP to allow users to back up the cust partition and to give it a slightly better display name. The /misc partition is also only present in the twrp.flags file. Much like the /cust partition, the /oeminfo partition is in the twrp.flags file to tell TWRP to allow users to back it up and give a display name. The /data line is needed because this Huawei device, like many Huawei devices, is encrypted but the encryption uses some special Huawei binaries and is encrypted with some sort of default password that the user cannot change. We use the Huawei binaries to decrypt the device automatically in recovery. The /data line here tells TWRP to use /dev/block/dm-0 instead of /dev/block/bootdevice/by-name/userdata which is required for proper mounting, etc. Lastly we have the /system_image line so that TWRP will add a system image option for backup and restore.
As we add more new devices, we’ll add more example device trees to https://github.com/TeamWin/ which should help you find more ways to use this new fstab support. Please note that using the v2 fstab format at this point is completely optional, so feel free to continue using v1 if that is what is more comfortable or if you have trouble with the v2 format support.
If you have questions, feel free to stop by #twrp on Freenode. If you post here I may not see it for a while as I have lots of threads out there and there's no way for me to keep track of them all. If you successfully port TWRP to a new device, please let us know! We love to hear success stories!
If you have code changes that you'd like to submit, please submit them through the Omni Gerrit server. Guide is here.
Once you get Omni or CM sync'ed and your TWRP flags set, you should do a source ./build/envsetup.sh We usually lunch for the device in question, so something like "lunch omni_hammerhead-eng".
After you lunch successfully for your device this is the command used for most devices:
Code:
make clean && make -j# recoveryimage
Replace the # with the core count +1, so if you have a dual core it's -j3 and a quad core becomes -j5, etc. If you're dealing with a "typical" Samsung device, then you'll need to
Code:
make -j# bootimage
Most Samsung devices have the recovery included as an extra ramdisk in the boot image instead of a separate recovery partition as found on most other devices.
Old guide here: http://forum.xda-developers.com/showpost.php?p=65482905&postcount=1471
So, now, hopefully you've compiled TWRP for your device and gotten it working. Now, you'd like to know how to get TWRP officially supported for your device so that it can be installed automatically with the TWRP app. In order for us to add "official support" for your device we'll need the following:
1) Device configuration files to compile TWRP from source for your device. This means that you cannot have repacked a recovery.img by hand to get it working. We need to be able to compile it from source so that we can easily release future updates.
2) We'll build a copy of TWRP and send it to you for validation. Once you've validated that we can build a working image for your device, we'll add it to the official TWRP app.
Note that we won't take credit for your port. You'll still get to post it on XDA to collect all the credit that goes with releasing something new for your device along with having your name listed on our website as the maintainer for the device. Also note that it's not always possible to provide automated installs for all devices.
You can now boot TWRP in an emulator. If you're trying to help develop TWRP, this can be a huge help as you don't have to risk your device and you can do everything directly on your computer.
{
"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"
}
Download this set of device configuration files.
Compile a recoveryimage using those device files. In the Android SDK, click on Tools -> Manage AVDs. Click New. Set it up as the following:
AVD Name: TWRP
Device: Galaxy Nexus
Target: ICS or newer though anything will probably work here
CPU: ARM (armeabi-v7a)
Check the box for hardware keyboard (your computer's keyboard will work in TWRP)
Up to you if you want to have the skin with controls present
Front Camera: None
Back Camera: None
RAM: 1024 VM Heap: 64
Internal Storage: 200
SD Card: Size: 500 MiB
Then click OK.
Once you have your AVD and your recoveryimage, you can boot TWRP in the emulator by browsing to your android-sdk/tools folder and run this command:
./emulator -avd TWRP -ramdisk CMFOLDER/out/target/product/twrp/ramdisk-recovery.img
Note that ADB doesn't work right away. About 10 to 15 seconds after TWRP finishes booting, ADB will come online. We start ADB via init.rc so even if TWRP fails to boot due to some kind of code error that you may have made, ADB should still work. Enjoy!
TWRP and A/B devices:
From a TWRP standpoint, A/B devices aren't a whole lot different from regular devices, but developers seem to be shy about working on these devices. I'm going to try to shed some light on this subject and hopefully this will serve as a guide for porting TWRP to A/B devices.
Firstly, let's understand what is an A/B device and how it's different. A/B devices have duplicates of many partitions on the device. An A/B device has 2x system partitions, 2x boot partitions, 2x vendor partitions, 2x modem / firmware partitions, etc. Only one slot is in use at a time. During early boot, the first stages of the bootloader read some small amount of data called the BCB or Bootloader Control Block and decide whether to boot the A partitions or the B partitions. When an OTA update is available, the data from the active slot is copied from the inactive slot and patched / updated. For example, if you're currently on slot A, your device would download the update and copy the existing system partition from slot A and patch / update it with the new updates into slot B. Once the copying and updating is complete, the BCB is updated and the device reboots using slot B. Next time an update is available, the system partition in slot B is copied to slot A and updated, the BCB gets updated, and we reboot to slot A. When viewing partitions on the device, you'll see something like this:
Code:
/dev/block/bootdevice/by-name/boot_a
/dev/block/bootdevice/by-name/boot_b
/dev/block/bootdevice/by-name/system_a
/dev/block/bootdevice/by-name/system_b
/dev/block/bootdevice/by-name/userdata
/dev/block/bootdevice/by-name/vendor_a
/dev/block/bootdevice/by-name/vendor_b
Note the dual boot, system and vendor partitions in the list above, but only one userdata partition.
While there is technically no requirement that I am aware of, all A/B devices shipped thus far have no separate recovery partition. Instead, the boot image contains the recovery in its ramdisk. The important thing is knowing that the boot image now also contains the recovery. For completeness, the system partition is a full root file system. During boot, if the kernel is told to boot to recovery, it will extract the ramdisk in the boot partition. If the kernel is not told by the bootloader to boot to recovery, then the kernel will mount the appropriate system partition (A or B) because the system partition is a full root file system. This means that the system partition on these devices is mounted to / instead of to /system and the system partition contains all of the files that would have normally been in the boot image ramdisk and a /system subfolder.
From a TWRP standpoint, there are 3 things that you have to do for an A/B device. First, you need to set
Code:
AB_OTA_UPDATER := true
in your BoardConfig.mk. Secondly, for any partition that has an A/B option, you need to add
Code:
flags=slotselect
in your fstab so something like this:
Code:
/boot emmc /dev/block/bootdevice/by-name/boot flags=slotselect
/system ext4 /dev/block/bootdevice/by-name/system flags=slotselect
/system_image emmc /dev/block/bootdevice/by-name/system flags=slotselect
/vendor ext4 /dev/block/bootdevice/by-name/vendor flags=slotselect;display="Vendor";backup=1
/vendor_image emmc /dev/block/bootdevice/by-name/vendor flags=slotselect
Lastly, once you get into TWRP, you will probably want to make sure that bootctl hal-info responds correctly with no errors. Usually the bootctl binary requires a proprietary library or even a couple of services to work correctly. If bootctl does not work correctly, then you will not be able to switch slots within TWRP correctly either.
In addition to setting
Code:
AB_OTA_UPDATER := true
you may also want to set:
Code:
BOARD_USES_RECOVERY_AS_BOOT := true
BOARD_BUILD_SYSTEM_ROOT_IMAGE := true
If you set
Code:
BOARD_USES_RECOVERY_AS_BOOT := true
then make recoveryimage will no longer work and instead you will have to make bootimage. I don't recommend setting either of these flags for TWRP-only build trees. These flags will probably be required for developers building full ROMs for A/B devices.
Installing / Flashing TWRP on A/B devices:
Since all known A/B devices do not have a separate recovery partition, you will eventually have to flash TWRP to the boot partition. On the Pixel 1 and 2, we use fastboot boot to temporarily boot TWRP without flashing TWRP. We are then supplying a zip to allow users to flash TWRP to both slots. You can download one of these zips from our website and update the zip as needed to support your devices. Eventually we will add tools to TWRP to allow users to flash recoveries on these devices without needing to use zips.
Recently, I worked on the Razer Phone. The Razer Phone unfortunately does not support fastboot boot. Instead, users have to determine their currently active boot slot using
Code:
adb shell getprop ro.boot.slot_suffix
then use
Code:
fastboot --set-active=_a
to switch slots to the inactive slot. From here, the user can
Code:
fastboot flash boot twrp.img && fastboot reboot
to get into TWRP. Once in TWRP they can then go to the reboot page and change back to their originally active slot, make a backup, then install TWRP. Using the inactive slot allows users to get a good, unmodified backup of their device before installing TWRP.
Hopefully this helps!
Debugging with gdb in TWRP guide can be found here!
Beep boop zee doop
I know I've PM'ed you but I would like to ask you again. What should I do after compiling the TWRP recovery binary? What files have to be copied and where? I'm trying to integrate it with an ICS kernel.
Dees_Troy said:
Once you get CM sync'ed, I suggest that you go ahead and compile a build of ClockworkMod (ClockworkMod source is included in the CM repos). We usually lunch for the device in question, so something like "lunch full_tenderloin-eng".
After you lunch successfully for your device this is the command used for most devices:
Code:
make clean && make -j# recoveryimage
Click to expand...
Click to collapse
I don't get this part. What is lunch supposed to be? is it supposed to be a individual command for a device or can I do "lunch full_tenderloin-eng" for all devices? Because I am building for a device that doesn't run Android natively (at least out of-the-box) so cyanogenmod doesn't support it on any way...
Also, can I use this for resistive screens? Just to make sure.
Thanks for the guide, I have been looking for this for a long time
thanks for the guide, well structured and not so complicated
i have only a question: i'm trying to build it for galaxy 5, the problem is that the resolution is 320x240, so can you tip me on modify the sources? (i've done this some days ago, but images were too large)
manuel100 said:
thanks for the guide, well structured and not so complicated
i have only a question: i'm trying to build it for galaxy 5, the problem is that the resolution is 320x240, so can you tip me on modify the sources? (i've done this some days ago, but images were too large)
Click to expand...
Click to collapse
Set the device resolution to 320x240...I'm pretty sure they have support for that resolution...and if they don't then you can copy one of there's except resize it all to 320x240
Edit-they only have 320x480 https://github.com/TeamWin/Team-Win-Recovery-Project/
My question: I built twrp from source a while ago using smasher's Samsung inject twrp zip...that worked fine for a while...but recently we switched to mtd format so that inject twrp zip doesn't work...neither does the inhect twrp button within twrp anymore...I've seen that the galaxy s has the same problem as well...just wondering if you know of a work around...
Sent from my SGH-I997 using Tapatalk 2
mg2195 said:
Set the device resolution to 320x240...I'm pretty sure they have support for that resolution...and if they don't then you can copy one of there's except resize it all to 320x240
Edit-they only have 320x480 https://github.com/TeamWin/Team-Win-Recovery-Project/
My question: I built twrp from source a while ago using smasher's Samsung inject twrp zip...that worked fine for a while...but recently we switched to mtd format so that inject twrp zip doesn't work...neither does the inhect twrp button within twrp anymore...I've seen that the galaxy s has the same problem as well...just wondering if you know of a work around...
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
thanks for respond, however i've tried resizing images to 320x240 but i don't know what should be the size of bottoms, because they are alway out-of-screen
what is smasher's Samsung inject twrp zip? but i think that the recovery doesn't work because you have to built it with mtd support (for ex. on madteam they are trying to build a mtd kernel, but for install that testing rom they built a special cwm with mtd support)
manuel100 said:
thanks for respond, however i've tried resizing images to 320x240 but i don't know what should be the size of bottoms, because they are alway out-of-screen
what is smasher's Samsung inject twrp zip? but i think that the recovery doesn't work because you have to built it with mtd support (for ex. on madteam they are trying to build a mtd kernel, but for install that testing rom they built a special cwm with mtd support)
Click to expand...
Click to collapse
Smashers inject twrp zip is a tool for Samsung devices that let's you get the recovery without flashing the whole kernel. You basically put the ramdisk-recovery.img in the zip and then flash. During the flash process it pulls the boot.img, replaces the current ramdisk-recovery.img with the new one that contains twrp. It then deletes the old boot.img and flashes the new one...not affecting the actual kernel...
The recovery itself has mtd support...I can use it if I flash the whole boot.img, but I don't want to release the recovery within a whole kernel...because then I have to keep it up to date with both twrp and kernel sources, not to mention the different kernels available for my device....I can't make a recovery for each kernel...don't have the time for that...that's where the inject came in handy....the user could use any kernel he wanted while still using twrp
Recovery logs say it fails to find the ramdisk inside the boot.img and then in parenthesis something about may not be using gzip compression...which it is....
Sent from my SGH-I997 using Tapatalk 2
---------- Post added at 07:21 AM ---------- Previous post was at 07:19 AM ----------
Deestroy did this same tutorial on rootzwiki...if you look at the second post you'll see info about the smasher inject twrp I was referring to...http://rootzwiki.com/index.php?/topic/23903-How-to-Compile-TWRP-from-Source
Sent from my SGH-I997 using Tapatalk 2
mfsr98 said:
I don't get this part. What is lunch supposed to be? is it supposed to be a individual command for a device or can I do "lunch full_tenderloin-eng" for all devices? Because I am building for a device that doesn't run Android natively (at least out of-the-box) so cyanogenmod doesn't support it on any way...
Also, can I use this for resistive screens? Just to make sure.
Thanks for the guide, I have been looking for this for a long time
Click to expand...
Click to collapse
can I get help here please?
mfsr98 said:
can I get help here please?
Click to expand...
Click to collapse
Its a single command...it opens up the menu for devices...just type lunch into the terminal and hit enter...you'll see what I mean. You will probably have to add your device to the menu by creating a vendorsetup.sh in your device repo if it doesn't already exist....
Sent from my SGH-I997 using Tapatalk 2
Thank you for the quick answer. Yes, I already have vendorsetup.sh on the boot.img. Sorry for the noob question
What about for android beginners???
Devarishi said:
What about for android beginners???
Click to expand...
Click to collapse
There's only so much that you can dumb it down and simplify it. There's lots of other guides out there for getting started. Compiling a recovery is not a super simple task that anyone and everyone can do and there's plenty of potential pitfalls including the possibility of bricking your device. If none or very little of this guide makes sense, then you might see if a developer for your device is interested in working on it instead.
how would you compile this for a device without an official cm9 build?
azoller1 said:
how would you compile this for a device without an official cm9 build?
Click to expand...
Click to collapse
Well, you don't need official cm9 if you can find any working device tree for you phone you are good to go.. For lg spectrum 4g, this could be useful.
Hey guys I'm trying to compile this for my phone the problem I'm running into is I need the root.ts I've searched and it doesn't come up with anything any help would be appreciated thanks
Sent from my SAMSUNG-SGH-I577 using xda premium
I have a mtk6577 device which is not in de device tree of CM9.
I can compile CWM for my device with CM9. Because I was only making recovery, there was no need for setting up boardconfig.
In this guide there is a part starting with TARGET_RECOVERY_INITRC which is not there in my boardconfig.
Also is stated:
"Your board config also needs to include architecture and platform settings. Usually these are already included if you're using device configs that someone else created, but if you created your own, you may need to add them. Without them, recovery will often seg fault during startup and you'll just see the teamwin curtain flash on the screen over and over."
Does this mean that I cannot build TWRP without it, even I can build CWM ?
gls9 said:
I have a mtk6577 device which is not in de device tree of CM9.
I can compile CWM for my device with CM9. Because I was only making recovery, there was no need for setting up boardconfig.
In this guide there is a part starting with TARGET_RECOVERY_INITRC which is not there in my boardconfig.
Also is stated:
"Your board config also needs to include architecture and platform settings. Usually these are already included if you're using device configs that someone else created, but if you created your own, you may need to add them. Without them, recovery will often seg fault during startup and you'll just see the teamwin curtain flash on the screen over and over."
Does this mean that I cannot build TWRP without it, even I can build CWM ?
Click to expand...
Click to collapse
Look for another mtk6577 device that has CM & copy the arch flags from it.