Related
I have tried all of the ICS roms, and always gets stuck at the same spot. Wi-fi is turning on.
It worked on the Revolver 4, but I wanted to try another one. Did a super wipe, and bam. Nothing after that..
Any thing I might be able to try?
Nandroid restore, if that won't work nvflash?
you mean use NVflash to do the rom install vs the recovery?
I made a topic about this, check my post (not able to give you a link right now sorry)
I also need help with this. I am trying to come from CM9 cornerstone build back to revolver. I have done a couple restores and I still get no WIFI. Anybody have anymore info on this?
Have a look at this : http://forum.xda-developers.com/showthread.php?t=1530612
You can try this:
- Turn off wifi
- rename the file /data/misc/wifi/wpa_supplicant.conf to wpa_supplicant.old
- reboot
- try wifi again to see if it works
**note
This might cause the tablet to forget any previously saved networks.
I have tried Outpoxs' method in varies combinations with no success also I have tired your method a.mcdear and also with no success. Mine is still stuck on Turing WI-Fi on... The one thing with outpox method there might have been something I was doing wrong.
This is how I fixed my tablet after 15 hours of trying everything. I downloaded the ota rooted full version of ics and performed a full wipe then made sure it booted into that rom with wifi working then proceeded to flash my revolver backup with no problems. Hope that helps.
Similar WiFi issue - still stuck
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
I've have a rooted TF101 B50 and most ROM's that I have tried seem to fail at this point as well. However, I did notice that when I flashed my first ROM (AOKP) it has the same stock kernel. So I tried another one. This time was Revolution 4. It seemed to work out just fine because I belive it has the stock kernel. Next I moved onto a CM10 Eruoskank ROM. It too had the problem of the AOKP ROM in that after I flashed it, the stock kernel was still present, presumably left over from the Revolution 4 ROM. I am now on Android Revolution HD 3.5.0 and it seems to work fine so I am sticking with it for the time being.
I beleive something in the flashing script of the ROM or the recovery program itself is not flashing the /boot partition properly. I am not a developer nor do I have an in depth knowledge of the inner workings of Android...but this is just a guess. I hope there is a way to flash just a kernel in the /boot partition from these individual ROMs. That would be nice.
If can access recovery then do a full wipe(system, cache and dalvik) and install the ROM again... that should do the trick... you might wanna try some other kernel also... there few kernels for ICS in the forum look for them and flash them via recovery...
Sent from my Transformer TF101 using xda app-developers app
It seems as thought someone else is on the same track as I am.
http://forum.xda-developers.com/showpost.php?p=29447134&postcount=8
rstry this:
take unit out of dock if you use one. restore via cwm if u can, to 3.01 firmware, honeycomb. wipe all cache, data, etc prior to flash.
DO NOT SIGN INTO GOOGLE ACCOUNT.
Turn tablet completely off following boot. Cold boot back on. Grab latest official firmware off Asus website, xx.27
Install via CWM, and again wipe ALL.
Boot into system again, and cold boot back on. Asus should prompt you with 300mB update now, which differs from the official .27,but had same filename...
I found this bug/glitch a few hours ago... Somehow downgrading to HC and back to stock triggers this unknown update...
See if you can reproduce please. I also saved the firmwares to sdcard external.
The various ROMs require a supporting kernel. I would try obtaining the correct kernel for the ROM you want and then flash them both at the same time from recovery.
Resolved - for me
From replies here and other research, it became clear to me that I should reflash my transformer back to stock (NVFLASH down to the metal). Every other ROM would show the stuck WiFi issue or (worse) would get into a boot loop.
This was something of a problem, because my volume up button was broken and I couldn't enter APX mode. I finally managed a workaround for that (see http://forum.xda-developers.com/showthread.php?t=1890236) and then used EasyFlasher to restore the Asus firmware. Now the WiFi works fine and all is well again.
So, as a last resort - scrub and start over.
Cheers!
--Roger
regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse
regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse
I also have the same issue. Bought the eee pad transformer with a cracked screen; touch screen did not work. I replaced it and everything works great! except for Wi-Fi =\ Any help would be greatly appreciated!
You should really start your own thread. That being said, first thing to try is to back up all your data and wipe it to factory using EasyFlasher. If the problem persists after a stock firmware flash, then it's likely a hardware issue. If it's resolved, then it was a rom/software issue.
regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse
Im 99% sure your problem is that you haven't got the right kernel for the rom your using, this is the usual outcome - wifi not working/ turning on. i don't think nandroid backs up the kernel so your basically restoring stock ICS rom with cm9s kernel. Try find the related kernel to rom your currently on. As for your rom failed flashing, you might be using a very old recovery try updating to the newest twrp recovery. Better yet join the dark side and move up to Jelly Bean, makes the tf101 a whole new device.
Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.
I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk
I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA
Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.
Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.
I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though
I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).
I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.
Hello, i recently bought an asus transformer and ive rooted it and installed a custom rom well today i had problems with it bootlooping into recovery well i fixed that now for some reason my wifi wont turn on it just says turning on wifi and doesnt do anything so what im wanting to do is fastory restore and unroot the device so i can start fresh can anyone point me into the right direction to do so? Thanks.
-Brad
You can Nvflash a stock ROM, but Guevor's kernel will also fix your wifi issues. Don't use ROM manager, it causes bootloops. Also try a different ROM (which did you flash), and you must get the CM9/AOKP based kernel to get wifi to work on an AOSP ROM. (See megatron version in guevor's thread)
Well, it won't let me post in the official thread so I'm forced to put it here.
I recently installed the Team EOS Jelly Bean nightly (Stingray MZ602) their gapps, and reflashed the ICS radio as recommended using Rogue Recovery. Things have been working well except the WiFi. It tends to cut out randomly. It will be connected yet not transmit or receive. I have to turn it off and on frequently in order for it to work. No, it's not the router or my network. I am hoping for a solution other than going back to ICS.
First thing I would do is to full wipe and format /system
And flash twrp recovery that is advised as stable flasher.
Then redownload the ROM and gapps and make sure check sum is OK,
Then flash and reboot.
This way, you would id the source of your issue, ROM bug or recovery flasher? Cuz I know other guys face no issues like yours with twrp. Worth to try. Good luck.
The twrp page hasn't been updated since April and the project itself hasn't been updated since October of 2011. How can you be sure that it'll work with the radio zip better than Rogue? Or even the Team EOS JB build?
Twrp is advised by team eos. They asked to use it. And you need twrp for Xoom,
http://forum.xda-developers.com/showthread.php?p=28988754
Installation method 4 thru goo manager.
I remember one of the stingray users had an issue with the radio flashing and it went great with twrp.
Good luck.
Didn't work. I still have to reset the WiFi every 5 minutes or so. Also, the twrp recovery takes a LOT longer to load than Rogue's. Almost thought it wasn't going to work for a bit until the 'curtain' finally rose.
Over 24-hour bump...
Just put on EOS 138 and reflashed the radios after going back to Rogue. Still radio issues with WiFi. Found some other threads detailing that Jelly Bean in general seems to have WiFi issues. As much as I hate it, I'm starting to think that I will have to 1) revert to ICS, 2) wait for an updated radio file, or 3) deal with it.
Wifi Issue
First Aid Computing said:
Just put on EOS 138 and reflashed the radios after going back to Rogue. Still radio issues with WiFi. Found some other threads detailing that Jelly Bean in general seems to have WiFi issues. As much as I hate it, I'm starting to think that I will have to 1) revert to ICS, 2) wait for an updated radio file, or 3) deal with it.
Click to expand...
Click to collapse
I always have that problem with their roms. Flash a kernel, thats always helped my situation.
Also I have zero issues with wifi on JB with my GNexus, N7, Infuse and Atrix. Its not JB, at least not as far as I have seen. Granted none are stock.
Which kernel would you recommend?
Also, until JB I have not had this issue with EOS builds.
issues
First Aid Computing said:
Which kernel would you recommend?
Also, until JB I have not had this issue with EOS builds.
Click to expand...
Click to collapse
I flashed Eos 138 last night (was on CNA), without doing the radios, nor a kernel, and didn’t have any problems.
The Eos forum states that it has the kernel baked into the rom, so flashing the kernel is likely redundant.
However, for ****s and giggles I tried flashing the Eos 3.0.15 kernel and it would not flash, but I was able to flash the Eos 3.0.5 kernel instead and it took. I haven’t seen any issues, either before or after the kernel flash, so perhaps you should try re-flashing the entire rom sans radios and see what happens.
One of the nice things about the Xoom is its pretty easy to fix anything you could do to it via ADB and fastboot, so try some different combos, or start all the way over (from stock). If that doesn’t help, try a different JB rom and see if you get the same problem.
Also make sure you are flashing the right rom, there are several variants for the Xoom - 3G, 4G, Euro, and of course wifi only.
Just flashed CM10 and the non-EOS gapps without flashing radios. Running on WiFi for about 20 minutes so far without issue. Will try more testing later today.
EOS 4 & Kindle
Thanks EOS for 4.2.1! Feels like most things are working...except Kindle locks up on start-up. Just sayin'....
Hi all,
I was given the TF700 by my grandma as she no longer used it and I've been trying to solve the issue of it being so sluggish etc, so I've managed to unlock the bootloader, flash a custom ROM however, since I tried to flash the KatKiss ROM, the WiFi refuses to work. Every ROM after that has had no WiFi either. I tried to flash back to stock, as was suggested to see if that would fix the WiFi issues, to see if that would help, however now it won't boot past the boot animation - no matter what ROM I try and use.
I'm refusing to give up on this guy as it has the potential to be an amazing tablet... Y'know, when I can actually get it to turn on.
I've checked and I'm on the latest bootloader (US_epad-10.6.1.14.10-20130601 - I'm hoping that's right?)
Does anybody have any suggestions? I can successfully boot into Kang TWRP and flash things via recovery, but I can't get any ROM to boot past the boot-animation. I don't want to get rid of the tablet, but I'm unsure of what to try next. As I can still get it powered on and into bootloader/TWRP, I figure there has to be some kind of hope. Have I missed off any details that may be needed?
If anyone could help me out, I'd be eternally grateful!
reterosexual said:
Hi all,
I was given the TF700 by my grandma as she no longer used it and I've been trying to solve the issue of it being so sluggish etc, so I've managed to unlock the bootloader, flash a custom ROM however, since I tried to flash the KatKiss ROM, the WiFi refuses to work. Every ROM after that has had no WiFi either. I tried to flash back to stock, as was suggested to see if that would fix the WiFi issues, to see if that would help, however now it won't boot past the boot animation - no matter what ROM I try and use.
I'm refusing to give up on this guy as it has the potential to be an amazing tablet... Y'know, when I can actually get it to turn on.
I've checked and I'm on the latest bootloader (US_epad-10.6.1.14.10-20130601 - I'm hoping that's right?)
Does anybody have any suggestions? I can successfully boot into Kang TWRP and flash things via recovery, but I can't get any ROM to boot past the boot-animation. I don't want to get rid of the tablet, but I'm unsure of what to try next. As I can still get it powered on and into bootloader/TWRP, I figure there has to be some kind of hope. Have I missed off any details that may be needed?
If anyone could help me out, I'd be eternally grateful!
Click to expand...
Click to collapse
It sounds as if you are not formatting properly between flashing roms.
Try that first: Wipe > Format data > type yes
let it finish, the process takes a good hour. Then convert /data to f2fs
https://forum.xda-developers.com/tr.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Flash the rom and gapps.
I bet it'll boot this time
berndblb said:
It sounds as if you are not formatting properly between flashing roms.
Try that first: Wipe > Format data > type yes
let it finish, the process takes a good hour. Then convert /data to f2fs
https://forum.xda-developers.com/tr.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Flash the rom and gapps.
I bet it'll boot this time
Click to expand...
Click to collapse
Thank you so much! I'd been formatting but maybe not properly.
I'll give it a go once it has some charge in it - it's been trying to boot for about 7 or so hours now. I'll report back with anything if it helps.
So, I've managed to get the tablet to boot - but I'm still stuck with no working WiFi. It just greys out and says disabled. Bluetooth seems to work, but, I can't even connect to my phone to use it's data connection via Bluetooth tethering. I managed to get it to boot on KatKiss 7.1 - any ideas on the WiFi issue? Is there a flashable zip to fix WiFi drivers?
reterosexual said:
So, I've managed to get the tablet to boot - but I'm still stuck with no working WiFi. It just greys out and says disabled. Bluetooth seems to work, but, I can't even connect to my phone to use it's data connection via Bluetooth tethering. I managed to get it to boot on KatKiss 7.1 - any ideas on the WiFi issue? Is there a flashable zip to fix WiFi drivers?
Click to expand...
Click to collapse
Nope, the rom should have everything you need. Don't know man - this is pretty unusual. You probably should flash it back to stock to have a point of reference.
If wifi still won't work on stock it's gotta be hardware.
Flash the stock blob in fastboot and then start from scratch:
https://forum.xda-developers.com/showpost.php?p=72801448&postcount=8
berndblb said:
Nope, the rom should have everything you need. Don't know man - this is pretty unusual. You probably should flash it back to stock to have a point of reference.
If wifi still won't work on stock it's gotta be hardware.
Flash the stock blob in fastboot and then start from scratch:
https://forum.xda-developers.com/showpost.php?p=72801448&postcount=8
Click to expand...
Click to collapse
Thanks for the link, but the official ASUS link in the post you've linked to is dead :/ I'll have a look after work tonight and see if I can find it anywhere else and whether I can get it working or not!
https://www.asus.com/us/supportonly/ASUS Transformer Pad Infinity TF700T/HelpDesk_BIOS/
I tried all of the above steps and re-flashed KatKiss to find that the WiFi still did not want to work, which resulted in not being able to get past the setup wizard. I'm not sure what to try next, but at least it was worth a shot. Thank you for your help!
Well - did wifi work on stock?
You know about this bug right? From the OP:
Note that current gapps setup wizard will crash as it is not fully compatible with android 7.1.2 (KatKiss >= 022)
unless you turn on wifi manually after the language selection in the initial setup.
(if you don't have a dock, use the extra wifi button in the navbar)
berndblb said:
Well - did wifi work on stock?
You know about this bug right? From the OP:
Note that current gapps setup wizard will crash as it is not fully compatible with android 7.1.2 (KatKiss >= 022)
unless you turn on wifi manually after the language selection in the initial setup.
(if you don't have a dock, use the extra wifi button in the navbar)
Click to expand...
Click to collapse
Just seen this! Yeah, the WiFi worked fine on stock, but any custom ROM I tried had the same issue, so I'm not 100% sure what caused it. I sold the tab on after flashing it back to stock, though.
Thank you for your help though!