Related
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
Note from the Author -
I am moving on to the N5 now and ditching my S3. I will continue to maintain this thread, however - please do PM me if you think that something needs to be changed or updated in this thread as I doubt I will be answering questions within the thread as much. Please don't PM support questions to me. Only PM updates that need to be made in the thread.
It's been a blast!
Regards
Dan
Please read this thread. Do not dismiss the "send for repair" option. Please do not create further threads asking for help because "nothing worked". I have included everything we know to be a working fix. If nothing here fixed your issue, send it for repair. Don't create yet another pointless thread like the 10 others a day we have to read...
IMEI
A unique identification number programmed onto your phone. It is required in order to be correctly identified on a mobile network. Without one, you cannot make calls, send SMS or use mobile data. Important stuff.
/efs
A partition on your internal memory containing important data including the IMEI. If the data in this partition gets corrupt, you will lose your IMEI
0049*** or 0000 IMEI
A generic IMEI, meaning your real IMEI is not readable, presumably because it is corrupt but there are other reasons too.
This thread aims to give you as much basic information as possible in an attempt to prevent the 10 - 20 threads we're getting per day about this issue.
I have a 0049 or 0000 IMEI. Why?
This means your phone cannot read your IMEI. There are 2 main reasons for this.
1) /efs is corrupt.
Whenever you flash a ROM, be that a custom ROM via a custom recovery or an official ROM via Odin, you risk corrupting your /efs partition and losing your IMEI.
There are 3 main steps to take to try to resolve this
Restore your EFS from a backup - A logical first step
No backup? Reflash the latest stock ROM using Odin*
Send the device for repair**
*Ultima rom users (prior to v15), first reflash the rom, choosing a non-stock kernel during the aroma install wizard first. Boefla is a good choice to test.
** a couple with "cannot mount /efs" errors have fixed their device by flashing ics. If you know you haven't got a VTU00M eMMC firmware 0xf1 - go for it. However for those of you who don't know, this would be extremely dangerous. You could get SDS so I do not recommend this action. If you are foolish enough to try it, flash 4.1.2 immediately afterwards.
2) /efs partition format changed
A quick note before going forward... when looking at a ROM build number, the last 3 characters mean Year, Month, Revision. Let's take XXEMG4 for example. M = 2013, G = July, 4 = revision 4. See "Other" section at the end of this post for more info
From July 2013 (XXEMG4) onwards, official Samsung ROMs change the format of your EFS Directory/Partition. Let's say these ROMs change from EFS v1 to EFS v2. Only basebands from July 2013 (MG2) onwards can read EFS v2.
Quick info rules:
EFS v2 Basebands can read EFS v2 and EFS v1
EFS v1 basebands CANNOT read EFS v2, ONLY EFS v1
This means if you have flashed an official ROM (or custom ROM based on official) From July 2013 (MG* or newer), you are now in a situation whereby only an EFS v2 baseband (MG* or newer) can read the IMEI in /EFS.
If you have ever flashed XXEMG* (or newer) ROM, to keep your IMEI working, you must:
Stay with the EFS v2 basebands (MG* or newer). You may flash other ROMs but must return to the MG* (or newer) baseband
Restore your EFS backup (taken before XXEMG* or newer ROM install) to use older (EFS v1) basebands. EFS backup must be an EFSv1 backup to use an EFS v1 baseband
If the above don't work, consider sending for repair...
*Ultima rom users (prior to v15), first reflash the rom, choosing a non-stock kernel during the aroma install wizard first. Boefla is a good choice to test.
Please note, it is flashing the ROM that alters EFS format, not the basebands themselves. You can flash the MG* or newer basebands safely on their own and return to an older baseband without issue.
You can download an EFS v2 baseband (CWM) flashable package HERE - updated to MJ3 by @maatsby
Aroma installer, choose between MG2, MG4, MH1 and MJ3 basebands
Basebands alone do not alter efs format
Backs up EFS in an uncompressed format (Use Root Explorer to restore)
Does NOT include RIL, works on AOSP and Sammy
For discussion of the efs format issue, see this thread.
How do I backup and restore /efs?
There are a few methods to backup /efs, but they all require customisation of your phone. Either root access, or a custom recovery. I appreciate that many of you do not wish to root your phones and just want to flash official ROMs via Odin... Well here are your choices:
Only use OTA or KIES to update (Official Method)
Root using CF auto root / Framaroot - backup efs and THEN flash via ODIN
Flash a custom recovery via Odin, backup efs and THEN flash a ROm via Odin
Risk it. Don't backup efs. Simply flash via Odin and hope for the best
...and here are the options for backing up / restoring efs (this list is not exhaustive)
EFS Pro - App needs root
SGSIII EFS backup / Restore - app runs from Windows / Linux and needs root
kTool - app needs root.
Philz advanced CWM rewcovery - custom recovery can take efs backups using the "Custom Backup" feature.
It's worth noting that some custom ROMs will give the option to backup efs, but you can never have too many backups!
.tar and .tar.gz backups can be extracted on /sdcard and then manually used to replace the files in /efs using a root explorer or adb as a last resort. Some people have reported more success deleting the /efs folder contents before hand. This is risky though, so only those of you who can backup the /efs with Philz recovery before trying this - should try it. Why Philz recovery backup the already broken EFS? well you can restore it if the phone doesn't boot and at least you are no worse off than before attempting this method. Messing woith EFS can cause your phone to not boot up so be CAREFUL!!!
Please see below for step-by-step instructions to restore a folder dump* of EFS using adb. Do so at your own risk!!!
This is useful if you cannot boot.
*An example of a folder dump would be an efs backup created using my mg baseband pack linked earlier in this thread.
Pre requisite is having adb "installed" on yoru windows PC. Download THIS file and follow the instructions in the readme.
1) Boot into recovery, connect usb and go to "mounts and storage". Toggle the "mount efs" and "mount data" options to mount these partitions. Tip, when mounted, the option then becomes "unmount x"
2) Open "cmd" in Windows and type "adb shell" to get to your adb prompt.
3) If you don't know where your efs folder dump is, you'll need to look for it using the list command. I know mine is on internal SD but I forget the name of it... (if you already have this on a computer, skip to step 4...
Code:
ls /data/media/0
lists all directories on my internal sd card. I now see it's called MG_EFS
Code:
exit
adb pull /data/media/p/MG_EFS c:\users\rootsu\desktop\MG_EFS
Now your folder dump is on your windows desktop.
It should look like this:
{
"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"
}
Please note at this stage, my MG_EFS contained dated folders each with backups. I took the content of one of these dated folders and dropped them directly inMF_EFS
4) type "adb shell" again to get into adb and check your efs contents is visible
Code:
ls -lh /efs
This will list your efs contents and permissisons:
Code:
-rw-rw-r-- 1 radio radio 152 Jan 1 2012 00000000.authtokcont
drwxr-xr-x 2 system system 4.0K Aug 10 17:37 FactoryApp
drwxrwxr-x 2 radio system 4.0K Aug 10 17:37 bluetooth
drwxrwxr-x 3 drm system 4.0K Aug 10 17:37 drm
-rw-rw-rw- 1 system system 6 Aug 13 2012 gyro_cal_data
-rw-r--r-- 1 radio radio 1.1K Jan 1 2012 h2k.dat
drwxrwxr-x 2 radio system 4.0K Aug 10 17:37 imei
drwx------ 2 root root 4.0K Jan 1 1970 lost+found
-rw------- 1 radio radio 7.6K Sep 10 06:45 nv.log
-rwx------ 1 radio radio 2.0M Sep 10 12:59 nv_data.bin
-rwx------ 1 radio radio 32 Sep 10 12:59 nv_data.bin.md5
drwxrwxr-x 2 radio system 4.0K Aug 10 17:37 wifi
-rw-r--r-- 1 radio radio 220 Jan 1 2012 wv.keys
5) Once confirmed you get a list similar to above (as opposed to nothing) take a screenshot of the files and remove the efs contents...
Code:
rm -Rf /efs/*
and use the list command again to confirm nothing is returned when looking in the efs parrtition
Code:
ls -lh /efs
6) Push your folder dump back to place and ls to check it worked
Code:
exit
adb push c:\users\rootsu\desktop\MG_EFS /efs/
adb shell
ls -lh /efs
7) You will probably notice that the permissions differ to those in your screenshot. If so, paste the below block command to grant the permissions back into the /efs
Code:
chmod 664 /efs/00000000.authtokcont
chmod 755 /efs/FactoryApp
chmod 775 /efs/bluetooth
chmod 775 /efs/drm
chmod 666 /efs/gyro_cal_data
chmod 644 /efs/h2k.dat
chmod 775 /efs/imei
chmod 700 /efs/lost+found
chmod 600 /efs/nv.log
chmod 700 /efs/nv_data.bin
chmod 700 /efs/nv_data.bin.md5
chmod 775 /efs/wifi
chmod 644 /efs/wv.keys
8) Exit and reboot
Code:
exit
adb reboot
There you have it, folder dump restored. If you're wondering if I did this myself before writing this guide, the answer is YES. I happily guinea pigged my device for you
Here is the full command list I used.
adb shell
ls /data/media/0
exit
adb pull /data/media/0/MG_EFS c:\users\rootsu\Desktop\MG_EFS
adb shell
ls -lh /efs
rm -Rf /efs/*
ls /efs
exit
adb push c:\users\rootsu\desktop\MG_EFS /efs/
adb shell
ls -lh /efs
chmod 664 /efs/00000000.authtokcont
chmod 755 /efs/FactoryApp
chmod 775 /efs/bluetooth
chmod 775 /efs/drm
chmod 666 /efs/gyro_cal_data
chmod 644 /efs/h2k.dat
chmod 775 /efs/imei
chmod 700 /efs/lost+found
chmod 600 /efs/nv.log
chmod 700 /efs/nv_data.bin
chmod 700 /efs/nv_data.bin.md5
chmod 775 /efs/wifi
chmod 644 /efs/wv.keys
ls -lh /efs
exit
adb reboot
I heard I can manually modify my IMEI, transplanted from another device?
Modifying an IMEI is illegal in many countries. Even if this was possible, discussion here would be against the rules. Your IMEI must not be modified. Either restore a backup or send for repair.
I'm stuck in factorymode, is this related?
Yes, factorymode is caused by corrupt efs. It is possible to fix it with root and a terminal emulator.
Firstly try these commands (case sensitive)
Code:
su
echo -n ON >> /efs/FactoryApp/factorymode
If they fail, use the more detailed commands:
Code:
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
This should hopefully return you to user mode. If not, the last thing you can try, which reportedly works is to delete /efs/FactoryApp/ folder, then factory reset from recovery. This *should* regenerate the folder. Your factory mode will still need "echo -n ON >> /efs/FactoryApp/factorymode" doing though, which can be done as described above or opening the file in a text editor and changing the content of the file to "ON"
Failing that, flash stock and send for repair.
See here for more info on factory mode
How does "Ariza patch" fit in to this?
Ariza patch does not fix IMEI issues. It fixes "00000" Serial number issues, which has similar symptoms. This patch does not work on EFS v2 ROMs. If you use it, you may irreparably break your phone.
Also it would seem, Phones that had this patch ON EFS v1 ROMS will break their IMEI if they upgrade to EFS v2 ROMS.
As yet, there is nothing proved to resolve this issue fully. Search the Ariza thread for posts by zuluman for potential fixes. This Page is hopefully the most useful or one of the patched modems posted
It would probably be best to get the serial number professionally restored either under warranty or by sla mobile repair shop. The Ariza patch was always only fixing something that should have been fixed under warranty anyway.... now we are seeing this issue - cut your losses
Send for repair
A couple of notes on this. Firstly, "Send for repair" does not necessarily mean you must return it to Samsung / Your carrier. It is simply a phrase. Many EFS issues can be resolved by taking it to a mobile repair shop.. In the UK, There's one on almost every street in a town / city centre, and they will charge about £20 to get it repaired. Around $25 USD / EUR. If you are out of warranty or are in a rush for the repair, this is a good option and yes, people are known to have been successful with this...
Secondly, a more personal note. If I suggest "send for repair" as a solution for you, it is not because I am unwilling to get involved in troubleshooting or helping (although this is all already covered in this post) - It is because I truly believe this is the best or only option for you. Mostly I will only recommend it if it is the only option. Seeing me say this a lot in this thread is because we need people to accept that there can only be a finite amount of approaches to fixing the issue. In some cases, I will recommend it if it is the BEST option. An example of that would be the ariza patch situation. The Change in EFS format broke all those serial number 000000 phones that were fixed with the ariza patch. It was my opinion before MG4 that serial number 000000 should have been the resolution to this issue. It still is. At the moment, there are not many options for broken ariza patched phones. My opinion is this is the order of best solutions.
1) Repair
2) Wait for ariza update
3) Try Zuluman patch.
I have said this a lot but it needed to go here too..
Other
How to work out when your baseband / ROM was released.
1) Take the last 3 characters from the name.
2) Compare the first of these characters against the below to get the year
L=2012
M=2013
3) Compare the second of these characters against the below to get the month
A=January
B=February
C= March
D=April
E=May
F=June
G=July
H=August
J=September
K=October
L=November
k=December
4) take the last of the 3 characters and compare against the below to get the revision number
1=Revision 1
2=Revision 2
3=Revision 3
4=Revision 4
5=Revision 5
6=Revision 6
7=Revision 7
8=Revision 8
9=Revision 9
A=Revision 10
B=Revision 11
C=Revision 12
D=Revision 13
E=Revision 14
F=Revision 15
etc
example:
MG4 = 2013 - July - Revision 4
This is a work in progress. None of this is my work, I am just compiling it into a single thread, so thanks to everyone answering questions in Q&A. If there is anything missing that you think should be added, please say so.
I used the app kTool to backup my efs. Won't that work?
Nice one :thumbup::thumbup:
rootSU said:
*note - efs | backup your efs | backup your efs | backup your efs | backup your efs | backup your efs | backup your
IMEI
A unique identification number programmed onto your phone. It is required in order to be correctly identified on a mobile network. Without one, you cannot make calls, send SMS or use mobile data. Important stuff.
/efs
A partition on your internal memory containing important data including the IMEI. If the data in this partition gets corrupt, you will loose your IMEI
0049*** IMEI
A generic IMEI, meaning your real IMEI is not readable, presumably because it is corrupt but there are other reasons too.
This thread aims to give you as much basic information as possible in an attempt to prevent the 10 - 20 threads we're getting per day about this issue.
I have a 0049 IMEI. Why?
This means your phone cannot read your IMEI. There are 2 main reasons for this.
1) /efs is corrupt.
Whenever you flash a ROM, be that a custom ROM via a custom recovery or an official ROM via Odin, you risk corrupting your /efs partition and losing your IMEI.
There are 4 main steps to take to try to resolve this
Restore your EFS from a backup - A logical first step
No backup? Reflash a stock ROM using Odin
Send the device for repair.
2) /efs partition format changed
The latest UK (BTU) 4.1.2 release (XXEMG4) which comes with the baseband of the same name, actually changes the format of efs.
If you have flashed XXEMG4 at any point, you are now in a situation whereby only the MG4 baseband can read the IMEI in /efs. The new efs format is not backwards compatible with older basebands. Probably, all new basebands will be compatible so in time this issue should diminish I expect.
If you have ever flashed XXEMG4, to keep your IMEI working, you must:
Stay with the baseband MG4. You may flash other ROMs but must return to the MG4 baseband.
Restore your efs backup (taken before MG4) to use older basebands.
For discussion of this issue, see this thread.
How do I backup and restore /efs?
There are a few methods to backup /efs, but they all require customisation of your phone. Either root access, or a custom recovery. I appreciate that many of you do not wish to root your phones and just want to flash official ROMs via Odin... Well here are your choices:
Only use OTA or KIES to update (Official Method)
Root using CF auto root / Framaroot - backup efs and THEN flash via ODIN
Flash a custom recovery via Odin, backup efs and THEN flash a ROm via Odin
Risk it. Don't backup efs. Simply flash via Odin and hope for the best
...and here are the options for backing up / restoring efs (this list is not exhaustive)
EFS Pro - App needs root
SGSIII EFS backup / Restore - app runs from Windows / Linux and needs root
Philz advanced CWM rewcovery - custom recovery can take efs backups using the "Custom Backup" feature.
I heard I can manually modify my IMEI, transplanted from another device?
Modifying an IMEI is illegal in many countries. Even if this was possible, discussion here would be against the rules. Your IMEI must not be modified. Either restore a backup or send for repair.
I'm stuck in factorymode, is this related?
Yes, factorymode is caused by corrupt efs. It is possible to fix it with root and a terminal emulator.
Firstly try these commands (case sensitive)
Code:
su
echo -n ON >> /efs/FactoryApp/factorymode
If they fail, use the more detailed commands:
Code:
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
This should hopefully return you to user mode. If not, restoring to stock and / or restoring an efs backup may be the next things you try before sending for repair.
See here for more info on factory mode
Other
This is a work in progress. None of this is my work, I am just compiling it into a single thread, so thanks to everyone answering questions in Q&A. If there is anything missing that you think should be added, please say so.
Click to expand...
Click to collapse
Nice information here again, I would add that some custom roms allow you to backup your efs
Sent from my GT-I9300 using Tapatalk 4 Beta just to annoy Gus
sidh10 said:
I used the app kTool to backup my efs. Won't that work?
Click to expand...
Click to collapse
As I said the list is not yet exhaustive
With kernels like siyah they create 2 efs files on the Internal SD card, is it enough to copy these to drop box or something and restore only if they are ever needed?
Sent from my GT-I9300 using xda app-developers app
Should be enough although I personally keep 3 separate backups
Sent from my GT-I9300 using Tapatalk 4
I was wondering.
I had a Galaxy Nexus, and Galaxy S III
What if I restore their backup efs into my current Galaxy S III
Will my second 9300's IMEI changed into old i9300 or i9250? Or just mess it up?
Sent from my GT-I9300 using xda premium
Doubtful. You cannot use someone else's efs backup to restore your own.
Sent from my GT-I9300 using Tapatalk 4
What happen in case my imei is correct and no have network connection? No registre network in case of arizapatch?
Sent from my GT-I9300 using xda app-developers app
Patch it
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Patch it
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
sorry I did not express well my question is why does that happen imei correct and no registre network
Sent from my GT-I9300 using xda app-developers app
No idea. Not to do with this thread. Try arizapatch?
Sent from my GT-I9300 using Tapatalk 4
Very neat, although I'd fix the 'loose' to 'lose'.
rootSU said:
No idea. Not to do with this thread. Try arizapatch?
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
I have a lot of time using the patch but I have no answer because it passes / thanks anyway for the explanation of efs
Sent from my GT-I9300 using xda app-developers app
Choristav said:
Very neat, although I'd fix the 'loose' to 'lose'.
Click to expand...
Click to collapse
Thanks. Typo
Sent from my GT-I9300 using Tapatalk 4
qtwrk said:
I was wondering.
I had a Galaxy Nexus, and Galaxy S III
What if I restore their backup efs into my current Galaxy S III
Will my second 9300's IMEI changed into old i9300 or i9250? Or just mess it up?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
You could potentially brick your device as is the case when flashing anything from another device onto your own, it would definitely cause problems with registering on your network.
If your network finds out as well you could also have a friendly visit from the police for cloning an IMEI. (it doesn't matter if you own the other device you are trying to change the ID of the device which is illegal.
Sent from my GT-I9300 using Tapatalk 4 Beta just to annoy Gus
@rootSU and others ,
guys i'm in trouble , i lost my imei and the classic "No service" error is haunting me,
i do have the back up efsbackup.tar.gz and efsdev-mmcblk0p3.img.gz in sdcard but how do i restore (the easiest way ? btw i have no idea by what action these backups are created , they were just there when i looked) plus, do i need to get back to stock before restore ? currently on a 4.2.2 rom . Thank you
Try
http://forum.xda-developers.com/showthread.php?t=1308546
chris_marsh said:
@rootSU and others ,
guys i'm in trouble , i lost my imei and the classic "No service" error is haunting me,
i do have the back up efsbackup.tar.gz and efsdev-mmcblk0p3.img.gz in sdcard but how do i restore (the easiest way ? btw i have no idea by what action these backups are created , they were just there when i looked) plus, do i need to get back to stock before restore ? currently on a 4.2.2 rom . Thank you
Click to expand...
Click to collapse
I've linked 3 apps in post 1. One of those should help
Sent from my GT-I9300 using Tapatalk 4
Background:
Trying out ROMs here and there, making backups along the way in TWRP. Turn out I had my favorite ROM from the start, so clean all the slates and performed a restore to Hybrid X Series 1.07. Everything is as it was...almost.
Apps are complaining about not being able to download to internal memory, there not being enough space, etc (there's plenty). Switching the download directory of these apps to the extSdCard is my current workaround.
What I've tried:
Fix Permissions from TWRP
Repair partition /data from TWRP using e2fsck
recursive busybox chown to 1001 on /data/media
restorecon on /data/media/0
This Fix Script Also found a similar flashable ZIP which did the same thing, but to no avail
None of these seem to have any effect. Also, trying to change permissions from Root Browser works on /sdcard, but not on any subfolders. Error returned is "Changing permissions was not successful. Please note that some file systems do not allow permission changes."
Any thoughts
funkeywoookey said:
Background:
Trying out ROMs here and there, making backups along the way in TWRP. Turn out I had my favorite ROM from the start, so clean all the slates and performed a restore to Hybrid X Series 1.07. Everything is as it was...almost.
Apps are complaining about not being able to download to internal memory, there not being enough space, etc (there's plenty). Switching the download directory of these apps to the extSdCard is my current workaround.
What I've tried:
Fix Permissions from TWRP
Repair partition /data from TWRP using e2fsck
recursive busybox chown to 1001 on /data/media
restorecon on /data/media/0
This Fix Script Also found a similar flashable ZIP which did the same thing, but to no avail
None of these seem to have any effect. Also, trying to change permissions from Root Browser works on /sdcard, but not on any subfolders. Error returned is "Changing permissions was not successful. Please note that some file systems do not allow permission changes."
Any thoughts
Click to expand...
Click to collapse
First off, this is an ownership issue, not a permissions issue
Second, chown 1001 gives ownership to Radio, not System. Chown to 1000 for System ownership
I never did find a solution to this problem. In my attempts to correct the problem, I ran chown on the entire /data partition by accident. The ROM booted, but everything crashed. After this, I just decided to salvage what little I might be able to save and move on with life.
The problem even persisted through wipe/reinstall of the ROM.
Finally, as a last resort, I had flash the stock version through Odin and start over from scratch.
So Hello everyone, i got interesting problem...
I bricked my phone
Phone: SM-9005
OS: Android 4.4.2
Firmware: N9005XXUGNG1
Recovery: TWRP 3.0 installed.
Root software installed which may be interesting "Xposed Additions, Lucky Patcher, SuperSu, Greenify"
Step by step.
// maybe helpful - cache / dalvik cache wiped and after reboot i started playing stuff
I used Root Browser (com.jrummy.root.browserfree) to copy 2 directories from my /downloads to /system.
There were /lib & /bin which contained unique libs and one executable so this would not affect system if everything went ok, but i didn't
After i started coping, root explorer asked me that "File already exist, overwrite or make a copy"? i pressed overwrite, in same second all apps in android started to generate "unexpected error", i tried to reboot and got boot into recovery
after i watched /system i found that what i tried to copy actually copied not to /system/lib & /system/app but to /system/system/lib & /system/system/app.
So i think there was some folder or file called system in /system directory which was overwritten. Or any kind of problem with dir / file permissions.
Any ideas of how to fix this / what was in /system/system / where to get bootlog to find after what "kernel panic" takes place or any other help?
Thanks.
// maybe somebody with same model version, same os version can upload zip file of own /system folder without /apps, /priv-apps and build.prop so i can compare whats lost compared to my data?
Fixed myself, root browser set wrong permissions to /system while was coping files... set back to 755 and it works
I have the Moto G7 International variation (INDIA/RETIN, it turns out; I'm in the US and thought I was buying the RETUS version, but I didn't pay enough attention to the store page). I have rooted the device easily, thanks to the assistance of these forums. I have also installed TWRP 3.3.1-2-river for the purpose of backups and restores, though there seems to be problem with it. However TWRP is not the focus of my question right now.
I have become quite annoyed with the boot animation on this phone and would like to change it. Putting new boot animations in the /system/media folder has not been working and it seems to be because this international model has a boot animation override (that trumps all other boot animation locations) in the /oem/retin/media folder. The /oem folder is initially read-only, but can be remounted with read-write without error (using root). Using MiXplorer or the adb shell, I can delete stuff from there without error as well. However, when I reboot, it all comes back. I suspect that the changes I make to the /oem folder are not actually persisted to whereever in the first place. When I look at the mounts on the phone, I see /oem is mounted from /dev/block/dm-1. /dev/block/dm-1 is listed in my partitions list when the phone is booted up normally. From what I can tell though (and I'm not that knowledgable on this topic), that is just a "wrapper" around some data elsewhere. How can I tell where this dm-1 partition's data is really coming from?
As additional information, the block list by-name lists the oem image as belonging to block mmcblk0p58. When I boot into TWRP and mount that block, I do see the usual /oem stuff in there. I deleted the boot animation from there and tested unmounting the block, rebooting into TWRP and remounting the block and can see that the boot animation is still properly deleted from there. However, when I boot the phone back up normally, I see the usual stuff (including the boot animation) in the /oem folder still. That might make some sense, since it is listed as being mounted from /dev/block/dm-1 and not from /dev/block/mmcblk0p58 (though I was hoping dm-1 was a wrapper for mmcblk0p58).
This is the only dm mount on the phone; I don't have the problem with /system being uneditable because it is mounted to dm-0 like I see in many other posts for other phones. In turn, I don't think I have the "base data is encrypted" problem from those cases either (it is "just" an oem setup and not personal data). This still seems somewhat like the dm-verity problem I read about with other phones though (although this one doesn't give the dm-verity warning when I try to remount /oem as read-write). Running the commands:
Code:
adb root
adb disable-verity
just tells me
Code:
disable-verity only works for userdebug builds
verity cannot be disabled/enabled - USER build
I'm not sure how to check if there is dm-verity on in the first place though.
As a more direct question (though I would still like to know how to trace this dm-1 partition backwards), how can I make changes to this /oem folder actually persist between reboots?
@Spaceminer described the exact same problem for the Moto G6 in the Universal DM-Verity remover thread. In the end he said that it wasn't solvable without a system root.
https://forum.xda-developers.com/an...rceencrypt-t3817389/post81974407#post81974407
(I have since returned the phone because of this.)
1equals2 said:
@Spaceminer described the exact same problem for the Moto G6 in the Universal DM-Verity remover thread. In the end he said that it wasn't solvable without a system root.
https://forum.xda-developers.com/an...rceencrypt-t3817389/post81974407#post81974407
(I have since returned the phone because of this.)
Click to expand...
Click to collapse
i was unable to get this to persist either. i ended up using magisk for my work instead.
@1equals2 @HT123 To persist changes to your /oem partition the HAB (high assurance boot) verification must be deactivated. I've already successfully tested it on my device, a Moto G6 plus.
Here are the required steps: (only for Stock ROM!!)
1.) Start TWRP and backup /vendor + /system
2.) Mount /vendor + /system and delete the following
files:
- /vendor/etc/init/hw/init.mmi.hab.rc
- /vendor/bin/init.mmi.hab.sh
- /system/verity_key
3.) Go to /vendor/etc/init/hw and adb pull init.mmi.rc in order to edit the file.
4.) Open it and delete the lines 19+20:
Code:
19 # Moto verified boot extension
20 import /vendor/etc/init/hw/init.mmi.hab.rc
5.) Save the changes, copy it back to its path and set permissions to: -rw-r--r-- root:root
==> After the next reboot /vendor and /oem are mounted as ../vendor_a and ../oem_a (depending on your active slot).
As the last step you have to customize fstab.qcom to be able to access the files within the /oem folder.
Adb pull /vendor/etc/fstab.qcom and open it. The last line defines how /oem is mounted during the init process. You should change it like this:
before:
Code:
/dev/block [...] /oem ext4 ro,nosuid,nodev,[STRIKE]context=u:object_r:oemfs:s0[/STRIKE] wait,slotselect,[STRIKE]verify[/STRIKE]
after:
Code:
/dev/block [...] /oem ext4 ro,nosuid,nodev,[COLOR="red"]barrier=1[/COLOR] wait,slotselect
Save it and copy it back. Permissions: -rw-r--r-- root:root
>>> REBOOT AND ENJOY!!