nvm
Try another kernel ? Make sure you use aosp version of the kernel. What exactly is the problem with wifi ?
Sent from my GT-N7100
I tried the Zoot's wipe you suggested earlier, didn't fix the problem. Tried a few different kernels, all bootlooped.
The wifi takes a very long time scanning for networks, and won't connect to any network (unsecured, WEP, WPA, nothing). Works perfect on roms mentioned in first post, but not on 4.1.2 based PA.
Why do you want pa ? For per-app-dpi ? Well that can be done on normal phone also.
Sent from my GT-N7100
---------- Post added at 11:34 PM ---------- Previous post was at 11:29 PM ----------
You might want to take a look in Settings > Wi-Fi hit the Menu button again and choose Advanced and then make sure Keep Wi-Fi on during sleep is set to Always. Disable wifi timer.
Sent from my GT-N7100
do this 100 percent works
To insure this doesn't happen, just follow these steps:
1. Dial *#0011#
2. Hit the left menu softkey to bring up the menu, and select 'Wifi'
3. Turn OFF the 'Wifi Power Saving'
4. Exit, and Reboot
Where is my 100 dollar
nabilsweet007 said:
To insure this doesn't happen, just follow these steps:
1. Dial *#0011#
Click to expand...
Click to collapse
"Connection problem or invalid MMI code."
Did you try what I did ?
Sent from my GT-N7100
Try to change the flash root file. Look for cwm6-root-n7100 and flash it through Odin. It should work fine after that. Good Luck =D
Wow $100. Just trying to help only.
Odin back to original stock rom. Check all connection its ok or not.
Check ur note 2 version *#1234# and also imei *#06#.
Flash pa according to ur note2 version.
Check ur imei.
Flash kernel n modem based on ur note2 version.
I've tried all these things and none of them make wifi work for me on cm10 4.1.2 based roms. I don't think the problem is as simple as changing a setting or root/recovery, because simply flashing a different rom (TW 4.1.2 or 4.2 based PA) fixes the wifi issue entirely.
The $100 offer still applies to any developer who knows what the problem is and can provide files & specific instructions on how to fix the wifi connection issues I have with 4.1.2 based PA roms. Until then I'm gonna run an unofficial PA3 rom, with zero wifi issues.
Try this
First do a mega wipe.
Then flash the latest stock rom for your country.
Then do a mega wipe again.
Then flash aosp kernel(redpill or uneak)
Then flash pa .
Then flash gapps.
Try all the aosp kernels.
Try previous versions of the rom.
Try different versions of gapps.
Sent from my GT-N7100
UtkarshGupta said:
Try this
Click to expand...
Click to collapse
Please stop posting.
jakeordie said:
Please stop posting.
Click to expand...
Click to collapse
Why ? I am just trying to help.
Sent from my GT-N7100
I have a feeling you have the wrong kernel. Try finding the correct kernel for your baseband. Can you also take a screenshot of what is happening?
Sent from my GT-N7105 using xda app-developers app
stratex5 said:
I have a feeling you have the wrong kernel. Try finding the correct kernel for your baseband. Can you also take a screenshot of what is happening?
Click to expand...
Click to collapse
In Settings it says the baseband is N7100XXDLK7. This is probably because I've since flashed a stock rom from Dr. Ketan's thread. The label on the retail box says N7100ZNDXSG (but it doesn't say that's the baseband).
Are there AOSP kernels made for specific basebands?
Wifi works perfectly with every rom I've tried except anything CM10 4.1.2 based. The screen tear happened the same way with PA 2.99, and the same neak kernel fixed it, but there was never a problem with wifi on 2.99
Have you flashed isolated baseband from working rom?
If you have stock rom, extract tar and you will find modem.bin and flash it using odin for 'phone' tab
Just for safety make nandroid backup before it.
Sent from my GT-N7100 using xda premium
dr.ketan said:
Have you flashed isolated baseband from working rom?
Click to expand...
Click to collapse
Isolated, no. Are you saying that flashing a rom zip via CWM overwrites the existing baseband?
At this point, the unofficial PA 3.1 is working for me where the official PA 2.99 wasn't.....so the $100 offer is no more. Thanks everyone for trying to help me fix the problem, but now I've got the phone set up how I wanted with another rom.
jakeordie said:
Isolated, no. Are you saying that flashing a rom zip via CWM overwrites the existing baseband?
At this point, the unofficial PA 3.1 is working for me where the official PA 2.99 wasn't.....so the $100 offer is no more. Thanks everyone for trying to help me fix the problem, but now I've got the phone set up how I wanted with another rom.
Click to expand...
Click to collapse
There is no official pa for note 2.
Just ports.
Sent from my GT-N7100
jakeordie said:
Please stop posting.
Click to expand...
Click to collapse
That's rude. anyways try contacting other PA users , if they have the same problem there's something wrong with the rom, if its only you then something is wrong with the phone ( i had something like that back in s2 days and aokp, only my phone had wifi problems with it, other s2's worked good). and why not try this
UtkarshGupta said:
There is no official pa for note 2.
Just ports.
Click to expand...
Click to collapse
I was referring to this one http://forum.xda-developers.com/showthread.php?t=1970341, is it not official?
lesalloum said:
That's rude. and why not try this
Click to expand...
Click to collapse
I said please. Personally I think it's rude for someone to be giving advice when they don't know WTF they're saying.
Before I edited the OP, it said I had tried replacing the etc/wifi files from 4.1.1 and it didn't work.....maybe you missed that, no worries and thanks anyways.
Related
Let's figure out why this has happen.
Please post which ROMs you've used.
Please post baseband version.
Post logcat
I'll go first.
I tried the Saurom,
then madmack's cm10,
then jellybeer,
then jelllybam.
I am using Baseband I317UCALK7 found here
I have 0 bluetooth issues.
Really appreciate you starting this thread.
So far I've tried:
- madmack's CM10
- JellyBeer v3. something.
- PA 2.56
None of these had working bluetooth for me. Won't even turn on. Sometimes the toggle won't even move.
I've flashed and reflashed and wiped and dirty flashed and wiped again in every combination possible.
I've tried keeping my min cpu frequency high, to no effect.
I'm about to try your 3.30 JellyBam and try the latest AOKP from the TMobile forum.
Will post logcat shortly.
static416 said:
Really appreciate you starting this thread.
So far I've tried:
- madmack's CM10
- JellyBeer v3. something. Something prior to your 3.35 which I'm downloading now.
- PA 2.56
None of these had working bluetooth for me. Won't even turn on. Sometimes the toggle won't even move.
I've flashed and reflashed and wiped and dirty flashed and wiped again in every combination possible.
I've tried keeping my min cpu frequency high, to no effect.
I'm about to try your 3.35 JellyBeer and try the latest AOKP from the TMobile forum.
Will post logcat shortly.
Click to expand...
Click to collapse
What ROMs did you have before the AOSP ones.
Try flashing the modem I posted.
ManelScout4Life said:
What ROMs did you have before the AOSP ones.
Try flashing the modem I posted.
Click to expand...
Click to collapse
I think I only used Saurom-Projekt prior to CM10, and Saurom is still my daily driver because I need the bluetooth.
I'm using Rogers and my baseband is I317MVLALJ2.
Just tried 3.35 JellyBeer and no luck. Toggle moves, no bluetooth.
---------- Post added at 09:28 PM ---------- Previous post was at 09:14 PM ----------
ManelScout4Life said:
What ROMs did you have before the AOSP ones.
Try flashing the modem I posted.
Click to expand...
Click to collapse
Flashing your modem just boot-loops my device. Probably because it's Rogers phone?
Reverting to Rogers modem and JellyBam 3.30 to get a logcat.
static416 said:
I think I only used Saurom-Projekt prior to CM10, and Saurom is still my daily driver because I need the bluetooth.
I'm using Rogers and my baseband is I317MVLALJ2.
Just tried 3.35 JellyBeer and no luck. Toggle moves, no bluetooth.
---------- Post added at 09:28 PM ---------- Previous post was at 09:14 PM ----------
Flashing your modem just boot-loops my device. Probably because it's Rogers phone?
Reverting to Rogers modem and JellyBam 3.30 to get a logcat.
Click to expand...
Click to collapse
Yes, in that thread it says that will happen on Rodger phones.
But try flashing the modem then an AOSP ROM over it
ManelScout4Life said:
Yes, in that thread it says that will happen on Rodger phones.
But try flashing the modem then an AOSP ROM over it
Click to expand...
Click to collapse
Nope. Flashing the modem first, then the ROM still results in boot loop.
static416 said:
Nope. Flashing the modem first, then the ROM still results in boot loop.
Click to expand...
Click to collapse
Have you tried to Odin back to 100% stock
ManelScout4Life said:
Have you tried to Odin back to 100% stock
Click to expand...
Click to collapse
AWESOME. I figured it out.
Well someone else did, and I copied it and it worked.
http://forum.xda-developers.com/showpost.php?p=36470002&postcount=219
I don't know why I didn't do a proper logcat earlier. I tried it once and it didn't seem to show anything, but I must not have timed it right.
My logcat shows exactly as this guy shows: http://forum.xda-developers.com/showpost.php?p=36468370&postcount=218
Basically, it can't find the proper .hcd file, because for some reason mine is named /system/bin/bcm4334_semcosh.hcd.
Renaming it to /system/bin/bcm4334_semco.hcd fixes it, without even a need for a reboot.
----
All that said, I've merely gotten bluetooth to turn on. No word yet on it's performance. But it's promising.
You shouldn't have to rename that file... that's what we need to figure out. Why certain devices are behaving like that.
cmenard said:
You shouldn't have to rename that file... that's what we need to figure out. Why certain devices are behaving like that.
Click to expand...
Click to collapse
Yeah, I didn't have to rename anything.
static416 said:
AWESOME. I figured it out.
Well someone else did, and I copied it and it worked.
http://forum.xda-developers.com/showpost.php?p=36470002&postcount=219
I don't know why I didn't do a proper logcat earlier. I tried it once and it didn't seem to show anything, but I must not have timed it right.
My logcat shows exactly as this guy shows: http://forum.xda-developers.com/showpost.php?p=36468370&postcount=218
Basically, it can't find the proper .hcd file, because for some reason mine is named /system/bin/bcm4334_semcosh.hcd.
Renaming it to /system/bin/bcm4334_semco.hcd fixes it, without even a need for a reboot.
----
All that said, I've merely gotten bluetooth to turn on. No word yet on it's performance. But it's promising.
Click to expand...
Click to collapse
Do you have any of these files in /data/.cid.info or /data/.rev or /data/.psm.info
I'm not going to double post...but you can read what I had to do to get BT to work here...http://forum.xda-developers.com/showpost.php?p=36582529&postcount=426
Long story...Yes...Blue tooth does indeed work for me......now
Mac
Bluetooth not working for me either. I've used Paranoid, JellyBeer, JellyBam. Only Touchwiz based ROM have working Bluetooth.
jeck77 said:
Bluetooth not working for me either. I've used Paranoid, JellyBeer, JellyBam. Only Touchwiz based ROM have working Bluetooth.
Click to expand...
Click to collapse
There will be a fix out tonight so that bluetooth works for everyone.
ManelScout4Life said:
There will be a fix out tonight so that bluetooth works for everyone.
Click to expand...
Click to collapse
Sweet! Looking forward to finally being able to flash a AOSP ROM on my phone.
ManelScout4Life said:
There will be a fix out tonight so that bluetooth works for everyone.
Click to expand...
Click to collapse
I wonder what the fix is, but I wonder if different devices have slightly different Bluetooth modules.
Sent from my SGH-T889 using xda app-developers app
Hi guys.
The title pretty much says it all.
I currently have the XXDME4 modem installed (went to this from XXDLJ2 and... I have no idea what modem I was using prior to that) and am using Slim Bean ROM. But, I want to give a TouchWiz ROM a try, to test something sound related (5 minutes), then be done with it and return to AOSP based ROMs and such. With all this modem/EFS talk... I am very confused. Don't know what modem/ROM base I am safe to go to now...
So. What TouchWiz ROM should I install and be free of any EFS ****ed up things?
Thanks in advance!
If u r happy with this modem, install a rom like assasin which gives you option whether to keep the old modem and kernal or to change it. If you dont change the modem, efs wont be messed up I fee
Sent from my GT-N7100 using xda app-developers app
Formhault said:
Hi guys.
The title pretty much says it all.
I currently have the XXDME4 modem installed (went to this from XXDLJ2 and... I have no idea what modem I was using prior to that) and am using Slim Bean ROM. But, I want to give a TouchWiz ROM a try, to test something sound related (5 minutes), then be done with it and return to AOSP based ROMs and such. With all this modem/EFS talk... I am very confused. Don't know what modem/ROM base I am safe to go to now...
So. What TouchWiz ROM should I install and be free of any EFS ****ed up things?
Thanks in advance!
Click to expand...
Click to collapse
Take a backup of the EFS by using the tool here. Then it'll be easy for you to restore.
http://forum.xda-developers.com/showthread.php?t=1922473
prabukannappan said:
Take a backup of the EFS by using the tool here. Then it'll be easy for you to restore.
http://forum.xda-developers.com/showthread.php?t=1922473
Click to expand...
Click to collapse
I know that, but... I wanna do it the easy way, without having to backup & all...
Anyway, guess I'm gonna have to do that.
One q. Now, as I am on XXDME4, if I ever switch to another modem which changes EFS... if I revert back to XXDME4, will it be okay?
(still got a lot to read on this thing, that's why I'm asking for now)
Formhault said:
I know that, but... I wanna do it the easy way, without having to backup & all...
Anyway, guess I'm gonna have to do that.
One q. Now, as I am on XXDME4, if I ever switch to another modem which changes EFS... if I revert back to XXDME4, will it be okay?
(still got a lot to read on this thing, that's why I'm asking for now)
Click to expand...
Click to collapse
Ya. If you lose your EFS anytime at all, Revert back to XXDME4 and restore this image.
There is no other easy ways than this. This would just take seconds and you're already rooted.
As mentioned by people before, you're fine as long as the ROMs you're flashing doesn't mess up with modem.
prabukannappan said:
As mentioned by people before, you're fine as long as the ROMs you're flashing doesn't mess up with modem.
Click to expand...
Click to collapse
That's what I initially wanted to find out : what ROMs out there don't do that... :laugh:
Formhault said:
That's what I initially wanted to find out : what ROMs out there don't do that... :laugh:
Click to expand...
Click to collapse
That's easy, download any rom, enter the archive with some Zip tool and replace the modem part with your current one. Or if you feel up to it, edit installation script to not flash modem. You can do the same with kernel so it is not flashed at all. That way you can use any rom without fear
Most roms are in fact compatible with wide variety of kernels / modems (even if some are included in installation - they are tested by developer to be fully compatible) so you should have no problems. For your information you can currently use all roms that are from ME6, MF2 and MG1 family - as Adam's kernel author mentioned, the compatibility problem lies in changed kernel ramdisk and he uses old one so you can flash his kernel over any TW rom without fear of breaking EFS.
mat9v said:
That's easy, download any rom, enter the archive with some Zip tool and replace the modem part with your current one. Or if you feel up to it, edit installation script to not flash modem. You can do the same with kernel so it is not flashed at all. That way you can use any rom without fear
Most roms are in fact compatible with wide variety of kernels / modems (even if some are included in installation - they are tested by developer to be fully compatible) so you should have no problems. For your information you can currently use all roms that are from ME6, MF2 and MG1 family - as Adam's kernel author mentioned, the compatibility problem lies in changed kernel ramdisk and he uses old one so you can flash his kernel over any TW rom without fear of breaking EFS.
Click to expand...
Click to collapse
Yeah...
Ok. So, as I now am on XXDME4, what other modems am I safe to go to? DME1, DMF2, DMG1...? Anything, EXCEPT for DME6?!
Formhault said:
Yeah...
Ok. So, as I now am on XXDME4, what other modems am I safe to go to? DME1, DMF2, DMG1...? Anything, EXCEPT for DME6?!
Click to expand...
Click to collapse
Anything before dme6. Dmf2 and dmg1 are after so not safe if you don't want the efs headaches.
-- Sent from the mighty Note 2 --
dr.m0x said:
Anything before dme6. Dmf2 and dmg1 are after so not safe if you don't want the efs headaches.
-- Sent from the mighty Note 2 --
Click to expand...
Click to collapse
F***. Now I don't know what's after and what's before. Can you please tell me what's before...?
It's hard because even in the modem thread, there is not a list with all modems in chronological order...
Formhault said:
F***. Now I don't know what's after and what's before. Can you please tell me what's before...?
It's hard because even in the modem thread, there is not a list with all modems in chronological order...
Click to expand...
Click to collapse
Samsung version naming is alphabetical followed by a hexadecimal suffix. Bmf1 is older than dmb2 which is older than dmb5 which is older than dmc3.
-- Sent from the mighty Note 2 --
dr.m0x said:
Samsung version naming is alphabetical followed by a hexadecimal suffix. Bmf1 is older than dmb2 which is older than dmb5 which is older than dmc3.
-- Sent from the mighty Note 2 --
Click to expand...
Click to collapse
I... I'm not good with hexa stuff... At all...
Can you please list me the modems/bases older than DME4 that are safe?
Sent from hyperspace
Formhault said:
I... I'm not good with hexa stuff... At all...
Can you please list me the modems/bases older than DME4 that are safe?
Sent from hyperspace
Click to expand...
Click to collapse
It's easy: rom names are created from years and months and inmonth revisions
so LL7 is revision 7 of December 2012 rom
A-January
B-February
C-March
D-April
E-May
F-June
G-July
and so on...
also
A-2001
B-2002
.
.
.
.
.
.
.
.
.
L-2012
M-2013
So anything before ME1 is really safe. Best would be to flash stock for example XXDMC2 and on that flash any new custom rom with modem and kernel flashing disabled.
Oh... I think I understand...
Sent from hyperspace
mat9v said:
So anything before ME1 is really safe.
Click to expand...
Click to collapse
I'll try finding a custom ROM DMC.
Sent from hyperspace
But hang on a second. What if I flash a new modem? I do not intend to stick to TW - I just wanna test something sound related cause NO ONE ELSE WOULD then go back to Slim/CM etc.
If I use the very latest modem (whichever that may be) and use them on CM... Would there be a problem?
Sent from hyperspace
Formhault said:
But hang on a second. What if I flash a new modem? I do not intend to stick to TW - I just wanna test something sound related cause NO ONE ELSE WOULD then go back to Slim/CM etc.
If I use the very latest modem (whichever that may be) and use them on CM... Would there be a problem?
Sent from hyperspace
Click to expand...
Click to collapse
Not from CM side CM mostly does not care what version of modem you have, and it's not the modem that is creating all those problems, but newer kernels (ME6 and newer). So don't touch the modem at all or flash it if you want. But don't flash newer kernel ME6, MF1 or MG1. Flash Perseus 36.3 kernel, do it immediately after flashing rom, without restarting recovery, because once you run new kernel even one time you have a problem.
mat9v said:
Not from CM side CM mostly does not care what version of modem you have, and it's not the modem that is creating all those problems, but newer kernels (ME6 and newer). So don't touch the modem at all or flash it if you want. But don't flash newer kernel ME6, MF1 or MG1. Flash Perseus 36.3 kernel, do it immediately after flashing rom, without restarting recovery, because once you run new kernel even one time you have a problem.
Click to expand...
Click to collapse
So... I can flash a ME6 ROM but not boot it, and flash this older modem again + Perseus THEN reboot and I'll be safe?
Sent from hyperspace
Formhault said:
So... I can flash a ME6 ROM but not boot it, and flash this older modem again + Perseus THEN reboot and I'll be safe?
Sent from hyperspace
Click to expand...
Click to collapse
Yes.
---------- Post added at 10:07 PM ---------- Previous post was at 09:50 PM ----------
Formhault said:
But hang on a second. What if I flash a new modem? I do not intend to stick to TW - I just wanna test something sound related cause NO ONE ELSE WOULD then go back to Slim/CM etc.
If I use the very latest modem (whichever that may be) and use them on CM... Would there be a problem?
Sent from hyperspace
Click to expand...
Click to collapse
Or you can tell me what and how to test and maybe I will be able to help
mat9v said:
Or you can tell me what and how to test and maybe I will be able to help
Click to expand...
Click to collapse
This.
Thanks in advance!
Hi guys!
First of all I am sorry for posting in this forum but I believe Korean Note 2 is similar in many aspect to N7105 and also there are devs who can read and maybe come up with something.
I have a question for you. Has anyone tried an Android 4.3 custom ROM on e250s (Korean Note 2) ? I am currently on 4.1.2, a combination of Milan 3.0 and Milan 4.0 (I think this ROMs are also for N7105 because in About device section my phone appears to be a N7105 after flashing), with some stock kernel and cwm. I have tried a few 4.3 ROMs for N7105 (CM 10.2, Beanstalk, Illusion) but all get stuck at the boot logo (Samsung Galaxy Note 2). I even tried different kernels, compatible with 4.3 (SJKernel and NeKo) but again, with no luck.
Do you have a solution, link, idea?
Thanks in advance guys!
Any links?
Sent from the TermiNOTEr 2!
borijess said:
Any links?
Sent from the TermiNOTEr 2!
Click to expand...
Click to collapse
Here is a screenshot of my system.
razvan11malancus said:
Here is a screenshot of my system.
Click to expand...
Click to collapse
Ok that's 4.1.2 don't get it. Thought you had 4.3 touch wiz.
Sent from the TermiNOTEr 2!
borijess said:
Ok that's 4.1.2 don't get it. Thought you had 4.3 touch wiz.
Sent from the TermiNOTEr 2!
Click to expand...
Click to collapse
Yes. My actual ROM is 4.1.2. I have tried Jedi X19 (4.1.2) and also BeanStalk, Illusion, CM 10.2 (4.3), with the same result. Stuck at boot screen logo.
Ni hao
razvan11malancus said:
Hi guys!
First of all I am sorry for posting in this forum but I believe Korean Note 2 is similar in many aspect to N7105 and also there are devs who can read and maybe come up with something.
I have a question for you. Has anyone tried an Android 4.3 custom ROM on e250s (Korean Note 2) ? I am currently on 4.1.2, a combination of Milan 3.0 and Milan 4.0 (I think this ROMs are also for N7105 because in About device section my phone appears to be a N7105 after flashing), with some stock kernel and cwm. I have tried a few 4.3 ROMs for N7105 (CM 10.2, Beanstalk, Illusion) but all get stuck at the boot logo (Samsung Galaxy Note 2). I even tried different kernels, compatible with 4.3 (SJKernel and NeKo) but again, with no luck.
Do you have a solution, link, idea?
Thanks in advance guys!
Click to expand...
Click to collapse
bbs.gfan.com/forum.php?mod=viewthread&tid=5919447&extra=page%3D2
cbeta1111 said:
bbs.gfan.com/forum.php?mod=viewthread&tid=5919447&extra=page%3D2
Click to expand...
Click to collapse
Thanks.
I have finally installed 4.3 ROM after flashing a file that converts the kernel to e250s.
Vibration issue
Hi guys!
Is anyone else having issues with vibrations when using a N7105 ROM (with Android 4.2.2 or 4.3)? I mean the phone does not vibrate at all.
Do you know a fix or something?
Thanks!
razvan11malancus said:
Hi guys!
Is anyone else having issues with vibrations when using a N7105 ROM (with Android 4.2.2 or 4.3)? I mean the phone does not vibrate at all.
Do you know a fix or something?
Thanks!
Click to expand...
Click to collapse
Use AOSP e250s Thor's kernel (update-0.27-aosp-KO-LTE-e250s-lsi-n7100.zip)
download:
mediafire.com/folder/41s5eea1er9dt/0.27
original thread:
forum.tegraowners.com/viewtopic.php?f=41&t=872
cbeta1111 said:
bbs.gfan.com/forum.php?mod=viewthread&tid=5919447&extra=page%3D2
Click to expand...
Click to collapse
what is that?
Cannot read chinese
can you give us link of downalod?
I own note 2 e250 s
---------- Post added at 02:55 AM ---------- Previous post was at 02:53 AM ----------
razvan11malancus said:
Thanks.
I have finally installed 4.3 ROM after flashing a file that converts the kernel to e250s.
Click to expand...
Click to collapse
which 4.3 ROM did you installed and how?
can you tell us bit more about converting kernels
Rajaasim1980 said:
what is that?
Cannot read chinese
can you give us link of downalod?
I own note 2 e250 s
---------- Post added at 02:55 AM ---------- Previous post was at 02:53 AM ----------
which 4.3 ROM did you installed and how?
can you tell us bit more about converting kernels
Click to expand...
Click to collapse
Hi. This is the link to the boot converter.
http://forum.xda-developers.com/showpost.php?p=36885456
All you have to do is flash this zip file from cwm after you first flash the ROM.
I have tried Illusion and PAC-MAN ROMs (N7105, Android 4.3) and also MIUI v5 for N7105 (Android 4.2.2) and all work fine.
There may be some ROMs (PAC-MAN) that give you "error 7" when flashing. You have to change the first line from META-INF/com/google/android/update script.
How I do that. I prefer to change the ROMs extension from zip to apk, then unzip it using APK Tool and go to the file, change extention to .txt and delete the first line (the one that starts with assert), thus the first line becoming the one with "show progress" or "mount". After that I zip it again with APK Tool and sign the ROM with ApkSign. I do not know why, I cannot sign it with APK Tool. After that, the flashing process should go fine. You have to install the right GApps for the ROM you are being flashing and then the boot converter from the link.
The only issue I have found was the absence of vibrations, but I managed to get it back by flashing Thor Kernel for Note 2, like cbeta1111 and eggymustdie told me. So huge thanks to them.
Good luck! Hope you will manage to install the desired ROM. In my opinion, PAC-MAN ROM is the best so far, with many, many options from CM, AOKP and Paranoid Android ROMs.
cbeta1111 said:
Use AOSP e250s Thor's kernel (update-0.27-aosp-KO-LTE-e250s-lsi-n7100.zip)
download:
mediafire.com/folder/41s5eea1er9dt/0.27
original thread:
forum.tegraowners.com/viewtopic.php?f=41&t=872
Click to expand...
Click to collapse
Thanks a lot man! It works now!
razvan11malancus said:
Hi. This is the link to the boot converter.
http://forum.xda-developers.com/showpost.php?p=36885456
All you have to do is flash this zip file from cwm after you first flash the ROM.
I have tried Illusion and PAC-MAN ROMs (N7105, Android 4.3) and also MIUI v5 for N7105 (Android 4.2.2) and all work fine.
There may be some ROMs (PAC-MAN) that give you "error 7" when flashing. You have to change the first line from META-INF/com/google/android/update script.
How I do that. I prefer to change the ROMs extension from zip to apk, then unzip it using APK Tool and go to the file, change extention to .txt and delete the first line (the one that starts with assert), thus the first line becoming the one with "show progress" or "mount". After that I zip it again with APK Tool and sign the ROM with ApkSign. I do not know why, I cannot sign it with APK Tool. After that, the flashing process should go fine. You have to install the right GApps for the ROM you are being flashing and then the boot converter from the link.
The only issue I have found was the absence of vibrations, but I managed to get it back by flashing Thor Kernel for Note 2, like cbeta1111 and eggymustdie told me. So huge thanks to them.
Good luck! Hope you will manage to install the desired ROM. In my opinion, PAC-MAN ROM is the best so far, with many, many options from CM, AOKP and Paranoid Android ROMs.
Click to expand...
Click to collapse
Thanks for detail response
I am using TWRP touch custom recovery. would this process work for TWRP?
I did not get second part about changing first line from META-INF/com/google/android/update script. where is that? You mean first line of custom 4.3/4.2 ROMs we are going to install?
and also do call recoding work in 4.3/4.2 PAC ROMS because i actually use this function and multi windows ?
This is dev forum, not Q&A. All questions should go in questions forum.
Rajaasim1980 said:
Thanks for detail response
I am using TWRP touch custom recovery. would this process work for TWRP?
I did not get second part about changing first line from META-INF/com/google/android/update script. where is that? You mean first line of custom 4.3/4.2 ROMs we are going to install?
and also do call recoding work in 4.3/4.2 PAC ROMS because i actually use this function and multi windows ?
Click to expand...
Click to collapse
Hi. It should definitely work with TWRP recovery as it installs like a normal zip file ROM.
The update script file is located in the ROM. You have to unzip it and go to that location as I have said in the anterior post.
Call recording works but I did not figured yet how to play the file after it is saved. It saves the file as a .3gpp but I think the problem is with Android 4.3 codecs.
EDIT: It works if you try to play it from the built in file manager. Not with Root Explorer. Do not know why.
Multiwindows work great in PAC-MAN ROM:
TheATHEiST said:
This is dev forum, not Q&A. All questions should go in questions forum.
Click to expand...
Click to collapse
Sorry, I know that this section is for developers only but I think it has more visibility here. It wont happen again.
razvan11malancus said:
Sorry, I know that this section is for developers only but I think it has more visibility here. It wont happen again.
Click to expand...
Click to collapse
That is an extremely bad excuse. What on earth do you think the dev forums would look like if everybody just decided to post non-relevant topics anywhere they wanted to?
TheATHEiST said:
That is an extremely bad excuse. What on earth do you think the dev forums would look like if everybody just decided to post non-relevant topics anywhere they wanted to?
Click to expand...
Click to collapse
Are you moderator or what?
Leave it for them to.move or delete
Sent from my GT-N7105 using Tapatalk 2
Rajaasim1980 said:
Are you moderator or what?
Leave it for them to.move or delete
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
Errr I did! and they have!!!!!
Doesn't mean I cant voice my opinion (Same as you did) as well as report post!
Good evening everyone. I recently got this phone from the Black Friday deal at Best Buy for 80$ and rooted and did all of that without much problem. I installed the Wicked ROM without any issues, and tested it out but I prefer AOSP. But when I flash Cyanogen or Bliss, I lose all of the mobile data , the baseband, here I include a screenshot. I have flashed a stock ROM once again, activated it again without any problem, but when I try to flash an AOSP ROM again I lose everything. Is there anything I can do about that? I have searched the forums and Google and found no solutions. Any help would be greatly appreciated.
Did you check to make sure that the md5 matched? Anytime I've had that happen either the md5 didn't match, or I needed to use a different kernel. My Goto kernel for AOSP ROMs has been BMS.
mattzeller said:
Did you check to make sure that the md5 matched? Anytime I've had that happen either the md5 didn't match, or I needed to use a different kernel. My Goto kernel for AOSP ROMs has been BMS.
Click to expand...
Click to collapse
Thanks for the tip, tried flashing Cyanogenmod with that kernel and the same thing happens, I lose all of the settings related to the Baseband, Modem and IMEI. I checked the md5 and it matches completely. I have no idea what is happening. For now I settled into the Conquest Singulalirty ROM which provides an ASJOP look but on offical firmware. But still I would like to know how to solve this problem so if anyone has any tips that would be greatly appreciated.
Is your phone the L710T model by any chance? I had the same problem with every rom I tried EXCEPT for Gummy 3.0. For some reason Gummy 3.0 recognizes my baseband/modem but if I try Gummy 4.0 or any other AOSP rom, no baseband.
Flash universal fix
luisro said:
Good evening everyone. I recently got this phone from the Black Friday deal at Best Buy for 80$ and rooted and did all of that without much problem. I installed the Wicked ROM without any issues, and tested it out but I prefer AOSP. But when I flash Cyanogen or Bliss, I lose all of the mobile data , the baseband, here I include a screenshot. I have flashed a stock ROM once again, activated it again without any problem, but when I try to flash an AOSP ROM again I lose everything. Is there anything I can do about that? I have searched the forums and Google and found no solutions. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Flash the file here: http://androidforums.com/threads/mo...apn-fix-wip-cm-aosp-4-4-x.840298/#post6516416
It will modify necessary files in the system to allow you to connect. Also, dial ##72786# to reactivate after flashing. That all worked for me on my Virgin S3 running Carbon. Good luck!
The SPH-L710T is what was on sale at BestBuy for $80 (as I found out after running into a similar problem), and it's a pain in the ass. It seems that TW ROMs are the only ones that don't break the radio... and the M10 snapshot of CM11 apparently (except rotation is backwards). I'm looking for a fix as well.
It seems that all of this can be fixed by a custom kernel, but there's no AOSP/CM kernel (that I know of) that fixes both.
I wish I knew something about kernel development...
kdude63 said:
The SPH-L710T is what was on sale at BestBuy for $80 (as I found out after running into a similar problem), and it's a pain in the ass. It seems that TW ROMs are the only ones that don't break the radio... and the M10 snapshot of CM11 apparently (except rotation is backwards). I'm looking for a fix as well.
It seems that all of this can be fixed by a custom kernel, but there's no AOSP/CM kernel (that I know of) that fixes both.
I wish I knew something about kernel development...
Click to expand...
Click to collapse
That is exactly the one that I have, the 80$ Best Buy from Black Friday. Yeah, I tried what metalhead131 said and it did not work. Hmmm, M10 snapshot worked for you? I will try it out them to see how it goes. In what way did it break the rotation? It does not rotate or is it inaccurate? It is a pain in the ass that we have so many ROMS available but we can't use them. I have been using the Conquest Singularity by Moon Knight. The one that is here in XDA is kinda of outdated but if you Google it you will find his blog with the latest update. He created an AOSP looking ROM but it is TW underneath. That combined with Gravity Box has satisfied me for now, but I hate no being able to flash AOSP ROMS. I know nothing about kernel development, but if someone wants to help with this I can provide anything they need in order to fix this problem with this T version of the phone.
I will try to take the kernel of the M10 and flash it with another ROM to see if the rotation works. I will update as soon as I do that.
luisro said:
That is exactly the one that I have, the 80$ Best Buy from Black Friday. Yeah, I tried what metalhead131 said and it did not work. Hmmm, M10 snapshot worked for you? I will try it out them to see how it goes. In what way did it break the rotation? It does not rotate or is it inaccurate? It is a pain in the ass that we have so many ROMS available but we can't use them. I have been using the Conquest Singularity by Moon Knight. The one that is here in XDA is kinda of outdated but if you Google it you will find his blog with the latest update. He created an AOSP looking ROM but it is TW underneath. That combined with Gravity Box has satisfied me for now, but I hate no being able to flash AOSP ROMS. I know nothing about kernel development, but if someone wants to help with this I can provide anything they need in order to fix this problem with this T version of the phone.
I will try to take the kernel of the M10 and flash it with another ROM to see if the rotation works. I will update as soon as I do that.
Click to expand...
Click to collapse
Yeah, the radio worked with the M10 snapshot. I was able to get the latest version of ParanoidAndroid to work with the M10 snapshot kernel as well.
When I say rotation is broken I mean when you hold it sideways, it rotates the wrong way, so it's upside down.
kdude63 said:
Yeah, the radio worked with the M10 snapshot. I was able to get the latest version of ParanoidAndroid to work with the M10 snapshot kernel as well.
When I say rotation is broken I mean when you hold it sideways, it rotates the wrong way, so it's upside down.
Click to expand...
Click to collapse
Excellent. Thanks for the good news! That doesn't bother me that much, so I will do that with the Bliss ROM that I wanted to install. I will keep investigating and trying things to see if we can fix the rotation issue. I will keep the thread updated.
Semi-Fix for the rotation issue on the M10 kernel.
After checking some apps out, I found one that worked well for the rotation problem using AOSP ROMS on the troublesome SPH-L710T. The app is called Adaptive Rotation Lock and is available for free on the Play Store. What it does is that a little button pops up everytime you rotate your phone, and if you don't click that button the screen will not rotate. So once you put your phone horizontallly, click on the button that pops up to allow the phone to rotate upside-down, then rotate the phone so it is not upside-down anymore, but do not click the button, so it stays in the correct rotation. It is a little cumbersome, but it beats always being upside down while using the phone horizontally! I think this is a good option while we find out how to fix this issue in the kernel.
kdude63 said:
Yeah, the radio worked with the M10 snapshot. I was able to get the latest version of ParanoidAndroid to work with the M10 snapshot kernel as well.
When I say rotation is broken I mean when you hold it sideways, it rotates the wrong way, so it's upside down.
Click to expand...
Click to collapse
Greeting kdude63. Thanks to your tips I was able to test many roms and as you settled on Paranoid Android. The only problem I have right now is that intermittently point I lose cell coverage for like 2 minutes, but then I get it back. Does that happen on your phone?
I have also tried many kernels to see if I find another one that works but no go. I am still using the M10 boot.img. Have you found another one that works?
And thanks for helping out with the ODIN tar for this phone! It makes me feel a lot more safe when I am experimenting.
Sent from my SPH-L710 using XDA Free mobile app
luisro said:
Greeting kdude63. Thanks to your tips I was able to test many roms and as you settled on Paranoid Android. The only problem I have right now is that intermittently point I lose cell coverage for like 2 minutes, but then I get it back. Does that happen on your phone?
I have also tried many kernels to see if I find another one that works but no go. I am still using the M10 boot.img. Have you found another one that works?
And thanks for helping out with the ODIN tar for this phone! It makes me feel a lot more safe when I am experimenting.
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
I don't currently use PA or CM as my daily driver, so I don't know. (I don't like dealing with the rotation issues)
I was testing some other kernels earlier, none of them worked before I got careless and accidentally flashed an i9300 kernel, so I can't use my phone for the time being.
Cnexus and several others have posted debrick images and stock ROMS for various versions of the s3. Good luck debricking
Sent from my CarbonROM 4.4.4 SPH-L710
luisro said:
Good evening everyone. I recently got this phone from the Black Friday deal at Best Buy for 80$ and rooted and did all of that without much problem. I installed the Wicked ROM without any issues, and tested it out but I prefer AOSP. But when I flash Cyanogen or Bliss, I lose all of the mobile data , the baseband, here I include a screenshot. I have flashed a stock ROM once again, activated it again without any problem, but when I try to flash an AOSP ROM again I lose everything. Is there anything I can do about that? I have searched the forums and Google and found no solutions. Any help would be greatly appreciated.
Click to expand...
Click to collapse
wait you had success flashing wicked????? which one????? that's my favorite rom I'm running Conquest at the moment tried to flash Wicked X bare-bones on the new T model but it didn't work sadly :'(
---------- Post added at 03:06 PM ---------- Previous post was at 02:54 PM ----------
metalhead131 said:
Cnexus and several others have posted debrick images and stock ROMS for various versions of the s3. Good luck debricking
Sent from my CarbonROM 4.4.4 SPH-L710
Click to expand...
Click to collapse
The debrick image for the T model was just barely posted last week in Android Forms....and there is a thread in the questions section here on XDA that has it linked
6th_Hokage said:
wait you had success flashing wicked????? which one????? that's my favorite rom I'm running Conquest at the moment tried to flash Wicked X bare-bones on the new T model but it didn't work sadly :'(
---------- Post added at 03:06 PM ---------- Previous post was at 02:54 PM ----------
The debrick image for the T model was just barely posted last week in Android Forms....and there is a thread in the questions section here on XDA that has it linked
Click to expand...
Click to collapse
Yep, I flashed it normally. Using Philz I got the Wicked 8 zip file and a couple of the addons that are available without any problems but since I don't like the Touchwiz UI too much I am currently running Conquest. Maybe try the full Wicked 8 zip? I did not try the barebones, but I can confirm that Wicked 8 works on the T model. It has the rotation issue but a couple of post ago I described how to get around that. Let me know if it works!
Sent from my SPH-L710 using XDA Free mobile app
luisro said:
Yep, I flashed it normally. Using Philz I got the Wicked 8 zip file and a couple of the addons that are available without any problems but since I don't like the Touchwiz UI too much I am currently running Conquest. Maybe try the full Wicked 8 zip? I did not try the barebones, but I can confirm that Wicked 8 works on the T model. It has the rotation issue but a couple of post ago I described how to get around that. Let me know if it works!
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
i was finally able to flash bare-bones i had to flash the updated kernel i used for Conquest beta 10
I'm glad! At least we can use Touchwiz based ROMs while we can find a way to create a kernel that is completely compatible with the T model. Is your rotation working correctly?
Sent from my SPH-L710 using XDA Free mobile app
luisro said:
I'm glad! At least we can use Touchwiz based ROMs while we can find a way to create a kernel that is completely compatible with the T model. Is your rotation working correctly?
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
Yes rotation is working and with the next few updates on CM side they will be fully working on the T model cause CM already updated a fix for the T model
I got spooked when the baseband disappeared and rotation was not working. Went back to stock. Of course you also seem to need the special 2.7 twrp in order to mount system. But the price was right.
Sent from my SPH-L710T using XDA Free mobile app
Q&A for Tweaked Lollipop Note 3 Coming soon
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Tweaked Lollipop Note 3 Coming soon. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
is this a rom a can flash?? do I have to flash any extra stuff??
You don't have to flash anything Extra at the moment it can be use as daily driver bugs still being repair update are coming
Sent from my SM-N900T using XDA Free mobile app
MasterX007 said:
You don't have to flash anything Extra at the moment it can be use as daily driver bugs still being repair update are coming
Sent from my SM-N900T using XDA Free mobile app
Click to expand...
Click to collapse
Idk what I did wrong i flashed then i was stuck at a bootload at the samsung note 3 screen..... But this has happen with all the tw lollipop roms i have tried to flash so i dont know what i am doing wrong
desean93 said:
Idk what I did wrong i flashed then i was stuck at a bootload at the samsung note 3 screen..... But this has happen with all the tw lollipop roms i have tried to flash so i dont know what i am doing wrong
Click to expand...
Click to collapse
What model of Note 3 are you using and recovery you using?
MasterX007 said:
What model of Note 3 are you using and recovery you using?
Click to expand...
Click to collapse
I have a Tmobile note 3 and i am using philz touch recovery
desean93 said:
I have a Tmobile note 3 and i am using philz touch recovery
Click to expand...
Click to collapse
in philz rec choose the option wipe to install clean rom and flash the Rom aafter just reboot the device let it boot its normal for it to take up to 10 minutes during the first boot
I am also on N900T it is working great
MasterX007 said:
in philz rec choose the option wipe to install clean rom and flash the Rom aafter just reboot the device let it boot its normal for it to take up to 10 minutes during the first boot
I am also on N900T it is working great
Click to expand...
Click to collapse
Ok.... Will try again So I dont need to flash a kernal?? For some reason I believe my problem is the kernal because any time I flash a custom rom and dont flash a kernal the rom doesnt want to boot up and Im stuck on the note 3 screen
desean93 said:
Ok.... Will try again So I dont need to flash a kernal?? For some reason I believe my problem is the kernal because any time I flash a custom rom and dont flash a kernal the rom doesnt want to boot up and Im stuck on the note 3 screen
Click to expand...
Click to collapse
no need to flash a kernel one is already provided in the Rom
MasterX007 said:
no need to flash a kernel one is already provided in the Rom
Click to expand...
Click to collapse
Ok.... Thank you so much!!! I will give it another try after this one didnt work... I had given up but I will try and flash again.... I will let you know the turnout
Thanks for the ROM. I'll be testing and report back on how it works for me.
One issue I immediately see if that wifi seems to not be working for me. Every time I try and turn it on, it is either greyed out and I can't toggle it, or if I am able to toggle it, it just doesn't do anything. I rebooted, still same issue. I think I flashed it properly (I wiped data, cache, dalvik, system), but I may try flashing again.
Has anyone else had this problem and is there a fix for this?
EDIT: Did a second full wipe and flash and still no wifi. Everything else seems to work connection wise, airplane mode, bluetooth, mobile data, just not wifi.
Already fix that problem
A new update should be here soon it is being uploading to mega wifi is fix
Sent from my SM-N900T using XDA Free mobile app
MasterX007 said:
Already fix that problem
A new update should be here soon it is being uploading to mega wifi is fix
Sent from my SM-N900T using XDA Free mobile app
Click to expand...
Click to collapse
Yup. That fixed it. Thanks.
I'm not having success getting Xposed Framework running on this ROM. Is there a way to get it working? Screenshot included.
want know how fix the heating and the loudness twerkv1 for n900t android 5.0
please can anyone tell me how to fix or conf the sound on this rom please
Techngro said:
I'm not having success getting Xposed Framework running on this ROM. Is there a way to get it working? Screenshot included.
Click to expand...
Click to collapse
Not yet compatible. Gotta wait for Xposed developer to make it compatible.
---------- Post added at 11:47 AM ---------- Previous post was at 11:46 AM ----------
mr adrian said:
please can anyone tell me how to fix or conf the sound on this rom please
Click to expand...
Click to collapse
You can look in the ROM thread for a fix...on page 4 or 5.
DPI change?
Hey, the ROM is still going smooth. No real issues so far (except my battery life isn't as good as before, but it's not terrible or anything).
I have been trying to change the DPI on this ROM, but I have not been able to make it stick. I have tried using the build prop editor app as well as directly editing the build prop via ES File Explorer. Neither has worked. Has anyone been able to change their DPI or is there something specific that I need to do to get it working?
Techngro said:
Hey, the ROM is still going smooth. No real issues so far (except my battery life isn't as good as before, but it's not terrible or anything).
I have been trying to change the DPI on this ROM, but I have not been able to make it stick. I have tried using the build prop editor app as well as directly editing the build prop via ES File Explorer. Neither has worked. Has anyone been able to change their DPI or is there something specific that I need to do to get it working?
Click to expand...
Click to collapse
Look in your battery stats see whats causing it
Sent from my SM-N9005 using XDA Free mobile app
I keep getting "invalid argument" when I try to download the mixerpath.xml for normal sound.. Is there another link for it?
bigdreco said:
I keep getting "invalid argument" when I try to download the mixerpath.xml for normal sound.. Is there another link for it?
Click to expand...
Click to collapse
Alright im going to post another link
Sent from my SM-N9005 using XDA Free mobile app