Gave up waiting for Lollipop from LG and went for Marshmallow. Rooted with Kingo root and installed TWRP from terminal emulator. Wiped and formatted /data. Flashed Marshmallow (MDB08M) and SuperSU. Rebooted and installed apps. Everything worked like a dream, no hassles or snags.
So far ROM is stable, smooth and nice to use. Battery life is good. A definite improvment.
I wasn't aware there was a 6.0 ROM. Link please.
Are you on the V500 or V510?
I'm on V500. Link http://forum.xda-developers.com/lg-...rom-android-6-0-marshmallow-20151028-t3235794
Good luck!
nilssongrey said:
I'm on V500. Link http://forum.xda-developers.com/lg-...rom-android-6-0-marshmallow-20151028-t3235794
Good luck!
Click to expand...
Click to collapse
Thanks! I'll flash later today!
I tried to flash this ROM and I'm having issues with doing that. Anyone knows what am I doing wrong here?
I had CM12.1 from @fefifofum earlier but I wanted to try something Marshmallow based.
I updated TWRP to the most recent stable version (2.8.7.1) and all I got trying to install zip from mentioned thread is:
Error flashing zip '/external_sd/aosp_v500-eng.adrianomartins-20151107.zip'
Updating partition details...
...done
No other errors. I wiped Dalvik Cache, Cache, Data and even System. Nothing has changed.
What else can I try to fix it? Cause in fact right now I've got unusable tablet
regards
Bartek
Sounds like a bad download. Did you check the MD5 hash of what you downloaded and compared it to what the download page said the original hash was, if it gives that info? Android File Host does, I didn't check where your file came from.
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
MD5 is correct. I think something went wrong with wipes. Maybe I wiped too much but I'm not sure how to check it.
Maybe current partition layout is broken and needs to be fixed somehow but I'm not sure how to check what's wrong.
Any way to turn on more debugging info during install?
Current message isn't very helpful :/
regards
Bartek
fenio said:
MD5 is correct. I think something went wrong with wipes. Maybe I wiped too much but I'm not sure how to check it.
Maybe current partition layout is broken and needs to be fixed somehow but I'm not sure how to check what's wrong
regards
Bartek
Click to expand...
Click to collapse
I wiped dalvik and cache. I formatted /data and then I flashed.
Regards/Hakan
nilssongrey said:
I wiped dalvik and cache. I formatted /data and then I flashed.
Regards/Hakan
Click to expand...
Click to collapse
Well it doesn't work for me. I'm still getting "Error flashing zip".
Maybe there are some additional steps to do when I'm moving from CM to AOSP?
regards
Bartek
fenio said:
MD5 is correct. I think something went wrong with wipes. Maybe I wiped too much but I'm not sure how to check it.
Maybe current partition layout is broken and needs to be fixed somehow but I'm not sure how to check what's wrong.
Any way to turn on more debugging info during install?
Current message isn't very helpful :/
regards
Bartek
Click to expand...
Click to collapse
For what it's worth, I don't think it's possible to wipe too much. At least, in TWRP, I commonly wipe everything: data, cache, dalvik, system, and internal storage with no trouble.
roirraW "edor" ehT said:
For what it's worth, I don't think it's possible to wipe too much. At least, in TWRP, I commonly wipe everything: data, cache, dalvik, system, and internal storage with no trouble.
Click to expand...
Click to collapse
Thanks for confirmation. But then I have no idea why it doesn't flash.
It fails almost instantly so it looks like it gives up at the beginning but file size and its checksum are fine.
What else can I try to do?
regards
Bartek
fenio said:
Thanks for confirmation. But then I have no idea why it doesn't flash.
It fails almost instantly so it looks like it gives up at the beginning but file size and its checksum are fine.
What else can I try to do?
regards
Bartek
Click to expand...
Click to collapse
Can you post a log from recovery? Go to TWRP's Advanced menu and choose Copy Log to SD Card, then upload it somewhere. Feel free to put it in a zip.
What did you use to check the hash of the file from the phone itself?
What filsystem do you have on /data? I have a vauge recollection from a Lollipop thread that there were problems coming from CM if /data was formatted F2FS
/Hakan
Ok forget the topic. Apparently you can't choose random directory to put your image before flashing.
For some TWRP complains and clearly states that something is wrong (/root if I recall correctly) but for some it just blindly fails (/external_sd or /recovery).
I had to move my image to /sdcard directory and TWRP flashed it with no issues.
Hope that helps someone
Thanks a lot for your help.
regards
Bartek
fenio said:
Ok forget the topic. Apparently you can't choose random directory to put your image before flashing.
For some TWRP complains and clearly states that something is wrong (/root if I recall correctly) but for some it just blindly fails (/external_sd or /recovery).
I had to move my image to /sdcard directory and TWRP flashed it with no issues.
Hope that helps someone
Thanks a lot for your help.
regards
Bartek
Click to expand...
Click to collapse
Happy to know that you solved it. Happy Marshmallow!
/Hakan
nilssongrey said:
Happy to know that you solved it. Happy Marshmallow!
/Hakan
Click to expand...
Click to collapse
Thanks. Works like a charm so far. Looking forward to see more apps supporting asking for permissions on demand not on installation time
regards
Bartek
nilssongrey said:
Rooted with Kingo root and installed TWRP from terminal emulator. Wiped and formatted /data. Flashed Marshmallow (MDB08M) and SuperSU. Rebooted
Click to expand...
Click to collapse
Hi nilssongrey
I have installed TWRP, wiped all, flashed Marshmallow (MDB08M) and SuperSU
But now I have not root permission.
I don't know what's wrong.
How can I have root access?
Thanks
peppomcr said:
Hi nilssongrey
I have installed TWRP, wiped all, flashed Marshmallow (MDB08M) and SuperSU
But now I have not root permission.
I don't know what's wrong.
How can I have root access?
Thanks
Click to expand...
Click to collapse
I don't think you're in the correct forum.
I suggest you read a whole lot more before you break your new phone.
peppomcr said:
Hi nilssongrey
I have installed TWRP, wiped all, flashed Marshmallow (MDB08M) and SuperSU
But now I have not root permission.
I don't know what's wrong.
How can I have root access?
Thanks
Click to expand...
Click to collapse
High,
You should download the latest edition from that thread. There were some problems with the previous one. Even a second attempt by the OP didn't resolve all issues. The latest MRA58V is stable and complete. Personally however I flashed a more loaded version of the OpenGapps project. Running smooth etc since 20 November... Don't flash the latest SU, but the version before (2.51 ).
Cheers
Cluey said:
I don't think you're in the correct forum.
I suggest you read a whole lot more before you break your new phone.
Click to expand...
Click to collapse
It's not a new phone but an old tablet.
dirlan2001 said:
High,
You should download the latest edition from that thread. There were some problems with the previous one. Even a second attempt by the OP didn't resolve all issues. The latest MRA58V is stable and complete. Personally however I flashed a more loaded version of the OpenGapps project. Running smooth etc since 20 November... Don't flash the latest SU, but the version before (2.51 ).
Cheers
Click to expand...
Click to collapse
I've used the latest version: MRA58V, 2015-11-18
I need root because I have the external sd issue and I want to try to solve it: sd not recognized and so on...
I've flashed SU 2.46: is it better another version?
I'll take a look at OpenGapps project.
Thanks for your reply,
cheers.
Related
I've captured the OTA zip for XT1052 India 4.4.4 update.
Instructions (You should be on android 4.4.2)
For both locked and unlocked bootloaders
1. Place the downloaded file in sdcard
2. Don't rename the file, it should be exactly as it is
3. Rooted users make sure you're as close to stock as possible
4. Go to settings-> about-> system updates
5. It will prompt to install the update
Download XT1052 India 4.4.4 OTA
Could you post the stock recovery image of the 4.4.2 ROM, please?
ron_gangte said:
Could you post the stock recovery image of the 4.4.2 ROM, please?
Click to expand...
Click to collapse
Sorry, I don't have that right now.
Thanks anyway. It'd be awesome if someone who has it posted. Anyone?
Yep, the update just popped up. How do you capture it by the way? What's the path?
devilsdouble said:
Yep, the update just popped up. How do you capture it by the way? What's the path?
Click to expand...
Click to collapse
/cache - find it w/Root Explorer, or similar.
samwathegreat said:
/cache - find it w/Root Explorer, or similar.
Click to expand...
Click to collapse
There are three folders under cache, backup, lost+found and recovery, none of them contain the update.
devilsdouble said:
There are three folders under cache, backup, lost+found and recovery, none of them contain the update.
Click to expand...
Click to collapse
You already installed it? Once you install it, the file is erased - forever. All OTAs are this way. You MUST extract it before you install it.
Confirm: Did you install it or not? Also, if not - has it downloaded completely?
EDIT: I'll take your lack of response as you confirming that you did install it...
I am downloading ota update my phone is rooted so should i unroot it first and remove xposed framework.. reply??
Hitesh1802 said:
I am downloading ota update my phone is rooted so should i unroot it first and remove xposed framework.. reply??
Click to expand...
Click to collapse
Yes, un-root, and remove all traces of having rooted. That includes any changes done to your System Files which Xposed might have done. You will have to flash the stock recovery too.
ron_gangte said:
Yes, un-root, and remove all traces of having rooted. That includes any changes done to your System Files which Xposed might have done. You will have to flash the stock recovery too.
Click to expand...
Click to collapse
thanks for the reply mate i have removed su by app option full unroot yes i am on stock recovery and uninstalled all modules and xposed framework..
after update i have to done that again..
Due to this i miss my old Samsung device just flash and you are on...
samwathegreat said:
You already installed it? Once you install it, the file is erased - forever. All OTAs are this way. You MUST extract it before you install it.
Confirm: Did you install it or not? Also, if not - has it downloaded completely?
EDIT: I'll take your lack of response as you confirming that you did install it...
Click to expand...
Click to collapse
No, my lack of response was because of the reading I was doing here on XDA as why I wasn't seeing the OTA zip file under cache. Then I realized that I did not download the OTA, I thought that it was downloaded already as I had data on and it was just asking me to whether it should install or not.
Now I downloaded the OTA, and it's there under cache folder, and now at a safe place on my desktop.
I would never install it on my phone without flashing back stock ROM again anyway. I like to do things fresh.
devilsdouble said:
No, my lack of response was because of the reading I was doing here on XDA as why I wasn't seeing the OTA zip file under cache. Then I realized that I did not download the OTA, I thought that it was downloaded already as I had data on and it was just asking me to whether it should install or not.
Now I downloaded the OTA, and it's there under cache folder, and now at a safe place on my desktop.
I would never install it on my phone without flashing back stock ROM again anyway. I like to do things fresh.
Click to expand...
Click to collapse
Good Deal. Thanks for clarifying, and glad you were able to extract it. :good:
I can relate -- I also prefer to always "do things fresh"
samwathegreat said:
Good Deal. Thanks for clarifying, and glad you were able to extract it. :good:
I can relate -- I also prefer to always "do things fresh"
Click to expand...
Click to collapse
Thanks. It's always nice to have the latest of Android. The new dialer is meaningless for me, again, it just changed it's viewing type, nothing else has been changed! Need to install ExDialer as usual. Will see if there's really something done with the camera, can't take any meaningful photos at 3:30 in the morning :laugh:
Just one thing, as I have taken the OTA after a fresh install of stock ROM, now I don't need to format it again from recovery right?
There is already a thread for the 4.4.4 rollout here, please use it instead of having two similar discussions going on in 2 separate threads. Thanks
Thread closed
I made a Twrp flashable zip for the CM12S OTA update
My initial warning was a
WARNINGS
This update is intended to be used to update from CM11S-XNPH05Q to CM-12.0-YNG1TAS0YL,
Users have reported it working via other dirty flashes, so do so at your own risk.
HOWEVER I AM NOT RESPONSIBLE FOR BRICKS OR YOUR OWN STUPIDITY
THIS IS YOUR ONLY WARNING
DOWLOAD HERE
Installation process (this will keep root, and keep twrp installed. if not just flashing the zip will reflash CM recovery each boot)
1) Download the OTA zip above and the latest SuperSU.zip (here)
2) put both files on your internal storage
3) Reboot into TWRP
4) flash the modified OTA and wipe the caches
5) Flash SuperSU.zip
6) reboot
Credits
@James1o1o with out him i wouldn't have the OTA zip
-iCatalystic (Reddit user who posted the megalink that James1o1o reposted)
@Harfainx for the method for making this twrp flashable
@Chainfire for SuperSU
Reserved for OP
Huzzah! Awesome, homie. Thanks for the link
Will this wipe the device?
IDK what the big deal is. I downloaded and flashed this one; http://forum.xda-developers.com/showpost.php?p=60095886&postcount=13
I was on OxygenOS
wipe and flash with TWRP
running perfect
spicediablo said:
Will this wipe the device?
Click to expand...
Click to collapse
nope, didn't when I flashed it
I heard people saying it would flash over CM11 nightlies and I didn't believe it. Just for grins, I backed up my CM12 nightlies, wiped cache/dalvik-art and gave it a whirl. So far no problems, but later in the day I'm going to do a clean install.
gcng said:
IDK what the big deal is. I downloaded and flashed this one; http://forum.xda-developers.com/showpost.php?p=60095886&postcount=13
I was on OxygenOS
wipe and flash with TWRP
running perfect
Click to expand...
Click to collapse
this has the assert lines removed from the updater script, you needed to remove them before on cm11.
Apparently not now, the warnings are because since this has a radio.img and other stuff you can brick your device.
Does this also flash modem etc.?
furrycurry said:
Does this also flash modem etc.?
Click to expand...
Click to collapse
yes, this is the OTA update that was pulled, just has a few lines removed from the updater-script
really?
working with multirom as secondary.
thoughtlesskyle said:
Credits
@James1o1o with out him i wouldn't have the OTA zip
Click to expand...
Click to collapse
FYI, James just copied the link from here:
http://www.reddit.com/r/oneplus/comments/32iby5/so_it_begins/
I'm glad he reposted it, but this guy deserves the credit for uploading it to Mega. :good:
CafeKampuchia said:
FYI, James just copied the link from here:
http://www.reddit.com/r/oneplus/comments/32iby5/so_it_begins/
I'm glad he reposted it, but this guy deserves the credit for uploading it to Mega. :good:
Click to expand...
Click to collapse
putting that in the OP now
Edit it's there, didn't know where it came from didn't mean to miss credit.
Hey, whats the difference its having from the one that is other post? There peoples are simply flashing from CM12 nightlies.
So after flashing it with Philz Recovery with the result "t", my Android just doesn't boot up anymore. The boot animation animates for an infinite time. What now?
Edit: Well, I held the power button until it was off, restarted and now it's working. It's magic. [place parrot here]
shaheen7m said:
Hey, whats the difference its having from the one that is other post? There peoples are simply flashing from CM12 nightlies.
Click to expand...
Click to collapse
You can try it at your own risk, there is a small updater script change that allows twrp to flash it. It does flash a radio which can be dangerous. If it's working for them then this should in Theory work, try it at your own risk and let us know if it works
thoughtlesskyle said:
You can try it at your own risk, there is a small updater script change that allows twrp to flash it. It does flash a radio which can be dangerous. If it's working for them then this should in Theory work, try it at your own risk and let us know if it works
Click to expand...
Click to collapse
One guy in the other thread already bricked his device trying to flash from Oxygen People flashing from CM11s & CM11/12 nightlies seem to be doing ok except for the occasional FC, probably from not clearing cache/dalvik.
CafeKampuchia said:
One guy in the other thread already bricked his device trying to flash from Oxygen
Click to expand...
Click to collapse
I bricked mine last week going from cm12 back to 11S, luckily I was able to get it up and running by flashing colorOS via their flashtool and then reflashing cm11S again.
These are reasons why I am stressing this so much. I had it happen, it sucks but I got my device back
thoughtlesskyle said:
I bricked mine last week going from cm12 back to 11S, luckily I was able to get it up and running by flashing colorOS via their flashtool and then reflashing cm11S again.
These are reasons why I am stressing this so much. I had it happen, it sucks but I got my device back
Click to expand...
Click to collapse
Totally agree. I like your huge disclaimer on the OP :good:
CafeKampuchia said:
Totally agree. I like your huge disclaimer on the OP :good:
Click to expand...
Click to collapse
Been doing this too long to be vague about that kind of stuff, if it was just system and boot img I'd tell you to flash it however you want because there isn't a ton of things that those can mess up
Had this phone close to a year and finally decided to root. I installed twrp but when I choose to mount system it says it can't so I can't root. Any ideas? Pretty sure there's a simple fix but I've been out of the rooting/roming stuff for a while.
You have to format data and cache partitions to allow twrp to red them but you will lose all your data.
Start in bootloader mode and use fastboot
Fastboot format data
Fastboot format userdata
Envoyé de mon Nexus 6P en utilisant Tapatalk
Ryno77 said:
Had this phone close to a year and finally decided to root. I installed twrp but when I choose to mount system it says it can't so I can't root. Any ideas? Pretty sure there's a simple fix but I've been out of the rooting/roming stuff for a while.
Click to expand...
Click to collapse
Exactly what are you trying to achieve? This will help us assist you better.
1) Only Root?
2) Root with decrypted storage?
DJBhardwaj said:
Exactly what are you trying to achieve? This will help us assist you better.
1) Only Root?
2) Root with decrypted storage?
Click to expand...
Click to collapse
Only root. Thanks.
Ryno77 said:
Only root. Thanks.
Click to expand...
Click to collapse
You have the latest version of TWRP? Theoritically, it should mount properly. Also, what Android version do you currently have?
DJBhardwaj said:
You have the latest version of TWRP? Theoritically, it should mount properly. Also, what Android version do you currently have?
Click to expand...
Click to collapse
Yes. Using Heisenberg's guide.....downloaded twrp 3.0.2-3 I believe. I also searched online and found 3.0.2.2 and that did the same thing.....wouldn't mount. Trying to root N. Thanks.
Ryno77 said:
Yes. Using Heisenberg's guide.....downloaded twrp 3.0.2-3 I believe. I also searched online and found 3.0.2.2 and that did the same thing.....wouldn't mount. Trying to root N. Thanks.
Click to expand...
Click to collapse
How about starting fresh by flashing the factory image? As I said, it should work, but for some reason it isn't.
I am running Nougat encrypted with TWRP and Root. For me it mounted perfectly.
DJBhardwaj said:
How about starting fresh by flashing the factory image? As I said, it should work, but for some reason it isn't.
I am running Nougat encrypted with TWRP and Root. For me it mounted perfectly.
Click to expand...
Click to collapse
Here's what I did yesterday. I downloaded dp4 because it worked better for me than U was. Flash all.bat. Booted phone and partially set up. Downloaded SU to internal storage, booted to bootloader, fastboot flash recovery twrp.img, reboot recovery.....found SU but couldn't do anything with it because system wasn't mounted. Tried all of this twice. Had a thought while typing this....twrpp not compatible with dp4 maybe? I'm on T now so I'd assume it would work if I tried again if that's the case. Thanks for the help.
Ryno77 said:
Here's what I did yesterday. I downloaded dp4 because it worked better for me than U was. Flash all.bat. Booted phone and partially set up. Downloaded SU to internal storage, booted to bootloader, fastboot flash recovery twrp.img, reboot recovery.....found SU but couldn't do anything with it because system wasn't mounted. Tried all of this twice. Had a thought while typing this....twrpp not compatible with dp4 maybe? I'm on T now so I'd assume it would work if I tried again if that's the case. Thanks for the help.
Click to expand...
Click to collapse
Instead of DP4, install the stable final release of nougat. TWRP had issues with Developer Preview.
Sounds good. Thanks again for the help.
Still have the same problem. I feel like I'm missing something obvious.
I got it to work. Not sure what I did to get it to work but I'm all set.
Finally flyme 6.0 beta official is released
link :- http://www.flyme.cn/firmwarelist-76.html#8
i just install this flyme 6.0 beta...seems to be great...dont know yet if it could be used as a daily...feedback later...thanks
So any reviews?
My review for the previous version of flyme 6, was this:
"Just flashed.. Great animations, graphics, sounds and a unique feeling in general.
BUT! This rom asks for every single app for internet and location permissions! from calendar to gallery and notes, in music app and so on.. And if you don't to give permissions there is only an "exit" option and you can't use the app! Maybe it's safe but it seems to me a little shady.
There are many chinese apps preinstalled which explains the size of the rom.
Furthermore some notifications are in chinese and you can't understand what they say.
I flashed opengapps after flashing the rom with no success, so I used a google installer from their store and it worked just fine..
Photos from the camera are stretched and Gallery doesn't show anything as mentioned..
wifi/bluetooth/data works fine."
(I don't know if any of these changed in this version)
Mchasard said:
i just install this flyme 6.0 beta...seems to be great...dont know yet if it could be used as a daily...feedback later...thanks
Click to expand...
Click to collapse
can you please mirror it because it seems like the official link is not working. I really want to download but not able to download from anywhere
download worked for me but failed to flash with status 7 error !! what's causing that anybody??
intoxicated.mad said:
download worked for me but failed to flash with status 7 error !! what's causing that anybody??
Click to expand...
Click to collapse
First flash oos 3.1.4 then wipe only dalvik cache/data don't wipe system.
ajmcklosky said:
First flash oos 3.1.4 then wipe only dalvik cache/data don't wipe system.
Click to expand...
Click to collapse
Thanked .... worked perfectly
intoxicated.mad said:
download worked for me but failed to flash with status 7 error !! what's causing that anybody??
Click to expand...
Click to collapse
please can you share zip with me on google drive or any where else ?
download link is not working for i tried many times
tapanrgohil said:
please can you share zip with me on google drive or any where else ?
download link is not working for i tried many times
Click to expand...
Click to collapse
Try this link: http://openrom-dl.flyme.cn/111732199/20170704/1499109120027/flyme_ONE-E1001_xs_6.7.6.30R-beta.zip
Did anyone flash it? I was stuck at TWRP. It wont boot to rom.
sundhar88 said:
Did anyone flash it? I was stuck at TWRP. It wont boot to rom.
Click to expand...
Click to collapse
First flash oos 3.1.4 then wipe only dalvik cache/data, don't wipe system.
ajmcklosky said:
First flash oos 3.1.4 then wipe only dalvik cache/data, don't wipe system.
Click to expand...
Click to collapse
I did that. nothing helped.
did you flashed successfully?
what version of twrp do you have?
It flashes its own twrp
sundhar88 said:
I did that. nothing helped.
did you flashed successfully?
what version of twrp do you have?
It flashes its own twrp
Click to expand...
Click to collapse
Yes, it worked perfectly on twrp 3.0.2-2 bluespark v41.
try flashing any other ROM or try downloading the ROM again.
Check if you can access the downloaded ROM files in winRAR or any zip extractor.
sundhar88 said:
I did that. nothing helped.
did you flashed successfully?
what version of twrp do you have?
It flashes its own twrp
Click to expand...
Click to collapse
I guess this ROM is for old boot loader.
How are y'all finding the ROM? How stable is it?
EDIT: I just flashed it and I really hate it. Prefer to use stock android
sundhar88 said:
I did that. nothing helped.
did you flashed successfully?
what version of twrp do you have?
It flashes its own twrp
Click to expand...
Click to collapse
Got a workaround just unmount system and then flash.
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.