Related
Hello Everybody,
I would like to begin by saying how much I've learned in xda-devs in the last few days just by searching around the forum and Fixing different things here and there.
This is such a great community that I decided to register
OK so heres the deal:
Last week i bought a Note-2 (N7100) running Samsung Android 4.1.2 (Israel Version) + Rooted
I wanted to upgrade to 4.3 but 4.3 isn't yet released in Israel according to sammobile.com and other people I asked.
I found a Stock Deodexed Pre-Rooted ROM here on the forums (I think version was MK4), Flashed it, and lost cellular abilities (there is signal but emergency calls only) and WiFi.
Flashed WiFi FIX by Dr. Ketan, and by installing Devil's kernel (Patched_N7100_MK4_KERNEL.zip) and GT-N7100_ModemMJ9.zip I was able to gain 3G Functionality back.
Phone was working great for a few days, but then I decided to upgrade to Dito Note v3.2 because i wanted Note-3 Functionality.
After flashing it, I lost the ability to register to network again, started receiving "UIds on the system are inconsistent " and phone crashed every few minutes, screen stoped working every now and then.
I immediately looked for a different ROM to flash, (couldn't find the original ROM I flashed but i found DrKetan_Custom_ROM_V6_1).
So i wipe the phone, cache, sd-card and everything besides formatting the internal storage, Installed this ROM but still had the same issues with ULDS on the system, phone crashes and display shuts down while phone is still working).
Desperate, I downloaded Stock firmware (With KNOX) and flashed it to my device (I used Odin 3.09 and flashed everything, BL,CP,AP,CSC that was included within the original ROM). this was the Seri-Lanka firmware if I remember right.
This time phone boots without complaining about system files, but got "Emergency calls only" (IMEI and S/N still ok!).
In addition, I now have bootloader with KNOX.
I then thought, maybe the modem version is incompatible with the Cellular frequencies in my country (Israel Freqs: 850,2100), so i looked for countries with similar freq and downloaded official firmware for Thailand.
Flashed it with ODIN (same as before, BL,CP,AP,CSC basically everything) device boots fine, WiFi was working, but couldn't register on network ("emergency calls only") even if you can see your provider while manual scanning, registers successfuly apparently,but still no service.
Fraustrated, I rooted the device (Knox turned 0x1 but it doesn't really matter to me cause no warranty anyway), installed Philiz and flashed the 2 Fixes I mentioned at the begining (Devils kernel + Mj9 modem).
This resolved "Emergency calls only" issue, but now i cannot open WiFi at all!.
I tried to flash WiFi fix that i found in this forums but it didn't work. I've given everything I have in the last 2 days trying to fix this issue but I cant seem to solve this problem.
Now I'm just thankful that I can start/receive phone calls with my device.
I can't seem to understand, how did I not have signal with stock ROM?
could it be EFS was corrupted somehow so that only MJ9 Modem + Devil's Kernel read it?
How can i FIX WiFi?
Included screen-shots of "About Phone" and "*#1234#"
Thanks ahead,
psycintosh said:
I can't seem to understand, how did I not have signal with stock ROM?
could it be EFS was corrupted somehow so that only MJ9 Modem + Devil's Kernel read it?
How can i FIX WiFi?
Included screen-shots of "About Phone" and "*#1234#"
Thanks ahead,
Click to expand...
Click to collapse
did you seen this
cosmyndemeter said:
did you seen this
Click to expand...
Click to collapse
Yes, this is the exact post that i followed to solve "Emergency calls only" issue, but unfortunately I still don't have WiFi
psycintosh said:
Yes, this is the exact post that i followed to solve "Emergency calls only" issue, but unfortunately I still don't have WiFi
Click to expand...
Click to collapse
try this wifi fix
cosmyndemeter said:
try this wifi fix
Click to expand...
Click to collapse
Just flashed this with Odin 3.09 but it didn't solve Wi-Fi Issues. isn't this fix for devices without the original Bootloader?
psycintosh said:
Just flashed this with Odin 3.09 but it didn't solve Wi-Fi Issues. isn't this fix for devices without the original Bootloader?
Click to expand...
Click to collapse
try to flash stock firmware with stock kernel with kies. here you find a guide and let me know if it solved the problem
cosmyndemeter said:
try to flash stock firmware with stock kernel with kies. here you find a guide and let me know if it solved the problem
Click to expand...
Click to collapse
OK Thanks very much for all of your help.
Does it matter what version of 4.3 I choose to flash via Kies?
In Israel only version 4.1.2 is available and I know that going back from 4.3 most likely will erase my IMEI / S/N.
If i choose a stock rom from SamMobile does it matter what country it comes from?
I don't really understand why are there different modems to different countries, aren't all versions alike?
cosmyndemeter said:
try to flash stock firmware with stock kernel with kies. here you find a guide and let me know if it solved the problem
Click to expand...
Click to collapse
OK so i flashed with Kies 3 and now Wifi is back but again, "Emergency calls only"..
any idea?
psycintosh said:
OK so i flashed with Kies 3 and now Wifi is back but again, "Emergency calls only"..
any idea?
Click to expand...
Click to collapse
try this fix
flash via recovery (phliz or twrp)
i have the same problem, and like you, i tried all fixes, but, with nothing solution. I've been thinking that there is no solution, just sell the bad phone and buy a new one, and then no more experience with :crying:
r0ckside0710 said:
i have the same problem, and like you, i tried all fixes, but, with nothing solution. I've been thinking that there is no solution, just sell the bad phone and buy a new one, and then no more experience with :crying:
Click to expand...
Click to collapse
I don't belive in this approach, I know for sure that there is a way.
after re-flashing with Kies and getting "Emergency Calls" again, i tried to flash only the modem, and i saw that i lost connection with cellular but Wi-Fi was still working. only after flashing Devil's kernel it seems that Wi-Fi stops working..
I just got home and i'm not expecting any calls until tomorrow, I will look around maybe an alternative kernel will solve our problems..
psycintosh said:
I don't belive in this approach, I know for sure that there is a way.
after re-flashing with Kies and getting "Emergency Calls" again, i tried to flash only the modem, and i saw that i lost connection with cellular but Wi-Fi was still working. only after flashing Devil's kernel it seems that Wi-Fi stops working..
I just got home and i'm not expecting any calls until tomorrow, I will look around maybe an alternative kernel will solve our problems..
Click to expand...
Click to collapse
Maybe we just need the correct kernel and modem, the problem is that no one's development. Another solution would be to discover how to downgrade from 4.3 to 4.1. For now, our only option is to wait for more solutions and development
r0ckside0710 said:
Maybe we just need the correct kernel and modem, the problem is that no one's development. Another solution would be to discover how to downgrade from 4.3 to 4.1. For now, our only option is to wait for more solutions and development
Click to expand...
Click to collapse
OK, so as I promised yesterday, I had the time to dig in to this subject yesterday and I managed to find a solution to get both, WiFi and Cellular working (together!)
Here are the steps i took:
1) Installed Stock ROM 4.3 with MK4 as the main and BL version (this will install Knox but i already had it) and modem version MJ9 (Odin 3.09)
2) Root the device with CF-Auto-Root-t03g-t03gxx-gtn7100
3) Install custom Recovery (I used philz_touch_6.07.9-n7100.tar.md5)
4) Very important! After device boots it automatically attempts to perform update with samsung! DO NOT LET IT as it will install updated modem version. it is important that we have MK4 Kernel and MJ9 Modem for this to work.
5) Flash via recovery the following files:
a) Patched_N7100_MK4_KERNEL - This installs a patched Kernel only this time because we didn't let phone update version after boot, it will be compatible with Phones version.
b) GT-N7100_ModemMJ9 - This patches the MJ9 Modem.
After performing all the above steps I finally managed to get Cellular connectivity and WiFi together. Hope it works for other people as well.
I still don't understand why Stock Kernel with Stock MJ9 modem won't work, what do those patches contain that allows me to get connectivity to cellular network?
This device is not black-list and IMEI is still original and S/N but for some reason won't work with stock.
Seems to me like some of the ROMs maybe modify EFS so that only patched Kernel and MJ9 Modem will work and it's not backwards compatible.
Can anyone confirm this? and if so, is there a way to convert the "modified" EFS version to stock compatible version? or is the EFS file encrypted with propriety Samsung encryption?
You can download the referred files here
is good to know that you resolved your problem! Only one question, this is the rom of my country, will serve me? Or that rom should I use? The specifications are from sammobile.com
Model: GT-N7100
Country: Mexico (Telcel)
Version: Android 4.3
Changelist: 2194881
Build date: Mon, 25 Nov 2013 16:04:50 +0000
Product Code: TCE
PDA: N7100UBUEMK4
CSC: N7100TCEEML1
MODEM: N7100UBUEMJ4
r0ckside0710 said:
is good to know that you resolved your problem! Only one question, this is the rom of my country, will serve me? Or that rom should I use? The specifications are from sammobile.com
Model: GT-N7100
Country: Mexico (Telcel)
Version: Android 4.3
Changelist: 2194881
Build date: Mon, 25 Nov 2013 16:04:50 +0000
Product Code: TCE
PDA: N7100UBUEMK4
CSC: N7100TCEEML1
MODEM: N7100UBUEMJ4
Click to expand...
Click to collapse
Hi, as you can see modem version for you is ending with MJ4 so it's not the same as my version.
Look for a version that has modem version ending with MJ9 and then apply the patch (because patch is for MJ9 modem, and not any other modem from my understanding)
Hope you get your device working!!
More explanation
Here are the steps i took:
1) Installed Stock ROM 4.3 with MK4 as the main and BL version (this will install Knox but i already had it) and modem version MJ9 (Odin 3.09)
2) Root the device with CF-Auto-Root-t03g-t03gxx-gtn7100
3) Install custom Recovery (I used philz_touch_6.07.9-n7100.tar.md5)
4) Very important! After device boots it automatically attempts to perform update with samsung! DO NOT LET IT as it will install updated modem version. it is important that we have MK4 Kernel and MJ9 Modem for this to work.
5) Flash via recovery the following files:
a) Patched_N7100_MK4_KERNEL - This installs a patched Kernel only this time because we didn't let phone update version after boot, it will be compatible with Phones version.
b) GT-N7100_ModemMJ9 - This patches the MJ9 Modem.
Hi there, and thanks a lot for your effort, I am really confused about step number 4, I haven't detected any update from Samsung's side, can you please provide more explanation?
Thanks
I have a question that might be simple to answer, but i need confirmation because i don't want to brick my device recklessly.
When i got my Moto Z play, i immediatley unlocked it, flashed TWRP and installed LineageOS. So my device (including bootloader and baseband) are still on the state it arrived i guess. But my OS ist the newest LineageOS (so android 7.1.2).
My Moto Z play is an XT1635-02 32GB (bootloader adds P7 as variant), software channel must be RETEU.
My bootloader is C0.14 (from 2016-07-11)
and my baseband is M8953_10208.08.04-47e (bootloader says M8953_10208.08.04.47R ADDISON_ROW_CUST)
Are there newer versions of baseband (which might more important) and booloader? And can i flash them without problems?
Just flashing the NON-HLOS.bin in fastboot and i'm fine? Can i also use the 7.0-modem from RETAIL?
Sorry, these questions might be dumb and too careful for old users, but i'm only used to nexus devices and i am scared of bricking my Z play! Nexus factory images always had baseband and bootloader version written in the filename so it was easy to find out if you need to update. In addition there was just one "software channel" which made it hard to brick a device or flash something wrong.
McFlypants said:
I have a question that might be simple to answer, but i need confirmation because i don't want to brick my device recklessly.
When i got my Moto Z play, i immediatley unlocked it, flashed TWRP and installed LineageOS. So my device (including bootloader and baseband) are still on the state it arrived i guess. But my OS ist the newest LineageOS (so android 7.1.2).
My Moto Z play is an XT1635-02 32GB (bootloader adds P7 as variant), software channel must be RETEU.
My bootloader is C0.14 (from 2016-07-11)
and my baseband is M8953_10208.08.04-47e (bootloader says M8953_10208.08.04.47R ADDISON_ROW_CUST)
Are there newer versions of baseband (which might more important) and booloader? And can i flash them without problems?
Just flashing the NON-HLOS.bin in fastboot and i'm fine? Can i also use the 7.0-modem from RETAIL?
Sorry, these questions might be dumb and too careful for old users, but i'm only used to nexus devices and i am scared of bricking my Z play! Nexus factory images always had baseband and bootloader version written in the filename so it was easy to find out if you need to update. In addition there was just one "software channel" which made it hard to brick a device or flash something wrong.
Click to expand...
Click to collapse
I'm running the original bootloader and baseband from 6.0.1 without any issue, so I would suggest leaving it.
I don't want to get on the wrong side of you but that wasn't my question.
I wanted to know this because i'm not sure if i get the most out of my phone with an older baseband. I can't use VoLTE for example which possibly is activated with a newer baseband. Or it might improve the signal.
McFlypants said:
I don't want to get on the wrong side of you but that wasn't my question.
I wanted to know this because i'm not sure if i get the most out of my phone with an older baseband. I can't use VoLTE for example which possibly is activated with a newer baseband. Or it might improve the signal.
Click to expand...
Click to collapse
Well I'll suggest you only flash the baseband that comes with your specific firmware, if you flash the baseband from another firmware package you will end up without a IMEI and you'll have a expensive brick, which you will send to me so I can use the screen to get my mzp working again. That will be payment for warning you
Good one, flashallthetime
Back in, uh, I think Atrix time or even HTC Desire it was normal to flash/change radio baseband. It supposed to improve radio, prolong battery life... In reality, most of the time didn't do anything, sometimes broke something...
So in theory, you can do that. Should be fine but I wouldn't recommend.
If you have to, to get VoLTE, I would make a backup of the current rom, follow guide to flash back to stock and then restore backup. But be extremely careful, so many users over here bricked their devices. As far as I can see, downgrading and the accepting OTA.
Sent from my LG-V940n using Tapatalk
flashallthetime said:
Well I'll suggest you only flash the baseband that comes with your specific firmware, if you flash the baseband from another firmware package you will end up without a IMEI and you'll have a expensive brick, which you will send to me so I can use the screen to get my mzp working again. That will be payment for warning you
Click to expand...
Click to collapse
Good idea, please return it to me afterwards if it's working! :good:
I tried to install leedroid oreo and after installing it went to the HTC logo then a black screen then the htc logo again on a loop . so i decided to install another 8.0 ROM i use (Purefusion os) and now my sim card is not being detected (ive tried it in another phone and it works) ive tried resetting and tried many different roms and also ive tired to restore to original os using the RUU exe tool but i keep getting the error 132 .. can somebody PLEASE help ?
BoganRabbit said:
I tried to install leedroid oreo and after installing it went to the HTC logo then a black screen then the htc logo again on a loop . so i decided to install another 8.0 ROM i use (Purefusion os) and now my sim card is not being detected (ive tried it in another phone and it works) ive tried resetting and tried many different roms and also ive tired to restore to original os using the RUU exe tool but i keep getting the error 132 .. can somebody PLEASE help ?
Click to expand...
Click to collapse
Same Problem My HTC 10 (US Unlocked) seems to be no longer recognizing the cellular radio I was switching between ROMs and I received an error when Android booted saying that decryption was unsuccessful and I had to factory reset the device. After performing the factory reset I was unable to connect to the mobile network, when I looked into the settings the IMEI was listed as Unknown. I have advance wiped data in TWRP by formatting everything on the phone and trying to reinstall Viper 10 (with encryption disabled) Restored the matching firmware and reinstalled Viper 10 with encryption disabled and even flashed the most recent stock RUU. I have never tried switching between US and EU firmware, From other treads I've noticed people had problems with their HTC 10's service by trying to switch from Sprint to Unlocked US.
Three things
1. LeDroids 8.0 requires 8.0 firmware
2. Purefusion os not sure why but I have signal
3. You maybe able to flash the ruu for your phone to recover.
As above... HTC Oreo firmware is required to run a HTC based Oreo ROM.
As noted in my opinion, once you upgrade to Oreo you cannot go back to N, you will loose cell service.
So next steps... Flash Oreo firmware.. flash Oreo ROM & profit.
You may need to do a full /data format prior to flashing.
You may also have to go into the *#*#4636#*#* menu and change the preferred network type there depending on your carrier, I have Verizon and I have to do that when I restart the phone.
lightweaponx said:
You may also have to go into the *#*#4636#*#* menu and change the preferred network type there depending on your carrier, I have Verizon and I have to do that when I restart the phone.
Click to expand...
Click to collapse
I would say that could possibly work but my phone doesn't even know what my IMEI number is won't read a SIM card
steezee said:
I would say that could possibly work but my phone doesn't even know what my IMEI number is won't read a SIM card
Click to expand...
Click to collapse
If you installed the Oreo Firmware you have to stay on an Oreo ROM right now. Make sure you have the latest TWRP, wipe everything, format data (not wipe) then reinstall Lee's ROM.
LeeDroid said:
As above... HTC Oreo firmware is required to run a HTC based Oreo ROM.
As noted in my opinion, once you upgrade to Oreo you cannot go back to N, you will loose cell service.
So next steps... Flash Oreo firmware.. flash Oreo ROM & profit.
You may need to do a full /data format prior to flashing.
Click to expand...
Click to collapse
Do you mean flashing the stock firmware RUU file ? ..because when i download the exe i use from HTC i recieve a 132 error
BoganRabbit said:
Do you mean flashing the stock firmware RUU file ? ..because when i download the exe i use from HTC i recieve a 132 error
Click to expand...
Click to collapse
I assume they are mentioning 3.xx.xxx.xx firmware but I can't find any 3. firmware that will flash (I'm looking for [617] US Unlocked)
lightweaponx said:
If you installed the Oreo Firmware you have to stay on an Oreo ROM right now. Make sure you have the latest TWRP, wipe everything, format data (not wipe) then reinstall Lee's ROM.
Click to expand...
Click to collapse
where can i download the oreo firmware ?
BoganRabbit said:
where can i download the oreo firmware ?
Click to expand...
Click to collapse
what model of the HTC 10 do you have?
I found The following
WWE Oreo 3.16.401.2 firmware
US Unlocked Oreo 3.16.617.2 firmware
steezee said:
I would say that could possibly work but my phone doesn't even know what my IMEI number is won't read a SIM card
Click to expand...
Click to collapse
sad thing is that that did't work for me on Tmobile with Pure Fusion Os 8.0 or any other non Sense based rom
Im having the same issue. Mistakenly updated with the latest Leedroid without flashing OREO first. It wasnt ovbious from the Leedroid.co.uk page. Now after reflashing several RUU my IMEI is showing as unknown. I have S-OFF now so hopefully there's some way of fixing my screw up.
acs111 said:
Im having the same issue. Mistakenly updated with the latest Leedroid without flashing OREO first. It wasnt ovbious from the Leedroid.co.uk page. Now after reflashing several RUU my IMEI is showing as unknown. I have S-OFF now so hopefully there's some way of fixing my screw up.
Click to expand...
Click to collapse
Flash the Oreo RUU for your CID/MID and you should get it back
or
Flash the Oreo firmware (That matches your CID/MID) that I linked for your phone above (might as well just use the wipe one which is what I used to get my phone back)
Flash TWRP (if you used the fullwipe without TWRP, if not skip to the next step)
Install an Oreo based Rom (You can't go back to N or before)
Thanks, that worked
How do you flash the oreo firmware? with fastboot or through twrp? I did the same thing, now I'm stuck trying to fix my phone. I tried download mode through fastboot and through twrp, neither worked for me.
acs111 said:
Thanks, that worked
Click to expand...
Click to collapse
What do you mean? Can you do phone calls?. Please tell us, what did you do? Step by step
Are you s-on or s-off? Please, be gentle with us.. Regards..
CarlosRDonXDA said:
What do you mean? Can you do phone calls?. Please tell us, what did you do? Step by step
Are you s-on or s-off? Please, be gentle with us.. Regards..
Click to expand...
Click to collapse
He did as the post before his suggested. (and many other posts here on XDA regarding Oreo update)
You have to install Oreo RUU or Oreo firmware + Oreo rom.
It's as simple as that.
Since I have no clue what variant/model of HTC 10 you have from what little you posted, I can't/won't direct you to a specific RUU or firmware.
But the info needed to determine that, has been posted many times.
santod040 said:
He did as the post before his suggested. (and many other posts here on XDA regarding Oreo update)
You have to install Oreo RUU or Oreo firmware + Oreo rom.
It's as simple as that.
Since I have no clue what variant/model of HTC 10 you have from what little you posted, I can't/won't direct you to a specific RUU or firmware.
But the info needed to determine that, has been posted many times.
Click to expand...
Click to collapse
Thanks santod040, the same happens to me with piranya ROM.
Hope your help... My device is htc 10, Cid htc__332 latín América, 2PS650000, pmewl. No sim detected, no imei, no base band. Need I to be s-off?. Thanks in advance...
Excuse me... I have been playing with ROMs trying solve my problem, actually have installed crdroid nougat 7.1.2, and time ago, my daughter erase original system twrp backup.
CarlosRDonXDA said:
Thanks santod040, the same happens to me with piranya ROM.
Hope your help... My device is htc 10, Cid htc__332 latín América, 2PS650000, pmewl. No sim detected, no imei, no base band. Need I to be s-off?. Thanks in advance...
Click to expand...
Click to collapse
You need Oreo firmware to run an Oreo rom.
Paste the output of the following command from Download mode:
fastboot getvar all
Remove your serial and IMEI from the output before posting.
Sent from my HTC6545LVW using Tapatalk
Hello all,
Follow my guide at your own risk. Read everything SUPER carefully to fix your Verizon LTE network connectivity on your US Retail unlocked Motorola G5 Plus.
I am here to save you all from flashing your phone countless times to try to bring back LTE with no EFS backup and no persist backup.
Here is a guide for XT1687 U.S. version of Moto G5+ (potter) that brings back Verizon LTE on STOCK Firmware/Rom and gives you OTA updates after downgrading from custom 8.1 Oreo roms.
I have not been able to relock bootloader, but that is okay. I am on stock firmware with OTA updates working and LTE working again.
Here is what I did:
I went ahead and flashed POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml to bring my phone back to stock from OMNI Rom 8.1 Oreo custom rom.
Obviously there is a bug that makes your IMEI 0 and loses all network connectivity after you flash back to stock from Oreo 8.1 64 bit roms on this phone.
1) Download the STOCK firmware/rom for XT1687 I used and extract the files: POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2.) Install ADB
https://forum.xda-developers.com/showthread.php?t=2588979
3)Extract the firmware to a folder using 7zip or right-click and extract all to folder in windows, then
4.) boot into your Moto G5+ bootloader by holding: Volume Down + Power button
Open a command prompt, copy and paste the following commands after installing ADB & Fastboot, make sure you launch command prompt or change directory to the same directory as the extracted rom files (cd C:/rom files):
You can type in CMD: fastboot devices to see if your device serial number shows up and you are ready to flash, make sure you are in bootloader mode first.
Paste the following commands in cmd prompt:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
Boot into your new stock rom now and use WIFI to update OTAs:
Make sure USB debugging is enabled > goto settings > click on build number 5 times then go back and goto developer options > usb debugging checked on
Your network connectivity will still be broken until we patch persist file but continue through the whole bootup for stock rom, set it up from new, and install all the OTA updates available through WIFI first.
5.) Install OTA updates over WIFI even though your network connectivity still doesn't work yet. Your IMEI will be 0 and you will have no network access.
Install all OTA updates with WIFI until your phone is on Build number: NPNS25.137-93-10, there is no firmware file to download this build, so it must be updated through OTA on wifi (all OTAs together should be ~300-500mb total).
6.)Download TWRP 3.2.1.0 and flash it using the following command: fastboot flash recovery twrp-3.2.1-0-potter.img:
https://dl.twrp.me/potter/twrp-3.2.1-0-potter.img.html
7.) Go into TWRP > backup > check EFS so it creates a folder in your phone storage TWRP folder, and then copy it into to a folder on your computer for future backups.
8.) Download Persist file linked here and boot phone in bootloader mode, use PC to copy persist file into TWRP folder > Newly created EFS backup folder > Persist file in your phone storage:
Code:
[url="https://nofile.io/f/RuxbqZAQayH/persist.ext4.win"]https://nofile.io/f/RuxbqZAQayH/persist.ext4.win[/url]
9.) TWRP > restore > check EFS backup folder you made earlier with your new persist file in it (should be 193kb for persist file). > restore the backup for EFS & Persist > reboot phone once its done.
10.) Ta-dah! The Verizon LTE network signal should be instantly back after you rebooted your phone into android OS.
Let me know if it worked for you on other versions as well. Everything is at your own risk. It worked for me and I just flashed it today 06/20/2018.
Also, files are from other devs on XDA, just made the guide to highlight the process steps that worked for me.
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
vwfan511 said:
Hello all,
Follow my guide at your own risk. Read everything SUPER carefully to fix your Verizon LTE network connectivity on your US Retail unlocked Motorola G5 Plus.
I am here to save you all from flashing your phone countless times to try to bring back LTE with no EFS backup and no persist backup.
Here is a guide for XT1687 U.S. version of Moto G5+ (potter) that brings back Verizon LTE on STOCK Firmware/Rom and gives you OTA updates after downgrading from custom 8.1 Oreo roms.
I have not been able to relock bootloader, but that is okay. I am on stock firmware with OTA updates working and LTE working again.
........
5.) Install OTA updates over WIFI even though your network connectivity still doesn't work yet. Your IMEI will be 0 and you will have no network access.
Install all OTA updates with WIFI until your phone is on Build number: NPNS25.137-93-10, there is no firmware file to download this build, so it must be updated through OTA on wifi (all OTAs together should be ~300-500mb total).
Click to expand...
Click to collapse
Nice guide, just a little correction: There is in fact a fastboot flashable NPNS25.137-93-10 stock firmware, here's a mirror, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud (the one where customer service get the firmware) but not everyone was able to download it from there.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
Nice guide, just a little correction: There is in fact a fastboot flashable NPNS25.137-93-10 stock firmware, here's a mirror, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud (the one where customer service get the firmware) but not everyone was able to download it from there.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
thanks but the link is dead there, know anywhere else to get it? and there the same for ATT and verizon right?
vonwap said:
thanks but the link is dead there, know anywhere else to get it? and there the same for ATT and verizon right?
Click to expand...
Click to collapse
Hmm, I've just tried the link and it works - I'm downloading the NPNS25.137-93-10 stock ROM as I write this from that provided Google Drive link.
As for the AT&T or Verizon versions, I'm not sure (though I think that retus devices on Verizon may have NPNS25.137-93-10, someone with a US device would be better suited to comment). Also, if I recall, devices on Verizon were on a different update path, from NPN25.137-33 to NPN25.137-35 (March 2017 security patch), then to NPN25.137.43-5 (May 2017 security patch), then to NPN25.137-83 (Aug 2017 security patch) before NPN25.137-93 (Nov 2017 security patch), then you should also get NPNS25.137-93-4 (Jan 2018 security patch), NPNS25.137-93-8 (March 2018 security patch), then NPNS25.137-93-10 (April 2018 security patch).
I would also caution against downgrading to NPNS25-137-33-5 (May 2017 security patch), as described in the guide, if your stock firmware was updated to a version newer than the May 2017 security patch. The reason being that if you have a device with a newer stock firmware previously flashed to it, downgrading to the May 2017 firmware may go okay, but you run the risk of hard bricking your device (as installing old OTA updates overwrites your bootloader, which is still present from the newer stock firmware). If your device was previously on the May 2017 stock security patch or older, you may not risk a hard brick but downgrading comes with risks.
Thus, it's probably best to attempt to flash NPNS25.137-93-10 for EU, US and Asia devices or NPNS25.137-92-10 for Brazil and Indian devices to avoid a downgrade.
vonwap said:
thanks but the link is dead there, know anywhere else to get it? and there the same for ATT and verizon right?
Click to expand...
Click to collapse
The link should be working as you see above in the post of @echo92 who has also answered your question as good as I could, maybe better.
I'm also not sure about the firmware path. 33-5 was May security patch here too but as you can see on the screenshot below August 2017 security patch was 33-11, at least here in Europe.
I'm pretty sure that there's no difference in the latest Verizon or AT&T firmwares but as @echo92 said, maybe a US user knows more about that (if you want to be 100% sure about that).
Imo if you go with the latest 93-10 (April security patch) firmware you should be on the safe side as a US user. Firmwares ending on 92-x are for India,Brasil and Asia Pacific, they should work but you won't receive any OTA updates as the updates pushed in the US an Europe search for 93-x firmwares.
Try the link again, maybe in a different browser.
If you can't download it at all I will mirror it on another hoster. Just send me a PM.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
The link should be working as you see above in the post of @echo92 who has also answered your question as good as I could, maybe better.
I'm also not sure about the firmware path. 33-5 was May security patch here too but as you can see on the screenshot below August 2017 security patch was 33-11, at least here in Europe.
I'm pretty sure that there's no difference in the latest Verizon or AT&T firmwares but as @echo92 said, maybe a US user knows more about that (if you want to be 100% sure about that).
Imo if you go with the latest 93-10 (April security patch) firmware you should be on the safe side as a US user. Firmwares ending on 92-x are for India,Brasil and Asia Pacific, they should work but you won't receive any OTA updates as the updates pushed in the US an Europe search for 93-x firmwares.
Try the link again, maybe in a different browser.
If you can't download it at all I will mirror it on another hoster. Just send me a PM.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
thanks worked with firefox, Ima try and get my VoLTe back on x1687? flashed to pixle 4g works but just left b/c scared to mess it up again. backed up my efs though. what is the persist ?
Wolfcity said:
The link should be working as you see above in the post of @echo92 who has also answered your question as good as I could, maybe better.
I'm also not sure about the firmware path. 33-5 was May security patch here too but as you can see on the screenshot below August 2017 security patch was 33-11, at least here in Europe.
I'm pretty sure that there's no difference in the latest Verizon or AT&T firmwares but as @echo92 said, maybe a US user knows more about that (if you want to be 100% sure about that).
Imo if you go with the latest 93-10 (April security patch) firmware you should be on the safe side as a US user. Firmwares ending on 92-x are for India,Brasil and Asia Pacific, they should work but you won't receive any OTA updates as the updates pushed in the US an Europe search for 93-x firmwares.
Try the link again, maybe in a different browser.
If you can't download it at all I will mirror it on another hoster. Just send me a PM.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Confusingly, the US series of firmwares seemed to be on different update paths until recently, when Motorola wisely appeared to unify them. The US equivalent of the 33-11 Aug 2017 update for EU/Brazil (and India?), as you posted, was NPN25.137-83, which was a follow on from either NPNS25.137-33-5 (May 2017) or NPNS25.137-35-5 or NPN25.137.43-5 (depending on which US network you were on). Needless to say, it got messy with regards to firmware updates...
But yes, I concur with you that the NPNS25.137-93-10 firmware should be a safe bet (especially as it's currently the latest firmware we have available anyway).
vonwap said:
thanks worked with firefox, Ima try and get my VoLTe back on x1687? flashed to pixle 4g works but just left b/c scared to mess it up again. backed up my efs though. what is the persist ?
Click to expand...
Click to collapse
It's a part of the nandroid backup.
persist.img is "persist" which contains data which shouldn't be changed after the device shipped, for example: calibration data of chips(wifi, bt, camera, etc.), certificates and other security related files. I heard it should contain the IMEI too but I'm not sure about that. You can't back it up with the official TWRP but with some unofficial versions, take a look here: https://forum.xda-developers.com/g5-plus/how-to/psa-efs-persist-t3807240
There are persist files uploaded here on XDA but it's a very hacky way as you have to use a file from the Moto G4 with side effects like yellowish photos.
Check the related threads.
Sent from my Moto G5 Plus using XDA Labs
Hmm sort of worried b/c im on att not sure if it makes a difference. Ill try and report back.
Wolfcity said:
Imo if you go with the latest 93-10 (April security patch) firmware you should be on the safe side as a US user. Firmwares ending on 92-x are for India,Brasil and Asia Pacific
Click to expand...
Click to collapse
Just a correction to the above, Asia Pacific (retapac) uses the 93 series as well.
NZedPred said:
Just a correction to the above, Asia Pacific (retapac) uses the 93 series as well.
Click to expand...
Click to collapse
Ok, thx for the info. So the 92-x firmware is only for India and Brazil.
Sent from my Moto G5 Plus using XDA Labs
Dont use if on any other carrier than verizon
Don't use this if you are not on verizon, I flashed this thinking it would fix some issues I was having with camera on my XT1687 and cricket wireless but now my imei is 0 and unrecoverable. If some on has a presist file and using cricket or att please share so I can see if that will help get LTE and IMEI back.
What firmware rom did you flash?
Did you follow guide and flash persist in TWRP that I linked to? Are you coming from custom Oreo rom?
When you flash back to stock from Oreo roms you will automatically lose IMEI and network connectivity.
Persist file is linked in first post :good::
Code:
https://www23.zippyshare.com/v/13MfpRhg/file.html
TWRP recovery needs to be flashed again after you flash the stock firmware.
You need to make an EFS backup in TWRP Recovery to create the EFS folder in your phone storage, after you finish flashing stock rom.
The persist.img backup needs to be restored in TWRP after you place it in your newly created EFS folder in your TWRP folder on phone storage.
Restore persist.img in TWRP after flashing stock firmware, you should not be flashing firmware only. Persist.img is what gives you your LTE network signal and IMEI back.
Let me know if you have further issues.
vwfan511 said:
Did you follow guide and flash persist in TWRP that I linked to? Are you coming from custom Oreo rom?
When you flash back to stock from Oreo roms you will automatically lose IMEI and network connectivity.
Persist file is linked in first post :good::
Code:
https://www23.zippyshare.com/v/13MfpRhg/file.html
TWRP recovery needs to be flashed again after you flash the stock firmware.
You need to make an EFS backup in TWRP Recovery to create the EFS folder in your phone storage, after you finish flashing stock rom.
The persist.img backup needs to be restored in TWRP after you place it in your newly created EFS folder in your TWRP folder on phone storage.
Restore persist.img in TWRP after flashing stock firmware, you should not be flashing firmware only. Persist.img is what gives you your LTE network signal and IMEI back.
Let me know if you have further issues.
Click to expand...
Click to collapse
Yep flashed presist file in link along with efs after rolling back to the firmware version you recommend, even went back to the the one prior to that after losing IMEI. Whatever I did screwed me up big time. Was able to get 3G back on stock but still no IMEI number. Really not sure what changed or went differently this time compared to other times that I've followed similar steps with no problems but whatever it was has caused me to lose 4G and IMEI completely without being able to recover it by flashing Oreo ROMs. Ohhh well I'll be keeping my eye out on deals at best buy now lol.
Wolfcity said:
Nice guide, just a little correction: There is in fact a fastboot flashable NPNS25.137-93-10 stock firmware, here's a mirror, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud (the one where customer service get the firmware) but not everyone was able to download it from there.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
tuxattack80 said:
Yep flashed presist file in link along with efs after rolling back to the firmware version you recommend, even went back to the the one prior to that after losing IMEI. Whatever I did screwed me up big time. Was able to get 3G back on stock but still no IMEI number. Really not sure what changed or went differently this time compared to other times that I've followed similar steps with no problems but whatever it was has caused me to lose 4G and IMEI completely without being able to recover it by flashing Oreo ROMs. Ohhh well I'll be keeping my eye out on deals at best buy now lol.
Click to expand...
Click to collapse
Try flashing Omni rom.. when I lost mine it wasn't working on other Oreo roms and PixelExperience was forceclosing nonstop, couldn't even get it to boot.
Code:
[URL="http://dl.omnirom.org/potter/"]http://dl.omnirom.org/potter/[/URL]
. My IMEI and 3g came back on Omni, then went back to stock and flashed persist..
Also make sure your TWRP is fully updated to 3.2.1.0, wipe cache dalvik...etc
vwfan511 said:
Try flashing Omni rom.. when I lost mine it wasn't working on other Oreo roms and PixelExperience was forceclosing nonstop, couldn't even get it to boot.
Code:
[URL="http://dl.omnirom.org/potter/"]http://dl.omnirom.org/potter/[/URL]
. My IMEI and 3g came back on Omni, then went back to stock and flashed persist..
Also make sure your TWRP is fully updated to 3.2.1.0, wipe cache dalvik...etc
Click to expand...
Click to collapse
okay thanks i'll give it a shot
Does anyone have a different way to get the persist file. The little zippy thing wants to have me downloading other crap that i dont want??
this worked fine for me on att, coming from google pixle oreo with working efs, restored my efs and this persists,
but my bootloader still says "ID: bad key" not sure if it matters. should i relock my boot loader? or not worry
Archangel said:
Does anyone have a different way to get the persist file. The little zippy thing wants to have me downloading other crap that i dont want??
Click to expand...
Click to collapse
Here's a mirror link for you:
https://nofile.io/f/RuxbqZAQayH/persist.ext4.win
https://nofile.io/g/ZH3emEjoBxxnId89k5DfprKEpe4Ikpis5p85S8edrSibxiLtMzbfYNS0tAx9qE4Q/persist.ext4.win/
Click to expand...
Click to collapse
Reuploaded for you on a different mirror as zippyshare has ads/bs now.
vonwap said:
this worked fine for me on att, coming from google pixle oreo with working efs, restored my efs and this persists,
but my bootloader still says "ID: bad key" not sure if it matters. should i relock my boot loader? or not worry
Click to expand...
Click to collapse
Relocking bootloader may not be possible unless you're on the latest firmware, I haven't relocked mine yet.
I am waiting for official Oreo update to go ahead and try... you can try the relock commands with the latest OTA firmware file.. but I can't guarantee it will work.
Basically forgot that I'd unlocked the bootloader and allowed the update, pretty stupid
Pretty sure that the next step from here is to flash the stock firmware, unless I'm mistaken?
Looking for any firmware for the XT1922-2 JETER model, which I think is an exclusively UK thing. Haven't been able to find any thus far which is both Jeter and XT1922-2, so would be intensely grateful if someone could help me!
Craventoby said:
Basically forgot that I'd unlocked the bootloader and allowed the update, pretty stupid
Pretty sure that the next step from here is to flash the stock firmware, unless I'm mistaken?
Looking for any firmware for the XT1922-2 JETER model, which I think is an exclusively UK thing. Haven't been able to find any thus far which is both Jeter and XT1922-2, so would be intensely grateful if someone could help me!
Click to expand...
Click to collapse
Yes just reflash latest stock firmware and you'll be good and what's your sw channel version? Like does it say reteu or something like that. There alot of models under the xt11922-2 device number.
ninjakira said:
Yes just reflash latest stock firmware and you'll be good and what's your sw channel version? Like does it say reteu or something like that. There alot of models under the xt11922-2 device number.
Click to expand...
Click to collapse
Unfortunately I've already tried flashing a few different firmware versions without success, so it just says the most recent version of that. Are there any models under the XT1922-2 called Jeter? I haven't been able to find any.
Craventoby said:
Unfortunately I've already tried flashing a few different firmware versions without success, so it just says the most recent version of that. Are there any models under the XT1922-2 called Jeter? I haven't been able to find any.
Click to expand...
Click to collapse
That's not Jeter. It's Aljeter. There's a bunch with that model number. But helps if know your original software channel.
madbat99 said:
That's not Jeter. It's Aljeter. There's a bunch with that model number. But helps if know your original software channel.
Click to expand...
Click to collapse
I dunno what to tell you, it says Jeter on the bootloader screen. Will have another go at flashing Aljeter software, but hasn't worked so far.
Craventoby said:
I dunno what to tell you, it says Jeter on the bootloader screen. Will have another go at flashing Aljeter software, but hasn't worked so far.
Click to expand...
Click to collapse
Some say Jeter in one line of props, then Aljeter in another. I know it's stupid. But all the ones with your model number (that I have seen anyways) are Aljeter. I could be wrong. But I don't think there is a Jeter with 3 GB of RAM
ninjakira said:
Yes just reflash latest stock firmware and you'll be good and what's your sw channel version? Like does it say reteu or something like that. There alot of models under the xt11922-2 device number.
Click to expand...
Click to collapse
Having some trouble, I get error messages when I try and flash both gpt.bin and bootloader.img - for both I get an error saying that the image failed validation/ preflash validation/ remote failure. Is there something I'm not doing?
Craventoby said:
Having some trouble, I get error messages when I try and flash both gpt.bin and bootloader.img - for both I get an error saying that the image failed validation/ preflash validation/ remote failure. Is there something I'm not doing?
Click to expand...
Click to collapse
You're likely trying to downgrade or have a locked bootloader, or both.
Craventoby said:
Having some trouble, I get error messages when I try and flash both gpt.bin and bootloader.img - for both I get an error saying that the image failed validation/ preflash validation/ remote failure. Is there something I'm not doing?
Click to expand...
Click to collapse
You can't downgrade if the gpt.bin has been updated which it has. Use the latest most recent firmware and everything should be fine. If the latest firmware has not been uploaded then I'm sorry to say your stuck with a bricked phone until the latest firmware is uploaded. Keep checking the link with the firmwares untill you see the latest one
ninjakira said:
You can't downgrade if the gpt.bin has been updated which it has. Use the latest most recent firmware and everything should be fine. If the latest firmware has not been uploaded then I'm sorry to say your stuck with a bricked phone until the latest firmware is uploaded. Keep checking the link with the firmwares untill you see the latest one
Click to expand...
Click to collapse
Actually, after trying the whole thing over a second time, flashing each command line by line, my phone is fixed. Have no idea how if what you're saying about it being impossible to downgrade is right, but certainly not complaining. In the end, the RETGB software for ALJETER was the one that worked.
Craventoby said:
Actually, after trying the whole thing over a second time, flashing each command line by line, my phone is fixed. Have no idea how if what you're saying about it being impossible to downgrade is right, but certainly not complaining. In the end, the RETGB software for ALJETER was the one that worked.
Click to expand...
Click to collapse
Hey as long as my guide helped you that all I care about In the end lol the biggest common issue most people have is not paying attention to the command lines lol. Glad your able to enjoy your phone. And it sounds exactly it sounds once the gpt.bin is updated you can't use a older firmware which in turn would be downgrading.
lol am I the only one who's been taking updates with unlocked bootloader having no problems?
blowingoff said:
lol am I the only one who's been taking updates with unlocked bootloader having no problems?
Click to expand...
Click to collapse
it seems the problem people are having is after they have already rooted their devices they're trying to take an ota update. Which you can't do. Having an unlocked bootloader doesn't affect that. the reason is because the stock recovery has been replaced by twrp. In order to install an ota update when your phone is rooted you must reflash either the stock firmware of the current version you're on or just flash the new stock firmware. Or in this case accidentally using the command lines wrong lol
ninjakira said:
it seems the problem people are having is after they have already rooted their devices they're trying to take an ota update. Which you can't do. Having an unlocked bootloader doesn't affect that. the reason is because the stock recovery has been replaced by twrp. In order to install an ota update when your phone is rooted you must reflash either the stock firmware of the current version you're on or just flash the new stock firmware. Or in this case accidentally using the command lines wrong lol
Click to expand...
Click to collapse
yes, just what I thought. unlocked bootloader doesnt change anyrhing, but having the phone system modified may do
ninjakira said:
it seems the problem people are having is after they have already rooted their devices they're trying to take an ota update. Which you can't do. Having an unlocked bootloader doesn't affect that. the reason is because the stock recovery has been replaced by twrp. In order to install an ota update when your phone is rooted you must reflash either the stock firmware of the current version you're on or just flash the new stock firmware. Or in this case accidentally using the command lines wrong lol
Click to expand...
Click to collapse
Also, people confusing 2 different issues regarding updates.
The only REAL issue I've heard is, after flashing firmware on an unlocked bootloader, they are no longer receiving OTA updates. Maybe changed their update channel or something.
madbat99 said:
Also, people confusing 2 different issues regarding updates.
The only REAL issue I've heard is, after flashing firmware on an unlocked bootloader, they are no longer receiving OTA updates. Maybe changed their update channel or something.
Click to expand...
Click to collapse
Yea that's why I've been starting to ask for sw channel version ? its been alot more helpful knowing that before anything lol. I haven't had any issue flashing stock firmware then taking an ota update its how I was able to take the latest security patch update as well as the other updates before they were uploaded on the firmware site ( I hate saying mirrors.lolinet because well darkweb has sites called that also unfortunately and there just not good lol) but that's just me lol