yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] wassk:
Hey guyz i wanna know something.. Coz i never format my sd card or internal memory..but i see when im flashing new rom and doing full wipe through recovery that it says wiping system/data using extfat4 or something... I forgat what it says...but i wonder then what kind of format is using my phone...coz i see now u talk alot about fat32,extfat and so on...sorry if i write it wrong coz im using my phone atm and i have just 3% of battery left so no time to read it again...hope u understand what im asking...thnx...
[Galaxy S II Android Development] j1gga84:
Could be possible..

Can I do a nandroid backup, fix partitions in STweaks and play the backup back or do I also play the corrupted partitions back?

Regards

Sent from my GT-I9100 using german Tapatalk 4
[Galaxy S II Android Development] Computoncio:
When you restore a nandroid you are restoring a partition, so errors are restored too.

The only way is to use titanium backup or similar app that only restores files.

When you flash a rom it only formats system in ext4, data partition is never touch.

What I'm talking is about sdcard0, internal sdcard file system type, the default is vfat but we can use others. But stay with vfat till we fix all the issues.

Phone: Samsung Galaxy SII - GT-I9100

Kernel: Dorimanx kernel v10.43v105-mv3

1st ROM : SlimSaber 4.4.2 Maliv3 by fusionjack build of 20140412 (Online)

2nd ROM :

MODEM: UHMS1

MODS: Partition Fix, Hue Blue v4.4 by Kroz :good:
[Galaxy S II Android Development] Troubadour666:
hi, i went to flash 107 , branch 8.

see images in attachement, named with order of boot after flash.

i clean browser 1rst rom, active stweacks tip recomended on 1rst rom and reboot, after new optimizing process after boot, i have same screen in browser auto opened like in 2ndBOOT-1rstROM-4.1.2.png image.

EDIT1

i reboot , this time 2nd rom and have 3rdBOOT-2ndROM-4.4.2.png check .

i fix stweaks on 2nd rom and reboot it and i have.......similar image than 3rdBOOT-2ndROM-4.4.2.png.
[Galaxy S II Android Development] nuraniharun:
+1

But 8.43fs4 doesnt give partition error in browser.

I think 8.43fs5....8.43v107 maybe broken for checking partition and it is corrupting device's partitions.

Because I fixed with odin (Pit file) and partition fix scripts then I flashed 8.43107, 106,... Unfortunately partitions error in browser.

Please fix this bug.
[Galaxy S II Android Development] j1gga84:
Hi [MENTION=4663860]Computoncio[/MENTION]

I can do what I want but I did not get v107 to run :(

I flashed v105, after that v106 and it booted without a problem, now I also flashed v107 over 106 but it stucks at bootlogo. I also wiped cache, dalvik and deleted the stweak settings in CWM recovery but still the same. When I flash v106 SlimSaber boots without a problem and bootlogo dissapears after a short time. I know that I have errors on my EFS partition (STweak says it) but I never had problems with this fact!

So what changed between v106 and 107 ?

I will install next SlimSaber version on a clean system and try to repair partitions before doing this but I think that will not help..

btw. in STweaks the check partitions button does not show values anymore.

regards
[Galaxy S II Android Development] TheImpossibleEnemy:
Had this too.Now it's working again.Atleast here on my setup.

Something is wrong with the partition errors detect(that browser thingy)IMHO.Did that file system fix in stweaks,also formatted system and data partitions in cwm.And still,even while in stweaks partitions status shows that everything is clean,I'm getting this partition error message in browser that doesn't show any particular or obvious problem(with many "xxxxxx..." where numbers should be,I believe),but at the end it says that fix is recommended.

Other than that,v107 runs without a single problem.

A million thanks!
[Galaxy S II Android Development] Computoncio:
The browser is only showing the log of the partition that is corrupt. Maybe dorimanx was right, he just fixes it on boot if it detects that the partition is corrupt.

The difference from v106 to v107 is the upgrade of the recovery and i fixed the browser opening without showing the log of the partition that was corrupt. That issue was my fault, i was pointing to the wrong file:( now it works as should.

If you check "auto fix in every boot" in stweaks in the other tab it will work as the old way and browser will not show up no more.

If the majority of users decide that showing the browser is annoying, just use the option stweaks. If you want i can rebove the browser, but you will have to look in / and check manually the logs.

As you can see as always, you have a choice. Just choose to be informed and manually fix the partitions , or it can fix automatically for you and you will not be disturbed by the browser think ;)

I have data partition corruption too, it a force reboot or if phones freezes it causes corruption, this way you can backup with TB, fix partitions, and restore with TB, if data ot any app disappears becauseyit was damage.

As you can see users always have a choice ;)

Phone: Samsung Galaxy SII - GT-I9100

Kernel: Dorimanx kernel v10.43v105-mv3

1st ROM : SlimSaber 4.4.2 Maliv3 by fusionjack build of 20140412 (Online)

2nd ROM :

MODEM: UHMS1

MODS: Partition Fix, Hue Blue v4.4 by Kroz :good:

---------- Post added at 08:08 AM ---------- Previous post was at 07:48 AM ----------

As you can see all tha images you have errors, that way the browser has open.

I don't know why the partitions gets corrupt as they do, i always had that issue, that why i implement the fix in every boot.

I have used only cm kernel from slimsaber and the same result, corruption in data partition, thr same goes to all roms i have used. Maybe that a feature of using custom roms :p but know we can fix it manually or automatically to prevent issues.

Since i activate the auto fix in every boot i dont have hot reboots or freezes. My phone is stable as a rock.

Phone: Samsung Galaxy SII - GT-I9100

Kernel: Dorimanx kernel v10.43v105-mv3

1st ROM : SlimSaber 4.4.2 Maliv3 by fusionjack build of 20140412 (Online)

2nd ROM :

MODEM: UHMS1

MODS: Partition Fix, Hue Blue v4.4 by Kroz :good:
[Galaxy S II Android Development] TheImpossibleEnemy:
Hmm...browser opens even if "check and repair file system on every boot" is turned on.Cron service is on and online if this matters.

v107 of course.

edit:

this wouldn't bother me much,but partition status button in stweaks shows that everything is clean and that's why it's somehow confusing to me.
[Galaxy S II Android Development] m1trand1r:
Hum.....10.43v107 by mate [MENTION=4663860]Computoncio[/MENTION] is working w/o issues or such here....I didn't even bother opening Stweaks as my profile is very nicely balanced.....and no....no browser popup window on my side.....so my partitions are clean I guess....[emoji106][emoji106][emoji106][emoji56][emoji56]

Good work devs...thank you for all your efforts.. [MENTION=5074262]StanTRC[/MENTION] [MENTION=4663860]Computoncio[/MENTION] , [MENTION=2376110]dorimanx[/MENTION] , [MENTION=1670821]cybernetus[/MENTION] ......Rock on....[emoji122][emoji122][emoji122]i'm trying to follow as much as I can [emoji12][emoji56][emoji56][emoji122][emoji122][emoji122]

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] Computoncio:
I know why browser shows up after cleaning the partitions, that's because i forgot to reset the flag :angel: my fault, on the next reboot it shouldn't open.

It's fixed, on the next version it will work ok, i hope :p
[Galaxy S II Android Development] j1gga84:
[MENTION=4663860]Computoncio[/MENTION]

Please have a look at the attached screenshots.

What does that mean for me? Errors in Partition or not? log-errors.html shows nothing as you can see and in STweaks I get no values :confused:

From previous Dorimanx betas I know that EFS Partition was not clean so how will I get EFS Partition clean? By pressing FIX DATA ON or OFF in other tab in STweaks and backup my apps with TB before doing this?

I also had another SoD. Could not turn screen on after it went of, log also in attachment

Something must be faulty because v107 does not boot on my side.

Regards
[Galaxy S II Android Development] pSyCh¤_O_O:
Hey guys

Log only shows on stock browser?

Just flashed 10.43v107 on Spirit ROM and it booted really fast so i guess my partitions are clean. Just checked to clean partitions from stweaks just in case... Stweaks says my partitions are clean apart from EFS as usuall.

OT:

Sorry for being a bit lost. A lot of work latelly...and my GF is on holidays so i have to spend time with her. Little time to test atm. Still following daily and flashing new releases though. If you dont see me posting its because everything is fine on my side.

Thanks team [emoji6]
[Galaxy S II Android Development] Computoncio:
I will see if i can release v108 today with the browser issue resolved.

[MENTION=5074262]StanTRC[/MENTION] recovery don't show status 7 when flashing zips anymore , great job mate [emoji106]

I will see this weekend if exfat issue is solved by the recovery update or not.

Phone: Samsung Galaxy SII - GT-I9100

Kernel: Dorimanx kernel v10.43v107-mv3

1st ROM : SlimSaber 4.4.2 Maliv3 by fusionjack build of 20140412 (Online)

2nd ROM :

MODEM: UHMS1

MODS: Partition Fix, Hue Blue v4.4 by Kroz :good:
[Galaxy S II Android Development] Troubadour666:
108 ? great :)

sometimes, not all times and depends of 8.43vXX i used, again with 107 now i have this little bug, when i flash an aroma cwm tool in 2nd rom to manage some stuff in rom and when i reboot, i have to boot 1rst rom at 1rst time. if not, 2nd rom never boot, i have just a normal reboot and then again choice of rom to boot . is there a flag somewhere to remove or not ?

thanks
[Galaxy S II Android Development] jgcaap:
Going to test kernel on weekend :)
[Galaxy S II Android Development] mitsos89:
I had exactly the same issue, no values in STweaks Check Partition.

I flashed the Fix_Partitions_v1.0.2.zip from Computoncio and it showed that I needed to fix them.

See Computoncio's Post for more help, its from his signature....
[Galaxy S II Android Development] Jgjd691995:
Could some help me compile the latest dorimanx kernel with a cpu throttle temp of 85°C I have made a custom heatsinkfor the phone and it is in place and working but having the throttle at 71°C doesn't work its just too low a temp for the foil to absorb the heat, according to tests it should reach a stable temp at ~~79°C if anyone could help me do this or even show me how it would be awesome since I guess its not possible to open the zip without destroying it.
[Galaxy S II Android Development] stylemessiah:
Are you mad?

Why would you want the phone to run hotter? and increase its chances of failing terminally?

Thought id heard everything, but a custom heatsink for a phone

Maybe its time to unsubscribe... :)
[Galaxy S II Android Development] pSyCh¤_O_O:
Haha...cool proyect...are you going to cook some eggs for breakfast?lol

Any pictures?
[Galaxy S II Android Development] Jgjd691995:
As the temperature increases the rate of emmition = rate of production that leads to a stable temp. And idk I've been on this thread **with the kernel** for a long time now **since before 5.50 I think** so I really don't think unsubbing is an option, also the performance drop form 1.6 to 0.8 is like half leading to a lot of lag, and um I've been using the phone for years so I'm really used to the heat

---------- Post added at 09:31 AM ---------- Previous post was at 09:25 AM ----------

Hmmmm pics r hard bro I have a 3300mah battery so to unwire that and to remove the heatsink is a prob
[Galaxy S II Android Development] stylemessiah:
I meant maybe its time for me to unsubscribe.....

How is purposely stressing your phone and increasing it temperature above what the individual components are rated for a good thing?

My phone has NO lag or heat, and its underclocked by a large amount for crying out loud...on a stock Samsung ROM....so maybe you should think about the ROM youre using instead of soldering things to your phone and trying to cook it?

For instance, youre running a ROM, going by your signature its CM11, that uses KK which isnt designed for our device, which also uses about 3 times more battery (ive tested it with BBStats and CM11 myself over a stock ROM, and its true of EVERY KK ROM ive tried), so its no wonder your phone is running warm.

But thats not the phones problem, its yours. If you want to add yet another stress to the phone, then........

Im just saying....
[Galaxy S II Android Development] Jgjd691995:
Hmmmmmm the thing is that dori has pushed the throttle temp to 78 in the past and our devices still live soooo.... I figured
[Galaxy S II Android Development] stylemessiah:
While it may be possible, it doesnt mean its a good thing :)
[Galaxy S II Android Development] Twiq:
Agree..

Just because we can, doesn't mean we have to..

considering there are lots of different devices, and not all of them could survive that "boiling point".. Just sayin ?

Running 0401 Sabered SlimKat | DorimanX 10.43v99.1
[Galaxy S II Android Development] j1gga84:
Thank you but I think v1.0.5 is the most up to date version.

[MENTION=4663860]Computoncio[/MENTION]

I did a nandroid backup and backed up my files with TB, when I go to recovery and want to flash your Partitions Fix v1.0.5 it starts but only "checking EFS, checking system and checking data" with no values appear and then nothing happens. I waited for about 10 minutes but nothing happens. When I reboot Dorimanx logo appears also for about 10 minutes until system starts. What could be the reason? Or can it take a long time if partitions are really damaged?

EDIT: ok, it worked after I clicked FIX on BOOT in STweaks. I ran your fix 3 times now, could you have a look on my log?

Regards
[Galaxy S II Android Development] RovG:
[MENTION=2376110]dorimanx[/MENTION] et al., even though this may be old news, I just wanted to share this with you & the other devs. Not sure if we have the same fixes as they reference.

eMMC bugs and fixes at

http://wiki.cyanogenmod.org/w/EMMC_Bugs
[Galaxy S II Android Development] Jgjd691995:
Option 2 modify sink to have a stable temp bellow 71°C
[Galaxy S II Android Development] dkgr_ser:
Our phones are too old to care about surviving another two years or more, and in general such an increase to a CPU's throttle temp (which is of course set by the manufacturer to a point below the actual limit of the CPU) affects just a little the overall lifetime of the soc's internals which is practically endless... it usually exceeds 10 years, will you keep the phone that much?:confused:

The problem is the heat that reaches other parts of the phone, such as screen or the plastics. Because yes, ****in plastic melts down... But a 10C raise to the throttle temperature or at most 5C raise to the heat that reaches other parts (cause it spreads to the whole phone surface) can't cause any damage, at least not soon.;)

So yeap, consider increasing the throttle temp isn't bad if you know what you're doing. Many games like asphalt 8 are ALMOST unplayble even on lower settings, while GPU o/ced to 440Mhz. CPU at 800Mhz just ****s everything up...:crying: After all to such an old phone we need more power so we can be happy about running every app till we buy a new one, not crying about its lifetime, cause then it's only use will be as phone and an alarm clock:rolleyes::silly: My nokia's battery though lasts for 2 weeks...:cowboy:
[Galaxy S II Android Development] amit1275:
60hrs on 107

Running 107 for last 60 hrs. without restart or hot reboots.. no sods, no delayed response.. good free memory.. great work developers
[Galaxy S II Android Development] mosespl:
Mate that because kk on cm11 for our phone miss proper drivers for games. Kitkat for our phone even never realesed. Our kitkat is just a taste of real 4.4. Our phone is elder and legacy:p if you want to play games on UC or OC i recommend you solid 4.1.2 modification+dori v8branch and that is the best compilation for games.

Fantastic work and congratulations for all devs in this thread.

Wysłane z mojego GT-I9100 przy użyciu Tapatalka
[Galaxy S II Android Development] budsixz:
V9.43 v107 by comp is working good till now(no sod or anything)

will report more later
[Galaxy S II Android Development] _Atom_:
8.43 v107 running good and feels stable in my device
[Galaxy S II Android Development] m1trand1r:
after so nice uptime and stability I have to update my rom now....to latest SaberKat by [MENTION=1228651]fusionjack[/MENTION] ....i'm really outdated right now....

Great work devs[emoji106][emoji106][emoji108][emoji108][emoji122][emoji122][emoji122][emoji56]

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] FPSUsername:
[MENTION=3763274]rkoby13[/MENTION] 94 hours and only 13% got off??

And I see 3G, I am sure you had it on the charger. otherwise, what is your stweaks profile / rom tweaks?
[Galaxy S II Android Development] Rachid.Ala:
v107 by comp is stable as rock. thank you all
[Galaxy S II Android Development] m1trand1r:
it's not about battery life dude[emoji24][emoji23][emoji58][emoji23]

my Stweaks profile can be found in other thread [emoji122][emoji106]

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] Twiq:
He was showing off the uptime, that means v107 is that stable ?

Running 0401 Sabered SlimKat | DorimanX 10.43v106
[Galaxy S II Android Development] clock51:
hello guys, Happy Easter to all, I would like to try the kernel 10:43 V107, where I can find thanks
[Galaxy S II Android Development] kwiateusz:
first post of thread, bottom, 2 links with repos...
[Galaxy S II Android Development] cybernetus:
After a reboot with the new v107 my phone shows a partition error and ... now, i'm not have success to reflash another kernel ...

I believe or i lost my partition table or i have problems with my rom/kernel ... i need to do a backup and reinstall my rom again ...
[Galaxy S II Android Development] cdaarif:
I've soft brick with 8.43v107. My device only shows samsung logo. Can't enter cwm. It happened when I updated from 8.43 v105 with kernel wipe script. Rom jelly snap v7.0.
[Galaxy S II Android Development] m1trand1r:
new 107??? ...10.x branch?.....weird.....i've updated my Sabered Kat yesterday including reflashing kernel and all was "dirty" flash ......0 issues.....although browser window opens and tells me to fix res/dev/data or smth simmilar.....but.....I can't really afford data wipe right now.....[emoji23][emoji23][emoji23][emoji23]

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] Twiq:
That is horror.. But flashing stock rom with odin restores the partition table right? If the bootloader didn't get destroyed too that is ?

I hope you manage to fix your device ASAP

Running 0401 Sabered SlimKat | DorimanX 10.43v106
[Galaxy S II Android Development] RovG:
[MENTION=5074262]StanTRC[/MENTION], [MENTION=4666971]Phil3759[/MENTION] has created an awesome touch interface for recovery. He has also made most of it open source. I believe that it will enhance this kernel even more if we had it. Please will you consider merging it with the new updated recovery that you have created.

http://xdaforums.com/showthread.php?t=2201860

Phil3769 was providing his touch recovery with stock kernel for i9100 but has since stopped due to kernel source constraints http://xdaforums.com/showthread.php?t=1877270
[Galaxy S II Android Development] m1trand1r:
which rom mate ? Spirit ?

I'll reboot now to see what'll happen ....:fingers-crossed:

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] cybernetus:
I'll need to install all things again. The problem is on recovery i believe.

I don't have success on installation of rom, kernel etc. The recovery isn't get the properties of the device ... it's a strange error.

I don't see this error before ...

There is no problem on fix this. I get the pit file on this topic http://xdaforums.com/galaxy-s2/development-derivatives/mod-partition-internal-memory-app-t2538947

And the problem is solved. But i believe i have another problem. I need to format all partitions again to get the phone up :)

This is a strange problem with my phone or with the v107 :) I believe the problem is on my phone :)

Hummm i neeed to reinstall all things again. But i believe this is a local problem on my phone.

Not a problem with the Kernel.

---------- Post added at 02:48 PM ---------- Previous post was at 02:48 PM ----------

Yeah, i'm on spirit now :)
[Galaxy S II Android Development] nik60:
hi,all

Yesterday, i flashed rom fusion v1 stock based in secrom for test dualboot with dori 8.43 v107

recovery say error device proprety---BOOT OK BUT .....PARTITION ERROR...

reflash with dori v104----error installation aborted( i tink because rom have vrtheme)

reflash with dori v107 and before reboot flash dori 8.43 v104

ALL WORKING FINE.
[Galaxy S II Android Development] Troubadour666:
no vrtheme process in fusion v1, even its named theme :)
[Galaxy S II Android Development] nik60:
hi.

yes, part 1 installation rom is OK ..error is in part 2 during "cross-breeder" installation (i tink)--v104
[Galaxy S II Android Development] razkal1:
Have no logs but can't flash zips to second rom.. recovery says can't change something in dev/__permissions__ on comps 107... On 105 all fine

Sent from whereever iam...
[Galaxy S II Android Development] Troubadour666:
Hi [MENTION=5074262]StanTRC[/MENTION] , what about vrtheme installtheme.sh script issue with new recovery ?

thanks
[Galaxy S II Android Development] jgcaap:
Whats the last version to test out?
[Galaxy S II Android Development] Spaulding89:
V107. Are u read the thread? [emoji53]
[Galaxy S II Android Development] jgcaap:
been off. Computoncio is helping me on developing a kernel wich works for me. :p thats why i asked
[Galaxy S II Android Development] Computoncio:
v108 is about to be release :highfive:

Exfat support is running fine :victory:, 2nd rom boot's, the only issue is that SlimBean doesn't support exfat sdcard0 :( If you know a rom that support it please share :good:

Status 7 error in recovery when flashing is fixed (ex: CrossBreader), thanks [MENTION=5074262]StanTRC[/MENTION].

Issues i found:

Can't format sdcard0 in ext4 recovery log here

Had to add a binary "mount.exfat-fuse" for mounting exfat in /sbin/init, mount.exfat was trowing "segmentation fault" but mount.exfat worked fine in /sbin/recovery-loader mounting sdcard0 (Input about this will be very appreciated since new binary is almost 900kB but in zip not in kernel ;))

Build v108 for all branches

Kernel_Dorimanx-V8.43v108-Comp-[23-36]-[21-04]-JB-SGII-PWR-CORE.zip MD5: 618028bfd54c780b4f6c26982214445a

Kernel_Dorimanx-V9.43v108-Comp-mv2-[23-13]-[21-04]-JB-SGII-PWR-CORE.zip MD5: b5a3b2927d68e3fc30cd4cb0cb9d938a

Kernel_Dorimanx-V10.43v108-Comp-mv3-[22-50]-[21-04]-JB-SGII-PWR-CORE.zip MD5: 37f22e6b195e29a350a462529cd77237

Commits:

Kernel V8: Exfat binary added in /system/bin on flashing the kernel

Kernel V9-mv2: Exfat binary added in /system/bin on flashing the kernel

Kernel V10-mv3: Exfat binary added in /system/bin on flashing the kernel

initramfs: Support for exfat added to kernel, now waiting for roms devs;)
[Galaxy S II Android Development] Twiq:
v108 looks good, i've just finished setting up my config.

Lets see how bad this build is ?

Running 0401 Sabered SlimKat | DorimanX 10.43v106
[Galaxy S II Android Development] StanTRC:
Hi!

It's not allowed to run programms that way.

You should use for example run_program("/sbin/sh", "/sdcard/vrtheme/installtheme.sh"), not just run_program("/sdcard/vrtheme/installtheme.sh") in updater-script and "exec /sdcard/vrtheme/zipalign", not just "/sdcard/vrtheme/zipalign" in installtheme.sh.

"/sdcard" leave is is.
[Galaxy S II Android Development] Troubadour666:
ok [MENTION=5074262]StanTRC[/MENTION] , i have to make some changes and report.

thanks.