Related
Is there anyway that I can install T-mobile firmware on my N9005 Galaxy Note 3? I tried to do it but it fails everytime. is there any way I can change my model number or something so I can install different firmwares from different variants? I ask this because I used to own a HTC One and I was able to change the model number so I could install different firmwares.
samanbabah said:
Is there anyway that I can install T-mobile firmware on my N9005 Galaxy Note 3? I tried to do it but it fails everytime. is there any way I can change my model number or something so I can install different firmwares from different variants? I ask this because I used to own a HTC One and I was able to change the model number so I could install different firmwares.
Click to expand...
Click to collapse
The better question is you have an international model so what is your goal? Are you trying to install a specific ROM to enable features (like modem frequencies) which have been disabled? You cannot install another model ROM on your device or you will just go into a boot loop or soft-brick your device and you will need to go through a recovery process. I'm going to assume you want to install a ROM for a specific feature or set of features which can be done but you simply need to ROOT and find a compatible ROM with the features you require.
Hope this helps!
cellrama said:
The better question is you have an international model so what is your goal? Are you trying to install a specific ROM to enable features (like modem frequencies) which have been disabled? You cannot install another model ROM on your device or you will just go into a boot loop or soft-brick your device and you will need to go through a recovery process. I'm going to assume you want to install a ROM for a specific feature or set of features which can be done but you simply need to ROOT and find a compatible ROM with the features you require.
Hope this helps!
Click to expand...
Click to collapse
yeah I was going to see if I would get LTE speeds if I'd installed the t-mobile firmware. also I want to be able to use Wifi calling as well. but the main reason I wanted to try out t-mobile firmware was, so I could get LTE speeds.
samanbabah said:
yeah I was going to see if I would get LTE speeds if I'd installed the t-mobile firmware. also I want to be able to use Wifi calling as well. but the main reason I wanted to try out t-mobile firmware was, so I could get LTE speeds.
Click to expand...
Click to collapse
Please refer to this post: http://forum.xda-developers.com/showthread.php?p=46653611#post46653611. You have posted a duplicate thread essentially asking the same information. I have provided a link which once viewed and completed should hopefully solve your issue. If not, respond to that thread and I'll help where possible. Thanks!
Hi, in an attempt to unlock Wifi Tethering capability on my phone, I installed [G900F]CyanogenMod 14.0-20161020-UNOFFICIAL-klte, and now I'm unable to make phone calls or use SMS/MMS.
Is there anything I can try to get service back?
I've tried installing a new modem with no success, using Odin, FlashFire, Terminal Server. I'm not confident I was doing it correctly though, or even if I was using the correct modem files.
I was able to root the phone with Stock firmware, but Mobile Hotspot/Wifi Tether wasn't built-in, and I had no success with any of the apps... FoxFi, Wifi Tether Router, Barnacle Wifi.
Some more information on the phone:
It's the StraightTalk variant made for TotalWireless MVNO. The phone's Stock firmware said it was the S902L Samsung S5 variant, but under the battery FCC ID of the device is actually just a G900V. I took it to the Verizon MVNO PagePlus and they were able to activate the phone, and everything was working perfect, until installing CM14.0.
A roadblock I found out, that might be the root of some of the problems, is the phone may not have the ability to unlock the bootloader, possibly limiting some modding methods. When looking at /sys/block/mmcblk0/device/cid, it starts with 11, designating a Toshiba eMMC chip.
I'll take any suggestions, or alternatives... I don't mind using the stock firmware or any other Roms. The main feature I'd like to have is the ability to use Wifi Tether and the basics, make calls, send sms.
Thank you.
I know this is off topic, but how in the world did you get CM14 running on G900V-CID11?
leotakacs said:
I know this is off topic, but how in the world did you get CM14 running on G900V-CID11?
Click to expand...
Click to collapse
I'm not entirely sure, but someone had an idea they mentioned to me, that it might've been possible to get CM installed from a very outdated Android version, from before CID 11 was locked. The previous stock Android version the phone came installed with was 4.4.2. It was the StraightTalk variant made for TotalWireless MVNO. The phone's Stock firmware said it was the S902L Samsung S5 variant, but under the battery FCC ID of the device is actually just a G900V.
You will not be able to run any version of Cyanogen on your Toshiba S5 properly. Your best course would be to install FlashFire from the play store and use it to install a TouchWiz ROM such as Moar (5.0) or Phoenix (6.0).
TechFellow1 said:
I'm not entirely sure, but someone had an idea they mentioned to me, that it might've been possible to get CM installed from a very outdated Android version, from before CID 11 was locked. The previous stock Android version the phone came installed with was 4.4.2. It was the StraightTalk variant made for TotalWireless MVNO. The phone's Stock firmware said it was the S902L Samsung S5 variant, but under the battery FCC ID of the device is actually just a G900V.
Click to expand...
Click to collapse
no, no, no. don't listen to any of these other people. if your phone boots CM14 then your bootloader is unlocked. this has nothing to do with bootloaders. you installed the wrong ROM for your phone. CM14-kltevzw is the correct variant for your phone, not CM14-klte.
see here:
https://archive.org/download/cmarchive_nighlies/cm-14.1-20161225-NIGHTLY-kltevzw.zip
Hariiiii said:
no, no, no. don't listen to any of these other people. if your phone boots CM14 then your bootloader is unlocked. this has nothing to do with bootloaders. you installed the wrong ROM for your phone. CM14-kltevzw is the correct variant for your phone, not CM14-klte.
see here:
https://archive.org/download/cmarchive_nighlies/cm-14.1-20161225-NIGHTLY-kltevzw.zip
Click to expand...
Click to collapse
He said his phone has a CID11 Toshiba chip. @OP, are you positive you have a Toshiba chip (11)?
leotakacs said:
He said his phone has a CID11 Toshiba chip. @OP, are you positive you have a Toshiba chip (11)?
Click to expand...
Click to collapse
It doesn't matter. He is on a straight talk phone. The bootloader is unlocked by default. The firmware is different.
Hariiiii said:
It doesn't matter. He is on a straight talk phone. The bootloader is unlocked by default. The firmware is different.
Click to expand...
Click to collapse
generally correct. best way to know would be to take a cid 11 based device, and flash twrp same way you would cid 15.
as far as i know though, most straight talk phones i see at work that i've repaired software wise have had unlocked bootloaders... which makes recovering/backing up files a breeze lol
KaptinBoxxi said:
generally correct. best way to know would be to take a cid 11 based device, and flash twrp same way you would cid 15.
as far as i know though, most straight talk phones i see at work that i've repaired software wise have had unlocked bootloaders... which makes recovering/backing up files a breeze lol
Click to expand...
Click to collapse
I think that is correct. Here's the final solution I came up with and everything's working perfectly now.
I flashed the kltevzw 14 version with TWRP and had no luck getting service, then I tried flashing the kitkat factory ROM with ODIN to see if that would fix it, but ODIN failed after many attempts. Finally I flashed with the lower but stable release kltevzw CM13, instead of the nightly, and everything worked again. I'm thinking I must be extremely lucky to have gotten a Straight Talk S5 variant with an unlocked bootloader, but it's interesting that even though my CID definitely starts with 11, the bootloader is unlocked. Not all hope is lost on CID 11 S5's.
TechFellow1 said:
I think that is correct. Here's the final solution I came up with and everything's working perfectly now.
I flashed the kltevzw 14 version with TWRP and had no luck getting service, then I tried flashing the kitkat factory ROM with ODIN to see if that would fix it, but ODIN failed after many attempts. Finally I flashed with the lower but stable release kltevzw CM13, instead of the nightly, and everything worked again. I'm thinking I must be extremely lucky to have gotten a Straight Talk S5 variant with an unlocked bootloader, but it's interesting that even though my CID definitely starts with 11, the bootloader is unlocked. Not all hope is lost on CID 11 S5's.
Click to expand...
Click to collapse
Are you able to dump your boot and bootloader partitions somehow? The "dd" command from adb shell somehow?
Couldnt we just use a diff program to compare yours with one of the Locked 11's?
TechFellow1 said:
I think that is correct. Here's the final solution I came up with and everything's working perfectly now.
I flashed the kltevzw 14 version with TWRP and had no luck getting service, then I tried flashing the kitkat factory ROM with ODIN to see if that would fix it, but ODIN failed after many attempts. Finally I flashed with the lower but stable release kltevzw CM13, instead of the nightly, and everything worked again. I'm thinking I must be extremely lucky to have gotten a Straight Talk S5 variant with an unlocked bootloader, but it's interesting that even though my CID definitely starts with 11, the bootloader is unlocked. Not all hope is lost on CID 11 S5's.
Click to expand...
Click to collapse
Delgoth said:
Are you able to dump your boot and bootloader partitions somehow? The "dd" command from adb shell somehow?
Couldnt we just use a diff program to compare yours with one of the Locked 11's?
Click to expand...
Click to collapse
No, all hope IS lost on CID 11's. You have a different phone provided by a different company. It is loaded with a different software and hardware configuration. There is no bootloader signature verification. Yes, the configuration is very similar to that of a G900V, but the bootloader comes unlocked. This is phone specific. This has no value for an actual G900V.
Hariiiii said:
No, all hope IS lost on CID 11's. You have a different phone provided by a different company. It is loaded with a different software and hardware configuration. There is no bootloader signature verification. Yes, the configuration is very similar to that of a G900V, but the bootloader comes unlocked. This is phone specific. This has no value for an actual G900V.
Click to expand...
Click to collapse
well if that's correct, then why does the dev edition bootloader work on the non-dev edition? Sure, its still a g900v, but never hurts to find a way and try
a little optimism can go a long way in life. don't think so negatively
KaptinBoxxi said:
well if that's correct, then why does the dev edition bootloader work on the non-dev edition? Sure, its still a g900v, but never hurts to find a way and try
a little optimism can go a long way in life. don't think so negatively
Click to expand...
Click to collapse
I say this because I have tried it and I know how it works. A bootloader needs to have the right signature that is recognized by the hardware. The reason the dev edition bootloader works on non dev edition is because they are the same phone, but with different bootloaders installed. The signature of the straight talk bootloader will not be recognized by the G900V hardware. Again, I have confirmed this personally. The straight talk is almost the same hardware as the verizon G900V, but it does not have bootloader signature verification enabled (and the bootloader that comes installed is unsecured).
Hariiiii said:
I say this because I have tried it and I know how it works. A bootloader needs to have the right signature that is recognized by the hardware. The reason the dev edition bootloader works on non dev edition is because they are the same phone, but with different bootloaders installed. The signature of the straight talk bootloader will not be recognized by the G900V hardware. Again, I have confirmed this personally. The straight talk is almost the same hardware as the verizon G900V, but it does not have bootloader signature verification enabled (and the bootloader that comes installed is unsecured).
Click to expand...
Click to collapse
alright, that makes sense. Thanks for explaining. Always interested in these things since i don't QUITE understand exploits at that level. I do mainly apk modifications and software dev
KaptinBoxxi said:
well if that's correct, then why does the dev edition bootloader work on the non-dev edition? Sure, its still a g900v, but never hurts to find a way and try
a little optimism can go a long way in life. don't think so negatively
Click to expand...
Click to collapse
because you don't have a clue about how the CID exploit works
the reason you can flash the dev aboot on a CID15 is because you can change the CID to match that of a dev edtion aboot checks the CID to see if a device as a dev edtion or not
the CID is a sort of serial number for the flash-chip and normally its write once and then read only value ,but because samsung was sloppy we can use some custom Samsung NAND vendor commands to change it so secure-boot thinks you have a dev editon and permits the flashing of a unsigned image
this is flat not possible on CID11 devices(toshiba NAND) there is no hope for cid11 devices with this method the commands needed simply do not exist PERIOD
Legitsu said:
because you don't have a clue about how the CID exploit works
the reason you can flash the dev aboot on a CID15 is because you can change the CID to match that of a dev edtion aboot checks the CID to see if a device as a dev edtion or not
the CID is a sort of serial number for the flash-chip and normally its write once and then read only value ,but because samsung was sloppy we can use some custom Samsung NAND vendor commands to change it so secure-boot thinks you have a dev editon and permits the flashing of a unsigned image
this is flat not possible on CID11 devices(toshiba NAND) there is no hope for cid11 devices with this method the commands needed simply do not exist PERIOD
Click to expand...
Click to collapse
I understand plenty enough to know the difference in the flash chips cid's with such like that... The fact of the matter i was trying to get at is that most Straight Talk phones are unlocked entirely without a care in the world, regardless of their CID/branding. Without the proper commands and 3rd party support, I get that there won't be a way. That's why I check my CID's first before buying S5's or Note 4's
Good afternoon ladies and gents,
I am here today seeking your guidance on compiling the stock rom for the lg v20 h910 (AT&T) variant. I was able to grab the rom source and the kernel source from here .... as far as that being the right rom is beyond me lol... but it matches the model number so i thought i would give it a try. and i am wondering if anyone can show me the right direction in do so myself. i have a desktop pc running win10 64 pro build 1607 ( redstone 2 ), but i also have a macbook pro if i cannot use my pc. if i have to install linux i will do so. any guidance would be much appreciated.
I want to lock the bootloader after the dirty santa exploit and also return the device to at&t for an upgrade, i want to get the s8+ . The reason i want to lock it and unroot ( stock it basically ) is because i am afraid of at&t coming after me for the full price of the device, especially that i have the NATF mega rom with the static boot screen and i am also afraid that they would think the device is not functional. The extrior of the device is flawless, no scratches nor dents or anything of that sort.
Nothing?
Can you not use google to search the forums for the answers on using LGUP to maybe restore your phone to stock, thus negating the need to possibly install multiple operating systems, or compile code?
I do not use your variant of this device (i am on the LS997) so my answer should be immediately discarded, but by and large more devices can be restored to factory utiluzing LGUP than can not be restored.
Good night, and good luck.
elijah420 said:
Can you not use google to search the forums for the answers on using LGUP to maybe restore your phone to stock, thus negating the need to possibly install multiple operating systems, or compile code?
I do not use your variant of this device (i am on the LS997) so my answer should be immediately discarded, but by and large more devices can be restored to factory utiluzing LGUP than can not be restored.
Good night, and good luck.
Click to expand...
Click to collapse
If there was an available kdz for my variant I would have used lg flash tool. Or lgup. Thats why i asked for a guide in the right direction when it came to compiling. Because the source code is available for h910 which is the at&t variant but no available kdz. So i was simply asking to learn how to compile a kdz from source code.
Mostly Sony XZ-series phones have limited LTE Carrier Aggregation bands on per country / provider. You can check here more information about that: https://forum.xda-developers.com/xperia-xz/how-to/lte-carrier-aggregation-combinations-t3577544
I made step by step instruction how to modify on Sony XZ, Sony XZs, Sony XZ Premium and Sony XZ1 LTE Carrier Combinations. Rooted phone required. This instruction should working also with Dual SIM models.
Sony XZ Premium after Android 9 PIE does not work anymore
You can check this on my blog site: https://mt-tech.fi/en/modify-sony-xz-xzs-xz-premium-and-xz1-lte-a-band-combos/
Make sure you make full modem backup and backup all config files to your computer, if need restore configuration.
To try this mod, it should be supported by the carrier also! Is there a way to find out in which countries it's rolling?
Sent from taptalk
550D said:
To try this mod, it should be supported by the carrier also! Is there a way to find out in which countries it's rolling?
Sent from taptalk
Click to expand...
Click to collapse
Did you mean LTE Carrier Aggregation support? You just should check what band your provider support and then find possible combos on our Google sheets (link on first post).
Many providers also support well 256QAM/64QAM but not every provider yet. There is no list yet.
That's my point... There is no "list". You just try it and see if it's working. But I'm not brave enough to try it -and IF it goes smoothly- see no result because my provider being ambitious in saving money than QoS :/
Sent from taptalk
550D said:
That's my point... There is no "list". You just try it and see if it's working. But I'm not brave enough to try it -and IF it goes smoothly- see no result because my provider being ambitious in saving money than QoS :/
Sent from taptalk
Click to expand...
Click to collapse
That should ask from local provider customer service.
When know local LTE bands then know possible CA-combinations.
hi,
i try your LTE mod but from the last update .192 i don't have 4x F8311 (Sony XZ) undefined device, I get 3 and not MI_04. What do you think about that and how could i unlock LTE ?
thanks
ND
bobladure said:
hi,
i try your LTE mod but from the last update .192 i don't have 4x F8311 (Sony XZ) undefined device, I get 3 and not MI_04. What do you think about that and how could i unlock LTE ?
thanks
ND
Click to expand...
Click to collapse
Maybe you have driver already installed? Open QPST App and see your phone already added automatically?
yes it's that
Thanks you a lot
i can unlock now
ND
@olkitu QPST on xz1/xz premium with Android Pie works using the magisk module that you can find here: https://forum.xda-developers.com/showpost.php?p=78919730&postcount=119. No need to install custom driver, you can use the driver from windows update. I'm saying it to you also because your tutorial is among the first results on Google
Edit: It seems to not work on XZ premium. I was wrong
HandyMenny said:
@olkitu QPST on xz1/xz premium with Android Pie works using the magisk module that you can find here: https://forum.xda-developers.com/showpost.php?p=78919730&postcount=119. No need to install custom driver, you can use the driver from windows update. I'm saying it to you also because your tutorial is among the first results on Google
Click to expand...
Click to collapse
Thanks for sharing this! I have to put test this Magisk module and then update my blog posts.
This driver is Qualcomm official driver for Xiaomi but yes if you can find it from Windows Update that is good.
olkitu said:
Thanks for sharing this! I have to put test this Magisk module and then update my blog posts.
This driver is Qualcomm official driver for Xiaomi but yes if you can find it from Windows Update that is good.
Click to expand...
Click to collapse
On oreo using the driver for xiaomi I had to manually insert the "COM" port, now with the drivers downloaded by windows the phone is autodetected*.
The device used by QPST is "USB\VID_05C6&PID_9091&REV_0404&MI_00". Sometimes with the module enabled the phone says "no service", to solve the problem just enable and disable the "Airplane mode", note that this does not interfere in any way with QPST/QXDM. Obviously you should disable the module after finishing the work.
And thak you very much for your work I still have some doubts about the lte_category file. Analyzing the firmware of many smartphones I understand how the files disable_cap_ies (disable 64qam/256qam capabilities), rrc_capable_plmn_list (limit the plmn that have capabilities not disabled) and the carrierpolicy works, but I found anything about lte_category :/
*In my case qpst is running in windows 7 compatibility mode
HandyMenny said:
@olkitu QPST on xz1/xz premium with Android Pie works using the magisk module that you can find here: https://forum.xda-developers.com/showpost.php?p=78919730&postcount=119. No need to install custom driver, you can use the driver from windows update. I'm saying it to you also because your tutorial is among the first results on Google
Click to expand...
Click to collapse
I can't get it to work on XZP Pie. Phone shows up in QPST, but as Unknown (No ESN). Same thing without the mod, but by running setprop commands from the shell. Used to work fine on Oreo.
jessenic said:
I can't get it to work on XZP Pie. Phone shows up in QPST, but as Unknown (No ESN). Same thing without the mod, but by running setprop commands from the shell. Used to work fine on Oreo.
Click to expand...
Click to collapse
Are you using a typec cable? Are you using the com port of the device "Qualcomm HS-USB Diagnostics 9091" ? Can you tell me if QPST see the device for few seconds during the boot?
Hi OLKITU, I wanted to ask you a question, I have a sony xperia xz1 compact Docomo version, rooted, I can open the band 20 following what you explain in your blog? https://mt-tech.fi/en/modify-sony-xz-xzs-xz-premium-xz1-and-xz2-lte-a-band-combos/
I am in France and I need the band 20. Thank you for your answer.
xavinaz said:
Hi OLKITU, I wanted to ask you a question, I have a sony xperia xz1 compact Docomo version, rooted, I can open the band 20 following what you explain in your blog? https://mt-tech.fi/en/modify-sony-xz-xzs-xz-premium-xz1-and-xz2-lte-a-band-combos/
I am in France and I need the band 20. Thank you for your answer.
Click to expand...
Click to collapse
Better buy device from France to support bands and carrier aggregation combinations used in France.
Thank you very much for your response, Olkitu. I am trying to enter qualcomm diagnostic mode, and I cannot. I have done everything you describe in your blog and nothing shows up in QPST. I even tried with the command (setprop sys.usb.config diag,adb), and I can't enter the diagnostic mode either. Do you know how to fix it? Thanks you
olkitu , little bit off topic but at what extent can be done with Qualcomm software to unlock the full potentioal of any phone? Im not talking about LTE and 5G, I mean Bluetooth, GNSS, Wifi, NFC, codecs. Because of the lack of tutorials on how to edit NV items EFS mods its a dangerous game.
xavinaz said:
Thank you very much for your response, Olkitu. I am trying to enter qualcomm diagnostic mode, and I cannot. I have done everything you describe in your blog and nothing shows up in QPST. I even tried with the command (setprop sys.usb.config diag,adb), and I can't enter the diagnostic mode either. Do you know how to fix it? Thanks you
Click to expand...
Click to collapse
Hi xavinaz.. I'm in the same situation as you. Have a docomo xz1 compact and need 20 band.
Have you found any solution ?
Right now I have Havoc 4.13 but I coudn't access the modem. But rolling back the phone to android 8 with the stock rom and using the temp root exploit you can access the modem as described in the tutorial.
But then I'm not be able to unlock the 20 band. So I go back to android 9 and now on havoc
Hello Bob, I have not been able to enable the band 20LTE. I have reviewed many blog and websites, and it is impossible.... I have not found the solution.
bob1791 said:
Hi xavinaz.. I'm in the same situation as you. Have a docomo xz1 compact and need 20 band.
Have you found any solution ?
Right now I have Havoc 4.13 but I coudn't access the modem. But rolling back the phone to android 8 with the stock rom and using the temp root exploit you can access the modem as described in the tutorial.
But then I'm not be able to unlock the 20 band. So I go back to android 9 and now on havoc
Click to expand...
Click to collapse
Hello Bob, I have not been able to enable the band 20LTE. I have reviewed many blog and websites, and it is impossible.... I have not found the solution.
Hi,
My D852 board failed from WiFi issue. While traveling replaced mobo with LS990 Sprint board. It won’t connect to data now because of cdma issue with gsm sim.
I’ve been reading on here for a week or more trying to sort out what I need to do.
Therefore, my goal is to get gsm data and sim working in the simplest way possible.
Please help:
1. Instructions to root it. It’s a LS990ZVE build with 5.01. I can’t find info on zve rooting. I google and find very little if anything. Do I have to downgrade or upgrade the system to root it?
2. Once I root I will install the TWRP app and make a NANDroid copy so I don’t get into trouble. I would like to install LineageOs 16 (or otherwise based on your opinions) for Android 9.0 and Gapps. Will this work on my motherboard and build?
3. Will the LineageOs 16 rom also fix the cdma to gsm problem? Or do I have to use a patch on top of lineageos16?
4. Can I perform all of these changes without using a pc? Using apps and the storage on the phone or sd card? I’m trying to keep it simple.
5. The board is clean right now without my old LG backup restored yet. At what point can I restore this LG backup to the new board? Before rooting? Or after flashing with LineageOs 16. The problem for me is I did the backup with the lg installed software and the file likely won’t be compatible once I flash with a new rom?
Please help.
Thank you.
Mechif said:
Hi,
My D852 board failed from WiFi issue. While traveling replaced mobo with LS990 Sprint board. It won’t connect to data now because of cdma issue with gsm sim.
I’ve been reading on here for a week or more trying to sort out what I need to do.
Therefore, my goal is to get gsm data and sim working in the simplest way possible.
Please help:
1. Instructions to root it. It’s a LS990ZVE build with 5.01. I can’t find info on zve rooting. I google and find very little if anything. Do I have to downgrade or upgrade the system to root it?
2. Once I root I will install the TWRP app and make a NANDroid copy so I don’t get into trouble. I would like to install LineageOs 16 (or otherwise based on your opinions) for Android 9.0 and Gapps. Will this work on my motherboard and build?
3. Will the LineageOs 16 rom also fix the cdma to gsm problem? Or do I have to use a patch on top of lineageos16?
4. Can I perform all of these changes without using a pc? Using apps and the storage on the phone or sd card? I’m trying to keep it simple.
5. The board is clean right now without my old LG backup restored yet. At what point can I restore this LG backup to the new board? Before rooting? Or after flashing with LineageOs 16. The problem for me is I did the backup with the lg installed software and the file likely won’t be compatible once I flash with a new rom?
Please help.
Thank you.
Click to expand...
Click to collapse
Your going to want to replace that board with a compatble gsm model or use the phone on sprint
Using a Sprint model board/G3 your gonna have nothing but problems and a bad time with it. Not worth the headache even if it was free
Sent from my SM-G960U using Tapatalk
Hi Hyelton,
Thank you for responding.
I would still like to give this a try as I have nothing to lose and will use the phone only for another 4-6 months then I’m buying a new phone. I’ve been dealing with the WiFi issue on the original board for 12monhs on a weekly basis, taking it apart and repositioning the plastic credit card fix and/or heating the WiFi chip. I can always flash this Sprint cdma board back to the original Sprint code with the nandroid backup if it’s not working happily. Also, I’m in Canada and can’t use the Sprint network from here.
Therefore, please let me know what methods to use as I will greatly appreciate help. I’m interested in this realm of android as a hobby and learning something new.
Mechif said:
Hi Hyelton,
Thank you for responding.
I would still like to give this a try as I have nothing to lose and will use the phone only for another 4-6 months then I’m buying a new phone. I’ve been dealing with the WiFi issue on the original board for 12monhs on a weekly basis, taking it apart and repositioning the plastic credit card fix and/or heating the WiFi chip. I can always flash this Sprint cdma board back to the original Sprint code with the nandroid backup if it’s not working happily. Also, I’m in Canada and can’t use the Sprint network from here.
Therefore, please let me know what methods to use as I will greatly appreciate help. I’m interested in this realm of android as a hobby and learning something new.
Click to expand...
Click to collapse
What software is it currently running? If anything newer most likely won’t have any chances... there are several methods. But most involve software version ZV8. If it’s newer than that downgrading is prob not an option.
And you’ll need a windows PC you can’t do this from the phone itself
Sent from my iPhone using Tapatalk
It has android 5.01 (lollipop?) and build is LS990ZVE
I had a hard time finding information on the differences of ZV_ line up of android so I don’t know if ZVE is newer or older than ZV8.
I have a laptop running Windows 7 and a pc running vista ( but vista pc not with me right now).
Mechif said:
It has android 5.01 (lollipop?) and build is LS990ZVE
I had a hard time finding information on the differences of ZV_ line up of android so I don’t know if ZVE is newer or older than ZV8.
I have a laptop running Windows 7 and a pc running vista ( but vista pc not with me right now).
Click to expand...
Click to collapse
Your most likely gonna need to find someone with an oculus box or whatever they’re called as I doubt you’ll be able to downgrade
Sent from my iPhone using Tapatalk
hyelton said:
Your most likely gonna need to find someone with an oculus box or whatever they’re called as I doubt you’ll be able to downgrade
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
What version android is zve? I’d like to read about the levels of android using these letter versions.
What levels or build versions allow me to do what I’m trying to do?
Is there anyone else on our forum here that would also be able to help that you know of?
Mechif said:
What version android is zve? I’d like to read about the levels of android using these letter versions.
What levels or build versions allow me to do what I’m trying to do?
Is there anyone else on our forum here that would also be able to help that you know of?
Click to expand...
Click to collapse
You stated that above. ZVE is 5.0.1. It’s newer than ZV8.
Your gonna need to pay someone with an oculus box most likely. And paying for a phone line that it would be cheaper to just buy a gsm one
Sent from my iPhone using Tapatalk