maybe he does not like your avatar
I resonede to his post 1 page back...
Arrr, I see, I think its beautiful lol.
maybe he does not like your avatar
I resonede to his post 1 page back...
What do you want: an uncertain emmc_cap_erase patch leading to potential instabilities or keep it stock and pray Samsung did their job well
I have amazing news
Good news: I elucidated the mystery of loosing the possibility to format internal sd from within Settings / Storage / Format USB
Bad news: It is caused by patching the binary sequence to avoid brick bug
Now, we are stuck... until Samsung release the source for JB
Detailed Info:
After repacking new leaked JB kernels for i900/n7000, internal sd could no more be formatted from phone (Format USB storage)
After revising all my code, I noted that even a simple unpack / repack of stock kernel without any modification, still causes the issue. So, it was restricted to my unpack / repack process
I tried changing mkbootimg, recompiling it, using third party scripts, same result.
I finally decided not to patch the binary sequence to try it: Stock kernel, unpacked and repacked worked
I tried my kernel, unpack / repack with editing initramfs but no patching for emmc_cap_erase: Again, it WORKS
Conclusion: the binary sequence is no more linked absolutely to the emmc_cap_erase. As xda Elite developer Entropy512 said, Samsung added probably a workaround for the brick bug without patching emmc_cap_erase. However, without their source code for JB, no one can assert it at 100%
Debate is open HERE : http://xdaforums.com/showthread.php?t=1901191
What do you want: an uncertain emmc_cap_erase patch leading to potential instabilities or keep it stock and pray Samsung did their job well
I will re-install an ICS ROM to test the issue and verify it is introduced by JB (I had 0 reports until JB leaks...)
I spoke with him now .. He says he had a German rom with region KOR..did you watch the video? It is XXLSA, so why another dump.....and I doubt this guy got this OTA
midreestaj said:Originally Posted by midreestaj
Can any body report with 24 hours of usage with 40+ apps installed on XXLSA with below?
1- Memory management over all
2- Min free memory reported by task manager app
EDIT: we would have a sh**storm here in thread, if this leak was CRAP!!! It is just the usual percentage of people having trouble mainly with theirselves
I already told you - I don't care formatting USB storage not availabale on device...people wanna do this still can on PC/Laptop connected with USB
I am a complete noob in kernel things, but what about this: http://xdaforums.com/showpost.php?p=33227621&postcount=1
Doesn't that tell us the kernel is probably save anyway? Or am I noobish wrong (would not be surprised anyway )?
Well when you're so sure just leave the stock kernel and make a few factory resets ok ?
I have amazing news
Good news: I elucidated the mystery of loosing the possibility to format internal sd from within Settings / Storage / Format USB
Bad news: It is caused by patching the binary sequence to avoid brick bug
Now, we are stuck... until Samsung release the source for JB
Detailed Info:
After repacking new leaked JB kernels for i900/n7000, internal sd could no more be formatted from phone (Format USB storage)
After revising all my code, I noted that even a simple unpack / repack of stock kernel without any modification, still causes the issue. So, it was restricted to my unpack / repack process
I tried changing mkbootimg, recompiling it, using third party scripts, same result.
I finally decided not to patch the binary sequence to try it: Stock kernel, unpacked and repacked worked
I tried my kernel, unpack / repack with editing initramfs but no patching for emmc_cap_erase: Again, it WORKS
Conclusion: the binary sequence is no more linked absolutely to the emmc_cap_erase. As xda Elite developer Entropy512 said, Samsung added probably a workaround for the brick bug without patching emmc_cap_erase. However, without their source code for JB, no one can assert it at 100%
Debate is open HERE : http://xdaforums.com/showthread.php?t=1901191
What do you want: an uncertain emmc_cap_erase patch leading to potential instabilities or keep it stock and pray Samsung did their job well
I will re-install an ICS ROM to test the issue and verify it is introduced by JB (I had 0 reports until JB leaks...)
Hello,
I make a mod with :
- Multi Windows with All Apps
- Mini Keyboard corrected in AZERTY
- Flash Annotate Corrected
- Phone with Record
- Smart Rotation
- Toogles in loockscreen
Flash in CWM : CWM Flash LSA MOD.zip
Confirmed that this was introduced start of JB leaks. ICS kernels do work nice once patched and repacked with my last recovery
Going to ask xda gods, but probably, you'll have to choose... painfully, until sammy releases sources
I am personally confident as there are 0 reports of bricks since JB was out (but it is true that most use my kernels and the bad binary-update files and recoveries are banned...
If it was that simple onyl...
problem is that for me, it means, the patching introduces random bug somewhere. It could be issues elsewhere too, not only sdcard formatting...
Till now, everything works, but this cannot be certain... The behaviour after the binary patch is really abnormal
But what could be the alternative? Finding 100 people fullwiping 100 times on unpached kernel...if noone bricks we can be 99.9% sure sammy solved brickbug anyway...
Every Rom cook or developer can take this ROM as base without asking for permission!!!
- minikeyboard in multiwindow mode will always write in QWERTY, even if QWERTZ or AZERTY is set as default
- zooming issue in video recorder (only in 1080p mode)
- no lockscreen toggles --> but you can use method provided by Robbie Hood: [DEV][MOD] Add Lockscreen shortcuts to JellyBean XXLS7 RippleLockScreen
Phil3759 said:The kernel I sent you comes with brand new recovery with deeply revised code for my settings part:
- Backup kernel with time stamp and free FLASH of kernels
- Backup and Flash logs now report true success/fail status
- Completely revised ors support
- Flash modem files from recovery
- 3.61 ---> 3.62: permissions fixed: now special backup and restore functions work again
- Update to cwm 6.0.1.9 + PhilZ Touch 3.34
- Add nandroid /preload backup & restore support
- Add option to flash modem image from recovery
- Fix Aroma File Manager path for devices without /emmc mount point
- Fix: mount sdcards before launch aroma as some times we did not have access to other sdcard under aroma
- Fix kerne/efs backup & restore for phones without /emmc
- Optimized backup/restore status log for kernel/efs/modem: now showing true success/failure based on exit code/stderr from CAT
- One ORS code is enough for custom and at boot scripts
- Fixed ORS backup job log
- Merge cm10 branch updates:
- Add support for doing a true ext4 format of /data on /data/media devices.
- Shorter confirmation menu if compiled as Philz Touch
Let's face it people, all these JB leaks for N7000 are pure crap let's hope that official version will be out soon cause all this flashing and fixing is really annoying :banghead: