Related
Ok so i've been messing with some other kernels to see if any of them would work, and needed a quick way to get out of bootloops. I haven't seen one yet so I mad a flashable Stock Kernel. Have fun.
http://www.androidfilehost.com/?fid=23329332407576394
Have you tried this with an international 4.4.2 rom? I tried an international rom earlier but wifi wouldnt work. Any ideas?
jimmydigital00 said:
Have you tried this with an international 4.4.2 rom? I tried an international rom earlier but wifi wouldnt work. Any ideas?
Click to expand...
Click to collapse
Im on Echoe rom and everything works fine?
I didn't do anything special either. Just on the 4.4 bootloader. If your on 4.3 bootloader then maybe flash the wifi/bluetooth/nfc fix
_INSPIREed said:
Im on Echoe rom and everything works fine?
I didn't do anything special either. Just on the 4.4 bootloader. If your on 4.3 bootloader then maybe flash the wifi/bluetooth/nfc fix
Click to expand...
Click to collapse
How did you get 4.4 intl rom to work on tmobile n3
Are you on 4.4.2 with the new bootloader? I did the OTA update, rooted, jnstalled twrp recovery and then tried instalking an international rom. It booted but the wifi did not work.
iamolu said:
How did you get 4.4 intl rom to work on tmobile n3
Click to expand...
Click to collapse
jimmydigital00 said:
Are you on 4.4.2 with the new bootloader? I did the OTA update, rooted, jnstalled twrp recovery and then tried instalking an international rom. It booted but the wifi did not work.
Click to expand...
Click to collapse
Yes I'm on 4.4 bootloader. I flashed the tmobile 4.4 nb4 tar. via odin. Flashed CF auto root n9005 version via Odin, and then flashed the TWRP .tar that @bigbiff posted via odin as well. Then in TWRP flashed the latest Philz recovery zip that works with 4.4 bootloader (thats my preference, I like PhilZ.) Then just downloaded and installed Echoe. By the way I had no idea International 4.4 Roms were sooo much faster than ours...its quite noticeable. WIFI and everything works out of box. no need to flash any kernels or anything.
I get stuck at Samsung Note 3 Screen..
Crazywhitie said:
I get stuck at Samsung Note 3 Screen..
Click to expand...
Click to collapse
gonna need more info if you want some help bud
_INSPIREed said:
Yes I'm on 4.4 bootloader. I flashed the tmobile 4.4 nb4 tar. via odin. Flashed CF auto root n9005 version via Odin, and then flashed the TWRP .tar that @bigbiff posted via odin as well. Then in TWRP flashed the latest Philz recovery zip that works with 4.4 bootloader (thats my preference, I like PhilZ.) Then just downloaded and installed Echoe. By the way I had no idea International 4.4 Roms were sooo much faster than ours...its quite noticeable. WIFI and everything works out of box. no need to flash any kernels or anything.
Click to expand...
Click to collapse
Can you send me the link to the Philz recover you used? I tried installing Sweet Rom (international) and it wiped my internal storage. Want to try Philz to see if that will resove that problem.
jimmydigital00 said:
Can you send me the link to the Philz recover you used? I tried installing Sweet Rom (international) and it wiped my internal storage. Want to try Philz to see if that will resove that problem.
Click to expand...
Click to collapse
its not the recovery, it's the updater script included in some international roms, you have to modify the updater script so that it doesnt do wipe internal. follow these instructions.
1. Download ROM, open .zip with winRAR or 7zip.
2. Navigate to META-INF\com\google\android
3. Drag updater-script to desktop and open in Notepad++ (http://notepad-plus-plus.org)
4. Delete the following... http://imgur.com/F7rdFCo
5. Save (make sure you save as the same format - just click save and not save as)
6. Drag back into same directory and overwrite the previous updater-script in the rom .zip
_INSPIREed said:
its not the recovery, it's the updater script included in some international roms, you have to modify the updater script so that it doesnt do wipe internal. follow these instructions.
1. Download ROM, open .zip with winRAR or 7zip.
2. Navigate to META-INF\com\google\android
3. Drag updater-script to desktop and open in Notepad++ (http://notepad-plus-plus.org)
4. Delete the following... http://imgur.com/F7rdFCo
5. Save (make sure you save as the same format - just click save and not save as)
6. Drag back into same directory and overwrite the previous updater-script in the rom .zip
Click to expand...
Click to collapse
Your the man!! Thanks
jimmydigital00 said:
Your the man!! Thanks
Click to expand...
Click to collapse
this work like a charm, it was made for 900W8 device which is same at tmobile n900t. Now we can flash any n9005 rom w/this WIFI,NFC,BT fix
http://fs1.androidfilesharing.com/74f88da21978feed#.UxjL5OddVss currently running SweetRom w/no issue about to try Omega Rom..Thanks to @Oogar
FANTASTIC SIR...good job, well needed!
Thank you.
iamolu said:
this work like a charm, it was made for 900W8 device which is same at tmobile n900t. Now we can flash any n9005 rom w/this WIFI,NFC,BT fix
http://fs1.androidfilesharing.com/74f88da21978feed#.UxjL5OddVss currently running SweetRom w/no issue about to try Omega Rom..Thanks to @Oogar
Click to expand...
Click to collapse
LITERALLY THAT MADE ME ROLL AROUND ON THE GROUND AND LAUGH MY ASS OFF.
That my friend was not made for the Canadian Variant. I and my friend MISCOM, made that fix when we started putting out Int. Roms for TMO and Canadian phones. If you go the the Stainless thread, you will see the original posting of that fix. That's why when you flash that fix it says, made by Miscom. All somebody did was change the name of the file and stick it up on other threads. I've in months only seen one person credit Miscom for the work we did. Not mad. Doesn't bother me, we made the fix and said here guys go grab it and put it on the N9005 page so everybody can fix this issue.
dragonstalker said:
LITERALLY THAT MADE ME ROLL AROUND ON THE GROUND AND LAUGH MY ASS OFF.
That my friend was not made for the Canadian Variant. I and my friend MISCOM, made that fix when we started putting out Int. Roms for TMO and Canadian phones. If you go the the Stainless thread, you will see the original posting of that fix. That's why when you flash that fix it says, made by Miscom. All somebody did was change the name of the file and stick it up on other threads. I've in months only seen one person credit Miscom for the work we did. Not mad. Doesn't bother me, we made the fix and said here guys go grab it and put it on the N9005 page so everybody can fix this issue.
Click to expand...
Click to collapse
@dragonstalker I had no idea, i came across the thread and tried it and it worked for me. I am just a user and not trying to step on n e one bad side because i know how much work y'all developer put in. With that been said thanks @miscom and @dragonstalker for the WIFI-BT-NFC fix. I used the 4.3 version but had no idea the 4.4 version wasn't original, by who posted it or started the thread no way for me to know that
iamolu said:
@dragonstalker I had no idea, i came across the thread and tried it and it worked for me. I am just a user and not trying to step on n e one bad side because i know how much work y'all developer put in. With that been said thanks @miscom and @dragonstalker for the WIFI-BT-NFC fix. I used the 4.3 version but had no idea the 4.4 version wasn't original, by who posted it or started the thread no way for me to know that
Click to expand...
Click to collapse
I wasn't blaming you. It's opensource, not like we wrote new code to do it. We just took the time to figure out how to fix make everything work.
Its funny because as you stated you had no way of knowing, people renaming it and posted it as their work do. This is probably the 5th name i've seen for this. It doesn't make me mad. Actually it makes me smile that something that was put out is still being used.
iamolu said:
this work like a charm, it was made for 900W8 device which is same at tmobile n900t. Now we can flash any n9005 rom w/this WIFI,NFC,BT fix
http://fs1.androidfilesharing.com/74f88da21978feed#.UxjL5OddVss currently running SweetRom w/no issue about to try Omega Rom..Thanks to @Oogar
Click to expand...
Click to collapse
Do you think Flash this will fix ax nb5 NFC problem
Sent from my SM-N9005 using XDA Premium 4 mobile app
iamolu said:
this work like a charm, it was made for 900W8 device which is same at tmobile n900t. Now we can flash any n9005 rom w/this WIFI,NFC,BT fix
http://fs1.androidfilesharing.com/74f88da21978feed#.UxjL5OddVss currently running SweetRom w/no issue about to try Omega Rom..Thanks to @Oogar
Click to expand...
Click to collapse
Did you do anything special to flash SweetRom? I am getting stuck at the Samsung Galaxy Note 3 screen (Set warranty Bit: kernel)
I get stuck on this screen with the stock kernel and also when I add a 4.4.2 kernel. Any ideas?
jimmydigital00 said:
Did you do anything special to flash SweetRom? I am getting stuck at the Samsung Galaxy Note 3 screen (Set warranty Bit: kernel)
I get stuck on this screen with the stock kernel and also when I add a 4.4.2 kernel. Any ideas?
Click to expand...
Click to collapse
What kernels have you tried. Do Wootever's latest . That or Civz. That's what the guys are running on Int. Tmo roms right now that i know of working.
dragonstalker said:
What kernels have you tried. Do Wootever's latest . That or Civz. That's what the guys are running on Int. Tmo roms right now that i know of working.
Click to expand...
Click to collapse
I tried civZ-SnapKat-Rev2.1-sm_n900t-4.4.2.zip
I will look for Wootever's now. Is it posted on international forum or on the t-mobile?
Thanks
When I tried to install the Justin's T-Mobile ROM to LS980 with ZVA version through TWRP, I got a boot loop (TWRP recovery image was installed via Flasify). Restored the factory ROM and tried to flash again, but I got the same boot loop. Is it due to the fact that the phone is on ZVA?
I read in the forum that I can use FreeGee to flash TWRP for LS980 ZVA, but it seems it does not help as well.
Do I need to go back to earlier version (ZV8 or ZV9?) to flash the T-Mobile ROM or is there a way to flash the ROM without going back?
Thanks for help in advance!
here is what i did
cherishzm said:
When I tried to install the Justin's T-Mobile ROM to LS980 with ZVA version through TWRP, I got a boot loop (TWRP recovery image was installed via Flasify). Restored the factory ROM and tried to flash again, but I got the same boot loop. Is it due to the fact that the phone is on ZVA?
I read in the forum that I can use FreeGee to flash TWRP for LS980 ZVA, but it seems it does not help as well.
Do I need to go back to earlier version (ZV8 or ZV9?) to flash the T-Mobile ROM or is there a way to flash the ROM without going back?
Thanks for help in advance!
Click to expand...
Click to collapse
I flashed the zv 7aboot file installled lokied twrp then from twrp did full wipe installed rom then flashed ls 980zv8 radio
do not reboot after flashing rom flash the radio then boot up you should be good. i got this info from the the tmobile cm11 working on sprint thread
it worked for me. I would check out that thread if i were you. hope it helps!
stillblaze01 said:
I flashed the zv 7aboot file installled lokied twrp then from twrp did full wipe installed rom then flashed ls 980zv8 radio
do not reboot after flashing rom flash the radio then boot up you should be good. i got this info from the the tmobile cm11 working on sprint thread
it worked for me. I would check out that thread if i were you. hope it helps!
Click to expand...
Click to collapse
Thanks for the reply. Do you know where I can find files to flash radio? I'll read the cm11 thread and see if I can find more info on that.
EDIT:Flashed ZV8 Radio after flashing the T-Mobile ROM it appears booting but I'm getting following error messages:
Unfortunately, the process com.android.phone has stopped
Unfortunately, VoIP call has stopped.
These messages keep popping up after pressing OK so I cannot get to the main screen.
What do I need to do now?
Well, I tried to flash the T-Mobile ROM again and it works fine now (without flashing the ZV8 again after flashing the ROM)!
cherishzm said:
Well, I tried to flash the T-Mobile ROM again and it works fine now (without flashing the ZV8 again after flashing the ROM)!
Click to expand...
Click to collapse
once you flash a radio like you stated. flashed the ZV8 after the rom you dont ever need to do that unless you recover from a TOT. file or switch your radio at some point. once you flash it your good man
and just in-case you didn't know your posting questions in the development area i see you did it twice so i figured you might think your in Q&A
are you using a t-mobile or att based sim card?
Shouldn't this post be in General or Q&A???
Are you good?
if you need any files or help let me know id be happy to help
Which rom is Justin's rom?? I have been searching and I cannot find something named justin's rom.
Can someone kindly point me to a link of the rom.
Thank you for your time.
jub2k3 said:
Which rom is Justin's rom?? I have been searching and I cannot find something named justin's rom.
Can someone kindly point me to a link of the rom.
Thank you for your time.
Click to expand...
Click to collapse
https://docs.google.com/file/d/0B6HYWZRx8JLsZm9rVU5sWjZSTjA/edit?usp=docslist_api
I like my phones like I like my women.... flexible
Got the link thanks. Now im trying to find a clean efs because my backup with freegee doesnt install and the one ioroot was supposed to create does not exist.
Sent from my GT-N5110 using Tapatalk
Google Play Store - No Connection Issue
Hello everyone,
I have flashed Justin's T-Mobile ROM onto my LS980 (Sprint G2) successfully after flashing ZV8 radio.
However, Google Play Store started giving me an error message - 'No Connection'.
I tried to follow the fix in the following thread but when I opened the hosts file there was already " 127.0.0.1 localhost" at the first line. I deleted the hosts file entirely and restarted the phone but it did not work either.
http://forum.xda-developers.com/showthread.php?t=2273994
Does anyone know what I need to do to get Play Store working again? When I factory reset it, it will start working but after few downloads, it stops working and displays the same 'No Connection' error message.
By the way, I have force closed 'automatic update' app disabled notification. Is it possibly why?
Any help will be appreciated!!
stillblaze01 said:
if you need any files or help let me know id be happy to help
Click to expand...
Click to collapse
Im having issues. The link for the Justin rom is no longer available. i lost my recovery and can only go into download mode. i have no idea how to flash recovery through adb. Do need to install the T Mobile drivers? I have the sprint drivers already installed. The phone doesnt stay on long enough for me to use the simple tool either.
DL mode
bhzmafia said:
Im having issues. The link for the Justin rom is no longer available. i lost my recovery and can only go into download mode. i have no idea how to flash recovery through adb. Do need to install the T Mobile drivers? I have the sprint drivers already installed. The phone doesnt stay on long enough for me to use the simple tool either.
Click to expand...
Click to collapse
In down load mode I would flash tot file then root and install rom if you still need a rom I have a stock tmobile rom not sure if its Justins and I should have a Cm11 running around let me know
I just recieved a sprint s3 sph-l710 with 4.4.2 from a friend. I rooted and installed trwp recovery but after looking through the roms I cant figure out which one would work. also I read some of the roms have a problem with LTE?
teknoweanie said:
I just recieved a sprint s3 sph-l710 with 4.4.2 from a friend. I rooted and installed trwp recovery but after looking through the roms I cant figure out which one would work. also I read some of the roms have a problem with LTE?
Click to expand...
Click to collapse
Check this thread: http://forum.xda-developers.com/galaxy-s3-sprint/development
Basically, the most stable ones are non-AOSP/CM roms. The others run pretty well, but may have a little issue here or there. The WickedX series is probably the most active TouchWiz rom (close to stock) that will have the fewest bugs.
Hmm when I installed thebarebones wicked x rom the phone seemed to heat up excessively. Most likely from the theme. It was sitting around 114 degrees Fahrenheit. on the stock one it goes from 80 sitting at about 95 to 104 degrees Fahrenheit when im using the stock Android browser.
teknoweanie said:
Hmm when I installed thebarebones wicked x rom the phone seemed to heat up excessively. Most likely from the theme. It was sitting around 114 degrees Fahrenheit. on the stock one it goes from 80 sitting at about 95 to 104 degrees Fahrenheit when im using the stock Android browser.
Click to expand...
Click to collapse
I prefer AICP 9.0 ( http://dwnld.aicp-rom.com/?device=d2spr ) but that's because I hate Touchwiz (stock) and I want lollipop. The latest nightlies are actually really stable, but if you want a for sure stable release I'd go with a kitkat d2lte ROM or touchwiz.
Is there a description of what's removed and changed for aicp? Or some interesting features? Looking for really barebones with most stuff removed. I got this stock one im using down to 1gb free ram so far. Seems to keep it cooler not doing so many processes all at once. Also i can down clock the cpu to below 1ghz without all the background stuff using up the excess processing power. Doesn't feel so much like a pocket warmer even while quickly going through pages.
Edit: have you had any problems with 9.0? It seems like data doesn't work for me on version 8 is there some fix to flash for 8 or should I just try 9?
If you're on the actual sprint (not virgin mobile, boost, etc) then your data should work fine on 9.0. AICP is not barebones, however. I'd think of it as cm with some good added features. However, I have like 1gb of free ram on aicp idle.
---------- Post added at 02:07 AM ---------- Previous post was at 02:06 AM ----------
9.0 works great for me on my virgin mobile s3. The latest nightlies are very stable.
Im on sprint.. Do i need to update firmware or flash a radio for it to work? Im using 4.4.2 stock. Also just to make sure im not doing it wrong. What are steps for flashing this specific rom?
teknoweanie said:
Im on sprint.. Do i need to update firmware or flash a radio for it to work? Im using 4.4.2 stock. Also just to make sure im not doing it wrong. What are steps for flashing this specific rom?
Click to expand...
Click to collapse
You are on ND8 if you are running that rom. Some people have reported success and some have not using that firmware. NJ2 seems to be better for running lollipop roms.
MAKE UP A NANDROID BAKCUP OF YOUR CURRENT SET UP
To update to NJ2: http://www.sammobile.com/firmwares/download/41671/L710VPUDNJ2_L710SPRDNJ2_SPR/
Flash a recovery via ODIN, it is the program you used in the above step: http://forum.xda-developers.com/showthread.php?t=2201860
There is also TWRP somewhere, but even though Philz isn't being developed, I haven' t had any issues with it. But if you want to recover your previous setup, it is probably best to use the same recovery as before.
Restore your old setup.
Most roms come with instructions for installation in the post. Basically, nAndroid backup, wipe data/system, install zip of rom, and then GApps if needed. Most custom roms are already rooted about of the box.
Do you have a link to the firmware that doesnt require me to register?
teknoweanie said:
Do you have a link to the firmware that doesnt require me to register?
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal.../stock-l710vpudnj2-pc-odin-flashable-t3007847
thank you! ill try to update it later. also if I update the firmware will i still be able to flash the back to a older rom? i know there probably isnt and you most likely would of posted it first but is there a firmware i can just flash from trwp recovery?
EDIT: also i am teknoweanie i just can never remember my password when i change computers/phones. lol ^^
Kannz2 said:
thank you! ill try to update it later. also if I update the firmware will i still be able to flash the back to a older rom? i know there probably isnt and you most likely would of posted it first but is there a firmware i can just flash from trwp recovery?
EDIT: also i am teknoweanie i just can never remember my password when i change computers/phones. lol ^^
Click to expand...
Click to collapse
No. You need to use odin for the firmware upgrade. Just make a backup of your rom before flashing. If you are using twrp now, just flash that tar through odin when you finish. Then, you can reboot to recovery and restore that backup after flashing the new firmware. And everything will be the same. The whole process will probably take you 30.minutes.
Hello!
I am trying to unlock my S3 (SGH-I747m) but the unlock code is not successful. I found a thread which made me hopeful but couldn't try the dial method as the dialing *#197328640# does not work on CM. http://forum.xda-developers.com/showthread.php?t=2712153
I know for a fact that the CM installation is _not_ the reason the unlock code is not working. This is because I had tried to unlock this phone way before I installed CM and it didn't work back then. Thinking back, I may have done something to the settings (reached via *#197328640#) over a year ago and I suspect that is why the unlock code is not working. Now, I would love to try out the steps listed in the aforementioned XDA thread but can't get to those options as they are not part of CM.
Is there a way for me to unlock (I have the code) this phone (CM installed) without reflashing stock Samsung ROM first?
Thank you.
ohTwadi said:
Hello!
I am trying to unlock my S3 (SGH-I747m) but the unlock code is not successful. I found a thread which made me hopeful but couldn't try the dial method as the dialing *#197328640# does not work on CM. http://forum.xda-developers.com/showthread.php?t=2712153
I know for a fact that the CM installation is _not_ the reason the unlock code is not working. This is because I had tried to unlock this phone way before I installed CM and it didn't work back then. Thinking back, I may have done something to the settings (reached via *#197328640#) over a year ago and I suspect that is why the unlock code is not working. Now, I would love to try out the steps listed in the aforementioned XDA thread but can't get to those options as they are not part of CM.
Is there a way for me to unlock (I have the code) this phone (CM installed) without reflashing stock Samsung ROM first?
Thank you.
Click to expand...
Click to collapse
The most likely reason that the unlock code is not successful is that you are no longer on the 4.1.1 modem. If you are not on the stock dialer the codes do not work even if you are on the 4.1.1 modem. And even on the stock dialer, not all codes are present after reaching the 4.3 modem.
IIRC
CM ROMs do not have the stock dialler and it is probably the stock dialler that you need to enter the unlock code.
audit13 said:
CM ROMs do not have the stock dialler and it is probably the stock dialler that you need to enter the unlock code.
Click to expand...
Click to collapse
Thanks!
I should mention that I can enter the unlock code just fine after rebooting the phone with another carrier SIM, just that the code is unsuccessful in unlocking the phone.
Since I am running Android 4.4.4, is it safe to simply download the stock 4.4.4 dialer and simple run the apk file on the phone?
http://www.androidpolice.com/2013/1...ll-it-manually-on-other-kitkat-roms-download/
I believe the phone will need the stock Samsung dialler.
I am not sure but the moto dialer may be an aosp dialer.
audit13 said:
I believe the phone will need the stock Samsung dialler.
I am not sure but the moto dialer may be an aosp dialer.
Click to expand...
Click to collapse
Oh okay. This is going to sound dumb, I'm not sure how to get the stock Samsung dialer which would be compatible with CM 11, i.e. Android 4.4.4.
Once I have it, I can simply flash it via recovery, correct?
What bootloader is on your phone? This is important to know before flashing anything.
audit13 said:
What bootloader is on your phone? This is important to know before flashing anything.
Click to expand...
Click to collapse
Samsung Phone Info app says the bootloader is I747MVLUFNK2
I suggest flashing back to stock using the nk2 firmware from sammobile: http://www.sammobile.com/firmwares/database/SGH-I747M/
Once you unlock the phone using the code, you can flash a custom recovery and re-flash cm.
audit13 said:
I suggest flashing back to stock using the nk2 firmware from sammobile: http://www.sammobile.com/firmwares/database/SGH-I747M/
Once you unlock the phone using the code, you can flash a custom recovery and re-flash cm.
Click to expand...
Click to collapse
I was afraid that was going to be the only option but was trying to avoid as I had a tough time flashing CM in the first place. Oh well, I will give this a shot soon. Thanks for all your help!
Flashing CM should be pretty easy.
After you unlock the phone, use Odin to flash TWRP. Boot into TWRP, create a nandroid backup. Copy CM and Gapps to your phone (internal or external memory), and flash CM11 and Gapps.
audit13 said:
Flashing CM should be pretty easy.
After you unlock the phone, use Odin to flash TWRP. Boot into TWRP, create a nandroid backup. Copy CM and Gapps to your phone (internal or external memory), and flash CM11 and Gapps.
Click to expand...
Click to collapse
As I read your post, very little of it made sense but I was able to work through it one item at a time. I inadvertently downloaded CM12 nightly and now running Android 5.1.1. Oh well, at least is not Samsung's crappy version.
Again, thank you for all the help!
Edit: Oh and phone was unlocked easily once I went back to stock Samsung ROM.
Glad you got it working. You could have sent me a PM to ask for more detailed instructions. I wasn't sure how familiar you were with flashing the s3 via Odin, etc.
audit13 said:
Glad you got it working. You could have sent me a PM to ask for more detailed instructions. I wasn't sure how familiar you were with flashing the s3 via Odin, etc.
Click to expand...
Click to collapse
Thanks. I didn't want to bother anymore than I already was. Plus, one has to learn at some point how to do these things anyway. So it worked out alright.
We're all here to help and I don't mind helping when I can. Others on this forum have helped me through many phones, including my s3 which I haven't had for 18 months.
I loaded CM-13.0 nightly and have Been updating as the updates come but when I go to make a call it takes forever to go through and start ringing and sometimes it r just hangs up. The data keeps going from LTE to nothing and no SIM . I can't get mms either. Can someone tell me what to do.thanks.
Sent from my SGH-T999 using Tapatalk
HUCCG said:
I loaded CM-13.0 nightly and have Been updating as the updates come but when I go to make a call it takes forever to go through and start ringing and sometimes it r just hangs up. The data keeps going from LTE to nothing and no SIM . I can't get mms either. Can someone tell me what to do.thanks.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Same thing is happening to me. I've tried using OctOs M and now I am on PacRom 6.0.1 and I am having the same "No sim card" error. I can text and call, but no Data whatsoever.
Have you tried changing your APN settings for your network on your phone?
wmzed said:
Same thing is happening to me. I've tried using OctOs M and now I am on PacRom 6.0.1 and I am having the same "No sim card" error. I can text and call, but no Data whatsoever.
Have you tried changing your APN settings for your network on your phone?
Click to expand...
Click to collapse
are you on the latest baseband for your phone?
ratchetrizzo said:
are you on the latest baseband for your phone?
Click to expand...
Click to collapse
My stock OS Is 4.1.2 and is running Baseband UVAMB7. Do I need to go for the higher updates for the LTE to work?
wmzed said:
My stock OS Is 4.1.2 and is running Baseband UVAMB7. Do I need to go for the higher updates for the LTE to work?
Click to expand...
Click to collapse
I think you need to be on UVUBOH1.
https://forum.xda-developers.com/showthread.php?t=1949687 has the list of FW and it looks like you are using a super super old baseband.
ratchetrizzo said:
I think you need to be on UVUBOH1.
https://forum.xda-developers.com/showthread.php?t=1949687 has the list of FW and it looks like you are using a super super old baseband.
Click to expand...
Click to collapse
Do I need to use ODIN for this? I tried installing UVUBOH1 with TWRP, but I get an error when I installing it:
"could not find 'META-INF/com/google/android/update-binary' in the zip file"
wmzed said:
Do I need to use ODIN for this? I tried installing UVUBOH1 with TWRP, but I get an error when I installing it:
"could not find 'META-INF/com/google/android/update-binary' in the zip file"
Click to expand...
Click to collapse
Yes, download https://www.androidfilehost.com/?fid=24052804347821137
NOTE, if you click on "UVUBOH1" and not the androidfilehost link in the FW thread, it links you to the wrong FW and you'll flash UVUBNC1! Make sure you click the androidfilehost link underneath UVUB0H1.
Then flash it with odin.
Afterwards let it reboot and upgrade, then odin TWRP back and either restore a nandroid or flash the rom of your choosing
Oh also, if you're still on 4.1 and on a touchwiz rom, you may want to factory unlock it before you upgrade.. Just because you can. Follow the unlock thread on here
ratchetrizzo said:
Yes, download https://www.androidfilehost.com/?fid=24052804347821137
NOTE, if you click on "UVUBOH1" and not the androidfilehost link in the FW thread, it links you to the wrong FW and you'll flash UVUBNC1! Make sure you click the androidfilehost link underneath UVUB0H1.
Then flash it with odin.
Afterwards let it reboot and upgrade, then odin TWRP back and either restore a nandroid or flash the rom of your choosing
Oh also, if you're still on 4.1 and on a touchwiz rom, you may want to factory unlock it before you upgrade.. Just because you can. Follow the unlock thread on here
Click to expand...
Click to collapse
Thank you so much! I will try this out soon and respond with the results! And I had already unlocked my device :. I had to root and use the RegionLock app to unlock it, as the *#197328640# menu option did not work for me.
wmzed said:
Thank you so much! I will try this out soon and respond with the results! And I had already unlocked my device :. I had to root and use the RegionLock app to unlock it, as the *#197328640# menu option did not work for me.
Click to expand...
Click to collapse
how did you make out?
ratchetrizzo said:
how did you make out?
Click to expand...
Click to collapse
Was quite a bit of trouble at first . I managed to download and flash the software. flashed TWRP via odin.
Then through TWRP, I rooted by using the Knox remover zip (as i was on official 4.3, my service signal did shoot up to normal again!). Installed SuperSU.
Now when I try to flash any ROM via TWRP it gives errors such as "Status 7", or error reading MD5 when I try to backup software.
wmzed said:
Was quite a bit of trouble at first . I managed to download and flash the software. flashed TWRP via odin.
Then through TWRP, I rooted by using the Knox remover zip (as i was on official 4.3, my service signal did shoot up to normal again!). Installed SuperSU.
Now when I try to flash any ROM via TWRP it gives errors such as "Status 7", or error reading MD5 when I try to backup software.
Click to expand...
Click to collapse
Make sure twrp is up to date for d2tmo, and make sure the rom you are flashing is 4.3 or later. I'm pretty sure that once you're on the latest 4.3 rom you can't flash anything lower
ratchetrizzo said:
Make sure twrp is up to date for d2tmo, and make sure the rom you are flashing is 4.3 or later. I'm pretty sure that once you're on the latest 4.3 rom you can't flash anything lower
Click to expand...
Click to collapse
Got the latest TWRP running, but still the same issue trying to flash OctOS M, PACROM 5.0.1, etc.
wmzed said:
Got the latest TWRP running, but still the same issue trying to flash OctOS M, PACROM 5.0.1, etc.
Click to expand...
Click to collapse
That's strange, I'm using 3.0.2.0 and the latest 999L baseband and I haven't had any issues with flashing.
I'm Using the MM pac rom but I've tried CM14.1 nightly builds with no problem
ratchetrizzo said:
That's strange, I'm using 3.0.2.0 and the latest 999L baseband and I haven't had any issues with flashing.
I'm Using the MM pac rom but I've tried CM14.1 nightly builds with no problem
Click to expand...
Click to collapse
I have finally managed to figure it out. You need to completely format the entire ROM currently installed from your phone. Once that is done, you can add any ROM to install properly. I'm running well on OctOS-N 3/17/2017 build.
Thanks all for your help.