[Q]Why can't my Galaxy Mini boot a CustomROM - Samsung Galaxy Mini

Hi all,
I have kind of a strange problem with my girlfriends Galaxy Mini S5570.
It was bought with Android 2.2.1 installed, later on I flashed a 2.3.4 Stock ROM with Odin.
What I try to achieve now is using a CustomROM and so far I've tried to flash CM7.2 and emanoN 6, both without luck. Here comes what I did and what happens for both ROMs:
using Odin 4.42 and without SIM or SD installed, I flashed a Stock 2.3.6 (XWKTN) (PASS)
also with Odin I flashed CWM 4 (PASS)
in order to flash the CustomROM of my choice I wiped everything on the Galaxy (data/cache/DalvikCache)
SD card has a 256MB ext4 partition that is mounted later as /sd-ext
using zip installation I flashed CM7.2 stable or later emanoN 6, flashing went fine
at time of reboot it always gets stuck
Everytime I try to boot one of the CustomROMs it shows the initial Model information, then the boot animation that ends with the shiny SAMSUNG text, then screens turns black but backlight still on and every couple of minutes the phone vibrates very short.
The phone can be accessed by adb and responds fine there but screen is always black with dimmed backlight. All relevant volumes are mounted. data partition has some 10,000kB on it which varies up and down by some kB.
Code:
# df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 143016 32 142984 0% /dev
tmpfs 143016 0 143016 0% /mnt/asec
tmpfs 143016 0 143016 0% /mnt/obb
/dev/stl14 25436 4200 21236 17% /cache
/dev/stl13 182672 10668 172004 6% /data
/dev/stl12 211400 166728 44672 79% /system
/dev/block/mmcblk0p2 245692 4236 241456 2% /sd-ext
/dev/block/vold/179:1
1678340 98384 1579956 6% /mnt/sdcard
/dev/block/vold/179:1
1678340 98384 1579956 6% /mnt/secure/asec
Code:
# ls /system
ls /system
T9DB bin etc lib misc xbin
TEAM build.prop fonts lost+found usr
app cameradata framework media wifi
# ls /data
ls /data
aeqcoe.txt dalvik-cache lost+found system
anr data misc system_ordered
app data_ordered property tombstones
app-private dontpanic radio zipalign.db
backup gps sd_ordered zipalign.log
cache local secure
cache_ordered log soundbooster.txt
# ls /sd-ext
ls /sd-ext
lost+found
# ls /mnt/sdcard
ls /mnt/sdcard
Android LOST.DIR
DCIM emanoNROM-v6-signed.zip
When trying emanoN 6 after CM7.2 failed, of course I went through the full procedure again, starting with Stock ROM via Odin. Also I tried using CWM 5 which I zip-installed from within CWM 4. Both ROMs hav the exact same behavior and I have no idea what causes it.
I can always access CWM or Download mode, nothing looks bricked to me. When I flash a Stock ROM again, no matter which, it just boots and runs fine.
Now it's my hope that anybody has seen this before and can point me to where the problem is.
Thanks and very best regards,
Peter

Did u root your your device
Sent from my GT-S5570 using Tapatalk 2

Did u do a full wipe ?
Sent from my GT-S5570 using Tapatalk 2

Hi Messi10,
at which point is rooting required when installing a pre-rooted ROM like CM7.2 or emanoN? Did I miss something here? I didn't apply any separate root solutions in the process.
Hi R.A.G.E,
yes I did. I always wiped data/cache/Dalvik Cache and once even Battery Stats. All content in data that I've posted in my initial post came from first boot of the CustomROM, in this case it was emanoN.
Thanks, Peter

PeBo75 said:
Hi Messi10,
at which point is rooting required when installing a pre-rooted ROM like CM7.2 or emanoN? Did I miss something here? I didn't apply any separate root solutions in the process.
Hi R.A.G.E,
yes I did. I always wiped data/cache/Dalvik Cache and once even Battery Stats. All content in data that I've posted in my initial post came from first boot of the CustomROM, in this case it was emanoN.
Thanks, Peter
Click to expand...
Click to collapse
For me i rooted my device first then i installed CMW i don't have any problem when flash roms
Sent from my GT-S5570 using Tapatalk 2

I always use 2.3.4 as my base and everything is always fine.
Do u have the sim inserted when u boot the phone after flashing a rom?

roofrider said:
I always use 2.3.4 as my base and everything is always fine.
Do u have the sim inserted when u boot the phone after flashing a rom?
Click to expand...
Click to collapse
Hi roofrider,
I used XWKTN and also XWKTH, both are 2.3.6. I did because that is told to be the base ROM for the emanoN. In his TUT parasmi says any 2.3.x would do as base but I tried XWKTH many times as well which is the one he mentions in his changelog.
When booting after flash I tried both, with and without SIM inserted. Makes no difference.
Is there anything I can check via adb to see where the phone gets stuck?
Where can I find the OS log files? Would like to have a look at them.
This it what it shows in dmesg every now and then:
Code:
<3>[ 1547.963619] kgsl kgsl: |kgsl_yamato_waittimestamp| Device hang detected wh
ile waiting for timestamp: 6, last submitted(rb->timestamp): 7, wptr: 87

ya, just do
adb logcat > log.txt
Then later terminate it with ctrl+c

wipe is also needed after flash, so wipe two times before installing and after ibstalling

dheeraj (dhlalit11) said:
wipe is also needed after flash, so wipe two times before installing and after ibstalling
Click to expand...
Click to collapse
not mandatory (i mostly don't do), but if things don't work, sure why not.

roofrider said:
ya, just do
adb logcat > log.txt
Then later terminate it with ctrl+c
Click to expand...
Click to collapse
Thanks, I did that now during a full boot until the first time it vibrated after a couple of minutes.
Condition: no SIM, SD with Ext4fs and VFAT, data/cache/dalvik cache wiped -> first boot of emanoN v6
As soon as the phone booted up I fired adb logcat, even before adb was ready. First response was "- waiting for device -", then it captured as per attachment.

Actually ur phone boots just fine, i see this a lot
Code:
W/SharedBufferStack( 2782): waitForCondition(LockCondition) timed out (identity=1, status=0). CPU may be pegged. trying again.
but then this is just a warning..
So ur display is actually just freezing...
Pulling out the battery and rebooting again gives the same result?
Also the bootanimation does not end with a samsung logo..at least not for CM7.
Also it vibrating once just after the bootanimation(or end stage of bootanimation) is normal.

roofrider said:
Actually ur phone boots just fine, i see this a lot
Code:
W/SharedBufferStack( 2782): waitForCondition(LockCondition) timed out (identity=1, status=0). CPU may be pegged. trying again.
So ur display is actually just freezing...
Pulling out the battery and rebooting again gives the same result?
Also the bootanimation does not end with a samsung logo..at least not for CM7.
Click to expand...
Click to collapse
Pulling battery is the only way to get out of it. At next reboot the same happens again.
This log was from emanoN v6. It checks if there is a custom bootanimation on SD card, if not it shows the Samsung default. You can see this in early stages of booting in the log.
Anyway, I have not confirmed the details via log file but the behavior was exactly the same when CM7.2 was flashed.
The vibration is not at this early stage but after having it some minutes on the table... untouched. In the log a whole lot of things happens again then. Could this be caused by a partly restart of something? Also it vibrates not once but endless times if I just leave it in this state. (Sorry, I still have the 5 minutes time barrier for editing/posting)
Now what could cause this message which appears a thousand times?
@dheeraj: I have wiped so many times: before, after and also before + after flashing. I'm sure it's nothing that can be solved with another wipe.

I'm exactly not sure..but googling this error helps a little...try searching maybe u'll find something.
--sry.
try running logcat longer and check..that should tell a little more.
possible reasons:
-try booting without SD card, it could be cos of a2sd (just a blind guess).
-maybe a certain app that is included is the culprit (again just a guess).
--OT--
U've been a member since 2010 and this is the 1st time ur posting!

Related

Help: Safestrap questions

Need some help here. Basically im on the tweaked bootstrap( the one where it says bootstrap recovery and reboot recovery when the apk is clicked on) and im currently running the monster rom. Ive been recently interested in installing safestrap but i have no idea how to switch over. Ive been reading alot of different forums and people have been struggling trying to switch and i heard theres data confliction and it can be difficult. Soo im gonna throw some questions at you guys and it might be alot but its good info that i would like to know so... thanks in advance!!
1) Do i have to start from scratch. Meaning wipe data as my first step?
2) is it as simple as deleting the bootstrap and installing safestrap?
3) Can i flash a new rom with safestrap (lets say cm7 for example) over the monster rom even tho monster was installed using the tweaked bootstrap?
4) using safestrap, how does it actually work? Meaning do i still install a new rom the same or similliar way as the tweaked bootstap? ( ex: cwm recovery.. install from sd.. etc.)
5) and the 5th question is. Im sure im missing some important info so.. What am i missing that would be helpful to me?
THANK YOU GUYS
Sent from my droid 3 using Tapatalk
you can just install safestrap but when you flash a rom now it will be flashed to your pre install partition leaving your original system (in this case with monster rom intact, though hash meant for you to keep the blur original system) intact. if you are leaving monster rom though i recommend just backing up with titanium backup and sbf ing back to stock then doing everything from safetsrap from now on
jellydroid13's answer is right on point.
However, I can answer your questions in more detail:
1. Installing Safestrap won't affect your primary system, as jellydroid13 says. It's meant to add a "2nd- system" where you're protected against bad flashes, etc. So there's no worry about /data for the 1st step.
2. Yes. Remove Koush's Bootstrap and Install Safestrap. Then open the app and use the "Install Recovery" button. The next time you reboot, you'll should see a splashscreen right after the Red "M" Logo. While that's being displayed you can enter Safestrap recovery by hitting the [ menu ] button.
3. No. Currently, there is no way for you to affect your MonsterROM /system from Safestrap. Be it flashing or otherwise. Now you can do a bunch of stuff with the data for your MonsterROM installation, via backup / restore, etc. But that's a bit more advanced.
4. Safestrap is basically a modified version of Clockwork Recovery. It has mostly the same menus for making backups, flashing ROMs, etc. If you're familiar with Koush's Clockwork Recovery, then you'll immediately know where everything is in Safestrap. For reference, Safestrap recovery is currently using CWRecovery 5.0.2.7 sources as it's base.
The biggest difference is that anywhere you see "/system" it's talking about a 2nd-system on your phone. SO, when you flash a ROM, you're flashing it to this 2nd area which you can now choose to boot from.
Added to the normal Clockwork Recovery menus is a Safestrap Menu, where you can set which system you want to boot from. When you "toggle" between the systems, Safestrap will stash your current data/cache files and save them and try to load any previously stashed data/cache for the system you're going to.
If you want your data from a previous ROM (or the Non-safe system) you'll need to advanced restore it from a backup file (data partition only). In many cases, data can cause a hung boot. If it does, then battery pull, go back into Safestrap recovery and wipe data/cache. You'll have to use a titanium backup instead once the OS is loaded.
5. Know that the /system backups you make in Safestrap are NOT compatible with Koush's Bootstrap(or the tweaked version of it). Safestrap expects to be loaded from the /preinstall partition. When you try and restore a Safe System to the main /system.. you will get a hung boot at the Red "M" Logo.
Don't do it... Bad.
Just so I understand.....
Hashcode, can you tell me if the following is true?
The actual phone has only one "real" /data partition.
Each time you toggle between systems (which is done via toggleing safe mode on and off), safestrap tars up the contents of /data and copies the tar file to sd/emmc, then DELETES the contents to free up the only real /data partition. Then optionally restores the /data from the previously deactivated system from a previously created tar file.
Right now my phone is running CM4D3 from an activated safesystem. Can I assume the contents of my original /system partition still contains the stock blur rom, and my original stock /data has been DELETED (after having been tarred up and moved to SD/EMMC by the toggle process)?
Questions:
Is the /restore partition a real actual disk partition or is it a subdirectory somewhere?
If something goes terribly wrong, is there a working SBF method that works no matter what has happened?
Following your directions, I do a "wipe data/factory reset". During this process, safestrap says it's formatting sdcard-ext. This obviously scared the **** out of me. Turns out my external sdcard was NOT formatted. What actually happened?
Now that I have a orig system and cm4d3 system in my tars, do I need to wipe data/cache and format system each time I toggle? (Does the unzipping of the saved system info do a format or wipe first)?
Since I did a backup BEFORE activating safe system, this backup does contain my stock /system and stock /data correct? I was using safestrap 1.04.
When you release a new version of cm4d3, do I need to wipe data before installing if I'm running a previous version of cm4d3?
When I installed safestrap, did you resize any of my physical partitions?
So far, I love SafeStrap and CM4D3. What was bugging me about stock (openvpn and tether) is working great! Thanks for all your hard work. For me, the only thing I see so far are the known audio-volume and camera issues. Also, it seems youtube and cam360 both try to scale and position video into a small box rather than go fullscreen (or be where they should be). MoboPlayer in hardware decode mode gets it wrong too, but in software decode mode, works fine.
Hello ryanmcdonald,
These are very insightful questions. I'm probably going to put them up on my FAQ.
Answers:
- Yes, the phone (and Safestrap) currently manage the 1 /data partition. (It's 2Gig in size, I couldn't find a 2nd area to store Safestrap's data in)
- Yes, it's doing a /data swap between toggles from the original system to 2nd-system.
- Your original system still contains the stock blur ROM. And your original /data has been moved to the .tar in {internal storage}/safestra/orig (and deleted from the /data partition)
- The restore files are stored in a subdirectory on your internal storage: safestrap/orig and safestrap/safe
- YES, we have a full fastboot for 5.6.890 (It's somewhere around here in the forums)
- The message is "formatting sd-ext" but yeah it looks scary when you first see it. The sd-ext area is where apps go when you place them on the SD card.
- You do not need to wipe data/cache between toggles now, as long as you want the same ROM and apps when you go back to that system.
- YES, you did exactly what you should have done: make a full backup prior to entering Safe Mode which means you have a fall back of your entire stock system for Safestrap to restore from should anything unforseen happen.
- You will not need to wipe data for new versions of CM4D3 (unless I say so in the release notes, but I can't think of a reason offhand.)
- No, I didn't resize any partitions. SIDE NOTE: I was considering in the future placing the 2nd-system and a new 2nd-data partition on the external storage area -- which would require resizing the vfat partition to be smaller by about 2GIG. But, I'll talk about that if I move towards that direction. I need to confirm that running from the SD card is a stable option through testing.
And thanks!
I had the Droid3Bootstrapper installed on my Droid3 with stock ROM. I uninstalled it and installed Safestrap apk.
I am getting the safestrap spalsh screen on boot up BUT when I hit the menu button I get a blank screen...I have to remove the battery to get it to reboot. Then it reboots to Blur with no problems...
I tried doing an factory reset within blur and still getting the same hang up after pushing the menu button on boot up...
Any suggestions on where I go from here?
Thank you!
johnniekombat said:
I had the Droid3Bootstrapper installed on my Droid3 with stock ROM. I uninstalled it and installed Safestrap apk.
I am getting the safestrap spalsh screen on boot up BUT when I hit the menu button I get a blank screen...I have to remove the battery to get it to reboot. Then it reboots to Blur with no problems...
I tried doing an factory reset within blur and still getting the same hang up after pushing the menu button on boot up...
Any suggestions on where I go from here?
Thank you!
Click to expand...
Click to collapse
I had the same problem but hashcode never answered after asking multiple times . After 3rd time reinstalling safestrap and reinstall recovery my phone bootlooped on droid 3 screen and had to debrick with .890 SBF.
When I tried safestrap then it worked fine. I think there is a bug when removing the old boostrap.
DoubleYouPee said:
I had the same problem but hashcode never answered after asking multiple times . After 3rd time reinstalling safestrap and reinstall recovery my phone bootlooped on droid 3 screen and had to debrick with .890 SBF.
When I tried safestrap then it worked fine. I think there is a bug when removing the old boostrap.
Click to expand...
Click to collapse
I remember he said he had 3 people who had issues like you are describing. i believe uninstalling his bootstrap and then installing safestrap should do it. i thought part of the safestrap install was to remove the other hijacks. when in doubt, SBF, root with 1 click, safestrap and go go go
edit: i recently moved from tweaked bootstrap to safestrap and it worked find for me and its in his instructions per the thread in dev. DoubleYouPee I see where you actually quoted Hashcode saying that but i cant find where he said he knew of a couple people who had problems but i know he said he was looking into it. that couldve been a prior release too, not sure.
johnniekombat said:
I had the Droid3Bootstrapper installed on my Droid3 with stock ROM. I uninstalled it and installed Safestrap apk.
I am getting the safestrap spalsh screen on boot up BUT when I hit the menu button I get a blank screen...I have to remove the battery to get it to reboot. Then it reboots to Blur with no problems...
I tried doing an factory reset within blur and still getting the same hang up after pushing the menu button on boot up...
Any suggestions on where I go from here?
Thank you!
Click to expand...
Click to collapse
Which version of the Droid3Bootstrap were you running? I had made an original one back in Sept. (before Koush picked up support). And that hijack was slightly different than Koush's. It may be that there's an issue with Safestrap cleaning up the hijack files for that original version.. but I'd like to see what you were running.
Well, in my case i was using your updated version of koush bootstrap. I succesfully used it to create 2 nandroids.
Then uninstalled, installed safestrap 1,04, installed recovery, reboot, touch menu, black screen. Retried a couple of times..on the 3rd time it bootlooped.
It works fine now though after SBF.
Hello Hashcode,
I was wondering if the deodexing rom found on the rootzwiki is compatible with safestrap, I had tried it last night but got nothing but a black lit up screen anf had to battery pull after several minutes
RandomTaskMan said:
Hello Hashcode,
I was wondering if the deodexing rom found on the rootzwiki is compatible with safestrap, I had tried it last night but got nothing but a black lit up screen anf had to battery pull after several minutes
Click to expand...
Click to collapse
I'm not sure but that ROM might still have the /system/etc/rootfs files in it which causes Safestrap to bomb out during boots.
You can try deleting that folder from the ROM. Then format your /system and re-flashing. Let me know if that fixes it.
---------- Post added at 04:30 PM ---------- Previous post was at 04:25 PM ----------
DoubleYouPee said:
Well, in my case i was using your updated version of koush bootstrap. I succesfully used it to create 2 nandroids.
Then uninstalled, installed safestrap 1,04, installed recovery, reboot, touch menu, black screen. Retried a couple of times..on the 3rd time it bootlooped.
It works fine now though after SBF.
Click to expand...
Click to collapse
There may be some case I'm missing for the cleanup of the old bootstrap code, and I'm nearly certain you ended up with 2 bootstraps installed. I'll have to take a look and see if I did anything different in my tweaked version vs. his which is available in the Market. Sorry about that.
I'd also like to apologize for missing your posting on the other thread asking for help. At the time I was checking 4 different forums for Safestrap issues, and working on a new release of CM7 for the D3.
Unfortunately, I totally passed over your posting some how and it got lost in the mix.
Hashcode said:
I'd also like to apologize for missing your posting on the other thread asking for help. At the time I was checking 4 different forums for Safestrap issues, and working on a new release of CM7 for the D3.
Unfortunately, I totally passed over your posting some how and it got lost in the mix.
Click to expand...
Click to collapse
Ah I see, well no problem then I also think it didn't properly remove the older boostrap. But I'm sure I followed the right steps. Anyway the debrick was very easy with the 5min debrick and it works great now. Used it with maverom.
Goodluck with safestrap and CM7 etc!
Worked like a charm! Thank you sir!
WORKS like a charm. Thank you for your hard work. Your dedication to the development of these products is greatly appreciated.
Bootloop in safe system of Droid 3 XT862
I have a bootloop problem. (Thanks to Safestrap, it's recoverable ) I activate the "safe system". Format /system. Wipe data (and cache, sd-ext, .android-secure). I also tried anally retentive extra wipes; didn't help. I installed CM4D3-nightly-20111116-1445.zip with gapps-gb-20110828-signed.zip; also tried motoblur-5.7.894.zip with the same result. I tried an extra wipe at this point; didn't help. Reboot (also tried power cycling and a battery pull; didn't help). Motorola logo for 8 secs, Safestrap boot menu for 10 secs, gray screen (lamp on but all pixels black) for 22 secs; at this point the boot animation should start, but the screen goes black (lamp off) for 5 secs and the Motorola logo reappears, starting from the beginning. I've removed and re-installed safestrap-1.06, didn't help. Here are some versions, from About Phone in the unsafe (stock) system:
Model Number: DROID3
System Version: 5.5.959.XT862.Verizon.en.US
Baseband Version: N_03.18.16P
Safestrap version: 1.06​In another thread Hashcode asked for this info: ls -l /system/bin/log*
lrwxrwxrwx root shell 2011-06-13 00:10 log -> toolbox
-rwxr-xr-x root shell 13952 2011-06-12 23:57 logcat
-rwxr-xr-x root shell 6975 2011-12-12 10:49 logwrapper (By: Hashcode)
-rwxr-xr-x root root 9760 2011-12-09 21:59 logwrapper.bin
cat /proc/cmdline #list breaks inserted for readability
console=/dev/null rw [email protected] vram=4M omapgpu.vram=0:4M
init=/init ip=off brdrev=P2A omap3_die_id androidboot.bootloader=0x0000
mmcparts=mmcblk17(pds),p15(boot),p16(recovery),p17(cdrom),p18(misc),
p19(cid),p20(kpanic),p21(system),p22(cache),p23(preinstall),
p24(userdata),p25(emstorage)
(busybox) df
Filesystem Size Used Free Blksize
/dev 219M 76K 219M 4096
/mnt/asec 219M 0K 219M 4096
/mnt/obb 219M 0K 219M 4096
/system 320M 312M 8M 1024
/data 1G 472M 1G 4096
/cache 535M 16M 518M 4096
/data/tmp 2M 12K 1M 4096
/pds 3M 1M 2M 1024
/preinstall 464M 181M 283M 1024
/mnt/sdcard-ext 966M 460M 505M 4096
/mnt/sdcard-ext 966M 460M 505M 4096 (listed twice)
/mnt/sdcard 11G 1G 9G 8192
/mnt/secure/asec 11G 1G 9G 8192
/mnt/sdcard/.android_secure: Cross-device link
/mnt/sdcard 11G 1G 9G 8192 (listed twice)
Does anyone have a suggestion what I could try next, or what detail I might have omitted? Normally I would install safestrap-1.07 but I'll wait for responses before trying.
jimcarter said:
I have a bootloop problem. (Thanks to Safestrap, it's recoverable ) I activate the "safe system". Format /system. Wipe data (and cache, sd-ext, .android-secure). I also tried anally retentive extra wipes; didn't help. I installed CM4D3-nightly-20111116-1445.zip with gapps-gb-20110828-signed.zip; also tried motoblur-5.7.894.zip with the same result. I tried an extra wipe at this point; didn't help. Reboot (also tried power cycling and a battery pull; didn't help). Motorola logo for 8 secs, Safestrap boot menu for 10 secs, gray screen (lamp on but all pixels black) for 22 secs; at this point the boot animation should start, but the screen goes black (lamp off) for 5 secs and the Motorola logo reappears, starting from the beginning. I've removed and re-installed safestrap-1.06, didn't help. Here are some versions, from About Phone in the unsafe (stock) system:
Model Number: DROID3
System Version: 5.5.959.XT862.Verizon.en.US
Baseband Version: N_03.18.16P
Safestrap version: 1.06​In another thread Hashcode asked for this info: ls -l /system/bin/log*
lrwxrwxrwx root shell 2011-06-13 00:10 log -> toolbox
-rwxr-xr-x root shell 13952 2011-06-12 23:57 logcat
-rwxr-xr-x root shell 6975 2011-12-12 10:49 logwrapper (By: Hashcode)
-rwxr-xr-x root root 9760 2011-12-09 21:59 logwrapper.bin
cat /proc/cmdline #list breaks inserted for readability
console=/dev/null rw [email protected] vram=4M omapgpu.vram=0:4M
init=/init ip=off brdrev=P2A omap3_die_id androidboot.bootloader=0x0000
mmcparts=mmcblk17(pds),p15(boot),p16(recovery),p17(cdrom),p18(misc),
p19(cid),p20(kpanic),p21(system),p22(cache),p23(preinstall),
p24(userdata),p25(emstorage)
(busybox) df
Filesystem Size Used Free Blksize
/dev 219M 76K 219M 4096
/mnt/asec 219M 0K 219M 4096
/mnt/obb 219M 0K 219M 4096
/system 320M 312M 8M 1024
/data 1G 472M 1G 4096
/cache 535M 16M 518M 4096
/data/tmp 2M 12K 1M 4096
/pds 3M 1M 2M 1024
/preinstall 464M 181M 283M 1024
/mnt/sdcard-ext 966M 460M 505M 4096
/mnt/sdcard-ext 966M 460M 505M 4096 (listed twice)
/mnt/sdcard 11G 1G 9G 8192
/mnt/secure/asec 11G 1G 9G 8192
/mnt/sdcard/.android_secure: Cross-device link
/mnt/sdcard 11G 1G 9G 8192 (listed twice)
Does anyone have a suggestion what I could try next, or what detail I might have omitted? Normally I would install safestrap-1.07 but I'll wait for responses before trying.
Click to expand...
Click to collapse
Looks like you never got the OTA for 5.6.890 install that first then try again.
I second the OTA install. In almost all cases, the ROMs are built from the 5.6.890 files (including kernel modules).
With 5.6.890 CM4D3 boots
Thanks, Hashcode and eww245! I de-installed Safestrap Recovery, uninstalled Safestrap entirely, (didn't remove Superuser, Busybox or setUID "su"), updated to system 5.6.890 and reinstalled everything. Now CyanogenMod CM4D3-nightly-20111116-1445.zip installs and boots successfully.
I have an initial report on items that I tested. Almost everything is working, except I have an unusual carrier issue which I haven't dealt with yet, and the cellular connection isn't going to happen until that's resolved one way or the other. Here's the URL: (sorry, I'm new on this site so am not allowed to put links in posts, mail to [email protected] and I'll send it). The only real failure is well known to you: the camera app in the distro doesn't show camera content. But surprisingly, the Barcode Scanner app can use the rear camera to read barcodes. This suggests that the underlying driver or interface library is not whacked; the camera app may be doing something that the others avoid.
Anyway, thank you Hashcode for putting together this system image.
safestrap 3.71
I rooted my AT&T I337 4.2.2 mf3 s4 and installed safestrap It said installed and when I press install recovery it comes up with installation complete but when I reboot the phone it just reboots the phone it does not go into a safe strap menu. I am using 3.71 ver.
One quick note I have been reading and learning a lot from this site and would like to thank all the Devs for thier work. Thanks for any help you can give.
:good:

[HACK] Increase Internal Memory Size to Whatever You Want!

Free Memory to > 1Gb!​
How to Increase your Internal Memory Size with very low effort!
NOTICE: This method works both on Rooted and NOT Rooted Phones!
You simply need to meet three easy requirements:
Stock Firmware installed on the Phone (custom ROMS not supported ...They don't need to!)
A microSD with two primary formatted partitions inside (the former 'to FAT32' and the latter 'to EXT4' filesystems)
Ready to Flash to your Galaxy Next via Odin
NOTICE: The following Black Box Howto is explained deep inside in the next post of this Thread (short explanation) and in This Thread from outside: Internal Memory to +1Gb! and related ones (long explanation / Italian Language)
HOW TO
1) Download Tass.ops file for Odin!
2) Type this number on your phone keyboard:
*#1234#
and keep note of the PDA code of the Firmware installed.
3) Download boot image ready for Odin and suitable for your firmware:
All modded images are inside my Google Drive; actually we find:
Code:
[b][url=https://docs.google.com/folder/d/0B3qe_9NlA1D_QVlKXy01bjZPbVE/edit]Memory Hack Google Drive Archive[/url][/b]
[b][size=3]Galaxy MINI/NEXT/POP[/size][/b]
S5570AIKQ3 S5570BGKS3 S5570BGKT2
S5570BVKQ4 S5570BVKT1 S5570DDKA7
S5570DDKQ7 S5570DXKPD S5570DXKT6
S5570JPKQ8 S5570JPKS1 S5570JPKT2
S5570JVKQ3 S5570JVKT1 S5570MJKS2
S5570XIKQC S5570XWKE3 S5570XWKQG
S5570XWKS2 S5570XWKS7 S5570XWKT7
S5570XWKTH S5570XWKTN S5570XWKTS
S5570XWKTU S5570XXKPF S5570XXKPI
S5570XXKPK S5570XXKS1 S5570XXKS4
S5570ZSKPC
-----------
S5570bVJKPB
-----------
S5570LWMKP9 S5570LWMKPJ S5570LWMKPO
[b][size=3]Galaxy MINI/NEXT/POP[/size][/b]
[b]Froyo[/b]
S5570DXKB1 S5570XIKFI S5570XWKC1
[b][size=3]Galaxy GIO[/size][/b]
S5660AIKT4 S5660DXKT8 S5660JPKT7
S5660XXKPA S5660XXKTF S5660XXKTI
S5660XXKTK S5660XXKTO
-----------
S5660MUGKG3
[b][size=3]Galaxy FIT[/size][/b]
S5670DDKB1 S5670DDKT3 S5670DXKPB
S5670DXKT4 S5670JPKQ7 S5670XWKQA
S5670XWKTI S5670XXKPQ S5670XXKPU
-----------
S5670LUBKP6 S5670LUBKPI
[b][size=3]Galaxy ACE[/size][/b]
S5830BOKS3 S5830DDKQ5 S5830DDKQ8
S5830DXKPB S5830DXKPD S5830DXKT5
S5830XWKPY S5830XWKS2 S5830XWKS9
S5830XWKT7 S5830XWKTM S5830XWKTQ
S5830XXKPH S5830XXKPP
your firmware not listed? ...take a look into Google Drive first, then let me know if you don't find anything!
4) Flash the downloaded archive with Odin
Example image follows:
{
"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"
}
5) THAT'S ALL FOLKS!
- - -​
How does it Work:
Scenario 1:
I switch on the Phone, without a MicroSD slotted in or with a microSD with a single FAT32 partition (broken or damaged microSD also suite this scenario...); GingerBread boots as usual!
No Difference!
Scenario 2:
I switch on The Phone with a microSD slotted in (with the second partition formatted as EXT4 filesystem but still EMPTY); Ginger boots acting as if
/data
is completely moved outside to microSD but just WIPED (not true obviously, and the original /data is safe inside the phone), so it resettle it from beginning...
NOTICE:
...If your second partition is 1Gb wide...
...your new Internal Memory will be 1Gb wide...
Scenario 3:
I switch on the Phone with the second partition of the microsd (EXT4) up and running (already resettled up for use and with my userdata on it); Ginger simply boots with
/data
moved outside to microSD with your userdata there and tons of apps just installed from the market...
Example Image of my New Internal Memory Size follows
- - -​
NOTICES & ADVICES:
If I want to remove the microSD from the slot, FIRST I NEED TO SWITCH OFF THE PHONE!
When I install apps from the Market, Ginger Misunderstands the actual new Internal Memory SIZE and puts the apk files to External Storage anyway! I simply need to move them "to the phone" via "Settings menu" immediately after!
When I switch on the Phone without the microSD, I boot using the original /data inside the phone, actually loosing all the apps installed onto the external one untill next boot with SDcard; and, of course, loosing my sms stored there and others personal userdata too.
Unfortunately this boot image heavy conflicts with Link2SD (great app anyway!), so you must choose one: This Boot image or Link2SD... not both... sorry!
Don't You Like the boot image just installed and You want to revert without flashing the full firmware to the Phone?
The original images, ready for Odin, are stored into my Google Drive too, inside BASE subfolders!
- - - - - - - - - - - - - - - - -​
THREAD ADDONS
CHECK FILESYSTEM FOR ERRORS
On post n. 43 you can find an Android Application useful to check the 2nd partition filesystem for errors once a month...
EXT4 Checkup Tool 1.0 RC3
P.S. Only for rooted phones!
Click to expand...
Click to collapse
HOW TO
From post n. 52 I explain exactly What I do deep Inside and Step by Step...
Click to expand...
Click to collapse
ADDED PHONE MODELS
In post n. 56 I added boot images modded for Galaxy FIT (S5670), Galaxy ACE (S5830) and Galaxy GIO (S5660)!
Click to expand...
Click to collapse
ALL IN ONE WONDER AUTOSCRIPT
In post n. 78 I added a Linux Script "All in one" to mod your boot Image on your own simply with a double-click!
Click to expand...
Click to collapse
MEMORY AND OVERCLOCK KERNEL
In post n. 148 you find modded images with OC Kernel inside
P.S. Only for rooted phones with CWM or Custom Recovery!
Click to expand...
Click to collapse
Patched Boot Image "Deep Inside"
As I stated in the previous Post, I skip the Long Explanation of this How to (Italian Threads online anyway) and briefly describe What I did!
1) Split Boot.img
I splitted boot.img into it's two main parts: The Kernel and the Ramdisk.
2) Edit ramdisk
2.1) Strip Samsung Kernel Modules
I figured out that Samsung modules used for rfs filesystem are compiled with all the debug symbols inside, so I stripped them saving more than 3Mb into the ramdisk!
NOTICE: The boot.img must not exceed 8Mb Size or I cannot flash it! BEWARE!
2.2) Add Ext4 kernel Modules
I compiled the jbd2.ko and ext4.ko modules for the attached Kernel and put them into /lib/modules inside the ramdisk:
Code:
gandalf $ ls -l ./ramdisk/lib/modules/
totale 1304
-rw-r--r-- 1 root root 236116 11 dic 08.24 [b]ext4.ko[/b]
-rw-r--r-- 1 root root 363932 11 dic 08.24 fsr.ko
-rw-r--r-- 1 root root 211200 11 dic 08.24 fsr_stl.ko
-rw-r--r-- 1 root root 58176 11 dic 08.24 [b]jbd2.ko[/b]
-rw-r--r-- 1 root root 260568 11 dic 08.24 rfs_fat.ko
-rw-r--r-- 1 root root 90968 11 dic 08.24 rfs_glue.ko
-rw-r--r-- 1 root root 99532 11 dic 08.24 sec_param.ko
gandalf $
2.3) Patch init.rc file
I patched the init.rc file into the ramdisk to load these modules into the kernel immediately after the first boot stage of the firmware:
Code:
# insmod fsr/rfs modules
insmod /lib/modules/fsr.ko
insmod /lib/modules/fsr_stl.ko
insmod /lib/modules/rfs_glue.ko
insmod /lib/modules/rfs_fat.ko
insmod /lib/modules/sec_param.ko
[color=red]insmod /lib/modules/jbd2.ko[/color]
[color=red]insmod /lib/modules/ext4.ko[/color]
2.4) Add busybox
I added a copy of busybox into /sbin.
I'll need it to mount ext4 filesystems on microSD later on.
Code:
gandalf $ ls -l ./ramdisk/sbin/
totale 2088
-rwxr-x--- 1 root root 117948 11 dic 08.18 adbd
-rw[color=red][b]s[/b][/color]r-xr-x 1 root root 2016700 11 dic 08.21 [b]busybox[/b]
lrwxrwxrwx 1 root root 7 11 dic 08.18 ueventd -> ../init
(i686) gandalf ~ (i686) $
2.5) Patch init.rc again
I changed the mount command for /data!
Original code:
Code:
# Mounting of system/userdata is moved to 'on emmc' and 'on nand' sections
# We chown/chmod /data again so because mount is run as root + defaults
[color=red][b]mount rfs /dev/stl13 /data nosuid nodev check=no[/b][/color]
chown system system /data
chmod 0771 /data
Patched code:
Code:
# Mounting of system/userdata is moved to 'on emmc' and 'on nand' sections
# We chown/chmod /data again so because mount is run as root + defaults
[color=red][b]exec /sbin/busybox sh /init.data.sh[/b][/color]
chown system system /data
chmod 0771 /data
2.6) add init.data.sh file
I added an external shell file, used to mount microsd /data avoiding the Android Init Language used by init.rc.
Code:
gandalf $ cat ./ramdisk/init.data.sh
#!/sbin/busybox sh
/sbin/busybox mount -o nosuid,nodev -t ext4 /dev/block/mmcblk0p2 /data || /sbin/busybox mount -o nosuid,nodev -t rfs /dev/stl13 /data
gandalf $
3) Repack ramdisk and kernel into boot.img
I used the AOSP mkbootimg tool to repack alltoghether.
4) Prepare Odin Archive ready for flash
I created a PDA Archive with only boot.img inside.
A command sequence could be, for example:
Code:
tar -H ustar -c boot.img > CODE_S5570XWKS7_boot.tar
md5sum CODE_S5570XWKS7_boot.tar >> CODE_S5570XWKS7_boot.tar
mv CODE_S5570XWKS7_boot.tar CODE_S5570XWKS7_boot.tar.md5
That's All!
Enjoy!
Wonderful
now i am using this: http://forum.xda-developers.com/showthread.php?p=18561098
i have s5570jpks1 in pda
phone:s5570xwks2
csc:s5570ojpks1
it's arabic firmware with 2.3.5
help me please
what pda i should use?
Increase Performance? Oh Yes!
denzel09 said:
...now i am using this: http://forum.xda-developers.com/showthread.php?p=18561098
Click to expand...
Click to collapse
Great Script! Really Interesting!
Good Idea to mix /data outside with some programs still onboard, looking to performance...
At a first glance I like a lot this command:
Code:
busybox mount -t ext4 -o noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue,noatime,nodiratime,nosuid,nodev /dev/block/mmcblk0p2 /data;
I achieve the same safe result while data=ordered and barrier=1 are defaults for ext4 mount command and because I compiled ext4 kernel modules with the extended attributes disabled (nouser_xattr).
I surely agree with noatime and nodiratime due to microsd lifecycle troubleshootings, but never set noauto_da_alloc...
...after some readings I figured out that it should be a MUST Option for SSD...
While working of this bunch of code
Code:
#-- SDCard Speed Fix
if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]
then
/system/xbin/echo "8192" > /sys/devices/virtual/bdi/179:0/read_ahead_kb;
fi;
I surely upgrade AS SOON AS POSSIBLE the attached boot images to gain performance without loosing stability..
Thanks a Lot!
P.S. Great Idea Again; thanks to Amarullz too.
Actually, anyway, I moved the whole GingerBread outside... I have /data, /system and /cache alltoghether into my microSD...
...that is: "free to experiment! No need to halt and reflash on errors"...
midomad said:
i have s5570jpks1 in pda...
Click to expand...
Click to collapse
I'll take a look. Please Hold on...
Doc_cheilvenerdi.org said:
I surely upgrade AS SOON AS POSSIBLE the attached boot images to gain performance without loosing stability..
Click to expand...
Click to collapse
Please do it ASAP, thanks
Doc_cheilvenerdi.org said:
...
I surely agree with noatime and nodiratime due to microsd lifecycle troubleshootings, but never set noauto_da_alloc...
...after some readings I figured out that it should be a MUST Option for SSD...
While working of this bunch of code
Code:
#-- SDCard Speed Fix
if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]
then
/system/xbin/echo "8192" > /sys/devices/virtual/bdi/179:0/read_ahead_kb;
fi;
....
P.S. Great Idea Again; thanks to Amarullz too.
Actually, anyway, I moved the whole GingerBread outside... I have /data, /system and /cache alltoghether into my microSD...
...that is: "free to experiment! No need to halt and reflash on errors"...
Click to expand...
Click to collapse
Wow, 8 MB ? Is that really useful ? I read somewhere that 3 MB is optimum, 4 MB is slightly waste. 8MB ? Then again I might be wrong, never tried 8MB myself.
It's a good thing you come up with this doc. I read at stepph's thread how you MOVED /system to MicroSD but somehow I forgot to ask. Now you mentioned it here. Is it safe ? No i/o bottleneck / noticeable lag ? I know we'll need a really fast and reliable MicroSD card. What's yours doc ?
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC4-KANG by squadzone
Doc,
Now this just came across my mind. With /system and /data in MicroSD, does this mean we can MULTIBOOT ?
Let's say I partitioned my sdcard into 5 : 1st one is FAT32 and the other 5 is ext4. I modified boot.img from (let's say) CM7 and stock GB. On CM7's init.rc i put /system and /data into partition 2&3. On stock GB's init.rc i put them into partition 4&5. Partition 6 is used for /cache. I flashed stock with modded boot.img, play around first. Then I flashed CM7 with modded boot.img and played around. Now each time I want to switch ROM, all I have to do is flash the appropriate boot.img using CWM. This boot.img will determine which partition will be used for /system and /data.
Could it work doc ?
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC4-KANG by squadzone
Read Ahead...
distan7 said:
Wow, 8 MB ? Is that really useful? I read somewhere that 3 MB is optimum, 4 MB is slightly waste. 8MB? Then again I might be wrong, never tried 8MB myself...
Click to expand...
Click to collapse
Antutu Benchmark Total Result on my Stock ROM with a 4Gb SD Class 4 said about 1650...
After moving (without tuning filesystems...) Antutu Said about 1450...
After Amarullz reading I remounted my filesystem from the shell this way:
Code:
# busybox mount -o remount,nosuid,nodev,noatime,nodiratime,errors=continue,nouser_xattr /cache (ext2 filesystem)
# busybox mount -o remount,ro,noatime,nodiratime,nouser_xattr,barrier=1,data=ordered,noauto_da_alloc /system (ext4)
# busybox mount -o remount,noatime,nodiratime,nouser_xattr,barrier=1,data=ordered,noauto_da_alloc /data (ext4)
#
Left commit=15 backwards, but I'll put it in the new init.rc of patched boot images... I also set barrier, data order and extended attributes, even if defaults...
and Antutu said about 1550...
Actually I'm trying on the fly this tweak
Code:
# busybox echo "[b]8192[/b]" > /sys/devices/virtual/bdi/179:0/read_ahead_kb
#
While googling for optimum value...
And Antutu said about 1600
Now I'm trying to stress the system with heavy loads from/to SDCard...
...Anyway I cannot say anything yet about Battery charge..
van8x10 said:
Please do it ASAP, thanks
Click to expand...
Click to collapse
...Boot images are ready to be shared with these patches on, but I need to test them one by one... I think to be Ready within tomorrow night...
midomad said:
i have s5570jpks1 in pda...
Click to expand...
Click to collapse
Found and patched 2.3.5 fimware S5570JPKS1 with these tweaks too... scheduled to be tested within tomorrow night too...
distan7 said:
...I read at stepph's thread how you MOVED /system to MicroSD but somehow I forgot to ask. Now you mentioned it here. Is it safe ? No i/o bottleneck / noticeable lag ? I know we'll need a really fast and reliable MicroSD card. What's yours doc?
Click to expand...
Click to collapse
It is safe... Up and running very heavy since last month...
Bottlenecks and lags occurr when I stress /data writing and /system reading while /cache is working... sometimes happens...
As I said somewhere else, if You like to play with your phone dont do it! but...
...if you like (for example) to test firmwares or play around deep inside the system without flashing anything and resuming from errors whenever you want... I call it "a Must Option"
I don't have a fast SD card (now on 4Gb class 4 and very old sailor...) so I cannot compare lags and performance for now with faster memories...
distan7 said:
...With /system and /data in MicroSD, does this mean we can MULTIBOOT ?
Let's say I partitioned my sdcard into 5 : 1st one is FAT32 and the other 5 is ext4. I modified boot.img from (let's say) CM7 and stock GB. On CM7's init.rc i put /system and /data into partition 2&3. On stock GB's init.rc i put them into partition 4&5. Partition 6 is used for /cache. I flashed stock with modded boot.img, play around first. Then I flashed CM7 with modded boot.img and played around. Now each time I want to switch ROM, all I have to do is flash the appropriate boot.img using CWM. This boot.img will determine which partition will be used for /system and /data...
Click to expand...
Click to collapse
I'm working on this in my spare time... Actually - without flashing anything - I cannot change kernel from one boot to another one, but via init.rc I could start following something written somewhere on /cache or /sdcard...I could - for example - shutdown CM7 saying that I want to boot (next time) to Stock GB and viceversa...
I'm not a True Developer (Long time ago I said "Hello World" to somebody but I don't know if I will be able to do it) but I'm trying to start the system asking to th euser what to do during the boot stage...(Hard Task for me, but why not...)
Doc_cheilvenerdi.org said:
Antutu Benchmark Total Result on my Stock ROM with a 4Gb SD Class 4 said about 1650...
After moving (without tuning filesystems...) Antutu Said about 1450...
After Amarullz reading I remounted my filesystem from the shell this way:
Code:
# busybox mount -o remount,nosuid,nodev,noatime,nodiratime,errors=continue,nouser_xattr /cache (ext2 filesystem)
# busybox mount -o remount,ro,noatime,nodiratime,nouser_xattr,barrier=1,data=ordered,noauto_da_alloc /system (ext4)
# busybox mount -o remount,noatime,nodiratime,nouser_xattr,barrier=1,data=ordered,noauto_da_alloc /data (ext4)
#
Left commit=15 backwards, but I'll put it in the new init.rc of patched boot images... I also set barrier, data order and extended attributes, even if defaults...
and Antutu said about 1550...
Actually I'm trying on the fly this tweak
Code:
# busybox echo "[b]8192[/b]" > /sys/devices/virtual/bdi/179:0/read_ahead_kb
#
While googling for optimum value...
And Antutu said about 1600
Now I'm trying to stress the system with heavy loads from/to SDCard...
...Anyway I cannot say anything yet about Battery charge..
...Boot images are ready to be shared with these patches on, but I need to test them one by one... I think to be Ready within tomorrow night...
Found and patched 2.3.5 fimware S5570JPKS1 with these tweaks too... scheduled to be tested within tomorrow night too...
It is safe... Up and running very heavy since last month...
Bottlenecks and lags occurr when I stress /data writing and /system reading while /cache is working... sometimes happens...
As I said somewhere else, if You like to play with your phone dont do it! but...
...if you like (for example) to test firmwares or play around deep inside the system without flashing anything and resuming from errors whenever you want... I call it "a Must Option"
I don't have a fast SD card (now on 4Gb class 4 and very old sailor...) so I cannot compare lags and performance for now with faster memories...
I'm working on this in my spare time... Actually - without flashing anything - I cannot change kernel from one boot to another one, but via init.rc I could start following something written somewhere on /cache or /sdcard...I could - for example - shutdown CM7 saying that I want to boot (next time) to Stock GB and viceversa...
I'm not a True Developer (Long time ago I said "Hello World" to somebody but I don't know if I will be able to do it) but I'm trying to start the system asking to th euser what to do during the boot stage...(Hard Task for me, but why not...)
Click to expand...
Click to collapse
thanks a lot bro i can't wait for you're boot img
Upgrade Complete!
Upgrade completed and new boot images uploaded.
Also added S5570JPKS1 to the list!
init.data.sh changed to
Code:
#!/sbin/busybox sh
if /sbin/busybox [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]
then
/sbin/busybox echo "[b]3072[/b]" > /sys/devices/virtual/bdi/179:0/read_ahead_kb
fi;
/sbin/busybox mount -o [b]noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue,noatime,nodiratime[/b],nosuid,nodev -t ext4 /dev/block/mmcblk0p2 /data || /sbin/busybox mount -o nosuid,nodev -t rfs /dev/stl13 /data
Enjoy again!
P.S. +10% Performance!
Doc_cheilvenerdi.org said:
Upgrade completed and new boot images uploaded.
Also added S5570JPKS1 to the list!
init.data.sh changed to
Code:
#!/sbin/busybox sh
if /sbin/busybox [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]
then
/sbin/busybox echo "[b]3072[/b]" > /sys/devices/virtual/bdi/179:0/read_ahead_kb
fi;
/sbin/busybox mount -o [b]noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue,noatime,nodiratime[/b],nosuid,nodev -t ext4 /dev/block/mmcblk0p2 /data || /sbin/busybox mount -o nosuid,nodev -t rfs /dev/stl13 /data
Enjoy again!
P.S. +10% Performance!
Click to expand...
Click to collapse
it's a little slowly but working like a charm
you're a life saver
Some apps run very slowly, especially import contacts from SD (file .vcf)!
(My Rom is the GingerBread Europe 2.3.6 PDA=S5570JVKT1)
Nice. Some interesting stuffs are really coming out from our forum I will give these mount option a shot.
I will try to convert /system and /cache to ext2 and leave /data as ext4 as system is mounted as r/o as default and cache can be formatted anytime.
I recommend you not to flash boot image for the ROM 2.3.6 PDA=S5570JVKT1. I've come back the original boot image!
van8x10 said:
I recommend you not to flash boot image for the ROM 2.3.6 PDA=S5570JVKT1. I've come back the original boot image!
Click to expand...
Click to collapse
Why? You must explain reasons ...
denzel09 said:
Why? You must explain reasons ...
Click to expand...
Click to collapse
Simply for me, some apps run very slowly:
- It took me ~1 hour to import contacts from vcf file on SD card
- When I was testing the Expense Manager App, My Phone Shutdown for unknown reason (not reboot), luckily not yet bricked
- I think It is not safe for me, then wait for a new version from Doc!
hey can u pls tell me how to do it?or can u pls do it for samsung galaxy ace?
Beta Testing...
van8x10 said:
Some apps run very slowly, especially import contacts from SD (file .vcf)!
(My Rom is the GingerBread Europe 2.3.6 PDA=S5570JVKT1)
Click to expand...
Click to collapse
How I Test all the boot images before sharing them
When I power on the phone the hardware bootstrap passing soon after the control to the (using PC terminology) BIOS (Basic Input OutPut System)... a sort of mini system used to poweron all the peripherals inside and related to the phone... (In my Galaxy Next - briefly - I find something similar in the code sequence mibib-qcsbl-oemsbl-amss-arm11boot)...
...Immediately after, the BIOS loads into memory the Kernel in a fixed position and an initial ramdisk (in a fixed position too) and leave control to the kernel...
...the kernel setup the ramdisk and use the second mini system inside to complete the boot stage...
...Finally the kernel - using commands in the ramdisk - give control to the real system - GingerBread.
Actually the Bios releases control to the kernel calling a routine starting always from a fixed point hardcoded in itself and the Kernel launch the system (wherever it is) looking in the init files inside the ramdsik...
While slightly upgrading GingerBread from 2.3.0 to 2.3.* the mid part of the full boot sequence (kernel + ramdisk) need only two things to work properly:
Kernel compiled with the first assembly code starting from the fixed position hardcoded in the Bios
init files in the ramdisk showing where the filesystem and its data are...
Finally: All boot.img of GingerBread flavours meet these prerequisites... so I can easily use anyone of them with my system (or any other minor version of Ginger) while my BIOS call the kernel and it is in the right place and the init files exit to the filesystem where it really is...
I simply flash one of the shared boot images and test it three times:
power on with micorSD outside (system boot as usual)
power on with microSD inside and /data empty (the system fill it with all what is needed)
power on with microSD already full of apps, userdata and cache
I check mount points, SD read ahead, browse something on Internet, Market...
...and Finally I feel comfortable with the image cooked...
...I can share It!
Why didn't I said that you can use any of the shared boot images
If I simply call the boot image (for example)
CODE_S5570DOC01_boot.tar.md5
probably several end users (not heavy skilled with Linux, boot, Android, etc...) could be scared to use it...
... so I decided to provide an image for any of the "most wanted versions" now on the network using the attached kernel (anyway slightly different each other) with the same name of the Stock Version...
How I handle Errors reported from end users
van8x10 said:
Simply for me, some apps run very slowly:
- It took me ~1 hour to import contacts from vcf file on SD card
- When I was testing the Expense Manager App, My Phone Shutdown for unknown reason (not reboot), luckily not yet bricked
- I think It is not safe for me, then wait for a new version from Doc!
Click to expand...
Click to collapse
With my Wind boot.image first, and then with the JVTK1 one, I did what follows:
First Test
I exported my contacts to SD twice (about 2 minutes every time)
I imported it four times from SD without overwriting existing ones (about 1 minute to 2 minute at last) growing it to 400 entries
I exported and Imported them again (2 +2 minutes)
Test made with both the boot images - same result
Second Test
I own Titanium Backup PRO so I performed a backup of 98 apps (about 200Mb mixed from /system and from outside /data) to SD (4-5 minutes)
I repeated 3 times forcing the full operation (always about 5 minutes)
I Verified the backups towards original apps (3-4 minutes) (Found 2 errors related to WiFi in both boot images)
I restored 25 apps (this time only the ones stored on the outside /data - left untouched /system); I needed 10-12 minutes to reinstall them while dr web light antivirus was underneath scanning them. (Market crashed once in JKVT1 boot image)
Third Test
Called friends by Phone,
Sent some SMS to them,
Whatsapped them too,
Browsed xda-developers forum with Opera Mobile and Tapatalk.
Fourth Test
Don't do it!
I started "via emulator terminal" to dump a 100Mb wide file copying from /dev/zero...
while writing to SD I removed it crashing the system...
All fine after reboot... but (I'll soon post about what I'm saying) I suggest to use tools like fsck for errors out of journals...
Last Test
I own a Very old SD (1Gb) at the end of its lifecycle...
Every time I use it, bad blocks appear... timing readouts... freezing PC ports where connected...
...so I consider it a very bad hardware...
...but very useful for extreme tests of hardware/software endurance...
I made this test only with JVKT1 anyway...
I prepared the 2 partitions in it on my Linux PC (system froze twice then I was able to write partion table and format them)...
...Power On the phone with SD inside...
...adb shell and ddms connected to follow the de-wipe operation from PC..
...needed 40 minutes to complete it...
...frustrating...
...the System ended up and running anyway...
Conclusions
I think that the problem noticed should be investigated outside the boot stage of Ginger JVKT1 image...
How I cook the boot images
The images to deal with are growing up (just preparing XXKPI) so I prepared a Batch Farm used to do the dirty job avoiding human errors...
...Obviously I check pre and post by Hand...
...Test on My Next...
...Share...
Once the Script will be STANDALONE FUNCTIONALE I'll share it too!
van8x10 said:
...luckily not yet bricked ...
Click to expand...
Click to collapse
No luck needed here...
Studying Brick deep inside, while the Flash operation doesn't touch the first BIOS code (mibib, ecc...), if I don't make mistakes with Tass.ops or images too big I cannot really Brick while flashing...
...obviously I can always kill definitely my system with a wrong root command...
...All situations that I can resolve at last using Odin again...
parasmi said:
Nice. Some interesting stuffs are really coming out from our forum I will give these mount option a shot.
I will try to convert /system and /cache to ext2 and leave /data as ext4 as system is mounted as r/o as default and cache can be formatted anytime.
Click to expand...
Click to collapse
Good Hint! Why do I need to journal a filesystem read only... I think I can deal with it occasionaly while readwriting something to it anyway!
THANKS!
when i want to use my phone on start up: keep rebooting many times and after that it works
any idea DOC?

[MOD] EXT4All Continued + Now with TWRP 2.3 Support

The purpose of this thread is to host a location and continue support for a really neat ext4 mod.
IMPORTANT: If you flash the no data limit mod you need to do it after every update or your data, which won't be lost will be hidden by the contents of the data data partition.
I'm going to keep this brief. The original thread was closed so I wanted to have a new location where everyone can find the files. But this is a new thread for Jermaine151's and my EXT4all mod.
Below is the original thread which already has a lot of useful information:
http://forum.xda-developers.com/showthread.php?t=1315372
Here is where you can find most of if not all the EXT4All files:
http://dinc.does-it.net/EXT4_Mods/
Sorry this thread isn't too organized but I threw one together so people could post on it with their comments.
This mod should work on all AOSP ROMs including ICS ROMs and MIUI. It's been confirmed on CM7 and MIUI but I've also tested on CM9. It should also work on all Sense ROMs and does work on every Sense ROM I've tested. Be sure to flash a newer version of the gingertiny kernel if you use a Sense ROM as the kernel version flashed to add ext4 compatibility is out of date.
V2 Mods with TWRP 2.3+ support and proper support for filesystem tweaks for ROMs that are already set to use ext4 found below:
V2 EXT4All Mods
FAQ
Q. How do I know if the ext4 mod(s) worked?
A. The best way is to do the following from terminal:
su
mount | grep /data
It should show a line with /data and ext4 and, if it has the no data limit, also a line with /data/data and ext4. If you're on an ICS/JB ROM it will show ext4 anyways. The best way to tell with the new version of the mod is to see if noauto_da_alloc shows in the results of the above commands.
Hey tiny, thanks for opening this btw. Wasn't sure if I should post here or on ur kernal thread but my girls dinc was having the data limit problem so I wiped cache and dalvic, flashed ext4 no data limit normal dalvic then flashed ur newest kernal (3/11 date). And I have been having the hardest time keeping her phone stable. I've tried every governor sav2, interactivex, ondemand, even sa, tried deadline, sio schedulers, even tried raising the voltages to a post u had on ur kernal thread, page 85 or something (wasn't sure if I should set the min and max of the voltages for the same thing, but that's wat I did). But she still says its very unstable. She's running stock+ 3.01 and she DOES have a cheap ebay battery in her phone, not quite sure how much that plays a role in the problem. She's at work right now so I can't pull any logs, but I know ull probably need a logcat? Or I dunno. If u could gimme directions on anything I should post to assist u. And I'm not overclocking at all for the record. On stock kernal she never had any stability issues, uptime of 200 hours+. But urs is definitely snappier and that damned data limit is the main reason y I even switched her over to begin with. Thanks tiny in advanced for everything u do!!!
Sent from my ADR6400L using xda premium
I'd prefer the kernel thread.
And I'll need a last_kmsg. Just copy /proc/last_kmsg with root explorer or another file explorer and attach it to a post on the kernel thread. Since you most likely eliminated undervolting by using the voltages on page 85 of the kernel thread, then it's possible the battery has an effect. I've heard that poorly made batteries can cause issues that stock batteries don't have so further deviation from stock may have an influence. Either way, I'll look at that log once you get it. Make sure not to battery pull until you can copy that log and try to do it within 24 hours of the last reboot to be safe.
the following thread contains very simple and plain english directions for using this MOD. it helped me, and it was my first time rooting. Thanks also to tiny4579 for posting this new thread.
http://forum.xda-developers.com/showthread.php?t=1488351
Question about this mod, I am running CM7.2, RC2, and onto rc3 soon.
I am having random resets, problems w/ my phone freezing, a mysterious message "sorry, process system is not responding", and other various issues. Could it be that the mod is causing some problems for my phone, or more about something that wasn't cleaned out when i flashed over a nightly?
funkpod said:
Question about this mod, I am running CM7.2, RC2, and onto rc3 soon.
I am having random resets, problems w/ my phone freezing, a mysterious message "sorry, process system is not responding", and other various issues. Could it be that the mod is causing some problems for my phone, or more about something that wasn't cleaned out when i flashed over a nightly?
Click to expand...
Click to collapse
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
I've been running various ICS roms and switched back to Warm rev 58. Upon installing the latest kernel and the Ext4 mod. I am unable to install apps. Any idea what may be causing this. I wasn't sure if it was the rom or not do I did an update with SVN and installed that with the same results. I have a nandroid with just the rom and all the apps I want, but would like to overclock and the stock kernel won't allow. And would also like to be able to install a new app should one arise.
Sent from my HTC Droid Incredible using xda premium
tiny4579 said:
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks, how do I generate the logcat?
Sent from my Incredible.
Aw yeah.
Ok. It's not the kernel. Installed the most recent and everything is fine. Installed the ext4 with dalvik moved before that and rebooted and apps were missing and it wouldn't let me install new apps and some of my previously installed apps were missing. When I tried to install them it said it was going to replace an existing app and then said app not installed.
Any ideas???
Sent from my HTC Droid Incredible using xda premium
tiny4579 said:
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
also, i can't see the file /proc/last_kmsg
i see /proc , and i see "kmsg" but i don't see "last_kmsg"
is that the same thing?
and for some reason, the android sdk doesn't work now, that i have uninstalled and reinstalled it...
funkpod said:
also, i can't see the file /proc/last_kmsg
i see /proc , and i see "kmsg" but i don't see "last_kmsg"
is that the same thing?
and for some reason, the android sdk doesn't work now, that i have uninstalled and reinstalled it...
Click to expand...
Click to collapse
Sorry I just dont have time tonight to explain. Maybe tomorrow.
Sent from my Galaxy Nexus using Tapatalk 2
hELLO!
I HAVE A LOGCAT!
and it captures 2 errors.
First, it captures the "sorry, system process not responding" error, and then it captures this weird thing where it restarts. it doesn't go all the way back to the "htc incredible" screen, however, it goes to the cyanogenmod animation, starts up, and THEN goes right back to the cyanogenmod animation, again!
finally, i shut it off, cuz i didn't know how to get the logcat to stop in ddms.
and i have the /proc/last_kmsg... how do i get it to you?
i added a .txt to the end of it so i could upload it, hope that works. is that what you need?
funkpod said:
hELLO!
I HAVE A LOGCAT!
and it captures 2 errors.
First, it captures the "sorry, system process not responding" error, and then it captures this weird thing where it restarts. it doesn't go all the way back to the "htc incredible" screen, however, it goes to the cyanogenmod animation, starts up, and THEN goes right back to the cyanogenmod animation, again!
finally, i shut it off, cuz i didn't know how to get the logcat to stop in ddms.
and i have the /proc/last_kmsg... how do i get it to you?
i added a .txt to the end of it so i could upload it, hope that works. is that what you need?
Click to expand...
Click to collapse
Try fix uids in amon ra recovery. Amon ra should be listed in from manager. I don't think it's the same as fix permissions in cwm which I believe there is file system based. From looking at your logcat there are a lot of unknown permission errors. Let me know. I'm at work so didn't have a lot of time to respond but wanted to check briefly.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
Try fix uids in amon ra recovery. Amon ra should be listed in from manager. I don't think it's the same as fix permissions in cwm which I believe there is file system based. From looking at your logcat there are a lot of unknown permission errors. Let me know. I'm at work so didn't have a lot of time to respond but wanted to check briefly.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
hey, thanks for looking at it. what do you do for work, that you are working during a holiday?
so, you think i should try fixing user id's in amon ra recovery.
and it should be listed in ROM manager, right?
Now, here's the question, if i'm going to be trying the new RC3 in CM7, and this time i am going to do a clean install, erasing everything. would i still need to fix permissions?
or maybe i should try flashing over RC2 and then fixing permissions?
funkpod said:
hey, thanks for looking at it. what do you do for work, that you are working during a holiday?
so, you think i should try fixing user id's in amon ra recovery.
and it should be listed in ROM manager, right?
Now, here's the question, if i'm going to be trying the new RC3 in CM7, and this time i am going to do a clean install, erasing everything. would i still need to fix permissions?
or maybe i should try flashing over RC2 and then fixing permissions?
Click to expand...
Click to collapse
Always worth a shot.. If you have the spare time try to flash over and fix permissions as 2nd~to-last thing you do before rebooting, ext mod should be last. Same with if you do a clean wipe to flash RC3 if flash over does not help.
I've personally never had an issue after a clean wipe with permissions, but it would not hurt if you did it anyway. It has been recommended when flash over though as a standard procedure. But only recommended
Sirknifealot said:
Always worth a shot.. If you have the spare time try to flash over and fix permissions as 2nd~to-last thing you do before rebooting, ext mod should be last. Same with if you do a clean wipe to flash RC3 if flash over does not help.
I've personally never had an issue after a clean wipe with permissions, but it would not hurt if you did it anyway. It has been recommended when flash over though as a standard procedure. But only recommended
Click to expand...
Click to collapse
okay, so when flashing rc3, make sure i fix permissions right before the last step, and then flash ext4all mod LAST on the list?
funkpod said:
okay, so when flashing rc3, make sure i fix permissions right before the last step, and then flash ext4all mod LAST on the list?
Click to expand...
Click to collapse
If you're wiping I don't see the point of fix permissions as it will fix it back to what it already probably is. I haven't fixed permissions in a while flashing ROMs and I've been ok. Force closes that I got that made me try fix permissions then weren't fixable with fix permissions anyway.
I would wipe, flash ROM, flash kernel if desired, then mod. Though if it's a sense ROM I would switch the order of kernel and mod flashing. So really you can do: ROM, ext4all mod, kernel after a wipe if you choose to wipe to fix your issue.
hey, flashed over to RC3! so far so good, slowly adding things back! will let everyone know how it goes!
Is there a possibility that all or part of this mod could be persistent over multiple wipings?
My reasoning for this question: I originally flashed the 1.0 normal mod on Nils' BGS. In the OP it says it converts the filesystem to ext4. Many moons later, and now on drk's CM9, terminal still lists cache and data as ext4. I did not, however, flash an ext4 mod on any versions of ICS. I know that when I do a factory reset, even though all is formatted, my sd-ext remains ext4, since I set it up that way for Link2sd. Is it possible that the data and cache blocks have also remained ext4 from the original use of this mod, despite wiping and formatting repeatedly?
...sorry...I was on the phone...
omniatic said:
Is there a possibility that all or part of this mod could be persistent over multiple wipings?
My reasoning for this question: I originally flashed the 1.0 normal mod on Nils' BGS. In the OP it says it converts the filesystem to ext4. Many moons later, and now on drk's CM9, terminal still lists cache and data as ext4. I did not, however, flash an ext4 mod on any versions of ICS. I know that when I do a factory reset, even though all is formatted, my sd-ext remains ext4, since I set it up that way for Link2sd. Is it possible that the data and cache blocks have also remained ext4 from the original use of this mod, despite wiping and formatting repeatedly?
...sorry...I was on the phone...
Click to expand...
Click to collapse
No, if you actually format the device like when the system runs the format command the filesystem will be ext4. However in your example of CM9 the ramdisk mounts data and cache as ext4. This will actually have a minor improvement over ext3. It'd still be an ext3 filesystem but loaded as ext4 so there's minimal performance gains.
In reality any time you flash a ROM or a boot.img type kernel (not any of mine) you will use the ramdisk of the ROM and reverse part of the effects. But since ROMs like CM9 and newer CM7 versions mount as ext4 you'll still see data and cache showing as ext4. Make sense? I never really did explain it properly before I think.

[Q] Boot hangs / partitioning problems while reflashing from CM9.1.0-p1 to CM10.1

I have severe problems when reflashing my Galaxy Tab GT-P1000 (via recovery) to CM 10.1 nightly. Before that, I ran 9.1.0-p1 for quite a while.
What I do:
Reboot to recovery (CWM-based Recovery v6.0.1.2)
wipe data/factory reset
wipe cache partition
install zip from sdcard, e.g. cm-10.1-20130504-EXPERIMENTAL-p1-cdesai.zip
It tells me: "This ROM uses an incompatible partition layout. Your /data will be wiped upon installation. Run this update.zip again to confirm install" and "assert failed: run_program("/tmp/updater.sh") == 0".
I re-run the zip as told.
It reboots to a seemingly updated CWM-based Recovery v6.0.3.2
And now, all kinds of errors occur. First time I tried, flashing seemingly went through (despite showing some ot the CWM error messages mentioned below). After rebooting, I ended up with a weird looking CM10 bootup animation (didn't fit to screen) animating forever with no further (visible) progress. I waited for more than 10 minutes and tried re-booting several times, but it hung there forever. I couldn't connect via adb.
After some tries, the error has changed. Now it won't come to starting CM10 at all, but CWM ends up in a loop saying "Root access is missing. Root device?". If I choose "Yes", it reboots to end up in the same question over and over again.
I tried a lot of nightlies, all showing a varying selection of the errors described above and none leading to a somehow booting CM10.1. I tried some of the official nightlies from get.cm (e.g. cm-10.1-20130515-NIGHTLY-p1.zip), cm-10.1-20130504-EXPERIMENTAL-p1-cdesai.zip from goo.im/devs/cdesai/cm as well as the OpenPDroid taste announced by alroger (cm-10.1-20130514-UNOFFICIAL-p1.zip).
They all seem to use the same new CWM, which gives me collection of error messages, all seemingly connected to partitioning:
Usually, I see a varying number of erros in /cache/recovery, e.g. that it can't mount and/or open /cache/recovery/command, as well as .../log, .../last_log and .../last_install and that it can't open the same files.
Sometimes, I see "E:unknown volume for path []. E: Can't mount"
Sometimes, when trying to wipe, I get informed that make_extf4fs failed on mmcblk0p3
Normally, I'd say that I'm either making a fundamental error in the process or my hardware is somehow badly broken. BUT what puzzles me is that I can go back to CM 9.1 at any time and flash it as often as I want - it always works and CM9 is starting up correctly.
So, I more suspect that my partitioning is somehow setup in a way that CWM v6.0.3.2 or the setup scripts from update.zip can't handle cleanly.
Any suggestions / ideas? Please let me know if there are any logs which could help in narrowing things down! I should be able to operate a Linux shell, so don't hesitate to suggest things I could try manually. (I can certainly access "adb shell" in the recovery - but please note that I didn't manage to connect with adb during the CM10 boot hang, so I can't provide logcat from that state, sorry...)
HTML:
[media=youtube]JmvCpR45LKA[/media]
:thumbup::thumbup:
And restock..
I recommend overcome method..
Search for it..or wait for priyana come here and post "click at my signature"
Then press the thanks button..
When you on stock..
Install the overcome kernal..
Flash cm10..3x
First..to get cwm..
Second..to change partition layout..
Third..to install cm10..
Then flash the gapss..
Reboot..
-----------------------------------
(҂`☐´)︻╦̵̵̿╤── .:System:.
-----------------------------------
No interest in solving the problem in CM10?
mike_disturbed said:
And restock..
I recommend overcome method..
Search for it..or wait for priyana come here and post "click at my signature"
Then press the thanks button..
Click to expand...
Click to collapse
Wow, first of all thx for the rapid answer! And thank you for the hint, I can certainly try that.
However, my initial intention was not only to have the problem solved for my tablet but I tried hard to do a qualified bugreport so that the situation can be correctly handled in the cm10.1 nightlies. I at least assume that an update from a clean CM 9.1 to CM10.1 should be a supported update path, no? As said, I returned to a clean CM 9.1 several times and re-tried the update from there.
So I assumed that the CM10 developers would be interested in my feedback and analyzing the error. Unfortunately, however, I'm not allowed to post that to the right thread yet, so I chose the Q&A channel.
If you don't think the developers are interested in the bug report, just let me know and I'll happily try your suggestion. Otherwise, I'd refrain from it now to not disturb the test case yet...
yoda_la said:
Wow, first of all thx for the rapid answer! And thank you for the hint, I can certainly try that.
However, my initial intention was not only to have the problem solved for my tablet but I tried hard to do a qualified bugreport so that the situation can be correctly handled in the cm10.1 nightlies. I at least assume that an update from a clean CM 9.1 to CM10.1 should be a supported update path, no? As said, I returned to a clean CM 9.1 several times and re-tried the update from there.
So I assumed that the CM10 developers would be interested in my feedback and analyzing the error. Unfortunately, however, I'm not allowed to post that to the right thread yet, so I chose the Q&A channel.
If you don't think the developers are interested in the bug report, just let me know and I'll happily try your suggestion. Otherwise, I'd refrain from it now to not disturb the test case yet...
Click to expand...
Click to collapse
I'm not really sure about this..but cm9, cm9.1 and cm10 , cm10.1..
They have different partition layout..and the rom zip..can change partition layout from gb to cm layout..something about mtd layout or something..lol
I'm not quite sure myself since i still using gb base rom..
Just help in general and q&a..then you can post at dev section..that's the rule..and it apply to everyone..even the dev..
Yeah the dev would definitely interested with that..but..i think that cm10 is been here long enough..and someone would likely brings that up already..but if you still think that it worth a shot..try pm'ing the dev..may take a while for the reply..but I'm sure the dev would love to get some helping hand..or just complete the 10 post..you have done 2 post here already..8 more to go..
-----------------------------------
(҂`☐´)︻╦̵̵̿╤── .:System:.
-----------------------------------
Only cm Rom from last year April onwards use new partition scheme.
If yours was old one, better restock.
Like mike said, check my signature.
Sent from my GT-N7100 using xda app-developers app
mike_disturbed said:
:
:
Flash cm10..3x
First..to get cwm..
Second..to change partition layout..
Third..to install cm10..
Then flash the gapss..
Reboot..
:
:
Click to expand...
Click to collapse
What can I say... that is totally f****** but damn it... it flamin' well works! I can't even guess how you came up with that sequence but THANK YOU! This has been driving me nuts.
Stil no luck...
Ok, tried all that several times, but it still doesn't work. "Restocking" is great as it brought back my /efs partition which has somehow been damaged during my first update tries, so thank you again!
However, my tab still won't boot with CM10, even after "restocking" successfully two times and trying different CM10 nightlies (the current cm-10.1-20130604-NIGHTLY-p1.zip as well as cm-10.1-20130504-EXPERIMENTAL-p1-cdesai.zip as I found specific success reports for that one on the forum). I also tried flashing CM10 3 times in a row as you told.
I always end up with a boot hang and the weird distorted boot animation shown forever. In recovery, I still see errors when accessing the
/cache partition. I've no idea whether this is the root cause of my boot hangs or if this is expected behaviour in CM10 nightlies, but when I try to wipe cache, I get:
Code:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p3
I also checked with "adb shell" in /proc/partitions and found that there's simply no mmcblk0p3 found by the kernel:
Code:
-> reboot to recovery
$ adb shell
~ # cat /proc/partitions
major minor #blocks name
31 0 7680 mtdblock0
31 1 7680 mtdblock1
31 2 443904 mtdblock2
31 3 22528 mtdblock3
31 4 12800 mtdblock4
31 5 11264 mtdblock5
179 0 15552512 mmcblk0
179 1 13586400 mmcblk0p1
179 2 1966080 mmcblk0p2
179 16 1024 mmcblk0boot1
179 8 1024 mmcblk0boot0
179 24 15339520 mmcblk1
179 25 15335424 mmcblk1p1
dmesg show no suspicious entries during mmc detection, it looks like mmcblk0 simply only has two partitions. So can someone tell whether I should have a mmcblk0p3 partition or if my fstab is somehow broken? Any idea how to narrow this down further?
yoda_la said:
Ok, tried all that several times, but it still doesn't work. "Restocking" is great as it brought back my /efs partition which has somehow been damaged during my first update tries, so thank you again!
Click to expand...
Click to collapse
How are you restocking? I used the Overcome method and files, going back to GB Stock Safe V5. Then I put the Overcome kernel 4.0.0 on, finally doing the CM10.1 x 3 and GApps.

[ROM][ULB] CM-13.0 for Xperia T Beta

Hello and welcome to CM-13.0 Beta 1 !
first of all a BIG thank you to @Adrian DC wich had constributed also to this rom (he fixed the camera and helped me with the other stuffs )
Known bugs:
- sometimes the device will bootloop (only in starting phase )
USE THE FLASHABLE HOTFIX for that
- sometimes RIL may not start (on bootup)
if you encounter one of these bugs please press and hold vol+ and powerbutton to FORCE SHUTDOWN and then reboot again
Other "bug":
- selinux disabled until i patched it
Sourcecode can be found on my git:
github.com/sdtbarbarossa
How to install:
1. make sure your internal SDCard is formated to exfat (you can use Whiteneos TWRP to get that)
2. clean install the rom ( wipe cache & data & system ) [alternativeley dirtyflash.... but then dont report bugs!]
3. flash gapps (i use OPENGAPPS - ARM - 6.0 - PICO )
4. reboot
5. wait several times
Downloadlink:
https://www.dropbox.com/s/7tr42vcejk1u1js/cm-13.0-20160403-UNOFFICIAL-mint.zip?dl=0
link is up
Sent from my Xperia T using XDA Free mobile app
error executing updater binary in zip
SonyXperiakiasT said:
error executing updater binary in zip
Click to expand...
Click to collapse
Code:
ApplyParsedPerms: lsetfilecon of /system/lost+found to u:object_r:system_file:s0 failed: Operation not supported on transport endpoint
?
Got that myself, it doesn't work with TWRP 3, you need an older version, i used TWRP 2.8.6.0
(fix) flash it with philz_touch_6.12.8
Q: how do you install supersu? It doen't work from google apps and I tried to flash it from TWRP and I got a bootloop
For me installation works with TWRP from 12.1 kernel. After creation of dalvik files it never ended with "apps are starting". Killed the device (Vol+ & Power) and got never ending boot animation... tried to reinstall. Now got "Operation not supported on transport endpoint". Restored "boot" from last 12.1 nand backup, rebooted to (that funny colored) revovery, wiped again, reinstalled (BTW open_gapps-arm-6.0-pico-20160403 in queue) and now..... hey, I get a PIN screen! Wifi & Google sign in works without problem. Developer options, root access, adb shell, seems alright for now - good night and many thanks to SdtBarbarossa!
vladut.alecsandru said:
Q: how do you install supersu? It doen't work from google apps and I tried to flash it from TWRP and I got a bootloop
Click to expand...
Click to collapse
From Xperia M I know it's very tricky or nearly impossible... For me the "onboard solution" for root access is okay. (did not try yet if it really works...)
Actually you are right, I didn't enable the root access from developer options the first time.. but it works and you don't need supersu
But I had no service and after a reboot it started to bootloop again..
bootloop after a reboot
Reinstalled again.. and after each app install I rebooted to see what might cause the bootloop
For me at least, it started to bootloop after I installed and gave root access to titanium backup.
1. the bootloop is a known bug lile i said ( it is that the mediaserver dont start for a unknown reason... depending on the random queue of loading librarys )
atm i prefere everyone to reboot not often x)
bootloops should be solvable by hardboot ( vol+ and powerbutton )
then there are 2 cases:
1.lib a gets loaded before lib b => it boots
2.lib b gets loaded before lib a => it loops
there is nothing how i can controll that atm
2. if you habe trouble flashing the rom please send me a log
3. guys can it be that the no service bug only appears on first boot?
Sent from my Xperia T using XDA Free mobile app
Here's an example logcat for a boot-loop. All boot loops I got were ending with that "Waiting for service media.audio_policy..."
BTW In my case has nothing to do with Titanium Backup, it seems to be random
I'll probably test the rom today. Keep up the good work SdtBarbarossa.
mankokoma said:
Here's an example logcat for a boot-loop. All boot loops I got were ending with that "Waiting for service media.audio_policy..."
BTW In my case has nothing to do with Titanium Backup, it seems to be random
Click to expand...
Click to collapse
yes i know... thx for the log its the same i get... this bug is just as random as i explained above... hard to find the real reason
so except for the bootup problems ... how is the rom? any other problems?
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
... how is the rom? any other problems?
Click to expand...
Click to collapse
First impression's really good. Much snappier than 12.1 - expected. It was a little tricky to change the 'sdcard0' to vfat. As suggested I tried to do it with the 12.1-kernel-TWRP... first did a backup to ext-sd but after copying with TWRP-filemanager it crashed, automatically rebooted the 13-ROM, killed the dalvik and boot-looped At least sdcard0 data were transfered!
So restored kernel & data from nand backup and after successful boot, tried to format sdcard0, mentioned "corrupt" in settings-Storage&USB but ERROR occurred. So I tried with adb shell
Code:
newfs_msdos -F 32 /dev/block/mmcblk0p15
OR
Code:
mkfs.exfat /dev/block/mmcblk0p15
BOTH returned Errors (that's why I tried both) but can't remember which one was successful
In settings-Storage&USB still "corrupt", but after reboot (without problems) there was sdcard0 with 11 GB free - yeaaaah!
Pushed back all the Osmand Map Stuff and so on and now also
Camera does not complain any longer because of missing sdcard and takes photos.
GPS fix is fast and stable... That's all for now!
Ahh and yes, I can do phone calls & sms (aber das ist ja nebensächlich)
hi!
so tried last cm13 beta, thanks for your work first of all.
had same problems as @mankokoma trying to format the sdcard to vfat via WhiteNeos latest twrp (same problem I reported multiple times in the old thread if you remember), it simply does not work, sdcard stays in ext4.
then I did run the commands mankokoma suggested in adb and then I could see vfat for sdcard in twrp. but now in twrp sdcard is not accessible at all. it doesn't mount etc had to use usb otg to install cm13. and in twrp 3.0 provided with cm13, again sdcard is not accessible at all ;(
btw, I full wiped (system, cache, data and dalvik), and thanks to otg I installed cm13 beta. upon very first reboot, phone optimized all apps, but then got stuck at "Android is starting - Starting apps message" forever. I had to force shutdown and reboot, then it booted fine and could pass the wizard.
sim was detected fine.
but I see internal sdcard always damaged in settings. rebooted countless times, didn't fix the problem. and camera app FCs, probably because I don't have any sdcards available...
If I click on the sdcard damaged, and then configure and format, I get an error message, and it doesn't work.
so the rom is still not usable for me atm very sad because the rom seems very promising and so fast!
EDIT: settings do FC here when trying to enter developer settings so can't enable builtin root?!
seems that your issues are all because of the sdcard not formated to exfat... you can "revive" it by formatting to ext4 but then you can only use it in twrp... try again to format it to exfat
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
seems that your issues are all because of the sdcard not formated to exfat... you can "revive" it by formatting to ext4 but then you can only use it in twrp... try again to format it to exfat
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
yes but how?? please tell me how to do that... in twrp 3.0 it keeps giving errors...
and by the way in twrp I see file system for sdcard is already vfat now! :silly:
nvm! trying again and again in twrp I always got error messages but now in settings it seems it is recognized! great! and camera started to work now will test it wonderful!
ps: FC in developer settings is still there... how did you get root? with supersu?
EDIT: and recording videos does not seem to work?
hi
tnx for rom is very good
but in my device internal stroge is not work and im format it but this not work
please help me
hamidmf12 said:
hi
tnx for rom is very good
but in my device internal stroge is not work and im format it but this not work
please help me
Click to expand...
Click to collapse
Try this, it worked for me :
http://forum.xda-developers.com/showpost.php?p=65265674&postcount=10

Categories

Resources