#include <std_disclaimer.h>
/*
* Your warranty is void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
Download: Link
- Works
Almost everything
- Doesn't work
FOD - fixed
You tell me
Source: https://github.com/Galaxya50
CLEAN FLASH :
Download the latest build and GApps
Reboot to recovery (has to be a custom recovery. TWRP, OrageFox, etc.)
Make a backup of ur data (Not Necessary)
Wipe Cache, Dalvik, System, Data (wiping internal storage is not necesary)
Flash the latest build
Flash Gapps
Reboot
DIRTY FLASH (may cause bugs. not recommended):
Download the latest build
Reboot to recovery
Flash the latest build
Flash Gapps
Wipe Cache
Reboot
Builder: Me
mistakes???
Chinito_H18 said:
mistakes???
Click to expand...
Click to collapse
wdym?
Suggestion: Please post more info such as "How To Install". Having a README or instructions in place helps alot.
Trying to flash Gapps and I get an error 20 code. The log says this "Installation failure: This Gapps package can only be installed on a 11.0.x ROM". I have attached the version of Gapps that I downloaded. Which one should I get that would actually work?
EDIT: After trying another version install for Android 12 I still get the same error. The log now says I need 12 (SDK 32). Tried to Google this but can't find where to get this. Any ideas?
Waz999 said:
Trying to flash Gapps and I get an error 20 code. The log says this "Installation failure: This Gapps package can only be installed on a 11.0.x ROM". I have attached the version of Gapps that I downloaded. Which one should I get that would actually work?
EDIT: After trying another version install for Android 12 I still get the same error. The log now says I need 12 (SDK 32). Tried to Google this but can't find where to get this. Any ideas?
Click to expand...
Click to collapse
Use this gapps:
https://sourceforge.net/projects/flamegapps/files/arm64/android-12.1/2022-09-20/FlameGApps-12.1-basic-arm64-20220920.zip/
ducanhmai172 said:
Use this gapps:
https://sourceforge.net/projects/flamegapps/files/arm64/android-12.1/2022-09-20/FlameGApps-12.1-basic-arm64-20220920.zip/
Click to expand...
Click to collapse
That worked. THANK YOU!
ducanhmai172 said:
Use this gapps:
https://sourceforge.net/projects/flamegapps/files/arm64/android-12.1/2022-09-20/FlameGApps-12.1-basic-arm64-20220920.zip/
Click to expand...
Click to collapse
Edit: No, it didn't. It seemed to install sucessfully. Now I'm just stuck on the Lineage boot animation, even after restarting
Waz999 said:
Edit: No, it didn't. It seemed to install sucessfully. Now I'm just stuck on the Lineage boot animation, even after restarting
Click to expand...
Click to collapse
huh, try this then:
NikGapps - Browse /Releases/NikGapps-SL/08-Sep-2022 at SourceForge.net
A Custom Google Apps Package that Suits Everyone Needs!
sourceforge.net
Waz999 said:
Edit: No, it didn't. It seemed to install sucessfully. Now I'm just stuck on the Lineage boot animation, even after restarting
Click to expand...
Click to collapse
yeah, for some reason flamegapps didnt work for me either, dunno why. use what ducanhmai172 sent
ducanhmai172 said:
huh, try this then:
NikGapps - Browse /Releases/NikGapps-SL/08-Sep-2022 at SourceForge.net
A Custom Google Apps Package that Suits Everyone Needs!
sourceforge.net
Click to expand...
Click to collapse
I had to factory reset as I couldn't get out of that damn boot animation loop. But once I did and re-installed the ROM, this version worked. Thank you!
Just flashed this, and for some reason the fingerprints seem to have stopped working? When I try to register one, I get about 3/4th the way through and then get an "Enrollment was not completed" error:
Any ideas on how to fix this?
Romner_set said:
Just flashed this, and for some reason the fingerprints seem to have stopped working? When I try to register one, I get about 3/4th the way through and then get an "Enrollment was not completed" error:View attachment 5720629
Any ideas on how to fix this?
Click to expand...
Click to collapse
Turn on dark mode, turn off auto brightness, increase maximum brightness, turn off super dark mode, you will be able to register your fingerprint, but it is also difficult to unlock with fingerprint if you do not meet the requirements. the above.( google translate)
adgjmwtpmjg said:
Turn on dark mode, turn off auto brightness, increase maximum brightness, turn off super dark mode, you will be able to register your fingerprint, but it is also difficult to unlock with fingerprint if you do not meet the requirements. the above.( google translate)
Click to expand...
Click to collapse
You're right, for some reason that fixes it. Thanks!
Romner_set said:
You're right, for some reason that fixes it. Thanks!
Click to expand...
Click to collapse
fixes it cuz the a50 fingerprint scanner isnt that grate and its optical so it uses light to see the fingerprint
Does it have the bug that having the BT connected and changing the Wi-Fi network both collapse and you have to restart the cell phone to be able to activate the Wi-Fi or BT?
Mcadall13 said:
Does it have the bug that having the BT connected and changing the Wi-Fi network both collapse and you have to restart the cell phone to be able to activate the Wi-Fi or BT?
Click to expand...
Click to collapse
i didnt encounter it personally, tho i dont use bt that much
Scorpionkm469 said:
i didnt encounter it personally, tho i dont use bt that much
Click to expand...
Click to collapse
If I send you log could you try to solve it?
Mcadall13 said:
If I send you log could you try to solve it?
Click to expand...
Click to collapse
send it in pastebin
Does hwc works?
Related
CyanogenMod 9 is a free, community built distribution of Android 4.0.4 (Ice Cream Sandwich) which greatly extends the capabilities of your phone.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is a preview build of CM9 for the Samsung Galaxy Player 4. It may cause all the things in the disclaimer to happen, or steal your girlfriend while you are busy flashing ROMs.
Note: Please backup your efs in case of something goes wrong (the zip should backup it but we're never too sure) To do so execute this command:
Code:
dd if=/dev/block/stl3 of=/sdcard/efs.rfs
Preview Install instructions:
1. Download cm-9-20130402-kernel-preflash.zip
md5: 4a900fcddbc3d81d121a7b9c9d4bb0a0
2. Download cm-9-20130408-UNOFFICIAL-ypg1.zip
3. Make all your backups.
4. Remove external sdcard (will be resolved later)
5. Make sure your efs is intact (not blank).
6. Boot into recovery, make more backups.
7. Flash cm-9-20130402-kernel-preflash.zip (temporary workaround for first-time install)
8. Flash cm-9-20130408-UNOFFICIAL-ypg1.zip
Installation Notes:
When you install for the first time, there is a conversion to the new MTD partition layout. The installer will flash the new kernel and reboot. It is possible for this process to hang up on the samsung logo (still working that part out). It is normal to see the Samsung logo appear 3 seperate times during this reboot phase. **Please wait at least a minute before assuming you are stuck.** If this happens, you should extract the boot.img from the installer zip and flash it with heimdall (heimdall flash --kernel boot.img, or other appropriate GUI methods). It should boot back into recovery and continue the installation. Once the install finishes, it should reboot once more back into recovery, which gives you the opportunity to flash your gapps.
**Google Apps are not included in these ROMs. You'll need to install those yourself if you want them. Recommended and highly suggested are the 4.0.4 gapps from goo.im.
Known Issues:
Back Camera: Still pictures work and will be clear although the preview window doesn't focus correctly. Video recording is working?
Front Camera: Still pictures and video works, although it's rotated 90 degrees.
Bluetooth (Turns on, but devices are not visible) Fixed 0405
External sdcard symlink (can still be accessed through /mnt/emmc)
Sources
Device tree: https://github.com/bbelos/android_device_samsung_ypg1
Kernel source: https://github.com/bbelos/android_kernel_samsung_palladio
Previous Builds:
cm-9-20130402-kernel-preflash.zip
md5: 4a900fcddbc3d81d121a7b9c9d4bb0a0
cm-9-20130402-UNOFFICIAL-ypg1.zip
md5: 62caad1c4ca1198a0a655e28ccc07a13
Reserved
Here's the gapps package if you want them:
Gapps Package Download
Also guys when you will enter into recovery using the three fingers method, it will do the same as like when you installed it the first time. (It will reboot 3 TIMES so don't panic if you think of it as a bootloop.)
Forgot that one too, if you have an external SD card inside your device, it's recommended that you remove it prior to the install. (if not well CWM will give you an infinite bootloop of installation aborted. The only way I've seen to fix it is to format your sdcard but I didn't want to go all through this soo...)
You will need a FULL EFS folder to install this rom as the installation script will check it. If you don't have it, you will have CWM bootloops. YOU'VE BEEN ADVISED!!
bbelos said:
CyanogenMod 9 is a free, community built distribution of Android 4.0.4 (Ice Cream Sandwich) which greatly extends the capabilities of your phone.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is a preview build of CM9 for the Samsung Galaxy Player 4. It may cause all the things in the disclaimer to happen, or steal your girlfriend while you are busy flashing ROMs.
Note: Please backup your efs in case of something goes wrong (the zip should backup it but we're never too sure) To do so execute this command:
Code:
dd if=/dev/block/stl3 of=/sdcard/efs.rfs
Preview Install instructions:
1. Download cm-9-20130330-UNOFFICIAL-ypg1.zip
md5: 17c62877c6de776c692cdb634aa730d2
2. Boot into recovery, make your backups and install.
Installation Notes:
When you install for the first time, there is a conversion to the new MTD partition layout. The installer will flash the new kernel and reboot. It is possible for this process to hang up on the samsung logo (still working that part out). If this happens, you should extract the boot.img from the installer zip and flash it with heimdall (heimdall flash --kernel boot.img, or other appropriate GUI methods). It should boot back into recovery and continue the installation. Once the install finishes, it should reboot once more back into recovery, which gives you the opportunity to flash your gapps.
**Google Apps are not included in these ROMs. You'll need to install those yourself if you want them. Recommended and highly suggested are the 4.0.4 gapps from goo.im.
Known Issues:
Camera
More to be listed later
Sources
Device tree: https://github.com/bbelos/android_device_samsung_ypg1
Kernel source: https://github.com/bbelos/android_kernel_samsung_palladio
Click to expand...
Click to collapse
THANK YOU GUYS!!! So basically, go to CWM, then back up first.. Then install right? That's it... ?
the playa! said:
THANK YOU GUYS!!! So basically, go to CWM, then back up first.. Then install right? That's it... ?
Click to expand...
Click to collapse
Yeah that's basically it.
zaclimon said:
Yeah that's basically it.
Click to expand...
Click to collapse
OK then.. Right now my player's being backed up.
the playa! said:
THANK YOU GUYS!!! So basically, go to CWM, then back up first.. Then install right? That's it... ?
Click to expand...
Click to collapse
i thought that if you tried to backup in the current CWM, it wouldnt work
goldflame09 said:
i thought that if you tried to backup in the current CWM, it wouldnt work
Click to expand...
Click to collapse
Its backing up just fine... Its taking quite a while though.
the playa! said:
Its backing up just fine... Its taking quite a while though.
Click to expand...
Click to collapse
well thats because you are on GB with a GB kernel. i dont think it works with the current cm9 kernel that most of us have
DAMMIT! Idk what happened.. It was flashing and then the screen went blank all the sudden and now its stuck on a solid Samsung logo! D:
Edit: I saw your post where it says to flash the boot.img but it said flash failed
the playa! said:
DAMMIT! Idk what happened.. It was flashing and then the screen went blank all the sudden and now its stuck on a solid Samsung logo! D:
Click to expand...
Click to collapse
Forgot that one. It may be possible that you get stuck at the Samsung boot logo. Try either bbelos solution or flash back to stock and retry.
Sent from my Nexus 7 using Tapatalk HD
zaclimon said:
Forgot that one. It may be possible that you get stuck at the Samsung boot logo. Try either bbelos solution or flash back to stock and retry.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I flashed back to stock and now I'm flashing TerraSilent.
the playa! said:
DAMMIT! Idk what happened.. It was flashing and then the screen went blank all the sudden and now its stuck on a solid Samsung logo! D:
Edit: I saw your post where it says to flash the boot.img but it said flash failed
Click to expand...
Click to collapse
two reasons why flash failed:
1. dont have the correct drivers
2. you need to be in download mode.
Well, don't try to do a dirty flash... It won't work. Neither flashing when you are already on mtd. Anyway, I'll wait till monday to get my backup on my other computer and test it out.
So happy to see more progress on CM9 for the 4.0.
I'm going to try this out, but I'll eventually go back to Gingerbread since I want to have a working camera. I have everything backed up, including EFS. So to go back I could just flash my GB backup over CM9 and it should work, right? Just want to make sure before I jump in.
Thanks for the hard work!
zamuz27 said:
So happy to see more progress on CM9 for the 4.0.
I'm going to try this out, but I'll eventually go back to Gingerbread since I want to have a working camera. I have everything backed up, including EFS. So to go back I could just flash my GB backup over CM9 and it should work, right? Just want to make sure before I jump in.
Thanks for the hard work!
Click to expand...
Click to collapse
Nope, you would need to go back to GB then restore your backup.
zamuz27 said:
So happy to see more progress on CM9 for the 4.0.
I'm going to try this out, but I'll eventually go back to Gingerbread since I want to have a working camera. I have everything backed up, including EFS. So to go back I could just flash my GB backup over CM9 and it should work, right? Just want to make sure before I jump in.
Thanks for the hard work!
Click to expand...
Click to collapse
No you will have to restore stock first then fix your efs, then i think you can reflash cwm and restore your backup.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
It keeps on going on and on... It keeps on rebooting... What have I done this time? I followed the instructions...
It's here, huray!
Out of curiosity, is there anything fixed in the rom from older releases, or is it mainly the cwm fix? I notice the only bug listed is camera - that would be nice, lol!
Sent from my YP-G1 running R.E.D.D
the playa! said:
It keeps on going on and on... It keeps on rebooting... What have I done this time? I followed the instructions...
Click to expand...
Click to collapse
Do you see a cwm flashing image of just the Samsung logo rebooting?
Hmm I didn't tried this rom myself so I don't know if it's working or not. Normally bbelos tries all the builds prior to upload it. Has anyone got it working?
Sent from my Nexus 7 using Tapatalk HD
SLIMSYSTEM V1.0
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Things You Need To Know
This is a test build. Sony has promised a Lollipop soon so I am not going to bother spending to much time on a firmware
that is going to be updated. you need to flash gapps or the device wont boot. Gapps is seperate for update purposes only. If you want to test this on a different variant please dont use the recommended method, use the Alternative Method and make a nandroid backup
HOW TO INSTALL
RECOMMENDED METHOD
1. Root
2. Install Recovery
3. Boot Into Recovery
4. Wipe Date, Cache, Dalvik
5. Flash Z3 Aroma Base
6. Flash GAPPS
7. Flash Z3 Aroma(AROMA MOD)
8. Reboot
ALTERNATIVE METHOD
Only the Latest 23.0.1.A.5.77 Firmware Has Been Tested at the moment but may work on other firmware.
Only D6603 has been tested but may work on other variants
1. Root
2. Install Recovery
3. Boot Into Recovery
4. Wipe Date, Cache, Dalvik
5. Flash Z3 Aroma(AROMA MOD)
6. Reboot
FEATURES
Zipalighn
Deodexed
Png Optimized
Aroma Install
Bloat Removal
More Personal
Bootanimation Selection
FUTER RELEASE
More Customization Options(More and More gets added as we go along)
Support Other Models(Not Confirmed but may be working)
Cleaner Base(After Lollipop is Released)
Proper GAPPS(After Lollipop is Released)
DOWNLOADS
Z3 Aroma Base
Z3 Gapps
Z3 Aroma
Reserved
Reserved
Good evening. I can flash this rom with Locked bootloader?
Thanks.
makisgk said:
Good evening. I can flash this rom with Locked bootloader?
Thanks.
Click to expand...
Click to collapse
yes he said locked and unlocked bro:cyclops:
@slipsystem
Nice Rom, but I cant get xposed modules to work due to rooting problems,
Flashed superuser as well..
XDA00000 said:
@slipsystem
Nice Rom, but I cant get xposed modules to work due to rooting problems,
Flashed superuser as well..
Click to expand...
Click to collapse
Thanks for this. I checked it out and you are correct for some reason I missed that it's not prerooted. Solution is to flash su binary. I will post a link in the first post later today.
slipsystem said:
Thanks for this. I checked it out and you are correct for some reason I missed that it's not prerooted. Solution is to flash su binary. I will post a link in the first post later today.
Click to expand...
Click to collapse
Hello
I flashed Super SU zip..still root problems with xposed modules.
Hello,
can you please post a list of what you've removed?
Nice Rom so far, smooth and a lot of bloatware removed.
As mentioned before there are some root issues.
Flashing supersu shows SuperSu working but still issues.
XDA00000 said:
Hello
I flashed Super SU zip..still root problems with xposed modules.
Click to expand...
Click to collapse
Cozmos23 said:
Nice Rom so far, smooth and a lot of bloatware removed.
As mentioned before there are some root issues.
Flashing supersu shows SuperSu working but still issues.
Click to expand...
Click to collapse
I have noticed it takes a few seconds to get root access from boot. I have noticed that the problem goes away when flashing a different kernel. also there is no need to re flash su binary if you flash a different kernel. strange it may be something to do with the kernel being stock. does anyone have this issue on locked bootloaders with stock rom?
sgiannouris said:
Hello,
can you please post a list of what you've removed?
Click to expand...
Click to collapse
as far as I can remember I removed
Stock Google Bloat
Hangouts
Books
Magazines
Chrome(replace with Sonys Browser from previous firmware)
ect
Sony Stuff
I think the only thing that was deleted was
Backup Restore
Update Checker
and Movie Maker
Stuff that was in /system/etc/product/applications
like Antivirus and Diagnostics
So nothing Important
the rest of the stuff you have the option to restore in the aroma installer
slipsystem said:
I have noticed it takes a few seconds to get root access from boot. I have noticed that the problem goes away when flashing a different kernel. also there is no need to re flash su binary if you flash a different kernel. strange it may be something to do with the kernel being stock. does anyone have this issue on locked bootloaders with stock rom?
Click to expand...
Click to collapse
I'm on locked bootloader...so can't flash a kernel.
XDA00000 said:
I'm on locked bootloader...so can't flash a kernel.
Click to expand...
Click to collapse
did you experience problems with root before on stock?
did you wipe data, cache and dalvik?
I will do some looking into root problem. what xposed modules are giving you errors? what are the errors?
slipsystem said:
did you experience problems with root before on stock?
did you wipe data, cache and dalvik?
I will do some looking into root problem. what xposed modules are giving you errors? what are the errors?
Click to expand...
Click to collapse
Yes I did wipe data etc.
Can't remember what the xposed modules errors was since I have moved back to stock rom.
@slipsystem
Is there a fix for this root problems mentioned.
On Stock I have no rooting problems with xposed modules.
Any caps please! ?
XDA00000 said:
@slipsystem
Is there a fix for this root problems mentioned.
On Stock I have no rooting problems with xposed modules.
Click to expand...
Click to collapse
Okay if will have a look into it. What xposed modules give you an error and what error are you getting? This will help me determine where the problem is.
slipsystem said:
Okay if will have a look into it. What xposed modules give you an error and what error are you getting? This will help me determine where the problem is.
Click to expand...
Click to collapse
As I said before I am on stock now..I am not going to reflash this Rom again just to see what the xposed error is!
The main xposed module that activates other module does not have proper root access
Just flashed this and its working good so far.
Anyone having root isues flash the kernel & superuser package from here:
http://forum.xda-developers.com/z3/development/root-stock-kernel-twrp-v01-test-28-09-t2889794
I have root access now :good:
dashrink said:
Just flashed this and its working good so far.
Anyone having root isues flash the kernel & superuser package from here:
http://forum.xda-developers.com/z3/development/root-stock-kernel-twrp-v01-test-28-09-t2889794
I have root access now :good:
Click to expand...
Click to collapse
its only for unlocked bootloaders!
After factory resetting/reinstalling [Resurrection_Remix][Android 6.0.1, r_52][Kenzo], the "Unfortunately Setting Has Stopped" has started appearing whenever I try to access the Privacy setting to change the password/pin/pattern option. I also noticed that the Fingerprint scanner is no longer in the Privacy setting.
Under TWRP I have also tried wiping Dalvik / ART Cache, Data, Internal Storage, and Cache when reinstalling any other Custom ROMs and Gaap. The other custom ROMS I've installed are causing the Setting->Privacy option to crash also. All the searches I've made doesn't seem to fix the issue, particularly the searches in the Redmi section. Any suggestion would be helpful, thanks.
phonester said:
After factory resetting/reinstalling [Resurrection_Remix][Android 6.0.1, r_52][Kenzo], the "Unfortunately Setting Has Stopped" has started appearing whenever I try to access the Privacy setting to change the password/pin/pattern option. I also noticed that the Fingerprint scanner is no longer in the Privacy setting.
Under TWRP I have also tried wiping Dalvik / ART Cache, Data, Internal Storage, and Cache when reinstalling any other Custom ROMs and Gaap. The other custom ROMS I've installed are causing the Setting->Privacy option to crash also. All the searches I've made doesn't seem to fix the issue, particularly the searches in the Redmi section. Any suggestion would be helpful, thanks.
Click to expand...
Click to collapse
Flash radio.zip fix.and dont forget to flash gapps after flashing roms.
Sent from my Redmi Note 3 using Tapatalk
khan_pegasus said:
Flash radio.zip fix.and dont forget to flash gapps after flashing roms.
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
It worked, thanks.
link to download radio.zip?
This situation happens when you switch to an OFFICIAL Rom from an UNOFFICIAL one like Mokee or RR from Siddhesh or Santosh. This is because these ROMs lock the bootloader and cause other problems too.
Radio.zip may not always fix the problem. If you are really stuck, there is a lengthy process that is guaranteed to work.
1. Flash one of the MiUI Fastboot ROM (global or chinese stable works fine) for RN3SD with Mi Flash tool. Use Flash All in the options at the bottom.
2. If you had an officially unlocked bootloader, use the Mi Unlocker tool to unlock your bootloader. Otherwise, you need to follow the unofficial unlock guide.
3. Flash official TWRP or a variant if you now what you are doing. Refer to this thread if you are not sure which TWRP will work.
3a. Download and copy this file to internal storage - LazyFlasher. I have verified this file to work with MiUI7 and MiUI8 global.
3b Reboot the phone in fastboot mode. On your PC, copy the TWRP img file to the adb directory and open command window there. Rename it to recovery.img. Use this command
Code:
fastboot flash recovery recovery.img
3c Boot into recovery (using ADB or Vol-pwr button shortcut). DO NOT BOOT into the phone before you do this. Flash the Lazyflasher zip with TWRP. You could probably flash this using fastboot too, I just never tried it.
Dhanajay made a guide video here. The video is a little outdated, and the updated instructions are in the description and comments.
You phone is now rooted and you have TWRP. Happy flashing.
This method will soon be outdated as a graphical UI for ADB is already in progress. Others have done it before, but this one shows real promise. Check here for details.
It has been a few months now since the RN3SD launch and the time has come when unofficial ROMs are no longer the best option around. Most Official ROMs, including the ones from RR and XOSP among others work great now and are incredbilby smooth and efficient. The war for the best kernel is now starting, and custom kernels will be responsible for the next round of reasons for bricked phones. Be VERY careful when you are flashing a ROM with a custom kernel. Be prepared to do some legwork if things go wrong.
Joswin said:
link to download radio.zip?
Click to expand...
Click to collapse
http://builder.balika011.me/official-cm13/cm-13.0-RADIOS.zip
I would also recommend anyone having this issue to read this post.
talkaboom said:
http://builder.balika011.me/official-cm13/cm-13.0-RADIOS.zip
I would also recommend anyone having this issue to read this post.
Click to expand...
Click to collapse
Link isn't working...
Can you mirror it?
Joswin said:
Link isn't working...
Can you mirror it?
Click to expand...
Click to collapse
Seems to be down. Normally works. Give it some time.
But if you are moving from an unofficial ROM, flashing radios alone is unlikely to work. Radio zip fix is for undetected SIM and IMIE errors. Check your IMIE number in About Phone. If you are showing an IMIE number instead of '0', flashing radio may be pointless.
Joswin said:
Link isn't working...
Can you mirror it?
Click to expand...
Click to collapse
New Link available.
https://mega.nz/#!9hlljJKD!QmjwPqMOH...gOqWkEJ0QasGE4
talkaboom said:
New Link available.
This link needs a decryption key not provided. Why even post this?
Click to expand...
Click to collapse
virtualgates said:
This link needs a decryption key not provided. Why even post this?
Click to expand...
Click to collapse
Link is from August 8th. That **** has mirrored a hundred times by now.
Also, the problem is now tackled in a different way. If you're facing a similar issue, ask in the rom thread you are trying to flash.
If you are facing this problem now, just flash the correct CM firmware.
P.S. On XDA, please do not question why someone posted a link or method that did not work for you. Do your research. No one is obligated to solve your problems.
Flashed radio. Zip. Worked for me.
Sent from my Redmi Note 3 using Tapatalk
Hello talkaboom!
the link is not working anymore. Any chance to upload it again please? Thanks a lot!
I have tried multiple ROMs, TWRP versions and builds, lastest firmware etc. Always hangs for a few seconds and then error 255. Nano flashes without issues but I want Aroma to get rid of stock apps and use Google Dialer etc
dustojnikhummer said:
I have tried multiple ROMs, TWRP versions and builds, lastest firmware etc. Always hangs for a few seconds and then error 255. Nano flashes without issues but I want Aroma to get rid of stock apps and use Google Dialer etc
Click to expand...
Click to collapse
Do you have sufficient space to flash Gapps Aroma in your system partition?
tnsmani said:
Do you have sufficient space to flash Gapps Aroma in your system partition?
Click to expand...
Click to collapse
4GB should be enough, right?
I'm trying to clean flash after a few months but encountered this again. I don't want to use Gapps nano.
Until I know, there is no a recovery for poco compatible with aroma
eLaDiio said:
Until I know, there is no a recovery for poco compatible with aroma
Click to expand...
Click to collapse
Wait really? I have never heard about this!
Oh wow. Is there a way to get around this? To be able to pick what I want to flash?
dustojnikhummer said:
Wait really? I have never heard about this!
Oh wow. Is there a way to get around this? To be able to pick what I want to flash?
Click to expand...
Click to collapse
Seriously? Dude, flash Pico or Nano and install the rest from Google play or APK Pure or something...
dustojnikhummer said:
Wait really? I have never heard about this!
Oh wow. Is there a way to get around this? To be able to pick what I want to flash?
Click to expand...
Click to collapse
Recovery doesn't support aroma gapps. Use this?
https://forum.xda-developers.com/poco-f1/themes/arm64-nikgapps-t3915866
Hi, I have been testing this on this device, and finally I was able to make AOSP 10 (GSI) run on our device.
Our device needs overlay to fix this issues. I will try to work into that
How to flash
WARNING: Your device must have unlocked bootloader
1. Download the latest TWRP Recovery: https://forum.xda-developers.com/mi...overy-unofficial-twrp-xiaomi-mi-note-t4015805
2. Download the latest AOSP 10 GSI (ab with gapps): https://github.com/phhusson/treble_experimentations/releases/
3. Download vbmeta.img: https://github.com/TadiT7/xiaomi_ce...9.3.1-release-keys/firmware-update/vbmeta.img
4. Disable vbmeta partition by flashing vbeta.img
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5. Flash TWRP
Code:
fastboot flash recovery <twrp_file_name.img>
6. Boot TWRP, make wipe (Format Data only!)
7. Flash the AOSP system.img file to System partition
NOTE: Trying to flash system.img using fastboot causes bootloop.
Aditionally here you can flash GAPPS and Magisk
- Flash GAPPS: https://opengapps.org/
- Flash Magisk: https://github.com/topjohnwu/Magisk/releases
10. Reboot system & enjoy!
Bugs
- Fingerprint
- Auto-brightness
- NFC
-Weird notification audio: can be fixed flashing this -> https://github.com/hmuny99/GsiSystemAudioFix/raw/master/fixaudiogsi.zip
-Video recording: can be fixed by flashing this -> https://forum.xda-developers.com/attachment.php?attachmentid=4374464&d=1514638461
-Flashing Magisk causes bootloop
- GCAM Camera starts to lag when the device has been on for a long time
Since we have a complete kernel sources/device tree, we can have this as a daily diver :good:
For now, I'd need the framework-res.apk from Stock rom, if someone could provide it, that would be really helpful
iFlashed said:
For now, I'd need the framework-res.apk from Stock rom, if someone could provide it, that would be really helpful
Click to expand...
Click to collapse
I saw this on another topic.
https://forum.xda-developers.com/showpost.php?p=81824837&postcount=50
Hi, what do you think, this flashing method will work with phhussons GSI too?
https://github.com/phhusson/treble_experimentations/releases
---------- Post added at 08:00 AM ---------- Previous post was at 07:43 AM ----------
If you need it still, I can copy it now, if you tell me the full path of this file.
technoboi1 said:
Hi, what do you think, this flashing method will work with phhussons GSI too?
https://github.com/phhusson/treble_experimentations/releases
---------- Post added at 08:00 AM ---------- Previous post was at 07:43 AM ----------
If you need it still, I can copy it now, if you tell me the full path of this file.
Click to expand...
Click to collapse
Same steps, Boots up, I recommend the system-quack-arm64-ab-gapps from your link, as it includes Gapps.
However, With that both I couldn't flash Magisk or I would get a bootloop. With LoS It would also not install gapps. But would boot just fine without Gapps or Magisk.
Currently Phhussons is working with Gapps. LOS Is not, atleast for me, but neither is working with Magisk 20.4.
thank for your reply, it has same bugs like LOS?
deathhall said:
Same steps, Boots up, I recommend the system-quack-arm64-ab-gapps from your link, as it includes Gapps.
However, With that both I couldn't flash Magisk or I would get a bootloop. With LoS It would also not install gapps. But would boot just fine without Gapps or Magisk.
Currently Phhussons is working with Gapps. LOS Is not, atleast for me, but neither is working with Magisk 20.4.
Click to expand...
Click to collapse
technoboi1 said:
thank for your reply, it has same bugs like LOS?
Click to expand...
Click to collapse
Yup, Same bugs
Sent from my Mi Note 10 using Tapatalk
I remember when Android P GSI comes, we have distorted audio bugs, maybe its same bug again.
Deleting folder vendor/lib64/soundfx fixed bug in Android P.
Bugs
- Fingerprint
- Auto-brightness
- NFC
-Weird notification audio
I have been working on an overlay, but seems like I couldn't fix any bug.
Fingerprint works, but for any reason the Google API/Fingerprint config app is not recognizing it, but I can see in logcat that sensor recognizes when I use the fingerprint with any problem, so maybe problem from the GSI?
For the rest of the bugs, nothing for now
Is there an improvement?
UtkuAblak said:
Is there an improvement?
Click to expand...
Click to collapse
I'm trying to contact with phhusson. Audio can be fixed flashing a .zip
This rom use stock camera or? And what about current photo quality?
Good work and thank you guys!
Hudinited said:
This rom use stock camera or? And what about current photo quality?
Good work and thank you guys!
Click to expand...
Click to collapse
I recommend using a Gcam in order to get better quality, for example: https://www.celsoazevedo.com/files/android/google-camera/dev-urnyx05/ (tell me if you find something better!)
how did you fix the fingerprint?
iSonik said:
how did you fix the fingerprint?
Click to expand...
Click to collapse
It's not fixed yet, What I just said is that 'works' in terms that if you touch the fingerprint it will be recognized in logcat, but nothing will happend on the fingerprint setup app. Currently I'm talking with phhusson about this and thinks that this could be a GSI related issue because he told me he will make a test image
technoboi1 said:
Hi, what do you think, this flashing method will work with phhussons GSI too?
https://github.com/phhusson/treble_experimentations/releases
---------- Post added at 08:00 AM ---------- Previous post was at 07:43 AM ----------
If you need it still, I can copy it now, if you tell me the full path of this file.
Click to expand...
Click to collapse
iFlashed said:
It's not fixed yet, What I just said is that 'works' in terms that if you touch the fingerprint it will be recognized in logcat, but nothing will happend on the fingerprint setup app. Currently I'm talking with phhusson about this and thinks that this could be a GSI related issue because he told me he will make a test image
Click to expand...
Click to collapse
My fingerprint is recognized in logcat as well as the button lighting up, but it doesn't work even in stock rom funny enough.
deathhall said:
My fingerprint is recognized in logcat as well as the button lighting up, but it doesn't work even in stock rom funny enough.
Click to expand...
Click to collapse
What do you mean when you say It doesn't work in stock rom funny enough?
iFlashed said:
What do you mean when you say It doesn't work in stock rom funny enough?
Click to expand...
Click to collapse
When I flashed this GSI for Lineage 17 when the other thread first started, even after Miflashing back to Global Stock my fingerprint doesn't work anymore, If i use the testing options, it'll activate the fingerprint and register me using my finger on it, but wont activate fingerprint settings as a password, it goes to the input screen then kicks back out immediately
deathhall said:
When I flashed this GSI for Lineage 17 when the other thread first started, even after Miflashing back to Global Stock my fingerprint doesn't work anymore, If i use the testing options, it'll activate the fingerprint and register me using my finger on it, but wont activate fingerprint settings as a password, it goes to the input screen then kicks back out immediately
Click to expand...
Click to collapse
This could be something related to unlocked bootloader? u tried to relock the bootloader?
iFlashed said:
This could be something related to unlocked bootloader? u tried to relock the bootloader?
Click to expand...
Click to collapse
Are you asking if i did, or i should? Also, I don't wanna hijack the thread, maybe chat in PM or Discord or whatever you prefer?