Do you know if there's a way to get Xposed working? I tried the Xposed Framework SDK 26 from inside Magisk, but it put me in a boot loop.
I think we now have Xposed - check the end of this discussion:
https://github.com/rovo89/Xposed/issues/310
I might give this a go when I'm feeling less lazy.
Well actually yes xposed is available. But I left this solution for a long time in favour of Magisk and it's modules to be honest
Sent from my HTC U11 using XDA Labs
thref23 said:
I think we now have Xposed - check the end of this discussion:
https://github.com/rovo89/Xposed/issues/310
I might give this a go when I'm feeling less lazy.
Click to expand...
Click to collapse
Thanks a lot for the link! Thanks a lot to rovo89 for the beta4!!!
xposed-v90-sdk26-arm64-beta4-test1.zip works fine on SHT-AL09 after flashing it via TWRP
What we need:
ROOT
TWRP
Flash with TWRP View attachment xposed-v90-sdk26-arm64-beta4-test1.zip
Install View attachment XposedInstaller_3.1.5.apk
PROFIT!
{
"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"
}
ZeuseZ said:
Thanks a lot for the link! Thanks a lot to rovo89 for the beta4!!!
xposed-v90-sdk26-arm64-beta4-test1.zip works fine on SHT-AL09 after flashing it via TWRP
What we need:
ROOT
TWRP
Flash with TWRP View attachment 4525802
Install View attachment 4525805
PROFIT!
View attachment 4525804
Click to expand...
Click to collapse
A lot of Xposed modules do not work. GravityBox, which is my favorite, completely f*ked up the rom - had to reflash. Tried a couple of others - didnt break things, but didnt work either. It's dangerous to try these modules, because TWRP restore doesn't really work.
If I'm not mistaken, in the event of a bad module, Xposed can be disabled at boot by pressing a hardware key over and over again. Not that I want to find out.
Anyways, Edge and Edge Pro work. They don't remap the fingerprint sensor functionality. But they have other useful features.
thref23 said:
If I'm not mistaken, in the event of a bad module, Xposed can be disabled at boot by pressing a hardware key over and over again. Not that I want to find out.
Click to expand...
Click to collapse
Which hardware key would that be? And what exactly does "over and over again" mean - how many times or for how long?
Apo11on said:
Which hardware key would that be? And what exactly does "over and over again" mean - how many times or for how long?
Click to expand...
Click to collapse
Any key. This must be where I read it:
https://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
Lukest85 said:
While the device boots you can activate the xposed safemode to disable the framework & modules, without flashing any files and without entering recovery or ROM.
Background:
People are posting when stuck at boot screens or bootloops with xposed installed and there have been lots of great solutions/advice from the community but I have not seen much info posted about the xposed safemode so thought I would share what I believe to be the easiest & first thing to try in order to boot & troubleshoot your setup.
To disable xposed:
1. Repeatedly press any single hardware button during early startup (as soon as device powers on)
2. Wait for device to finish booting into recovery/ROM
3. Fix your setup
Details:
1. The first recognised key press generates two vibrations
2. Then continue to press the same hardware button four more times within 5 seconds
*Each key press generates a short vibration*
3. Success is confirmed with a long vibration
NB
• Activating safemode adds the file 'disabled' (no quotes) to data/data/de.robv.android.xposed.installer/conf/
• The 'disabled' file can be created manually from recovery or rom to disable xposed & modules
• If problems with hardware buttons try pressing the touchscreen to activate safemode
To re-enable xposed:
1. Remove the file 'disabled' using file manager or terminal
2. Reboot
3. Enjoy
***common reasons for xposed related bootloops are due to xposed module/s conflicting with system or each other, and user installing the incorrect framework for the device/sdk. Please investigate these options first and read/search the xposed Q&A OP/thread if you're unsure before posting or contacting devs***
xposed Q&A thread:
http://forum.xda-developers.com/showthread.php?t=3030118
Disclaimer:
**I cannot guarantee safemode works with every version of xposed or every device but it has always worked for me on differing setups, roms & devices.**
I hope this is helpful and will be updating the post again so stay tuned for more detailed/technical info.
Give thanks to talented & amazing devs: @Tungstwenty - xposed safemode @romracer - xposed @rovo89 - official xposed
Fantastic work & great dedication !!!
Click to expand...
Click to collapse
thref23 said:
Any key. This must be where I read it:
https://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
Click to expand...
Click to collapse
That's not really helpful in our case. It says to keep pressing and then it will boot into recovery. Step 3 says "Fix your setup" . If TWRP is not working properly (and that's exactly point - it does not, so there is no fixing) there is no benefit in booting into the recovery. Doing stuff like clearing cache does nothing when Xposed module screws up the rom. Not to mention you dont really need this Xposed "feature" in order to boot into recovery or download mode. You can just shut down your device and then use the regular, designated hw key combination in order to boot into either.
Apo11on said:
A lot of Xposed modules do not work. GravityBox, which is my favorite, completely f*ked up the rom - had to reflash. Tried a couple of others - didnt break things, but didnt work either. It's dangerous to try these modules, because TWRP restore doesn't really work.
Click to expand...
Click to collapse
TWRP restore works fine for me.
magnumlove said:
TWRP restore works fine for me.
Click to expand...
Click to collapse
You have different M5 model than mine - the 10" if I recall correctly. Partition table and a bunch of other things are not the same. You have the same or very similar model as the OP from that twrp thread, so it's not surprising the recovery works for you. If someone with SHT-AL09 says the restore works for them - that's a different story, and I'd have to start troubleshooting my own device. As of this moment, I think this recovery build is not fully compatible with 8.4" LTE version. It's failing to mount /system and /vendor partitions, and after some troubleshooting I've done I can see there are 4 versions of mount binary on my device. For example, when I manually invoke the one in /sbin folder - I can do "mount -o remount,rw /system" just fine, but when I try the same with mount version from /system/bin folder - it fails. And there is 2 more of them. It's not clear which one twrp is using when it's trying to mount partitions for restore, but it's obviously the wrong one. The only way I see to fix this is to recompile twrp.
I have the SHT-AL09. When I was bootlooped (I was actually more bricked than bootlooped), I installed TWRP, and I could not mount anything (except my SD card) as read/writeable.
After the equivalent of a factory reset, I installed TWRP, and it seems to work perfectly.
I have not tried to restore a backup. But I wonder if doing so would work after the equivalent of a factory reset, if not while bootlooped.
thref23 said:
I have the SHT-AL09. When I was bootlooped (I was actually more bricked than bootlooped), I installed TWRP, and I could not mount anything (except my SD card) as read/writeable.
After the equivalent of a factory reset, I installed TWRP, and it seems to work perfectly.
I have not tried to restore a backup. But I wonder if doing so would work after the equivalent of a factory reset, if not while bootlooped.
Click to expand...
Click to collapse
"seems to work perfectly" and "I have not tried to restore a backup" are contradicting statements in this context. "seems" sounds like a guess. If you want to be about 95% sure it will work -boot into twrp, goto Advanced->Terminal and type "mount". Examine if your /system and /vendor partitions are mounted as "ro" or "rw" - if it's ro then your restore is likely to fail. Needless to say, to be 100% sure you have to actually attempt a restore. Make certain to decrypt your /Data using PIN/password when twrp prompts you, otherwise you will get screwed. TWRP doesn't need to decrypt in order to wipe, and it wipes the /Data partition before every restore. If you don't decrypt and attempt restore - /Data will get wiped, but then the /Data restore will fail, because it's encrypted. In that case, theoretically you should be able to boot into twrp again, and it should prompt you for PIN /password to restore /Data again. Once you provide it and successfully decrypt - you should be run the restore again and restore the missing /Data partition from nandroid backup.
Apo11on said:
"seems to work perfectly" and "I have not tried to restore a backup" are contradicting statements in this context. "seems" sounds like a guess. If you want to be about 95% sure it will work -boot into twrp, goto Advanced->Terminal and type "mount". Examine if your /system and /vendor partitions are mounted as "ro" or "rw" - if it's ro then your restore is likely to fail. Needless to say, to be 100% sure you have to actually attempt a restore. Make certain to decrypt your /Data using PIN/password when twrp prompts you, otherwise you will get screwed. TWRP doesn't need to decrypt in order to wipe, and it wipes the /Data partition before every restore. If you don't decrypt and attempt restore - /Data will get wiped, but then the /Data restore will fail, because it's encrypted. In that case, theoretically you should be able to boot into twrp again, and it should prompt you for PIN /password to restore /Data again. Once you provide it and successfully decrypt - you should be run the restore again and restore the missing /Data partition from nandroid backup.
Click to expand...
Click to collapse
Without rebooting back into TWRP, I think all partitions are mounted r/w. Previously, if I unchecked 'mount system partition read only,' it would stay checked - not anymore. And I was able to successfully flash Xposed. That's what I mean by "seems to work perfectly."
I have TWRP backups now, that I hope I never have to try and restore. For now I'd much rather leave well enough alone than to be 100% certain. Plus I kind of hate rebooting.
thref23 said:
I have the SHT-AL09. When I was bootlooped (I was actually more bricked than bootlooped), I installed TWRP, and I could not mount anything (except my SD card) as read/writeable.
After the equivalent of a factory reset, I installed TWRP, and it seems to work perfectly.
I have not tried to restore a backup. But I wonder if doing so would work after the equivalent of a factory reset, if not while bootlooped.
Click to expand...
Click to collapse
Restore works fine from EMUI to EMUI. I had issues when trying to restore back to EMUI from a GSI-TWRP hung on the splash screen. Managed to restore in the end after flashing stock system img. All my back ups were made with PIN screenlock removed.
Apo11on said:
A lot of Xposed modules do not work. didnt break things, but didnt work either
Click to expand...
Click to collapse
same here, most modules don't work, has anyone found a solution?
Si73 said:
Restore works fine from EMUI to EMUI. I had issues when trying to restore back to EMUI from a GSI-TWRP hung on the splash screen. Managed to restore in the end after flashing stock system img. All my back ups were made with PIN screenlock removed.
Click to expand...
Click to collapse
I don't have screenlock but I haven't managed to create any backup, because of the famous 255 error
I've got huawei mediapad m5 lite (bah2-w19)
Related
CleanViewpad7 v1.0
based on latest official stock Viewpad 7 firmware Android 2.2.2
{
"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"
}
With installed ADW Launcher EX:
This build is for Viewsonic Viewpad 7. I’ve made this build mainly because I had one big problem with stock one – it was offering little space for my apps. I've used this opportunity to add extra features and remove some annoying ones. Here is the list of changes:
based on latest official stock Viewpad 7 firmware Android 2.2.2
added Darktremor Apps2SD 2.7.5.2 functionality (require that you have extra partition on your SD card for storing your apps; exact procedure to create one is described in installation procedure)
fully deodexed and zipalligned ROM
ROM is rooted (Superuser.apk + su)
installed BusyBox with support for init.d scripts
replaced "Welcome" boot animation with stock android 2.2 animation
installed Gingerbread keyboard
installed Morelocale2 for more languages
modified framework-res.apk and services.jar with Gingerbread look like + % battery
removed Aldiko,RSS, TouchPAL_M20
updated gapps to newest version (Gmail, GoogleQuickSearchBox, Maps, Market, VoiceSearch) & YouTube
modified host file for ad-free
Now you don’t have to worry about decreasing internal storage when you install more application. You don’t also lose access to application when you phone is connected in drive mode to computer, because application data is being hold on ext3 partition on SD card. That partition isn’t mounted when your phone is connected to computer. The things that are redirected to this partition are: /data/app, /data/app-private and /data/dalvik-cache. Firmware should also work with compatible devices such as: Cherry Mobile Superion, Commtiva Linx N700, Olivepad VT-100, Spice MI700, and Camangi FM600 but I don't have these devices, so I cannot verify. As always make a backup before installing any custom firmwares.
Requirements:
installed Clockwork Recovery Partition as described here [TOOL] Viewpad 7 Backup, Root & Recovery
Changelog:
V1.0
initial release
Installation:
Power down your device.
Power on device holding power button and both volume keys simultaneously.
Upon power up you will see the birds logo and 'enter recovery' text in the top left corner of the screen.
Use the volume keys to step through the menu, power to select and back. (there is bug in clockwork when you press volume keys it jumps 2 steps; to jump one step press and hold volume and then press power to select)
Select the "advanced->Partition SD Card" item, next select size for your Apps2SD partition (1024MB recommended), next select 0 as size of swap partition. (Remember that this will delete all data on your SD card, so make backup of SD card if you need !!!)
After the partitioning will be done select the "reboot system now" item.
Using USB cable connection or SD card reader copy CleanViewpad7_signed_v1.0.zip to root folder of SD card.
Power down your device.
Power on device holding power button and both volume keys simultaneously.
Select the "backup and restore->Backup" item to make a backup of the current firmware in case something goes wrong. The backed up ROM should be located in: /sdcard/clockworkmod/backup/date&time/
Select the "wipe data/factory reset->Yes – delete all user data” to clear old stuff.
Select the "install zip from sdcard->choose zip from sdcard" item and select CleanViewpad7_signed_v1.0.zip.
After flashing will be done select the "reboot system now" item. First boot may take a few minutes.
Migrate from stock or another build:
Make backup of your phone using Titanium Backup (select all user applications).
Copy all files and folders from SD card to local folder on your computer.
Install Clockwork Recovery Partition, create partition on SD card and install ROM as described in installation guide.
Copy all files and folders from local folder on your computer back to SD card.
Restore applications using Titanium Backup and reboot your phone.
Download:
http://www.multiupload.com/79WKJUXMX5
Credits to:
Darktremor
hucqim80
dsixda
mendozinas
-Mr. X-
If you like my work please consider donating:
Thanks everyone for donations.
Nice work bro.although it would be better to use the latest a2sd version of darktremor(2.7.5.3)
which supports ext4 partition and data2sd feature.so instead of adding a2sd 2.7.5.2 you can provide a link to the flashable zip of the latest DT-a2sd (http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip). it works i have tested it.
hi
thanks i have downloaded this from ur tablet rom post
thanks a mill this is exactly what i want will use the same give u a feedback on the same
thanks
hari
works on Olivepad VT-100
hi
this is FYI for Olivepad VT-100 users
i have Flashed this ROM and works for Olivepad VT-100
thanks for this nice rom ill give a feed back latter as i have just installed the same
Feedback
not sure if the apps are getting installed on the SD the first time i installed the ROM i did a data/factory reset
installed the rom and i had only 118MB phone storage(i have the ext partition done before stating the process)
ok then i re in stalled rom again and i still see 118 MB so i tried installed skype its a 7MB file but still i see 1MB used on the phone
not confy with titanium and i have a similar rom installed on my samsung galaxy 3
on that all i do is install the new rom without any wipe and the same works
kindly advise on the same as i really would like the apps2SD working
thanks
hari
googlehome said:
Nice work bro.although it would be better to use the latest a2sd version of darktremor(2.7.5.3)
which supports ext4 partition and data2sd feature.so instead of adding a2sd 2.7.5.2 you can provide a link to the flashable zip of the latest DT-a2sd (http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip). it works i have tested it.
Click to expand...
Click to collapse
hi
i installed this attachment on ur ROM via CWM and bang i got 154MB free on phone Storage and i can see than all installed app are on my SD so i would like to confirm that this works
one small request im more confy with the Touchpad keyboard i did try installing the one i had of the original rom its getting installed but im not getting an option to use it i think because ur apps are deodexed and the official on coming on stok rom is only odexed can any one help on this pls
but thanks now i got exactly what i want
hari
I have had huge issues getting this to flash properly, keep getting to the 3 birds and no further...followed your steps exactly...1gb ext part thru cwm and wiped everything...would flashing from another custom rom affect this ? should i try from stock maybe?
joethc said:
I have had huge issues getting this to flash properly, keep getting to the 3 birds and no further...followed your steps exactly...1gb ext part thru cwm and wiped everything...would flashing from another custom rom affect this ? should i try from stock maybe?
Click to expand...
Click to collapse
hi
i flashed from stock ROM
try flashing from stock rom it should work
flashed back to stock, rooted, flashed cwm through adb shell, reboot to recovery, wipe data /factory reset...install cleanviewpad7 signed zip and it still sticks at the 3 birds gets no further after waiting 10mins one time and 20 the next....any other ideas? I dont know why this is not working for me...I can flash other roms no problem using sut or cwm.....it seems to be flashing the file really fast ...open to anything i really want to get this going
hi buddy
i tried to help with what ever limited knowledge i had based on my experience
sorry im not a techie i just go by the instructions given and do it
even yesterday i flashed another rom and re flashed this one everything went well for me
so sorry i think on one of the developer can help u as i dont seem to understand why u are having this problem sorry im not able to help u
joethc said:
flashed back to stock, rooted, flashed cwm through adb shell, reboot to recovery, wipe data /factory reset...install cleanviewpad7 signed zip and it still sticks at the 3 birds gets no further after waiting 10mins one time and 20 the next....any other ideas? I dont know why this is not working for me...I can flash other roms no problem using sut or cwm.....it seems to be flashing the file really fast ...open to anything i really want to get this going
Click to expand...
Click to collapse
joethc said:
flashed back to stock, rooted, flashed cwm through adb shell, reboot to recovery, wipe data /factory reset...install cleanviewpad7 signed zip and it still sticks at the 3 birds gets no further after waiting 10mins one time and 20 the next....any other ideas? I dont know why this is not working for me...I can flash other roms no problem using sut or cwm.....it seems to be flashing the file really fast ...open to anything i really want to get this going
Click to expand...
Click to collapse
Remember to wipe your data,cache as well as dalvik cache before flashing the rom.
i followed step by step. once booted it showed android setup but touch screen wasnt working. any one know why? i am using viewpad 7. thanks in advance
smargarites said:
i followed step by step. once booted it showed android setup but touch screen wasnt working. any one know why? i am using viewpad 7. thanks in advance
Click to expand...
Click to collapse
hi
have u rooted added CWM & busy box only on doing these can u flash this roms
it worked on my Olivepad so im quite sure it will work for u
I still can not get this going I have tried a billion different things..wiped everything stock, still no luck. The only other time I have had this issue is an incomplete upload but if everyone else has it working from this specific upload i dont know what to say ...ill keep trying and hopefully get it soon Thanks everyone for the quick responses!!!!! Is there a way to get this packaged to flash with sut l3?
FlashoManiac said:
hi
have u rooted added CWM & busy box only on doing these can u flash this roms
it worked on my Olivepad so im quite sure it will work for u
Click to expand...
Click to collapse
yes i have it rooted. what i had to do was boot the stock rom boot.img with this rom. working great right now.
I followed the directions in the first post and then downloaded the file from post#2.
Once you have the file from post #2 on your SD card, rename it to update.zip and then boot your device into Clockwork Recovery and select the "update from zip" option. Rebooted and my device now has 167MB of available space on the internal phone storage.
Thanks guys... this is the way the device should have shipped from Viewsonic, and although it aint no Gingerbread, I'm finally happy with my Viewpad after several months if dissapointment.
One thing that I find to be very strange is that it appears that some data is saved somewhere?
Even after I performed the following:
Formatting the SD Card
Wipe data/factory reset
Wipe cache partition
Wipe dalvik cache
Load the new ROM
Did not log into any kind of google account and basically skipped all the setup options.
The device still shows all the wireless hotspot data that I logged into before. Why does it have the password for my WiFi router after all those steps were performed.
If I were to sell the device to someone else, is there any way to be sure ALL data has been cleared from the device?
Cheers!
Great work, good to see another ROM for the Viewpad!!!
Will for sure try it...
A few questions:
You are using the a2sd version of darktremor(2.7.5.3), I personally use Link2SD which also moves all data, cache,... to the 2nd partition of the SD card...
It's actively developed and it's free, so check it out...
Is this ROM with the kernel from tj-style? Then we can overclock to 824Mhz and it gives a nice speed boost...
If then you do not want to use it for your ROM, you can set it to the stock speed with SetCPU...
Thanks,
Nick
Since many people are requesting for TJstyle's oc'd kernel.I modified this ROM to add the kernel and some other stuff.
Here is the download link:
http://dl.dropbox.com/u/21654931/VPAD7_signed.zip
My quadrant score crossed the 1000 mark for the first time
Screenshot:
googlehome said:
Since many people are requesting for TJstyle's oc'd kernel.I modified this ROM to add the kernel and some other stuff.
Here is the download link:
http://dl.dropbox.com/u/21654931/VPAD7_signed.zip
My quadrant score crossed the 1000 mark for the first time
Screenshot:
hi
thanks flashed this it works on a Olivepad
can u kindly give me the same with the touchpad keyboard as i was not able to install the same on the previous rom. haven't tried on ur rom will try and keep u posted. May be in future u could start a separate rom thread for ur roms
thanks for the nice rom like the battery indicator
Click to expand...
Click to collapse
Worked perfect here! I love the boot animation! This is exactly what i needed! many thanks to everyone here for helping out!
Have installed this rom and the dark tremor update but my phone storage is still decreasing when I install apps. I have set up an ext 4 partition on my sd card.
:'(
LegoKernel - With F2FS
NOTE This kernel version doesn't support "All-F2FS"
This is a Kernel for Android 4.4. I made this for SlimKat so i don't know if this will work with other roms.
Some users reported working also on:
Cyanogenmod (Reported by: buggatti)
Carbon (Reported by: Nosterius)
OmniROM (Reported by: SkOrPn)
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
The idea was of ss2man44. F2FS helps Nexus 7 2012 where he needs: IO Speed and slowdown after long period (months?) of use. This Filesystem is used in others phone too like Moto X where he shows good performance.
I tested this myself for some weeks without problems and i'm happy.
I started from the stock Slim kernel.
There are also others features by me:
Ported sl[aou]b from Linux 3.4
Ported timer and workqueue from Linux 3.4
Ported random from Linux 3.13-rc4
Ported rwsem from Linux 3.11
Kernel NEON Mode
Etc..Etc..
Added GPU OC (Franco way..)
Added Toggle for FSYNC
Revert CPU OC things (We don't need it and it was a bit dirty..)
Instructions:
I already said that i did this for SlimKat so my advice is to start this procedure with a working SlimKat rom or another rom that is reported to work good. (See the start of this post)
F2FS is a Filesystem so we have to Format our memory in this mode. How can we do this? We need a "special" TWRP and LegoKernel
Download LegoKernel LegoKernel-F2FS-140228
Download "special" TWRP recovery-F2FS-A.img
Copy LegoKernel on Tablet
Flash LegoKernel with your current Recovery
Flash "special" TWRP with Fastboot
I said "FORMAT" so it's obvious that you will lose all your data (even Movies..Music..all!). Backup them on PC to restore easily at the end.
Now..
Reboot in Recovery (To know that you are on "special" TWRP note that the BackKey is Red at the bottom-right)
Go to Wipe menu
Format Data (Not the simple Wipe!)
Reboot
Enjoy. (Now you may want to restore your backup)
Report back how do you feel your tablet now. I have a very positive opinion about this thing!!
Changelogs:
- 28/02/13: Add Kexec Support
Some thing you have to know:
After the switch to F2FS you can use only kernel with F2FS Support
Backup made with standard TWRP may not work with "special" TWRP and reverse.
How come back?
Flash a standard TWRP
Format Data
Flash your previous ROM/Kernel
Reboot
Github
It's great that someone else beside sgt.meow (Oxydo kernel) picked up ss2man44's idea. :good:
working great with cm 11
and Thank a lot for adding fsync off.. NOW THE NEXUS 7 FLIES
MultiROM v22a - With F2FS
I have adapted Tassadar MultiRom to work with F2FS. (All credits to him)
You need:
Its Multirom zip. Here
Kernel with F2FS Support and Kexec Support
(As now LegoKernel-F2FS-140228 is the only LegoKernel that work with MultiROM)
TWRP with F2FS Support and MultiROM. Here (For Grouper)
TWRP with F2FS Support and MultiROM. Here (For Tilapia)
If you already switched to F2FS:
Move Multirom zip and Kernel to your tablet
Flash TWRP with F2FS Support and MultiROM with Fastboot or Flashify
Reboot in Recovery
Flash Kernel
Flash MultiROM zip
Reboot
If you didn't switch to F2FS and want to do it now:
Copy Kernel to your tablet
Flash Kernel with your current Recovery
Flash TWRP with F2FS Support and MultiROM with Fastboot
Reboot in Recovery
Format Data in Wipe menu (you will lose all your files!!) Not the simple Wipe!
Reboot
Copy MultiROM zip to your tablet
Reboot in Recovery
Flash MultiROM zip
Reboot
Some things you have to know: (READ THEM)
All your ROMs must support F2FS so if you want to use "normal" ROMs you have to "share kernel"
I have tested this with SlimKat as Primary and CM11 as other ROM
I think i did some errors writing all the procedures. Hope they are right now.
Hi,
this mod works well for me on my Nexus 7 3G running CyanogenMod 11. I've been running this just for a few hours, but the filesystem performance seems much better, my N7 no longer lags when installing apps, which it did before.
The only problem, or rather inconvenience, I had is that the recovery is not made for the N7 3G, so it won't install ROMs and stuff made for tilapia, as it expects them made for grouper. It would be cool to have a tilapia version of the recovery, or some instructions in the OP on how to use it there.
If you want to use this mod on tilapia, you have to:
Install the special recovery by legolas93 from the first post.
Format /data from within the recovery (format, not just wipe).
Install back a recovery made for tilapia and DO NOT FORMAT /DATA!
Install your ROM/gapps/hippo/etc.
Flash the modified kernel from the firts post.
Anyway, big thanks to legolas93 for doing this. Have you also considered making /system and /cache as f2fs? Do you think it would have any significant benefits?
Hmm, well I decided to try this as well, however after flashing the kernel I sat it down for a few minutes so I could fire up my laptop (it has Fastboot on it) and when I came back to the tablet it was turned off. I turned it on and now out of the blue its asking for a password to decrypt the storage?
I have ran CM11 for the past year on it and purchased it brand new from Google last January. However, after trying my Google email password it is still asking for a password.
Anyway, I decided to do a full wipe, installed CM11 2/28, LegoKernel and Gapps. And upon rebooting its still taking me to a screen asking for a password. Anyone know why it would spontaneously ask for a password? is there a default password I am supposed to use with this kernel by chance? lol, I am at a loss and I usually have everything under control grr haha
EDIT:
CM11 2/28 is installed
Latest LegoKernel
Latest PA_Gapps
And I have not been able to flash the latest TWRP on it yet. But I do have the latest TWRP (MultiROM version) on it.
EDIT: #2, Ok I managed to use Fastboot on my laptop and I flashed the special TWRP. I went a head and re-wiped factory-reset and also re-flashed the CM11 rom and the latest LegoKernel, but after a reboot its still asking for some unknown password. Why would it need a password all of a sudden?
SkOrPn said:
Hmm, well I decided to try this as well, however after flashing the kernel I sat it down for a few minutes so I could fire up my laptop (it has Fastboot on it) and when I came back to the tablet it was turned off. I turned it on and now out of the blue its asking for a password to decrypt the storage?
I have ran CM11 for the past year on it and purchased it brand new from Google last January. However, after trying my Google email password it is still asking for a password.
Anyway, I decided to do a full wipe, installed CM11 2/28, LegoKernel and Gapps. And upon rebooting its still taking me to a screen asking for a password. Anyone know why it would spontaneously ask for a password? is there a default password I am supposed to use with this kernel by chance? lol, I am at a loss and I usually have everything under control grr haha
Click to expand...
Click to collapse
Did you format the /data partition with the modified recovery? This happens when Android can't access the /data partition, in this case very probably because there is a mismatch between the filesystem on /data (ext4) and the filesystem the kernel expects (f2fs). You have to first format the /data partition so it would have f2fs.
frantisek.nesveda said:
Did you format the /data partition with the modified recovery? This happens when Android can't access the /data partition, in this case very probably because there is a mismatch between the filesystem on /data (ext4) and the filesystem the kernel expects (f2fs). You have to first format the /data partition so it would have f2fs.
Click to expand...
Click to collapse
I cant remember now if I did or didn't format /data. I remember formatting everything except for OTG I think, lol.
Anyway, I used NRT and put the device back to stock, then I installed the modified F2FS TWRP recovery. Now I have the modified Recovery installed, and a fresh stock rom rooted with usb debug enabled. I just finished downloading the latest CM11 Rom and the LegoKernel and put it into my freshly formatted sdcard. I am sitting in TWRP at this moment but worried about flashing the kernel again. haha
Going to try again. Will report back. But first, let me make sure I have this right since I am trying to flash a ROM at the same time now.
1st. Flash the CM11 ROM
2nd. Flash the LegoKernel
3rd. Format /data???
4th. Flash Gapps?
I am almost certain I did this before, that's why I am asking.
SkOrPn said:
1st. Flash the CM11 ROM
2nd. Flash the LegoKernel
3rd. Format /data???
4th. Flash Gapps?
Click to expand...
Click to collapse
That should do it. Remember, you have to format /data, just wiping is not enough. And you'll have to flash gapps via sideload, because formatting /data also removes everything on /sdcard.
Personally, I'd format /data first, just to be sure you don't delete a part of the CM11 ROM after installing, but I think CM11 recovery zip doesn't flash anything into /data anyway, so it doesn't matter.
frantisek.nesveda said:
That should do it. Remember, you have to format /data, just wiping is not enough. And you'll have to flash gapps via sideload, because formatting /data also removes everything on /sdcard.
Personally, I'd format /data first, just to be sure you don't delete a part of the CM11 ROM after installing, but I think CM11 recovery zip doesn't flash anything into /data anyway, so it doesn't matter.
Click to expand...
Click to collapse
Ok, that must be what I am doing wrong then. I somehow was not aware that wiping /data was not going to do it. I did the above but I wiped /data and now I am back to the password screen yet again. Not sure if I have to go all the way back to stock again or not now.
SkOrPn said:
Ok, that must be what I am doing wrong then. I somehow was not aware that wiping /data was not going to do it. I did the above but I wiped /data and now I am back to the password screen yet again. Not sure if I have to go all the way back to stock again or not now.
Click to expand...
Click to collapse
It will be enough if you now just format /data and flash gapps again. You probably never had to go back to stock anyway, I didn't and everything went well.
frantisek.nesveda said:
It will be enough if you now just format /data and flash gapps again. You probably never had to go back to stock anyway, I didn't and everything went well.
Click to expand...
Click to collapse
Yeah everything seems OK now. Just waiting for Google to re-install all my apps. Wish I had realized there was a difference between wipe and format, and that the format data button is just staring you in the face too. lol
Thanks for your help bud. :good:
SkOrPn said:
Yeah everything seems OK now. Just waiting for Google to re-install all my apps. Wish I had realized there was a difference between wipe and format, and that the format data button is just staring you in the face too. lol
Thanks for your help bud. :good:
Click to expand...
Click to collapse
You're welcome. Glad I helped.
frantisek.nesveda said:
Hi,
this mod works well for me on my Nexus 7 3G running CyanogenMod 11. I've been running this just for a few hours, but the filesystem performance seems much better, my N7 no longer lags when installing apps, which it did before.
The only problem, or rather inconvenience, I had is that the recovery is not made for the N7 3G, so it won't install ROMs and stuff made for tilapia, as it expects them made for grouper. It would be cool to have a tilapia version of the recovery, or some instructions in the OP on how to use it there.
If you want to use this mod on tilapia, you have to:
Install the special recovery by legolas93 from the first post.
Format /data from within the recovery (format, not just wipe).
Install back a recovery made for tilapia and DO NOT FORMAT /DATA!
Install your ROM/gapps/hippo/etc.
Flash the modified kernel from the firts post.
Anyway, big thanks to legolas93 for doing this. Have you also considered making /system and /cache as f2fs? Do you think it would have any significant benefits?
Click to expand...
Click to collapse
Sorry. I dind't have time to do the tilapia recovery. But now i have just uploaded a TWRP Recovery with F2FS and MultiROM for Tilapia! Let me know if it is ok
I think that TWRP need some non-trivial edits from TWRP-guys to be able to use /system and /cache as f2fs. Anyway i don't think that we will gain some big benefits because..
- /cache is used very little..maybe only by recovery (i'm not 100% sure..)
- /system is used only by reading from it 99% of time so i dubt that we will gain some major benefits
Even Moto X use f2fs only for /data partition, maybe this is the best way to use it!
hows the battery life on this kernel, plus im running Kang-aroo kernel which mean ill lose all of the neat tweaks it supports, will you be adding tweaks and mods to this kernel or is this minimum version going to be how it stays moving forward.
Wtf
{
"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"
}
Enviado desde mi Nexus 5 mediante Tapatalk
Why does it keep taking me back to the multirom menu when ever I boot it up ? You sure the kernel supports kexec-hardboot ?
Edit : Looks like flashing the kernel again after flashing the multirom fixed it.
Fransis88 said:
Wtf
Click to expand...
Click to collapse
Did you format /data with the modified TWRP? Remember, you have to FORMAT, not just wipe. And if you are really absolutely sure you did format, try flashing the kernel again.
Fransis88 said:
Wtf
Enviado desde mi Nexus 5 mediante Tapatalk
Click to expand...
Click to collapse
You failed to use the format button. I did the exact same thing. All you have to do now is go back into the modified TWRP and use the "format data" button. It will work perfectly after that.
Sent from my Nexus 7 using Tapatalk
Depreciated!! See this thread for the new recommended package. All of my instruction below is still valid, just use the new package from thread linked here.
http://forum.xda-developers.com/showthread.php?t=3234422
~~DISCLAIMER~~Flashing roms, kernels, and mods come with NO guarantee, NONE, ZILCH, NADA . . Do NOT use this package if you do not grasp and understand this concept. You have been warned.
This is a recovery flashable that will extract your boot.img, unpack all pieces, modify fstab.shamu to disable forced encryption, repackage, and flash boot.img back to system. It does NOT actually unencrypt your device. More on that later.
It will work on ANY kernel for this device, regardless of whether it is the stock kernel, or a custom ROM kernel. Also to date, it has shown to work on any version of android . . it is essentially future proof (unless google throws us a major curve ball in the future and radically alters how encryption is triggered at first boot).
Why use this? Who is this package for?
-If you are running 100% Stock Rom, but have a recovery installed and wish to unencrypt your storage. No root needed.
-Running a custom kernel you like, but it forces encryption and you want to change that.
-Currently unencrypted but want to flash a rom that uses FORCEENCRYPTION by default (cyanogenmod12).
-Just bored and want to toss the dice and see what happens.
That is pretty sweet right? Now you can flash anything and as long as you flash this afterwords, you wont have to worry about booting a rom and seeing that dreaded "Encrypting" screen anymore.
What doesn't this do?
-Well, to be blunt . . it does NOT actually UNENCRYPT your device. You will have to bite that bullet on your own, but I will offer some advice on that front later.
Changelog:
03/30/2015
Remove my ill advised attempt to auto patch nightlies, not possible
01/12/2015
Initial Build/Release
Includes fully working patch to initrd, specifically fstab.shamu to revert FORCEENCRYPTION by default.
Buglist:
Auto patch support removed, would never work anywayaddon.d support not currently working - fix is to flash this package with every nightly to preserve unencryption
How to download and install?
Download - NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip
Reboot Recovery - TWRP only has been tested as working
Select "Install" and navigate to where ever you stored that file . . likely /sdcard/downloads/
Take a deep breath and wait for it to finish.
TADA . . done. Reboot and Profit!!
NOTE: You can feel free to flash this as part of a line of other packages.
Example: You are already unencrypted and want to flash Cyanogenmod 12 (assumes you have all packages downloaded already)
-TWRP factory reset (optional but recommended when coming from another rom)
--TWRP's built in factory reset function does quite well, but if you are like me and want a clean slate . .
---TWRP>Wipe>ADVANCED WIPE> and check System, Data, Cache (will leave internal storage intact). This is recommened specifically in conjunction with switching GApps.
-Install> and select all packages at once. I recommend the following order . . Rom, then my Kernel Patcher, then SuperSU (optional), then GApps last.
That was certainly easy right? Well the truth is, unless you are already unencrypted . . nothing will be different. You will still be encrypted. Bummer right? But that is where these next steps come in. They will give you the options available to reach the fabled unencrypted status!!
Below are the only three options I know of unencrypt once you are running a patched kernel. Select one below that works for you.
~~WARNING~~
The below methods WILL erase EVERYTHING from data, including your INTERNAL STORAGE. Backup all important files, pictures, etc before proceeding. You have been told!!
-Go to Android>Settings>Backup & restore>Factory data reset (may not work properly with a custom recovery installed)
-Reboot to recovery and go to TWRP>Wipe>FORMAT DATA . . type "yes" to confirm
-Reboot to bootloader and type . .
Code:
fastboot format userdata
[note - I originally said to use the fastboot erase userdata function. This caused a recovery bootloop. Switching to "format" instead solved this issue. Thanks @aussie1234 for pointing this issue out to me]
Edit: make sure you boot android first after unencrypting before going into recovery. This will allow the proper creation of multiuser partitions, otherwise, twrp will not use the proper /data/media/0/ as root of storage.
Some may notice there is an experimental addon.d included. This NOT WORKING YET. DO NOT TRY AND USE IT. Not quite sure yet where in the chain it is broken, but that will be a problem for another day. In theory it should, but . . read the "disclaimer" at the top of this post. The idea here is to be able to flash nightlies as they roll out without having to re-apply this patch manually every time. This function is NOT supported on Stock Roms. If you try it and it works, let me know. Do NOT come yelling to me that it did not work and crying that you are now encrypted again. No whiner babies allowed.[REMOVED: didn't work and caused conflicts with some packages]
At the core of this tool is a script build by @dk_zero-cool which can be found . . [DEV][INITRD][2013-10-25] Injector - An Android Ramdisk Injection Tool
Ultimately, this package is as much his as it is mine. It is his magic script that did the hard part, I just put it to work in a new way.
Please don't share this package directly, link them back here if needed. That way, they can get proper support and instruction for its use.
Also thanks to @rascarlo . . his github made it easy to find what needed modded.
Nice! Now just to double check, im unencrypted so if i flash cm12 and this cm12 wont encrypt my phone while still using cm's kernel?
That is correct. In my tests it has worked just fine that way.
Edit: In fact, I just tested this exactly and works as expected.
On a side note, I can confirm that addon.d support does NOT work - do not attempt it. I updated the OP to reflect this and add a stronger warning. Right now you MUST flash this everytime you flash a rom that forces encryption.
Just what the doctor recommended for a flash-addict like my self....
Thanx :silly:
. . . uploaded from a hand-held Killer WHALE
Works like a charm much alohas bradah hixanthus
So say I flash a ROM. I want to do ROM, kernel, your boot.IMG, the gapps followed by a factory reset/erase user data if I understand correctly?
Example : DirtyUnicorns then leankernel your zip and then gapps
bmwh0r3 said:
So say I flash a ROM. I want to do ROM, kernel, your boot.IMG, the gapps followed by a factory reset/erase user data if I understand correctly?
Example : DirtyUnicorns then leankernel your zip and then gapps
Click to expand...
Click to collapse
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
hlxanthus said:
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
Click to expand...
Click to collapse
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
bmwh0r3 said:
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
Click to expand...
Click to collapse
Just do the factory rest then if already encrypted unless data is removed it will stay encrypted
Sent from my Nexus 6 using Tapatalk
hlxanthus said:
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
Click to expand...
Click to collapse
bmwh0r3 said:
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
Click to expand...
Click to collapse
hlxanthus said:
Below are the only three options I know of unencrypt once you are running a patched kernel. Select one below that works for you.
~~WARNING~~
The below methods WILL erase EVERYTHING from data, including your INTERNAL STORAGE. Backup all important files, pictures, etc before proceeding. You have been told!!
-Go to Android>Settings>Backup & restore>Factory data reset
-Reboot to recovery and go to TWRP>Wipe>FORMAT DATA . . type "yes" to confirm
-Reboot to bootloader and type . .
Code:
fastboot erase userdata
Edit: make sure you boot android first after unencrypting before going into recovery. This will allow the proper creation of multiuser partitions, otherwise, twrp will not use the proper /data/media/0/ as root of storage.
Click to expand...
Click to collapse
https://github.com/imoseyon/leanKernel-shamu/commit/58ac4f97d882414bdea35d0d1ef0cd6f9027a3bb
Yes, lean kernel doesnt force encryption. If you are currently on lean kernel, so one of the three methods to unencrypted from above (quoted from my OP)
This worked great for me! Thank you SO much!
jtorress said:
This worked great for me! Thank you SO much!
Click to expand...
Click to collapse
It really is that simple isn't it? Glad it was of help!!
Mine is encrypted n6 running cm12 nightly .
So flashing this will format my storage or just data partition ?
I dont wanna loose my personal data's :/
This will not wipe anything. The package only turns an encryption forced kernel into a no force encryption kernel. It is then up to you to follow one of the three options from my OP to reach actual unencryption status.
But you can relatively easily do it, though it will take a little time. Boot to recovery, flash my package, and then create a nandroid backup. Then backup the entirety of your internal storage to your PC or OTG storage device. Once that is done, do one of the 3 methods to unencrypt. Once you do that, boot android (this step is important as it builds proper multiuser partitions) then restore data to your internal storage. Then boot back to recovery and restore your nandroid backup. That will take you back to the exact point you were before but now unencrypted.
I did all steps,but it still shows me that I'm encrypted. What am I doing wrong?
indigo888 said:
I did all steps,but it still shows me that I'm encrypted. What am I doing wrong?
Click to expand...
Click to collapse
Walk me through in your own words what you did. Maybe we can figure out where you went wrong.
hlxanthus said:
Walk me through in your own words what you did. Maybe we can figure out where you went wrong.
Click to expand...
Click to collapse
I flash package and made nandroid backup in recovery.Then made factory reset and boot Android till welcome select language. Then switched off into recovery and restored backup....
And when you say you did a factory reset, how did you do that? A twrp factory reset will not work as it leaves the internal storage in tact. I am very explicit on the 3 ways to do this part (at least I thought I was).
hlxanthus said:
And when you say you did a factory reset, how did you do that? A twrp factory reset will not work as it leaves the internal storage in tact. I am very explicit on the 3 ways to do this part (at least I thought I was).
Click to expand...
Click to collapse
I did it from menu/settings/backup and reset.
indigo888 said:
I did it from menu/settings/backup and reset.
Click to expand...
Click to collapse
Might be worth trying the other two methods as well. TWRP's format data method and the fastboot userdata method are pretty thorough. Should get you up and running
Hi guys.
Today I turn on my galaxy s3 and it displays a motionless lockscreen (I can't turn the screen off, nor do anything with the touchscreen). It has already happened twice or three times.
I reboot it holding the power button for some time, and it bootloops.
ROM: Omnirom 4.4 (I've had it for 2/3 weeks, worked well)
KERNEL: Boeffla Kernel
RECOVERY: Philz 6.0.4.8 (I also have Aroma file manager)
It has happened some times already since I installed this ROM and I had fixed it flashing the xposed-disable zip, but this time it didn't work.
I think if I do a factory reset and reinstall the ROM everything will work, but I really can't lose all the stuff I have there (e.g. notes, contacts, SMSs, whatsapp chats...).
I cleared cache, dalvik, pulled out the battery, updated to the latest nightly via recovery; nothing worked.
Tried to unroot via Aroma FM, didn't manage to.
/dev/log is empty for Aroma FM, if I "ls" with the console it shows there are the regular folders, but I can't "cd" them for logs.
I attach the last logcat got from the Aroma FM console.
Is there any way I can get my phone back to work? Or can I save all my data?
Fanaticism said:
Hi guys.
Today I turn on my galaxy s3 and it displays a motionless lockscreen (I can't turn the screen
off, nor do anything with the touchscreen). It has already happened twice or three times.
I reboot it holding the power button for some time, and it bootloops.
ROM: Omnirom 4.4 (I've had it for 2/3 weeks, worked well)
KERNEL: Boeffla Kernel
RECOVERY: Philz 6.0.4.8 (I also have Aroma file manager)
It has happened some times already since I installed this ROM and I had fixed it flashing
the xposed-disable zip, but this time it didn't work.
I think if I do a factory reset and reinstall the ROM everything will work, but I really can't
lose all the stuff I have there (e.g. notes, contacts, SMSs, whatsapp chats...).
I cleared cache, dalvik, pulled out the battery, updated to the latest nightly via recovery; nothing worked.
Tried to unroot via Aroma FM, didn't manage to.
/dev/log is empty for Aroma FM, if I "ls" with the console it shows there are the regular folders, but I can't "cd"
them for logs.
I attach the last logcat got from the Aroma FM console.
Is there any way I can get my phone back to work? Or can I save all my data?
Click to expand...
Click to collapse
I don't know about the bootloop issue, I would just do a clean install and start again, but if your recovery is working, mount internal sd card as usb storage and copy what you want to keep to your computer.
You don't need to wipe data partition were your stuff is located. Just format system and flash the same rom again via recovery. This will wipe any init.d scripts and uncommon apps or frameworks which causing bootloop.
Only ROM, do not install Boeffla kernel.
If this will not help than make backup of data partition via CWM and copy this file by adb to PC where you will be able to extract needed data.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
Thanks for your replies!
I've already flashed the latest omnirom zip, which formatted /system in order to be installed (didn't it?).
What do you mean by "uncommon apps or frameworks"? What will I actually lose if I format /system?
However I'm making a backup of /data anyway.
System partition store only main system files, system settings and frameworks ie xposed framework, busybox binaries. All normal apps and their settings and data are stored on data partition ie SMS, emails etc.
Formatting system is good practice before flashing different android versions but also helps to get rid of all unnecessary scripts and garbage from old ROM.
You will not loose anything important from your private data.
And you are right, usually installer script formats system partition before copying new files but sometimes strange things happens it will not harm but may help.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
SirKunon said:
System partition store only main system files, system settings and frameworks ie xposed framework, busybox binaries. All normal apps and their settings and data are stored on data partition ie SMS, emails etc.
Formatting system is good practice before flashing different android versions but also helps to get rid of all unnecessary scripts and garbage from old ROM.
You will not loose anything important from your private data.
And you are right, usually installer script formats system partition before copying new files but sometimes strange things happens it will not harm but may help.
Click to expand...
Click to collapse
I've formatted /system and installed the latest Omnirom zip (before getting the bootloop I had an earlier version). I've turned on the device and it shows a dialog:
{
"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"
}
Like if I've wiped dalvik cache. It says "Android upgrade" "Launching apps".
EDIT:
Rebooted. Now it bootloops "as usual".
Maybe I need to wipe /boot? I don't know what to do. :S
Try different rom, cyanogenmod maybe?
Or try to launch the system in safe mode by hitting left capacity button (menu) after powering on the phone, but I don't know it works on custom roms.
Finally if you have your backup you can factory reset your phone to check it will start clean or it is a hardware failure. You can restore your backup later.
Do not format boot partition.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
SirKunon said:
Try different rom, cyanogenmod maybe?
Or try to launch the system in safe mode by hitting left capacity button (menu) after powering on the phone, but I don't know it works on custom roms.
Finally if you have your backup you can factory reset your phone to check it will start clean or it is a hardware failure. You can restore your backup later.
Do not format boot partition.
Click to expand...
Click to collapse
Thanks mate. I will try that today, and let you know this afternoon.
I've deleted some of the last modified folders and files in /data (apps-asec, system, .sto...), formatted /system, installed the latest omnirom, and this time it boots normally; altough it is impossible to use the phone, as "Google play services has force stopped" dialogs continuously appear.
Anyway, it looks like the whole /data folder has been wiped (maybe when the system recognizes something is missing from there, it wipes the whole thing), as apps don't have their data any more; altough some configurations have been kept (wifi passwords for example), and of course my apps have been kept as well (in fact I only deleted some folders from /data). It looks like the problem lies in /data.
Is all the data I'd like to preserve in "/data/data"? In that case I could try to restore only /data/data and see if the phone boots.
However the "force stop" dialogs problem is annoying.
Thanks for your help mate!
Don't wipe manually. Asec, you have removed , is virtual data folder.
Just make sure to have full backup of system. Choose backup, advanced, and select all partitions in CWM. When it's done connect to PC and copy backup in safe place.
Enter recovery once again and select wipe data factory settings. Wipe also cache, system and dalvik from advanced wipes menu.
Flash ROM and Gapps.
Flash SuperSU zip package if you like.
Reboot system and wait until first long boot finishes.
Config your Gmail account and wait for app restoration protocol.
If everything works fine reboot phone once more and load system. Check is it OK.
If so reboot into recovery and backup this clean system with all partitions, even efs.
Repeat copying this backup to PC procedure.
Now you can try to restore only data partition from first backup via recovery mode.
Choose restore, advanced and select only data partition.
Wait for restore and reboot.
Check if it's working, or not. If you got bootloops again then something is wrong with that data partition. Can't say what it may be.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
SirKunon said:
Don't wipe manually. Asec, you have removed , is virtual data folder.
Just make sure to have full backup of system. Choose backup, advanced, and select all partitions in CWM. When it's done connect to PC and copy backup in safe place.
Enter recovery once again and select wipe data factory settings. Wipe also cache, system and dalvik from advanced wipes menu.
Flash ROM and Gapps.
Flash SuperSU zip package if you like.
Reboot system and wait until first long boot finishes.
Config your Gmail account and wait for app restoration protocol.
If everything works fine reboot phone once more and load system. Check is it OK.
If so reboot into recovery and backup this clean system with all partitions, even efs.
Repeat copying this backup to PC procedure.
Now you can try to restore only data partition from first backup via recovery mode.
Choose restore, advanced and select only data partition.
Wait for restore and reboot.
Check if it's working, or not. If you got bootloops again then something is wrong with that data partition. Can't say what it may be.
Click to expand...
Click to collapse
It bootloops, so the problem lies in /data. If I manually copy in /data "apps", "apps-lib" and "data", the new rom does not see them. I will restore apps and data with some nandroid extractor.
Thanks for you help.
Last thing: I'm now trying to restore apps+data with this app, but it kepps saying "unable to create applist". How can I restore them? Is there any better app for this purpose?
After the latest magisk update 20.0, twrp (3.3.1-0) asks to Swipe to allow modification or keep read only. I always choose swipe to allow modification as that's what you primarily install twrp for, but even after doing so twrp fails to read my internal memory. Before this magisk update it didn't ever ask me this, except for the first time i installed twrp. Just shows 0MB and fails to mount storage for backing up or repair (Repair file system gives an error code 8).
Now the thing is that everything was working perfectly fine until this latest magisk update. Rom works fine (Havoc OS v2. 5), magisk works fine, root works fine, phone is encrypted just as it was before, everything is fine except twrp and i really need twrp to keep working as it was before.
Now yes, I have removed pin/password and tried to make twrp work, switched from pattern to pin as some solutions out there say that twrp will ask for the pin on boot up and on entering the correct pin it will decrypt the internal storage and all will be fine. But no, it didn't work.
Whatever it is am damn sure its magisk. Rom is the same, kernel is what came with the rom, no magisk modules installed, infact I run magisk in core mode only (yes I have disabled core mode only to see if it fixes the problem). I have attached a screen shot of magisk home screen and you can see that under the advanced settings Force encryption is enabled (just like it was enabled while installing magisk for the first time, I have never messed with those settings) and the other two are disabled. Do i need to check that recovery mode? Whatever the solution is, it is preferable that I don't loose my rom and data. But if there's a 100% working solution which involves wiping everything then please mention that too.
Also some solutions need you to change the file format of the internal storage, and I am a little afraid to try that.
Sorry for the extra long post, Thanks in advance.
ronish.x said:
After the latest magisk update 20.0, twrp (3.3.1-0) asks to Swipe to allow modification or keep read only. I always choose swipe to allow modification as that's what you primarily install twrp for, but even after doing so twrp fails to read my internal memory. Before this magisk update it didn't ever ask me this, except for the first time i installed twrp. Just shows 0MB and fails to mount storage for backing up or repair (Repair file system gives an error code 8)....
Click to expand...
Click to collapse
Check your TWRP logs. They will contain clues as to what might be the problem. Then post the logs in your TWRP forum. You can get the logs via adb
Code:
adb pull /tmp/recovery.log
adb pull /tmp/dmesg.log
Did you try changing the storage type? That helped me once. Also what helped was using the latest or an older version of twrp, you can also try doing this. Let me know what happens.
Soojikahalwa said:
Did you try changing the storage type? That helped me once. Also what helped was using the latest or an older version of twrp, you can also try doing this. Let me know what happens.
Click to expand...
Click to collapse
Changing the storage type would be safer or flashing the same version of twrp on top of it (as I have the latest one) or an older version would be better? I will use the official twrp app for the later.
ronish.x said:
Changing the storage type would be safer or flashing the same version of twrp on top of it (as I have the latest one) or an older version would be better? I will use the official twrp app for the later.
Click to expand...
Click to collapse
Try using an older version of twrp first. Changing storage type for system or data might lead to data lose. Make a backup in any case.