[HOW-TO] Earpiece not working/no invoice sound - ONE General

Hello!
So the last couple of weeks I have not been able to hear the other part in phone when making outgoing calls from my device. I have not had any problems at all receiving calls. This fix is not only for Oneplus One, but can be applied to any phone with root access and a custom recovery. Other problems I have found when browsing through internet is;
https://jira.cyanogenmod.org/browse/CYAN-5728 - Cyanogenmod
https://code.google.com/p/android/issues/detail?id=82949 - Nexus 4
... and a bunch of other forums threads.
This problem happened to me when I was using #mirrorenabler. Although this is an awesome application something unfortunately went wrong for me. You can see at the bottom of the first post under the header "For those with audio issues after applying the Force-Close Fix:" that this can be a problem caused by #mirrorenabler. However, this was the case for me, people with similar issues should try these methods and report back.
So I got two ways of fixing this.
METHOD #1
1. Download Root explorer.
2. Go into /System/etc/ and open audio_policy.conf and replace everything with this new audio_policy.conf. THIS AUDIO_POLICY IS ONLY TESTED WITH ONEPLUS ONE. IF YOU ARE USING ANOTHER DEVICE YOU HAVE TO FIND SOMEONE WITH A WORKING DEVICE DUMPING THEIR AUDIO_POLICY FOR YOU. I DO NOT TAKE RESPONSIBILITY.
3. Save, close and reboot device.
Voila. It should work. However if it doesn't, here is another way I was trying;
METHOD #2
1. Backup apps with titanium backup.
2. Backup your SMS
3. Download your ROM u're using again.
3. Reboot into recovery
4. Make a nandroid backup
-- THESE STEPS BELOW IS IMPORTANT --
5. Wipe factory data/reset
6. Wipe cache
7. Go into mounts and storage
8. Format /system
9. Format /data
10. Format /cache
11. Enter advanced
12. Wipe dalvik
9. Flash ROM then gapps
10. Reboot and let the ROM settle.
Method #2 is more likely to work. However, I thought it was worth posting both method as the first method might work for some. Please note that just wiping factory data is not going to work because it doesn't remove the system and data files.
Method #3 | UPDATE
After a while, my earpiece sound disappeared again. Then I started googling and found out that this can also be a problem due to the phone thinks you have earphones plugged in. Luckily there's an app Soundabout that I found that can force the sound through the earpiece. If you have this problem, take a look at Soundabout. After I downloaded it and set the phone call audio to earpiece and connecatable devices -> wired headset settings -> Wired headset detection to OFF, everything works like a charm. Never had the problem since.
If this helped you. Please give me a thanks. Hope this helped someone out there! :fingers-crossed:

superioor said:
METHOD #2
1. Backup apps with titanium backup.
2. Backup your SMS
3. Download your ROM u're using again.
3. Reboot into recovery
4. Make a nandroid backup
-- THESE STEPS BELOW IS IMPORTANT --
5. Wipe factory data/reset
6. Wipe cache
7. Go into mounts and storage
8. Format /system
9. Format /data
10. Format /cache
11. Enter advanced
12. Wipe dalvik
9. Flash ROM then gapps
10. Reboot and let the ROM settle.
Method #2 is more likely to work. However, I thought it was worth posting both method as the first method might work for some. Please note that just wiping factory data is not going to work because it doesn't remove the system and data files.
If this helped you. Please give me a thanks. Hope this helped someone out there! :fingers-crossed:
Click to expand...
Click to collapse
Dirty flashing your ROM should replace all files in system anyway so wiping everything isn't necessary.
sent from my amazingly awesome OnePlus One with Stereo Mod
Don't forget to hit thanks!

abhi08638 said:
Dirty flashing your ROM should replace all files in system anyway so wiping everything isn't necessary.
sent from my amazingly awesome OnePlus One with Stereo Mod
Don't forget to hit thanks!
Click to expand...
Click to collapse
Sure. It should, but the #mirrorenabler code were still in the audio_policy.conf for me when I manually checked it.

superioor said:
Sure. It should, but the #mirrorenabler code were still in the audio_policy.conf for me when I manually checked it.
Click to expand...
Click to collapse
Well that app is no longer needed so this shouldn't cause any more problems
sent from my amazingly awesome OnePlus One with Stereo Mod
Don't forget to hit thanks!

abhi08638 said:
Well that app is no longer needed so this shouldn't cause any more problems
sent from my amazingly awesome OnePlus One with Stereo Mod
Don't forget to hit thanks!
Click to expand...
Click to collapse
As I said in the first post this might be the correct methods to fix problems for nexus 4 and other similar problems for Oneplus One. It is worth a shot.

If you have problem with the Earpiece not working, please check the lated method (#3) that I have posted in the first post. This solved the issue permanently for me.

Thank you so much buddy.
---------- Post added at 12:43 PM ---------- Previous post was at 12:37 PM ----------
Hey buddy thank you so much. Had the problem with the earpiece and now I have successfully resolved the problem using the method#3 that you have mentioned(Didn't try the first two methods,jumped directly to the third one). Phone's working absolutely fine now. Thanks to you. God bless you.

Related

Power Amp "Too many failed files" Final, Permanent FIX!

If there is another method out, please forgive me. I have tried many and this is the only one to work for me.
1. Backup all data and apps with TI Backup!
2. Reboot into CWM
3. Backup your rom with CWM for the love of god!
4. Wipe data/Factory reset 3 times
5. Wipe cache 3 times
6. Wipe dalvik cache 3 times
7. Install a fresh ROM and DO NOT RESTORE DATA!!!
8. Boot into freshly installed rom and use TI Backup to batch restore everything you hold dear to you exept for Power Amp.
9. Restore Power Amp "APP ONLY" / Or install fresh copy
You will now notice that you can change songs as much as you want for as long as you want and no more errors!!!!
I hope this helps some of you out as it did for me. This also should work for any galaxy s phones as we seem to be the ones maily affected.
biggnasty989 said:
If there is another method out, please forgive me. I have tried many and this is the only one to work for me.
1. Backup all data and apps with TI Backup!
2. Reboot into CWM
3. Backup your rom with CWM for the love of god!
4. Wipe data/Factory reset 3 times
5. Wipe cache 3 times
6. Wipe dalvik cache 3 times
7. Install a fresh ROM and DO NOT RESTORE DATA!!!
8. Boot into freshly installed rom and use TI Backup to batch restore everything you hold dear to you exept for Power Amp.
9. Restore Power Amp "APP ONLY" / Or install fresh copy
You will now notice that you can change songs as much as you want for as long as you want and no more errors!!!!
I hope this helps some of you out as it did for me. This also should work for any galaxy s phones as we seem to be the ones maily affected.
Click to expand...
Click to collapse
wow. All that just to get powerAMP working properly? Why not just use playerPRO
What is this in relation to? Is there a rom or mod that breaks it? I have been using it for about 8 months and have never had a problem. I am mostly stock with a theme, volume rocker and tws fix.
Sent from my SPH-D700 using XDA Premium App
crawrj said:
What is this in relation to? Is there a rom or mod that breaks it? I have been using it for about 8 months and have never had a problem. I am mostly stock with a theme, volume rocker and tws fix.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
When you install a new rom and just "restore data" from CWM it somehow messes with the way power amp reads files and sees too many blank spaces or something in between songs.
Dont forget to export your contacts too, since you wont be restoring data! this is the best advice I can give. I know its a pain in the ass but all my friends with Epics, and even a fascinate bro, have done this and are now totally enjoying power amp without probs.
Ive had this issue a few times and decided to search about it... This is what I found to work without loading any data, well other than power amp settings... simply go to settings>applications>manage applications>poweramp the select clear data. Worked fine for me. i got the poweramp error, went to clear data, went back to poweramp and started listening to music.... just thought id chime in with a easier route
puff601 said:
Ive had this issue a few times and decided to search about it... This is what I found to work without loading any data, well other than power amp settings... simply go to settings>applications>manage applications>poweramp the select clear data. Worked fine for me. i got the poweramp error, went to clear data, went back to poweramp and started listening to music.... just thought id chime in with a easier route
Click to expand...
Click to collapse
This worked for me too, SO MUCH EASIER.
Thanks
biggnasty989 said:
When you install a new rom and just "restore data" from CWM it somehow messes with the way power amp reads files and sees too many blank spaces or something in between songs.
Dont forget to export your contacts too, since you wont be restoring data! this is the best advice I can give. I know its a pain in the ass but all my friends with Epics, and even a fascinate bro, have done this and are now totally enjoying power amp without probs.
Click to expand...
Click to collapse
Power Amp is nice but retarded haha. i never had this issue the only problem i get is this license isn't valid but it is too and it was working for the past month now all of sudden you don't work, but even though the message appears i can still play music and use the app.

GSM Calling on Stock ICS Works Perfectly,

Hey all,
I wnated to let everyone know that almaqdad has perfected a mod that allows flawless gsm calling from P-7500
Check out the thread on the Android Developer Forum (GTab 10.1) or follow this link:
http://forum.xda-developers.com/showthread.php?t=1875024
Some pointers:
1. Make sure that you are rooted. I dont know if this would affect the mod, but my tab was rooted when i did this
2. Make sure that you have a custom recovery CWM or TWRP
3. Make a full backup. Save a copy of the backup on ur PC. Use titanium or other software to back up ur apps
4. Copy the appropriate files on the rooot folder of ur tab.
5. Format the cache and Dalvik Cache.
6. Flash both the .zip files and boot into android
7. Voila! Your tab is now a 10.1 inch phone as well!
Issues that i faced:
The first time i flashed the files, it simply refused to work. My simcard wasn't detected. I has applied a couple of patches that might have
Been interfearing with the mod, so I used odin to reflash my rom. I then flashed CWM followed by rooting the rom.
Next install currupted the market. I think this was because I was so excited about trying out this mod and there were a couple of active
Downloads running and I rebooted the tab, took a backup and formatted cache and dalvik cache. Then applied the mod. This currupted the market,
It would finish the download then crash as it was trying to install the app. I think this was because it resumed the downloads from wgere it left off
Without chcecking the file integrity
I then did a factory reset, flashed tge mods and everything now works flawlessly. Even the gsm calls are flawless and I've made calls that lasted a good hour at a time.
Be Sure to Reboot the tab a couple of times if your calls drop for no reason after a couple of mins. Calls are best if you are uding a headset. The mike on the tab is very good, although your voice may sound a bit different on the other end of the line. Enjoy!
**Update**
Voice calling works best with a headset plugged in, I'm using an ordinary headphone. Otherwise, the calls disconnect after roughly 40s-1min. I'm not allowed to post on the Dev forum. In case the Mod Dev is unaware of this, I would appreciate if someone would post this bug on his post.
I don't know if this bug is rectified with the use of a BT headset.
No bugs for me with Toldo's rom
mohsin.parwez said:
Hey all,
I wnated to let everyone know that almaqdad has perfected a mod that allows flawless gsm calling from P-7500
Check out the thread on the Android Developer Forum (GTab 10.1) or follow this link:
http://forum.xda-developers.com/showthread.php?t=1875024
Some pointers:
1. Make sure that you are rooted. I dont know if this would affect the mod, but my tab was rooted when i did this
2. Make sure that you have a custom recovery CWM or TWRP
3. Make a full backup. Save a copy of the backup on ur PC. Use titanium or other software to back up ur apps
4. Copy the appropriate files on the rooot folder of ur tab.
5. Format the cache and Dalvik Cache.
6. Flash both the .zip files and boot into android
7. Voila! Your tab is now a 10.1 inch phone as well!
Issues that i faced:
The first time i flashed the files, it simply refused to work. My simcard wasn't detected. I has applied a couple of patches that might have
Been interfearing with the mod, so I used odin to reflash my rom. I then flashed CWM followed by rooting the rom.
Next install currupted the market. I think this was because I was so excited about trying out this mod and there were a couple of active
Downloads running and I rebooted the tab, took a backup and formatted cache and dalvik cache. Then applied the mod. This currupted the market,
It would finish the download then crash as it was trying to install the app. I think this was because it resumed the downloads from wgere it left off
Without chcecking the file integrity
I then did a factory reset, flashed tge mods and everything now works flawlessly. Even the gsm calls are flawless and I've made calls that lasted a good hour at a time.
Be Sure to Reboot the tab a couple of times if your calls drop for no reason after a couple of mins. Calls are best if you are uding a headset. The mike on the tab is very good, although your voice may sound a bit different on the other end of the line. Enjoy!
**Update**
Voice calling works best with a headset plugged in, I'm using an ordinary headphone. Otherwise, the calls disconnect after roughly 40s-1min. I'm not allowed to post on the Dev forum. In case the Mod Dev is unaware of this, I would appreciate if someone would post this bug on his post.
I don't know if this bug is rectified with the use of a BT headset.
Click to expand...
Click to collapse
No need for new thread, there Is already one open In the general forum, please search before posting new threads ( http://forum.xda-developers.com/showthread.php?p=31109073
Sent from my GT-P7500 using xda app-developers app
thanks
yes followed instructions and its working

[Help Needed] Apps won't restore or install after flashing rom [SOLVED!]

Well, my first venture into rom flashing hasn't been the most successful one as it's caused a really strange issue that a couple people on another thread have tried to help me solve, but I figure I had hijacked that thread long enough so this issue deserved it's own thread.
I rooted, unlocked bootloader, and installed TWRP v2.4.0.0 on Stock Android 4.1.1. Everything worked great. Until I flashed a rom. Now, I have been through wiping Cache, Dalvik Cache, Factory Reset, Flashing the rom (I've tried 4 with the same exact issue), flashing Gapps... All seems to go well and it says "success" when I flash, and I reboot into system. Run the setup of Google. Everything seems great and working fine. Here's where the problem is. When Google Play Store starts downloading for restore, and I'm on a solid wifi connection, nothing downloads. I have also tried stopping the downloads and installing apps individually. When I do that, I receive the same error message over and over for any app:
Unknown error code during application install: "-24"
I've rebooted, wiped cache, dalvik cache. Nothing installs. Same error. I did somehow, some way, get Titanium backup to install after numerous tries... when I try to restore any of that backup it just hangs on the first app. It does not restore anything. No batch apps. No single apps. No app data.
The odd thing is, the first time I flashed a rom, it seemed to load up fine. Stupidly, when I was running Titanium Backup for a restore I was not paying attention to what I was restoring. I was restoring all apps and app data... It caused an issue and a bunch of force closes, as you can probably imagine. So I rebooted into recovery and wiped and reinstalled rom and gapps. And virtually nothing has installed since. I have wiped and reinstalled AOKP, PACman, Carbon, and CM to no avail. Nothing seems to solve my issue. I'd love to at the very least be able to regularly install apps from the Play Store. At this point I'm not even concerned with restoring app data if that's too much to ask. I just want to be able to use my phone normally again as this is my "daily driver". If I have to go back to 4.1.1, that would be fine with me. I just want to get back to normal. And I'll do whatever it takes to get there. Any help at all would be appreciated.
Here is the original thread that some people have been giving me great advice on as to what to do, but none of it has fixed the issue yet unfortunately:
http://forum.xda-developers.com/showthread.php?t=2341470
Jersey846 said:
Well, my first venture into rom flashing hasn't been the most successful one as it's caused a really strange issue that a couple people on another thread have tried to help me solve, but I figure I had hijacked that thread long enough so this issue deserved it's own thread.
I rooted, unlocked bootloader, and installed TWRP v2.4.0.0 on Stock Android 4.1.1. Everything worked great. Until I flashed a rom. Now, I have been through wiping Cache, Dalvik Cache, Factory Reset, Flashing the rom (I've tried 4 with the same exact issue), flashing Gapps... All seems to go well and it says "success" when I flash, and I reboot into system. Run the setup of Google. Everything seems great and working fine. Here's where the problem is. When Google Play Store starts downloading for restore, and I'm on a solid wifi connection, nothing downloads. I have also tried stopping the downloads and installing apps individually. When I do that, I receive the same error message over and over for any app:
Unknown error code during application install: "-24"
I've rebooted, wiped cache, dalvik cache. Nothing installs. Same error. I did somehow, some way, get Titanium backup to install after numerous tries... when I try to restore any of that backup it just hangs on the first app. It does not restore anything. No batch apps. No single apps. No app data.
The odd thing is, the first time I flashed a rom, it seemed to load up fine. Stupidly, when I was running Titanium Backup for a restore I was not paying attention to what I was restoring. I was restoring all apps and app data... It caused an issue and a bunch of force closes, as you can probably imagine. So I rebooted into recovery and wiped and reinstalled rom and gapps. And virtually nothing has installed since. I have wiped and reinstalled AOKP, PACman, Carbon, and CM to no avail. Nothing seems to solve my issue. I'd love to at the very least be able to regularly install apps from the Play Store. At this point I'm not even concerned with restoring app data if that's too much to ask. I just want to be able to use my phone normally again as this is my "daily driver". If I have to go back to 4.1.1, that would be fine with me. I just want to get back to normal. And I'll do whatever it takes to get there. Any help at all would be appreciated.
Here is the original thread that some people have been giving me great advice on as to what to do, but none of it has fixed the issue yet unfortunately:
http://forum.xda-developers.com/showthread.php?t=2341470
Click to expand...
Click to collapse
2 suggestions:
1) i think others have reported having issues with TWRP 2.4, so try 2.5 or 2.3.2.3
2) I think the error could be a lack of internal storage, so certainly try the "wipe internal storage" in TWRP (after making sure that your ROM/GApp files, backups (including Tibu) are saved to your external folder
jco23 said:
2 suggestions:
1) i think others have reported having issues with TWRP 2.4, so try 2.5 or 2.3.2.3
2) I think the error could be a lack of internal storage, so certainly try the "wipe internal storage" in TWRP (after making sure that your ROM/GApp files, backups (including Tibu) are saved to your external folder
Click to expand...
Click to collapse
Ok giving this a shot. I did notice that you had mentioned a different version of TWRP than I had. I will try the wiping internal storage before I install a different TWRP then if that doesn't work, TWRP. Gotta find the external folder. Unless you just mean anything that is on the actual SD card.
Jersey846 said:
Ok giving this a shot. I did notice that you had mentioned a different version of TWRP than I had. I will try the wiping internal storage before I install a different TWRP then if that doesn't work, TWRP. Gotta find the external folder. Unless you just mean anything that is on the actual SD card.
Click to expand...
Click to collapse
i would actually recommend installing TWRP 2.5 first.
never wipe external SD card.
if you have an app called Root Explorer, that works best.
jco23 said:
i would actually recommend installing TWRP 2.5 first.
never wipe external SD card.
if you have an app called Root Explorer, that works best.
Click to expand...
Click to collapse
Ok I'll try 2.5 then. And I wasn't gonna wipe the card, just was wondering if when you said external folder you were talking about the SD card. Root explorer works great.. if i could install it.
EDIT: Since I am away from my computer, I tried the multiple wipe method. Didn't change anything. So I will be changing TWRP versions later and will post an update.
Jersey846 said:
Ok I'll try 2.5 then. And I wasn't gonna wipe the card, just was wondering if when you said external folder you were talking about the SD card. Root explorer works great.. if i could install it.
EDIT: Since I am away from my computer, I tried the multiple wipe method. Didn't change anything. So I will be changing TWRP versions later and will post an update.
Click to expand...
Click to collapse
You never mentioned using TWRP 2.4. DEFINITELY replace that. Also, just a thought. If you haven't already done so, try using the option to fix permissions. I'm fairly sure its an option in TWRP.
Sent from my XT907 using xda premium
Back in business! Wow thank you all so much! What a pain it's been but without the help I'd have never guessed how to get this running as perfectly as it is now. Here's what worked for me:
Installed TWRP 2.5 (Instead of what I had, 2.4)
Then followed jco23's precise directions:
jco23 said:
- I use TWRP 2.3.2.3 (SS has been uninstalled via it's own app, not Tibu or the system awhile ago) - but TWRP 2.5 works just fine for others
- after downloading the ROM and GApps (or any file that I intended to flash for that matter), I always place the file on the mnt/external1 directory. I
m not sure if this will make a difference, but I recall it being an issue back on my Droid Charge days
- after flashing the files, does TWRP say successful?
- perhaps you do need to a double wipe of everything prior to flashing:
1) mount everything
2) wipe cache
3) wipe dalvik cache
4) wipe system
5) factory reset/wipe data
6) wipe internal storage (if you do this, make sure to change your TiBu backup folder to your external1 directory, or this will be gone too!!!!! also make sure that the system backup you made is on the external1 directory as well
7) reboot recovery
8) install ROM
9) install GApps
Click to expand...
Click to collapse
And it's working flawlessly. Able to download or restore anything from Gapps. Was able to restore some specific app data from Titanium Backup (did not want to ruin the phone again and do that full restore so I selected specific apps that I really wanted the data on).
Thanks to everyone who took the time to assist me and a special thanks to jco23 and netizenmt who were with me through this whole debacle, leading me through every possible fix they could think of. As for those of you that may be wondering which ROM I settled on... AOKP.
Good for you bro! That stinking TWRP 2.4.0 is such a menace! Wish there was a way to have it yanked from circulation. Glad you're up and running!
Sent from my Droid Razr M using xda premium
Jersey846 said:
Back in business! Wow thank you all so much! What a pain it's been but without the help I'd have never guessed how to get this running as perfectly as it is now. Here's what worked for me:
Installed TWRP 2.5 (Instead of what I had, 2.4)
Then followed jco23's precise directions:
And it's working flawlessly. Able to download or restore anything from Gapps. Was able to restore some specific app data from Titanium Backup (did not want to ruin the phone again and do that full restore so I selected specific apps that I really wanted the data on).
Thanks to everyone who took the time to assist me and a special thanks to jco23 and netizenmt who were with me through this whole debacle, leading me through every possible fix they could think of. As for those of you that may be wondering which ROM I settled on... AOKP.
Click to expand...
Click to collapse
glad you finally got it working - this is just the first step in becoming a crack-flasher....
jco23 said:
glad you finally got it working - this is just the first step in becoming a crack-flasher....
Click to expand...
Click to collapse
Yeah, I've got it bad. I have had CM 10.1, Slimbean, Carbon AND AOKP on my phone all in the last 2 days. Carbon is on it right now. No telling what will be on it by tonight.
Sent from my XT907 using xda premium
netizenmt said:
Yeah, I've got it bad. I have had CM 10.1, Slimbean, Carbon AND AOKP on my phone all in the last 2 days. Carbon is on it right now. No telling what will be on it by tonight.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
funny, and the goal is to find a ROM that you're happy with and don't need to flash.
but I've been on Carbon since 7/5, and very happy.

[GUIDE] How to flash roms/kernels

This a simple guide I made for the note 3. Seeing these 2 questions being asked alot here so posting it here. Will need to edit it a bit so currently it's a WIP.
NOTE- First thing you should do before flashing roms/kernels for the first time is backup EFS.
How to flash CLEAN flash roms -*This is how I flash roms(even updates of the same rom) and the method i recommend to users. It is better to take 10 mins to set your phone again rahter than wasting more time to fix issues that could have been avoided by a clean flash.
NOTE- This is a MUST when changing roms.
1. Make a nandroid backup in recovery
3. Wipe data/factory reset
4. Wipe system
5. Wipe cache
6. Wipe dalvik
7. Flash ROM
8. Flash gapps
9. Flash kernel(optional)
10. Reboot
11. Wait 10 mins, then do another reboot
12. Enjoy
How to DIRTY flash roms -*This method is used by users when flashing a update of the same rom.*
NOTE- Some users follow this and some just flash the rom without wiping anything.
Note- If you flash rom that has aroma installer you will need to edit the updater script to make sure the aroma doesn't wipe system before flashing rom.
1. Make a nandroid backup in recovery
3. Wipe cache
4. Wipe dalvik
5. Flash ROM
6. Flash gapps
7. Flash AK kernel(optional)
8. Reboot
9. Wait 10 mins, then do another reboot
10. Enjoy
How to SUPER CLEAN flash roms -*This is the method that I recommend to your that have weird issues, even after clean flashing.
Will be adding this method. Need to edit it a bit.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
How to flash flash kernels -*Many users say to wipe cache/dalvik but it's useless as neither if their partitions are affected when flashing a kernel.
1. Boot into recovery*
2. Flash kernel*
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
@Khizar welcome back man, good to see you're writing guides again. Get that RC title again!
Sent from my OnePlus One using Tapatalk VIP
nicholaschum said:
@Khizar welcome back man, good to see you're writing guides again. Get that RC title again!
Sent from my OnePlus One using Tapatalk VIP
Click to expand...
Click to collapse
Yeah let's hope ppl actually read and my time editing see stuff to make it for OPO isn't wasted.. These forums seem to be worse than the note 3 ones.. Man saw this guy today who apparently couldn't find the link to gapps that was posted in the OP.. SMH
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Khizar said:
This a simple guide I made for the note 3. Seeing these 2 questions being asked alot here so posting it here.
Click to expand...
Click to collapse
While this is true, it's because people are too lazy to use the search feature or at least look at the stickies. But the information is out there already.
[GUIDES][Q&A]How-To Guides For Beginners + Q&A
CafeKampuchia said:
While this is true, it's because people are too lazy to use the search feature or at least look at the stickies. But the information is out there already.
[GUIDES][Q&A]How-To Guides For Beginners + Q&A
Click to expand...
Click to collapse
I've seen that thread, it's pretty useful bit I wouldn't say "the information is out there already. If you read the thread his instructions are just telling users how to wipe and flash roms.
The point of my thread was, or still is, to list all the different ways to flash roms. Clean, dirty, super clean. Most new users don't know the difference.
With that being said I am not saying anything negative about the guide nor am I comparing the 2 guides. Think that I should add that, on the Internet things are usually misinterpreted.
I am simply making a bit know detailed and specify guide just for flashing roms.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Amazing as usual! You're a treasure, my friend! So happy to see you back on xda!
Plus... do you really want me to tell you how we "dirty flashers" flash roms? love you man, you're perfect!
NOTE- This is a MUST when changing roms.
1. Backup EFS -Not necessary every time you flash a ROM.
2. Make a nandroid backup in recovery -Not necessary every time you flash a ROM.
3. Wipe data/factory reset
4. Wipe system
5. Wipe cache
6. Wipe dalvik
7. Flash ROM
8. Flash gapps
9. Flash AK kernel(optional) -There are many kernels available for our device, not just AK.
10. Reboot
11. Wait 10 mins, then do another reboot -Not necessary.
12. Enjoy
Transmitted via Bacon
daxgirl said:
Amazing as usual! You're a treasure, my friend! So happy to see you back on xda!
Plus... do you really want me to tell you how we "dirty flashers" flash roms? love you man, you're perfect!
Click to expand...
Click to collapse
Haha no comments... ?
timmaaa said:
NOTE- This is a MUST when changing roms.
1. Backup EFS -Not necessary every time you flash a ROM.
2. Make a nandroid backup in recovery -Not necessary every time you flash a ROM.
3. Wipe data/factory reset
4. Wipe system
5. Wipe cache
6. Wipe dalvik
7. Flash ROM
8. Flash gapps
9. Flash AK kernel(optional) -There are many kernels available for our device, not just AK.
10. Reboot
11. Wait 10 mins, then do another reboot -Not necessary.
12. Enjoy
Transmitted via Bacon
Click to expand...
Click to collapse
Did you read the first few sentence of the OP? Like I said it's a WIP and I need to edit stuff.
But after seeing your edits, the only thing I agree I need to edit out is doing an EFS backup every time you flash a rom. Nandroid is a must IMO, you never know when you'll be unlucky.
As for the "there are many kernels avaliable".. It says optional next to it for a reason.
And about waiting 10 after a rom/kernel and rebooting not being necessary, from my experience it helps let the rom/kernel settle. There was a time when devs used to recommend that. I still do that and recommend it.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Khizar said:
Haha no comments... ?
Did you read the first few sentence of the OP? Like I said it's a WIP and I need to edit stuff.
But after seeing your edits, the only thing I agree I need to edit out is doing an EFS backup every time you flash a rom. Nandroid is a must IMO, you never know when you'll be unlucky.
As for the "there are many men kernels avaliable".. It says optional next to it for a reason.
And about waiting 10 after a rom/kernel and rebooting not being necessary, from my experience it helps let the rom/kernel settle. There was a time when devs used to recommend that. I still do that and recommend.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Click to expand...
Click to collapse
Yeah I did read it and that's why I was putting forth my constructive criticism. The nandroid isn't an absolute must every time you flash though, if you have at least one nandroid on your phone at all times you have insurance against the unknown, whether or not you do that with every flash is purely optional (as opposed to describing it as essential, because it just isn't).
There's a reason devs don't recommend to reboot a second time after a ROM flash anymore, because it isn't essential either.
I only mentioned the kernel because it might seen as favouritism, and it's always best to remain objective in a guide thread.
I'm detecting animosity in your reply. Don't get me wrong, I'm all for having resources, I'm about to add your thread to my index thread so folks can find it easier. I'm just pointing out things that aren't actually essential every time a ROM is flashed, trying to save the user unnecessary time and effort.
Transmitted via Bacon
---------- Post added at 07:45 PM ---------- Previous post was at 07:38 PM ----------
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
timmaaa said:
Yeah I did read it and that's why I was putting forth my constructive criticism. The nandroid isn't an absolute must every time you flash though, if you have at least one nandroid on your phone at all times you have insurance against the unknown, whether or not you do that with every flash is purely optional (as opposed to describing it as essential, because it just isn't).
OK. I agree with this, I'll change it to optional and have a bold warning that you should have atleast one nandroid just in case at all times.
There's a reason devs don't recommend to reboot a second time after a ROM flash anymore, because it isn't essential either.
OK this one I am kinda biased about, have had the same discussion with many others. I've always experienced that if I use a rom/kernel right after I flash everything is a bit laggy. If I wait 10 mins and reboot, everything is a lot smoother.
I only mentioned the kernel because it might seen as favouritism, and it's always best to remain objective in a guide thread.
Hmm.. You do have a point, I'll edit that bit.
I'm detecting animosity in your reply. Don't get me wrong, I'm all for having resources, I'm about to add your thread to my index thread so folks can find it easier. I'm just pointing out things that aren't actually essential every time a ROM is flashed, trying to save the user unnecessary time and effort.
Feedback is always welcome. I appreciate you taking the time and commenting here.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks for adding the thread to the index. :good:
Khizar said:
Thanks for adding the thread to the index. :good:
Click to expand...
Click to collapse
No worries mate. All good, and well done on the thread!
Transmitted via Bacon
Khizar said:
Yeah let's hope ppl actually read and my time editing see stuff to make it for OPO isn't wasted.. These forums seem to be worse than the note 3 ones.. Man saw this guy today who apparently couldn't find the link to gapps that was posted in the OP.. SMH
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Click to expand...
Click to collapse
CafeKampuchia said:
While this is true, it's because people are too lazy to use the search feature or at least look at the stickies. But the information is out there already.
[GUIDES][Q&A]How-To Guides For Beginners + Q&A
Click to expand...
Click to collapse
Nice job and I agree it was getting a little crazy in here as well with the how do I flash this rom crap. I thought this was self explanatory but it seems to be a lot of first timers in here.
I know you said your instructions are a WIP but simply remember when you are ready to put out the finished product you must think as they do the super duper noobs and try and make it as flashing for dummies as possible. They will hold on to your every letter.
I agree that a recent nandroid is needed and honestly I keep 2 at least on my phone because I have been burnt with a corrupted backup before. Also who wants to restore a rom from 2 months ago.... :good:
Nice work
If I may I would like to make some suggestions ??? may I? And no... not as a dirty flasher... if is OK with you, I will...
playya said:
Nice job and I agree it was getting a little crazy in here as well with the how do I flash this rom crap. I thought this was self explanatory but it seems to be a lot of first timers in here.
I know you said your instructions are a WIP but simply remember when you are ready to put out the finished product you must think as they do the super duper noobs and try and make it as flashing for dummies as possible. They will hold on to your every letter.
I agree that a recent nandroid is needed and honestly I keep 2 at least on my phone because I have been burnt with a corrupted backup before. Also who wants to restore a rom from 2 months ago.... :good:
Nice work
Click to expand...
Click to collapse
Yes I think I'll try to make it simpler and more easier for new users to understand, a dummy proof version as you said. Thanks for your feedback.
daxgirl said:
If I may I would like to make some suggestions ??? may I? And no... not as a dirty flasher... if is OK with you, I will...
Click to expand...
Click to collapse
Since when have you needed to ask for permission Anna..? Anyways all suggestions are welcome.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Khizar said:
Yes I think I'll try to make it simpler and more easier for new users to understand, a dummy proof version as you said. Thanks for your feedback.
Since when have you needed to ask for permission Anna..? Anyways all suggestions are welcome.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Click to expand...
Click to collapse
Well we already know that I am a polite non xda material
Sooooooo here we go...
1. When you wipe data in any recovery, it includes AT LEAST 3 things: a. Format data partition b. Eliminate dalvik exec files along with that (since dalvik cache sits on data partition) c. Format cache
So after wiping data, there is not reason to wipe cache and dalvik cache, since they have already been cleaned as a whistle.
2. During rom installation, new framework jars are being pushed over /system/framework. It's enough for just android.policy.jar to be replaced, the android will rebuild all dalvik upon boot (hence the "Android is upgrading. Optimizing xx app out of xxx"). All the major jars upon replacement will wipe dalvik and rebuild it. It's enough to have 1 byte of difference.
So I guess that summorizes the need for wiping dalvik cache.
3. As for wiping system. Well things are a bit more controversial here. Since any normal rom updater script has as first command "mount /system" and as second command "delete recursive /system", it seems like there is no need as well. BUT!!!
There seems to be a discussion whether formatting system (which is done when it's unmounted) the way recovery does it in "mounts and storage " is more "thorough and effective" then recursively deleting it (when it's mounted) by the updater script.
So I can see the point in formatting system! Well, a little...
Hey, don't get me wrong, I admire this guide and I think it's super helpful! I just always feel the need to set things straight with this "triple wipe" that everyone keeps recommending.
Imo, wipe data is simply enough that is IF you're not a dirty flasher. ..
Now to the last part! You guys all have pretty uh the same sqlite vs in all those aosp/cm/aokp roms.
All I am saying: sometimes you can try to flash without wipe, if there is a problem, which in most cases there won't be, some individual data/data databases can be deleted and rebuilt. Maybe we should write a guide on dirty flashing I am certainly good at THAT
daxgirl said:
Well we already know that I am a polite non xda material
Sooooooo here we go...
1. When you wipe data in any recovery, it includes AT LEAST 3 things: a. Format data partition b. Eliminate dalvik exec files along with that (since dalvik cache sits on data partition) c. Format cache
So after wiping data, there is not reason to wipe cache and dalvik cache, since they have already been cleaned as a whistle.
2. During rom installation, new framework jars are being pushed over /system/framework. It's enough for just android.policy.jar to be replaced, the android will rebuild all dalvik upon boot (hence the "Android is upgrading. Optimizing xx app out of xxx"). All the major jars upon replacement will wipe dalvik and rebuild it. It's enough to have 1 byte of difference.
So I guess that summorizes the need for wiping dalvik cache.
3. As for wiping system. Well things are a bit more controversial here. Since any normal rom updater script has as first command "mount /system" and as second command "delete recursive /system", it seems like there is no need as well. BUT!!!
There seems to be a discussion whether formatting system (which is done when it's unmounted) the way recovery does it in "mounts and storage " is more "thorough and effective" then recursively deleting it (when it's mounted) by the updater script.
So I can see the point in formatting system! Well, a little...
Hey, don't get me wrong, I admire this guide and I think it's super helpful! I just always feel the need to set things straight with this "triple wipe" that everyone keeps recommending.
Imo, wipe data is simply enough that is IF you're not a dirty flasher. ..
Now to the last part! You guys all have pretty uh the same sqlite vs in all those aosp/cm/aokp roms.
All I am saying: sometimes you can try to flash without wipe, if there is a problem, which in most cases there won't be, some individual data/data databases can be deleted and rebuilt. Maybe we should write a guide on dirty flashing I am certainly good at THAT
Click to expand...
Click to collapse
1. I get what you're saying with the wiping being a little excessive, again this comes down to experience. My guide is made from what I have personally experienced.
Factory reset does wipe cache and dalvik but I am a believer in "better safe than sorry". Same thing with wiping system even though, like you said, most updater scripts wipe system. Also the bigger reason WHY I am firm in saying atleast wipe data and system is cuz I have noticed in sometimes that when I wipe system as opposed to only wiping data, the experience is better so I have come to the conclusion that the recoveries manual wiping options are to be trusted more.
2. You're right about the dirty flashing, you'll be happy to hear I've been flashing dirty since I got the phone. Now dirty flashing different roms is a bit tricky but I have had success, however even if it gets messy I always have a backup.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Khizar said:
9. Wait 10 mins, then do another reboot
Click to expand...
Click to collapse
I can not understand this step? After the first reboot the new OS booted UP, you must set in and installing the Google APPS update if it available. After the first bootup, why should the users rebooting the device?
Criton30 said:
I can not understand this step? After the first reboot the new OS booted UP, you must set in and installing the Google APPS update if it available. After the first bootup, why should the users rebooting the device?
Click to expand...
Click to collapse
After the first boot up, Java has to create it's working areas for the OS to function well, and it configures the kernel and miscellaneous trash handling (if dirty flashed). Rebooting will clear the supposedly terminates "completed services" after they were used to configure Android on first boot, hence things like kernel will be set on next boot, and on the next boot, you will have a clean Daily Driver configuration.
Also, it's like "why do you reboot your computer after a new install of a big program?", well, for it to settle, and to reinitiate the program. In this case, Android was setting up all your working directories on your internal storage, clearing out junk it may have had, and also rebuilding of the VM. That's a lot of work. Why not reboot to make sure everything that has been sitting on idle after making all these folders, would be terminated completely so just to make sure everything goes right.
nicholaschum said:
After the first boot up, Java has to create it's working areas for the OS to function well, and it configures the kernel and miscellaneous trash handling (if dirty flashed). Rebooting will clear the supposedly terminates "completed services" after they were used to configure Android on first boot, hence things like kernel will be set on next boot, and on the next boot, you will have a clean Daily Driver configuration.
Also, it's like "why do you reboot your computer after a new install of a big program?", well, for it to settle, and to reinitiate the program. In this case, Android was setting up all your working directories on your internal storage, clearing out junk it may have had, and also rebuilding of the VM. That's a lot of work. Why not reboot to make sure everything that has been sitting on idle after making all these folders, would be terminated completely so just to make sure everything goes right.
Click to expand...
Click to collapse
so if I understand you correctyl, after the first bootup after the OS installation I must reboot the phone before setting up the google account and soo on?

XtremeAddiction [5.8.021S-Le2]

Note: i am just sharing this ROM. Credits to All XDA developers for various mods & for identifying & compiling perfect sounds libs etc and tweaking the rom which makes this rom awesome. If you are a music & performance lover then this rom is for you.
*********************************************************************************************************************************************************************************************​XtremeAddiction for LeEco Le 2 X52x Devices, INDIAN and U.S Variants,Snapdragon 652 devices only.
XtremeAddiction Rom (Marshmallow stock based) with super Tweaks,mods,performance with mind blowing music performance and lots more.
*****************************************************************
****************************************************************************************************************************​Features :
** Android 6.0.1
** -Rooted
** BussyBox
** Full Init.d support and tweaks
** Better Wifi / 4G
** Awesome Audio / Music Quality
** Good improved Video Quality
** Imporoved battery backup
** Injected Optimal Audio Libs and tweaks
** Build.prop Tweaks
** And Many More….
Tip: just uninstall the Bassboost app. (Must do it for beats boom)​ROM Installation :
Note : This is one time setup and you must follow exact steps in order for installtion,or else you will miss the WoW factor of rom.
Download all the zip files to your device memory/CPU memory GIVEN BELOW .
Clean Installation:
1. Reboot to Twrp then Tap Wipe>Swipe to factory rest then >advance wipe>select dalvik,cache,system,and data then swipe to wipe. (no need to wipe internal storage)
2. Go back then tap install and select XtremeAddiction_Le2 from your storage and install it,after flashing completed don't reboot your device, go back and tap wipe and again swipe to factory reset then go back
Install
1. RootFix.zip then go back and install
2. Init.dFix.zip then go back and install
3. SuperVivid.zip then go back and install
4. ARISESoundSystem.zip then wipe dalvik/cache and reboot the device.(First boot may take a while)
After first boot
Open EuiModder App first uncheck every thing and select / check Enable Standard Scale Mode, then go back
Next open SELinuxModeChanger app and tap Permissive after that reboot the device to Twrp and
Install
5. XAudio.zip then go back and install
6. XtremeBeats.zip then go back and install
7. BassMagic.zip then go back and install (Update)
8. Le2_BeatsAudio.zip then wipe dalvik/cache and reboot the device. That's it you are ready to rock
Addon / Optional Installation ixelLauncher_Transparent:
Boot into Twrp and install PixelLauncher_Transparent.zip then reboot the device.
Note : For those who dont have CDLA earphones I Recommend to use good Bluetooth Stereo headsets for best music performance. Bluetooth rocks with this rom.
DOWNLOAD: CLICK HERE
Thread cleaned up.
Please respect each other. No need to go mad on each.
If you spot a rule violation, please report it along with appropriate evidence.
If you feel someone annoying, kindly add them to your ignore list and move on.
Regards
Vatsal,
Forum Moderator.
Screenshots Please
Thank you for posting this rom. Had trouble finding it since it wasnt on the development page. Ive gone through about 7 roms and none were 100% working and I had a lot of trouble finding a way to get back to stock 21s for my X522. All the custom roms Ive tried either have a broken camera, missing cell broadcast, or hangouts wouldnt work on it when trying to make a call or use video chat. This is the only stable working rom Ive came across so far.
redspeed said:
Thank you for posting this rom. Had trouble finding it since it wasnt on the development page. Ive gone through about 7 roms and none were 100% working and I had a lot of trouble finding a way to get back to stock 21s for my X522. All the custom roms Ive tried either have a broken camera, missing cell broadcast, or hangouts wouldnt work on it when trying to make a call or use video chat. This is the only stable working rom Ive came across so far.
Click to expand...
Click to collapse
Thank you for appreciating. All nougat ROMS are almost stable. using MOKEE 7.1.2 and its ready for daily use.
Is volte working fine?
Drooes said:
Screenshots Please
Click to expand...
Click to collapse
in OP
I'm asking again... @Leeco Le x522 Is Volte working fine becoz i'm fed with up small eui(bad sot). Please report.
AbhiAndro said:
I'm asking again... @Leeco Le x522 Is Volte working fine becoz i'm fed with up small eui(bad sot). Please report.
Click to expand...
Click to collapse
dear i hope so coz VoLte is stable in 21s
wht about the sot on this rom?
cjcool_123 said:
wht about the sot on this rom?
Click to expand...
Click to collapse
same as 21s
cjcool_123 said:
wht about the sot on this rom?
Click to expand...
Click to collapse
5-6 H
I'm assuming if I remove root the font will be back to normal? On some applications the font is way too big. (I assume due to the Instructions given)
Christhepenguin said:
I'm assuming if I remove root the font will be back to normal? On some applications the font is way too big. (I assume due to the Instructions given)
Click to expand...
Click to collapse
Answer is yes.
Well, if anyone is willing to help. I removed SuperSU and tried to replace it with magisk but I can't because my internal storage isn't showing up and it ask for a password to decrypt.
Christhepenguin said:
Well, if anyone is willing to help. I removed SuperSU and tried to replace it with magisk but I can't because my internal storage isn't showing up and it ask for a password to decrypt.
Click to expand...
Click to collapse
Try format data to remove encryption.
Is anyone else experiencing this? I know there is an issue with zoom being forced on when the phone is rooted. However my phone is randomly switching back and forth between zoom and normal by itself and it's most obvious in both chrome and Gmail where the text being a different size when I open it up. I've tried the build prop fix but it's still switching between both modes.
Sumank490 said:
Try format data to remove encryption.
Click to expand...
Click to collapse
Yeah, it worked but got bootlooped and way thing lead to another. ROM got deleted and couldn't boot. Now I'm on Resurrection Remix. It did remove the encryption. Just couldn't boot.
Christhepenguin said:
Yeah, it worked but got bootlooped and way thing lead to another. ROM got deleted and couldn't boot. Now I'm on Resurrection Remix. It did remove the encryption. Just couldn't boot.
Click to expand...
Click to collapse
Tried Clean flash the ROM?
Sumank490 said:
Tried Clean flash the ROM?
Click to expand...
Click to collapse
Wasn't able to flash anything. Kept getting errors and eventually couldn't see any of my stuff again. It's all good though.

Categories

Resources