Greetings!
I'd like to present a TWRP recovery for the single-sim Xperia X. This release works on Xperia X F5121 and F5122
DISCLAIMER:
I'm not responsible for any damage done to your device. You have been warned.
REQUIREMENTS
Unlocked bootloader
Working ADB and Fastboot (You can get the latest version through Android Studio or by visiting this site)
FEATURES
MTP support
ADB Sideload
Backups and restores almost every partition
Full SELinux support
Working encryption. You can access /data within recovery
NEEDS TESTING
USB-OTG
DOWNLOADS
INSTALLATION
Unlock the bootloader
Download the file
Put the following code in CMD/Terminal:
Code:
fastboot flash recovery twrp-3.1.1-suzu-*.img
//Replace * with the version you want to flash
Unplug the cable
Press Volume Down + Power to activate the recovery. When installed properly, the device should vibrate funnily, purple LED should appear and after a couple of seconds you should see the TWRP screen.
Enjoy!
BUILD
You need to sync the OmniROM and vendor blobs from DonkeyCoyote. You can find my sources on GitHub.
android_device_sony_loire_common
https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Thanks:
@grayleshy - for initial TWRP
@AndroPlus for some of his flags
OmniROM team for sources
If you find my work useful, consider buying me a cup of coffee
[TWRP] TWRP 3.1.0 for Xperia X
Old OP below:
Team Win Recovery Project 3.1.0
REQUIREMENT:
- Unlocked bootloader
FEATURES:
- MTP support
- USB OTG storage support
- Covers most partitions for nandroid backups
- ADB root
- Full SELinux support
- Support for partition decryption
Download: Dropbox
Installation via the bootloader (Platform-tools (adb & fastboot))
Code:
fastboot flash recovery recovery.img
Running TWRP: turn the phone off, wait 5 seconds, then pinch at the same time the power key and the volume down key until the device vibrates, release the keys. Recovery starts within 5-10 seconds.
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
Special thanks kistigun for testing recovery on the device.
Changelog: twrp.me
TWRP was going on OmniRom 7.1 sources and XperiaDeveloper.
SOURCEs: Suzu; loire; Common.
Nice work! Finally no more decryption problems on the X!
Working well, thanks!
One question ; is it possible to reboot the recovery via twrp reboot menu (or use an app like flashfire /flashify)? When I've tried the phone boots normally instead.
baddesthad said:
One question ; is it possible to reboot the recovery via twrp reboot menu (or use an app like flashfire /flashify)?
Click to expand...
Click to collapse
Unfortunately the reboot Recovery does not work from the specifics of the section, but in the future maybe will be fixed. If I don't find how to fix that button will be removed.
samavar89 said:
Unfortunately the reboot Recovery does not work from the specifics of the section, but in the future maybe will be fixed.
Click to expand...
Click to collapse
Good to know, thanks for clarifying
Is there a difference to the 3.1.0 TWRP recovery from the Poison thread?
Oel said:
Is there a difference to the 3.1.0 TWRP recovery from the Poison thread?
Click to expand...
Click to collapse
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
kistigun said:
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
Click to expand...
Click to collapse
Ah...
Ok, Thanks!
kistigun said:
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
Click to expand...
Click to collapse
No,
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
someone knows a recovery that finally works?
robby.pgn said:
No, don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
Click to expand...
Click to collapse
This problem is strange, please provide a log recovery.
I flashed this on my xperia x dual on nougat 7.0
I can go to recovery but when i try to turn on the phone normally it says "The phone is corrupt and cant be trusted bluh bluh..."
it says press power button to continue but when i press it screen turns off and nothings happens
what should i do?!
Kianush said:
I flashed this on my xperia x dual on nougat 7.0
I can go to recovery but when i try to turn on the phone normally it says "The phone is corrupt and cant be trusted bluh bluh..."
it says press power button to continue but when i press it screen turns off and nothings happens
what should i do?!
Click to expand...
Click to collapse
In Your kernel there is support for DM-Verity and Sony RIC?
it's stock kernel man, I unlocked bootloader and flashed stock nougat for xperia X dual sim
I just wanna root it, if there is any other way pls help me out
-----
btw after this problem i used flashtool to flash system and kernel from stock rom to be able to use my phone again
robby.pgn said:
No,
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
someone knows a recovery that finally works?
Click to expand...
Click to collapse
Kianush said:
it's stock kernel man, I unlocked bootloader and flashed stock nougat for xperia X dual sim
I just wanna root it, if there is any other way pls help me out
-----
btw after this problem i used flashtool to flash system and kernel from stock rom to be able to use my phone again
Click to expand...
Click to collapse
use this tool/guide to make a rooted kernel(and edit DM-Verity and Sony RIC): https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
grayleshy said:
Team Win Recovery Project 3.1.0
Click to expand...
Click to collapse
I've installed and tried this TWRP in my Xperia X with MM. Very nice that it can access the data partition! I did not try to install any zip yet.
Some problems I've seen:
dmesg.log: no output
recovery.log: https://pastebin.com/EwbtuC9q
What is interesting in the output:
Code:
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sd
CANNOT LINK EXECUTABLE "sh": cannot locate symbol "__fwrite_chk" referenced by "/sbin/busybox"...
I:exfat-fuse failed to mount with result '', trying vfat
I:Unable to mount '/external_sd'
I:Actual block device: '/dev/block/mmcblk1p1', current file system: 'vfat'
Looks like something is not right with the busybox in the image. Maybe it is that what is causing the external sdcard (in my case in exfat filesystem) not being mounted?
Thanks
robby.pgn said:
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup.
Click to expand...
Click to collapse
This problem is almost resolved, just need to test, but I don't have time to compile recovery. In the test version recovery without decryption, problem solved.
juliompinheiro said:
I've installed and tried this TWRP in my Xperia X with MM. Very nice that it can access the data partition! I did not try to install any zip yet.
Some problems I've seen:
dmesg.log: no output
recovery.log: https://pastebin.com/EwbtuC9q
What is interesting in the output:
Code:
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sd
CANNOT LINK EXECUTABLE "sh": cannot locate symbol "__fwrite_chk" referenced by "/sbin/busybox"...
I:exfat-fuse failed to mount with result '', trying vfat
I:Unable to mount '/external_sd'
I:Actual block device: '/dev/block/mmcblk1p1', current file system: 'vfat'
Looks like something is not right with the busybox in the image. Maybe it is that what is causing the external sdcard (in my case in exfat filesystem) not being mounted?
Click to expand...
Click to collapse
This issue failed to reproduce, and yet there is no solution. You the problem is not in Busybox, and something else.
grayleshy said:
Running TWRP: turn the phone off, wait 5 seconds, then pinch at the same time the power key and the volume down key until the device vibrates, release the keys. Recovery starts within 5-10 seconds.
Click to expand...
Click to collapse
For whatever reason I'm not able to boot into TWRP like I should be. I've used the poison version of TWRP before so I know what to do, and yet the phone will just boot normally despite holding volume down and power when off.
I know that TWRP is installed though as I am able to boot to it if I first boot to the bootloader using a USB cable but that is very cumbersome to do though.
grayleshy said:
This issue failed to reproduce, and yet there is no solution. You the problem is not in Busybox, and something else.
Click to expand...
Click to collapse
Clearly for the image available at your dropbox there are some libraries dependency errors, not only for the 'busybox', but also for other binaries that are in /sbin.
I do not know why this issue is only happening on my device since you said you can't reproduce this error. If there is anything I can do to help solve this strange behavior, count on me. I am an advanced linux user, but not too familiar with android specifics.
On latest 333 ROM for UK so that fingerprint scanner works on my Xperia X F5121.
I also modified by kernel/boot so that TWRP doesn't brick (actually boot loop) the device like it did the first time. After using these awesome instructions flashing TWRP recovery from here didn't kill the device any longer: https://forum.xda-developers.com/crossdevice-dev/sony/root-root-stock-firmware-modern-sony-t3558904
I was able to take an early nandroid backup before a bunch of Titanium restores, etc. Now I get stuck at "Backing up data" step and it literally doesn't move to the next file. Attaching an image of where I get stuck. FYI, I do use password encryption on the backup and I did disable MD5 creation... still just stuck.
Next tests are to:
see if the stall is on the same exact file number
try no encryption
do a check disk (fsck) type of repair just in case I have corruption --- on my brand new device
Any suggestions greatly appreciated!
UPDATED:
I only back up Boot, System & Data (the default)
On second attempt it stopped at file 18869 of 22065 --- so it does jump and not consistently stop at a certain file.
Related
Team Win Recovery Project 2.6, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. TeamWin started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of additional features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
HTC Droid Incredible 4G LTE product page on TeamW.in
Older versions can be found here if needed.
Download
Download TWRP 2.6.3.0 Official (Change Log)
MD5: 22c58a87402b4049f8bafa1b07b1a765
Download TWRP 2.6.3.0a Unofficial
MD5: fd9f7b520bec55c980d0ea39616aa271
Includes these commits on top of 2.6.3.0: Never generate empty backup name, Remove unneeded images, check for space after = too, Improvements to Update_Log_File, Fix checking for file_contexts in updater
GooManager Installation:
Automated installation through GooManager will only work if you have the su binary (root access) on your ROM. If you have just performed unlock or S-OFF, you must use the manual installation method for the first recovery installation.
Install the GooManager application from Google Play
Open GooManager, pull up the menu, and select Install OpenRecoveryScript
Confirm the first prompt, then verify the filename in the second prompt (openrecovery-twrp-2.6.3.0-fireball.img) and confirm again
After the recovery has been installed, pull up the menu and choose Reboot Recovery
Manual Installation:
Requirements: you must have fastboot set up: Windows Guide, Mac Guide, Ubuntu Guide
1) Reboot your phone to the bootloader:
Method 1: Disable fast boot under Settings > Power > Fast boot. Shut down the phone. Hold Volume-Down and Power simultaneously until the phone vibrates. Continue holding volume down, but release the power button. When you reach the bootloader, choose the FASTBOOT menu option using the volume keys to move up/down and the power key to select.
Method 2: If you have adb installed, then with your phone fully booted up, type: adb reboot-bootloader
2) Flash the recovery image using fastboot. Open a terminal and navigate to the directory with the downloaded image. Type:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-fireball.img
When the image has finished flashing (usually less than 10 seconds), issue the command
Code:
fastboot reboot-bootloader
3) Use the volume keys to navigate to BOOTLOADER and then select it with the power key. After the phone finishes scanning for PJ____.zip images, choose RECOVERY from the menu. This will start TWRP recovery.
Themes:
TWRP supports themes! Create a folder called theme within the TWRP folder on your internal storage and copy ui.zip into it. You can either search for themes compatible with the 540x960 resolution (check out the EVO 3D forum for instance) or build your own. Known themes listed below:
Holo TWRP Theme by prairiedogn
HTC TWRP Theme by prairiedogn
Blue Dalek Theme by agentc13
Sports Recovery Themes by lnando84
Gray Theme by lnando84
Themes written for earlier versions of TWRP may not have themed elements for new features. Be sure to compare the user interface before and after applying a theme to make sure everything shows up. You can check the log for errors as well (the middle button on the bottom of the TWRP interface), it will say something like: "unable to load button image" if resources are missing.
Additional Information:
The boot image comes from RUU 2.17.605.2
This build includes HTC Dumlock in case it is needed. S-OFF users can safely ignore it. HTCDev Unlock users (who are still S-ON) can try it out if experiencing trouble writing to the /boot partition. It can be found under Advanced in the recovery.
Credits:
Dees_Troy for adding the Inc 4G to TeamWin's officially supported devices for TWRP
con247 for putting in the original effort to build TWRP on the Inc 4G
utkanos and KemoNine for building assistance
TeamWin for TWRP and their great building guide
CyanogenMod for way too many reasons
Release History:
Official 2.6 - In addition to TWRP's official changes, this version also introduces support for AOSP data encryption. Additionally, Aroma installers should not fail anymore.
Official 2.4 - Builds are now maintained by TeamWin: Change Log
Official 2.3.3.0 - Identical to Build 1.2
Build 1.2 - Mount internal and external SD to computer via USB
Beta 1.1 - HTC Dumlock included
Beta 1.0 - Initial Release
Known issues / Workarounds / To Do
The charging status LED currently does not turn on when the phone is charging. This is really a non-issue since there is a charge level and charging indicator within the recovery.
If the phone is powered off while plugged into USB, it will temporarily reboot into recovery then shut down 20-30sec later.
Source
The device tree is at github.com/cyanogenmod/android_device_htc_fireball.
great, glad to see this coming
Do you think this could get goo manager support? Thanks for all that you do.
Sent from my DROID RAZR using Tapatalk 2
Awesome! Thanks updating now
jamminjon82 said:
Do you think this could get goo manager support? Thanks for all that you do.
Click to expand...
Click to collapse
I need successful user reports for all the features. Once I get confirmation that everything works as expected, I'll submit my device tree to TWRP and ask for official builds. Goo manager support would follow from there.
I updated the build to version 1.1. For those who are S-OFF, there's no difference from 1.0. For those who are S-ON and using HTCDev Unlock (from team fireballas), there's now HTC Dumlock included. I'm still not sure if it is even needed...
im running a backup now. i'll try wiping and restoring too
---------- Post added at 02:18 PM ---------- Previous post was at 01:37 PM ----------
Backup, wipe, and restore all work as well as backup compression and backup rename. Under wipe I didn't know about internal and android secure are those required for a full wipe?
Linch89 said:
im running a backup now. i'll try wiping and restoring too
---------- Post added at 02:18 PM ---------- Previous post was at 01:37 PM ----------
Backup, wipe, and restore all work as well as backup compression and backup rename. Under wipe I didn't know about internal and android secure are those required for a full wipe?
Click to expand...
Click to collapse
Relevant posts about androidsecure:
http://forum.xda-developers.com/showthread.php?t=1934739
http://forum.xda-developers.com/showpost.php?p=27172605&postcount=218
Internal wipe clears out your internal sdcard's media partition (pictures, music)... probably don't want to do that.
Good look glad I didn't. Well as far as I can tell this is recovery is a win pun intended
im trying to mount my phone to my computer while in recovery and its not working v2.3.3.0 idk if its my computers usb its certainly not my phones micro usb the thing is brand new
The ability to mount the phone's sdcards on the computer while in TWRP was unknown to me. I'm working on the issue. The attached recovery is a first stab at a fix, let me know if it works (my faith is low though since the devices didn't mount in ubuntu for me).
MD5: 6fa24210afa860c38fef3f2a7d4360d1
Edit: the attached recovery did not fix the issue. I'll try to look into this sometime this week (research presentations and job interviews over the next few weeks so time is very scarce right now).
Linch89 said:
im trying to mount my phone to my computer while in recovery and its not working v2.3.3.0 idk if its my computers usb its certainly not my phones micro usb the thing is brand new
Click to expand...
Click to collapse
Mine isn't mounting either, internal nor external card, but I can get it to work through ADB, (work around for the time being)
Interesting side note though, (and this may be expected by some, it was new to me) while in TWRP recovery and running shell though ADB it was listing my actual external SD card as "sdcard" and actual internal SD as "internal_sdcard". I have used CWM on another device and I don't remember it changing the file structure while in recovery. Also I had shell root upon issuing the adb shell command. This is my first device using TWRP, it was just different.
Edit: Never Mind, I am running TWRP v2.2.0, this may not have any validity with the OP's version, sorry.
Edit my Edit: OK I just flashed v2.3.3.0 and same goes, I can get in through ADB and I have shell root once in shell. However, the file system looks like it should with "sdcard" and internal and "external-sd" as external. All else seems normal.
DavDoc said:
Mine isn't mounting either, internal nor external card, but I can get it to work through ADB, (work around for the time being)
Click to expand...
Click to collapse
I worked on the sd card mounting issue last night, but still have not figured it out. I will try to get some assistance from the TWRP folks if I find time tonight. Just to make sure, the feature worked when you used TWRP 2.2 by con247?
In fact, I may be misinterpreting how the feature works. Is the computer supposed to auto-mount your SD card when plugged in via USB, or do you have to activate the feature from within TWRP somewhere?
DavDoc said:
Interesting side note though, (and this may be expected by some, it was new to me) while in TWRP recovery and running shell though ADB it was listing my actual external SD card as "sdcard" and actual internal SD as "internal_sdcard". I have used CWM on another device and I don't remember it changing the file structure while in recovery. Also I had shell root upon issuing the adb shell command. This is my first device using TWRP, it was just different.
Click to expand...
Click to collapse
I just tested and this is what I see:
Code:
drwxrwxrwx 11 root root 16384 Jan 1 1970 external_sd
drwxrwxrwx 11 root root 32768 Jan 1 1970 sdcard
EDIT: Both in TWRP and in 'adb shell' the locations are correct.
It doesn't auto mount upon connecting usb, I didn't try mounting it though, through TWRP settings. From what I can tell, both versions work the same, they just have different names for the file structure, and only for the external and internal sdcards - didn't really investigate any other files.
Edit: To answer your first question, no it didn't work in either version. Don't know who's v2.2.0 it is, but it is the recovery that was added into the supercid.auto script.
mdmower said:
I worked on the sd card mounting issue last night, but still have not figured it out. I will try to get some assistance from the TWRP folks if I find time tonight. Just to make sure, the feature worked when you used TWRP 2.2 by con247?
In fact, I may be misinterpreting how the feature works. Is the computer supposed to auto-mount your SD card when plugged in via USB, or do you have to activate the feature from within TWRP somewhere?
I just tested and this is what I see:
Code:
drwxrwxrwx 11 root root 16384 Jan 1 1970 external_sd
drwxrwxrwx 11 root root 32768 Jan 1 1970 sdcard
EDIT: Both in TWRP and in 'adb shell' the locations are correct.
Click to expand...
Click to collapse
i think they mean usb mounting is gone it is suposed to be under mount option
jose51197 said:
i think they mean usb mounting is gone it is suposed to be under mount option
Click to expand...
Click to collapse
Right, so if I just understood this a couple of days ago I could have had a fix pretty quick. I naively thought the phone was supposed to auto-mount to the computer, which would make no sense because the drives would then be inaccessible to TWRP's routines. Anyways, build 1.2 enables the feature and both internal and external SD cards can be accessed.
mdmower said:
Right, so if I just understood this a couple of days ago I could have had a fix pretty quick. I naively thought the phone was supposed to auto-mount to the computer, which would make no sense because the drives would then be inaccessible to TWRP's routines. Anyways, build 1.2 enables the feature and both internal and external SD cards can be accessed.
Click to expand...
Click to collapse
Its back thanks I wish I can thank you twice and don't want to complain but only thing missing is the backup android.secure option under backup
Sent from my ADR6410LVW using xda app-developers app
jose51197 said:
Its back thanks I wish I can thank you twice and don't want to complain but only thing missing is the backup android.secure option under backup
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
Does your .android_secure folder actually have anything in it? Mine is empty on Viper 2.1.1. I just moved an app to SD and the folder is still empty. The reason I ask is because the and-sec folder is correctly mounted and linked to /sdcard/.android_secure when in TWRP.
I've never seen anything in android secure ever on any phone
Linch89 said:
I've never seen anything in android secure ever on any phone
Click to expand...
Click to collapse
On my OG DInc running AOSP that folder would indeed store sdcard apps... strange its different now....
I moved all apps my apps to sd card and I checked android_secure under sdcard and sdcard2 in root explorer and nothings in there. I can't delete the folder though so it must be of some importance
T-Mobile Springboard S7-303u
Was on S7-301u stock, works perfectly
Tried to update SuperSU from CWM
I might messed up and mis-flashed the CM10.1 Sep.10 by after_silence
http://forum.xda-developers.com/showthread.php?t=2045808
Rebooted, stuck at the Huawei logo screen (logo, instead of boot animation)
dload folder stock recovery, still stuck at the Huawei logo
Fastboot fine, free to flash recoveries
Formatted everything in TWRP, flashed CM10.1
Booted into system perfectly, IMEI/MAC all gone
Reflashed several times, still only CM10.1 works, with IMEI CHANGED!!!!!!
IMEI SV: 00
SIM lock also relocked (previously unl*cked might be related to changed IMEI)
Even with the T-Mobile SIM, can call/text/HSPA+
Correctly reads SIM operator, blank Net operator
Additional observations:
Only cm10.1 kernel will boot system
With stock kernel + cwm/twrp, cannot manipulate internal storage (system/data/cache...)
A white screen right before booting into recovery
TWRP keeps saying "Unknown File System: datamedia" "Updating partition details..."
It looks to me:
1) internal storage is either collapsed or changed into some different format (only accessible by cm10.1 kernel)
2) to the hell of it I cannot understand where does the different IMEI come from
3) collapsed radio files? (ADB pushed Tmobile stock before flashing cm10.1)
Please kindly input. I do not care about stock ROM, I just want my original IMEI back, want correct Net Operator, want SIM lock gone. Ideally the storage is restored, so that it is back to normal...
Many thanks to all!
Similar stories:
http://forum.xda-developers.com/showthread.php?p=38363578
441Excelsior said:
hi all, my friend got mediapad and he wanted custom rom so I flashed twrp recovery and his tablet became bricked, it shows huawei logo, then white screen and then after few seconds it shuts down, I tried to restore my backup to his tablet (CM10.1) via twrp and then it booted without problems but when I do wipe data/actory reset, the white screen and bootloop appears again, where is the problem? in twrp recovery? should I choose cwm for his device? twrp shows error "E: unknown filesystem datamedia" (also on my device but mine works without problems)
thanks for any help
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=37663928&postcount=48
netfortius said:
Just a follow-up to my earlier "used twrp to wipe everything": re-applied (i.e.
$ fastboot flash recovery twrp.img
with the trwp.img from auto_recovery, but booting the system still goes through the same process:
teamwin logo, then:
E:Unable to mount '/data'
E:Unable to recreate /data/media folder
E: Unknown File System: 'datamedia'
Updating partition details...
E:Unable to mount '/data'
E:Unable to mount internal storage
E:Unable to mount /data/media during GUI startup
E:Unable to locate page (main2)
Formatting Cache using make_ext4fs...
Done
E:Unable to mount /data when trying to read settings file
E:Unable to mount '/data'
After the above, if I power down and back up, I go back to log screen, then immediately "Encryption unsuccessful", with the two options:
"Reset tablet"
and
"Encrypt tablet" ... choosing the latter asks for a key which I do not have. Choosing the former goes to ... you guessed:
teamwin logo, then
E:Unable to mount '/data'
E:Unable to recreate /data/media folder...
Any ideas how to recover from this?
Click to expand...
Click to collapse
maybe there are 2 different hardware versions of mediapad
441Excelsior said:
maybe there are 2 different hardware versions of mediapad
Click to expand...
Click to collapse
This might not be the case because the stock firmware was once working...
but if there are 2 versions of mediapad, CM could have support for only one....it can be something like on my HTC Desire S (first models have sony displays and second made in 2012 have hitachi mddi displays) - I have version with MDDI display and therefore CM does not boot on my device but stock firmware works on both versions...so maybe SU-303u is a bit different than SU-301u
441Excelsior said:
but if there are 2 versions of mediapad, CM could have support for only one....it can be something like on my HTC Desire S (first models have sony displays and second made in 2012 have hitachi mddi displays) - I have version with MDDI display and therefore CM does not boot on my device but stock firmware works on both versions...so maybe SU-303u is a bit different than SU-301u
Click to expand...
Click to collapse
This might not be my situation:
Before crash:
Stock works / cm works
After crash:
Stock not working / cm works with wrong IMEI
you said that you got message about unsuccessfull encryption, why did you wanted to encrypt your device? maybe it failed and now partitions are unaccessible or corrupted
441Excelsior said:
you said that you got message about unsuccessfull encryption, why did you wanted to encrypt your device? maybe it failed and now partitions are unaccessible or corrupted
Click to expand...
Click to collapse
That's not what I said, but some quotes from others...
I never tried to encrypt, but I will try to encrypt and decrypt and see if it helps.
you can try flash stock rom via fastboot manually every partition
441Excelsior said:
you can try flash stock rom via fastboot manually every partition
Click to expand...
Click to collapse
Is there any detailed instruction of how to do this? I tried fastboot push of a bunch of files from T-Mobile stock rom, but it did not help.
Not sure if it is the same thing as flashing partitions...
unzip the stock rom somewhere, boot tablet into fastboot mode, connect usb, then open cmd, change working dir to dir with unpacked zip and via command 'fastboot flash <partition> <filename>' flash every file, partition names are the same as files names (but without extension)
441Excelsior said:
unzip the stock rom somewhere, boot tablet into fastboot mode, connect usb, then open cmd, change working dir to dir with unpacked zip and via command 'fastboot flash <partition> <filename>' flash every file, partition names are the same as files names (but without extension)
Click to expand...
Click to collapse
Tried and did not help. This is actually what dload folder is exactly doing...
Now it is not the contents in those partitions are corrupted, but the partitions themselves are corrupted. Pushing recovery files in whatever way won't fix partitions...
Problem solved by luck.
Flashed TMO stock
then S7-302u stock
booted into system
said "last encryption failed, encrypt again or reset?"
chose reset
then everything back to normal
never tried to encrypt the tablet
not sure what happened.
might be some bug in the stock S7-301u ROM
which told the tablet to do crazy things.
Congrats :good:
Can you share your both files which makes you happy
Q&A for [TOOL][NABI2] NabiLab - Root, Play, Recovery
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [TOOL][NABI2] NabiLab - Root, Play, Recovery. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
State of Nabi 2 Root as of 12/14?
So I have admittedly been out of the loop on the state of rooting my two Nabi 2s since after I restored them to stock and all back last year when they released the update that included the Gapps. So I've been running stock since then and am on the latest firmware (2.4.6 I believe). All is mostly fine, but I would really like to get the external SD cards to be writable again, and from what I can tell, I need root again to do that.
So...as of today...what is the state (and best procedure) of rooting the Nabi 2 on the latest OTA update? Is Nabi Lab still the best tool? From what I've pieced together from scattered threads, it's looking like possibly use Nabi Lab to install TWRP, and then use that to install the SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053). However, I could likely be wrong...hence why I'm asking.
Eyebolt said:
So I have admittedly been out of the loop on the state of rooting my two Nabi 2s since after I restored them to stock and all back last year when they released the update that included the Gapps. So I've been running stock since then and am on the latest firmware (2.4.6 I believe). All is mostly fine, but I would really like to get the external SD cards to be writable again, and from what I can tell, I need root again to do that.
So...as of today...what is the state (and best procedure) of rooting the Nabi 2 on the latest OTA update? Is Nabi Lab still the best tool? From what I've pieced together from scattered threads, it's looking like possibly use Nabi Lab to install TWRP, and then use that to install the SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053). However, I could likely be wrong...hence why I'm asking.
Click to expand...
Click to collapse
Nabilab will still work as long as you use a version with a Jellybean TWRP(since you are on 2.4.6).
katinatez repackaged it for jellybean here:
http://forum.xda-developers.com/showpost.php?p=48987089&postcount=2088
I've searched high and low and can't find anything. I have nabi2S running KitKat. Every rooting guide I've found is for JB. Is there any way to root the 2S?
Sent from my Nexus 5 using XDA Free mobile app
jaxbierley said:
I've searched high and low and can't find anything. I have nabi2S running KitKat. Every rooting guide I've found is for JB. Is there any way to root the 2S?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
For the sake of anyone else looking for this information we are discussing it at the main Nabi thread starting at post #2477
http://forum.xda-developers.com/showthread.php?t=1905674&page=248
Stock Restore
Hi
I have downloaded NabiLab, as I am having wifi issues on my updated Nabi2. I unzipped, ran the .bat and chose option 3 (with my nab connected via USB). Nothing happened, no errors etc, the screen flashed up and shut down. Do I need to do something with the Nabi (recovery mode etc), do I need to install anything from NabiLab before trying this? Any help would be appreciated
Firepants said:
Hi
I have downloaded NabiLab, as I am having wifi issues on my updated Nabi2. I unzipped, ran the .bat and chose option 3 (with my nab connected via USB). Nothing happened, no errors etc, the screen flashed up and shut down. Do I need to do something with the Nabi (recovery mode etc), do I need to install anything from NabiLab before trying this? Any help would be appreciated
Click to expand...
Click to collapse
What version of software? Use Nabilab2015 http://forum.xda-developers.com/showpost.php?p=59073456&postcount=2544
It has more diagnostic info. Just be in Android or TWRP with ADb enabled. It also can see if drivers are loaded.
Hacking Nabi2 to Allow Data2SD
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
ashahin1 said:
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
Click to expand...
Click to collapse
If you are not sure which line to change, I have the fstab.mt799 file attached with this post. You can simply replace your file with this one.
ashahin1 said:
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
Click to expand...
Click to collapse
If you don't have the time to do all these steps, I have the modified boot file attached here.
Yo can either follow steps 7 and 8 above to write it, or use the fastboot command as follows:
Code:
fastboot flash boot new_boot.img
Nabi2 not found
Hi, I purchased a reconditioned Nabi, which was reset back to stock. The wifi worked fine, until I updated it through the tablet. I am now on version 2.0 with no wifi. I have tried various options through NabiLab , however my Nabi is not recognised as being connected (although windows picks it up). Please help!
Swipe to restore
I am trying to return my nabi to stock, i can get to the screen that asks you to 'swipe to restore' but the screen is not responding. I dont have issues with the touchscreen normally
Aytul said:
I am trying to return my nabi to stock, i can get to the screen that asks you to 'swipe to restore' but the screen is not responding. I dont have issues with the touchscreen normally
Click to expand...
Click to collapse
That's weird...if you keep messing with it you may find a spot a little left, right, higher, or lower where you can grab the button to swipe....or you try to re-flash TWRP or maybe there's a new version of TWRP for your particular nabi software version.
did you ever get nabilab to see it? did you check the device manager to see if it was totally recognized? Are developer options enabled?
n3wt said:
That's weird...if you keep messing with it you may find a spot a little left, right, higher, or lower where you can grab the button to swipe....or you try to re-flash TWRP or maybe there's a new version of TWRP for your particular nabi software version.
did you ever get nabilab to see it? did you check the device manager to see if it was totally recognized? Are developer options enabled?
Click to expand...
Click to collapse
The Nabi is showing as a device, it's responds as it should up to the point of TWRP. I had to repeatedly press buttons to get to the restore swipe and have tried many times, unsuccessfully. Where do I enable developer options?
I am on version 2 (Nabi) and using the most up-to-date version of NabiLab. I am trying to restore to stock so that the software version goes back, as the update has stopped my wifi working. Even a factory reset doesn't take the Nabi software back further than v2.0
Aytul said:
The Nabi is showing as a device, it's responds as it should up to the point of TWRP. I had to repeatedly press buttons to get to the restore swipe and have tried many times, unsuccessfully. Where do I enable developer options?
I am on version 2 (Nabi) and using the most up-to-date version of NabiLab. I am trying to restore to stock so that the software version goes back, as the update has stopped my wifi working. Even a factory reset doesn't take the Nabi software back further than v2.0
Click to expand...
Click to collapse
For developer options you go to settings, scroll all the way down, if you don't see "Developer options" there, press About tablet, then repeatedly tap build number until it pops up and says "You are now a developer!", then go back and now you should see the Developer options menu item, press it and then make sure it's on at the top and that the USB Debugging option is checked.....then try nabilab again.
n3wt said:
For developer options you go to settings, scroll all the way down, if you don't see "Developer options" there, press About tablet, then repeatedly tap build number until it pops up and says "You are now a developer!", then go back and now you should see the Developer options menu item, press it and then make sure it's on at the top and that the USB Debugging option is checked.....then try nabilab again.
Click to expand...
Click to collapse
Yes this is enabled, as without it I am unable to run nabilab etc. The problem is TWRP & the version of software I am running on the tablet?
Aytul said:
Yes this is enabled, as without it I am unable to run nabilab etc. The problem is TWRP & the version of software I am running on the tablet?
Click to expand...
Click to collapse
Well, the touch issues are probably due to a bad build of TWRP but not necessarily the wrong one. The problem with nabilab not being able to see the tablet I think has to be drivers. Have you checked device manager to make sure there are no unrecognized things? 'cause the tablet show up as two separate things in there and it sounds like the USB storage part is working but not the adb and/or fastboot part(s).
n3wt said:
Well, the touch issues are probably due to a bad build of TWRP but not necessarily the wrong one. The problem with nabilab not being able to see the tablet I think has to be drivers. Have you checked device manager to make sure there are no unrecognized things? 'cause the tablet show up as two separate things in there and it sounds like the USB storage part is working but not the adb and/or fastboot part(s).
Click to expand...
Click to collapse
I've managed to sort the drivers by installing PDANet, then managed to sort TWRP by installing an older version. I've now updated to 2.1 on the Nabi but no luck with the wifi issue..i'm guessing it's really broken and it happening whilst updating may have been a coincidence?!
Aytul said:
I've managed to sort the drivers by installing PDANet, then managed to sort TWRP by installing an older version. I've now updated to 2.1 on the Nabi but no luck with the wifi issue..i'm guessing it's really broken and it happening whilst updating may have been a coincidence?!
Click to expand...
Click to collapse
It might just be broken but that's a heck of a coincidence... Do you have a backup from before the wifi issue started? If so, I'd try to thoroughly wipe everything but your external sd card and then restoring your backup and see if that helps.
n3wt said:
It might just be broken but that's a heck of a coincidence... Do you have a backup from before the wifi issue started? If so, I'd try to thoroughly wipe everything but your external sd card and then restoring your backup and see if that helps.
Click to expand...
Click to collapse
Hi, I bought it as a reconditioned did unit. Turned it on, updates it (wifi worked) and then had this problem, so no backup to go back to unfortunately
This is a CyanogenMod 12.1 ROM for the Exynos3470 based Samsung Galaxy Tab 4 7.0 LTE (T235/T235Y).
DO NOT USE IT FOR T230(NU)/T231 OR YOU WILL BRICK YOUR DEVICE
Although T235 and T230(NU)/T231 (T230:WiFi / T231:3G) share the "Galaxy Tab 4 7.0" name they are not related in terms of hardware due to the different SoCs used (Samsung Exynos3470 vs. Marvell PXA1088).
Hence please do not ask for support or ROMs for the T230(NU)/T231.
Working features
Receiving and making calls
Hardware sensors (Acceleration)
Audio
Bluetooth
Wifi
HW accelerated GUI
MTP storage
GPS
USB-OTG (Mass-Storage, Keyboard, Mouse working, USB-Audio untested)
Camera (pictures+video: Back+Front)
Non-working features:
SELinux
Known issues:
See the Bug Report section of this thread
Disclaimer:
You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
Applications that use KNOX (e.g. "Private Mode") might not work anymore when returning to the stock ROM, as the device is regarded as compromised. Do not flash this ROM if you need those applications.
The image is only for Tab 4 7.0 SM-T235 and SM-T235Y (Exynos)
It might be instable, crash your device, drain your battery, or even might damage your smartphone
Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Click to expand...
Click to collapse
Before you start:
Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.
Download:
Odin3-v1.85
TWRP 2.8.7.0 recovery image [09/08/2015] (AndroidFileHost Mirror)
CM 12.1 ROM (AndroidFileHost Mirror)
Google Apps (contains Google Play, ...) for Android 5.1.1 from Jajb (Recommended) or the one that suits you best from Consolidated GApps.
Install recovery:
Reboot your device into Odin mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
Confirm the following warning message with the Volume-Up button.
Connect your device to your PC via USB
Make sure the device driver's are installed on your PC
Start Odin
In Odin select PDA and select the recovery image (recovery.tar.md5)
Check that only "Auto Reboot" and "F. Reset Time" is set
Click on "Start": the kernel image should be flashed now and the device should reboot afterwards. By flashing the recovery, your warranty will be void.
After the recovery flashing process was successful, power of your device. If not restart into Download mode and flash again or flash the stock rom.
Before you flash:
You need the latest TWRP recovery (see links above). Otherwise TWRP might not be able to flash the ROM.
Wipe the device to avoid problems with remaining files from the old installation (see instructions below). This also applies if you already installed an older version of CM 12.1.
Flash CyanogenMod:
Reboot into recovery mode (Press Volume-Up + Home + Power button)
If you come from a stock ROM, this is your opportunity to make a Backup of your phone(Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM (for me it got stuck after a restore during boot. But the backup was made with a different version of TWRP, so it might work in general) - simply do not expect too much of it at the moment.
If you haven't copied the installation files yet, you can now copy the GApps and CyanogenMod zip to your internal sd or external sd (be careful not to put the files into the data directory of the internal sd card as this will be deleted in the next step). Be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files. If MTP does not work from recovery, try it directly from Android or remove the external sd card from the phone and put it into your PC.
Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe). Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
Install the CM 12.1 ROM zip-package
Install the GApps zip-package
Reboot the system and enjoy a Lollipop
How to root:
No SuperSu is needed as CyanogenMod already comes with integrated root support. Root access is disabled by default.
You normally do not need root access. If you want to activate root access for apps, do the following:
Open the Settings menu, select "About Phone"
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.
In case you want to go back to the stock ROM:
lf you do not have the latest stock ROM you can download it from SamMobile
Reboot your phone into Odin mode
Open Odin on your PC and connect your smartphone with your PC via USB
If you have a zip-file unzip it so that you have a .tar.md5 file
In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
Normally the stock rom fails to boot as the data from CM12 is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
Reboot
Changelog
Code:
09/08/2015:
*Update kernel to T235XXU1AOD1
*Synchronize with newest CM 12.1 sources (contains stagefright patches)
*Fixed black screen on minimal brightness
12/07/2015:
* Charging animation in standby-mode fixed
11/07/2015:
* Update to newest CyanogenMod sources (LMY48G)
* Left touchkey working now (configured as App-Switch button)
* Camera Preview working (saving a picture might still crash)
30/06/2015:
* Image sizes reduced to fix "unable to mount /system" problems
28/06/2015:
* Initial test-build
This section is for developers:
A README file with build instructions can be found here:
https://github.com/cm-3470/patcher_degaslte
Sources:
Code:
https://github.com/cm-3470/android_device_samsung_degaslte
https://github.com/cm-3470/android_vendor_samsung_degaslte
https://github.com/cm-3470/android_kernel_samsung_degaslte
https://github.com/cm-3470/android_device_samsung_smdk3470-common
Developers welcome
Help from other developers is always welcome. See the bug/feature section and this thread to see what is missing. Just give some short info (here in this thread or PM) that you want to work on some issue or feature so that work can be synchronized. Maybe there are also other devs that want to work with you on the same issue.
Knowledge in how the kernel works and good programming skills in C, C++ and Java would be nice but not necessary for all problems. At least you should be able to build the ROM and test your changes yourself but you do not need experience in porting ROMs.
XDA:DevDB Information
[T235][ROM][5.1.1][LMY48G] CyanogenMod 12.1 for T235(Y) [Alpha 09/08/2015], ROM for the Samsung Galaxy Tab 4
Contributors
hennymcc
Source Code: https://github.com/cm-3470
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version from 09/08/2015]
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-06-29
Last Updated 2015-09-24
i've tried to test the rom but i can't install so far... i've wiped all but it said it can't mount system again...
http://www.mobosdata.com/samsung-galaxy-tab-4-7-0-lte-sm-t235y
According to this the SM-T235Y is based on Marvel cpu vs exynos on the sm-t235
Does anyone really know the differences ? On another page i read the sm-t235y has a snapdragon 400 ...
Hectic confusing samsung numbering + different devices with same model name .
@hennymcc
do you have included selinux_defconfig in your twrp kernel?
androidboot.selinux=disabled at twrps kernel cmd line should be removed
i wiped system and all partitions using your new twrp but when i install the zip file then /system becomes unmountable
/system is formated ext4
should i try to format it f2fs ?
interstellar22 said:
i wiped system and all partitions using your new twrp but when i install the zip file then /system becomes unmountable
/system is formated ext4
should i try to format it f2fs ?
Click to expand...
Click to collapse
any marvell devices will not work with this or any other custom rom.
sub77 said:
any marvell devices will not work with this or any other custom rom.
Click to expand...
Click to collapse
this is an exynos device not marvell
and now for some reason i cant restore the backup i made
i tryed restorng the backup with twrp 2.8.6.0 recovery from this thread and the 2.8.1.0 from the other.
one gives boot animation loop and the other is stuck at boot
hennymcc said:
In case you want to go back to the stock ROM:
lf you do not have the latest stock ROM you can download it from SamMobile
Click to expand...
Click to collapse
Stock Roms on Android File Host (quicker, free-er host site than Sammobile)
@interstellar22 did you try wiping cache after you restored, before you booted?
thisisapoorusernamechoice said:
Stock Roms on Android File Host (quicker, free-er host site than Sammobile)
@interstellar22 did you try wiping cache after you restored, before you booted?
Click to expand...
Click to collapse
i tryed once without wiping cache, but i had cache backed up also
then i tryed to do a factory reset
still stuck at bootlogo
and adb logcat and adb devices shows nothing
sub77 said:
@hennymcc
do you have included selinux_defconfig in your twrp kernel?
androidboot.selinux=disabled at twrps kernel cmd line should be removed
Click to expand...
Click to collapse
The default selinux setting is enforced. As the selinux configuration files are not complete, Android would not boot.
Setting androidboot.selinux=permissive might work, but when I tested this setting on my S5 mini, it was rather unstable for some reason.
interstellar22 said:
http://www.mobosdata.com/samsung-galaxy-tab-4-7-0-lte-sm-t235y
According to this the SM-T235Y is based on Marvel cpu vs exynos on the sm-t235
Does anyone really know the differences ? On another page i read the sm-t235y has a snapdragon 400 ...
Hectic confusing samsung numbering + different devices with same model name .
Click to expand...
Click to collapse
sub77 said:
any marvell devices will not work with this or any other custom rom.
Click to expand...
Click to collapse
interstellar22 said:
this is an exynos device not marvell
Click to expand...
Click to collapse
T235 and T235Y definitely use Exynos 3470 SoCs. Here an extract from the T235Y default.prop:
Code:
ro.product.model=SM-T235Y
ro.product.name=degasltezt
ro.product.device=degaslte
ro.product.board=universal3470
ro.chipname=exynos3470
The default.prop file of the T235 is similar, only that the product name is degasltexx.
Marvell's PXA1088 SoC is used in the T230/NU which is the non-LTE (WiFi-only) variant of the Tab 4 7.0.
Marvell's PXA1088 and Samsung's Exynos3470 are totally different and have nothing in common (except an ARM core), the same applies to Qualcomm's Snapdragon. There are many websites that mention wrong SoC names as Samsung's naming scheme is rather confusing.
The same applies to the S5 Mini: G800F/M/Y -> Exynos3470, G800H -> Qualcomm Snapdragon.
corneo said:
i've tried to test the rom but i can't install so far... i've wiped all but it said it can't mount system again...
Click to expand...
Click to collapse
Code:
Info: format successful
I:mkfs.f2fs -t 1 /dev/block/mmcblk0p18 process ended with RC=0
Done.
Why was the system partition formatted with f2fs? The default file system is ext4.
The TWRP partition table is hardcoded to ext4 so that's probably the reason for these lines:
Code:
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p18', current file system: 'ext4'
Could you reformat it with ext4?
interstellar22 said:
i tryed once without wiping cache, but i had cache backed up also
then i tryed to do a factory reset
still stuck at bootlogo
and adb logcat and adb devices shows nothing
Click to expand...
Click to collapse
Did you flash the stock ROM with Odin?
And afterwards wipe the data partition and then the cache with the _stock_ recovery (as TWRP is not available after flashing the stock ROM)?
interstellar22 said:
i wiped system and all partitions using your new twrp but when i install the zip file then /system becomes unmountable
/system is formated ext4
should i try to format it f2fs ?
Click to expand...
Click to collapse
Short summary:
interstellar22 and corneo tried it so far and both got the error message "/system unmountable"
Strange that corneo was able to generate an error log.
@corneo: did you create the log with adb?
At least according to corneo's log, it seams that after the F2FS format the partition is reformatted with EXT4 afterwards:
Code:
Formatting system using make_ext4fs function.
It also says:
Code:
erasing 588800 blocks
blkdiscard failed: Invalid argument
writing 134395 blocks of new data
lseek64 failed: Invalid argument
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/cm-12.1-20150627-UNOFFICIAL-degaslte.zip'
Error flashing zip '/external_sd/cm-12.1-20150627-UNOFFICIAL-degaslte.zip'
Not that sure about what causes this error. Maybe the partition sizes have to be changed.
hennymcc said:
Short summary:
interstellar22 and corneo tried it so far and both got the error message "/system unmountable"
Strange that corneo was able to generate an error log.
@corneo: did you create the log with adb?
At least according to corneo's log, it seams that after the F2FS format the partition is reformatted with EXT4 afterwards:
Code:
Formatting system using make_ext4fs function.
It also says:
Code:
erasing 588800 blocks
blkdiscard failed: Invalid argument
writing 134395 blocks of new data
lseek64 failed: Invalid argument
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/cm-12.1-20150627-UNOFFICIAL-degaslte.zip'
Error flashing zip '/external_sd/cm-12.1-20150627-UNOFFICIAL-degaslte.zip'
Not that sure about what causes this error. Maybe the partition sizes have to be changed.
Click to expand...
Click to collapse
i've created the log in recovery and copied it to sd.
now i flashed the tab again with odin and try it again. same issue...
Gesendet von meinem One M8
i managed to get the original firmware back with odin
could it be that the system.new.dat file is corrupted ?
i had formated system with ext4 then did the update and was still getting unable to mount /system afterwards
so most probably the system.new.dat file has some problems or i have no idea why i cant mount /system afterwards
Maybe it is caused by wrong BOARD_...IMAGE_PARTITION_SIZE values in BoardConfig.mk.
Could you please post the contents of /proc/mounts and /proc/partitions:
Code:
cat /proc/mounts
cat /proc/partitions
The above should be performed from the stock ROM. The device must be rooted.
Hmm, the problem might be here:
Code:
Patching system image unconditionally...
blockimg version is 2
erasing 588800 blocks
blkdiscard failed: Invalid argument
writing 134395 blocks of new data
lseek64 failed: Invalid argument
588800 * 4096 = 2411724800 bytes (2,2GB)
This is the value of the BoardConfig.mk taken from the S5 Mini (BOARD_SYSTEMIMAGE_PARTITION_SIZE := 2411724800).
But the system partition is only 2233466880 bytes:
Code:
/system | /dev/block/mmcblk0p18 | Size: 2096MB Used: 1828MB Free: 268MB Backup Size: 1828MB
Code:
I:wipe_path '/system'
Formatting System using make_ext4fs function.
Creating filesystem with parameters:
Size: 2233466880
The system.img itself is only 500MB in size. So I guess reducing the image size should fix the problem.
An updated ROM is available. The image sizes have been reduced. I hope this fixes the problems with the system-partition.
Also use the new TWRP recovery as the partition sizes might be hardcoded in the old one.
good news! new recovery and system image works! very smooth so far, searching for bugs now. the only one i found are the extended settings option. it doesn't work but thats no problem for me. thank you very much!
Gesendet von meinem One M8
OFFICAL TWRP RELEASED, this thread is no longer active. 3-30-2018
https://twrp.me/motorola/motorolamotox4.html
---
UNOFFICIAL BUILDS -- USE AT YOUR OWN RISK AND KNOW HOW TO GET YOURSELF OUT OF TROUBLE IF IT ARISES. I ASSUME NO RESPONSIBILITY FOR YOUR BROKEN THINGS.
UPDATED 01-11-2018
There are now 7.1 based and 8.0 based builds. Obviously, be careful to select the proper download. While I don't think flashing/booting the wrong one would permanently brick the device, let's not find out
For now I will not be attempting to make data decryption work. It is REQUIRED that you unencrypt your device by formatting userdata, so back up your stuff first.
IMPORTANT NOTES: TWRP for OREO is a bit of a pain as it currently requires manually editing your fstab. I have tried to automate this process, but it breaks stuff. So just be aware before you begin that it is a rather time consuming process.
If you make any change to your boot partition after flashing SuperSU, you will need to reflash it or you will get a bootloop.
8.0 OREO TWRP INSTALLATION:
OREO SEEMS VERY FINICKY AND DOES NOT LIKE CHANGES TO ITS FILESYSTEM -- BE PREPARED TO REFLASH STOCK.
0. FLASH OREO FACTORY IMAGE (may work otherwise, but we should be starting from fresh stock here)
1. Download FASTBOOT BOOTABLE TWRP for 8.0/OREO below
2. Download SuperSU 2.82 SR5 below
3. Move SuperSU to external SD or USB OTG
4. From bootloader, fasboot BOOT TWRP
5. Flash SuperSU (note: do not format /data now... not necessary and will cause errors on boot)
6. Reboot system
7. With any root file editor/text editor (Amaze, Total Commander, etc) open /system/vendor/etc/fstab.qcom as a text file for editing.
8. At the end of the /data partition entry, delete "fileencryption=ice" and replace it with "encryptable=footer".
9. Save fstab.qcom (and make sure it is actually saved properly!)
10. Reboot to bootloader and fasboot BOOT TWRP
11. Go to Wipe, hit the FORMAT DATA button, and type "yes" to format /data. This will erase your data, obviously:silly:
12. Reboot system (should now be unencrypted, verify in Settings>Security or by booting TWRP and checking /data with File Manager.
If you later choose to flash TWRP (not the bootable we used here!), you may need to flash SuperSU again to avoid bootloops.
7.1.1 NOUGAT TWRP INSTALLATION:
1. Download current TWRP for 7.1.1 build below
2. Download SuperSU 2.85 SR5 (https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
3. Move SuperSU to your external Micro SD card.
4. Fastboot flash the TWRP image.
5. Reboot to TWRP.
6. FORMAT data (not wipe...use the "FORMAT DATA" button and type "yes". OBVIOUSLY THIS WILL ERASE YOUR DATA)
7. Install SuperSU 2.85 SR5
8. Reboot to system (it WILL bootloop a couple times...don't panic!) and confirm that device is unencrypted by checking that SETTINGS>SECURITY>ENCRYPTION now prompts "encrypt" (don't do it).
DOWNLOADS:
TWRP FOR 7.1.1 (Nougat) DOWNLOAD: https://drive.google.com/open?id=1Et-AQgCNx7WDAwzihlI51euUa2ixKHEP
TWRP FOR 8.0 (Oreo) DOWNLOAD: https://drive.google.com/open?id=1WcVS_3rloF7jxPulj_jKxfsp3zy5pB5N
FASTBOOT BOOTABLE TWRP IMAGE (OREO BASED): https://drive.google.com/open?id=12ClviqtEjtflB63UQ1CZQNKEqkprBO0u **For temporary TWRP boot using "fastboot boot". Do not flash or you will be stuck in recovery!**
DEVICE TREE: https://github.com/mightysween/android_device_motorola_payton (NEEDS TO BE UPDATED WITH OREO BRANCH)
changelog:
BETA4
-reverted to 3.2.0 for current build (release candidate rebased to 3.2.1).
-fixed "format data" button
-finalized fstab for OTG/SD/INTERNAL mounting
-target is now UNENCRYPTED devices only (/data decrypt will not be fixed)
BETA3
-Rebased to TWRP 3.2.1
-USB OTG working
-all partitions mounting correctly
-considered working except for decrypt and MTP/ADB
BETA2
-fixed internal storage mount
BETA1
- updated source to TWRP 3.2.0
ALPHA3
- Fixed USB mounting (adb/mtp still nonfunctional) BROKEN IN BETA1
ALPHA2
- SD Card fixed
ALPHA1
- /system is now properly mounted.
- now plays nice with our working root method.
- ramdisk is patched to prevent first boot encryption once /data is decrypted (now requires flashable ZIP)
NOT WORKING:
adb/mtp/sideload
/data decryption (abandoned -- /data access requires unencryption)
CREDITS: @kraatus90 for kernel fix, @Chainfire for SuperSU, @jcadduono for no-verity-opt-encrypt scripts.
---
Thanks so much for all your work!
hi,
you said this is really unstable and could brick the device easily. however, you seem to be testing and experimenting with your device a lot, so i'd like to ask if you have any particual unbrick method that you use when something goes wrong.. like, a via fastboot flashable image or something simmilar...?
thanks for your work!
Thanks for you work. If you have any unbrick methods pls tell.appreciated your work ?
I am not going to provide step by step "unbrick" methods, because until the partitioning is properly set up, TWRP has potential access to things that can not be fixed.
Again, this is still highly experimental.
All that said, my entire process to protect any device remains the same: Have a backup for every partition you will be testing, make as few changes as possible at a time, test boot images before flashing (fastboot boot), and test restore methods frequently (flashing back to stock or backups), and don't do anything unless you are highly certain of the outcome.
By those standards, there is nothing to gain by installing TWRP right now, as its basic function (install/backup/restore) is not set up yet.
Found the BoardConfig flag to enable FBE (TW_INCLUDE_CRYPTO_FBE := true) but do not have the lib it is dependent on (libe4crypt) and I don't see it anywhere yet...
For reference (not sure this is most current, but it demonstrates the process)
https://github.com/nijel8/TWRP/commit/bd7492de28963b7e74e8e5d3f17ec9a5a287d9c3
I have confirmed that FBE support is present in the source, dependent on this missing module... so need to figure out where/how to enable it.
It is possible that this entire process is specific to only certain devices (i.e. Pixel, Nexus). If this is the case, we may be stuck at this point for awhile.
Obvious workaround is to not be encrypted to begin with -- but that isn't a "solution".
mightysween said:
It is possible that this entire process is specific to only certain devices (i.e. Pixel, Nexus). If this is the case, we may be stuck at this point for awhile.
Click to expand...
Click to collapse
This appears to be the case, unfortunately. Seems that the TWRP FBE support was built specifically for the Google implementation of FBE which was merged into kernel sources for Nexus and Pixel. Not even using the qseecomd I assumed it was... will remove on next build.
Info on FBE:
https://source.android.com/security/encryption/file-based
Will be testing options to disable forced encryption, and if necessary dm-verity...
Anyone who wants to dig through kernel for related flags and props, it would be greatly appreciated!
Hey, where did the big "format data" button go in TWRP? Is that optional on compile... can't find a flag for it...
Making good progress this morning.
Seem to have a build with properly decrypted /system, and working SD Card. I also have patched the boot.img to disable forced encryption on the first boot. But now, I can not find a safe way to fully format (not "wipe") the /data partition. As mentioned in the previous post, the "FORMAT DATA" button is missing. The fastboot command "fastboot format userdata" returns an error that it does not support RAW format.
Need to figure out why this is happening... and once I do, I believe I can reformat /data without encryption and then will have an almost fully working TWRP build. Obviously, the ideal solution would be to have TWRP work out of the gate with an encrypted /data, but until then this is going to be our best option.
Will post an updated test build in the OP soon.... needs further testing before I would recommend non-expert users to try it.
Getting very close now!
UPDATE: ADDED NEW BUILD TO OP
---
Also, just occurred to me that the ramdisk will need to be patched every time, so now that I have SD card support will be testing some of the existing flashable ZIPs out there that are designed specificially to prevent first-boot encryption and/or disable dm-verity.
---
mightysween said:
Hey, where did the big "format data" button go in TWRP? Is that optional on compile... can't find a flag for it...
Click to expand...
Click to collapse
This is really the only hold up... I changed the partition from 'Advanced Wipe", but as expected, it was still encrypted on boot as it doesn't actually format the footer where encryption is stored. I can't figure out where that darn "FORMAT DATA" button ran off to, and that is exactly what we need here.
mightysween said:
This is really the only hold up... I changed the partition from 'Advanced Wipe", but as expected, it was still encrypted on boot as it doesn't actually format the footer where encryption is stored. I can't figure out where that darn "FORMAT DATA" button ran off to, and that is exactly what we need here.
Click to expand...
Click to collapse
I don't know how to help except to say that using TWRP 3.1.0-MOD_1 with my XT1254 (DROID Turbo), when you go to wipe it has two buttons --- one on the left for Advanced Wipe and Format Data on the right.
johnjingle said:
I don't know how to help except to say that using TWRP 3.1.0-MOD_1 with my XT1254 (DROID Turbo), when you go to wipe it has two buttons --- one on the left for Advanced Wipe and Format Data on the right.
Click to expand...
Click to collapse
I have 3.1.1-0 (same version I am building here) on several other devices, and the button is there. It has to be triggered by something during compile, but I can't figure it out. Driving me nuts
Looking through TWRP source, and can find actions for every other button (wipe, backup, restore, install, etc) but not for format. Hmm.
I posted over on an old but semi-active TWRP flags thread, maybe someone will have some insight.
Wondering if I make a stock boot image without the encryption tag in fstab, and then wipe data and reboot... then flash my image. That may make it so the data partition is never encrypted in the first place and allow TWRP to work.
But that is an ugly, non-user friendly fix. Why can't we just format /data?
---
Final update for today... this seems to be a compile issue, which is a good thing. I tried to manually decrypt /data from the TWRP command line, and got this:
No crypto support was compiled into this build.
Click to expand...
Click to collapse
So, I must be missing something in boardconfig still... and maybe need to set up a small proprietary vendor folder with the necessary libs
mightysween said:
Final update for today... this seems to be a compile issue, which is a good thing. I tried to manually decrypt /data from the TWRP command line, and got this:
So, I must be missing something in boardconfig still... and maybe need to set up a small proprietary vendor folder with the necessary libs
Click to expand...
Click to collapse
Thanks for doing all of this! I wish I had the time and knowledge to help.
Had a few PM's checking on TWRP status, so an update.
The good news is that the X4 is using Qualcomm based decryption for /data... the bad news is that most if it seems to be closed source. This will take some time for me to figure out, but I have already made some progress by sifting through logs.
Right now, I am trying to find a device with similar decrypt scheme to have some more guidance on the process.
mightysween said:
Had a few PM's checking on TWRP status, so an update.
The good news is that the X4 is using Qualcomm based decryption for /data... the bad news is that most if it seems to be closed source. This will take some time for me to figure out, but I have already made some progress by sifting through logs.
Right now, I am trying to find a device with similar decrypt scheme to have some more guidance on the process.
Click to expand...
Click to collapse
dont know all about these things but maybe xiaomi mi a1 twrp can help as it is also using same a/b partition. and twrp is already there for it
vivek638 said:
dont know all about these things but maybe xiaomi mi a1 twrp can help as it is also using same a/b partition. and twrp is already there for it
Click to expand...
Click to collapse
Thanks, the Mi A1 is one of the devices I have been comparing to, and has been quite helpful.
mightysween said:
Thanks, the Mi A1 is one of the devices I have been comparing to, and has been quite helpful.
Click to expand...
Click to collapse
Keep searching. wish i could have helped but dont know anything about compiling n all..
I'm not much of a programmer, but I can look through the files. Is there anything in particular we're searching for?