Related
Hi
I'm going to update my a500 to 3.1
I have unrootedmy device but how to remove CWM completly????
Please help
Why don't just update via CWM:
http://forum.xda-developers.com/showthread.php?t=1154492
1) re root your device
2) go into acer recovery installer and reflash to the backed up recovery (or do the stock recovery for your version)
3) de root.
I had to do this to get my update to work.
Do you know where can I find stock recovery for my version?
I have Acer_A500_1.139.05_COM_GEN1
thank you!
simonsgray said:
1) re root your device
2) go into acer recovery installer and reflash to the backed up recovery (or do the stock recovery for your version)
3) de root.
I had to do this to get my update to work.
Click to expand...
Click to collapse
When i installed ARI, it backed up my current recovery. When i went back into ARI, my old recovery was the first option. Sorry, explanation sucks, i don't have screenshots for you. I know there are threads with most of the software/firmware elements of most of the different versions, maybe do some digging? This would be the best place to start: http://forum.xda-developers.com/showthread.php?t=1126364
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Thanks! I used stock one in ARI, woks good.
simonsgray said:
When i installed ARI, it backed up my current recovery. When i went back into ARI, my old recovery was the first option. Sorry, explanation sucks, i don't have screenshots for you. I know there are threads with most of the software/firmware elements of most of the different versions, maybe do some digging? This would be the best place to start: http://forum.xda-developers.com/showthread.php?t=1126364
Click to expand...
Click to collapse
Euclid's Brother said:
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Hi Euclid, are you able to post a copy of that install-recovery.sh file? I don't seem to have it in my system/bin anymore
...That is assuming the file is not unique to each device??
I'm thinking the reason my OTA update wouldnt install is because i dont have the stock recovery menu.
Thanks!
I really don't get why everyone is spazzing over this... If you've already taken the steps to root and install CWM in the first place, why not just install the stock 3.1 image that's been provided in the dev section? It's 100% stock, no need to wait for Acer to stop twiddling their dangly bits...
Floatingfatman, that is exactly what I did, and it worked perfectly. Good advise!
FloatingFatMan said:
I really don't get why everyone is spazzing over this... If you've already taken the steps to root and install CWM in the first place, why not just install the stock 3.1 image that's been provided in the dev section? It's 100% stock, no need to wait for Acer to stop twiddling their dangly bits...
Click to expand...
Click to collapse
Yeah thats what i ended up doing to update it to 3.1.
Reason i want it back to stock is that i couldnt update via OTA at all (downloads fine but install fails at ~20% with the ! in a red triangle).
I was hoping by restoring it to stock the OTA would work, and so any future updates could also be done via OTA as opposed to finding a workaround each time.
Other than that, it's working just fine for now.
Euclid's Brother said:
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
I don't understand 'change permission from 444 to 544'. Root Manager lets me choose between, 'Read, Write or Execute'. Could you please elaborate?
Thanks
Never mind. Problem solved.
I hope this is in the right place, and im probably the highest level of noob at this so im sorry if i dont get all the terminoligy right
A few weeks ago, i decided to try and root my phone (after seeing that i could connect my usb to it) and had attempted to install philz custom recovery (6?) and install superSu and a custom ROM.
I had failed this and got it stuck in a boot loop (i think i may have done it twice by accident xd) and then my brother had done his magic and put cyanogenmod on the s5.
I just tried to install the same superSu zip. file that i used last time (i thought it should work) but now its telling me there is no Su binary or something, it also appears not to connect to the internet.
I guess my questions are, what did i do wrong?
how can i fix it?
what should i do next time?
Cyanogenmod is pre-rooted, you simply have to enable it from the developer options. SuperSU is not required.
That being said, if you had flashed an official SuperSU Zip through recovery, it should have installed the binary as well, so maybe your Zip is not right?
Official download here:
https://download.chainfire.eu/696/SuperSU
To fix it, re-flash cyanogen or some other rom. Possibly re-flash your modem too if cellular isn't working.
Next time, leave it to your brother to mess with things lol
Sean89us said:
Cyanogenmod is pre-rooted, you simply have to enable it from the developer options. SuperSU is not required.
That being said, if you had flashed an official SuperSU Zip through recovery, it should have installed the binary as well, so maybe your Zip is not right?
Official download here:
To fix it, re-flash cyanogen or some other rom. Possibly re-flash your modem too if cellular isn't working.
Next time, leave it to your brother to mess with things lol
Click to expand...
Click to collapse
so i dont need to download that file atall, if cyanogenmod is pre rooted? i did go into the recovery and only clicked install (was i meant to clear the cache partitions?).
what is pre rooted? i went to download the root checker and it told me that my phone wasent rooted, i said to my brother so do i not need supersu, he said yea u do if u want to root it (so i just went into the SD and redownloaded the one before, but now its telling me that it wasent rooted).
and what happens if i reflash it? will it just get rid of supersu to how it was when my brother gave me it? or will it alter some other stuff aswell
stormy_ll said:
so i dont need to download that file atall, if cyanogenmod is pre rooted? i did go into the recovery and only clicked install (was i meant to clear the cache partitions?).
what is pre rooted? i went to download the root checker and it told me that my phone wasent rooted, i said to my brother so do i not need supersu, he said yea u do if u want to root it (so i just went into the SD and redownloaded the one before, but now its telling me that it wasent rooted).
and what happens if i reflash it? will it just get rid of supersu to how it was when my brother gave me it? or will it alter some other stuff aswell
Click to expand...
Click to collapse
When you re-flash it will go back to being fresh/clean
No, you don't need SuperSU. Cyanogenmod comes with root built-in. Read below.
http://getgoogles.blogspot.com/2015/04/how-to-enable-root-access-mode-on.html
Hi. I was enjoying Lineage OS's latest ROM (14.1) and wasn't able to enjoy the "nightly" updates because when I went to do the update, I found out I needed a compatible recovery to do so. I had TWRP sitting on my computer and would FASTBOOT Boot twrp.img to flash roms. When I saw you needed to install twrp to make the Nightly update feature work, I flashed it with fastboot. I also went ahead and decided to start from scratch with a fresh install and used the latest Nightly LIneage OS file . After it installed, it booted up great. But when I went to add many apps back to my phone, so many of them were not showing up in the play store. And when some did, it would say "Incompatible Device" So I went to my settings and decided to try out the Nightly update hoping maybe that was the problem. When it booted to TWRP, nothing happened. So I hit REBOOT. and no matter what I choose, it just boots back into TWRP. Even when I hold the power button down and let it boot back up. Without touching any volume buttons, it just boots into TWRP. I can't get back to my OS. I'm going to try to install Lineage OS again and just hope I can get to my phone to make sure I'm getting messages from friends, doctors, etc...
Any help on how to fix this would be appreciated. I used this site " http://www.androidinfotech.com/2016...2-laser-ze551kl-marshmallow-install-twrp.html "
to root my phone so I could use Titanium Backup. I'm hoping something in there didn't mess me up.
Thank you in advance.
-Fuzzy
Well dang. I tried installing LINEAGE OS rom again and hoped for some strange reason it would boot into it. TWRP just keeps loading. I try the Reboot command in TWRP then choose SYSTEM and it still just goes to TWRP.
Well sometimes it just helps to air your frustration. As is true with many things in life. Say it out loud. Etc...
I was sure I had THE latest version of TWRP installed when this was happening. I rechecked to make sure. I didn't. I was 1 version away. Fastboot flashed that and it's booting normally . For now. Now, to see if I can get those apps to show up in the play store.
Things like Snapchat, Facebook messenger, etc... would just not show up.
Nope. That's still a problem . I wonder why this is happening?
Try clearing dalvik cache and sync you data for your mail account. I think those app wil show up. As for snapchat, you can't install it via playstore you can't pass safetynet.
FuzzyFone said:
Hi. I was enjoying Lineage OS's latest ROM (14.1) and wasn't able to enjoy the "nightly" updates because when I went to do the update, I found out I needed a compatible recovery to do so. I had TWRP sitting on my computer and would FASTBOOT Boot twrp.img to flash roms. When I saw you needed to install twrp to make the Nightly update feature work, I flashed it with fastboot. I also went ahead and decided to start from scratch with a fresh install and used the latest Nightly LIneage OS file . After it installed, it booted up great. But when I went to add many apps back to my phone, so many of them were not showing up in the play store. And when some did, it would say "Incompatible Device" So I went to my settings and decided to try out the Nightly update hoping maybe that was the problem. When it booted to TWRP, nothing happened. So I hit REBOOT. and no matter what I choose, it just boots back into TWRP. Even when I hold the power button down and let it boot back up. Without touching any volume buttons, it just boots into TWRP. I can't get back to my OS. I'm going to try to install Lineage OS again and just hope I can get to my phone to make sure I'm getting messages from friends, doctors, etc...
Any help on how to fix this would be appreciated. I used this site " http://www.androidinfotech.com/2016...2-laser-ze551kl-marshmallow-install-twrp.html "
to root my phone so I could use Titanium Backup. I'm hoping something in there didn't mess me up.
Thank you in advance.
-Fuzzy
Click to expand...
Click to collapse
What version of TWRP have you used? If it's 3.0.2.4 and below, update it.
darkeyes22 said:
What version of TWRP have you used? If it's 3.0.2.4 and below, update it.
Click to expand...
Click to collapse
(As shown in Post #3)
Already updated it. I got that part of the problem fixed. Thanks tho! :good:
FuzzyFone said:
(As shown in Post #3)
Already updated it. I got that part of the problem fixed. Thanks tho! :good:
Click to expand...
Click to collapse
What do you mean by saying "part of the problem"? Maybe I can help you with the rest of it.
darkeyes22 said:
What do you mean by saying "part of the problem"? Maybe I can help you with the rest of it.
Click to expand...
Click to collapse
Hello. I'm running the latest version of LineageOS 14.1 (just installed the nightly update) and several of the apps close the second I launch them. Clock was the first one I noticed . Loading pictures to share in other apps from Quckpic. and other apps I can't remember right now.
So I wanted to backup everything and try a different Rom thinking I might not have those problems. I installed SU and TWRP and then Titanium Backup Pro. After installing SU I had root. This morning I went to run a current backup and it said I no longer had root.
Dang. I have to go to the Pain Clinic. Time always catches up with me so fast when trying to problem solve.
Thank yo for reaching out! I really appreciate it. Especially with a phone that's not so popular out there in the wild that it's limited on folks available for help. it's 9:16am where I'm at. I'll probably be back in a few hours from now.
Thanks again, DarkEyes.
-Fuzzy
FuzzyFone said:
Hello. I'm running the latest version of LineageOS 14.1 (just installed the nightly update) and several of the apps close the second I launch them. Clock was the first one I noticed . Loading pictures to share in other apps from Quckpic. and other apps I can't remember right now.
So I wanted to backup everything and try a different Rom thinking I might not have those problems. I installed SU and TWRP and then Titanium Backup Pro. After installing SU I had root. This morning I went to run a current backup and it said I no longer had root.
Dang. I have to go to the Pain Clinic. Time always catches up with me so fast when trying to problem solve.
Thank yo for reaching out! I really appreciate it. Especially with a phone that's not so popular out there in the wild that it's limited on folks available for help. it's 9:16am where I'm at. I'll probably be back in a few hours from now.
Thanks again, DarkEyes.
-Fuzzy
Click to expand...
Click to collapse
Re-check your root with Root Checker. If you still have it, flash su removal through TWRP and flash systemless SuperSU. If you don't have it, just install systemless SuperSU. After you do that, boot back to the system (your boot might loop once - it's normal, do not interrupt boot), give TB pro root access, and see if it helped.
darkeyes22 said:
Re-check your root with Root Checker. If you still have it, flash su removal through TWRP and flash systemless SuperSU. If you don't have it, just install systemless SuperSU. After you do that, boot back to the system (your boot might loop once - it's normal, do not interrupt boot), give TB pro root access, and see if it helped.
Click to expand...
Click to collapse
Hello. Sorry it took me long to reply. After appointment, I was in too much pain to get online.
I installed thru Fastboot "addonsu-remove-14.1-arm64-signed.zip" rebooted, then installed addonsu-14.1-arm64-signed.zip thru Fastboot too and rebooted. Still no root. I checked it with RootChecker and there was no root.
Running latest nightly of LineageOS.
FuzzyFone said:
Hello. Sorry it took me long to reply. After appointment, I was in too much pain to get online.
I installed thru Fastboot "addonsu-remove-14.1-arm64-signed.zip" rebooted, then installed addonsu-14.1-arm64-signed.zip thru Fastboot too and rebooted. Still no root. I checked it with RootChecker and there was no root.
Running latest nightly of LineageOS.
Click to expand...
Click to collapse
Through Fastboot? Try through TWRP, flash removal, then flash Systemless SuperSU (not the one you have now).
Here is the link to systemless SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Hi
1st Step is Install official TWRP 3.1.1 which is availble for our device ze551kl aka Zool or ZooLD.
Boot in to TWRP
wipe cache+Dalvik cache+system+ASDF+internal storage.
now install Lineage rom latest version.
then gapps.
wipe dalvik cache.
hit Reboot system option
.it wlll not go in bootloop if u followed these steps which are guided by Devs here.
if u still facing bootloops u must have done extra ordinary thing with ur Device.
RonakRonak said:
Hi
1st Step is Install official TWRP 3.1.1 which is availble for our device ze551kl aka Zool or ZooLD.
Boot in to TWRP
wipe cache+Dalvik cache+system+ASDF+internal storage.
now install Lineage rom latest version.
then gapps.
wipe dalvik cache.
hit Reboot system option
.it wlll not go in bootloop if u followed these steps which are guided by Devs here.
if u still facing bootloops u must have done extra ordinary thing with ur Device.
Click to expand...
Click to collapse
It is Z00T that is ZE551KL, not Z00L. Do not even think about flashing something that was developed for Z00L on Z00T. It will not work.
Sent from my ASUS_Z00UD using XDA Labs
darkeyes22 said:
It is Z00T that is ZE551KL, not Z00L. Do not even think about flashing something that was developed for Z00L on Z00T. It will not work.
Sent from my ASUS_Z00UD using XDA Labs
Click to expand...
Click to collapse
Yes.i already mentioned model name.
Hey all.
I'm in need of a bit of help. I have a J5 and was getting sick of being told theres never any space to install apps, so I rooted it hoping to be able to remove the stock apps that come inbuilt like word, excel etc.... Anyway, I then decided to take it a step further and try and install a custom rom, long story short, im stuck with a green screen
I've been googling and following tutorials for hours now and I'm really at the point of giving up, so thought I would reach out incase i'm just over tired from it all and making silly mistakes.
I have TWRP 3.1.1-0 on my phone, I installed Lineage 14.1 figured out how to change the updater-script, green screen. I then installed a stock rom advanced I found here, green screen. I tried Aokp nightly nougat, green screen. After googling green screen I found a post saying its something to do with incompatibility from TWRP and that I need to install lollipop 5.1.1 firmware first before I can change to lilneage 14.1... Ive been googling for ages and I'm either coming to sites that want me to pay to download it at a reasonable speed or wait for hours. I'm a bit dubious as no other rom seems to have worked and I'm not sitting here with an empty phone.
Thanks.
LowKee84 said:
Hey all.
I'm in need of a bit of help. I have a J5 and was getting sick of being told theres never any space to install apps, so I rooted it hoping to be able to remove the stock apps that come inbuilt like word, excel etc.... Anyway, I then decided to take it a step further and try and install a custom rom, long story short, im stuck with a green screen
I've been googling and following tutorials for hours now and I'm really at the point of giving up, so thought I would reach out incase i'm just over tired from it all and making silly mistakes.
I have TWRP 3.1.1-0 on my phone, I installed Lineage 14.1 figured out how to change the updater-script, green screen. I then installed a stock rom advanced I found here, green screen. I tried Aokp nightly nougat, green screen. After googling green screen I found a post saying its something to do with incompatibility from TWRP and that I need to install lollipop 5.1.1 firmware first before I can change to lilneage 14.1... Ive been googling for ages and I'm either coming to sites that want me to pay to download it at a reasonable speed or wait for hours. I'm a bit dubious as no other rom seems to have worked and I'm not sitting here with an empty phone.
Thanks.
Click to expand...
Click to collapse
Flashing LP / MM / N ROMs based on AOSP/LOS over stock MM/ROMs based on stock MM --> green screen.
How to flash MM/N ROMs based on AOSP/LOS:
1) Install 5.1.1 stock firmware.
2) Install TWRP 5.1.1 (Nick's or Vince's).
3) Flash the MM/N ROM you want.
#Henkate said:
Flashing LP / MM / N ROMs based on AOSP/LOS over stock MM/ROMs based on stock MM --> green screen.
How to flash MM/N ROMs based on AOSP/LOS:
1) Install 5.1.1 stock firmware.
2) Install TWRP 5.1.1 (Nick's or Vince's).
3) Flash the MM/N ROM you want.
Click to expand...
Click to collapse
Don't suppose you know where I can find a copy, as I said in earlier post all the sites I find either take ages or want paying to upgrade to premium.
LowKee84 said:
Don't suppose you know where I can find a copy, as I said in earlier post all the sites I find either take ages or want paying to upgrade to premium.
Click to expand...
Click to collapse
Updato.
Awesome, went from 3 hour download to 15 minute download, finally some progress, thank you
LowKee84 said:
Awesome, went from 3 hour download to 15 minute download, finally some progress, thank you
Click to expand...
Click to collapse
Meh, tried to install but saying invalid zip file format.
LowKee84 said:
Meh, tried to install but saying invalid zip file format.
Click to expand...
Click to collapse
You extract the .zip and install it with Odin...
#Henkate said:
You extract the .zip and install it with Odin...
Click to expand...
Click to collapse
Okay, done that. So now I can install another rom from twrp or do I do it via odin?
LowKee84 said:
Okay, done that. So now I can install another rom from twrp or do I do it via odin?
Click to expand...
Click to collapse
TWRP.
You install only stock ROM with Odin (.tar format).
#Henkate said:
TWRP.
You install only stock ROM with Odin (.tar format).
Click to expand...
Click to collapse
Okay.
Anything else I need to do first? Do I need to root it again?
LowKee84 said:
Okay.
Anything else I need to do first? Do I need to root it again?
Click to expand...
Click to collapse
Most of the roms comes with root. In case it doesnt have root, you flash it after flashing the ROM.
#Henkate said:
Most of the roms comes with root. In case it doesnt have root, you flash it after flashing the ROM.
Click to expand...
Click to collapse
When I installed 5.1.1 it changed back to android recovery so I had to reinstall twrs recovery, then root again to be able to flash, but this time Lineage 14.1 finally installed
Thank you for your help.
LowKee84 said:
When I installed 5.1.1 it changed back to android recovery so I had to reinstall twrs recovery, then root again to be able to flash, but this time Lineage 14.1 finally installed
Thank you for your help.
Click to expand...
Click to collapse
So... I wanted to remove audioFx as I have no need for it, I had to root again... I tried the same root that I used originally but made it so it kept getting stuck on lineage boot screen and gave me no response on trying to boot to recovery. Any idea what went wrong?
Back to lineage again without root.
LowKee84 said:
So... I wanted to remove audioFx as I have no need for it, I had to root again... I tried the same root that I used originally but made it so it kept getting stuck on lineage boot screen and gave me no response on trying to boot to recovery. Any idea what went wrong?
Back to lineage again without root.
Click to expand...
Click to collapse
Did you flash the official SuperSU module from the lineage site?
No, I used Odin with the cf autoroot for my device.
I had problems with cf auto root, particularly the green screen on boot,try flashing the supersu from their site.
Tried it, used first one on the site, installed okay but can't see the su app anywhere, then tried the x86 version in case but wouldn't install.
Oh never mind, had to enable dev mode and enable root for apps and adb first, there is no actual app. I ran another app and it asked for root permission.
LowKee84 said:
Oh never mind, had to enable dev mode and enable root for apps and adb first, there is no actual app. I ran another app and it asked for root permission.
Click to expand...
Click to collapse
So it works?
It work
I'm just trying to understand what I did here. This is the first phone that's given me this much trouble.
Was running 7.1.1 stock. Finally got annoyed by that auto volume thing from sony that I had time to flash AOSP. I followed
https://forum.xda-developers.com/x-compact/development/nougat-7-1-1-android-source-project-t3555510
I used xperifirm/flashtool to update to newest UK firmware ( US has no fingerprint ) . I did NOT backup my drm keys. I have them from before when I rooted. Besides I didn't need them really. I use opencamera.
Followed that guide exactly. Everything worked. Then I flashed twrp 3.1.1 from adb. I think this is where I went wrong. I wanted to flash supersu and viper4android. As soon as I tried this I got twrp errors about mounting /data. Missing crypto footers. I also noticed that supersu binary always said it needed updating, and viper4android would not install drivers.
Did some googling. Saw I just had to format /data from twrp. TWRP was unable to format data with the same errors. More google, saw I had to recreate the /data from terminal from this link https://forum.xda-developers.com/xperia-sp/help/format-data-using-twrp-3-0-2-t3371137 .
Did that. Same errors in twrp. Ok had enough. Restored my twrp backup from 7.1.1 where everything worked. That went through and just hosed everything, due to not being able to read /data. After this finished I was stuck in a boot loop.
Got into fastboot and reran the original AOSP guide above. Now I'm there. Everything left exactly as it was. No twrp etc.
My question is what the heck did I break and how? And as a secondary question can I root this, if so how? The recovery that is flashed with that guide cannot mount /sdcard so I don't see a way to flash supersu for example.
Just trying to understand before I really break something.
j1tters said:
I'm just trying to understand what I did here. This is the first phone that's given me this much trouble.
Was running 7.1.1 stock. Finally got annoyed by that auto volume thing from sony that I had time to flash AOSP. I followed
https://forum.xda-developers.com/x-compact/development/nougat-7-1-1-android-source-project-t3555510
I used xperifirm/flashtool to update to newest UK firmware ( US has no fingerprint ) . I did NOT backup my drm keys. I have them from before when I rooted. Besides I didn't need them really. I use opencamera.
Followed that guide exactly. Everything worked. Then I flashed twrp 3.1.1 from adb. I think this is where I went wrong. I wanted to flash supersu and viper4android. As soon as I tried this I got twrp errors about mounting /data. Missing crypto footers. I also noticed that supersu binary always said it needed updating, and viper4android would not install drivers.
Did some googling. Saw I just had to format /data from twrp. TWRP was unable to format data with the same errors. More google, saw I had to recreate the /data from terminal from this link https://forum.xda-developers.com/xperia-sp/help/format-data-using-twrp-3-0-2-t3371137 .
Did that. Same errors in twrp. Ok had enough. Restored my twrp backup from 7.1.1 where everything worked. That went through and just hosed everything, due to not being able to read /data. After this finished I was stuck in a boot loop.
Got into fastboot and reran the original AOSP guide above. Now I'm there. Everything left exactly as it was. No twrp etc.
My question is what the heck did I break and how? And as a secondary question can I root this, if so how? The recovery that is flashed with that guide cannot mount /sdcard so I don't see a way to flash supersu for example.
Just trying to understand before I really break something.
Click to expand...
Click to collapse
I don't know if I know what went wrong, but I wonder, 1) why not Magisk, and 2) why not TWRP 3.2.1? Might be better off...
levone1 said:
I don't know if I know what went wrong, but I wonder, 1) why not Magisk, and 2) why not TWRP 3.2.1? Might be better off...
Click to expand...
Click to collapse
I've never really used magisk. Flashable zip? I'd need a working twrp since the recovery included with that rom can't mount /sdcard.
I think I just happened to grab 3.1.1, I must have missed the 3.2.1 version. At this point I'm not flashing anything until I know it works. I don't remember seeing it in nougat, but I see that under 8.1 the phone status shows as encrypted.
I'm a little leery of flashing anything currently since I currently have no root so I cant use titanium to backup. I also don't want to end up with a non working recovery again. I posted to that aosp thread seeing if anyone rooted it.
At this point I'd almost like to get a working twrp just to go back tro 7.1 where everything worked.
j1tters said:
I've never really used magisk. Flashable zip? I'd need a working twrp since the recovery included with that rom can't mount /sdcard.
I think I just happened to grab 3.1.1, I must have missed the 3.2.1 version. At this point I'm not flashing anything until I know it works. I don't remember seeing it in nougat, but I see that under 8.1 the phone status shows as encrypted.
I'm a little leery of flashing anything currently since I currently have no root so I cant use titanium to backup. I also don't want to end up with a non working recovery again. I posted to that aosp thread seeing if anyone rooted it.
At this point I'd almost like to get a working twrp just to go back tro 7.1 where everything worked.
Click to expand...
Click to collapse
Find twrp in rom forum here, and search xda for Magisk. Flash twrp, wipe everything, then flash rom, then flash Magisk. See if all better... Also, you can flash V4A modules, (and many others), through Magisk.
Twrp - https://forum.xda-developers.com/x-compact/development/ub-twrp-v3-2-1-xperia-x-compact-t3793837
Magisk - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
levone1 said:
Find twrp in rom forum here, and search xda for Magisk. Flash twrp, wipe everything, then flash rom, then flash Magisk. See if all better... Also, you can flash V4A modules, (and many others), through Magisk.
Twrp - https://forum.xda-developers.com/x-compact/development/ub-twrp-v3-2-1-xperia-x-compact-t3793837
Magisk - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Ok. So I'm reflashing the rom via fastboot just like that guide states. Just ignoring the recovery flash?
j1tters said:
Ok. So I'm reflashing the rom via fastboot just like that guide states. Just ignoring the recovery flash?
Click to expand...
Click to collapse
I have never flashed recovery with aosp, because it doesn't do anything. I haven't tried aosp O yet, though. Typically, yes, skip the recovery flash and flash twrp instead.
levone1 said:
I have never flashed recovery with aosp, because it doesn't do anything. I haven't tried aosp O yet, though. Typically, yes, skip the recovery flash and flash twrp instead.
Click to expand...
Click to collapse
I'll give it a whirl. One question though, since I've never run into this. What do you mean because it doesn't do anything? Granted this is the only aosp I've played with so far, so my knowledge is a bit limited.
j1tters said:
I'll give it a whirl. One question though, since I've never run into this. What do you mean because it doesn't do anything? Granted this is the only aosp I've played with so far, so my knowledge is a bit limited.
Click to expand...
Click to collapse
Stock recovery is usually limited to stock functions. If you want to customize, you need custom recovery.
levone1 said:
Stock recovery is usually limited to stock functions. If you want to customize, you need custom recovery.
Click to expand...
Click to collapse
Ohhh. right. I thought you meant recovery didn't do anything with aosp. Read that wrong, brain fart.
So nope. Twrp cannot read /data. Same error as before. Magisk seems to have installed.
My guess is this is all coming from the forced encryption, though I haven't done enough research.. I'm going to see if I can get viper running..
j1tters said:
Ok. So I'm reflashing the rom via fastboot just like that guide states. Just ignoring the recovery flash?
Click to expand...
Click to collapse
Just wanted to say thanks. Magisk and viper are installed and working. TWRP still errors out with not being able to read /data but I got viper and root, and thats all I wanted.
Thanks!
j1tters said:
So nope. Twrp cannot read /data. Same error as before. Magisk seems to have installed.
My guess is this is all coming from the forced encryption, though I haven't done enough research.. I'm going to see if I can get viper running..
Click to expand...
Click to collapse
Yeah, I guess still no custom kernels for O yet, so... Did you already try decrypt data with twrp?
Nope. I got what I wanted at this point. I'm leaving well enough alone. I don't see having to really do anything with TWRP in the near future. I'll miss being able to do a full backup, and I'm a little annoyed I cant restore my 7.1 backup but I can live with that. I see I can decrypt but I'm a little gun shy and don't want to break anything again.
At the end of the day AOSP + viper is really all I needed.
Thanks again for all the help.