Related
Required:
Install B2CAppSetup.exe, LG PC Suite IV and related driver.
1. Run LGMobile update
2. Plug your optimus 3d (debug mode on) and wait for the connection
3a. If there is a new version, click on Start upgrading software for lg phone
3b. If you allready have latest version, click on User/Support then emergency mode, insert your IMEI and click on check
4. Wait for download and upgrading (15/20 min)
PS. you will loose root, but you will not loose data, data.img is untouched
PS2. if you got some problems, try again. I've tried few time before have a successfully flash.
Thanks Fabio!!
Trying it now
Lets hope it works
It Worked
I was on the right path before, but i took 3 tries to get it updated!
Thanks!
Renegade_Rulez said:
Trying it now
Lets hope it works
It Worked
I was on the right path before, but i took 3 tries to get it updated!
Thanks!
Click to expand...
Click to collapse
What do you mean by 3 tries? What error message were you getting, if any?
shollywood said:
What do you mean by 3 tries? What error message were you getting, if any?
Click to expand...
Click to collapse
It just stopped at 50% and the third time it worked.
Thanks....
I keep getting phone does not support S/W update message
Sent from my SCH-I510 using XDA App
I'm having the same problem as the person above me.. i tried so many times.. i still get the same message "software not supported for this model.."
Please help..
Im in the US , have a developer model on May software. I changed the country to UK and was able to install drivers. I installed Pc Suite. But still getting that error message stating my phone model don't support s/w update
Sent from my SCH-I510 using XDA App
largo79 said:
Im in the US , have a developer model on May software. I changed the country to UK and was able to install drivers. I installed Pc Suite. But still getting that error message stating my phone model don't support s/w update
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Is it possible your model is 925 and not 920?
We need CWM so we can make a backup before trying to mess around in the system
It seems my recovery partition was messed up so again install original rom...
Renegade_Rulez said:
We need CWM so we can make a backup before trying to mess around in the system
It seems my recovery partition was messed up so again install original rom...
Click to expand...
Click to collapse
ROM Manager should start supporting the p920 later today.
erezak said:
Is it possible your model is 925 and not 920?
Click to expand...
Click to collapse
No its a 920 as I'm getting the same. So your updater always defaults to USA when you open it up correct?
aremcee said:
ROM Manager should start supporting the p920 later today.
Click to expand...
Click to collapse
wow thanks
The famous CM developer aremcee, nice to see you here as well.
Really loving your work on the LG O2x!
Looking forward to use CM7 on my O3D as well if someone decides to pick up the challenge (hint hint )
Renegade_Rulez said:
wow thanks
The famous CM developer aremcee, nice to see you here as well.
Really loving your work on the LG O2x!
Looking forward to use CM7 on my O3D as well if someone decides to pick up the challenge (hint hint )
Click to expand...
Click to collapse
It'll be a while before that. We had zero support for OMAP4 in CM, and merging it in will have to be done carefully to avoid breaking everything else. The only thing I merged in already was the bootimage-building stuff, in order to get CWM out there.
aremcee said:
It'll be a while before that. We had zero support for OMAP4 in CM, and merging it in will have to be done carefully to avoid breaking everything else. The only thing I merged in already was the bootimage-building stuff, in order to get CWM out there.
Click to expand...
Click to collapse
No hurry for that, whenever you are ready we will see it
Thanks a lot for your hard work!
aremcee said:
ROM Manager should start supporting the p920 later today.
Click to expand...
Click to collapse
Done. You can now flash CWM from ROM Manager (and reboot into recovery, and backup, and all the neat stuff RM does) on the O3D.
aremcee said:
Done. You can now flash CWM from ROM Manager (and reboot into recovery, and backup, and all the neat stuff RM does) on the O3D.
Click to expand...
Click to collapse
Did my first backup feels good to be safe again!
Can I move the backup to external sd?
Sent from my LG-P920 using Tapatalk
Where can i find the CWM for this phone?
My phone model is LGP929 -- and its running the 08 software
I rooted my tablet and it worked fine. I then proceded to modify my build.prop file. My friend sent me his to work from but i mistakenly copied it over directly. Now the tablet will not boot. How can i restore to factory or whatever i need to do?
(please spare me from the "you shouldn't have done that" speech, trust me i know lol)
need more info
what model number do you have, what can you get into, what cant you get into etc
lowgoz said:
need more info
what model number do you have, what can you get into, what cant you get into etc
Click to expand...
Click to collapse
sorry, late night, not really with it lol
its model tf101 US version and it has the latest ICS firmware, stock recovery. i can get it to load the recovery screen with the wipe data option. sorry for my poor terminology im new to the whole android rooting stuff.
You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf
baseballfanz said:
You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf
Click to expand...
Click to collapse
i've already tried this. it just gives me the dead android with a red exclamation point. also for some reason my windows pc says "the device cannot start" and im unable to use adb.
What is the serial number of your tf?
Hopefully it's one that's nvflash compatible
baseballfanz said:
What is the serial number of your tf?
Hopefully it's one that's nvflash compatible
Click to expand...
Click to collapse
dont think it is, starts with B90
i think the mods rudely removed my post in general forum where i was actually getting some help, but whatever. still need help here if anyone has any ideas.
I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.
gee one said:
I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.
Click to expand...
Click to collapse
ok well heres the issue. earlier way early this morning when this first started i was able to adb in, saw it was going in an infinite loop in logcat. now for some reason windows, and i've tried 3 installations of it, says the device cannot start. to me it sounds like something weird with the device. any ideas?
The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?
roflcopterofl said:
The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?
Click to expand...
Click to collapse
i think its too late for that now, adb wont work. im guessing now maybe the recovery isnt working because i had a newer version of the os than i can get a copy of right now. anyone have/know where i can get 9.2.1.17 fw?
If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.
gee one said:
If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.
Click to expand...
Click to collapse
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?
joshcrumley100 said:
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?
Click to expand...
Click to collapse
just tried it on linux, adb wont detect the device, so no luck there. im just hoping the .17 firmware will work on it, if not idk what to do.
In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??
gee one said:
In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??
Click to expand...
Click to collapse
it had Asus Transformer or something like that, it had it listed, but thats all. couldnt interact with the device.
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
gee one said:
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...
Originally Posted by gee one
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...
Click to expand...
Click to collapse
Sorry for the confusion- I think the full 9.2.1.17 rom that asus posts on their website will work, as long as it checks the rom version in recovery default.prop. It's not clear to me how it checks the "rule" that prevents downgrading. It's a maybe, but there's still a chance.
sent from my cyanogen(mod) vision
Hi, I read that anyone with a developer's account can access the developers' preview build of Android L, that was supposed to be available today, I have a developer's account (to upload apps to the market) but I don't see any build of android L, is this the required account? or is there any other type of account required? thanks!
saman0suke1 said:
Hi, I read that anyone with a developer's account can access the developers' preview build of Android L, that was supposed to be available today, I have a developer's account (to upload apps to the market) but I don't see any build of android L, is this the required account? or is there any other type of account required? thanks!
Click to expand...
Click to collapse
it will be here when its released, as of yet it is not released
http://developer.android.com/index.html
keep refreshing the page like the rest of us
saman0suke1 said:
Hi, I read that anyone with a developer's account can access the developers' preview build of Android L, that was supposed to be available today, I have a developer's account (to upload apps to the market) but I don't see any build of android L, is this the required account? or is there any other type of account required? thanks!
Click to expand...
Click to collapse
I guess it'll be available in a few hours.
I guess they just haven't released it, yet.
Don't forget their different timezone.
Thank you all, maybe I'm getting too desperate I just wanted to confirm that my account is the right one, I'll be refreshing until it appears, thanks again!
EDIT: I believe being rooted would not be a problem at the moment of the installation, right? I know that I'll lose root after that, but as long as the actual installation does not give me problems, it's fine.
saman0suke1 said:
Thank you all, maybe I'm getting too desperate I just wanted to confirm that my account is the right one, I'll be refreshing until it appears, thanks again!
EDIT: I believe being rooted would not be a problem at the moment of the installation, right? I know that I'll lose root after that, but as long as the actual installation does not give me problems, it's fine.
Click to expand...
Click to collapse
Considering that the images will have to be flashed through fastboot, you'll probably lose root and everything else on data/system partitions (unless they don't wipe it, but I think it does).
saman0suke1 said:
Thank you all, maybe I'm getting too desperate I just wanted to confirm that my account is the right one, I'll be refreshing until it appears, thanks again!
EDIT: I believe being rooted would not be a problem at the moment of the installation, right? I know that I'll lose root after that, but as long as the actual installation does not give me problems, it's fine.
Click to expand...
Click to collapse
maybe it will be problem to root new androi L cause I've read somwhere that there is a lot of security updates and also samsung knox in new android so we will see if it will be able to root
saman0suke1 said:
Thank you all, maybe I'm getting too desperate I just wanted to confirm that my account is the right one, I'll be refreshing until it appears, thanks again!
EDIT: I believe being rooted would not be a problem at the moment of the installation, right? I know that I'll lose root after that, but as long as the actual installation does not give me problems, it's fine.
Click to expand...
Click to collapse
if it's a factory image it'll wipe the whole phone and root probably wont work until its updated to support L
MidnightDevil said:
Considering that the images will have to be flashed through fastboot, you'll probably lose root and everything else on data/system partitions (unless they don't wipe it, but I think it does).
Click to expand...
Click to collapse
That's fine, I believe that flash through fastboot does not include a total wipe including camera folder and all that right? never done it that way, better be prepared. Thanks!
saman0suke1 said:
That's fine, I believe that flash through fastboot does not include a total wipe including camera folder and all that right? never done it that way, better be prepared. Thanks!
Click to expand...
Click to collapse
As long as you don't flash the userdata.img, all /sdcard data will be fine. You don't have to flash userdata.img to bump android versions! System, boot would do just fine (and bootloader if they bump it as well)
Or you could just wait till a flashable zip is posted. Someone will have one up within hours of release.
Roxas598 said:
if it's a factory image it'll wipe the whole phone and root probably wont work until its updated to support L
Click to expand...
Click to collapse
Whole phone means photos, and any kind of files? I prefer to ask so I make a backup first :S , never done it this way, thanks!
saman0suke1 said:
Whole phone means photos, and any kind of files? I prefer to ask so I make a backup first :S , never done it this way, thanks!
Click to expand...
Click to collapse
Read my previous post.
saman0suke1 said:
Whole phone means photos, and any kind of files? I prefer to ask so I make a backup first :S , never done it this way, thanks!
Click to expand...
Click to collapse
Yep every single thing on the phone will be gone so backup everything you need
saman0suke1 said:
That's fine, I believe that flash through fastboot does not include a total wipe including camera folder and all that right? never done it that way, better be prepared. Thanks!
Click to expand...
Click to collapse
You'll lost everything... Photos,data file...
vin4yak said:
As long as you don't flash the userdata.img, all /sdcard data will be fine. You don't have to flash userdata.img to bump android versions! System, boot would do just fine (and bootloader if they bump it as well)
Click to expand...
Click to collapse
Unless they changed the folder structure like they did a few releases ago - if they did, best to do a clean install.
I'm backing up right now just in case.
Don't wanna mess with the installation script by flashing some things and not others (although there would be virtually no risk by flashing system and boot partition), but better safe than sorry, after all, we can just shove everything back when finished
Consider ir a backup routine, and you'll have an updated bk
jj14 said:
Unless they changed the folder structure like they did a few releases ago - if they did, best to do a clean install.
Click to expand...
Click to collapse
That's an entirely different scenario. Each and everyone of us would need to wipe clean if that happens but usually a system and boot flash would do just fine
The N5 has been my FIRST of many, many, many Android phones and even Windows Pocket PC phones that I haven't felt the need to unlock/root etc. Everything has just worked great on it and I have always been able to do everything I wanted to do from this phone. I have been so satisfied with the phone that it has kept me away from XDA for a while. Don't know if that is a good thing or bad, lol. I used to be on this site for hours every single day and now I feel like I am light years behind in rooting. HA!
L has me interested though and I am contemplating unlocking my bootloader for it which just becomes a PITA with losing your data and adding things back and all that great stuff that takes so much of your time. Then if things suck you have to flash back to something else and the never ending process continues. The N5 has gotten me so much time back in my life but I feel like it might demand some of my time back to it. Oh I hate this stuff!!!!
I think I'll make a backup, just in case, as someone said previously, I would prefer to make a clean installation if it's needed and use the image provided by Google.
Thanks!
Hello everyone, i have learned to port ubuntu touch on other device for a few days, and this is the first time for me to port a ubuntu touch rom.
This rom is based on phablet-20130303-cm_mb526.zip for defy, and i added some milestone2's bin, lib, bootmenu and etc in it so that it could run on our milestone2.
Don't get happy yet. As you know, i'm new here and i even don't have this phone(i have d2g, it doesn't have any cm10.1+ rom). so this rom is just a homework for me to check whether i could port ubuntu touch or not. i don't know what will happen after you flash this rom, so please make sure that you can fix your phone by bootmenu or rsd.
how to flash it?
1. Backup your current Rom.
2. Download the Milestone2 Mini-Android base for Ubuntu Touch and place it on your device:
https://drive.google.com/file/d/0Bylduk-LZybUelp6SGV0ZFlvWGM/view?usp=sharing
3. Download the Touch Preview Filesystem .zip and place it on your device:
http://www.mediafire.com/?dg5bf836ohvioot
4. Wipe all (data/cache, dalvik cache)
IMPORTANT:
5. Install the armhf package FIRST, and then the phablet-20141025-ubuntutouch_milestone2.zip SECOND.
thanks for @lukasz124 finding this problem！
6. Reboot and See whether your device can boot or not.(it will cost about 5-10 minutes for your device to boot if this rom could work, and no bootanimation!)
7a. To switch off your phone remove the battery manually
7b. To return back to android reboot back into recovery and reinstall or restore your rom.
8. If your rom is not booting it could be due to the ext 4 format of /data so go into stock recovery and wipe all (data/cache, dalvik cache), reboot, reinstall.
and that is all. i can't wait to see whether this rom can work or not!
thanks MYHK-to help me porting this rom kayant-for his defy ubuntu touch rom e-mars-for his porting work on cm
Tks, Anyone out there already tested? Has some print? Do you know if wifi, usb, etc, is working? Thanks
shulinbao said:
Don't get happy yet. As you know, i'm new here and i even don't have this phone(i have d2g, it doesn't have any cm10.1+ rom). so this rom is just a homework for me to check whether i could port ubuntu touch or not.
Click to expand...
Click to collapse
If this works you can have my phone. It's kinda crappy, but does the job.
Could not install the ROM.
Kiil said:
Could not install the ROM.
Click to expand...
Click to collapse
THANK YOU VERY MUCH FOR YOUR TESTING. there are two .zip file to flash, please tell me which .zip file could not install, thank you!
No problem. I could not make either one to work. Tried CWM and "install zip file", is this the correct procedure?
Kiil said:
No problem. I could not make either one to work. Tried CWM and "install zip file", is this the correct procedure?
Click to expand...
Click to collapse
thank you for your testing, it's a really strange problem. the Mini-Android base is port from cm11- milestone2 by e-mars and the Touch Preview Filesystem is official. i don't know whether my sign tool is ok or not, and i don't know if the script works well. you know is hard for me to solve any problem, but i always keep on trying it.
maybe i have to find others to keep on this project, i think if someone have any skill, it's not hard for him to port it.
shulinbao said:
thank you for your testing, it's a really strange problem. the Mini-Android base is port from cm11- milestone2 by e-mars and the Touch Preview Filesystem is official. i don't know whether my sign tool is ok or not, and i don't know if the script works well. you know is hard for me to solve any problem, but i always keep on trying it.
maybe i have to find others to keep on this project, i think if someone have any skill, it's not hard for him to port it.
Click to expand...
Click to collapse
I disabled signature checking, so it is not that. Unfortunately I'm not familiar with logging CWM otherwise you would get a nice log : D Yeah, it seems like a nice project, hopefully some people will join, droid/milestone series seems like a perfect one for Ubuntu.
Hi!! Thanks for trying to bring Ubuntu to our Milestone 2!
I've tried to install, but the system goes on infinite reboot. I think I'm doing something wrong.
yuriaps said:
Hi!! Thanks for trying to bring Ubuntu to our Milestone 2!
I've tried to install, but the system goes on infinite reboot. I think I'm doing something wrong.
Click to expand...
Click to collapse
How did you install it? Probably not through CWM?
yuriaps said:
Hi!! Thanks for trying to bring Ubuntu to our Milestone 2!
I've tried to install, but the system goes on infinite reboot. I think I'm doing something wrong.
Click to expand...
Click to collapse
THANK YOU FOR YOUR HELP! maybe i need log............................ i had a talked with myhk yesterday, he have been porting ubuntu touch for a year, and he told me that the way of my porting work seems right...
shulinbao said:
THANK YOU FOR YOUR HELP! maybe i need log............................ i had a talked with myhk yesterday, he have been porting ubuntu touch for a year, and he told me that the way of my porting work seems right...
Click to expand...
Click to collapse
It's probably us, then : D
What kind of methods would you use to flash it? Is cwm good enough or do you need adb?
Kiil said:
It's probably us, then : D
What kind of methods would you use to flash it? Is cwm good enough or do you need adb?
Click to expand...
Click to collapse
thank you for your helping!
i think cwm is ok, the log will only be used to find what cause the problem, and that will cost a long time... maybe after the android5.0 of milestone2 come out. the android 5.0 of defy came out yesterday in China and Russia, it won't take a long time to wait for the android 5.0 of miletone2.
but ubuntu touch of milestone2 is different..... as you know i don't have milestone2, it should take a long time in printing logs over and over again to find problem.
Did anyone install this?
I also got infinite reboot
I could donate you my kind of old milestone 2. Depends on postal charges, tho. Pm me, if you're interested.
.
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