Database Info

[Q] "Error mounting /data!" in Clockworkmod

I'm trying to install Cyanogenmod to my Nexus 5. (I installed it successfully to my Nexus 7 2012 and was very pleased with it.) I've been following the instructions on this page: http://wiki.cyanogenmod.org/w/Install_CM_for_hammerhead, but I can't get Clockworkmod to mount the /data partition. I get an error. It just says "Error mounting /data!" and nothing else.
I get numerous other errors when trying to do just about anything else. I've also tried reinstalling Clockworkmod.
This is kinda/sorta urgent, because I'm without a phone until I can get this resolved. [**Another update: Not as urgent as I thought because Lollipop does boot up after all. Still, I really like CM and I'd love a solution.]
Update: One thing I should have mentioned is that I'm using adb and fastboot in Linux Mint 17.1. I don't know how relevant that is, but I thought it was worth mentioning.

Get rid of Clockworkmod, it's outdated and was discontinued quite a while ago. Use TWRP 2.7.1.0.

BirchBarlow said:
Get rid of Clockworkmod, it's outdated and was discontinued quite a while ago. Use TWRP 2.7.1.0.
Click to expand...
Click to collapse
Well, that's interesting; I had no idea. Would the instructions on that page be more-or-less the same, but with TWRP?
Update: So far, seems to have worked. The phone is booting into Cyanogenmod right now for the first time. I'll report back if there are any problems, but so far everything looks fine.
To answer my own question (for anybody who may come across this via Google), the instructions on that page do actually work almost identically with TWRP. Also, TWRP 2.8 did not work for me, but the specific number listed by BirchBarlow did.
Again, to BirchBarlow, thank you very much!

adanedhel728 said:
Well, that's interesting; I had no idea. Would the instructions on that page be more-or-less the same, but with TWRP?
Update: So far, seems to have worked. The phone is booting into Cyanogenmod right now for the first time. I'll report back if there are any problems, but so far everything looks fine.
To answer my own question (for anybody who may come across this via Google), the instructions on that page do actually work almost identically with TWRP. Also, TWRP 2.8 did not work for me, but the specific number listed by BirchBarlow did.
Again, to BirchBarlow, thank you very much!
Click to expand...
Click to collapse
*headbang* I meant to say TWRP 2.8.1.0 (2.8.2.0 is faulty), but anyway you're welcome.

BirchBarlow said:
*headbang* I meant to say TWRP 2.8.1.0 (2.8.2.0 is faulty), but anyway you're welcome.
Click to expand...
Click to collapse
Haha, glad to know it.

FNF Ifive Mini 4S root?

Hello xda,
I recently bought the newly released FNF Ifive Mini 4S from Banggood and i was wondering if anyone is planning to make a root and/or custom recovery for it?
Thanks

+1
Me too, I own one of the beauties, and I would love to have it rooted!

fdomi said:
+1
Me too, I own one of the beauties, and I would love to have it rooted!
Click to expand...
Click to collapse
What are your experiences so far?

I just bought one for about 85€.
Hope it gets a little more attention and someone can root it.

Where? Can't find it for that price.

Hello, Can owners of this tablet give me some info on it's thermal performance? Specifically, how warm the case gets on the hands, CPU temps under load and the SoCs throttling behavior.
Thanks.

lost2 said:
Where? Can't find it for that price.
Click to expand...
Click to collapse
It was an offer/sale on Gearbest!
However it wasnt shipped even after 2 weeks... china :fingers-crossed:
R. D. said:
Hello, Can owners of this tablet give me some info on it's thermal performance? Specifically, how warm the case gets on the hands, CPU temps under load and the SoCs throttling behavior.
Thanks.
Click to expand...
Click to collapse
Will do if i get my hands on mine! Will do some stress tests and see how warm it gets!

I ordered it too for 100$ on gearbest. Finally after week and a half it is shipped out now, but tracking still shows pre-advised, so I think I won't get it for at least 2-3 weeks

Ordered mine from gearbest a couple days ago so it will be a while before I get it. I have rooted and installed custom firmwares on other tablets before so I have a basic understanding of how things work but I have never done this totally from scratch. I have been doing a lot of research and study on this and have a few ideas. First thing I'm going to try is to boot a custom recovery for the rk2388 chip with the fastboot boot recovery.img command and then then do some backups of the nand. After that I will try to extract the kernel from stock and insert it into a generic android 6.01 rom and see if I can flash it from within the custom recovery. Hopefully it will work( I know I will have to work on drivers and such too) but first things first just want to see if it will work. My main thing I'm scared of is messing it up and bricking the tablet. I'm hoping that providing fastbooting the custom recovery works I can restore to stock ROM if I mess anything up. Wish me luck and let me know if you have any ideas that may help.

+1 interested in this tablet.

Απουσιολόγος said:
For root, try "Kingroot ".
Click to expand...
Click to collapse
Have you tested it?

In this specific device no, but it worked in all devices I own.

When you get it, give KingoRoot a try. Chances are it will work.. Hopefully..

Joeblah said:
Ordered mine from gearbest a couple days ago so it will be a while before I get it. I have rooted and installed custom firmwares on other tablets before so I have a basic understanding of how things work but I have never done this totally from scratch. I have been doing a lot of research and study on this and have a few ideas. First thing I'm going to try is to boot a custom recovery for the rk2388 chip with the fastboot boot recovery.img command and then then do some backups of the nand. After that I will try to extract the kernel from stock and insert it into a generic android 6.01 rom and see if I can flash it from within the custom recovery. Hopefully it will work( I know I will have to work on drivers and such too) but first things first just want to see if it will work. My main thing I'm scared of is messing it up and bricking the tablet. I'm hoping that providing fastbooting the custom recovery works I can restore to stock ROM if I mess anything up. Wish me luck and let me know if you have any ideas that may help.
Click to expand...
Click to collapse
If you brick it FNF has a recovery tool themselves. It is an update/recovery tool and can be found by googleing: fnf ifive mini 4s upgrade tool. Just pick the first one from techtablets.com.

There seems to be TWRP available for similar RK3288 Tablets here: http://crewrktablets.arctablet.com/?p=4776
It's a bit of an old post though, only TWRP 2.8.4.0, not sure if it will work 100% on this device. Would love to know if it works.

stephendt0 said:
There seems to be TWRP available for similar RK3288 Tablets here: http://crewrktablets.arctablet.com/?p=4776
It's a bit of an old post though, only TWRP 2.8.4.0, not sure if it will work 100% on this device. Would love to know if it works.
Click to expand...
Click to collapse
I found this post as well yesterday and decided to test it. TWRP does not seem to work, but CWM works just fine! I successfully installed chainfires supersu. Should I write a small tutorial or something?

UnknownDK said:
I found this post as well yesterday and decided to test it. TWRP does not seem to work, but CWM works just fine! I successfully installed chainfires supersu. Should I write a small tutorial or something?
Click to expand...
Click to collapse
Yes please!

stephendt0 said:
Yes please!
Click to expand...
Click to collapse
Will get right to it then!

stephendt0 said:
Yes please!
Click to expand...
Click to collapse
It is done You can find it here

Today is shaping up to be a great day. First I wake up and receive notice stating that my tablet has finally shipped. Then I come here and see more activity on this forum with progress. Congrats and good job on installing chanfires SuperSU DK. Does that mean you have full root now? And also did you install cwm or use the fastboot boot recovery recovery.img command just to boot the recovery?

Needing rom flashing advice

The phone is not fully booting.

What?

aholeinthewor1d said:
What?
Click to expand...
Click to collapse
Just because my Verizon pixel ran into a boot loop after Resurrection rom a change grom purenexus. I've known issues from the past to be about build, ( European, ECT.) Or order of operations. Even supersu, usually after the fact for supersu. As a junior member with some xp I started this thread anyway after an Odin to stock. What did I do wrong,? Google pixel, Verizon, NOF26V, unlocked. I flashed twice, then Odin. Still looped.

April fool's ... ? Odin ... Really

piperx said:
April fool's ... ? Odin ... Really
Click to expand...
Click to collapse
I was thinking the same thing

Right so... I wanted to flash Resurrection rom. I did that with TWRP duh. And pixel won't finish it's boot for 30plus minutes after. So what do I do? I Odin stock NOF26V in download mode to get my phone running again. Comprehend?

piperx said:
April fool's ... ? Odin ... Really
Click to expand...
Click to collapse
Yeah, Odin. Download mode. That's how to save a phone from a bad rom flash

alladinscastle said:
Yeah, Odin. Download mode. That's how to save a phone from a bad rom flash
Click to expand...
Click to collapse
Odin is a Samsung thing. Fastboot mode or recovery or bootloader mode are the usual terms for a Google phone.

alladinscastle said:
Right so... I wanted to flash Resurrection rom. I did that with TWRP duh. And pixel won't finish it's boot for 30plus minutes after. So what do I do? I Odin stock NOF26V in download mode to get my phone running again. Comprehend?
Click to expand...
Click to collapse
I comprehend just fine, the real question though:
Do you have any idea what your doing ?

piperx said:
I comprehend just fine, the real question though:
Do you have any idea what your doing ?
Click to expand...
Click to collapse
I had no problems flashing pureexus on my Verizon pixel. Resurrection rom is giving me problems. Phone won't boot past Google screen. Matched vendor. It's not that. What Android build is Resurrection Rom based on?

alladinscastle said:
I had no problems flashing pureexus on my Verizon pixel. Resurrection rom is giving me problems. Phone won't boot past Google screen. Matched vendor. It's not that. What Android build is Resurrection Rom based on?
Click to expand...
Click to collapse
Really?
https://forum.xda-developers.com/pixel-xl/development/rom-t3548615

If im running 7.1.1 and Resurrection is 7.1.0. could the downgrade from flashing cause my problem?

alladinscastle said:
If im running 7.1.1 and Resurrection is 7.1.0. could the downgrade from flashing cause my problem?
Click to expand...
Click to collapse
wipe your data and cache partitions.

alladinscastle said:
I had no problems flashing pureexus on my Verizon pixel. Resurrection rom is giving me problems. Phone won't boot past Google screen. Matched vendor. It's not that. What Android build is Resurrection Rom based on?
Click to expand...
Click to collapse
How in the hell do people flash things they know nothing about?
Do you read at least the op of anything you flash?
I'm still tryin to get over the Odin post

Answer this. Resurrection's thread title says 7.1.1. The Op says 7.1.0r7. " users are now asking if the new build will be 7.1.2. " What is is the current build based on. If the Op is outdated, what good is it?
P.s. I have seen some op updates on the rom thread... ok, some things are still outdated.
Your attitude needs work, maybe consider not replying. I do know some things about rom flashing. It is unnecessary to be rude. It is ok to make corrections about a post.

piperx said:
How in the hell do people flash things they know nothing about?
Do you read at least the op of anything you flash?
I'm still tryin to get over the Odin post
Click to expand...
Click to collapse
Do you enjoy showing off? At be more class at it.......

alladinscastle said:
Do you enjoy showing off? At be more class at it.......
Click to expand...
Click to collapse
Just because I do my homework (read, read some more, read again, read til I fully understand) before I blindly install something is not showing off.
It's called "common sense"
This stuff is not rocket science

piperx said:
Just because I do my homework (read, read some more, read again, read til I fully understand) before I blindly install something is not showing off.
It's called "common sense"
This stuff is not rocket science
Click to expand...
Click to collapse
I agree on this. I do the same, read, read, and read some more until I understand what I am doing. I used to root phones that aren't "google" versions and learned how much of a pain it was.. therefore I am owned the last Nexus brand, and the first Pixel. Using a Google phone is so much easier! But yeah, reading is key. I hopped into this thread to see if someone needed some help, read through the posts, and was so lost as to what this user is doing.. Odin? If the user who is having issues is reading this, just boot your phone to bootloader, use fastboot and format userdata the device (wipe/format) and then fastboot flash the stock 7.1.2 image and wait for custom ROMs to update.

piperx said:
Just because I do my homework (read, read some more, read again, read til I fully understand) before I blindly install something is not showing off.
It's called "common sense"
This stuff is not rocket science
Click to expand...
Click to collapse
Alright moving on. Just generic crap on my thread here

Great news. I'm am now running Resurrection ROM. All I did differently for my Verizon pixel was move from 26V to 27B build. I flashed the rom and twrpRC1, Then I rebooted to bootloader mode and flashed the vender using the adb fastboot command. "Fastboot flash vendor vendor.img" need more specific instruction. See me!!! No more problems here.

ADB and 8T

Okay... I've been searching all over the net for this problem and I keep getting posts that skirt the issue. At least, that's what it seems. So I will begin and you can decide... and thanks for whatever info you can throw my way.
Brand new OnePlus 8T. I want to root it. Duh. So, Got the Tiny ADB and Fastboot package and all the rest, but the issue is with unlocking the bootloader. Other problems may appear later, but this is the issue now.
So, connect phone to PC (Windows 8.1) and the only way that ABD recognizes my phone is when the USB prefs are set to 'No Data Transfer". Yes, I have installed the proper drivers from the phone. So, when the 'No Data Transfer' is selected, ADB recognizes the phone and will issue the command, ABD Reboot Bootloader and the phone reboots to the bootloader. Nice! Unfortunately, it appears that once the phone has booted to the bootloader, it has changed the USB Prefs and now ADB and fastboot do not see the phone. Obviously this sucks. And here is the problem. As far as I know, I have ticked off on all the proper settings. USB Debugging, etc. No joy!
I found a post elsewhere that showed how to set the default USB mode and that didn't work either. My experience has been that ADB used to see the phone under the 'File Transfer' and PTP options before, but it doesn't now. I can't explain this.
So, pretty frustrated. This shouldn't be so bloody difficult. It's only a couple of commands and I have done this with other phones in the past so it's not like I have no previous experience. But I have already wasted way too much time here this go around. Anyone have an answer? I'll be your best friend!!
Thanks all..
R

Try nother USB C cable. Some not able to handle data.

rogerebert said:
Try nother USB C cable. Some not able to handle data.
Click to expand...
Click to collapse
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!

Ran Doid said:
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Click to expand...
Click to collapse
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/

BillGoss said:
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
Click to expand...
Click to collapse
Hey Thanks, Bill. I"ll give this a whirl and see how it goes. I'll report back after. Cheers!

Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R

Ran Doid said:
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Click to expand...
Click to collapse
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.

BillGoss said:
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
Click to expand...
Click to collapse
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??

Ran Doid said:
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Click to expand...
Click to collapse
Sorry, I've no idea about that. Try flashing TWRP again.

BillGoss said:
Sorry, I've no idea about that. Try flashing TWRP again.
Click to expand...
Click to collapse
Okay, well.. I'll have to figure it out then. Thanks much, Bill. Appreciate your help. Happy Holidays!

Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...

Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11

BillGoss said:
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
Click to expand...
Click to collapse
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,

Mickade said:
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Click to expand...
Click to collapse
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".

BillGoss said:
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
Click to expand...
Click to collapse
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Thx,

Mickade said:
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Click to expand...
Click to collapse
If they could fix the interminable start up time for TWRP that would be brilliant. But I believe the problem is with a file system check rather than the actual decryption which is quite fast.
Sorry, croquettes and mash aren't in my menu. But empanadas - absolutely!

Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R

Ran Doid said:
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Click to expand...
Click to collapse
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.

BillGoss said:
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
Click to expand...
Click to collapse
There-in why I asked if you might point me at something reliable. But I guess not...
Thanks anyway..

Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
Actually a trick you can use is in twrp if you have the magisk APK change the ext to zip and install in twrp it patches the boot img for you in right slot so you don't have to pull img from phone

Development [CLOSED][KERNEL] [Android 13] [v13.1] MVK - Maximum Velocity Kernel

.

Reserved
Placeholder thread for further development

Kernel development is fast underway. Those interested in helping test please let me know. The first thing I need to test is whether the builds Im making will work on ALL variations of the June release. Im just on the generic one and thats what I built for but anyone on a carrier build or the JP one that wants to verify boot and that things are working correctly that would be extremely helpful.

I have a rooted T-Mobile 6a if you're still looking for a tester.

Delete

ctfrommn said:
Delete
Click to expand...
Click to collapse
I can test. I'm on the Verizon build.

Give me some time.....stuff ended up not working as intended. Probably tomorrow, but thank you.

Sounds good, looking forward to it. Also yes I'm on the June build.

Every new device I get has a learning curve to building for it. This one is totally new to me but Ill get it sorted out soon enough one way or another.
Ideally I want to resurrect Velocity....baby steps though

Sounds like a winner to me...I'm all about AOSP1
I'll let you sink your teeth into it and will prolly jump in after the August update...have a feeling it'll be substantial. We share the same opinion...fast and dependable above all.

Ok, I think were finally cooking with gas.....looks like gone are the days of a simple boot.img flash and Ill need to migrate to using an anykernel zip format, which is fine and in a lot of ways simpler provided you have an app to flash them. Not sure if you can sideload these but Ill look into it further. I should have an actual test up yet today for anyone who can flash it.

ctfrommn said:
Every new device I get has a learning curve to building for it. This one is totally new to me but Ill get it sorted out soon enough one way or another.
Ideally I want to resurrect Velocity....baby steps though
Click to expand...
Click to collapse
Yeah, I'm getting back into it after years of not messing with my phones, my last real contribution to XDA was in 2019. This time I'm hoping to get into the development scene rather than just messing around, good luck! Lots if not everything has changed since my days.

I ran out of time to get anything super exciting done (this is a giant PITA) but there is a zip in the test folder that "should" work on all June builds but feel free and let me know if it doesnt.
At this point this is a optimized (slightly by my standards) stock build. Everything works normally and it does feel better.
No idea if this works via ADB sideload but kernel apps should all work, FKM does for sure.

ctfrommn said:
I ran out of time to get anything super exciting done (this is a giant PITA) but there is a zip in the test folder that "should" work on all June builds but feel free and let me know if it doesnt.
At this point this is a optimized (slightly by my standards) stock build. Everything works normally and it does feel better.
No idea if this works via ADB sideload but kernel apps should all work, FKM does for sure.
Click to expand...
Click to collapse
After flashing it with FKM, how would I go about getting Magisk flashed again? I haven't used FKM in quite a while.

JRJ442 said:
After flashing it with FKM, how would I go about getting Magisk flashed again? I haven't used FKM in quite a while.
Click to expand...
Click to collapse
If youre rooted now you will be after as well

Can we get a variant for a13 beta?
Look forward to trying this out

ctfrommn said:
I ran out of time to get anything super exciting done (this is a giant PITA) but there is a zip in the test folder that "should" work on all June builds but feel free and let me know if it doesnt.
At this point this is a optimized (slightly by my standards) stock build. Everything works normally and it does feel better.
No idea if this works via ADB sideload but kernel apps should all work, FKM does for sure.
Click to expand...
Click to collapse
Flashing with FKM results in boot loop for me, flashing stock boot.img didn't fix it. I'll just have to flash full stock firmware with wipe option disabled.
EDIT: Phone really did not like me using the flash-all.bat from firmware to flash it, refused to flash system partitions. Ended up using Android Flash Tool from Google and now the phone is back.
Thankfully the 6a is not my main phone so I can keep testing builds even if they bork the phone. Let me know if you need any logs.

What build are your on?

ctfrommn said:
What build are your on?
Click to expand...
Click to collapse
SD2A.220601.002

Interceptor777 said:
SD2A.220601.002
Click to expand...
Click to collapse
Very weird, works fine for me