Develop Bugs

[Q] Flash rom with adb (no sdcard)

I googled the question quite extensively but have found no conclusive answers
Is there a way to flash a rom without first transferring it to the SD card (specifically for DHD)? There seems to be something wrong with my SD bay as my phone cannot mount the SD card successfully (it works fine on my computer), so I'm looking for a way to flash a new rom on the phone to rule out the possibility that the ROM is what's causing the SD card failures.
Google turned up a couple of results that seemed promising, but they all say you have to use Amon_RA recovery, which (to my knowledge) does not exist for DHD, and following the same steps while using CWM recovery leads to an error.
Unfortunately, as a new user I can't post the link to the method. It basically involves pushing the rom to /data/ on the phone then executing the command
recovery --update_package=DATA:ROM.zip
this should flash the rom. But because I'm using CWM there is an error, because CWM doesn't allow you to flash that way (or something to that effect)
Currently running IceColdSandwich 3.0.test4
Is there any way I can flash a rom without needing the SD card?? I don't wanna have to buy a new SD bay :/

Maybe this helped .. googled some more
http://forum.xda-developers.com/showthread.php?t=625950

Mount /sdcard
Just like you mounted /data try to mount sdcard using this adb comments,
./adb shell
su
# mount -o rw,remount rootfs /
# chmod 777 /mnt/sdcard
and push your ROM form computer, i.e ("adb push d:\adb directory\Your ROM /sdcard")
and try to mount sdcard in CWM....
I hope this would work for you,
NOT TESTED BY ME !! Pl replay

[d2tmo][CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Now: one common recovery for all: d2lte
The below specific variants are no more updated, use d2lte common variant
SGH-T999 (d2tmo)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse

Reporting issues:
1- Keep in mind I do not own the device: be precise in your description providing step by step details and screen log output
2- Provide a log: Advanced / Report Error, then attach the philz_recovery.log here
exfat is enabled: report if working or not
Let me know about any issue so that we can debug it + LOGS

Downloading now, will flash in a second or two and report back.

mt3g said:
Downloading now, will flash in a second or two and report back.
Click to expand...
Click to collapse
Will be waiting for first feedbacks, first bugs, or a first perfect (would be rare, even if I am getting a bit used now to Qualcomm devices)

Flashes fine and looks great.
The time is off by 7 hours for me looked in settings for creating a time zone slot, with no success. The screenshot feature is dope but didn't work, gave me tears and not visible screens. Will flash a kernel in a second to test that much out. Will flash a ROM and create a backup later to test more thorough. The screen is what I got from swipe to left for screenshot in recovery.
EDIT: Kernel falshed fine. so all in all no real issues to report as it works as a recovery should, all but testing nandroid and restoring.
T-Mobile SGS III

mt3g said:
Flashes fine and looks great.
The time is off by 7 hours for me looked in settings for creating a time zone slot, with no success. The screenshot feature is dope but didn't work, gave me tears and not visible screens. Will flash a kernel in a second to test that much out. Will flash a ROM and create a backup later to test more thorough. The screen is what I got from swipe to left for screenshot in recovery.
EDIT: Kernel falshed fine. so all in all no real issues to report as it works as a recovery should, all but testing nandroid and restoring.
T-Mobile SGS III
Click to expand...
Click to collapse
Thank you for the positiv eearly report
fb2png for screenshots doesn't support most new boards. Hopefully it will be fixed later
Time is GMT by default. Time zone can be set under GUI settings, it should work. If not, provide a log

Phil3759 said:
Thank you for the positiv eearly report
fb2png for screenshots doesn't support most new boards. Hopefully it will be fixed later
Time is GMT by default. Time zone can be set under GUI settings, it should work. If not, provide a log
Click to expand...
Click to collapse
It sure was and time is correct now, I like the brightness settings also, lots of goodies in there. I'll report back later tonight if no one else does on nandroid and such.

ill try it out im using twrp recovery so itll be fun to try something new lol
omg! its touch enabled
and i like the color at first the layout is a win for me so far and ui is to
great job
clock is working changed to my time zone with daylight savings time fine
omg just found out i can you my home back and menu in it
im having fun playing with it im easy to entertain lol give me a break
ok new favorite recovery lol im hooked lol

I do not expect any issue with nandroid backups as it was largely debugged now on other devices
However:
- Mount USB storage works?
- exfat is ok?
- A last important point: when you boot into recovery, /system is mounted or unmounted? To see this, go into Mounts and Storage menu after you booted in recovery. /system should show (mount) and not (unmount)
I ask this to tune things if needed as this is completely repacked around stock ramdisk and kernel to enable exfat mainly

My stuff is fat32 so I can't help there... system is not mounted it shows mount/ system

Just booting into it and scrolling through some of the options was a treat within itself. Don't have much more to say (that hasn't been said already) but I'm glad we're able to have such a refined recovery. I'll let you know if I bump into any issues, as I tend to not stay in recovery mode for too long (when I actually have something to flash, etc. I'll test more). Thanks!
Sent from my SGH-T999 using Tapatalk 4 Beta

Phil3759 said:
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Click to expand...
Click to collapse
I was able to install it perfectly with Odin with the only difference from your installation instructions being that the phone rebooted into normal mode, so I just entered recovery mode via Rom Toolbox.
I am unable to access an external 64GB SDXC formatted as exFat. I tried to mount /external_sd and /sd-ext and neither one worked. I don't know if this is relevant but the normal mount point for the external SD card on the Galaxy S3 is /mnt/extSdCard.
The aroma file manager doesn't see the external card either.
Everything else seems to be working though I haven't tried to do a backup or a restore.
Thanks for your help...

Love the UI! Very easy to navigate. Everything seems to be running smoothly so far. Installed a few AOSP and TW ROMs successfully. Kernels I've tested are BMS, KT747, and LK. All were successful as well.
EDIT: Backup and restore options seem to work just fine. No issues with Mounts or storage I'm on a fat32 card so I can't test exfat unfortunately. Will let you know if anything comes up within the next day or 2.
Thank you very much for sharing this. It is pretty dope.

Thank you all
Will wait a bit more for reports about exfat
Some 64Gb cards always caused issues on some phones, mainly if they were not formatted as they should (primary partition and default block size)
Sent from my GT-I9100 using Tapatalk 2

I tried flashing the zip file but install keeps aborting?
Sent from my SAMSUNG-SGH-I747 using xda premium

Phil3759 said:
Thank you all
Will wait a bit more for reports about exfat
Some 64Gb cards always caused issues on some phones, mainly if they were not formatted as they should (primary partition and default block size)
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
When I had problems with the early exfat drivers from Samsung, I reformatted the card as Fat32 and ran with that for some time. After installing an update from Samsung/T-Mobile where the exFat issues were fixed I used the following procedure to convert the card to exFat:
1. Copied all data from the card to a PC via a card reader.
2. Deleted all partitions from the card using a partition manager on the pc
3. Installed the card into the phone and let the phone partition and reformat the card.
4. Copied all data from the PC back to the card via a card reader.
5. Re-installed the card into the phone.
It has been several months since I converted the card back to exFat and I have had no problems with app on the phone accessing the card. This include Nandroid Manager, Online Nandroid and Titanium Backup as well as all of the normal Android utilities.
The partition information is:
Partition Type: Primary
Psttition Type Id: 0x0C
File System: exFAT
Serial #: 0
First Physical Sector: 2048 (Cyl: 0, Hd:32, Sect: 33)
Last Physical Sector 124735487 (Cyl: 7764, Hd: 108, Sect: 24)
Total Physical Sectors: 124733440 (60905.0MB)
Physical Geometry: 7764 Cyls, 255 Hds, 64 Sects.
That's the best that I could do on short notice. I am trying to find a utility that will give me more information under Windows 7.
Thanks again and again...
Mike
P.S. If I can help with some testing or programming, please let me know. I'm fighting learning java but I am pretty good with C/C++ and assembler.

ChitownWingMan said:
When I had problems with the early exfat drivers from Samsung, I reformatted the card as Fat32 and ran with that for some time. After installing an update from Samsung/T-Mobile where the exFat issues were fixed I used the following procedure to convert the card to exFat:
1. Copied all data from the card to a PC via a card reader.
2. Deleted all partitions from the card using a partition manager on the pc
3. Installed the card into the phone and let the phone partition and reformat the card.
4. Copied all data from the PC back to the card via a card reader.
5. Re-installed the card into the phone.
It has been several months since I converted the card back to exFat and I have had no problems with app on the phone accessing the card. This include Nandroid Manager, Online Nandroid and Titanium Backup as well as all of the normal Android utilities.
The partition information is:
Partition Type: Primary
Psttition Type Id: 0x0C
File System: exFAT
Serial #: 0
First Physical Sector: 2048 (Cyl: 0, Hd:32, Sect: 33)
Last Physical Sector 124735487 (Cyl: 7764, Hd: 108, Sect: 24)
Total Physical Sectors: 124733440 (60905.0MB)
Physical Geometry: 7764 Cyls, 255 Hds, 64 Sects.
That's the best that I could do on short notice. I am trying to find a utility that will give me more information under Windows 7.
Thanks again and again...
Mike
P.S. If I can help with some testing or programming, please let me know. I'm fighting learning java but I am pretty good with C/C++ and assembler.
Click to expand...
Click to collapse
Sadly, without a recovery log or even better a dmsg log, I cannot help a lot
exfat drivers are from /system/lib, so the ones used by your ROM. They are not bundled with the recovery as that causes issues for some
can you try this in adb shell:
Code:
mount -t extfat /external_sd
Give the error message if it fails
If it fails, try this
Code:
mount /system
insmod -f -v /system/lib/modules/exfat_core.ko
insmod -f -v /system/lib/modules/exfat_fs.ko
mount -t extfat /external_sd
Give output of these command lines if they do fail

Phil3759 said:
Sadly, without a recovery log or even better a dmsg log, I cannot help a lot
exfat drivers are from /system/lib, so the ones used by your ROM. They are not bundled with the recovery as that causes issues for some
can you try this in adb shell:
Code:
mount -t extfat /external_sd
Give the error message if it fails
If it fails, try this
Code:
mount /system
insmod -f -v /system/lib/modules/exfat_core.ko
insmod -f -v /system/lib/modules/exfat_fs.ko
mount -t extfat /external_sd
Give output of these command lines if they do fail
Click to expand...
Click to collapse
Manual mount:
~ # mount -t extfat /external_sd
mount -t extfat /external_sd
mount: mounting /dev/block/mmcblk1p1 on /external_sd failed: Invalid argument
The mount was successful after the insmod commands. I was also able to cd to /external_sd and do an "ls -l".
Can I modify a script to include the insmod's or do you have to do it?
Thanks again...

ChitownWingMan said:
Manual mount:
~ # mount -t extfat /external_sd
mount -t extfat /external_sd
mount: mounting /dev/block/mmcblk1p1 on /external_sd failed: Invalid argument
The mount was successful after the insmod commands. I was also able to cd to /external_sd and do an "ls -l".
Can I modify a script to include the insmod's or do you have to do it?
Thanks again...
Click to expand...
Click to collapse
Ok, we're on the way to fix it
Can you try this now, in adb shell, after a recovery reboot please
Code:
mount /system
insmod /system/lib/modules/exfat_core.ko
insmod /system/lib/modules/exfat_fs.ko
mount -t extfat /external_sd
That way I can limit the potential causes. It is same as above without insmod options in command

Phil3759 said:
Ok, we're on the way to fix it
Can you try this now, in adb shell, after a recovery reboot please
Code:
mount /system
insmod /system/lib/modules/exfat_core.ko
insmod /system/lib/modules/exfat_fs.ko
mount -t extfat /external_sd
That way I can limit the potential causes
Click to expand...
Click to collapse
Before I tried what you asked I rebooted into recovery. In other words, I ran the adb shell commands while the phone was in your recovery program. Is that what you mean?

[Q] SD Card Ext Mount issues - INTERESTING clue but need help.

Dear enthusiastic helpful geeks
I have an interesting challenge for all those who are interested.
I am android fan, amateur and a doctor by profession.
I have 3 years old HTC Desire Bravo GSM
I rooted using Unrevoked 2 years ago and used CyanogenMod.
I have been using S2EXT app all these years to solve the well known internal memory problem.
I found Jelly Bean very interesting and flashed the VJ 4.2.2 CM10.1 V6.3
I just love it.
With terminal emulator, I used the commands as instructed and had this message.
$ su
# a2sd install
Found block device: /dev/block/mmcblk0p2
Removing flag a2sd
Removing flag ad2sd
Removing flag dc2sd
setting flag a2sd
/system/bin/a2sd: line 73: /sd-ext/.a2sd: Read-only file system
chmod: /sd-ext/.a2sd: No such file or directory
Would you also like to move DALVIK-CACHE?
You can later undo this with 'nocachesd' (y|n)
I came to know SD EXT is not mounted
Tried mounting sdext through ROM manager and got the message
E:Can't mount /dev/block/mmcblk0p2
(File exists)
I flashed back CM 7 reluctantly
SD ext did not mount at first.
I downloaded S2EXT and I had to tick the box which said Mount as ext4 (mount sd-ext as ext4 without journaling)
Now, the disabled options got enabled and I could ask for the movement of applications, dalvik cache and rest of the stuff to sd ext.
I have the log generated by S2EXT app about what happened.
Initialization...
Ext partition found: /dev/block/mmcblk0p2
Use built-in tune2fs
Use built-in e2fsck
Setup read_ahead value
Start mounting /dev/block/mmcblk0p2 as ext4
Setup options to /dev/block/mmcblk0p2:
tune2fs 1.41.12 (17-May-2010)
Checking /dev/block/mmcblk0p2:
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/mmcblk0p2: 839/262144 files (3.5% non-contiguous), 196501/1048576 blocks
Disabling journaling on /dev/block/mmcblk0p2:
tune2fs 1.41.12 (17-May-2010)
tune2fs 1.41.12 (17-May-2010)
Mounting /dev/block/mmcblk0p2...
/dev/block/mmcblk0p2 successfully mounted!
Config found on /data/data
Status dir not found! Create...
Config now on /data/data
Unmount /cache/download...
/sd-ext/download mount as /cache/download
Phone details
BRAVO PVT3 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
RADIO-5.11.05.14
Aug 10 2010,17:52:18
Unrevoked to root
Main and returned to CyanogenMod 7.2.0.1
ROM Manager
Clockworkmod revovery
S2EXT
GParted partitioning SD Card
1. Primary ~14GB FAT32
2. Primary ~1GB ext4
I want to use CM10.1 VJ version 6.3 and to be able to mount SD Ext and move apps to it so that my internal memory does not get full.
S2EXT can fix this issue but is not compatible with JellyBean. - How could it do? Can I do it somehow?
Why is that mounting SD Ext and moving apps is not possible on VJ version?
I am not so confident in using adb shell and other advanced stuff as advised in the forum.
Hence, writing all I know to see if someone can spot a solution and help me solve it in a simpler way.
Help me enjoy the Jelly Bean and make my Desire Re-Live !
[/FONT][/SIZE][/SIZE][/FONT][/FONT][/SIZE][/SIZE][/FONT][/FONT]

I suspect ROM manager may have caused a problem, it's a known issue that that app is bad for Desire. Mounting the ext-ext may have screwed it up somewhere.
Uninstall it.
I would backup the FAT32 bit of the sd card to PC, delete all partitions and repartition using gparted again, just in case. You can go for 1.5-2GB if you really don't want to run out of space.
Then reflash the rom, follow the instructions to use A2SD, don't bother with S2E anymore.
Up to you, I would also consider going s-off as well, it's a lot more advantageous. You can then do things such as change hboot for smaller ROMs and have even more space for apps. You could also install 4EXT recovery (see my sig), and do the partitioning using that recovery too.

Thanks a lot
Thanks Eddiehk6 for your wonderful advice.
ROM manager - I can uninstall it.
I tried S-Off using Revolutionary but it somehow did not let me pass with the Beta key (invalid key)
I will try again.
Advice on SD ext size is useful. I shall do it.
S2E does not work with Jelly Bean anyway
I shall try 4ext recovery.
Thanks once again.
I will update this for future reference of someone like me
gagbel

gagbel said:
ROM manager - I can uninstall it.
I tried S-Off using Revolutionary but it somehow did not let me pass with the Beta key (invalid key)
I will try again.
Click to expand...
Click to collapse
Yes, uninstall ROM manager. It's not all bad, just very bad with this phone, you don't need it.
As for the BETA key, just make sure you type it exactly, or copy / paste (but make sure you don't copy any leading or trailing spaces). Most likely you confused an i or 1 or L or O or 0 somewhere.

Update
Dear Eddiehk6
Thanks for the response.
I successfully S-OFF
You were right I mistook 1 l and I characters while using Revolutionary beta key. Also, I was wrong in putting IMEI number instead of the Serial number. Funny enough SN comes in the black window of Revolutionary.
I also installed 4EXT recovery as I became S-OFF.
Partitioned as per the tutorial in this forum.
Flashed CM10.1 VJ version as per the instructions.
A2SD Termminal emulator again had problems with mounting of SD EXT !
I used Mount2SD
Init.d script was not installed - when I installed it, moved the apps, they disappeared. I could not find the Play services also !
Memory was still consumed. Apps were there but not seen.
I finally gave up at early hours of the morning and went back to CM7 reluctantly.
The log from S2E has a clue. I just don't know how to use that clue.
Have a look above at the orange log of S2E if you can and see if you understand please.
My search tells me that I should have some adb shell knowledge to solve it and I don't !
I am ok with old ROM. Help me if you can to make my Desire live longer.
gagbel

gagbel said:
Dear Eddiehk6
Thanks for the response.
I successfully S-OFF
You were right I mistook 1 l and I characters while using Revolutionary beta key. Also, I was wrong in putting IMEI number instead of the Serial number. Funny enough SN comes in the black window of Revolutionary.
I also installed 4EXT recovery as I became S-OFF.
Partitioned as per the tutorial in this forum.
Flashed CM10.1 VJ version as per the instructions.
A2SD Termminal emulator again had problems with mounting of SD EXT !
I used Mount2SD
Init.d script was not installed - when I installed it, moved the apps, they disappeared. I could not find the Play services also !
Memory was still consumed. Apps were there but not seen.
I finally gave up at early hours of the morning and went back to CM7 reluctantly.
The log from S2E has a clue. I just don't know how to use that clue.
Have a look above at the orange log of S2E if you can and see if you understand please.
My search tells me that I should have some adb shell knowledge to solve it and I don't !
Click to expand...
Click to collapse
At least you're s-off now which is good
So how did you partition your sd card? I know you have 4EXT and it's easy to partition with that, but I would personally stick to gparted in this instance as you need to start from scratch, also you've used it before anyway?
Make sure you backup the sd card, then delete all partitions first (don't resize). Then make one FAT32 partition, and one (~1.5GB) ext4 partition, no swap.
Within 4EXT recovery there should be an option to check the partitions are aligned, do this (they should be if properly done in gparted, but worth a check)
Full wipe again, reflash rom just to be sure.
Try getting the terminal emulator commands working first, follow all instructions exactly. Don't use another app or script for now, start clean and get it working.
If you still get the error, /dev/block/mmcblk0p2 error, I think this may be related to a usb brick, not absolutely sure, there is 'USB unbrick' option within 4EXT as well, try that.
I am ok with old ROM. Help me if you can to make my Desire live longer.
gagbel
Click to expand...
Click to collapse
CM7 is still fine, just because it's 'old' doesn't make it bad, the Desire can still live long. Now that you're s-off you can even change hboot with that ROM and get more internal memory if you like, even more space for apps
I'm still on a GB ROM myself nothing wrong with it. Stable, battery is fine for me. Regardless you should still be able to get A2SD working.

Update
Thanks Eddiehk6
I would try all that you told me.
I had used 4ext recovery as I was exited with the S-OFF and Change of recovery status of my phone.
I would try and do clean start again and see.
The link I was mentioning which involves adb shell knowledge is the message #4 in this link http://forum.xda-developers.com/showthread.php?t=848967
recurrent theme is e2fsck. I don't know how to use these codes: Terminal emulator / adb shell ? But I would try your method as I can do them.
I would also check alignment through the recovery.
Mildwild download link is broken. I would try for JB first and then if no luck, I would try GB. Its just that in my nexus7, I am used to JB.
CM7 is most stable I have seen ( i have used only one ROM so far I am quite happy with it too.
Thanks for all the support.
gagbel

Another useful link
Another useful link which I don't know how to use as I don't have adb shell knowledge.
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/#entry56396

Solved
Problem was with mounting ext 4 of my card
S2e could mount it
But s2e was not compatible with 10.1 of cyanogenmod
Hence I put 10 version
Used s2e to mount
It did not move apps
Used terminal emulator as per instructions by vj
All worked thanks all of you
Sent from my HTC Desire using xda app-developers app

[q&a] [recovery][desire hd] twrp 2.8.1.0 && cwm 6.0.5.1 - unofficial

Q&A for [RECOVERY][DESIRE HD] TWRP 2.8.1.0 && CWM 6.0.5.1 - UNOFFICIAL
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 [RECOVERY][DESIRE HD] TWRP 2.8.1.0 && CWM 6.0.5.1 - UNOFFICIAL. 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!

TWRP 2.8.1.0
I have a problem to make sd-ext partition with TWRP 2.8.1.0 partition editor. Same problem was with version 2.7.1.0.
E. Unable to locate sd-ext partition.
Partitioning SD Card...
umount: can't umount : No such file or directory
I:umount "$SWAPPATH" process ended with ERROR=1
I:sd card block device is '/dev/block/mmcblk1', sdcard size is: 7958MB, fat size: 5910MB, ext size: 2048MB, ext system: 'ext4', swap size: 0MB
Removing partition table...
I:Command is: 'parted -s /dev/block/mmcblk1 mklabel msdos'
Iarted -s /dev/block/mmcblk1 mklabel msdos process ended with RC=0
Creating FAT32 partition...
I:Command is: 'parted /dev/block/mmcblk1 mkpartfs primary fat32 0 5910MB'
Information: You may need to update /etc/fstab.
Iarted /dev/block/mmcblk1 mkpartfs primary fat32 0 5910MB process ended with RC=0
Creating EXT partition...
I:Command is: 'parted /dev/block/mmcblk1 mkpartfs primary ext2 5910MB 7958MB'
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0
Information: You may need to update /etc/fstab.
Iarted /dev/block/mmcblk1 mkpartfs primary ext2 5910MB 7958MB process ended with RC=0
mount: mounting /sdcard/.android_secure on /and-sec failed: No such file or directory
I:mount '/sdcard/.android_secure' '/and-sec' process ended with ERROR=255
E:Unable to locate sd-ext partition.
Click to expand...
Click to collapse

marek287 said:
I have a problem to make sd-ext partition with TWRP 2.8.1.0 partition editor. Same problem was with version 2.7.1.0.
E. Unable to locate sd-ext partition.
Click to expand...
Click to collapse
@jrior001 I guess /sd-ext just has to be added to twrp.fstab?

marek287 said:
I have a problem to make sd-ext partition with TWRP 2.8.1.0 partition editor. Same problem was with version 2.7.1.0.
E. Unable to locate sd-ext partition.
Click to expand...
Click to collapse
Is this a feature you've used on ace previously? I can't see where it was ever implemented for ace in the past and the devices trees as I see them are not built to support sd-ext, frankly I'm not familiar with it at all.
It its something we should have or other ace recoveries have had I'll look into it but I don't want to waste time reinventing something ace never had.

jrior001 said:
Is this a feature you've used on ace previously? I can't see where it was ever implemented for ace in the past and the devices trees as I see them are not built to support sd-ext, frankly I'm not familiar with it at all.
It its something we should have or other ace recoveries have had I'll look into it but I don't want to waste time reinventing something ace never had.
Click to expand...
Click to collapse
This is feature that I have use with 4ext recovery. I make sd-ext partion (2048MB) to apps and link all apps with Link2SD. If I install twrp recovery, it even don't show sd-ext partition. It show only about 5.6 GB size partition. I can't repartition it to full size (8GB) with twrp. Only way is to install 4ext recovey to delete all partions or make new partitions because even coputer don't show this sd-ext partition after using twep partition maker.

marek287 said:
This is feature that I have use with 4ext recovery. I make sd-ext partion (2048MB) to apps and link all apps with Link2SD. If I install twrp recovery, it even don't show sd-ext partition. It show only about 5.6 GB size partition. I can't repartition it to full size (8GB) with twrp. Only way is to install 4ext recovey to delete all partions or make new partitions because even coputer don't show this sd-ext partition after using twep partition maker.
Click to expand...
Click to collapse
I've got the partitioning working but once I reboot I'm not seeing that new sd-ext partition anywhere. Looks like cm doesn't support it either? What ROM are you running?

jrior001 said:
I've got the partitioning working but once I reboot I'm not seeing that new sd-ext partition anywhere. Looks like cm doesn't support it either? What ROM are you running?
Click to expand...
Click to collapse
No it must work with CM. Try 4ext recovery to make partitions.
I am long Mustaavalkosta [UNOFFICIAL] CyanogenMod 11 Nightlies / Releases user.

marek287 said:
No it must work with CM. Try 4ext recovery to make partitions.
I am long Mustaavalkosta [UNOFFICIAL] CyanogenMod 11 Nightlies / Releases user.
Click to expand...
Click to collapse
I got it figured out. The app is creating an init.d script to mount the new partition for you. I'm going to test a few things and see if I can't get sd-ext supported natively in @Mustaavalkosta builds.
In the meantime test this one for me please
https://www.dropbox.com/s/978yvck90ysunw7/twrpACE_SDEXTTEST_recovery.img?dl=0

jrior001 said:
I got it figured out. The app is creating an init.d script to mount the new partition for you. I'm going to test a few things and see if I can't get sd-ext supported natively in @Mustaavalkosta builds.
In the meantime test this one for me please
https://www.dropbox.com/s/978yvck90ysunw7/twrpACE_SDEXTTEST_recovery.img?dl=0
Click to expand...
Click to collapse
It gives no errors but I can't see sd-ext partition in my computer (Ubuntu). Mounting SD card and SD-ext shows only SD card.
Link2SD app link apps to SD-ext and it shows it in storage info but mounting SD-ext is not working.

marek287 said:
It gives no errors but I can't see sd-ext partition in my computer (Ubuntu). Mounting SD card and SD-ext shows only SD card.
Link2SD app link apps to SD-ext and it shows it in storage info but mounting SD-ext is not working.
Click to expand...
Click to collapse
I've got a commit waiting for mustavaa's approval to add a folder at /sd-ext to mount that partition too. Also with my last test build of twrp its making the partitions fine. You may need to have your link2sd app redo the mount scripts. Its the first option in the menu after letting twrp create your partitions.

TWRP 2.8.1.2 & HTC Desire HD (PD98100)
Question about TWRP 2.8.1.2 and HTC Desire HD, how to get touch screen work? I have tested couple of versions without luck. Is there any other recovery tool without touchscreen UI? I would like to test CyanogenMod 12. Thanks!
Edit: HW/ user fault, touch screen works just fine now.

Hey jrior. Do u know how to make ace work with art? Something to do with changing /cache to 300 or more? Thanks

Jykke76 said:
Question about TWRP 2.8.1.2 and HTC Desire HD, how to get touch screen work? I have tested couple of versions without luck. Is there any other recovery tool without touchscreen UI? I would like to test CyanogenMod 12. Thanks!
Click to expand...
Click to collapse
First I've heard if any touch issues, this has been well tested on both desire HD and inspire 4g. Get me recovery logs and kmsg from recovery boot and I'll take a look.
marknoll said:
Hey jrior. Do u know how to make ace work with art? Something to do with changing /cache to 300 or more? Thanks
Click to expand...
Click to collapse
Art is default on LP...not sure what your talking about

Art on cm 11

marknoll said:
Art on cm 11
Click to expand...
Click to collapse
In not inclined to spend time on cm11 at all, but in my experience on other devices at worked OK on cm11. I'm assuming you tried to convert and it failed? If so did you have xposed installed? I know that breaks art

Yes. I tried and failed. Its in a boot loop. I read somewhere to open terminal emulator and input df to see specs. If /cache is less than 300, it won't convert. I even tried partitioning the SD and no success.
---------- Post added at 05:44 PM ---------- Previous post was at 05:43 PM ----------
Yes. I had xposed installed. But I did a fresh clean install, and it still bootloops

marknoll said:
Yes. I tried and failed. Its in a boot loop. I read somewhere to open terminal emulator and input df to see specs. If /cache is less than 300, it won't convert. I even tried partitioning the SD and no success.
---------- Post added at 05:44 PM ---------- Previous post was at 05:43 PM ----------
Yes. I had xposed installed. But I did a fresh clean install, and it still bootloops
Click to expand...
Click to collapse
Cache partition is to small for the conversion I guess...nothing I can do about that.

I was told that I had to downgrade the boot loader from 2.0 to .85. Lol

Can I flash twrp? I'm on cwm currently
Sent from my C2305 using XDA Free mobile app

bahunrobotm said:
Can I flash twrp? I'm on cwm currently
Sent from my C2305 using XDA Free mobile app
Click to expand...
Click to collapse
Thatsba good idea if you want to flash the newer cm12 builds, twrp is the only thing that works with the newer builds

Xperia M TWRP İnternal Storage 0 MB Problem!

Hello to everyone. I am using Xperia M and can not mount data, system mount via TWRP Recovery. I also can not load the stock version and kernel with Flashtool. The device goes into recovery mode, is charged and is recognized as a nickname when connected to a PC. I will be glad if you help me.

didyou said:
Hello to everyone. I am using Xperia M and can not mount data, system mount via TWRP Recovery. I also can not load the stock version and kernel with Flashtool. The device goes into recovery mode, is charged and is recognized as a nickname when connected to a PC. I will be glad if you help me.
Click to expand...
Click to collapse
Your device got ebola. There is no solution. Sorry mate.

Use internal storage 0 mb problem in TWRP Recovery. No flashing kernel and roms.

didyou said:
Hello to everyone. I am using Xperia M and can not mount data, system mount via TWRP Recovery. I also can not load the stock version and kernel with Flashtool. The device goes into recovery mode, is charged and is recognized as a nickname when connected to a PC. I will be glad if you help me.
Click to expand...
Click to collapse
i am having same problem . but my internal storage is mounted as android os and my actual storage is not visible please help me.

fix for 0MB internal storage problem
Your device is still recoverable if you can boot into twrp successfully
Go to advanced --> terminal
Check your partition table with
fdisk -l /dev/block/mmcblk0
it will print out the partition table, last 3 should be system, cache and data
format system with ext4, for me that was /dev/mmcblk0p25 - YOURS MAY DIFFER
make_ext4fs /dev/block/mmcblk0p25
format data with ext4, for me that was /dev/mmcblk0p27
make_ext4fs /dev/block/mmcblk0p27
For me, this was met with errors, so format it with exfat first, mkfs.exfat /dev/mmcblk0p27, reboot into recovery, then format with make_ext4fs.
You cannot do this through advanced wipe, because twrp tries to guess your partitions AFTER mounting them, then reads /system is mounted on /dev/block/mmdblk0p25, but it's not mounted, so no repairing/formatting through that. Use the terminal instead, then reboot, twrp will find the partitions then.
afterwards reboot again into recovery. I didn't have to reformat cache, but you may have to. try mkfs.ext2 on that. You will always want to go with make_ext4fs though.
internal storage should show up again now, wiping and installing zips will work again.

rak-zero said:
Your device is still recoverable if you can boot into twrp successfully
Go to advanced --> terminal
Check your partition table with
fdisk -l /dev/block/mmcblk0
it will print out the partition table, last 3 should be system, cache and data
format system with ext4, for me that was /dev/mmcblk0p25 - YOURS MAY DIFFER
make_ext4fs /dev/block/mmcblk0p25
format data with ext4, for me that was /dev/mmcblk0p27
make_ext4fs /dev/block/mmcblk0p27
For me, this was met with errors, so format it with exfat first, mkfs.exfat /dev/mmcblk0p27, reboot into recovery, then format with make_ext4fs.
You cannot do this through advanced wipe, because twrp tries to guess your partitions AFTER mounting them, then reads /system is mounted on /dev/block/mmdblk0p25, but it's not mounted, so no repairing/formatting through that. Use the terminal instead, then reboot, twrp will find the partitions then.
afterwards reboot again into recovery. I didn't have to reformat cache, but you may have to. try mkfs.ext2 on that. You will always want to go with make_ext4fs though.
internal storage should show up again now, wiping and installing zips will work again.
Click to expand...
Click to collapse
Thank you for your message I just saw. I tried, but I still see the internal memory of 0MB when I try to Wipe.
https://imgyukle.com/i/Rk24Gt
https://imgyukle.com/i/Rk264c
https://imgyukle.com/i/Rk2fyR

didyou said:
Thank you for your message I just saw. I tried, but I still see the internal memory of 0MB when I try to Wipe.
Did you reboot after? You can try the advanced format in twrp, maybe you need to use exfat for your partition 27 (data) or ext3 not ext4 for system. Try some combinations.
Which twrp version is installed?
I checked mine and partitions 25 to 27 are formatted with ext4. I have latest twrp 3.0.2.0 and use lineage 14.1. from here.
Partition table looks fine, same sizes as me.
Click to expand...
Click to collapse

rak-zero said:
didyou said:
Thank you for your message I just saw. I tried, but I still see the internal memory of 0MB when I try to Wipe.
Did you reboot after? You can try the advanced format in twrp, maybe you need to use exfat for your partition 27 (data) or ext3 not ext4 for system. Try some combinations.
Which twrp version is installed?
I checked mine and partitions 25 to 27 are formatted with ext4. I have latest twrp 3.0.2.0 and use lineage 14.1. from here.
Partition table looks fine, same sizes as me.
Click to expand...
Click to collapse
I am using TWRP version 3.1.1.0. I tried to make Wipe after it restarted after operations but it still seems to be 0MB. I tried to change the file system, but not through the terminal.
Click to expand...
Click to collapse