hello DEVELOPERS !
SO I need help with: -Format-signed.zip folder- when you flash it from recovery on Nexus One is DELETE everything (format /data /system /cache and /sd-ext) INSTEAD WIPE, unfortunately this FORMAT.zip doesn't working with Nexus S
Can some one rebuild this ? so it's gonna work for us?
YOU CAN SAY: I can go into CWR and select Mounts and manually format /data /system /cache and /sd-ext
TRY TO FORMAT and restart the phone....u phone gonna boot...+(sd-ext always gives error when u wipe, or format it)
after "my" format you phone gonna stack on boot loader....because it's nothing there !
Hi all,
as I have not yet enough thraeds I can't post in the Development section. As the new SAGA LBC MOD V.0.6 is on the way (I am using 0.5.4) I would like to know how my partitions should be formatted using this mod?
Should everything be EXT4 or EXT3 or even a mixture as I have today.
I have flashed the recovery and I am now on 4EXTRecovery v2.1.0 which shows following FileSystems
system ext4
data ext3
cache ext3
sdcard fat32
When SAGA LBC MOD v0.6 is out I want to start from scratch with a perfect configured device.
Please advice what I should do.
THX
LBC Mod fully supports ext4, there is no reason to use ext3 for any partition as ext4 offers some performance increase. SD stays fat32 of course, there is no need for sd-ext on our phone.
Thanks for your quick answer.
I will then partition my Filesystem to EXT4.
Thank you.
masterl1983 said:
Hi all,
as I have not yet enough thraeds I can't post in the Development section. As the new SAGA LBC MOD V.0.6 is on the way (I am using 0.5.4) I would like to know how my partitions should be formatted using this mod?
Should everything be EXT4 or EXT3 or even a mixture as I have today.
I have flashed the recovery and I am now on 4EXTRecovery v2.1.0 which shows following FileSystems
system ext4
data ext3
cache ext3
sdcard fat32
When SAGA LBC MOD v0.6 is out I want to start from scratch with a perfect configured device.
Please advice what I should do.
THX
Click to expand...
Click to collapse
Don't worry about doing any specific partitioning, ensure that you're using the correct RECOVERY EXT4.
If you're not then download EXT4 Recovery if you don't already have it and use CWM to flash it.
There is an option in EXT4 recovery which will show you the type of all of your partitions and another option that will convert any EXT3 to EXT4 without data loss.
Although the LBC WIPE script that it is recommended that you run before you flash LBC v0.5.3 will pre format all of these partitions in the correct format (EXT4) before you flash the ROM!
I m using stock Rom and early flash ateeq kernel v3. also support int.d . when I m using increase memory script like m2sd, ungaze,a2sd my ext4 not mount on boot pls help about it
....
if you are on CMW switch to twrp or Yaano's recovery
Use TWRP 2.2.2.0 by oblikas, it works with ext4 fs. The Yannou's recovery mount sd-ext with ext4 fs, but when you make a backup it saves sd-ext as ext3 fs and when restore you don't have ext4 no more.
Anybody found some fixes for yannou's recovery?
And the new TWRP 2.3.3.0 doesn't see sd-ext with ext4 fs.
Anybody tried TWRP 2.3.3.0 with sd-ext and ext4 file system?
Hi Thanks for a very nice rom
I am tesing and if nay bug foud ill try to post if i am allowed ...
But i am unbale to enable int2Ext+ in my Phone.... i tried
Reflashing the ROM
Reflashing zip......
Could soen one expalin me setp by step...cuz the instructions at this page didnot work...
My cell phone is LG P500
Thankyou very much for your help.....
Unable to enable int2Ext+ (Fixed for JB 4.2.2)
Its becoming annoying as the memory is very low and i barely have a few apps but are needed 200mb internal memory is so low CronModINt2Ext+ fixed for 4.2.X did not work........ :crying:
Also if my recovery is an Issue
Also which recovery is stable enough and formats the sd-ext in ext4 ..... i am using CWM 5.0.2.6
My device is LG P500.......
Thanks
Personally I'm using AmonRA recovery (link in signature).
it formats ext2 and then you can "upgrade" it to ext3 and ext4.
installing the script is very simple:
1) mount /system, mount /data, mount /sd-ext.
2) install zip.
3) unmount /data, unmount /sd-ext.
4) format (wipe) sd-ext
5) reboot
uf0999 said:
Personally I'm using AmonRA recovery (link in signature).
it formats ext2 and then you can "upgrade" it to ext3 and ext4.
installing the script is very simple:
1) mount /system, mount /data, mount /sd-ext.
2) install zip.
3) unmount /data, unmount /sd-ext.
4) format (wipe) sd-ext
5) reboot
Click to expand...
Click to collapse
Nope it didnt work ... although my recovery is CWM 5.0.2.0
FInally Flashed a new recovery (Amon RA)....
Flashed a new Rom.... PAC ROM 20.0
And used the fiexd INT2EXT+.....
It Worked Thanks
I made a F2FS conversion to Data Partition.When I made a restore the Data Partition cannot be Mount or do a Format.With any recovery(CWM,TWRP,Philz) the Data partition Cannot be mounted or formated.What Can I do?I read threads on the Transformer Forum but nothing of these working for me :crying:
andreas1996 said:
I made a F2FS conversion to Data Partition.When I made a restore the Data Partition cannot be Mount or do a Format.With any recovery(CWM,TWRP,Philz) the Data partition Cannot be mounted or formated.What Can I do?I read threads on the Transformer Forum but nothing of these working for me :crying:
Click to expand...
Click to collapse
Only one that can mount it will be twrp 2.7.1.1 (or the f2fs twrp released in dev)
If it has corrupted just format it back to ext4 and start again.
This is the log when I press wipe or repair partition.in the mount menu i cant select any partition
Sent from my GT-I9505G using XDA Free mobile app
andreas1996 said:
This is the log when I press wipe or repair partition.in the mount menu i cant select any partition
Click to expand...
Click to collapse
That's not a log, it's a screenshot. The log is in /tmp/recovery.log, so you can use adb pull to get it and post it. Or you can probably use the "copy log to SD card" option in the advanced menu.
Here is the log.I compressed the file because the log format is not supported to attachments.
andreas1996 said:
Here is the log.I compressed the file because the log format is not supported to attachments.
Click to expand...
Click to collapse
According to the log, your recovery can't access any partitions on your eMMC. To find out more, reboot to your recovery again and run on the connected PC:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt
and read/post the resulting files.
Here is the two files your commands gave me
andreas1996 said:
Here is the two files your commands gave me
Click to expand...
Click to collapse
Your tablet's eMMC seems to have no partitions at all:
Code:
<6>[ 4.770320] mmcblk0: unknown partition table
What exactly did you do for "a F2FS conversion to Data Partition"? Did you format mmcblk0 instead of mmcblk0p8?
The only thing I did after f2fs conjversion is in Philz recovery I select wipe to install a new ROM.And the problem began.
andreas1996 said:
The only thing I did after f2fs conjversion
Click to expand...
Click to collapse
If you expect help, you need to answer my question. I did not ask what you did *after* the f2fs conversion - what exactly did you do to convert /data to f2fs?
enter recovery-wipe-advanced-repair or change filesystem-f2fs-reboot
andreas1996 said:
enter recovery-wipe-advanced-repair or change filesystem-f2fs-reboot
Click to expand...
Click to collapse
Friend! You got the attention of one of the few people who may be able to help you get your tab back! Use it!
Post DETAILED steps of what you did or _that is going to ignore you!
Which recovery and version thereof did you use?
What did you do afterwards? You mention 3 recoveries. Did you flash all of them?
What did you do in which order in each of them?
Provide as many details as you can!
First I used the modded twrp recovery from the f2fs thread.I did the f2fs and the chromi-kk work successfull.But because battery drain I wanted to install the last chromi-x version based to stock firmware.Next,I didn't convert f2fs back to ext4,but I made a full wipe with twrp 2.7.1.1.And my problems began.
Also I tried full wipe from the latest CWM and Philz recovery with the same results
andreas1996 said:
First I used the modded twrp recovery from the f2fs thread.I did the f2fs and the chromi-kk work successfull.But because battery drain I wanted to install the last chromi-x version based to stock firmware.Next,I didn't convert f2fs back to ext4,but I made a full wipe with twrp 2.7.1.1.And my problems began.
Also I tried full wipe from the latest CWM and Philz recovery with the same results
Click to expand...
Click to collapse
Define "full wipe".
Which CROMi-X version did you try to flash?
Details, details....
andreas1996 said:
First I used the modded twrp recovery from the f2fs thread.I did the f2fs and the chromi-kk work successfull.But because battery drain I wanted to install the last chromi-x version based to stock firmware.Next,I didn't convert f2fs back to ext4,but I made a full wipe with twrp 2.7.1.1.And my problems began.
Also I tried full wipe from the latest CWM and Philz recovery with the same results
Click to expand...
Click to collapse
OK So your issue is that you have left your data partition as f2fs and installed a kernel/rom that does not understand f2fs.....
So as I see it - install a recovery that will reformat as EXT4 - format data and start again?
sbdags said:
So as I see it - install a recovery that will reformat as EXT4 - format data and start again?
Click to expand...
Click to collapse
How would you format data without a data partition?
sbdags said:
OK So your issue is that you have left your data partition as f2fs and installed a kernel/rom that does not understand f2fs.....
So as I see it - install a recovery that will reformat as EXT4 - format data and start again?
Click to expand...
Click to collapse
I tried that but the TWRP gave me a ERROR message(cannot mount Data).Tomorrow i will upload screenshots and full logs for that,because my transformer has empty battery because of the attempts
andreas1996 said:
I tried that but the TWRP gave me a ERROR message(cannot mount Data).Tomorrow i will upload screenshots and full logs for that,because my transformer has empty battery because of the attempts
Click to expand...
Click to collapse
So try formatting from adb?
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
sbdags said:
So try formatting from adb?
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Click to expand...
Click to collapse
When I doing the command (make_ext4fs /dev/block/mmcblk0p8) I receive the message : Need size of file system.
Something seems to be wrong with your GPT. Unfortunately the busybox tools don't support big offsets to read it, so let's first see if the Tegra-specific partition table (which is not used by the kernel) is still there - that won't help you immediately but will show if the eMMC can be read at all and where the partitions are supposed to be. Post the output file of this command:
adb shell hexdump -s 0x300000 -n 2048 -C /dev/block/mmcblk0boot0 > pt.txt