I've attempted flashing the Pixel Android R GSI on my 7 Pro. The only problem is that I'm finding there is no sound, there are random reboots, and no data signal. I tried installing the GMS as was suggested, but to no avail. I'm thinking I may need to flash a vendor image...the only problem is that I can't find one for the life of me, and I have no idea how to extract it from a ROM...I've tried EVERYTHING. Can anyone help? Thank you!
In another thread bout this it is choppy. It's nothing you can really do with it. I don't understand why we can't use the regular Android release. I assume you are using the efrons build?. But also they are saying that the Efron build runs smoother on devices that was released with Android 10. Like the 7t. It's in OnePlus 7 pro xda forum you can search it.
Related
hi everyone, I am new to this forum.
i've been interested in rooting / mods for my old Samsung s9 to give it a new life.
I did so by rooting it using the TWRP app in combination with the Magisk V23.0
now what happened was that i was downloading some random apps yesterday and for some reason the phone went on bootloop...
i accidentally deleted the system without making a backup lol... a little stupid of me...
now it keeps telling me that i've no OS on my phone. i was thinking that i could easily find the ''un-edited'' or simple version of my original OS. but i've looked through many sites without succes.. either looks 2 good to be true or just fake...
is there anyone who can advise me on what to do? i just want my phone to work with any OS right now... but which one is the cleanest or best to use? i do prefer a newer os like 10
thanks in advance!
If you still have access to recovery mode, your best choice would probably be installing LineageOS. It's the most lightweight ROM and many ROMs are based on Lineage. From what i can see, your phone is no longer officially supported.
I found this one based on Lineage 18.1 (Android 11). Before installing, take a look at the bugs, working, and installing sections.
And don't forget to install the Google Apps after installing the system and before rebooting.
that looks crispy. i appreciate your quick & good advise. can you tell me wether i can still run Magisk on it?
Yes, you can still flash Magisk or any type of root with both the OS and the GApps.
what i'm consider about is, wether a region code CRC matters?
had this device all of a week (barely), seemed to work great out of the box, have left it stock intentionally.
take the April security update, reboot.
Have completely lost pinch zoom / multitouch and it seems as though the screen's settings, software or combination are completely misaligned / out of whack regarding touch input.
It's the kind of behavior you get when you have a droplet on your screen and the phone screen is getting erratic input... like it's compromised or fragmented somehow.... I've increased sensitivity which made the phone more usable, but I can barely use the bottom row of my home screeen. If I switch to left hand and try my L thumb, it better detects the input (if I aim WAY LOW). Almost like the calibration for the screen touch has been completely FUBAR.
Hoping custom software and lack of OTA updates fixes this? Has this community seen this issue and are custom ROMs a way out of the mess, or is this a hardware issue that absolutely requires the device to be returned and replaced? Seems odd the change happened with no physical change to the phone.
Same issue here when updating. Complete factory reset fixed mine
@beflythis hey did you figure the fix out? I have a similar issue. Factory reset didn't help me
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
anshuuu03 said:
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
Click to expand...
Click to collapse
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
This is definetly an issue with what seems to be the software, not sure exactly what is wrong though (I dont know too much about kernel driver code),
anshuuu03 said:
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Click to expand...
Click to collapse
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Do let me know if it works. It would be a life saver
fbievan said:
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
Click to expand...
Click to collapse
I think downgrading to Android 10 has worked for almost everyone facing this problem
vovapolischuk said:
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
Click to expand...
Click to collapse
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Now that i know that im now going crazy, and atleast one other person has very very similar story to mine, there needs to be a proper fix. I do know that android 10 and android 11 do have different touchscreen drivers. Downgrading then upgrading back wont work, atleast to my knowledge. I've done plenty of looking, and just don't know whats wrong. If any kernel devs that know their way around touchscreen drivers, and pixel 4as. Would be a life saver. But I have little idea of whats actaully going wrong.
anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Yep, downgrading again to Android 10 alllows multittouch to work
anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
fbievan said:
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
Click to expand...
Click to collapse
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
fbievan said:
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
Click to expand...
Click to collapse
Make sure to test, test, and test
anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
Can I ask: has that worked for you?
fbievan said:
Can I ask: has that worked for you?
Click to expand...
Click to collapse
I think I will try and do the 10 > 11 > 12 > 13 in a few days. I am stuck with some work and cannot afford to keep resetting my phone atm. But I will update here whatever is the update on that
Hi. for 2 days I have been googling and looking on this forum on which rom is best for nexus 2012, but I can't find anything at all. most posts are for 2013 version or outdated with dead links.
I was able to get lineage 14.1 on it, but it was missing google play, after following some guide here and installing Gapps, it then stopped booting. it got stuck on the google logo and that's it. lineage 14.1 itself worked fine, installation of gapps succeeded, but simply won't boot. tried several times. always gets stuck on google logo (waited over 15 minutes).
before that i had some kali version on it, but out of the blue it stopped working and wouldn't boot anymore, that's where i deciced to try lineage. i dont want kali on it anymore as it was sluggish to start with.
so I thought I'll just put original rom on it and was looking for original 2012 rom download, but it seems like it comes in pieces like system.img boot.img ..etc and I don't want to overwrite my bootloader or lock the device again or cause other issues. I just want a working rom that can be sideloaded.
can someone please point out which rom is actually working with nexus 7 2012 and can be flashed using sideload or twrp loader.
I already have everything working, such as twrp, fastboot ..etc. I can easily sideload any working zip or img, but I simply can't find a working one.
I find only dead links on this forum and elsewhere, such as this one "xxxxxx" which is suppose to be for some nightly version. and some dead gapps links that point to dead domains or link just doesn't even exist.
please dont start suggesting to buy new tablet. i'm poor and i have no money and i only need this tablet to use with my smart plugs and camera. i'm not going to buy new tablet just for that. i just want to keep it on charger 24/7 so i can monitor my plugs and camera. that's all.
but for that i need working android rom and google play store so i can download and update apps.
I don't have any backups nor important data on it, however i want to keep it unlocked and keep the twrp.
any help would be appreciated. thanks.
Mod Edit: Link removed
so your question is about gapps?
aIecxs said:
so your question is about gapps?
Click to expand...
Click to collapse
uhh, no..
I quote:
mordaxify said:
can someone please point out which rom is actually working with nexus 7 2012 and can be flashed using sideload or twrp loader.
Click to expand...
Click to collapse
lineage 14.1 itself worked fine, or not?
aIecxs said:
lineage 14.1 itself worked fine, or not?
Click to expand...
Click to collapse
it was bit sluggish and got stuck couple times during boot, but it worked.
I think better question to ask is: does any of the ROMs comes with gapps?
It was like 5-6 years ago so i don't remember much, but i installed some version of kali on it and it had everything included (play store and other stuff). however as i mentioned before, for some reason it got really, really sluggish and at some point it just stopped booting completely.
so your question is about gapps. ROMs always should provided without google apps for licence violation.
use older installer. check recovery.log
My attempt to install the OOS Cam bricked my phone.... so my question is Why did my phone got bricked exactly? I want to know what I did wrong since I really want to use the OOS Camera.So I was trying to get the original stock camera app to work on my device because the other ones looks horrible. I mean I have a kind of flagship device and the photo quality looks like my old cheap Huawei phone.
First I tried with an 3.x.x version of the app installed as an normal application. It works but the quality is still bad.
This is where I got that apk: https://forum.xda-developers.com/t/apk-oneplus-camera-for-any-a11-custom-rom.4350205/
On Reddit there is a post that said if you replace the Camera.apk on /system/app/Camera with the OnePlus Camera it should work.
The result? It worked and the quality seems better!....but some functions of the app like video or changing the size of the picture crash the app. Now the phone got really hot for some reason. No idea why but anyways I decided to go "creative" and I analyzed the official OxygenOS Rom(This is where I got the OOS Camera apk) to see what files where related to the OnePlus Camera app and then I pushed it through ADB to the respective directories of my phone.
These are the directories that I added with their specific files:/system/priv-app/OnePlusCameraService/
/system/system_ext/priv-app/OnePlusCamera/
/system/system-ext/priv-app/OnePlusGallery/
Then I rebooted the phone expecting to see the OnePlus Camera working in all it's glory!...The phone got stuck in the boot logo.
The phone stays on the boot logo for some seconds, then reboots again but this time in Recovery mode and says this:
Can't load Android System. Your data may be corrupt. If you continue to get this message, you might need to perform a factory data reset and erase all user data store in this device.
Click to expand...
Click to collapse
I did the factory data reset but it did not work.
Now this might seem relatively easy to fix by using adb right? Well it is the worst moment to have the usb port damaged so until I fix that I have this beautiful OnePlus Paperweight.
The last detail is I actually deleted a folder which contained the .xml config files of the OOS Cam I installed on the second try because I thought it might cause some issues with the last try. Those files were on /system/data/
The phone have the bootloader open because I use a custom ROM and this one is called "/e/" which is based on Lineage OS. I used the wireless ADB function since my usb port is damaged, it jsut works as a charge port.
Again my main motive to this post is to understand "what did I do wrong?". I don't get why Android thinks the data is corrupted. The files are the official ones and as far I know I didn't deleted any important files. I even want to try with a more modern version of the app since I use the 6.4.45. This is the one that came on my phone the moment I opened the box. I want to see if the quality of the pictures got better with a newer one.
If you read this massive dump of text...thank you!
Hi everyone,
This is driving me mad. I've been trying to install a bunch of different ROMS on my Samsung Galaxy A10 and while it seemingly installs just fine, when I press "reboot system" it gets into a perpetular loop. Am I doing something wrong here?
Bliss OS Rom v14 w/ Android 11 for Samsung A10 Arm64 ( Stable Unofficial ) released 2021
IMO you should contact developers of Bliss OS to get your issue fixed.
Recovering Spaghetti said:
Hi everyone,
This is driving me mad. I've been trying to install a bunch of different ROMS on my Samsung Galaxy A10 and while it seemingly installs just fine, when I press "reboot system" it gets into a perpetular loop. Am I doing something wrong here?
Click to expand...
Click to collapse
I don't have experience with Samsung phones in particular, but with Moto phones I've used the online recovery tool to restore the phone back to stock and start over. Not sure there is anything similar with Samsung? Good luck!
jwoegerbauer said:
Bliss OS Rom v14 w/ Android 11 for Samsung A10 Arm64 ( Stable Unofficial ) released 2021View attachment 5799499
IMO you should contact developers of Bliss OS to get your issue fixed.
Click to expand...
Click to collapse
Hi,
The thing is I also tried DotOS & OctaviOS & the issue perseveres
vdun1188 said:
I don't have experience with Samsung phones in particular, but with Moto phones I've used the online recovery tool to restore the phone back to stock and start over. Not sure there is anything similar with Samsung? Good luck!
Click to expand...
Click to collapse
Hi, I believe there is, but the thing is that this is like my third ROM on this phone (Decided to install a new one after my bluetooth headphones refused to connect with my phone while being able to connect just fine to literally everything else) & this is the first time I'm having issues like that. Before, when I managed to install the ROM then it was smooth sailing since hence why I'm asking for help. I've spent a few hours trying different ROMS already.
Recovering Spaghetti said:
Hi, I believe there is, but the thing is that this is like my third ROM on this phone (Decided to install a new one after my bluetooth headphones refused to connect with my phone while being able to connect just fine to literally everything else) & this is the first time I'm having issues like that. Before, when I managed to install the ROM then it was smooth sailing since hence why I'm asking for help. I've spent a few hours trying different ROMS already.
Click to expand...
Click to collapse
Since it has worked fine up to now I'd like to first exhaust all the concievable solutions before going for the nuclear option of stock firmware.
Recovering Spaghetti said:
Since it has worked fine up to now I'd like to first exhaust all the concievable solutions before going for the nuclear option of stock firmware.
Click to expand...
Click to collapse
Understood. For some reason that is beyond my comprehension, it seems it is sometimes suggested to install stock and then a different custom ROM. Again, I don't know what it is actually supposed to do, as I've stayed with LineageOS to keep it simple. I'm not saying to stay with stock, just use it to get phone back to default, then start from there.
nuclear option..stock - hahaha )
Gawd Damit, I tried LineageOS too & a bunch of other stuff & it's always the same problem. I'm all out of ideas now.
Please help, Tried every ROM, same result, doesn't boot
Hi, I've got a Samsung Galaxy A10 SM-A105F and I tried installing all kinds of different roms on it and they install just fine but then when i go to boot to system I end up in this hell hole of perpetual booting and restarting. I've been at it...
forum.xda-developers.com