Database Users

Mod flipout

Hello,
There is someone really working on a port of any custom to this cellphone?
I have brought a new phone (Samsung Galaxy Nexus) and I want to port my old MB511 to CyanogenMOD or MIUI.
I have some experience on embedded systems, bootloaders, Linux kernel development, but nothing related to cellphone or android.
So, I really want to start a mod but I want some help in order to make it
Reading (and-developers DOT com) I realized that I need:
1) Use recover 'Open Recovery' or 2ndboot
2) Compile Cyanogen kernel or MIUI (For OMAP-3410)
3) try to boot kernel
4) port cyanogen/miui
5) copy devices binaries
Do someone have any clue or a start point in order to get any step done? I'm new.
Any help will be appreciate.

1.There is someone really working on a port of any custom to this cellphone?
NO. No anyone.
1) Use recover 'Open Recovery' or 2ndboot
Dexter_nlb FlipOut Recovery (CWM based v2.5.1.2)
http://forum.xda-developers.com/showthread.php?t=942160
polovinamozga Big Bootstrapped Recovery
http://forum.xda-developers.com/showpost.php?p=14796425&postcount=412
laidaxin 2ndInit_Installer (For MB508)
http://forum.xda-developers.com/showthread.php?t=1471549
2) Compile Cyanogen kernel or MIUI (For OMAP-3410)
Flipout's bootloader is locked. So...
3) try to boot kernel
Flipout's bootloader is locked. So...
4) port cyanogen/miui
Maybe you can ask laidaxin.
He would ready to port MB502.
He already port CM7 to MB508 success.
I hope this was useful to you

Just port CM7 from the Flipside.... Change libs and build.prop... They have the same processor and both have Android 2.2 I believe
Sent from my MB520 using XDA App

marquae11 said:
Just port CM7 from the Flipside.... Change libs and build.prop... They have the same processor and both have Android 2.2 I believe
Sent from my MB520 using XDA App
Click to expand...
Click to collapse
very good ideea, but the bootloader is still locked

laluth said:
1.There is someone really working on a port of any custom to this cellphone?
NO. No anyone.
1) Use recover 'Open Recovery' or 2ndboot
Dexter_nlb FlipOut Recovery (CWM based v2.5.1.2)
http://forum.xda-developers.com/showthread.php?t=942160
polovinamozga Big Bootstrapped Recovery
http://forum.xda-developers.com/showpost.php?p=14796425&postcount=412
laidaxin 2ndInit_Installer (For MB508)
http://forum.xda-developers.com/showthread.php?t=1471549
2) Compile Cyanogen kernel or MIUI (For OMAP-3410)
Flipout's bootloader is locked. So...
3) try to boot kernel
Flipout's bootloader is locked. So...
4) port cyanogen/miui
Maybe you can ask laidaxin.
He would ready to port MB502.
He already port CM7 to MB508 success.
I hope this was useful to you
Click to expand...
Click to collapse
my recovery can't run in 2.1ROM,and the other two can't update ZIP because it can't mount system partion. I still finding the recovery and try to make a one that can help me to update to CM7 for MB502.

vladtdr said:
very good ideea, but the bootloader is still locked
Click to expand...
Click to collapse
The bravo and defy bootloader is locked yet I can flash a defy rom by deleting boot.img and devtree.img then it should be fine.
sent from my Motorola Bravo running CM7 White Rabbit Edition 1.3 with my added Beats Audio and Bravia Engine!

laluth said:
1) Use recover 'Open Recovery' or 2ndboot
Dexter_nlb FlipOut Recovery (CWM based v2.5.1.2)
http://forum.xda-developers.com/showthread.php?t=942160
polovinamozga Big Bootstrapped Recovery
http://forum.xda-developers.com/showpost.php?p=14796425&postcount=412
laidaxin 2ndInit_Installer (For MB508)
http://forum.xda-developers.com/showthread.php?t=1471549
Click to expand...
Click to collapse
Has someone fully tested any of these recovery
full backup and full restore?

laidaxin said:
my recovery can't run in 2.1ROM,and the other two can't update ZIP because it can't mount system partion. I still finding the recovery and try to make a one that can help me to update to CM7 for MB502.
Click to expand...
Click to collapse
I just done by hand boot using Big Bootstrapped Recovery method (looking source code) - and I saw some wrong mount methods. So I could I help you and maybe we can make a mod together.
I have a CWM functional om my MB511 but I don't figure out how to do next step (port CM/MIUI),
What I did:
1) copy necessary files https://github.com/iuridiniz/CharmBootstrap/assets
Code:
adb push hijack/ /sdcard/hijack
2) backup everything (adb shell as root)
Code:
#!/bin/sh
BACKUP_DIR=/sdcard/backup-`date +%s`
mkdir $BACKUP_DIR
echo "
/cdrom/cdrom_vfat.bin
/system/bin/mot_boot_mode
/sbin/adbd
/sbin/e2fsck
/sbin/fix_permissions
/sbin/killrecovery.sh
/sbin/mke2fs
/sbin/nandroid-md5.sh
/sbin/parted
/sbin/postrecoveryboot.sh
/sbin/recovery
/sbin/sdparted
/sbin/tune2fs
" | \
while read i; do
if [ -n "$i" ]; then
cp $i $BACKUP_DIR
fi
done
Figure out which partition has /system and /cdrom using mount
Code:
mount
output:
Code:
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock7 /system yaffs2 ro 0 0
/dev/block/mtdblock9 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock8 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock6 /cdrom yaffs2 rw 0 0
tmpfs /tmp tmpfs rw,size=2048k 0 0
/dev/block/mtdblock0 /pds yaffs2 rw,nosuid,nodev 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw 0 0
/dev/block/vold/179:2 /data/sdext2 vfat rw,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,errors=remount-ro 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
system: /dev/block/mtdblock7 (in ro mode, need change)
cdrom: /dev/block/mtdblock6 (in rw mode, no change)
Install HIJACK BOOTSTRAP
Code:
##########################################################################
# HIJACK
mount -oremount,rw /dev/block/mtdblock7 /system
cp /sdcard/hijack/mot_boot_mode.bin /system/bin/mot_boot_mode.bin ;
cp /sdcard/hijack/hijack /system/bin/hijack ;
rm /system/bin/mot_boot_mode
ln -s hijack /system/bin/mot_boot_mode
mount -oremount,ro /dev/block/mtdblock7 /system
Install clockworkmode
Code:
################################################################3
# RECOVERY
#mount -oremount,rw /dev/block/mtdblock6 /cdrom
rm /cdrom/cdrom_vfat.bin
mkdir /cdrom/recovery
cp /sdcard/hijack/update-binary /cdrom/recovery/update-binary
cp /sdcard/hijack/update.zip /cdrom/recovery/recovery.zip
cp /sdcard/hijack/hijack /cdrom/recovery/hijack
cp /sdcard/hijack/mot_boot_mode.bin /cdrom/recovery/logwrapper
#mount -oremount,ro /dev/block/mtdblock6 /cdrom
Now If I want to boot in recovery mode I need to create this file /data/.recovery_mode
Code:
echo 1 > /data/.recovery_mode
Thanks to polovinamozga

To port a CM7 ROM,the recovery is the first,but we still need a way to look at the logcat during booting the system,and a way to copy the .rc files to /sbin.These three things are most important!
maybe we need a 2nd-init boot thing that can only success to ports the CM,I still working on this.
if you want to work with me,pleast sent email to [email protected].

laidaxin said:
To port a CM7 ROM
Click to expand...
Click to collapse
But without upgrading the kernel will be possible to run CM7 (Gingerbread) ? I think that only CM6 (Froyo) will be possible.
Charm already has Froyo?

Defy CM9 came run with the 2.2 froyo kernel,why charm or filpout cant run 2.3 with the 2.1 kernel?
It is possable to build and run 2.3 with the older kernel.

laidaxin said:
Defy CM9 came run with the 2.2 froyo kernel,why charm or filpout cant run 2.3 with the 2.1 kernel?
Click to expand...
Click to collapse
I don't know, it's because all tutorial for defy CM9 I'found ask me to upgrade to 2.2 (from 2.1) before.

even froYo 2.2 would be such a difference! a lot of apps could be installed... do you really think you can make it! *____*

iuridiniz said:
I don't know, it's because all tutorial for defy CM9 I'found ask me to upgrade to 2.2 (from 2.1) before.
Click to expand...
Click to collapse
yes! Because some bin files can't run in the 2.1 system,like the bootmenu and the bootstrape recovery's bin files.
But the kernel can run the 2.3.So what we can do is to make a bootstrap recovery that can run in the 2.1 ROM and then jump to the 2.3.
It is difficult that we can't flash the kernel to the system,a hard work!

i think shuld bee a way to by-pass the boot loader ... no ?

spinky360 said:
i think shuld bee a way to by-pass the boot loader ... no ?
Click to expand...
Click to collapse
yes!!!This is what i do now,but so difficult that only me to work on this.

Geko90 said:
even froYo 2.2 would be such a difference! a lot of apps could be installed... do you really think you can make it! *____*
Click to expand...
Click to collapse
I agree with that! Even a 2.2 based firmware would make a difference on the Flipout, so even if Cyanogen Mod 6 is possible I would love to use it on our phone!
Of course, if CM7 is a realistic option I would prefer that

laidaxin said:
yes!!!This is what i do now,but so difficult that only me to work on this.
Click to expand...
Click to collapse
Ther is smth with wath to help u ?
on wath version of bootloader u are working ?

mark this thread for reading later on cellphone

laidaxin said:
yes!!!This is what i do now,but so difficult that only me to work on this.
Click to expand...
Click to collapse
HI,
I'll try to fix flipout recovery or bootstrap recovery on my ME511.
I've found source codes of these two recovery and tested the apk on my phone.
It seems that bootstrap recovery can backup and restore successfully, but flipout recovery can only backup, it has no response when starting to restore system partition.
I'll test them more and make a zip file to try to update it using recovery. And make some fix to let it works well on flipout or charm.
Sent from my U8500 using XDA
Edit1：
I've tested that flipout recovery can't restore successfully if bootstrap recovery is installed and then un-installed before flipout recovery is installed , but bootstrap recovery can restore successfully if flipout recovery is installed and then un-installed before bootstrap recovery is installed.
If bootstrap recovery is installed and then un-installed before flipout recovery, one way to let flipout recovery can restore again is flash sbf and start from the beginning.
Edit2：
update zip files using flipout recovery failed. I'll test bootstrap recovery after flash sbf and start from the beginning.

[Q][HELP]My TAB is BRICKED AFTER FLASH quicksilver 0.8

Firstly have to thank you the rom developer, the ROM is very smooth, I like it so much.
But I am facing a serious problem now, while I flashing the 0.8 version, updating half way, the tab is auto reboot, and now it was stop at "Samsung GALAXY Tab 7.7". It is too bad.
I post here is trying to get help, below is the step that I do before boot looping:
1) Update my tab 7.7 from HC to ICS (Australia firmware with Odin) It run smooth.
2) Download CWM.zip, download QuickSilver 0.5, 0.6, 0.7
3) Boot my tab into recovery mode, too bad I failed to install via the android recovery, so I install CMW to install the QuickSilver, from 0.5 to 0.6, to 0.7
4) I install the ROM without wipe anything, and hooray, it running SMOOTH
5) Today, I check on the same post, and found that there are new version for the ROM, 0.8 & 0.9
6) But this time, 0.8 need a wipe data and wipe cache. So i just follow the instruction.
7) I boot into CWM recovery, and wipe data, wipe cache and wipe Davch.
8) Then I start flashing 0.8, but in the half way, it auto reboot, and now boot looping in "Samsung Galaxy Tab 7.7"

Solution that have been tried:
1) Flash with PIT + MALAYSIA OFFICIAL Firmware (Odin)
2) Flash Malaysia Official Firmware (Odin)
3) Flash PIT + ICS Australia firmware (Odin)
4) Flash ICS Australia firmware (Odin)
All doesn't work, it auto reboot after installation then just boot looping

But after flashing ICS, I able to access into recovery mode, I try to wide data and factory reset.
But it failed, it stop at:
-- Wiping data...
Formatting /data...
Then it will auto reboot, and boot looping in "Samsung GALAXY Tab 7.7"

when you boot into recovery, is Adb working, can you Adb to your device?
check below thread and see if you have the same issue and try the solution provided to fix corrupted data partition. Let us know how it goes and using which OS HC or ICS.
http://forum.xda-developers.com/showthread.php?t=1625675&highlight=bootscreen

zorbakun said:
when you boot into recovery, is Adb working, can you Adb to your device?
check below thread and see if you have the same issue and try the solution provided to fix corrupted data partition. Let us know how it goes and using which OS HC or ICS.
http://forum.xda-developers.com/showthread.php?t=1625675&highlight=bootscreen
Click to expand...
Click to collapse
I can use ADB, I am trying the command that shown in the thread, but no hope:
e2fsck -c /dev/block/mmcblk0p10 (3G)
it show an error message:
/dev/block/mmcblk0p9: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p9: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p9: 1596/53312 files (0.0% non-contiguous), 189332/212992 bloc
ks
~ #
~ # e2fsck -c /dev/block/mmcblk0p10
e2fsck -c /dev/block/mmcblk0p10
e2fsck 1.41.6 (30-May-2009)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p
10
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ #

I'm not sure what you should do next! did your TAB test positive for the SuperBrick Bug?! May be Entropy512 can help you...Good Luck.

Flash stock rom with odin
Sent from my GT-S5660 using xda premium

Try to get to Download Mode (Not Recovery) > Use ODIN on PC > Flash the PIT > Reboot > Flash the stock ICS > Flash the ROM
I've got the Download Mode bootloop first time I've tried the Quicksilver or Zeta, I solved it the way described above. Hope this helps.

BAD_BOY_KIEV said:
Try to get to Download Mode (Not Recovery) > Use ODIN on PC > Flash the PIT > Reboot > Flash the stock ICS > Flash the ROM
I've got the Download Mode bootloop first time I've tried the Quicksilver or Zeta, I solved it the way described above. Hope this helps.
Click to expand...
Click to collapse
Thanks for everyone help, last night I am trying on flash a PIT (which I found from XDA P6800_ATO_PIT), and then boot into recovery, and use adb shell, e2fsck -c /dev/block/mmcblk0p10
That have been 8 hours, it still keep running on:
.......................................................................
Error reading block 131299 (Attempt to read block from filesystem resulted in sh
ort read) while getting next inode from scan. Ignore error? yes
Force rewrite? yes
Error reading block 131300 (Attempt to read block from filesystem resulted in sh
ort read) while getting next inode from scan. Ignore error? yes
Force rewrite? yes
Error reading block 131301 (Attempt to read block from filesystem resulted in sh
ort read) while getting next inode from scan. Ignore error? yes
Force rewrite? yes
Is that mean it try to recover? Or just checking the memory? Shall I terminate it?

BAD_BOY_KIEV said:
Try to get to Download Mode (Not Recovery) > Use ODIN on PC > Flash the PIT > Reboot > Flash the stock ICS > Flash the ROM
I've got the Download Mode bootloop first time I've tried the Quicksilver or Zeta, I solved it the way described above. Hope this helps.
Click to expand...
Click to collapse
I think I didn't try this, but what I have try is:
Download Mode (Not Recovery) > Use ODIN on PC > Flash the PIT > Reboot > Flash the stock ICS (odin) > reboot
But it still boot looping.
May I know, do you do a wiping after flash ICS and before flash the other ROM?
You flash the rom with Odin? Or CWM?

this is the reason i always try my best to stay away from noob custom roms for me stock ICS is working great i wonder why people are so curious to try buggy roms right now these two custom roms zeta and quciksilver gives nothing advantage over the stock ics

irmani said:
this is the reason i always try my best to stay away from noob custom roms for me stock ICS is working great i wonder why people are so curious to try buggy roms right now these two custom roms zeta and quciksilver gives nothing advantage over the stock ics
Click to expand...
Click to collapse
Because we don't have alot ofnpro devs working on this tab, a few people who obviously know what they're doing are filling in some of the gaps (not gapps)---and they need testers. I applaud everybodys efforts, and its nice to see activity in this forum IMHO. ;-P
Sent from my GT-P6800 using XDA Premium HD app

Same problem!
How we fix the /data/ partition?

update progress:
able to fix /data by
- install parted over recovery mode
follow below step
you must edit start , end position of blk10
parted /dev/block/mmcblk0
Parted 1.8.8.1.179
print
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 264MB 210MB ext4 CACHE
8 264MB 281MB 16.8MB MODEM
9 281MB 1153MB 872MB ext4 FACTORYFS
10 1153MB 15.3GB 14.1GB ext4 DATAFS
11 15.3GB 15.7GB 470MB ext4 HIDDEN
12 15.7GB 15.8GB 8389kB FOTA
rm 10
(parted) mkpartfs primary ext2 4215 6362(parted) name 10 DATAFS
~ # tune2fs -j /dev/block/mmcblk0p10~ # e2fsck -fDp /dev/block/mmcblk0p10
~ # tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p10
~ # e2fsck -fDp /dev/block/mmcblk0p10
Click to expand...
Click to collapse

zoftdev said:
parted /dev/block/mmcblk0
...
print
...
rm 10
(parted) mkpartfs primary ext2 4215 6362
(parted) name 10 DATAFS
~ # tune2fs -j /dev/block/mmcblk0p10
~ # e2fsck -fDp /dev/block/mmcblk0p10
~ # tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p10
~ # e2fsck -fDp /dev/block/mmcblk0p10
Click to expand...
Click to collapse
Thank you zoftdev 1.000.000 times !
after a whole week (day & night) I finally solved the problem with your "fix"
Problem: (7.7 6800 Tab, HC Hong Kong stock)
1. HC Hong Kong stock
2. no wipe
3. install ICS Austria stock
4. no wipe !
5. install Zeta 2 via Odin (not Quicksilver, kinda offtopic here...)
all ok, with old HC data, apps settings
and hence there mistakes begins:
6. install ICS Austria stock again, for a new Zeta CLEAN install
8. wipe data/cache/dalvik, from SD running, not installed CWM 5.5.4.0 (that was the REAL mistake, the wipe)
9. install Zeta 2
10. endless boot loop...
for all week tried everything I knew and all I found on this forum
install Pit, install stock HC, reinstall ICS Austria stock, Pit again, HC Romania, Hong Kong, Vodafone,
wipe data/cache/dalvik again and again, install ICS Austria stock again...
hours and hours, again and again... revers order again,
all non working fixes,
madness...
and finally find your post... install SDK Android
very noob on Android, (I'm an old symbian fan,
did not know much about Android, at I learned a lot about this OS in this week)
Thank you again zoftdev !!!

zoftdev said:
update progress:
able to fix /data by
- install parted over recovery mode
follow below step
you must edit start , end position of blk10
Click to expand...
Click to collapse
Hy,
All goes ok and acording to your instructions until i reac the command
"mkpartfs primary ext2 4215 6362" where unfortunatly after 10-15 minutes it gives me this message:
Error: input/output error during write on /dev/block/mmcblk0
Retry/Ignore/Cancel?
I keep giving it ignore an after the second ignore it says:
writing per-group metadata...x% (time left XXXX:xx)
I am now at 4% after 2 hours....and every 30 second i must hit "ignore" to the error that i mentioned here.
Any ideeas?

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

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

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

Reserved...

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

Very good , thank you very much

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Samsung GT-T230NU - Bricked - Bootloop - TWRP "Unable to Mount"

Tl;dr : Bricked my Table, probably by formatting partitions through TWRP
Hi Everyone, longtime lurker here. I managed to do the (nearly-)impossible and brick my Tab 4. I turn to you in last resort but I may be too far down to save anything, let's see if anyone is up to the challenge!
Specs first:
Samsung SM-T230NU ( 7" / Wi-Fi)
Rooted (TWRP), Stock Rom
I'm fairly certain USB debugging was enabled before the tab bricked
What Happened:
The tab had been acting up due to insufficient internal memory, I decided to factory reset to clear the tablet.
The first factory reset using TWRP didn't remove any of the apps or content on the tab. Probably because I was using Titanium Backup.
So I go back and attempt To Format Data through TWRP an d that's where the trouble began.
All of sudden the Tab was stuck in Bootloop.
My first reaction is to reboot in recovery and see what was going on, and that's when I noticed a problem with TWRP:
{
"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"
}
Exact message is
e:unable to mount '/data'
e:unable to recreate /data/media folder
Updating partition details
e:unable to mount '/data'
e:unable to mount storage
e:unable to mount /data/media during gui startup
full selinux support is present.
e:unable to mount /data/,edia/twrp/.twrps when trying to read settings file.
e:unable to mount '/data'
MTP Enabled
e:unable to mount '/data'
e:unable to mount '/data'
So obviously there's a problem with TWRP, I try flashing it again on the tab by ODIN (Process successful, ODIN picks-up the device) but the problem persists
I also tried flashing a stock rom via TWRP and ODIN, the flash was successful but in both cases the tablet always stayed in bootloop.
Think that's bad? Here's where I probably f***ed up hardcore and bricked the tab; Looking on XDA for solution to get TWRP to work I stumbled onto this thread
Bootloop + E:unable to mount /data
The solution seemed to have worked for others so I stupidly tried entering the following command in TWRP's Terminal Command...
mke2fs -T ext4 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
BOOM, now the tablet doesn't even load into Bootloop anymore, it just boots into this **very reassuring** and **completely normal** screen
Looking further into the thread linked above, I realize I may have formatted a random partition!
"mmcblk0p8" may or may not be identical on the Asus Trasformer TF700 (source of the thread) as it is on the GT-T230NU but I highly doubt it.
In order to be sure, I went back into TWRP and checked my partition sizes and sure enough, Data is now completely empty
The other partitions seem to be all there, especially System and Cache. However there also seems to be something weird with
the "Internal Storage" partition, because when I try to repair this partition TWRP tells me it's and Invalid selection.
I think that re-caps my problem completley. I want to also say I am fully aware I was doing things I didn't fully understand nor had researched, my bad, let's not make this into a shaming thread
I appreciate your help fellow xda-ers
EDIT 1: Since the imgur links aren't working here is the URL for the entire album: http://imgur.com/a/OVB4f

@DeLime well, you might have messed up the partitions. If you can still boot into download mode, in my opinion, I believe you should flash an service firmware that has the PIT file (re partitions and format things accordingly since TWRP in your case can't repair).
Use this tool to download your firmware and be sure to tick the binary nature box. http://forum.xda-developers.com/showthread.php?p=57842725 Once the firmware is downloaded and decrypted, you will need an program called Odin. There are a few posted on xda. Simply open the Odin 3.09 etc, and place the tar.md5 firmware in the appropriate sections in odin. The 4 firmware files should have similar names like Odin (PDA, CSC etc). Then plug your tablet to your computer while your tablet is in download mode and hit start on Odin. Then you can flash twrp and repair your data partition. The option should be in wipe somewhere I can't remember. There shouldn't be the need to use terminal.
If anyone else has any other suggestions, let me know.
Sent from my XT1526 using Tapatalk

I guess you should flash stock firmware, btw tab 4 variants are SM-T230nu nit gt-t230nu ;D this error might happen when you wipe /system and attempt reboot without flashing other system (on other device thread some one had same problem)

DUHAsianSKILLZ said:
@DeLime well, you might have messed up the partitions. If you can still boot into download mode, in my opinion, I believe you should flash an service firmware that has the PIT file (re partitions and format things accordingly since TWRP in your case can't repair).
Click to expand...
Click to collapse
No possibility to return to Download mode, when I boot I only get a black screen with written "Power Upload Reasonower Key" and below that "H/W Revision : 0.3"
Home+Power+Volume down doesn't take me to download mode and neither does Recovery Mode. This is strange because when the problem first occurred I could still return to Download mode, but the next day I couldn't anymore.
Use this tool to download your firmware and be sure to tick the binary nature box. http://forum.xda-developers.com/show...php?p=57842725 Once the firmware is downloaded and decrypted, you will need an program called Odin. There are a few posted on xda. Simply open the Odin 3.09 etc, and place the tar.md5 firmware in the appropriate sections in odin. The 4 firmware files should have similar names like Odin (PDA, CSC etc).
Click to expand...
Click to collapse
This doesn't work since I can' download the Phone Info SAMSUNG app that is supposed to give me my tab's region (My tablet being bricked and all).
I have tried using several region names in SAM FIRM such as "Europe" ,"USA", "North America", "Canada" and "AUT" but to succes, SamFirn keeps telling me;
"Could not fetch info for SM-T230NU/(Region Name here)"
Finally, I tried finding other Stock Rom's on other host site but they are all a single .tar.md5 files, none have PIT or CSC files
Thanks again for your advice, I'm sorry it doesn't work and unfortunately I'm still pretty stuck!

DeLime said:
No possibility to return to Download mode, when I boot I only get a black screen with written "Power Upload Reasonower Key" and below that "H/W Revision : 0.3"
Home+Power+Volume down doesn't take me to download mode and neither does Recovery Mode. This is strange because when the problem first occurred I could still return to Download mode, but the next day I couldn't anymore.
This doesn't work since I can' download the Phone Info SAMSUNG app that is supposed to give me my tab's region (My tablet being bricked and all).
I have tried using several region names in SAM FIRM such as "Europe" ,"USA", "North America", "Canada" and "AUT" but to succes, SamFirn keeps telling me;
"Could not fetch info for SM-T230NU/(Region Name here)"
Finally, I tried finding other Stock Rom's on other host site but they are all a single .tar.md5 files, none have PIT or CSC files
Thanks again for your advice, I'm sorry it doesn't work and unfortunately I'm still pretty stuck!
Click to expand...
Click to collapse
So you cant boot into ANY mode that makes sense? Hmm never seen this before

I let the tablet de-charge completeley in hopes that I could re-access the download mode but no luck, still receive the same black screen "Power Upload Reasonower Key" and below that "H/W Revision : 0.3".
So now I'm really thinking of going shopping for a new tablet, if anyone has an idea I'm willing to try it out, I think this tab is doomed anyways

DeLime said:
I let the tablet de-charge completeley in hopes that I could re-access the download mode but no luck, still receive the same black screen "Power Upload Reasonower Key" and below that "H/W Revision : 0.3".
So now I'm really thinking of going shopping for a new tablet, if anyone has an idea I'm willing to try it out, I think this tab is doomed anyways
Click to expand...
Click to collapse
If you cant get in download mode i think you should buy a new tab (do favor to yourself: dont buy samsung, they never give updates)

I had exactly the same problem (black screen "Power Upload Reasonower Key" and below that "H/W Revision : 0.3"), due exactly to the same reasons (following the advice
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8
, in order to sort out "Unable to mount" ), with exactly the same device (SM-T230NU), and yesterday I could sort it out, with some luck. It's working perfectly now.
I'm not an expert at all, not even close. I just tried to do some research and I got some luck. Given the status of your device, I'd say you do not have much to lose if you give a try to this.
What I did:
1. I stopped trying for a while, perhaps a couple of hours with the device power turned off ( I don't know whether this is important or not; it's just what I did)
2. After this while, I connected my tablet to my PC via USB (by the way, I have android SDK installed in my PC, in order to be able to use adb), tried to turn on the tablet in recovery mode (TWRP, the same you have), and surprisingly recovery mode appeared.
3. I made sure not to lose this connection: I didn't know if I would ever be able to get in recovery mode again.
4. I pulled out (with adb) recovery.log to PC. After many lines in that document, I found a section beginning with "Partition Logs:" which clearly describes which "mmcblk" to which partition. For instance, mmcblk0p9 belongs to recovery
Code:
[COLOR="Red"]/recovery | /dev/block/mmcblk0p9 |[/COLOR] Size: 16MB
Flags: IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p9
Display_Name: Recovery
Storage_Name: recovery
Backup_Path: /recovery
Backup_Name: recovery
Backup_Display_Name: Recovery
Storage_Path: /recovery
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
With reference to 'cache' (mmcblk0p14) and 'data' (mmcblk0p16) partitions, I noticed that size, used space, free space available and backup size was zero for both of them:
Code:
[COLOR="Red"]/cache | /dev/block/mmcblk0p14 [/COLOR]| [COLOR="SeaGreen"][B][U]Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB[/U][/B][/COLOR]
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p14
Display_Name: Cache
Storage_Name: Cache
Backup_Path: /cache
Backup_Name: cache
Backup_Display_Name: Cache
Storage_Path: /cache
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
and
Code:
[COLOR="red"]/data | /dev/block/mmcblk0p16[/COLOR] | [COLOR="seagreen"][B][U]Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB[/U][/B][/COLOR]
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
Symlink_Path: /data/media
Symlink_Mount_Point: /sdcard
Primary_Block_Device: /dev/block/mmcblk0p16
Display_Name: Data
Storage_Name: Internal Storage
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /data/media
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
MTP_Storage_ID: 65537
I realized this should the a good reason for:
Code:
I:Can't probe device /dev/block/mmcblk0p16
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p16', current file system: 'ext4'
Code:
I:Can't probe device /dev/block/mmcblk0p14
Failed to mount '/cache' (Invalid argument)
I:Actual block device: '/dev/block/mmcblk0p14', current file system: 'ext4'
5. Therefore, I applied the
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8
advice to these other blocks, with
Code:
adb shell
mke2fs -T ext4 /dev/block/mmcblk0p14
mke2fs -T ext4 /dev/block/mmcblk0p16
6. In view that both operations were successful, I dared to reboot to recovery. Once TWRP was reloaded (luckily!) I took a look at the recovery script (pressed the icon placed at the bottom right side in TWRP) to discover that there was no 'Unable to mount' issues, except for 'sdcard'. I understood that there was no need to mount, for the recovery would probably have done it for me. It was time for trying bootloader mode and flashing stock firmware via Odin.
7. And it worked! The only remaining odd symptoms are that it takes a couple of minutes for the screen to get active and the "Samsung melody" only sounds partially (big issue, ha?)
I hope this is useful for you although you posted your trouble a few months ago; this happened to me just last weekend.

If you can get into recovery.
I had tried flashing firmware and then flashed twrp.
Inside twrp I selected wipe and then format data. It fixed the problem with failure to mount /data.

you dirty, dirty gravedigger you
inspectergadget said:
If you can get into recovery.
I had tried flashing firmware and then flashed twrp.
Inside twrp I selected wipe and then format data. It fixed the problem with failure to mount /data.
Click to expand...
Click to collapse
Since ya dug up that grave, Imma pipe up with a request to the OP for some closure on this one.

thelous said:
So you cant boot into ANY mode that makes sense? Hmm never seen this before
Click to expand...
Click to collapse
I have this same issue with my Samsung, after I had attempted my build of cm 10.1 for this device. But, I can go to download mode, system, and recovery.
---------- Post added at 11:05 AM ---------- Previous post was at 10:58 AM ----------
thelous said:
If you cant get in download mode i think you should buy a new tab (do favor to yourself: dont buy samsung, they never give updates)
Click to expand...
Click to collapse
Same, had same issue on my tab, but cm 10.1 broke it. system, recovery, and download mode works fine. I gave up, so I had bought my neighbors galaxy tab 2 7.0 wifi (espressowifi) and installed cm 13.1 on it, works like a charm.

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

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

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

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