Hello World,
I have been on pac_quincyatt-nightly for a while now, my last version/update was pac_quincyatt-nightly-20140710 and had camera issues (resolved) but screen flickering, which XDA helped me and mentioned go into developer options and check HW Overlay box....having similar issue in latest update but not as bad. Flickers when using keyboard on any app, and wallpaper flickers.
1. how to keep HW overlay option permanently checked?
2. Anyone else have random freezing? (I leave roms/settings stock and close/exit unused apps constant)
sincerely,
The Noob
Pac_QuincyATT-Nightly-20140825
4.4.4RC-1
3.0.101-Cyanogenmod-g21fdfb2 (Monday 25 aug 14)
hehe figured out how to get developer options by accident honest truth...
si1entONE said:
Hello World,
I have been on pac_quincyatt-nightly for a while now, my last version/update was pac_quincyatt-nightly-20140710 and had camera issues (resolved) but screen flickering, which XDA helped me and mentioned go into developer options and check HW Overlay box....having similar issue in latest update but not as bad. Flickers when using keyboard on any app, and wallpaper flickers.
1. how to keep HW overlay option permanently checked?
2. Anyone else have random freezing? (I leave roms/settings stock and close/exit unused apps constant)
sincerely,
The Noob
Pac_QuincyATT-Nightly-20140825
4.4.4RC-1
3.0.101-Cyanogenmod-g21fdfb2 (Monday 25 aug 14)
hehe figured out how to get developer options by accident honest truth...
Click to expand...
Click to collapse
Download and flash this in recovery.. http://forum.xda-developers.com/showthread.php?t=2741733
Its an aroma installer with many options..one being disable he overlays..FYI..uber kernel never ran great for me with PAC nightlies. So I just stuck with original kernel during aroma install.
Don't forget to thank pollution.
Gil81 said:
Download and flash this in recovery.. http://forum.xda-developers.com/showthread.php?t=2741733
Its an aroma installer with many options..one being disable he overlays..FYI..uber kernel never ran great for me with PAC nightlies. So I just stuck with original kernel during aroma install.
Don't forget to thank pollution.
Click to expand...
Click to collapse
Thank you for the link, directions are simple a little to simple to be true. I installed what I wanted and even flashed cache as it was an option. A noob I am and now I have "the process com.android.phone has stopped" now I can not get rid of it. Going back into recovery and see what I can do. Last resort a whole device reflash and then install this patch piece by piece (I only selected what is needed 3 items).
si1entONE said:
Thank you for the link, directions are simple a little to simple to be true. I installed what I wanted and even flashed cache as it was an option. A noob I am and now I have "the process com.android.phone has stopped" now I can not get rid of it. Going back into recovery and see what I can do. Last resort a whole device reflash and then install this patch piece by piece (I only selected what is needed 3 items).
Click to expand...
Click to collapse
Reflash the ROM of choice..clean install ( wipe cache, dalvik cache, data, and system ) not internal or external sdcard.
Let ROM boot and chill for about ten minutes..then reboot recovery and flash pollution aroma. Don't flash the uber kernal..or any other. Just pick disable hw overlays and a boot animation, if you want. Then pick clear cache and dalvik and reboot. Should be good to go. Let me know how it goes.
si1entONE said:
Thank you for the link, directions are simple a little to simple to be true. I installed what I wanted and even flashed cache as it was an option. A noob I am and now I have "the process com.android.phone has stopped" now I can not get rid of it. Going back into recovery and see what I can do. Last resort a whole device reflash and then install this patch piece by piece (I only selected what is needed 3 items).
Click to expand...
Click to collapse
Gil is giving some solid advice. The only thing I might add is flashing the rom once by itself, then flash the rom again with the gapps. you can get 2 different results from 2 different flashes. It merely helps embed the rom in a bit better.
I rarely have issues with my cleanliness.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Related
Ive flashed back to the stock rom many many times after playing with roms here and wanting to go back. Almost every time before I did I would use a zip through clockwork that wipes everything and I did this time too but for some reason after odin installs the stock firmware successfully the phone reboots as usual then goes through its checks and it always fails to wipe data. So my biggest issue is the phone is unusuable until I can do this because it boots to the tmobile screen and then the screen goes black but the phone is on as the capacative keys at the bottom still light up when touched. Any help on this would be great but its looking like Im going to have to get another one.
pablo1215 said:
Ive flashed back to the stock rom many many times after playing with roms here and wanting to go back. Almost every time before I did I would use a zip through clockwork that wipes everything and I did this time too but for some reason after odin installs the stock firmware successfully the phone reboots as usual then goes through its checks and it always fails to wipe data. So my biggest issue is the phone is unusuable until I can do this because it boots to the tmobile screen and then the screen goes black but the phone is on as the capacative keys at the bottom still light up when touched. Any help on this would be great but its looking like Im going to have to get another one.
Click to expand...
Click to collapse
Are you sure you didn't get this after you installed the Voodoo lag fix??? You will have to read through this, but it looks like there's a fix in this thread.
http://forum.xda-developers.com/showthread.php?t=781456
Got to page three and read from there.
You are correct. I finally narrowed it down because I had done several updates through clockwork today but that was it. I am reading through forums to see about a fix, good thing I have other phones to play with too.
i got the same thing. did you figure it out?
menacetwosociety said:
i got the same thing. did you figure it out?
Click to expand...
Click to collapse
I hope someone answered you.
It messed up because I flashed the Vibrant Voodo Lag-fix w/OC-Optimized 2.6.29 Kernel - Beta4 9/19/2010
To disable, simply place a new folder in the "Voodoo" folder on your SDcard (the internal one) name it "disable lagfix" (e.g /sdcard/Voodoo/disable lagfix") no extention just that exact name and reboot. After your phone boots and you check that your /data partition is again RFS you can re-apply any other kernel you were using.
now redo the stock kernel and stock rom via odin and you should be fine.
yea im having same issue, how do you put the folder in if the phone doesn't show anything, just a black screen?!
I have same problem
How can i add the folder if the screen is black?
please help
thanks
update: http://forum.xda-developers.com/showpost.php?p=8698655&postcount=150
this fixed my problem
gottijr said:
I have same problem
How can i add the folder if the screen is black?
please help
thanks
update: http://forum.xda-developers.com/showpost.php?p=8698655&postcount=150
this fixed my problem
Click to expand...
Click to collapse
Thanks!!!!!!!!!!!!! This fixed my mess up too.
how can i do it with my vibrant turn black after booting ?
yep, this fixed me right up... once i realized i needed odin 1.3 to do it... but it did work and all is well...
thanx this worked for me as well
I have been trying since yesterday evening to install the CM9 nightly build. I've read through every single post in the thread ( http://forum.xda-developers.com/showthread.php?t=1778170 ) and I still can't seem to do it. I've flashed a few ROMs in the past with no issues, but for some reason this one is not making any sense. Maybe it's a good thing because I've learned so much and had my heart drop a few times thinking my phone is ruined. My issue seems to be with my version of CWM I guess? The first step of the instructions says to: 1. Install ClockworkMod Recovery for "quincyatt".
I don't understand this. I click on the link in the thread and the CWM file is a .img file, so I don't understand how to flash it to my phone. I've downloaded ROM manager (and paid for the premium version) and flashed the newest version through there. When I do that, it completely messes up CWM and keeps giving me errors anytime I try to install any ROM. It freezes on most things I do, keeps giving cache errors, etc. It seems like there's an issue with flashing the newest version through ROM manager. So how do I get CM9 on my phone? Do I need to update CWM someway? I currently have the version in the CWM thread ( http://forum.xda-developers.com/showthread.php?t=1584576 ) with the latest release 04-14. If someone can please give me an explanation for what I'm missing here, that would help greatly. I've been on this forum for a few years and always read and search. I actually just made my first post yesterday to help someone when I was encountering the same issue with CWM that they were and finally figured it out after hours of reading.
THANK YOU!
jaxjonesdrew32 said:
I have been trying since yesterday evening to install the CM9 nightly build. I've read through every single post in the thread ( http://forum.xda-developers.com/showthread.php?t=1778170 ) and I still can't seem to do it. I've flashed a few ROMs in the past with no issues, but for some reason this one is not making any sense. Maybe it's a good thing because I've learned so much and had my heart drop a few times thinking my phone is ruined. My issue seems to be with my version of CWM I guess? The first step of the instructions says to: 1. Install ClockworkMod Recovery for "quincyatt".
I don't understand this. I click on the link in the thread and the CWM file is a .img file, so I don't understand how to flash it to my phone. I've downloaded ROM manager (and paid for the premium version) and flashed the newest version through there. When I do that, it completely messes up CWM and keeps giving me errors anytime I try to install any ROM. It freezes on most things I do, keeps giving cache errors, etc. It seems like there's an issue with flashing the newest version through ROM manager. So how do I get CM9 on my phone? Do I need to update CWM someway? I currently have the version in the CWM thread ( http://forum.xda-developers.com/showthread.php?t=1584576 ) with the latest release 04-14. If someone can please give me an explanation for what I'm missing here, that would help greatly. I've been on this forum for a few years and always read and search. I actually just made my first post yesterday to help someone when I was encountering the same issue with CWM that they were and finally figured it out after hours of reading.
THANK YOU!
Click to expand...
Click to collapse
Try using TWRP recovery. I believe it flashes successfully.
http://forum.xda-developers.com/showthread.php?t=1647575
It is a zip not a. Img i just clicked it myself. Dont use the stock browser. Download dolphon browser hd. And click the link. The zip file you download is there. Flash it in cwm recovery. Easy easy stuff.
Download rom manager from the market. From within the app you can install CWM. This is what the post means.
Oops, sorry didn't read your whole post at first.
I had the same problem. What I did to fix it was purchase the touch recovery upgrade from within rom manager and that fixed my problems. If you have $2 to spare give it a shot. Good luck!
Sent from my SAMSUNG-SGH-I717 using xda premium
Thanks for the replies. I finally got it to work with TWRP. Now of course when it loads up everywhere I click I get an error saying 'Unfortunately, the process android.process.acore has stopped. :laugh: Here we go again.
Do what i said in my post above. Make sure to wipe data cache and dalvik cache in CWM recovery. Or dont listen and continue to enjoy the issues. Also dont use rom manager. Its more problems then its worth. Good luck
Thank you, I appreciate your help. Well I figured out how to get that error to stop. Now just need to figure out how to get all my contacts on here that were only saved on my SIM and I'll be good to go. This was a really good learning experience. I'm really liking TWRP
Do yourself a favor and put all contacts on your Gmail account. You can enter them on a PC quickly. Just be sure to always select your Gmail account to sync.
Another option is to use Titanium Back Up and restore the contacts once moving to a new ROM.
Sent from my SAMSUNG-SGH-I717 using xda premium
Big Dawg 23 said:
Do yourself a favor and put all contacts on your Gmail account. You can enter them on a PC quickly. Just be sure to always select your Gmail account to sync.
Another option is to use Titanium Back Up and restore the contacts once moving to a new ROM.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Thanks, I synced them all to Gmail. Much faster now! Finally got it all up and running. Just a question about using the 'touch key notification lights' Does this kill the battery? It seems like it stays on until you read your text, so if you get one while asleep those lights just stay on?
Use bln app from market and uncheck in system settings. You can set that to turn off whenever you'd like
froidroid said:
Use bln app from market and uncheck in system settings. You can set that to turn off whenever you'd like
Click to expand...
Click to collapse
awesome app!! bought the paid version. thanks man!
silver03wrx said:
It is a zip not a. Img i just clicked it myself.
Click to expand...
Click to collapse
Some of the links are .zip files and some are .img files.
This is the ONLY thread you guys will talk about the CrDroid ROM.
DONT post questions or whatever at the other leaked AOSP ROM thread else it'll create much confusion
So far annoyances thats been reported are:
• Random reboots (at least for some people)
• Auto-brightness
• Underclocked CPU
• Not working HDR & Panaroma (solved with workaround)
DOWNLOAD LINK FOR CRDROID ROM
http://pan.baidu.com/s/1bnzqPBL
Reserved
Via the Internet
Regarding Random Reboots !
I have been using the ROM since yesterday though i have yet not observed a single reboot . I have tried following things as suggested in AOSP thread however it does not give me a reboot. Auto Brightness is the only lingering issue i faced !
Any pointers to reproduce the reboots ?
M3gAtR0N said:
I have been using the ROM since yesterday though i have yet not observed a single reboot . I have tried following things as suggested in AOSP thread however it does not give me a reboot. Auto Brightness is the only lingering issue i faced !
Any pointers to reproduce the reboots ?
Click to expand...
Click to collapse
LKspro said:
after u have the first reboot, cover the upper sensors and touch the screen while it is off. Then the screen should freeze and rebbot after a while
Click to expand...
Click to collapse
This is from @LKspro
Via the Internet
TiTAN-O-One said:
This is from @LKspro
Via the Internet
Click to expand...
Click to collapse
I have reproduced the same however it did not cause a reboot for me ! Thats why asked !! Is this the encountered random reboot occurrence ?? Or do we have something else too ?
Good rom lots of settings but useless... always reboot..
M3gAtR0N said:
I have reproduced the same however it did not cause a reboot for me ! Thats why asked !! Is this the encountered random reboot occurrence ?? Or do we have something else too ?
Click to expand...
Click to collapse
Yeah, first time it happens random, but if it once happens to you, then you will be able to reproduce it.
Anyone try to use the boot.img from leaked AOSP ROM and put I to this ROM? If yes do the random reboot still happening?
wai10691 said:
Anyone try to use the boot.img from leaked AOSP ROM and put I to this ROM? If yes do the random reboot still happening?
Click to expand...
Click to collapse
I can try this but not sure of the exact steps to follow... I like the CM rom very much.. blazing fast with ART, but random reboots quite often. I am now using wakelock to control the reboots. if you think changing the boot.img can help, i will try it out. lemme know what to do for tht
krispuniq said:
I can try this but not sure of the exact steps to follow... I like the CM rom very much.. blazing fast with ART, but random reboots quite often. I am now using wakelock to control the reboots. if you think changing the boot.img can help, i will try it out. lemme know what to do for tht
Click to expand...
Click to collapse
Before flashing the ROM zip simply replace the boot.img in the crdroid with the one from aosp.
I can try this later but I'm outside now
wai10691 said:
Before flashing the ROM zip simply replace the boot.img in the crdroid with the one from aosp.
I can try this later but I'm outside now
Click to expand...
Click to collapse
Done... Flashing went ok but after booting all my apps are gone (I didnt do a clean wipe while flashing.. only wiped dalvik)
The apps are gone anyway.. so i went back to recovery and did another clean flash.. Reboot the phone, but no mobile network. Unable to latch on to network even manually.. so may be there is something missing in the boot.img ?
Back key
Anyone can confirm back key in this rom didnt behave as it should after deleting pre-install files such as baidu services apps
edit 1 - looks like it has been warned by the dev as do not delete keyboard input method or else back button wont work..
Where is the link to the ROM. I'd update OP. Also, is there any bugs with the ROM? Or is it working like AOSP?
Via the Internet
Download link
http://pan.baidu.com/s/1bnzqPBL
SAC23 PORTED MOAR N3
tdunham & rompnit
… Proudly Present …
[M]other [O]f [A]ll [R]oms ..aka.. MOAR
Take control of your phone
OP HOST LINK
MY MIRROR HOST LINK # 1
MY ANDROID FILE HOST # 2
MD5 74ad7725fa79dabfb7853fce52b614e1
WHATS BROKEN
CAMERA S5
GUYS MAKE SURE IF IT DOESENT BOOT JUST REMOVE BATTERY AND REBOOT U MAY HAVE TO DO IT 2 TIMES BUT IT WILL BOOT[/SIZE]
Click to expand...
Click to collapse
This is the first of many guides I will be posting and keeping up with.
It will be utilized for Q&A FAQ and HOW TO so we can keep the development thread for development purposes.
Post your questions and Myself or other knowledgeable users of Sac23 ROMS will answer as quickly as possible.
So ......
FAQ:
what do i do if its not booting on start up A- pull battery then restart.(IF YOU HAVE A REMOVABLE BATTERY)
after booting im getting a services have stopped wait or close A- pull the battery and restart.(IF YOU HAVE A REMOVABLE BATTERY)
the tweaks open then close help? A- need to deny super user for it then go in and change what u want then re enable superuser for it
how to install
install like u would any rom then wait for 2 min ( if wont boot )
pull battery and restart then you'll see optimizing apk's count down.(IF YOU HAVE A REMOVABLE BATTERY)
***Guys This Is A Port So remember it will have small glitches here and there but all in all should be stable ***
For starters HOW TO INSTALL a ROM by SAC23
Installing with TWRP (View All Supported Devices>>> Find TWRP for your device):
Philz can be used and I will post instructions for it later https://www.mediafire.com/folder/qc3z1c59s8g03/PHILZ
This assumes that you ALREADY have TWRP Recovery installed on your phone and you know how to use it.
Download the ROM of choice...move it onto the EXT SD CARD.
VERY IMPORTANT>>> Move all music, pics, important data from internal storage to the ext SD card and/or to your pc, etc. because during this process, the internal will be completely erased.
Recommended Method to Flash SACS Custom ROMS using TWRP
Boot into TWRP
Select Wipe > Advanced Wipe
Select Dalvik, System, Data, Internal Storage, and Cache. Swipe to Wipe (do this THREE TIMES)
Go back to previous Advanced Wipe screen.
Select Format Data, Type YES, Press GO. (do this THREE TIMES)
Go back to previous Advanced Wipe screen.
Swipe to Factory Reset. (do this THREE TIMES)
Go back to MAIN menu and STOP HERE !!!!! READ NEXT STEP CAREFULLY....
[*]Select REBOOT INTO RECOVERY mode and Swipe to Install Super User. DO NOT REBOOT INTO SYSTEM!
[*]AFTER THE PHONE REBOOTS INTO RECOVERY:
NOW proceed with installing The ROM
Select Install Zip, Drill down to Sac23's Rom you want to flash, and Swipe to install.
Follow on screen instructions (if there are any).
When prompted, REBOOT SYSTEM.
THE FIRST BOOT WILL TAKE A MINIMUM OF 20 MINUTES..... SOME DEVICES EVEN LONGER...
.
.
HAVE PATIENCE
When the Home Screen appears and it is obvious that the install has completed, allow the phone to settle for another 10 minutes BEFORE you begin setting up your personal preferences and accounts.
If everything seems normal, set your phone up and profit.
IF IT WON'T BOOT....(IF YOU HAVE A REMOVABLE BATTERY)...try pulling battery and replacing battery then restart phone and you should see "Android Updating"
After setting up your personal info and you are now ready, the first thing you should always do after flashing any ROM is to go to settings, system updates, and refresh/update your PRL & PROFILE then reboot the phone. Second thing is go to settings, more networks, mobile networks, network mode, and select LTE/CDMA.
saved 1
New Recovery update for NOTE 3
bigbiff said:
Can you test http://techerrata.com/bigbiff/openrecovery-twrp-2.8.5.0-hltespr.img.tar
If it works well I will push it out.
Click to expand...
Click to collapse
wormy987123 said:
Booted up made back up and was able to restore. Anything else you want tested?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
saved 2
For future use
saved 3
For future use
saved 4
For future use
saved 5
For future use
Cannot install as OP describes.
Only way I've found is to flash @sac23 TWLP 5.0 V2 then dirty flash MOAR LP.
Biggest issue I've found, to make this not a daily driver is when calling, other people on line cannot hear a word you're saying.
Back to N4 port.
Nickitt said:
Cannot install as OP describes.
Only way I've found is to flash @sac23 TWLP 5.0 V2 then dirty flash MOAR LP.
Biggest issue I've found, to make this not a daily driver is when calling, other people on line cannot hear a word you're saying.
Back to N4 port.
Click to expand...
Click to collapse
@Nickitt
We are working in the incall issue with @sac23
Just out of curiosity. With this being an S5 port and if anyone remembers the original S5 port. Anyone having issues with the mic. and sound issues. Have you guys messed with any of the sound options in mod control? Like normal, loud, extreme sound mods. Not sure if @sac changed them, if he did not then when trying them on the note 3 it will break the mic. because they are meant for the S5. Just asking. I have been running this since this afternoon and have had many calls today and no issues here. I have not messed with the sound mods.
fsunoles101 said:
Just out of curiosity. With this being an S5 port and if anyone remembers the original S5 port. Anyone having issues with the mic. and sound issues. Have you guys messed with any of the sound options in mod control? Like normal, loud, extreme sound mods. Not sure if @sac changed them, if he did not then when trying them on the note 3 it will break the mic. because they are meant for the S5. Just asking. I have been running this since this afternoon and have had many calls today and no issues here. I have not messed with the sound mods.
Click to expand...
Click to collapse
You would be the first person that has flashed this Rom to have working sound/mic in calls. Yes, people can receive and call perfectly fine but when you talk, no one can hear you.
I've flashed this Rom 3 times now differently and messed with some system applications in hopes of fixing this issue myself but to no extent.
If you can actually talk to the other person please tell us how you went about installing. Thanks.
sac23 said:
incoming sound fix test v1
let me know guys
http://www.mediafire.com/download/3ez7uil20zktcjz/moar_incoming_call_sound_fix_test.zip
Click to expand...
Click to collapse
Sent from my SM-G900P
Please try this test for in call hearing loss and report back
rlmiller said:
Sent from my SM-G900P
Please try this test for in call hearing loss and report back
Click to expand...
Click to collapse
Does work for me. Perfect, thank you.
When using automatic brightness it seems at though it goes all the way dim so you'll have to un-check auto and set it to your liking.
When disabling the s finder and quick connect in MOAR settings, it is still there when on the lock screen and you pull the notification bar down.
When pulling s-pen out, you cannot use pen on screen doesn't recognize you're touching the screen with the pen.
It realizes you've pulled it out from the slot but that's about it.
Has anyone have bluetooth working? I haven't been able to get to work.
Jose Reyes said:
Has anyone have bluetooth working? I haven't been able to get to work.
Click to expand...
Click to collapse
Here you go dude. Go here. Download V2 and flash in recovery. Should take care of your Bluetooth issues.
http://forum.xda-developers.com/showthread.php?t=2938607
Anyones phone crashing? Its been happening several times a day. It says something like security watchdog bit.
Sent from my SM-G900P using XDA Free mobile app
fsunoles101 said:
Here you go dude. Go here. Download V2 and flash in recovery. Should take care of your Bluetooth issues.
http://forum.xda-developers.com/showthread.php?t=2938607
Click to expand...
Click to collapse
This patch did not work on my device... thanks Went back to Sac's Note 4 ROM....
Edit: I reflashed the ROM waited until it was completly setup then rebooted and flash this patch and it does work
Working?? It is for me.
Ok so this is what I did, None of this is my work, I took no part in any of this development, I think I just got lucky.
Wipe
Wipe
Wipe
Installed Sacs ported rom V2, no reboot straight back into Recovery
Installed Sacs Moar Port, no reboot straight back into Recovery
Installed Sacs Moar Port fix for the mic problem
Wiped cache and davlik rebooted system
Went thru the entire setup made sure things were good and made a backup
Then I dirty flashed this right over....
http://forum.xda-developers.com/gal...-tw-note-4-port-5-0-1-darklord-rom-1-t3017604
This is the link for the 1.4 file https://mega.co.nz/#!XYw0TArb!7DoNDNHAK-1H0RBcyUMR0qPPtdarKCtR6uA7QTKeiDw
It kept just enough of Sacs rom to work... bluetooth works, data works, S pen works, Camera works, Lte works......
It is no longer a MOAR Rom its a Note 4 Lollipop port with alot of worknig stuff.
I'm about to do it in reverse and see what happens.. wish me luck.
rancherochido said:
Ok so this is what I did, None of this is my work, I took no part in any of this development, I think I just got lucky.
Wipe
Wipe
Wipe
Installed Sacs ported rom V2, no reboot straight back into Recovery
Installed Sacs Moar Port, no reboot straight back into Recovery
Installed Sacs Moar Port fix for the mic problem
Wiped cache and davlik rebooted system
Went thru the entire setup made sure things were good and made a backup
Then I dirty flashed this right over....
http://forum.xda-developers.com/gal...-tw-note-4-port-5-0-1-darklord-rom-1-t3017604
This is the link for the 1.4 file https://mega.co.nz/#!XYw0TArb!7DoNDNHAK-1H0RBcyUMR0qPPtdarKCtR6uA7QTKeiDw
It kept just enough of Sacs rom to work... bluetooth works, data works, S pen works, Camera works, Lte works......
It is no longer a MOAR Rom its a Note 4 Lollipop port with alot of worknig stuff.
I'm about to do it in reverse and see what happens.. wish me luck.
Click to expand...
Click to collapse
Good luck brother let us know how it goes
fsunoles101 said:
Here you go dude. Go here. Download V2 and flash in recovery. Should take care of your Bluetooth issues.
http://forum.xda-developers.com/showthread.php?t=2938607
Click to expand...
Click to collapse
I extracted the missing files from this zip and placed them in the appropriate folders, fixed permissions, rebooted and bluetooth works!
Thanks for the great find!
hey guys can i go to back to a mja modem from nh7 ?
Hi,
After successful rooting and rebooting, i have hit "Cleanup to switch to another superuser app" and now, cannot boot. Phone stays with Mi logo and constanty loops with screen blink.
Tried to go to recovery mode, reinstall SuperSU, clean cache, but no luck.
Kindly asking for help.
Flash fastboot rom and root again.
tried, didnt help.
TWRP loads ok. SR3-SuperSU-v2.79 also installs, cache wiped/dalvik, all same
at4500 said:
tried, didnt help.
TWRP loads ok. SR3-SuperSU-v2.79 also installs, cache wiped/dalvik, all same
Click to expand...
Click to collapse
Wipe data, cache, and dalvik, and reinstall your ROM. You will lose all your data, downloaded apps, and settings (I hope you made backups of them), but you will have your phone back.
at4500 said:
Hi,
After successful rooting and rebooting, i have hit "Cleanup to switch to another superuser app" and now, cannot boot. Phone stays with Mi logo and constanty loops with screen blink.
Tried to go to recovery mode, reinstall SuperSU, clean cache, but no luck.
Kindly asking for help.
Click to expand...
Click to collapse
Reinstall rom as DarthJabba said and also start using Magisk instead of SuperSu, since its more compatible and stable.
MyNameIsRage said:
Reinstall rom as DarthJabba said and also start using Magisk instead of SuperSu, since its more compatible and stable.
Click to expand...
Click to collapse
Thanks, this made my day, finally decided to opt for reflashing.
Here is a good vid guide for ones who do it first time in life:
u tube dot com slash watch?v=mfXd5E-Ix6w
Will look for magisk now. Thanks again. Phone is usable now.
at4500 said:
Thanks, this made my day, finally decided to opt for reflashing.
Here is a good vid guide for ones who do it first time in life:
u tube dot com slash watch?v=mfXd5E-Ix6w
Will look for magisk now. Thanks again. Phone is usable now.
Click to expand...
Click to collapse
Good news. You probably only needed to wipe the data partition - but you might as well start afresh.
BTW, I have been using supersu for a long time, without any problems. So I would very much doubt whether rooting via supersu was the cause of the problem. I suspect that the problem might have been caused by "Cleanup to switch to another superuser app". I have not done that in years, and I am not sure why anyone would want to do it now.
There is no harm trying magisk, but I prefer supersu myself.
DarthJabba9 said:
.. I suspect that the problem might have been caused by "Cleanup to switch to another superuser app". ..
Click to expand...
Click to collapse
Right, this is (silly of me) exactly what i did.