Hello everyone,
First of all, I can't thank the devs enough for the hard work they are doing for Sakura (R6P). I just have one confusion regarding the new Android 10 build of the Pixel experience. Am I the only one or anyone else also facing the mounting problem while trying to convert an app tp system app (a message showing 'system not in proc/mounts' or something like that). And if I try to do any modification to the build.prop or anything else, it stucks my device on boot-loop (well, I am no expert of course). Is this a problem or it's just something that is not possible on Android 10? An answer would be much more appreciated.
Thank you
Same problem
Hi,
I have the same problem with Android 10 in the Pixel Experience project. I just installed the Android 10 package using TWRP without any problem or notice but when trying to reboot after installation, the TWRP says "are you sure, No OS is installed" and if press yes the phone will stucks in bootloop.
Related
Hey there,I flashed boot-animation image (.img) file in /firmware partition through TWRP recovery by mistake, now my ZUK Z2 plus can't detect SIM or WI-FI access points(Also the mac address now indicates 02:00:00:00:00 which seems odd).What a, I suppose to do to save my device?
ps:this is my first time that I'm asking for help here on XDA given that I'm it's frequent visitor from last 5 years.This particular problem that I mentioned above is beyond my knowledge of android modifications.Help In Any Form Is Appreciated. HOPE i get my device in fully working condition again otherwise I will have to stop my journey of tinkering every android device that I ever owned which will be really sad for me since I cant keep ruining my devices like that.(Happened with my previous YU YUPHORIA )
Sunnyda said:
Hey there,I flashed boot-animation image (.img) file in /firmware partition through TWRP recovery by mistake, now my ZUK Z2 plus can't detect SIM or WI-FI access points(Also the mac address now indicates 02:00:00:00:00 which seems odd).What a, I suppose to do to save my device?
ps:this is my first time that I'm asking for help here on XDA given that I'm it's frequent visitor from last 5 years.This particular problem that I mentioned above is beyond my knowledge of android modifications.Help In Any Form Is Appreciated. HOPE i get my device in fully working condition again otherwise I will have to stop my journey of tinkering every android device that I ever owned which will be really sad for me since I cant keep ruining my devices like that.(Happened with my previous YU YUPHORIA )
Click to expand...
Click to collapse
Flash stock through mi flash tools it will solve your problem.
Hello everyone!
I have a problem with my Samsung s4 mini LTE version, i was installing LineageOS 14.1 on it, but when i flash GApps 7.1 Aroma, the phone boots and a popup pops up and says "Setup wizard has stopped"! I have read on other threads that you need to pull down the notification panel to get into the settings, but the problem is, IT'S IMPOSSIBLE TO PULL DOWN THE NOTFICATION PANEL!
I have tried to flash it all over again and again and again, but it dosen't help :crying:
If someone have a solution for this, I would be so happy to hear what is is
PS. Sorry for my bad English it isn't my primary language...
Olivgamer05 said:
Hello everyone! I have a problem with my Samsung s4 mini LTE version, i was installing LineageOS 14.1 on it, but when i flash GApps 7.1 Aroma, the phone boots and a popup pops up and says "Setup wizard has stopped"!...
Click to expand...
Click to collapse
Your best bet is to post this question within the following Official LineageOS thread for your device.
https://forum.xda-developers.com/showthread.php?t=3471761
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
This may help or may not, but it could be one possible cause:
Did you boot lineageOS once before flashing gapps?
AFAIR for gapps to work properly, it needs to be flashed right after flashing a custom rom, without starting the custom rom in-between.
Or put another way, when the phone starts up normally for the first time, gapps already needs to be installed. otherwise it can't run its setup wizard correctly.
also, a common problem for crashes like this is missing permissions for system apps. And i think the setup wizard not running correctly on first boot can cause some. (note that lineageOS also has a setup wizard. not sure how they're chained today)
note that i'm intentionally fuzzy on the details. It is what I vaguely remember, and I'm just writing this as some help may be better than none.
I had this same problem but with a different device. Followed the directions to a T, but still no go. Also tried the 'pull down notifications' supposed 'fix', while I guess that worked for some, didn't work for me (and you) either.
Here's what did work: And yes, it goes against the directions (but I tried it anyway), **don't** install gapps before booting the new rom, install after booting and doing as minimal set up as you can.
I'm not certain why this worked for me, but it seems to be because of the 2 diff 'set up' wizards, and the way they communicate to ea other and other apps. If you look in the bug logs (for both Los and Gapps), this problem goes way back, with numerous fix attempts.
It worked for me to install them separately, I suppose it might for you also. Good Luck.
Olivgamer05 said:
Hello everyone!
I have a problem with my Samsung s4 mini LTE version, i was installing LineageOS 14.1 on it, but when i flash GApps 7.1 Aroma, the phone boots and a popup pops up and says "Setup wizard has stopped"! I have read on other threads that you need to pull down the notification panel to get into the settings, but the problem is, IT'S IMPOSSIBLE TO PULL DOWN THE NOTFICATION PANEL!
I have tried to flash it all over again and again and again, but it dosen't help :crying:
If someone have a solution for this, I would be so happy to hear what is is
PS. Sorry for my bad English it isn't my primary language...
Click to expand...
Click to collapse
Aroma is to big you can only use micro or nano or pico gapps on S4 Mini
Hi guys n Gals How you all doing? Staying safe i hope!! Im posting this incase it is of any use to anyone who happens to stumble upon an old tablet as i did, But is absolutely bamboozled with what to do next.
Well then i had been looking for help on this issue with regard to Kindle Jem and done my fair share of reading before signing up here.
I am right out of the wrapper and wet behind the ears with Kindles and the like(1st time rooting anything at all) however i managed to install TWRP 2.8.6.0 on su rooted kindle using the bin4ry method.
I followed step by step a tutorial on Youtube named " KindleFireHD89 to pure android"
1. At first i was getting read/load errors:
when attempting to flash cm10.1 cm11/12 through adb sideload i was getting the error message "unable to read cm 11/12" or "unable to load cm11/12" each time i try to flash the rom.
So I done some research on XDA and found a thread to do with the \LARGEADDRESS issue , so downloaded the program to use more than 2GB ram for the flash process, all to no avail. (THIS WAS ABSOLUTELY NO USE AT ALL)
I soon figured i was copying and pasting the commands for flash/fastboot wrong ( i was forgetting to add .img to the name of the image files i was pasting into the command prompt to flash lol)
2. I done a bit of reading around and saw that most , if not all the files were severely obsolete (like the Jem) so i searched around and first upgraded to TWRP 3.0.0.2 from 2.8.6.0 which i feel made a big difference if not just for a smoother gui alone.
3. As my determination and curiosity got the better of me i began replacing the roms also , flashing newer ones each time in this order:
cm 10.1 (success)
cm 11(success)
cm 12.1 (success)
And finally onto Lineage OS 14.1 along with GApps 7.1 Pico where i remain , however i am unable to fix the bluetooth issue as i dont know the commands/ paths or method to alter the LTE file replacement. (any help with this would be great guys or girls (i know Ladye made a fix i think) i just dont know how to go about editing these files.
I got into the menu brand new , though weirdly it wasnt by the volume up button, it was by turning on/off about 5 times and then holding the POWER button in and finally the TWRP Recovery screen would popup.
### edited### i know this is an old kiindle hence why there is no replies .....
####23rd May 2020 EDITED YET AGAIN ##### So i wondered whether there was a recent newish kinda Rom for the JEM after managing to flash (with great difficulty and beginners syndrome) custom rom in TWRP 3.0.0.2.
As i said earlier this was a kindle that was found and when i got it in out the rain and dried off with the hairdrier treatment , was amazed it still worked. So i figured it was a tough mofo and deserved to live outwith the bin since he made it this far.
Anyway when i checked it out the firehd 8.9 was blacklisted ((((Which i am assuming will mean i at least dont need to worry about disabling OTA updates??????))))
So bottom line and after all the fuss above trying to root etc i got 14.1 lineage os without the bluetooth but ill figure that out soon.
For anyone out there this post may help if you can be bothered to read through it haha.
###Last but not least I would like to thank all the guys n gals who make these mods possible and xda themselves for not binning these old posts for noobs like myself . Respect people . thanks again man ###
Have recently started to have issues with my S20+ super fast charging. Thought this could be the charger so tried a new one and the issue still exists. Seems to super fast charge as soon as the phone has rebooted and then stops and goes back to the "Check USB connection" message.
Also appears that the supplied USB C head phones no longer work connected to the phone. These work perfectly fine connected to my computer so i guess its unlikely an issue with the head phones.
Thinking back this issue appears to have started around the time the latest android was rolled out in the 2nd half of December. Has anyone else experienced the same issues and if so is there a fix?
Thank You
Android 11 One UI 3.0 is full of bugs on Galaxy devices. I won't install it unless it's improved. If you can factory reset to the original OS that may be your best option.
varcor said:
Android 11 One UI 3.0 is full of bugs on Galaxy devices. I won't install it unless it's improved. If you can factory reset to the original OS that may be your best option.
Click to expand...
Click to collapse
Thanks for your thoughts, i was coming to the conclusion this may be it. I did do a factory restore however this is the same OS (Android 11) - Would the only way to go back to Android 10 be downloading the ROM and installing it manually?
robonz said:
Thanks for your thoughts, i was coming to the conclusion this may be it. I did do a factory restore however this is the same OS (Android 11) - Would the only way to go back to Android 10 be downloading the ROM and installing it manually?
Click to expand...
Click to collapse
Here's a step by step tutorial to guide you through the process.
Downgrade Android 11 Back To Android 10 on Samsung Galaxy S20/S20+
In this comprehensive tutorial, we will show you the steps to downgrade the Samsung Galaxy S20/S20+ devices from Android 11 to Android 10.
www.getdroidtips.com
Hi there. I'm trying a buncha roms to see which ones will run a particular app the dev is still polishing up. (It's called SDR++ and is a full-featured SDR receiver app for android)
Anyhow, over the course of flashing/reflashing and running RESTOCK on it - which is a fabulous set of utils for wannabe peeps like me - I have run into a strange error.
My tab is an N7 2013 16gb "flo", and lately I've noticed that a bunch of roms error out from TWRP with error #7, meaning TWRP somehow thinks the tablet isn't a "flo" - but it is. And yes, I triple check the roms I download to make sure they're NOT for a "deb."
How do I fix this or get around it? And be kind please, I really know zero about this stuff, but I *can* read and type.
Thanks for your expertise.
cranky_dan
Which recovery are you using ? There is one which renames the device to "flox". This recovery is required for flashing official LOS 18.1
MikiGry said:
Which recovery are you using ? There is one which renames the device to "flox". This recovery is required for flashing official LOS 18.1
Click to expand...
Click to collapse
Which recovery? TWRP pops up when I boot into recovery.
However, when I'm in fastboot, the device reports that it's "flo".
cranky