Related
I installed a tmobile m919 s4 rom Wicked v8 to be exact.. onto my att s4 using safestrap recovery
The rom installed fine with aroma installer everything works fine besides wifi it wont toggle on
I have tried multiple m919 kernels, ive even factory reset wipe cache system and dalvic and re installed rom.
The wifi will not toggle on at all.
i know we can flash other carriers roms just fine cause the rom flashes fine with lte data and shows No hiccups besides the wifi toggle issue?
I have also asked the same question on the i337 forum hoping to cross reference the issue on both sides..
i know its mentioned when using a tmobile rom on the att variant a specific kernel must be flashed because of the locked boot loader, but i wasnt sure if they mean use an att kernel or tmobile kernel on the att s4
The roms flash fine with working lte data and boots just fine using the kernel thats set up into the aroma installer ..but the wifi toggle on/off issue is that a issue with Wicked rom v 8 ?
I know someone reading knows where the issue and fix must be ?
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
iamdofus said:
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Do you by chance have a refurbished s2?
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
es0tericcha0s said:
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
Click to expand...
Click to collapse
OK thanks for reply, I have one more solution give me. Some time I will give try that it worked for me.
Sent from my SGH-T989 using XDA Premium 4 mobile app
es0tericcha0s said:
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Click to expand...
Click to collapse
ok lets stat it with this
1) download both the scripts of infamous wipe cache and infamous super wipe.
2) format your both SD card with PC (FAT32)
2) put both these wipe files and and your rom file ( i prefer try slimbean rom first)
3) Now in twrp 2.6.0.0- follow the steps
i) format your phone with twrp options
ii) again format your phone with infamous super file. (by going in to INSTALL ZIP file option in TWRP)
iii) than format with infamouse cache file (by going in to INSTALL ZIP file option in TWRP)
iv) install your rom and compatiable GAPPS zip file.
v) after installing or somewhere between procedure if twrp says something about supersu birnaries are not correct than click on DO . NOT FIX
vi) again format infamouse cache wipe.
vii) now FINALLY reboot the rom.
it should work, and it worked for me. if u sucessfully run the rom than you can eailsy run all the AOSP roms in this forum. Again If you try this please do tell me what happend.
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
es0tericcha0s said:
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
Click to expand...
Click to collapse
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
UltimaniumX said:
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
Click to expand...
Click to collapse
Yep, very much phone specific. Used same recovery, same rom zip and gapps off the same external SD card, to be certain. That one updated just like every other S2 I've done. And it's the Tmo version. The At&t models are i777 S2 or i727 S2 Skyrocket. The i9100 is international and has a physical home button. But the phone was not modified at all. No root, custom recovery, etc. I was only able to resolve it by first starting with an AOSP 4.1.2 rom and working my way up to 4.4. One of the weirder issues I've come across.
es0tericcha0s said:
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
Click to expand...
Click to collapse
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
tpag02 said:
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
Click to expand...
Click to collapse
Sorry, I don't pay attention to the notifications on XDA very often. I don't usually browse the S2 forums unless needed because I have an N5, but anyway... The 4.1.2 rom you used, was it TW or AOSP type? I used 2.6.0 to wipe everything, then used cache and superwipe zips then 4.1.2 AOSP type rom then cache wipe zip again then after that booted, I was able to go back to 2.6.1 and flash a 4.3 via wiping, wipe zips, installing rom then cache wipe again. After that, repeated with a KK rom and now it loads roms just like it should. If you want more precise help, feel free to hit me up on Hangouts with my username: es0tericcha0s. Good luck! I know how frustrating it can be when it gets a little out of whack like this...
I'm in the same boat
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
DennyTek said:
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
Click to expand...
Click to collapse
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
TMO 4.1.2
es0tericcha0s said:
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
Click to expand...
Click to collapse
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
yep
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
ya, well at least I am anyways
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I had tried with and without and did not make any difference.
DennyTek said:
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Click to expand...
Click to collapse
I just started working on a VZW S3 on T-Mobile service that has this issue. Happens on stock VZW 4.1.2, stock T-Mobile 4.1.2 rom, custom 4.1.2 T-Mobile rom, and stable CM 10.2. Weirdest thing... full wipes including /system inbetween each flash. Changed the modem too. Nothing helps. Pretty sure it's a bad board at this stage.
Cool beans, 0! Having this exact problem, will try your method for my s2, btw which aosp 4.1.2 did u use? Can I get a link? Thanks been having the problem for a few months now and just gave up haha, been super thirsty for that beanstalk kk build
One last thing can u also provide a link to the 4.3 that u used? I really want it to work and want to follow what u did to the , megabyte
Hi Everyone, I'm actually confused, I've downloaded Ditto Note 3 V3.1.1 (http://forum.xda-developers.com/showthread.php?t=2504016) and i want to flash it. It says that it needs bootloader 4.3. I just want to ask, is this with the knox security thing? coz i wanna get rid of that and ofcourse use the phone normally. Any suggestions guys to properly flash DN3 V3.1.1 without knox and properly use it without wifi issues. Thanks in advanced guys.. By the way my phone is Samsung Galaxy Note II (GT-N7105) LTE International
jasonowitzki said:
Hi Everyone, I'm actually confused, I've downloaded Ditto Note 3 V3.1.1 (http://forum.xda-developers.com/showthread.php?t=2504016) and i want to flash it. It says that it needs bootloader 4.3. I just want to ask, is this with the knox security thing? coz i wanna get rid of that and ofcourse use the phone normally. Any suggestions guys to properly flash DN3 V3.1.1 without knox and properly use it without wifi issues. Thanks in advanced guys..
Click to expand...
Click to collapse
Just stay with your current bootloader. If Wi-Fi doesn't work after a couple of reboots, install Dr Ketan's Wi-Fi fix and see if it works.
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. replies with quotes will be replied to faster.
Irwenzhao said:
Just stay with your current bootloader. If Wi-Fi doesn't work after a couple of reboots, install Dr Ketan's Wi-Fi fix and see if it works.
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. replies with quotes will be replied to faster.
Click to expand...
Click to collapse
Just to make sure.. there is no knox thing? so ill just do the normal flash and if wifi wont work,, ill just flash dr ketan's wifi fix? Thanks oopppsss.. i forgot.. im coming from 4.1.2
jasonowitzki said:
Just to make sure.. there is no knox thing? so ill just do the normal flash and if wifi wont work,, ill just flash dr ketan's wifi fix? Thanks oopppsss.. i forgot.. im coming from 4.1.2
Click to expand...
Click to collapse
Yep
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. replies with quotes will be replied to faster.
Irwenzhao said:
Yep
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. replies with quotes will be replied to faster.
Click to expand...
Click to collapse
last questions sir... can i have a theme modification in case i successfully flash the rom ? like this one (http://forum.xda-developers.com/showthread.php?t=1940742) coz im currently using rom wanamlite with motomoto00 Theme.. would that be possible also to integrate motomoto to DN3? thanks a million times
jasonowitzki said:
last questions sir... can i have a theme modification in case i successfully flash the rom ? like this one (http://forum.xda-developers.com/showthread.php?t=1940742) coz im currently using rom wanamlite with motomoto00 Theme.. would that be possible also to integrate motomoto to DN3? thanks a million times
Click to expand...
Click to collapse
Nope. That theme's for AOSP (Omega ROM, to be specific) while Ditto Note 3 ROM is TouchWiz-Based.
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. replies with quotes will be replied to faster.
Irwenzhao said:
Nope. That theme's for AOSP (Omega ROM, to be specific) while Ditto Note 3 ROM is TouchWiz-Based.
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. replies with quotes will be replied to faster.
Click to expand...
Click to collapse
is this the right link for dr. ketan's wifi fix? (http://forum.xda-developers.com/attachment.php?attachmentid=2342179&d=1382427777)
Thank you so much for answering all my queries.. you're such a big help..
jasonowitzki said:
is this the right link for dr. ketan's wifi fix? (http://forum.xda-developers.com/attachment.php?attachmentid=2342179&d=1382427777)
Thank you so much for answering all my queries.. you're such a big help..
Click to expand...
Click to collapse
Can't see that, I'm on my phone sorry. (Link to that thread will do)
P.S. I never use XDA on my computer haha
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. replies with quotes will be replied to faster.
Or you can just flash MJ5 bootloader, it is 4.3 bootloader without knox. Much better IMHO than wifi fix.
Sent from my Nexus 7 using xda premium
dalanik said:
Or you can just flash MJ5 bootloader, it is 4.3 bootloader without knox. Much better IMHO than wifi fix.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I would rather stick with my old bootloader. Personal opinion.
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
jasonowitzki said:
Hi Everyone, I'm actually confused, I've downloaded Ditto Note 3 V3.1.1 (http://forum.xda-developers.com/showthread.php?t=2504016) and i want to flash it. It says that it needs bootloader 4.3. I just want to ask, is this with the knox security thing? coz i wanna get rid of that and ofcourse use the phone normally. Any suggestions guys to properly flash DN3 V3.1.1 without knox and properly use it without wifi issues. Thanks in advanced guys.. By the way my phone is Samsung Galaxy Note II (GT-N7105) LTE International
Click to expand...
Click to collapse
Mate, on the DN3 OP, it was written very clear.
Pls ignore about the wifi patch or anything abt it.
1. If u want to use stock kernel on DN3, u have to use new bootloader. Only new bootloader can dupport 4.3 stock kernel without wifi problem. But new bootloader will come with KNOX.
2. If u want to stick with old bootloader, u can do like what I did... full wipe - flash 3.1.1 dn3 - reboot (at this point u will be with stock kernel nd wifi not working) - update ota to 3.2 dn3 (u have to use ur data network. If ota fail, boot to recovery, flash the zip manually from OTA UPDATE folder) - reboot (wifi still not working) n let few mins to let the rom settle - reboot to recovery - wipe cache and wipe dalvik - flash devil - reboot - done! Ur wifi works nd u r still on 4.1.2 bootloader.
Fyi : devil 2.3.2 is good. Gyroscopes is now working.
Sent from SM-N9005 with xda-app
antique_sonic said:
Mate, on the DN3 OP, it was written very clear.
Pls ignore about the wifi patch or anything abt it.
1. If u want to use stock kernel on DN3, u have to use new bootloader. Only new bootloader can dupport 4.3 stock kernel without wifi problem. But new bootloader will come with KNOX.
2. If u want to stick with old bootloader, u can do like what I did... full wipe - flash 3.1.1 dn3 - reboot (at this point u will be with stock kernel nd wifi not working) - update ota to 3.2 dn3 (u have to use ur data network. If ota fail, boot to recovery, flash the zip manually from OTA UPDATE folder) - reboot (wifi still not working) n let few mins to let the rom settle - reboot to recovery - wipe cache and wipe dalvik - flash devil - reboot - done! Ur wifi works nd u r still on 4.1.2 bootloader.
Fyi : devil 2.3.2 is good. Gyroscopes is now working.
Sent from SM-N9005 with xda-app
Click to expand...
Click to collapse
okay.. now its somewhat clear to me.. the confusing part for me is the OTA update to 3.2? how can it be done... ? you save me here buddy.. i would also love to flash the devil coz ive read its working perfectly with boeflla? is that right?
jasonowitzki said:
okay.. now its somewhat clear to me.. the confusing part for me is the OTA update to 3.2? how can it be done... ? you save me here buddy.. i would also love to flash the devil coz ive read its working perfectly with boeflla? is that right?
Click to expand...
Click to collapse
Actually there is no OTA update to 3.2. You would have to download 1.5GB file and flash it.
jasonowitzki said:
okay.. now its somewhat clear to me.. the confusing part for me is the OTA update to 3.2? how can it be done... ? you save me here buddy.. i would also love to flash the devil coz ive read its working perfectly with boeflla? is that right?
Click to expand...
Click to collapse
ok.
as I mentioned earlier, the process to flash will be :
Flash DN3 v.3.1.1 => reboot (you will boot up the rom with stock kernel, with non working wifi if you are on 4.1.2 bootloader).
Up to here, do not need to worry. let the rom boot up, and then make sure superSU is working.
On my device, there will be a pop up on the notification bar, saying v.3.2 is available. Just click that one. If ask for root permission, grant it.
The OTA updater will download the v.3.2. Just follow instruction. Normally it will reboot to recovery, but won't install the v.3.2. I have no idea why.
When you are in recovery, just wipe cache, and dalvik. then you choose install file from internal sd (the OTA updater will download and save the file on internal SD). Browse to folder call "OTA Updater", and then folder download.
You will find the v.3.2 zip file there.
Just flash it, reboot again after that.
When the rom boot up, you can check on the about device, that you are now on v.3.2.
Now when v.3.2 is up, you can now change to devil kernel (up to you to choose which version. I'm using v.2.3.2 devil kernel), by go into recovery, wipe cache, and dalvik, and then flash your devil kernel.
Then let the system boot up. Now you will have a working Wifi
Notes :
Don't forget to go into Wifi advanced setting, and turn off (uncheck) always scanning. To have a better battery life. This option sucks battery a lot on 4.3 android.
if I'm not wrong, Viper will be better.
Good Luck!
Sent from the corner of this rounded earth behind my PC.
antique_sonic said:
ok.
as I mentioned earlier, the process to flash will be :
Flash DN3 v.3.1.1 => reboot (you will boot up the rom with stock kernel, with non working wifi if you are on 4.1.2 bootloader).
Up to here, do not need to worry. let the rom boot up, and then make sure superSU is working.
On my device, there will be a pop up on the notification bar, saying v.3.2 is available. Just click that one. If ask for root permission, grant it.
The OTA updater will download the v.3.2. Just follow instruction. Normally it will reboot to recovery, but won't install the v.3.2. I have no idea why.
When you are in recovery, just wipe cache, and dalvik. then you choose install file from internal sd (the OTA updater will download and save the file on internal SD). Browse to folder call "OTA Updater", and then folder download.
You will find the v.3.2 zip file there.
Just flash it, reboot again after that.
When the rom boot up, you can check on the about device, that you are now on v.3.2.
Now when v.3.2 is up, you can now change to devil kernel (up to you to choose which version. I'm using v.2.3.2 devil kernel), by go into recovery, wipe cache, and dalvik, and then flash your devil kernel.
Then let the system boot up. Now you will have a working Wifi
Notes :
Don't forget to go into Wifi advanced setting, and turn off (uncheck) always scanning. To have a better battery life. This option sucks battery a lot on 4.3 android.
if I'm not wrong, Viper will be better.
Good Luck!
Sent from the corner of this rounded earth behind my PC.
Click to expand...
Click to collapse
Thanks so much for this wonderful instructions.. now its very clear to me.. thanks
Hey guys,
So i've been reading up on how to install international ROMs on my tmo n900T. I've downloaded all the necessary wifi / network fix files and tmo kernels. However, whenever I try to install either Bobcat ROM or X-Note 13.0, after the Aroma install, everything in my internal SD card gets wiped....every time. This includes the /system folder, which means the phone won't boot.
I've tried both ROMs and it does it. I can install the TMO Jedi ROM just fine, which also uses Aroma. I've also tried to install both those roms from both Philz Touch Recovery and TWRP 2.7.0.0.
Any ideas what could be going wrong?
dirrtyswan said:
Hey guys,
So i've been reading up on how to install international ROMs on my tmo n900T. I've downloaded all the necessary wifi / network fix files and tmo kernels. However, whenever I try to install either Bobcat ROM or X-Note 13.0, after the Aroma install, everything in my internal SD card gets wiped....every time. This includes the /system folder, which means the phone won't boot.
I've tried both ROMs and it does it. I can install the TMO Jedi ROM just fine, which also uses Aroma. I've also tried to install both those roms from both Philz Touch Recovery and TWRP 2.7.0.0.
Any ideas what could be going wrong?
Click to expand...
Click to collapse
I've never tried those roms and Jedi is a great rom but as for using international rom, I am using Omega v12 (4.4.2), everything works, especially native bluetooth tethering (the reason i went International).
Good luck.
kadster007 said:
I've never tried those roms and Jedi is a great rom but as for using international rom, I am using Omega v12 (4.4.2), everything works, especially native bluetooth tethering (the reason i went International).
Good luck.
Click to expand...
Click to collapse
Thanks I might try out that ROM. I did some more research and I think my issue is common for a few international ROMs. I found the reason and some workarounds here:
http://forum.xda-developers.com/showthread.php?t=2490351&page=13
Going to give it a try now.
What exactly needs to be done to get dn3 rom working on the us tmobile note 2? Im having an issue finding the appropriate steps.
1. Be sure you download DN3 for the N7105 or i317
2. If you're not on 4.3 Bootloader then download Devil Kernel or AGNi Kernel (this will help get wifi to work)
3. Download Tmobiles mk7 modem
4. Be sure you're using TWRP or CWM
5. Wipe - System, Data, Dalvik-Cache & Cache
6. Flash DN3 Rom and reboot. (Flashing things over it before its first boot will not alliw it to boot)
7. Flash Kernel and modem.
Thanks. I couldnt find any definitive posts on the process. What kernel do you reccomend?
I'm using Devil but I've heard good things with AGNi.
Hope we get 4.4.2 dn3 soon
one80oneday said:
Hope we get 4.4.2 dn3 soon
Click to expand...
Click to collapse
my mouth is drooling for this
any scoop on it?
Double0EK said:
1. Be sure you download DN3 for the N7105 or i317
2. If you're not on 4.3 Bootloader then download Devil Kernel or AGNi Kernel (this will help get wifi to work)
3. Download Tmobiles mk7 modem
4. Be sure you're using TWRP or CWM
5. Wipe - System, Data, Dalvik-Cache & Cache
6. Flash DN3 Rom and reboot. (Flashing things over it before its first boot will not alliw it to boot)
7. Flash Kernel and modem.
Click to expand...
Click to collapse
Would u recommend the same steps for me? I have a tmobile note 2 and I unrooted it to get it back to 4.1.1 so I could unlock it to use my at&t sim card and everything working great so I rerooted it and now I want to flash the dn3 rom but im not sure what steps I need to take? Would I need abdifferent approach from your recommended steps here?
express21 said:
my mouth is drooling for this
any scoop on it?
Click to expand...
Click to collapse
Soon.
Sent from my NoteII
Does DN3 have all the Tmobile apps like wifi calling and visual voice mail? Does it have Note 3 apps too like the calendar and action memo
edo101 said:
Does DN3 have all the Tmobile apps like wifi calling and visual voice mail? Does it have Note 3 apps too like the calendar and action memo
Click to expand...
Click to collapse
It is not based on a tmo TW rom so WiFi calling is not included.
Hastily spouted for your befuddlement
How is battery life on DN3?
Currently im gettin on my current rom average 16 hours with 3 hours screen and 26 % battery left.
Is this rom up there with these figures?
Thanks in advance.
Cheers
I get 1 day+ 3 hours from 100% charge and im always on wifi so its a great rom and its stable.
I cant wait to get 4.4!
Sent from my SGH-T889
Hey guys. I installed dn3 v3.1.1 LTE yesterday and in aroma, I chose the n7105 install. Everything booted up and I got 4G instantly. After letting it sit for a little, I started using it and experienced a little lag and went ahead and flashed devil kernel 2.3.2. The phone is still lagging at times and had 3 random freezes/restarts. And the blue tooth audio is choppy at times when I'm doing anything else on the phone. Extreme lag at times. I'm coming from jedi X2 and updated my bootloader when I installed jedi.
Any suggestions?
I'm using tmobile note 2
Sent from my GT-N7105 using XDA Free mobile app
desikilla said:
Hey guys. I installed dn3 v3.1.1 LTE yesterday and in aroma, I chose the n7105 install. Everything booted up and I got 4G instantly. After letting it sit for a little, I started using it and experienced a little lag and went ahead and flashed devil kernel 2.3.2. The phone is still lagging at times and had 3 random freezes/restarts. And the blue tooth audio is choppy at times when I'm doing anything else on the phone. Extreme lag at times. I'm coming from jedi X2 and updated my bootloader when I installed jedi.
Any suggestions?
I'm using tmobile note 2
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
DN3 is already on KitKat. You should flash that.. you will need to be, atleast, on the 4.1.2 bootloader. Then you can flash AGNi Kernel 4.0
Double0EK said:
DN3 is already on KitKat. You should flash that.. you will need to be, atleast, on the 4.1.2 bootloader. Then you can flash AGNi Kernel 4.0
Click to expand...
Click to collapse
I wish someone would make a youtube tutorial on how to do this...
Really?
Is self explanitory...
Be sure you have at least MD1 bootloader.
1. Download Rom
2. Backup current Rom (optional)
3. Wipe
4. Flash Rom
5. Reboot
6. Setup
7. Reboot back into recovery and flash other options (kernel, modem, superSU...etc)
Double0EK said:
1. Be sure you download DN3 for the N7105 or i317
2. If you're not on 4.3 Bootloader then download Devil Kernel or AGNi Kernel (this will help get wifi to work)
3. Download Tmobiles mk7 modem
4. Be sure you're using TWRP or CWM
5. Wipe - System, Data, Dalvik-Cache & Cache
6. Flash DN3 Rom and reboot. (Flashing things over it before its first boot will not alliw it to boot)
7. Flash Kernel and modem.
Click to expand...
Click to collapse
Does flashing the kernel and modem get the Wi-Fi calling to work? I just wanted to confirm. I am not sure if you were referring to Wi-Fi in general. Thanks.
vandoc said:
Does flashing the kernel and modem get the Wi-Fi calling to work? I just wanted to confirm. I am not sure if you were referring to Wi-Fi in general. Thanks.
Click to expand...
Click to collapse
WiFi in general. You have to be on a T-Mobile stock ROM to use WiFi calling with T-Mobile as already answered on the first page.