For information on what F2FS is see the link here: https://en.wikipedia.org/wiki/F2FS
http://www.xda-developers.com/f2fs-put-to-the-test-against-ext4/
Basically F2FS is a newish file system and was designed by Samsung purely for flash memory devices. It is significantly faster in write speed and therefore yields benefits when used on partitions like DATA and CACHE.
However the SYSTEM partition is read only and therefore would not benefit from F2FS as EXT4 is capable of high speed read. Not only that Ext4 adds benefits of data integrity due to being a journaling file system.
As the system partition is not being touched, any Rom can be used, stock or custom.
This guide will explain how to convert to the F2FS file system.
1. The first step is to convert the DATA and CACHE partition to F2FS.
For this a custom Recovery with F2FS support is required. I have already built modified versions of TWRP which fully support F2FS which can be found here: http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
2. Install then boot to TWRP then make a backup of the DATA partition to your EXTERNAL SD CARD
Next select WIPE > ADVANCED WIPE then select CACHE then REPAIR OR CHANGE SYSTEM > CHANGE FILE SYSTEM > F2FS. Finally SWIPE TO CHANGE.
This will then format to F2FS, do the same for the DATA partition.
PLEASE NOTE THIS WILL COMPLETELY WIPE THE INTERNAL STORAGE, SO BACK UP ANY FILES YOU NEED TO THE PC OR EXTERNAL SD CARD!
3. Once the format is complete reboot TWRP by selecting the 'Recovery' option under the REBOOT tab.
4. Once rebooted to TWRP restore the backup of the DATA partition that was made earlier.
Ignore the warning about the backup being created with Ext4.
5. When that completes reboot to DOWNLOAD mode.
Next load up the relevant kernel below for your particular device in ODIN, put it in the AP slot then hit START.
SM-T805 BOCC KERNEL
SM-T800 BOCC KERNEL (confirmed working by godsfilth)
SM-T700 BOCC KERNEL(needs testing)
If the above kernels don't work because you have updated your rom to a later base you may need the updated kernels below. I have also added ext4 support in case anyone wants to switch back:
SM-T700 BOE6 KERNEL
SM-T705 BOE6 KERNEL
SM-T800 BOE6 KERNEL
SM-T805 BOE6 KERNEL
NOTE: the kernels provided are for Lollipop ONLY and is completely stock built from Samsung Sources except for the F2FS modifications. Also the kernel will allow Permissive mode to be set but is Enforcing by default( I think it should be the users decision and not forced permissive)
To change modes use SELinux mode changer http://forum.xda-developers.com/showthread.php?t=2524485
I wanted this kernel to be as untouched and stable as possible, so as not to introduce any issues. If you wish to have a custom kernel ask your kernel developer to add F2FS support.
6. Once the flashing process is complete with ODIN the tablet should boot. It may take a good while for the tablet to boot as its sets itself up and you will see the normal SAMSUNG logo, so don't worry if you have to wait a while.
Once booted further reboots will boot as normal and infact will probably notice quicker startups. I notice almost 5-10 seconds faster and a quicker tablet overall.
Have tested this thoroughly for days and has been stable with no issues.
IF ANYONE WANTS TO TRY THIS OUT AND THEN RETURN TO EXT4, ITS A SIMPLE MATTER OF FOLLOWING THE SAME PROCEDURE, BUT CHOOSING EXT4 IN TWRP.
Source code
GOOD LUCK AND PLEASE GIVE FEEDBACK.
.
T800 kernel added. Not tested as I don't have the T800, so can someone confirm it works?
ashyx said:
T800 kernel added. Not tested as I don't have the T800, so can someone confirm it works?
Click to expand...
Click to collapse
thanks loved f2fs on my N7 i'm making a backup now not sure if I'll be able to test before work or if I'll have to wait till tomorrow
so it seems the T800 doesn't boot.
after a minute or two logcat starts running but seems to my untrained eye to loop to the same things every few minutes.
i can still force a reboot into recovery so no harm done, if you have any ideas ill test them out, ill try again sometime tomorrow maybe my sleep deprived brain missed something
godsfilth said:
so it seems the T800 doesn't boot.
after a minute or two logcat starts running but seems to my untrained eye to loop to the same things every few minutes.
i can still force a reboot into recovery so no harm done, if you have any ideas ill test them out, ill try again sometime tomorrow maybe my sleep deprived brain missed something
Click to expand...
Click to collapse
How far does it boot and how long did you wait, do you see the second multicoloured Samsung logo?
It does boot on my t805 fine as do all t800 kernels, so seems strange it doesn't on your t800.
I will post another boot.img for you to try.
Can you try booting again then send me the kernel log.
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
ashyx said:
How far does it boot and how long did you wait, do you see the second multicoloured Samsung logo?
It does boot on my t805 fine as do all t800 kernels, so seems strange it doesn't on your t800.
I will post another boot.img for you to try.
Can you try booting again then send me the kernel log.
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
Click to expand...
Click to collapse
boots to the "samsung galaxy tab s" splash screen then dims a little and stays there left it for 10 minutes while i figured out where adb pull and windows 10 had decided the kmsg file should go as well as while i typed this.
i did see an error in recovery when formatting data as f2fs it said something along the line of "mount -o bind /data/media/sdcar0 error=255" pretty sure it was longer than that ill get the whole message if you want.
kmsg should be attached let me know if you need anything else
godsfilth said:
boots to the "samsung galaxy tab s" splash screen then dims a little and stays there left it for 10 minutes while i figured out where adb pull and windows 10 had decided the kmsg file should go as well as while i typed this.
i did see an error in recovery when formatting data as f2fs it said something along the line of "mount -o bind /data/media/sdcar0 error=255" pretty sure it was longer than that ill get the whole message if you want.
kmsg should be attached let me know if you need anything else
Click to expand...
Click to collapse
That error message is normal because you've formatted the data partition, it's just a warning it can't mount sdcard/0.
Did you make sure that you formatted both cache and data to f2fs?
Also the kernel log you posted is from recovery not boot. To get the boot kernel log, boot as normal, give it a minute then immediately restart to recovery. Then run the command in the twrp terminal or adb.
ok so now that the kernel is working and i've played with it for a little while its definitely snappier at startup compared to ext4, noticeably so also apps seem to be a quicker as well ill play around with it some more and see but definitly plan on keeping it f2fs and swapping my girlfriends over as well
Any idea if apps like FolderMount that mount internal storage folders (like OBB) to the external card?
i am going to install the T700 and see how it goes...
All good on T805 (T805XXU1BOE3) (using other f2fs enabled kernel). Thank you!
I would like to tell @ashyx a very enthusiastic THANK YOU for taking the time to put this guide and F2FS kernel together. We need more developers like you man. I'm happy I do not have to give up F2FS just because I got a new device, so thank you for this.
I would like to ask anyone who has not thanked ashyx, to please take the time and hit his thanks button. He deserves it :good:
Much appreciated, thanks for the feedback. :thumbup:
ashyx said:
Much appreciated, thanks for the feedback. :thumbup:
Click to expand...
Click to collapse
Your most welcome. Going to test this on stock 5.0.2 on my T700 here soon.
Updated the kernel sources in op.
ashyx said:
Updated the kernel sources in op.
Click to expand...
Click to collapse
After flashing the new T700 kernel it does not boot for me. Saw the Samsung logo as usual for about 5 minutes maybe, but then the logo disappeared and then nothing. Seems to have shut down. The power button no longer worked to boot up either. However, it goes into Download Mode just fine.
Going to flash it again. BRB with some news. Thanks
EDIT: Flashed a second time and still the same, ROM will not boot on the BOE6 kernel. Thanks again
SkOrPn said:
After flashing the new T700 kernel it does not boot for me. Saw the Samsung logo as usual for about 5 minutes maybe, but then the logo disappeared and then nothing. Seems to have shut down. The power button no longer worked to boot up either. However, it goes into Download Mode just fine.
Going to flash it again. BRB with some news. Thanks
EDIT: Flashed a second time and still the same, ROM will not boot on the BOE6 kernel. Thanks again
Click to expand...
Click to collapse
Which firmware base are you running?
ashyx said:
Which firmware base are you running?
Click to expand...
Click to collapse
I was running CarbonROM 5.1.1.
I can no longer boot system, and it wont boot to recovery either. What is the button combo for recovery again? Maybe I have it wrong.
I thought I had downloaded a zip for stock 5.0.2, but I cant find the darn thing now, lol. I have a TWRP backup of 4.4.2 and 5.0.2 (I think), but I'm on 5.0.2 Bootloader. Plus I need TWRP mode in order to even restore the backups.
is there a ODIN tar of 5.0.2, preferably rooted? I found TWDetox, but its a zip for TWRP to install. Damn it, lol I know for fact I found a tar for 5.0.2 but now I can't find it. I need to find a RedBull maybe that will help me locate it. LOL
POWER + VOL DOWN + HOME as soon as it restarts quickly change to VOL UP whilst still holding the other buttons.
ashyx said:
POWER + VOL DOWN + HOME as soon as it restarts quickly change to VOL UP whilst still holding the other buttons.
Click to expand...
Click to collapse
Hmm, thanks I have not seen that combo mentioned anywhere on the internet yet. You rock dude, it worked... :good:
Related
Hi guys,
Tried to upgrade from Darchdroid 2.6.5 to 2.7 today and am now stuck with an unusable phone.
I get a boot loop OR I get stuck on the HTC boot screen for 20+ min. I'm not sure why I get stuck on either one.
This advice was given to me today in the 2.7 thread:
hold down menu+back+power and do a hard reset.
then wipe everything. [EVERYTHING ext4, ect.]
then flash DD2.7
then flash GoogleBits.
good luck.
edit: this has the newest kernel.
__________________
Click to expand...
Click to collapse
The problem is, in order to complete a hard reset, you have to reboot the phone!(right?) But when I reboot, I just get stuck on the HTC boot screen. Is there wiping instructions (i.e. do I need to do certain things from adb instead of the phone?) that I'm missing out on?
Thanks so much. Really loved 2.6.5. Don't know why I keep getting suckered into updating
A hard reset is the same thing as doing a factory reset. So, go into recovery, go tinto the wipe list, and wipe everything on that list. Then, flash it and reboot.
HeroMeng said:
A hard reset is the same thing as doing a factory reset. So, go into recovery, go tinto the wipe list, and wipe everything on that list. Then, flash it and reboot.
Click to expand...
Click to collapse
Thx, Heromeng. Did exactly what you said - wiped everything possible in AmonRa 1.7 and now I'm back to a boot loop.
Some further info: When I was upgrading from 2.6.4 to 2.6.5, Darch said I should push the boot.img from 2.6.4 to make things work. That did the trick for the last update (although I don't know why!).
Is pushing the boot.img from 2.6.4 the way to get 2.7 to work on my phone?
Alright, I went ahead and pushed the boot.img from 2.6.4 and now it's working. I guess it's just like 2.6.5.
My question:
What am I sacrificing by using this boot.img instead of the one from 2.7? I'm not clear what the trade-off is.
Thanks again.
Back up your sd card, then repartition it.
Sometimes ramswapz corrupts the sd card, so you have to format it and repartition before being able to flash a new ROM.
---------------------------------------
There isn't enough of a difference between the kernel where your phone shouldn't boot.
Decad3nce said:
Back up your sd card, then repartition it.
Sometimes ramswapz corrupts the sd card, so you have to format it and repartition before being able to flash a new ROM.
---------------------------------------
There isn't enough of a difference between the kernel where your phone shouldn't boot.
Click to expand...
Click to collapse
Decad3nce: I've re-partitioned it 3 separate times and every time it's a boot loop! Would you tell me if I'm doing this all in the correct order?
-Wipe everything.
-Re-partition sd card
-Enable USB toggle
-Move 2.7 and Googleshits from computer to Phone
-Flash ROM
-Flash googleshits.
-Reboot.
note: I was able to boot into 2.7 with the (pushed) 2.6.4 boot.img but I wasn't able to start wi-fi. So I'm assuming the 2.6.4 boot.img had something to do with that and that's why I'm trying a "virgin" 2.7 flash again.
All I can say is I'm in the same boat. It seemed to me, in my earlier tinkerings, that my phone needed a boot.img that was slightly less overclocked. The few DarchDroid successes I've had were from lower-clocked boot.img's. Without it, I just look at the HTC logo forever.
bohiti said:
All I can say is I'm in the same boat. It seemed to me, in my earlier tinkerings, that my phone needed a boot.img that was slightly less overclocked. The few DarchDroid successes I've had were from lower-clocked boot.img's. Without it, I just look at the HTC logo forever.
Click to expand...
Click to collapse
That's really helpful info, Bohiti. I thought I was alone here!
I am in 2.7 now with the 2.6.4 boot.img but I'm unable to start wi-fi.
This is a dealbreaker for me.
Why would the boot.img affect wi-fi??
Well sorry, kind of. While what I said was true, I just now tried the hard reset suggested to you. (Menu+Back+Power). And then I wiped everything and flashed 2.7 and GoogleShits. And it booted fine, quickly. Only on HTC screen for 10 seconds maybe.
So I'm not in the same boat, though in the past I've had the same symptom with my phone. I haven't rebooted again, maybe I just got lucky.
Darch made changes to his kernel(so it boots at a higher frequency); your phone probably can't handle it then.
Bug him, jus10o, or me(tomorrow) about making a 710mhz bootable.
Decad3nce said:
Darch made changes to his kernel(so it boots at a higher frequency); your phone probably can't handle it then.
Bug him, jus10o, or me(tomorrow) about making a 710mhz bootable.
Click to expand...
Click to collapse
Thanks decad3nce. I will do just that! And thanks for the info, bohiti.
Finally some positive news!
sariamanascar said:
Thanks decad3nce. I will do just that! And thanks for the info, bohiti.
Finally some positive news!
Click to expand...
Click to collapse
I lied. it defaults at 710 on boot. But, try booting 2.6.7 with no sd card in your phone. (do a full wipe, I mean everything)
Decad3nce said:
I lied. it defaults at 710 on boot. But, try booting 2.6.7 with no sd card in your phone. (do a full wipe, I mean everything)
Click to expand...
Click to collapse
OK, just tried this two different times.
No boot loop(!) but now it just hangs on the HTC logo.
Any other ideas?
Bout to go ask Darch and jus10o for ideas....Btw, should I PM them or create a thread?
Thanks again for your help.
sariamanascar said:
OK, just tried this two different times.
No boot loop(!) but now it just hangs on the HTC logo.
Any other ideas?
Bout to go ask Darch and jus10o for ideas....Btw, should I PM them or create a thread?
Thanks again for your help.
Click to expand...
Click to collapse
already told jus10o, but feel free to pm him or Darcj anyways. one of us just needs to compile a kernel that defaults and limits itself under 710.
Decad3nce said:
already told jus10o, but feel free to pm him or Darcj anyways. one of us just needs to compile a kernel that defaults and limits itself under 710.
Click to expand...
Click to collapse
Just PM'd them myself. Thanks for the help, Dec.
Has this issue been addressed? I am having the exact same issue. I have flashed just about every rom on XDA and never had any issues, but I am having the same problem with 2.7 and Buffed2.0...both overclocked kernels. On 2.7 if I do a few battery pulls the phone somehow gets past the HTC logo but everytime I reboot i get the boot loop again.
I have never had any issues like this so I have never had to pull a log. If this would be helpful i would be glad to do it but would need directions on how to.
For all future visitors: Dec was kind enough to modify a kernel that got GPS and Wifi working for me - so thanks Dec. Problem was, GPS eventually started crapping out and I had a whole bunch of force closes over the past week. Including my phone app even crashing on me.
Today, I finally gave up on 2.7 and am on to PureHero which is largely AOSP and (for the non-OC'd version) a lot more stable. While I don't like the look as much, for those of us on weak phones, I think it's the best option.
I had the same issue, but flashed the uv kernel and it booted fine ever since. Couldn't run 2.7 till then.
stand corrected
I recently flashed the UV kernel and I have to say, everything works great. I stand corrected - no one told me the uv kernel was the same thing as "under clocking" a a kernel but I guess that's what it does. Thx.
Worked for me too
Hi just wanted to add that the UV kernel also solved my bootloop problems with DD 2.7.
A few times before the UV I was lucky, and after the 2nd or 3rd iteration of the bootloop it would get past the htc screen and boot. Happened enough times to get hooked on 2.7 haha But the last time I rebooted the phone it was very stubborn and stayed stuck no matter what I tried. That sent me searching back here. Glad I found your post, I assumed the UV kernel was only for those having battery issues, based on the main 2.7 thread.
NOTE: I am not the developer of this rom! I am only posting it on XDA with the permission of the Bonsai Team. The download link is on the Bonsai website, they use a checkout system to track downloads and to present you with an easy way to donate if you choose. YOU DO NOT HAVE TO DONATE TO DOWNLOAD! I will do my best to keep this post updated with change logs.
Custom tuned and ready for your sleek new Samsung tablet. The Bonsai ROM provides superior battery life and performance delivering on the promise of the Android OS for mobile devices.
This is an early beta release Bonsai for your Samsung Galaxy Tab 10.1 based from the stock Android Honeycomb v3.1 release. We’ve consolidated the latest Android community developments and rolled in the Bonsai magic to produce a replacement Android OS that will double your stock tablet performance.
Note: Due to going to some shell scripting where we have richer language and can control the install better, we are not able to update the progress bar while in this stage of running the install.
Some of the features of this release include: (credits below)
Android Kernel updated to v2.6.36.4
Overclockable kernel
Kernel module support for tun, cifs, aufs, ntfs, bluetooth mouse, xbox joystick
Voodoo Sound v9 (first release for Galaxy Tab 10.1) (Updated to v10)
init.d initialization script support
Ext4 filesystems can be configured without journaling enabled
New ROM packaging and install reduces package size by 20%
Deodexed and png graphics optimized
v0.1.5 Changes:
Update to Voodoo sound v10
Fixed problem with Plex app not streaming video
Kernel tuning which has raised MFlops from about 50 to 80 (AnTuTu score around 5800)
Changed init.d script permissions to accomodate “challenged” editor apps
Install script changes to accomodate more device variations
Known to run on Locked and Unlocked retail Tablets and I/O Tablets
Fixed problem where tablet would not boot with USB cable attached
Reduced delay seen when booting the device
Known Issues:
A few users have reported issues with boot animations in most cases the device seems to boot fine.
There seems to be a problem with CWM when its flashed via Rom Manager.
Google I/O Devices are currently not working. (There are instructions in post 121)
Install Instructions:
Download the ROM
Move the .zip to /sdcard
Unplug anything connected to the Tab
Reboot to Recovery
Make a nandroid backup
Wipe cache
Wipe dalvik
Flash the .zip
Reboot
Please be patient and wait for it to boot it it can take a while
Enjoy
If you want to change the OC settings, you will need to edit the file, /etc/init.d/24-cpufreq to set these values. The values are in the top of the file as follows:
Code:
FREQGOV=’ondemand’
MAXFREQ=’1000000’
MINFREQ=’216000’
Change these values as you wish. The parameters are applied on reboot.
Credits:
kernel: @pershoot []
voodoo sound: @supercurio []
Along with those changes that were provided in earlier releases, we are providing a number of changes that have been backported from the nVidia Tegra development. Changes include:
Tegra CPU power control
Add Tegra CPU perfmon context for power
Redisgn of Tegra CPU reset handling
Various Tegra CPU (cortex-A9) cache handling fixes
Fix memory leak in video driver
Tegra shared clock cleanup
Please flash this file after installing the 0.1.5 ROM package.
0.2.4 KERNEL UPDATE
DOWNLOAD HERE
NOTE: TouchWiz UX version includes the v0.2.4 Kernel. This ROM package is double the size of the non-TouchWiz, now weighing in at 350MB. Please help us conserve bandwidth. If for some reason you believe the ROM package to be corrupt, please double check your package using the md5sum command. The md5 checksum of this package is: 484a758563e661a7731aeed4a1e880f0
This is an early beta release Bonsai for your Samsung Galaxy Tab 10.1 based from the stock Android Honeycomb v3.1 release which includes TouchWiz. We’ve consolidated the latest Android community developments and rolled in the Bonsai magic to produce a replacement Android OS that will more than double your stock tablet performance.
WITH TOUCHWIZ UX DOWNLOAD HERE
----------------------------------------
you can use setcpu to change cpu frq.
Bug report: if you turn off your tab and plug into the charger to enable charging mode, it causes reboot loop (therefore you can't charge it while off)
antonyfl said:
you can use setcpu to change cpu frq.
Bug report: if you turn off your tab and plug into the charger to enable charging mode, it causes reboot loop (therefore you can't charge it while off)
Click to expand...
Click to collapse
Thanks for the bug report. As for the setcpu thing, while you can do that the system is configured with its own governor of sorts and setcpu fights with it and can cause some slowdowns so its not recommend to use it.
Currently the best way is to adjust it in an init script located in /etc/init.d/24-cpufreq
Any idea why I get a scrambled picture when i reboot that hangs before booting?
it seems like a boot logo/animation crapping out
DroidHam said:
Any idea why I get a scrambled picture when i reboot that hangs before booting?
Click to expand...
Click to collapse
so far no, however the dev is looking into this issue, as well as the kernel panic issue.
I am enjoying this ROM, glad an official thread was made
i'll add my issue in hopes someone can help. tried to load rom yesterday. it boot looped at the initial "samsung galaxy tab" screen. powered down then into upload mode, kernel panic. got into fastboot and booted cwm. tried to restore my last nandroid and it boot looped at the samsung animation screen. tried another nandroid and got error at data. i get either of these responses. i've tried to factory reset and still get boot loops. repeated all these a hundred times and boot loop at either of those screens. any ideas on how to get this thing back running. at this point i don't even care so much about a nandroid, i'd settle for any type of working tab.
bodiecon said:
i'll add my issue in hopes someone can help. tried to load rom yesterday. it boot looped at the initial "samsung galaxy tab" screen. powered down then into upload mode, kernel panic. got into fastboot and booted cwm. tried to restore my last nandroid and it boot looped at the samsung animation screen. tried another nandroid and got error at data. i get either of these responses. i've tried to factory reset and still get boot loops. repeated all these a hundred times and boot loop at either of those screens. any ideas on how to get this thing back running. at this point i don't even care so much about a nandroid, i'd settle for any type of working tab.
Click to expand...
Click to collapse
Have you tried to use odin to restore the tab to stock? i would suggest you try this first.
this ODIN version: HERE
this pda md5: HERE
Also I would like to add that when flashing the Bonsai ROM make sure your tab is not connected to anything including the charger and usb.
I have had ZERO issues at all with this ROM
Tried install on a rooted 16G running pershoot's latest oc kernel......
Wiped dalvik/cache
installed
reboot
never got past the gt 10.1 screen, was able to get back to recovery and restored my nandroid backup
maybe it was a bad flash, going to try one more time unless anyone has suggestions or sees something I missed
mark1962nc said:
Tried install on a rooted 16G running pershoot's latest oc kernel......
Wiped dalvik/cache
installed
reboot
never got past the gt 10.1 screen, was able to get back to recovery and restored my nandroid backup
maybe it was a bad flash, going to try one more time unless anyone has suggestions or sees something I missed
Click to expand...
Click to collapse
Reread the instructions because I added an additional step, also if the problem persist try going back to a stock kernel first and let me know how that goes.
Also keep in mind the first boot takes a very long time, my first boot took almost 15mins, and about five of that was on the first boot screen.
djrajir said:
Reread the instructions because I added an additional step, also if the problem persist try going back to a stock kernel first and let me know how that goes.
Also keep in mind the first boot takes a very long time, my first boot took almost 15mins, and about five of that was on the first boot screen.
Click to expand...
Click to collapse
The first time I rebooted to recovery through Rom Manager (which I don't generally do), this wouldn't affect anything would it?
mark1962nc said:
The first time I rebooted to recovery through Rom Manager (which I don't generally do), this wouldn't affect anything would it?
Click to expand...
Click to collapse
I'm not sure, it shouldn't however there have been issues like this before which is why i always manually reboot my device into recovery (such as what is currently going on with Galaxy S 4g devices)
what is journaling?
Also i flashed this (over pershoots kernel)
and now its stuck on Samsung Tab 10.1 at boot
I flashed following the instructions and everything installed fine except I keep getting fc on most of the apps I try to run. Anyone else having that issue?
lollee76 said:
I flashed following the instructions and everything installed fine except I keep getting fc on most of the apps I try to run. Anyone else having that issue?
Click to expand...
Click to collapse
How did you reinstall apps? Market or TiBu?
SS2006 said:
what is journaling?
Also i flashed this (over pershoots kernel)
and now its stuck on Samsung Tab 10.1 at boot
Click to expand...
Click to collapse
Please let me know if you get it to work (this was my experience as well)....I'm going to give it another shot after dl'ing.
I cant seem to turn it on anymore cause battery died while it was frozen
i pluged it in, at one time it showed the battery charge indiciator
now its just not turning on
mark1962nc said:
How did you reinstall apps? Market or TiBu?
Click to expand...
Click to collapse
The first time I tried I did the whole wipe data/factory,cache,dalvik and re-installed apps using My Backup and got fc like crazy...so then I restored my nandroid backup and started over (Note I did test one app with TiBu by installing from the market and restoring just the data to that app using TiBu and it just hung up).
This morning I read this post and restored my nandroid again and tried the directions in OP and only wiped cache and dalvik which left my apps as is.
I also want to note I was using pershoots kernel before flashing this ROM.
I have no idea what happened to this Tab but it was brought to me with no way of getting into the boot loader, it just sits on the Samsung Screen. I was able to get it to the service screen and use Heimdall to upload CWM to it and then went to enter a format of the device and I'm getting all sorts of errors. I'm guessing the /data is corrupt *very* corrupt. I'm not sure how to do a full format. I think that with everything cleared I know enough to get it going again but no matter what I do I can't get the /data to format. I've tried fixing permissions and that takes 20 minutes and then says it's completed but yet I have no option of mounting /data in any way or clearing it. I'm so frustrated, I'm just looking everywhere for a way to nuke it back to where I can load even a stock ROM to get this thing to come back to life. Any ideas??!??!
matt.wolfley said:
I have no idea what happened to this Tab but it was brought to me with no way of getting into the boot loader, it just sits on the Samsung Screen. I was able to get it to the service screen and use Heimdall to upload CWM to it and then went to enter a format of the device and I'm getting all sorts of errors. I'm guessing the /data is corrupt *very* corrupt. I'm not sure how to do a full format. I think that with everything cleared I know enough to get it going again but no matter what I do I can't get the /data to format. I've tried fixing permissions and that takes 20 minutes and then says it's completed but yet I have no option of mounting /data in any way or clearing it. I'm so frustrated, I'm just looking everywhere for a way to nuke it back to where I can load even a stock ROM to get this thing to come back to life. Any ideas??!??!
Click to expand...
Click to collapse
What was the last known ROM did you install? which android? froyo (2.2), gingerbread 2.3.* or ics?
were you able to mount /data and /dbdata?
what error message did you get?
-- I take it you are not able to go to download mode (Power + Volume Down)?
What happen after you press Power + Volume Down?
If you can go to download mode:
Try this:
http://forum.xda-developers.com/showpost.php?p=23348040&postcount=121
if not, try the above link - Retreive .rfs file in .tar and push it using heimdell.
same solution with more instructions:
http://forum.xda-developers.com/showpost.php?p=13470380&postcount=8
hope it will help. If not let's try something else.
So, just for purpose of discussion (I tapped and ended up sending it in to Verizon with stock flashed back on it), it had ICS on it last. It was, jeeze, I can't remember what ROM but it was one of the ICS ROMS for the tab that are out. I used this tab like two days before with ICS running on it and had no issues when I used it but then two days later back in the owners hands it took a huge #*$&. I could mount /dbdata but not /data. It would fail a factory reset or a data wipe/format or a permissions reset every time.
I could get into the download mode for Heimdall to flash various other ROMS to it that would, according to Heimdall, successfully flash but then going in and doing a data wipe would fail to get the ROM to start up properly. I could do custom boot with CWM that is available for TAB but I couldn't get the stock boot loader to come up on stock ROMS. So odd, I appreciate the response because I wasn't sure if anyone would even be able to address such an odd thing.
Oh, on a side note, I could also not do a Dalvak wipe which I know nothing about but know it's important to wipe on occasion between ROMs - if that gives any insight into the real issue. The only thing I can surmise is that, somehow, that /data became corrupt and would not wipe. I thought of looking into ADB commands but whenever I would hook the Tab to my computer I could never get ADB to recognize it no matter what driver I used. Very frustrating to meet your match on tech.
**if it comes back and they wont help, I'll try this method you've posted though. In fact, I should be seeing it back shortly and I'll let you know what they've done.
matt.wolfley said:
**if it comes back and they wont help, I'll try this method you've posted though. In fact, I should be seeing it back shortly and I'll let you know what they've done.
Click to expand...
Click to collapse
No Please if you had ICS last, Do NOT flash the .rfs. ICS runs on ext4. But I hope VZW had it fixed for you.
A guy over at the oficial oneplus forum (https://forums.oneplus.net/threads/aging-mode.468296/)
found out that if you press vol up and down at the same time the phone boots from a different partition,
instead of sde18(boot) it starts from sde19(boot_aging)
after comparing boot.img with boot_aging.img
it seams that the ramdisk ist the same, just that boot_aging contains an additional kernel module: wlan_aging.ko
also the kernel itself is 2 MB larger than the default one...
Anyhow this mode is probably not use in normal phone operation but rather some part of post production testing/burn-in
So we could probably use it for something useful....
Like switching between two kernels without the full multiboot....
Or may be having two different recoveries...
This is indeed very interesting and could potentially be useful. Switching over between the modified TWRP and standard TWRP could then be a thing?
could be worth a try..
MisterCoolBeans said:
This is indeed very interesting and could potentially be useful. Switching over between the modified TWRP and standard TWRP could then be a thing?
Click to expand...
Click to collapse
Not two different twrp versions since its the boot partition but we could use two different kernels
Solution for a native dualboot maybe?..
This isin't the boot used for unbricking the phone ?
As far as i understand the unbrick process, no it is not.
I think i can be used for dual boot just as well as for a alternative recovery. to my understanding the difference between boot, boot_aging, and recovery is which is booted when. I think if we would blast recovery to boot the phoen would always by default start with recovery, and if we flash boot to recovery we could also implement a sort of dual boot just that than we wouldn't have any recovery.... just my 2 cent
About dualboot, look here: http://forum.xda-developers.com/oneplus-3/how-to/op3-partitions-t3454215 we dont have a spare 3 GB partition, so if we want to dual boot, the new kernel has to be modded to have the system image in the data partition.
Or we use the 1,5 GB unused pace on the last block device as you can see in the partition overvirew I made, for CM with pico gaps that could be enough.
Actually that could be really cool, to have a secondary OS on the phone that does not conflict with the main one
Does that work with unlocked bootloader?
I tryed to press vol up+vol down + power and i get to the normal bootlaoder boot menu,
when i press in the menu power agian it shows a oneplus logo and text fastboot mode but it enters twrp and that is it.
I wonder if this key combination is only avilable when the bootloader is locked...
Apparently you can boot from that partition using the Engineering mode: *#36446337#
if you select "auto aging" the software will than ask you if you wont to reboot...
Anyone remember this thread?
There apparently is a bootloader bug that allows to unlock it without getting the usual boot screen: https://securityresear.ch/2017/02/08/oneplus3-bootloader-vulns/
I wonder if once used these method to unlock you get the option back to boot into the aging boot partition, and if this could be used for something useful.
Like having two different recoveries or switching between different kernels with only one reboot.
One of the most interesting threads currently in OP3 section.
I hope our kernels and recoveries devs join OP in this interesting, challenging and potentially useful quest.
I think the kernel devs will already know about this, so it's probably not that much of a breakthrough, sorry to be that guy although it does remind me of the secondary boot.img for the unbrick of a nexus 5
Hi,
Please indulge me if this it a bit silly, but I am confused about installing magisk from recovery. I flashed the patched image to recovery partition, as per the github guide (https%3A//topjohnwu.github.io/Magisk/install.html%23boot-image-patching, sorry for the encoding, system forbids me to post link cuz I am new). Yet at this point I am unsure about what to do next. This is what I see now when I boot my phone to recovery using key combo:
- Reboot system now
- Apply update from ADB
- Apply update from internal storage
- Wipe data/factory reset
- Wipe cache partition
- Mounts a storage
If I select "Reboot system now", nothing seem to happen and it all looks like a normal startup.
In short, I would like to know how to run to a ystem with Magisk enabled.
Thanks in advance!
You're not actually supposed to boot to recovery. You need to release the key combo once you see the splash screen. Reference:
https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery
Edit: and don't worry... Everyone's a noob at some point or another.
Didgeridoohan is right: It sounds like you're booting into your phone's stock recovery, instead of your custom recovery.
Forgive my presumptions, or if I sound condescending, but if you happened to have patched and flashed your partition mods with a PC, you might want to check if you even have a custom recovery installed. (I know that some phones aren't capable of having a custom recovery flashed, so your situation might be different.) If you don't have one, that would be the first step (most folks use TWRP). Once you can boot into your custom recovery, though, you should be good.
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 20.4), using Tapatalk
Didgeridoohan said:
You're not actually supposed to boot to recovery. You need to release the key combo once you see the splash screen. Reference: ...install.html#magisk-in-recovery
Edit: and don't worry... Everyone's a noob at some point or another.
Click to expand...
Click to collapse
Right, this is the part where I get confused. I did follow the link you mentioned. After pressing [power] & [volume up] for about 8 seconds, I feel a vibration and the screen lights up, thats when i released the keys. I ended up getting that menu i describe above...(tears)...
Ideally, what should I see if things go right?
NeoHiPPy1980 said:
Didgeridoohan is right: It sounds like you're booting into your phone's stock recovery, instead of your custom recovery.
Forgive my presumptions, or if I sound condescending, but if you happened to have patched and flashed your partition mods with a PC, you might want to check if you even have a custom recovery installed. (I know that some phones aren't capable of having a custom recovery flashed, so your situation might be different.) If you don't have one, that would be the first step (most folks use TWRP). Once you can boot into your custom recovery, though, you should be good.
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 20.4), using Tapatalk
Click to expand...
Click to collapse
No worries. Any suggestion is much ppreciated. Just to be sure (correct me if i m wrong), I thought that patching an image file is an independent way of installing magisk in case custom recovery is not available. So that s my case.
Anyhow, I would really like to learn a bit more about the situation where recovery partition contains both the stock recovery and custom recovery/patched image. There doesnt seem to be any difference whether i release the key combo or not once I see a splash screen. I always end up with that blue menu in recovery.
Wubwubdubdub said:
No worries. Any suggestion is much ppreciated. Just to be sure (correct me if i m wrong), I thought that patching an image file is an independent way of installing magisk in case custom recovery is not available. So that s my case.
Anyhow, I would really like to learn a bit more about the situation where recovery partition contains both the stock recovery and custom recovery/patched image. There doesnt seem to be any difference whether i release the key combo or not once I see a splash screen. I always end up with that blue menu in recovery.
Click to expand...
Click to collapse
If you don't mind my asking, which model of phone do you have? Most phones have a similar button combo, but are a bit quirky to get into the recovery.
Ex: On my LG V20, I have to hold Vol-, and Power, but release the power button at the splash screen for 0.5-1 seconds (while still holding Vol-) and then press/hold the Power button again...
As a suggestion, you may want to see if your phone has a similar quirk, depending on the make /model.
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 20.4), using Tapatalk
[Solved] by flashing boot image instead of recovery image
I am still puzzled by the complications with booting into recovery mode. To work around it, I attemped installing Magisk using boot image patch and succeeded. Objective achieved yet question remains. Anyways, a big thanks to Didgeridoohan and NeoHiPPy1980. Knowing that someone will provide help is what stopped me from giving up.
NeoHiPPy1980 said:
If you don't mind my asking, which model of phone do you have? Most phones have a similar button combo, but are a bit quirky to get into the recovery.
Ex: On my LG V20, I have to hold Vol-, and Power, but release the power button at the splash screen for 0.5-1 seconds (while still holding Vol-) and then press/hold the Power button again...
As a suggestion, you may want to see if your phone has a similar quirk, depending on the make /model.
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 20.4), using Tapatalk
Click to expand...
Click to collapse
I have a Ulefone, not sure if you ve heard of it
But that won't matter. I managed to get it working another way (see to my last post). I should probably have done that before making this post. Thanks for your assistance!
Great to hear you got things working, but why did you think you needed to use the recovery image for your device? Was any of the installation instructions unclear and in need of improvement (I'm just trying to learn for future reference)?
Didgeridoohan said:
Great to hear you got things working, but why did you think you needed to use the recovery image for your device? Was any of the installation instructions unclear and in need of improvement (I'm just trying to learn for future reference)?
Click to expand...
Click to collapse
Frankly, I find the Magisk Installation Guide to be one of very few documentation that is concise, coherent and user-friendly for both regular user and developer. So a big thumb up for you all! For your reference, here is the process of how I was lead to believe I needed the recovery img:
1.
I followed the instruction on "know your device" (https%3A//topjohnwu.github.io/Magisk/install.html#knowing-your-device). The first command returns nothing and the seconde comand returns true. Naturally, I assumed this means that my device is using system-as-root on a non-A/B device.
2.
I then read:
If your device is NOT A/B, but IS using system-as-root, then you will have to install Magisk to the recovery partition of your device. Follow the instructions in Boot Image Patching, but instead of using your boot image, use your recovery image. "
Click to expand...
Click to collapse
(https%3A//topjohnwu.github.io/Magisk/install.html#getting-started)
I am not sure if I misunderstood sth. At this point I still believe that according to the instruction I should have patched my recovery image. I do not know what system-as-boot actually is...
Yes, it does seem like your device is A-only system-as-root, which would normally mean you need to use the recovery image.
Unfortunately, with the Android ecosystem being as fractured as it is there will always be exceptions...
Thanks for the detailed response.
Hi Guys
Wubwubdubdub, I have got a question for you. I followed the same instructions as you mentioned in first post and ran into problems as well. How did you get around this problem? What is the difference between the two ways you mentioned here? (I believe I used the first way).
Wubwubdubdub said:
I flashed the patched image to recovery partition, as per the github guide
Click to expand...
Click to collapse
Wubwubdubdub said:
To work around it, I attemped installing Magisk using boot image patch and succeeded. Objective achieved yet question remains.
Click to expand...
Click to collapse
Thanks in advance!
MM