well, i've follow every single tutorial on a32 4g's xda page, even tried some youtube ones, but my phone just WON'T boot GSIs
it is not an a325F like most people, it's an a325M (the difference is that a325M support more LTE frequencies),
Well, i install samsung stock firmware, then install TWRP, run multidisabler, then format data, then reboot again, then factory reset and then finally installing the GSI as an .img file applied to System Image
that was the first method i tested, i tested many others, with no sucess
what happens, you may ask? the phone starts, show samsung logo with the classic warning above it, and after 3 secs it restarts.... a literal bootloop
can you guys help me? im tired of samsung's stock ONE UI, it's sooooo laggy
i've tried CrDroid, RiceDroid, Lineage with no success
i will try using DSU, ill return here later
installed the GSI using DSU sideloader w/ magisk, lets see if it boots
HEH didn't boot..... wtf is wrong with this phone???
i even tested GOOGLE'S OFICIAL GSI and it DIDNT BOOT.... yeah this phone is ****ted
applesucksLmao said:
i even tested GOOGLE'S OFICIAL GSI and it DIDNT BOOT.... yeah this phone is ****ted
Click to expand...
Click to collapse
Did you format your phone at each time? And do you have installed a thing in top of magisk? Try this magisk ---> https://huskydg.github.io/magisk-files/
kilam9900 said:
Did you format your phone at each time? And do you have installed a thing in top of magisk? Try this magisk ---> https://huskydg.github.io/magisk-files/
Click to expand...
Click to collapse
will try
doesn't work, even with no magisk it just bootloops
you know what, **** it, i had enough with this phone, guess ill just install normal ONE Ui and debloat it... the phone literally doesn't accept any GSI and bootloops, not even using android's own DSU system
Factory reset doesn't mean system wipe, it just means a data wipe. It goes back to Samsung's boot animation because OneUI is still installed.
Wipe Dalvik/ART Cache, System, Data and Cache and try again.
Have you also checked what kind of GSI your phone supports? Maybe it's A-Only, maybe it's AB.
Myrmeko said:
Factory reset doesn't mean system wipe, it just means a data wipe. It goes back to Samsung's boot animation because OneUI is still installed.
Wipe Dalvik/ART Cache, System, Data and Cache and try again.
Have you also checked what kind of GSI your phone supports? Maybe it's A-Only, maybe it's AB.
Click to expand...
Click to collapse
i did that yesterday, and it's virtual AB
Did you disable AVB/VBmeta?
applesucksLmao said:
you know what, **** it, i had enough with this phone, guess ill just install normal ONE Ui and debloat it... the phone literally doesn't accept any GSI and bootloops, not even using android's own DSU sys
Click to expand...
Click to collapse
kilam9900 said:
Did you disable AVB/VBmeta?
Click to expand...
Click to collapse
yep
applesucksLmao said:
yep
Click to expand...
Click to collapse
sure at 100%? because it could be this and even google says it
kilam9900 said:
sure at 100%? because it could be this and even google says it
Click to expand...
Click to collapse
ye i've done it
applesucksLmao said:
ye i've done it
Click to expand...
Click to collapse
Did you disable encryption?
kilam9900 said:
Did you disable encryption?
Click to expand...
Click to collapse
yes, with multidisabler and i even tried one time using a force decrypt zip
applesucksLmao said:
yes, with multidisabler and i even tried one time using a force decrypt zip
Click to expand...
Click to collapse
with anykernel one?
kilam9900 said:
with anykernel one?
Click to expand...
Click to collapse
what do you mean? i didn't flash any kernel, oh actually, i tried one time with the kernel someone posted here on a different thread
Related
I was trying to deodex the stock system of my xperia Z1 Compact,
I botched it a bit and ended up having to wipe it completely and flash the stock rom back,
Now every time I enter the CWM bootloader it wipes my system,
This means I am unable to root my device or deodex it,
Any ideas would be much appreciated,
Phone was rooted before I attempted to deodex it,
Cwm and bootloader are two other things. Please explain something more
McTRASH692 said:
I was trying to deodex the stock system of my xperia Z1 Compact,
I botched it a bit and ended up having to wipe it completely and flash the stock rom back,
Now every time I enter the CWM bootloader it wipes my system,
This means I am unable to root my device or deodex it,
Any ideas would be much appreciated,
Phone was rooted before I attempted to deodex it,
Click to expand...
Click to collapse
mosespl said:
Cwm and bootloader are two other things. Please explain something more
Click to expand...
Click to collapse
Oops, sorry, I meant recovery,
Every time I boot into CMW Recovery it completely removes the rom from my phone,
McTRASH692 said:
Oops, sorry, I meant recovery,
Every time I boot into CMW Recovery it completely removes the rom from my phone,
Click to expand...
Click to collapse
I have never heard about such an issue. Have you tried flashing the Dualrecovery on your phone and just do it with TWRP?
Schlengge said:
I have never heard about such an issue. Have you tried flashing the Dualrecovery on your phone and just do it with TWRP?
Click to expand...
Click to collapse
Can you point me to a tutorial?
McTRASH692 said:
Can you point me to a tutorial?
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=2261606
That's the link to the original post. For further questions you might consider asking them there later. Tutorial and guidance can be found in the first post.
I bet you your self are wiping the system, the only thing you need to wipe are the caches.
XperienceD said:
I bet you your self are wiping the system, the only thing you need to wipe are the caches.
Click to expand...
Click to collapse
Nope, don't wipe anything, I can boot into recovery then select reboot to system and it will reboot but system isn't there so it gets stuck on the sony screen and the led will alternate between off and pink,
McTRASH692 said:
Nope, don't wipe anything, I can boot into recovery then select reboot to system and it will reboot but system isn't there so it gets stuck on the sony screen and the led will alternate between off and pink,
Click to expand...
Click to collapse
Well theres user error somewhere along the line as like Schlengge said I've never heard of it wiping the system.
XperienceD said:
Well theres user error somewhere along the line as like Schlengge said I've never heard of it wiping the system.
Click to expand...
Click to collapse
Not 100% sure it's system wipe but it wont boot into system once I run CWM,
McTRASH692 said:
Not 100% sure it's system wipe but it wont boot into system once I run CWM,
Click to expand...
Click to collapse
Are you using the right recovery, using files from other devices is a common error.
XperienceD said:
Are you using the right recovery, using files from other devices is a common error.
Click to expand...
Click to collapse
Made sure it was, I previously had root, then I hunted down and installed the deodex version of stok firmware, something went wrong there, (no picture),
I then had to flash odexed stock firmware, now this probem,
Hi all
My friend's wife has a swift with YOG4PAS33J and he says her notifications mention a system upgrade.
Has anyone else noticed same? I ask because https://cyngn.com/support mentiones Cyanogen OS 12.1 (5.1.1) cm-12.1-YOG4PAS33J-crackling.
Thanks
Yes I have installed the upgrade YOG7DAS2FI and now running cyanogen 12.1.1.
Yep - changelog on twitter (Wileyfox).
It seems I haven't posted enough to allow me to post links.
is a ZIP file available for flashing via TWRP?
Dior DNA said:
is a ZIP file available for flashing via TWRP?
Click to expand...
Click to collapse
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver
mermigas said:
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver
Click to expand...
Click to collapse
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI
Dior DNA said:
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI
Click to expand...
Click to collapse
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464
mermigas said:
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464
Click to expand...
Click to collapse
your russian seems good enough
meanwhile https://cyngn.com/support got updated
Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!
seb5049 said:
Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!
Click to expand...
Click to collapse
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).
Dior DNA said:
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).
Click to expand...
Click to collapse
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.
seb5049 said:
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.
Click to expand...
Click to collapse
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.
mermigas said:
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.
Click to expand...
Click to collapse
Should I install everything in the zip? Won't that wipe all of my data?
seb5049 said:
Should I install everything in the zip? Won't that wipe all of my data?
Click to expand...
Click to collapse
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.
Dior DNA said:
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.
Click to expand...
Click to collapse
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?
seb5049 said:
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?
Click to expand...
Click to collapse
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success
Dior DNA said:
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success
Click to expand...
Click to collapse
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.
seb5049 said:
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.
Click to expand...
Click to collapse
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated / changed during or right after upgrade.
Dior DNA said:
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated change during or right after upgrade.
Click to expand...
Click to collapse
Yeah, I did. By the way, I disabled the permissions again, but everything's fine now.
I keep getting a zram dump pop up that can never got before after flashing in twrp. Does anyone else have this issue? It turns into a boot loop when flashing arise sound mod and sometimes after flashing ROMs. It boot loops between the Google splash and the zram dump screen. Man this is annoying Any help would be highly appreciated!
I did a complete clean flash with a factory image wiping everything, and reinstalled twrp. That stopped it for me.
What process did you use when doing the complete factory flash?
chapelfreak said:
I did a complete clean flash with a factory image wiping everything, and reinstalled twrp. That stopped it for me.
Click to expand...
Click to collapse
And did you flash the 7.1.2 factory image or 7.1.1?
chapelfreak said:
I did a complete clean flash with a factory image wiping everything, and reinstalled twrp. That stopped it for me.
Click to expand...
Click to collapse
Guessphx said:
And did you flash the 7.1.2 factory image or 7.1.1?
Click to expand...
Click to collapse
If you bought your pixel from google and NOT from verizon, flash the 7.1.2 factory image, then boot twrp RC1 and flash RC2
Guessphx said:
And did you flash the 7.1.2 factory image or 7.1.1?
Click to expand...
Click to collapse
I used a computer and used flash all to flash 7.1.2, before I did that I backed up all the stuff I on my phone I didn't want to lose like pics.
Thank you I appreciate it going to do this when I get home
chapelfreak said:
I used a computer and used flash all to flash 7.1.2, before I did that I backed up all the stuff I on my phone I didn't want to lose like pics.
Click to expand...
Click to collapse
chapelfreak said:
I used a computer and used flash all to flash 7.1.2, before I did that I backed up all the stuff I on my phone I didn't want to lose like pics.
Click to expand...
Click to collapse
Do you have a 32gb or 128gb? I heard if you do this on a 128 gigabyte it messes up the storage
Guessphx said:
Do you have a 32gb or 128gb? I heard if you do this on a 128 gigabyte it messes up the storage
Click to expand...
Click to collapse
I have the 128GB and never once had an issue. I know with the N6 it happened to it, but I'm not if that happens to our pixels .
You miss Full-Disk Encryption on your OnePlus 5?
Here's a fix.
Flash the zip below after flashing your kernel (which means after every ROM update as well!).
The very first time you flash this mod, you'll have to format userdata, or bad things will happen.
First-time Install instructions:
Flash your ROM
Flash the attached Zip
(Optional) Flash Magisk
Format userdata. In TWRP, go to Wipe -> Format Data
Reboot
You are now unencrypted.
To encrypt in Full-Disk Encryption mode, go to Settings -> Security -> Encrypt
You're now in FDE mode!
Profit!
And don't forget to reflash this module every time you flash a new boot image.
XDA:DevDB Information
Full-Disk-Encryption Enabler for OP5, Device Specific App for the OnePlus 5
Contributors
Fif_
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2017-09-12
Created 2017-09-13
Last Updated 2017-09-13
Here's the Zip.
@Fif_ should i erase "internal storage" or just data partition!Thank You!
Sent from my ONEPLUS A5000 using Tapatalk
dragoi90 said:
@Fif_ should i erase "internal storage" or just data partition!Thank You!
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
You need to format the data partition. That all also nuke the internal storage by the way, so your phone will be back to factory reset.
Is this used for people who decrypted their devices and wish to go back to encrypted so that they can flash roms that only works with encrypted?
BlueEffect said:
Is this used for people who decrypted their devices and wish to go back to encrypted so that they can flash roms that only works with encrypted?
Click to expand...
Click to collapse
No this is for people that want to run FDE rather than FBE. Eg. to have Xposed working.
Fif_ said:
No this is for people that want to run FDE rather than FBE. Eg. to have Xposed working.
Click to expand...
Click to collapse
You can have Xposed working with FBE by just soft rebooting using Xposed installer.
alukarulz said:
You can have Xposed working with FBE by just soft rebooting using Xposed installer.
Click to expand...
Click to collapse
You are right, but I don't want to have to do that, I want Xposed on the first boot...
BlueEffect said:
Is this used for people who decrypted their devices and wish to go back to encrypted so that they can flash roms that only works with encrypted?
Click to expand...
Click to collapse
If you want the go under settings and security and encrypt your phone
BlueEffect said:
Is this used for people who decrypted their devices and wish to go back to encrypted so that they can flash roms that only works with encrypted?
Click to expand...
Click to collapse
ndarkside93 said:
If you want the go under settings and security and encrypt your phone
Click to expand...
Click to collapse
This is used to change encryption type from FBE to FDE. You can also use it to run decrypted.
Fif_ said:
This is used to change encryption type from FBE to FDE. You can also use it to run decrypted.
Click to expand...
Click to collapse
I know.I was just answering his question.
alukarulz said:
You can have Xposed working with FBE by just soft rebooting using Xposed installer.
Click to expand...
Click to collapse
Fif_ said:
You are right, but I don't want to have to do that, I want Xposed on the first boot...
Click to expand...
Click to collapse
Ahh... I see... I am getting tired of having to soft reboot after each reboot. It looks like this FDE mod/hack would resolve this problem, right? Are there any real drawbacks to using FDE over FBE? What about if/when I decide to switch to another ROM?
sjamie said:
Ahh... I see... I am getting tired of having to soft reboot after each reboot. It looks like this FDE mod/hack would resolve this problem, right? Are there any real drawbacks to using FDE over FBE? What about if/when I decide to switch to another ROM?
Click to expand...
Click to collapse
I downside is you have to flash the fde flash file Everytime you flash an update. Plus the first time you need to erase data.
alukarulz said:
I downside is you have to flash the fde flash file Everytime you flash an update. Plus the first time you need to erase data.
Click to expand...
Click to collapse
Would I have to also erase my data when switching to a different ROM?
alukarulz said:
I downside is you have to flash the fde flash file Everytime you flash an update. Plus the first time you need to erase data.
Click to expand...
Click to collapse
I'm already flashing Magisk after every ROM update, so it's just one more zip to flash.
Actually stock OOS doesn't seem to care, you only have to flash this mod once, before you convert to FDE.
OOS 4.5.10 will happily boot in FDE even without the mod, provided that the data partition is already FDE.
That's not the case for every ROM.
Another downside is that no unattended boots are possible. You have to type in the FDE password to boot into Android.
sjamie said:
Would I have to also erase my data when switching to a different ROM?
Click to expand...
Click to collapse
No. Only once.
Fif_ said:
I'm already flashing Magisk after every ROM update, so it's just one more zip to flash.
Actually stock OOS doesn't seem to care, you only have to flash this mod once, before you convert to FDE.
OOS 4.5.10 will happily boot in FDE even without the mod, provided that the data partition is already FDE.
That's not the case for every ROM.
Another downside is that no unattended boots are possible. You have to type in the FDE password to boot into Android.
Click to expand...
Click to collapse
Thanks! I'll definitely give this mod a try if I truly get tired of having to soft boot after each normal boot. Is there a tasker profile or some other way to automate that?
sjamie said:
Thanks! I'll definitely give this mod a try if I truly get tired of having to soft boot after each normal boot. Is there a tasker profile or some other way to automate that?
Click to expand...
Click to collapse
Yes you can, run in a root shell:
Code:
setsid sh -c 'stop; start'
But I always run into strange things in Xposed if it's not running at boot, so YMMV.
Be careful not to just restart the system UI but the full zygote stack.
Fif_ said:
Yes you can, run in a root shell:
Click to expand...
Click to collapse
Thank you. What exactly is that command doing? Do I have to run it after each boot?
sjamie said:
Thank you. What exactly is that command doing? Do I have to run it after each boot?
Click to expand...
Click to collapse
"stop" stops all Android services.
"start" starts them again.
The "setsid sh" wrapper is there so that the commands will survive the Android shutdown and run to completion even if the parent process calling root is killed (which will happen as soon as "stop" runs).
Yes you'd have to run this after every boot.
But be careful that the second time Android starts after a boot is not detected as a second boot event or you'll end up in a restart loop.
HELLO GOOD PEOPLE I RECENTLY UPDATE MY A32 UNFORTUNATELY IT GOT STUCK IN REBOOT LOOP , I HAD TO WIPE /FACTORY SETTING TO GET MY PHONE BACK. IS IT POSSIBLE TO RECOVER MY DATA.
dont think so... atleast not easily
TAMBAZ said:
HELLO GOOD PEOPLE I RECENTLY UPDATE MY A32 UNFORTUNATELY IT GOT STUCK IN REBOOT LOOP , I HAD TO WIPE /FACTORY SETTING TO GET MY PHONE BACK. IS IT POSSIBLE TO RECOVER MY DATA.
Click to expand...
Click to collapse
Yes you can, just download your phone firmware from samfw and use ODIN but DO NOT USE DEFAULT CSC USE HOME_CSC TO AVOID DATA FORMAT
kilam9900 said:
Yes you can, just download your phone firmware from samfw and use ODIN but DO NOT USE DEFAULT CSC USE HOME_CSC TO AVOID DATA FORMAT
Click to expand...
Click to collapse
he factory setting wiped the phone
applesucksLmao said:
he factory setting wiped the phone
Click to expand...
Click to collapse
Hoh my bad
kilam9900 said:
Hoh my bad
Click to expand...
Click to collapse
he probably means if he could recover the data like how they do on PC hard drives, but because of FStrim and other stuff on android, i don't think so
applesucksLmao said:
he probably means if he could recover the data like how they do on PC hard drives, but because of FStrim and other stuff on android, i don't think so
Click to expand...
Click to collapse
No, only online backup can work
@TAMBAZ