Related
Hi, everyone. This is my first post on XDA. I'm in Eastern Canada, and my local area just recently got LTE coverage, so I'm keen on taking advantage, but I'm on the international Note 3. I just recently upgraded from 4.3 to 4.4.2. Rooted with towelroot. Obviously Bell insists that there's absolutely no way I can get on their LTE network, although research suggests otherwise. I should note that my signal strength is typically bad (and erratic) compared to my friends'. Too many details are better than not enough, so here we go.
Model: SM-N9005
Model name: GALAXY Note 3
Country of origin: Made in Vietnam
Manufacturing date: 2013.09.11
Knox: 0x0
Original/Firmware/Active CSC Code: XME
CSC Country/ISO: Malaysia (MY)
Product code: SM-9005ZKEXME
Version: Android 4.4.2
Build date: Aug 28, 2014
Bootloader/Baseband/PDA: N9005XXUGNH1
CSC: N9005OLBGNH1
Kernel: 3.4.0-1955971, [email protected] #1, Thu Aug 28
Build: KOT49H.N9005XXUGNH1
Changelist: 1955971
Active mobile operator name: Bell
Active mobile network code: 302610
1) I assume that there's no easy way to go about this, so I'm wondering if it's possible to "convert" the SM-N9005 to a SM-N900W8 (Bell Note 3), so to speak? In other words, can I safely use Odin to change my phone to read as below?
BMC (Bell Canada)
PDA/MODEM: N900W8VLUCNB7
CSC: N900W8OYACNB7
And if so, would LTE then work? Currently I have these bands available: 1, 3, 5, 7, 8, 20, but I need many more than that.
2) If the above outline won't work, will I need to use the method from the following thread?
http://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059
This looks rather heavy for my level experience, as I've never used custom firmware or kernels, and I'd prefer not to trip knox, if possible.
I know there's a fair amount of material on this, but I wanted to get insight on my particular situation before I make any reckless attempts.
Thank you in advance, for any help or direction.
frosty400 said:
I'd prefer not to trip knox, if possible.
Click to expand...
Click to collapse
You will trip KNOX regardless whether you mod or flash a different model's modem.
Best way is to try unlock the bands manually instead of attempting to flash another model's baseband as that may cause a permanent brick in the modem level. By modding you can always reflash.
Remember to take an EFS backup, by flashing TWRP then backing up EFS and dumping it on your computer just in case.
Sent from my OnePlus One using Tapatalk VIP
Thanks a lot, nicholaschum. I've since read up on it some more, and I'm definitely not alone on wanting to do this. Given the complexity of the band-enabling process, it may just be easier to sell my N3 and invest in a N4 directly from Bell. I'd hate to screw something up and be unable to return it to its original state.
frosty400 said:
Thanks a lot, nicholaschum. I've since read up on it some more, and I'm definitely not alone on wanting to do this. Given the complexity of the band-enabling process, it may just be easier to sell my N3 and invest in a N4 directly from Bell. I'd hate to screw something up and be unable to return it to its original state.
Click to expand...
Click to collapse
It's not so complex. You can follow 32 steps in the Quick Start Guide of that thread.
You don;t need to calculate NV items manually. You can use Qualcomm NV Calculator app to calculate.
You even can try that guide with your stock om/kernel and see if the NV items stick? If they stick after reboot, that's OK. If they will not stick, then you will need the custom kernel.
Thanks, vndnguyen. My concern is that I might mess something up throughout the process and brick my phone, or render it unusable. That isn't an option at this point, or a risk I'm quite willing to take. I assume there are risks involved here. But are you saying that the worst that can happen if I try this on a stock rom/kernel that the NV items just simply won't stick? No harm done? I'd prefer to hear from someone who's done this on the same model with the same stock rom/kernel, only because I'm not well versed in this type of thing.
PS - I assume by "then you will need the stock kernel", you meant 'custom kernel'.
frosty400 said:
Thanks, vndnguyen. My concern is that I might mess something up throughout the process and brick my phone, or render it unusable. That isn't an option at this point, or a risk I'm quite willing to take. I assume there are risks involved here. But are you saying that the worst that can happen if I try this on a stock rom/kernel that the NV items just simply won't stick? No harm done? I'd prefer to hear from someone who's done this on the same model with the same stock rom/kernel, only because I'm not well versed in this type of thing.
PS - I assume by "then you will need the stock kernel", you meant 'custom kernel'.
Click to expand...
Click to collapse
Yes, my typo, I have edited my post. Sorry.
I personally didn't try that instruction, as I don't need to add bands at the moment.
In any case, I appreciate your help. I'm guessing that I would indeed need a custom rom/kernel to have any chance at success, only because nothing ever goes how I hope it does
It's too bad there wasn't a 'batch' app to help automate at least some of the process. To add more bands, open 'band-adding app' and click 'add more bands' :laugh:
frosty400 said:
...
It's too bad there wasn't a 'batch' app to help automate at least some of the process. To add more bands, open 'band-adding app' and click 'add more bands' :laugh:
Click to expand...
Click to collapse
If you read the Quick Start Guide, you will see there are 32 steps and they are not too complex. The most hard thing is calculation NV items, and you can use Qualcomm NV Calculator to calculate. All other steps are easy to understand. If you need more help at any steps in that guide, please let me know.
Thanks again, vndnguyen. If I knew it would work on my stock rom/kernel, I might attempt it, but I don't really have the time to spare if there's no guarantee that it will. I'd end up having to commit more time to a custom rom/kernel, wherein I'm sure something would go wrong. My problem is, once I start something, I can't get away from it In fact, I should be working right now - not posting here
Hi, all. I didn't make it far in the band unlock process because I can't even seem to get into diagnostic mode.
As soon as I go into USB settings and select CP, the below USB SETTINGS section disappears, and underneath CP is "OK" and "Reboot". It doesn't seem as if I can get it to stick on CP, or choose the below USB SETTINGS simultaneously (but it does say "Saved" after clicking OK). If I select 'RNDIS + DM + Modem' first and then CP, it does appear to take both settings, but it never shows both settings at the same time so I don't really know. Also can't seem to have USB debugging checked simultaneously, or else it won't even show up in device manager when plugged in. It does show up if I leave USB debugging unchecked, but again, not sure if I'm really in diagnostic mode. Not sure if this is related, but when I go to *#9090# it says:
DIAG CONFIG
NOT SUPPORTED
I've tried several drivers (uninstalled, reinstalled) both automatically and manually, and tried putting kies on and off, many reboots of both PC and phone, different USB ports, etc.
IN QPST there's a checkbox to show only diagnostic ports. If I uncheck this box, I can select something, but don't think that helps me. I'm getting the feeling that diagnostic mode is blocked or disabled. Any ideas? Thanks.
frosty400 said:
Hi, all. I didn't make it far in the band unlock process because I can't even seem to get into diagnostic mode.
As soon as I go into USB settings and select CP, the below USB SETTINGS section disappears, and underneath CP is "OK" and "Reboot". It doesn't seem as if I can get it to stick on CP, or choose the below USB SETTINGS simultaneously (but it does say "Saved" after clicking OK). If I select 'RNDIS + DM + Modem' first and then CP, it does appear to take both settings, but it never shows both settings at the same time so I don't really know. Also can't seem to have USB debugging checked simultaneously, or else it won't even show up in device manager when plugged in. It does show up if I leave USB debugging unchecked, but again, not sure if I'm really in diagnostic mode. Not sure if this is related, but when I go to *#9090# it says:
DIAG CONFIG
NOT SUPPORTED
I've tried several drivers (uninstalled, reinstalled) both automatically and manually, and tried putting kies on and off, many reboots of both PC and phone, different USB ports, etc.
IN QPST there's a checkbox to show only diagnostic ports. If I uncheck this box, I can select something, but don't think that helps me. I'm getting the feeling that diagnostic mode is blocked or disabled. Any ideas? Thanks.
Click to expand...
Click to collapse
I've done a lot of exploration on the bands unlocking topics, summarised here: http://forum.xda-developers.com/showthread.php?t=2869657
I haven't been able to unlock on my S5.
Hi, I followed the DirtySanta tutorial, used the US996 DeODEXed Rom. I knew this was a possibility but thought that I could get back to stock using the KDZ, unfortunately my phone is now seen as US996. I've tried modifying both the build.prop, and KDZ but I still can't get LGUP to flash back to stock. Is there anything I can do?
Service Unavailable is probably due the frequency signal issue.
Remember that Wind runs in AWS bands, while the US996 runs on regular bands (Bell, Rogers, Telus)
I'm sure the phone works fine if you use a Rogers SIM on it.
so, the trouble / solution is figuring out how to flash back the Tmobile / Wind modem back into the phone.
also set the phone to use the proper AWS bands 1700 / 2100, or the new LTE band 66
AllGamer said:
Service Unavailable is probably due the frequency signal issue.
Remember that Wind runs in AWS bands, while the US996 runs on regular bands (Bell, Rogers, Telus)
I'm sure the phone works fine if you use a Rogers SIM on it.
so, the trouble / solution is figuring out how to flash back the Tmobile / Wind modem back into the phone.
also set the phone to use the proper AWS bands 1700 / 2100, or the new LTE band 66
Click to expand...
Click to collapse
T-Mobile H918 supports LTE Band 66, try and flash a H918 ROM maybe? Or access the hidden menu and enable AWS, but you'll lose LTE and only have 4G that way.
See here to access the hidden menu but change 915 in the command to 996 or the model the phone is showing as.
https://forum.xda-developers.com/v20/how-to/access-hidden-menu-h915-t3515098
Edit: Let me know if it works, and you get LTE back (not just 4G) I really want to know to root my H915 as well. You used the [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151, right?
Second edit: If you're going to try to flash an H918 ROM I'd strongly suggest you flash an H918 kernel that is suggested in the dirty santa thread, I think the Konverged is what people are using. No hard evidence either way flashing an H918 ROM would work but it may not as the boot image is a 996.
Thanks guys. I flashed the Konverged kernel earlier, it helped crash-wise but nothing on the signal end. Last night I extracted the files from the H91510e kdz and tried to flash the modem that was included but that hasn't helped, I want to try the CDMATool but it isn't recognising my account so I'll wait for a bit. I tried to use the hidden menu but it doesn't seem to do work on this firmware unfortunately.
Splinter77 said:
Thanks guys. I flashed the Konverged kernel earlier, it helped crash-wise but nothing on the signal end. Last night I extracted the files from the H91510e kdz and tried to flash the modem that was included but that hasn't helped, I want to try the CDMATool but it isn't recognising my account so I'll wait for a bit. I tried to use the hidden menu but it doesn't seem to do work on this firmware unfortunately.
Click to expand...
Click to collapse
Try this, make sure USB Debugging is enabled. Turn off phone. Remove the battery. Put battery back in. Hold the volume up button and plug in USB cable. It may boot into download mode or it may boot into the dirty santa corrupt screen. If it does boot into the corrupt screen , let go of up button, press the power button then IMMEDIATELY press the volume up button. Either way you should be in download mode. You want download mode, not fastboot. Make sure LGMobileDriver_WHQL_Ver_4.1.1.exe drivers are installed.
Download LG Support Tool. http://www.mylgphones.com/lg-software-tools-download the 'Download and install LGMobileSupportTool.exe' link. Install and run it. If you've already installed the drivers hit cancel when they go to install.
Then go to 'Options' 'Upgrade Recovery' Make sure you have the IMEI number from under the battery and put it in no dashes or spaces. It should download and install the firmware if you've done the tap 'About Phone' 'Developer Options' 'Enable USB Debugging' but I'm sure you know this.
If all goes well you should be back on stock firmware.
Hope it works, it should but I'm not 100% sure.
The good news is that it recognized my phone as H915, but unfortunately half way through the setup it through a weird error. Part of me is thinking of restoring my twrp backup and trying uppercut again. I'm hoping that will get the program to see my phone correctly.
EDIT: I tried the KDZ installer again, without trying to restore the TWRP backup and my phone is back to stock and getting a signal. Thanks again to the both of you.
Splinter77 said:
The good news is that it recognized my phone as H915, but unfortunately half way through the setup it through a weird error. Part of me is thinking of restoring my twrp backup and trying uppercut again. I'm hoping that will get the program to see my phone correctly.
EDIT: I tried the KDZ installer again, without trying to restore the TWRP backup and my phone is back to stock and getting a signal. Thanks again to the both of you.
Click to expand...
Click to collapse
What I suggested worked without the TWRP backup? Or another way?
your best bet is to somehow find a way to install the stock rom through TWRP then you can install the KDZ. Cause I had the same issue as you, i have a Verizon V20 with the US996 rom and it wouldnt let me flash the verizon KDZ until I installed NotSoStock rom thats based on the Stock Verizon Rom
EDIT: Just saw you got back to Stock. Disregard this lol
KedarWolf said:
What I suggested worked without the TWRP backup? Or another way?
Click to expand...
Click to collapse
I didn't use the TWRP backup at all in the end. Your method didn't fully install, but it made the phone see itself as an H915 again which allowed uppercut/LGUP to install the KDZ so it was a big help
Congrats! on the recovery, this is a good reference thread for anyone trying to recover from a bad root, and needs to get back to stock.
Splinter77 said:
The good news is that it recognized my phone as H915, but unfortunately half way through the setup it through a weird error. Part of me is thinking of restoring my twrp backup and trying uppercut again. I'm hoping that will get the program to see my phone correctly.
EDIT: I tried the KDZ installer again, without trying to restore the TWRP backup and my phone is back to stock and getting a signal. Thanks again to the both of you.
Click to expand...
Click to collapse
did you use the upgrade option in the lg up tool of refurbish
If you guys still have issues with service disabled i was able to fix my device by using the hidden menu options on this thread and selected (device reset R&D only) once i selected this option i finaly recived service
mmjs14 said:
If you guys still have issues with service disabled i was able to fix my device by using the hidden menu options on this thread and selected (device reset R&D only) once i selected this option i finaly recived service
Click to expand...
Click to collapse
@mmjs 14
Are you saying you have a rooted 915 with everything working?
guess not lol
I am having the same issue with an h910, but the service only works sometimes. Many times it is searching (and draining the battery in the process), but sometimes it will get service and be OK. Quite frustrating, and no way to revert because no kdz available. Anyone else with h910 having this problem?
Hi,
I'm not sure if I'm off topic here or not. I have an LG V20 H910-10c (Nougat 7.0) and I am having an issue with a Service not working after using DirtySanta to Root my phone and I am praying that someone can help me out with. I have already tried a Factory Wipe/Reset and Wipe Dalvik/ART & Cache and have Formatted Data to remove Encryption, etc..
Timeline: The phone worked fine in all aspects before Rooting it.
After Rooting it, I had this issue.
I then tried a Factory Reset and got stuck in a TWRP Bootloop.
I fixed the Bootloop issue with a Reset (Yes then Yes).
The issue is still there.
ISSUE: When I boot into Android, I get the following message;
"LGSmartcardService has stopped"
.....and I cannot use my External SD Card (TWRP sees it fine, I Flashed SuperSU from it).
I have Googled my brains out and simply cannot find any suggestions, except to perform a Factory Reset, which I did and that's what put me into the Bootloop and I reset the way you said and now it boots up okay, except that error message is still there.
I have not put any apps on the phone or anything. It's factory fresh (except for Rooting it).
I hope I'm not violating any rules by posting this, but the page I used to Root it has a REAL SMALL downloadable file called "V20-Root.zip" that contains everything, including the Batch files with the steps that they perform in them. I did NOT use the ROM, as that's ONLY for Sprint users and my phone is an AT&T model (Unlocked and my Carrier is MetroPCS). But I put it here, just in case someone wishes to bless me by taking a look and seeing if there's something to note. I am not a coder by any means. I do understand some basics, but I couldn't see anything that would cause this sort of problem. I did NOT install the ROM listed, because it's for Sprint users ONLY and I have an AT&T (Unlocked, using MetroPCS) H910. Here's the link to the page:
https://tinyurl.com/yacdendm
I really need my Ext SD Card to be seen! I use it extensively and it would be a real hindrance not to have it! Plus this is my ONLY phone (no landline) and I am disabled and must run everything, including my home network and laptop, etc. from it and I need its space for things I have to have available on my phone to do things that I need to do, so any help would be appreciated GREATLY!
I do need to be Rooted, so going back to factory with whatever Mpdel # ROM an LG Tool sees me as might make me unable to Root again.
Please Help Me and Thank You!
Dave
My Name is Maxton. I am 11 years old and trying to flash a lineage OS Equivalent on my LG V20. Any advice?
Hi Maxton,
Glad you made it here.
1.You might want to read this:
H918 - lafsploit works - trying to install latest official Lineage
Greetings from Los Angeles. After following the steps kish and runningnak3d provided using lafsploit, I am having difficulty narrowing down what I’m missing. My goal is to be running the latest Lineage official builds. With high-end specs, an...
forum.xda-developers.com
to decide if the LOS (Lineage OS) on H918 is for you or not.
2. And if more information needed after that, try searching for H918 Lineage (or, replace H918 with your own model)
3.
You need to start by finding out:
a. what model is your V20: (In settings and also on the label under the battery)
models with unlockable boot loaders WITHOUT using the engineering aboot:
H918 - (use fastboot oem unlock)(T-Mobile)(engineering bootloader dont work on TMO - instant brick!)
US996 - (use unlock.bin from LG) (GSM Unlocked for US Cellular with CDMA)
models that can use "engineering aboot" (leaked dev version of bootloader)
using the engineering aboot: "BUT we have an engineering aboot for the rest of V20s,
and we can just push the engineering aboot, and twrp just like back when dirtycow worked"
H910 - (AT&T) - some reports of issues
H990 - (T-Mobile, Verizon, Unlocked, AT&T for HK[Dual SIM 990N], Global[Dual SIM 990DS and Mexico[990T])
VS995 - (Verizon with CDMA)
LS997 - (Sprint with CDMA)
b. what ARB you're on, ARB0 or ARB1
dial: *#LGMENU#*model# , so if your model is H918 then ( *#546368#*918# )
choose SVC Menu
choose Version
scroll to bottom
c. what software version you are running:
SETTINGS > ABOUT PHONE > SOFTWARE INFO
d. what Android OS you are running - see that in About Phone as well, it is either Nougat 7x or Oreo 8x
With this information about your phone, a lot more of what you read will start making sense.
4. I can't give you the exact step by step, because I don't know it. However, I can give you this advice:
Do not do anything until you fully unlocked your bootloader (if it applies to your model), and verified it is unlocked. Because if you do, you may get in to a catch 22 situation where to fix it you need the unlocked bootloader, but you can't unlock it because the phone won't boot. Once unlocked, think twice before locking it back, accept OTA, etc. Read about that before doing it.
5. Try to read as much as you can before you do anything to it, especially about every situation that causes a "brick" , and about ways out of a brick. There is so much info here, but all dispersed in so many threads, you might want to think of a method of how to make sure that once you read something, you will never have to read it again, or at least be able to instantly find it. You will appreciate that over time.
6. For your second thread, try naming it in a way that has your main question, like "How to get the latest Lineage on H918?". Thing is, people are busy, they read thread titles and open only those they are interested in. Whats worse, sometimes they only search for threads titles containing certain keywords. So, that way more people are likely to read your thread.
On the other hand, some of the best guys here learned what they know by doing it, and breaking many phones in the process. The trick is that this way, you never forget and you don't waste time, so if this way suits your personality better, it is not a bad way to go, it is only things, you'll have many more.
Could someone please point me in the direction of a custom ROM that will (or even might) work on Samsung j7 sky pro SM-272VL(GP)
Before anyone suggests, I have already read all of the information out there on rooting, ODIN, TWRP, etc for this phone. It sounds like several have tried, but no one has actually been able to gain root, although there may be hope for that due to security flaw https://www.exploit-db.com/exploits/45379 mentioned in this post #21
SM-S727VL Analysis, Partition Table, and Factory
-- UPDATE #1 (11/05/18) added So I've got myself a Tracfone Variant of the Samsung J7, The "Galaxy J7 Sky Pro" [SM-S727VL] CDMA. As far as I can tell, this variant is sold on both the Tracfone and StraightTalk carriers, and it seems to just run...
forum.xda-developers.com
I have also read all of the only other thread out there on this device on the subject of rooting, or anything really:
SM-S727VL Root and Recovery
I cannot for the life of me get this phone rooted or a recovery installed. Odin always fails and ADB doesn't recognize the device. Does anyone have any info on rooting this device? I really just want to at least be able to update this thing to...
forum.xda-developers.com
However not much was accomplished in these peoples attempts other than a bricked phone or 2, and most of the participants seem to have moved onto other devices.
I however do not have any issue with needing to root as I own the device, and as it is I can boot into a recovery ODIN mode that says that FRP Lock is off, and the screen is showing a "download in progress" background to a console, waiting for me to send the updated firmware/custom ROM/whatever from the USB cable. See attached image.
I run Linux and have for the last 20 years have used too many Distros to count, but can work with most any, but prefer debian based although I have much respect for Gentoo, and their compile everything package management, and have spent considerable time on it as well. l have unlocked and installed custom ROM's of of many types on many phones, and am working with the combined experience of myself, and my friend who has done the same, except even more on more different devices than myself. But neither of us has worked on such an obscure model as this one with so little information posted publicly on the internet for anyone to find as this one. But if there is a way to do it, I'm sure between the two of us, we can and will make it happen.
Can anyone be of any help? I would really like to get something out of the phone for the $100 that it cost me. Things I would like to run would be Kali Nethunter, and/or Andrax or Cyanogenmod/LineageOS or really any other AOSP that is not google f***ed. Basically any custom ROM (whichever, whatever type and version has the best chance of working on this phone, since there are none posted publicly that are specifically made for this device that we can find for this obscure, excessively undocumented model of phone. Just getting TWRP will be a good start, and I'm pretty sure we can handle that. However in the mentioned posts even the the TWRP file that is made for this phone, people are having troubles installing in their experiences, and bricking their phones in the process, so I definitelly would prefer not to have a repeat of what happened there.
Thank you in advanced for any and all information, hints, tips, tricks, etc. I would like to not brick this phone as the only other person who attempted to do anything with this phone unfortunately had done.
Hello everyone. I recently purchased a used Pixel 4. Past owner said WiFi+Data stopped working after updating Android and that the phone is unlocked and carrier-free. I need to unlock bootloader in order to install GrapheneOS but it is greyed out. As you can see in the screenshots, it seems like the phone is not recognizing WiFi and IMEI hardware while booted. IMEI does show up in the barcode menu option in fastboot. System UI crashes if I try to open WiFi config. The only thing I could try was tethering via Bluetooth from my other phone and updating Android OS and apps. Already tried wiping everything and forcing phone to connect to Google while on Bluetooth tethering by pressing (*#*#2432546#*#*) in the dialer as sugested here: https://source.android.com/setup/contribute/flash#preparing-your-device
This doesn't show any success or error message.
One thing that may have happened is this: https://www.phonearena.com/news/google-pixel-android-12-verizon-update-issue_id136367
Apparently Google sent OTA Verizon update to unlocked Pixel 4's by mistake. Maybe the wrong software is what is making it not recognize WiFi+Data?
Current installed build is 12.1.0 (SQ3A.220605.009.A1, Jun 2022). Maybe I should wait for a new SP* instead of SQ* build to come out and try installing it? This is because P is for the main platform branch as explained here: https://source.android.com/setup/start/build-numbers#build-ids-defined
Hopefully it comes out before October since that is the end-of-support date.
OTA builds: https://developers.google.com/android/ota#flame
Other option would be to try out this but it seems the riskiest and last resort option:
Unlock carrier locked bootloader Pixel [BETA]
UPDATE AS OF 16 OF MAY 2023 This project isn't working right now, but I am still working on it. However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get...
forum.xda-developers.com
And yet another option would be to purchase a new board and replace it.
What do you think? I tried submiting the IMEI to T-Mobile's site and it says it is OK to be ported. Verizon's site didn't let me submit the IMEI I don't know why. And for AT&T I didn't find any site for that. IMEI checks say it is not blacklisted.
Did u solve this?