After i flashed Twrp my phone wont get any service and i have checked imei and it is at 00000000. Is there a way to fix this?
I have my original imei number with me
Any help would be appreciated
R0gueThund3r said:
After i flashed Twrp my phone wont get any service and i have checked imei and it is at 00000000. Is there a way to fix this?
I have my original imei number with me
Any help would be appreciated
Click to expand...
Click to collapse
You pure or style? Try pulling sims card and reinsert? Not heard that one just from flashing twrp.
Sent from my XT1575 using Tapatalk 2
milski65 said:
You pure or style? Try pulling sims card and reinsert? Not heard that one just from flashing twrp.
Sent from my XT1575 using Tapatalk 2
Click to expand...
Click to collapse
I am using the pure and i have tried reinserting the sim card , and i checked the sim card in another phone and it works
R0gueThund3r said:
I am using the pure and i have tried reinserting the sim card , and i checked the sim card in another phone and it works
Click to expand...
Click to collapse
You've done nothing else but unlock bootloader and twrp via adb?
Sent from my XT1575 using Tapatalk 2
milski65 said:
You've done nothing else but unlock bootloader and twrp via adb?
Sent from my XT1575 using Tapatalk 2
Click to expand...
Click to collapse
That and adding super Su
R0gueThund3r said:
That and adding super Su
Click to expand...
Click to collapse
I'll keep looking, but I haven't seen that mentioned.
Sent from my XT1575 using Tapatalk 2
I've got the same issue, unlocked the bootloader and flashed TWRP via the command line (as well as SuperSU via TWRP). Rebooted and re-inserted the SIM multiple times to no avail.
Edit: I've tried looking for the APN settings on my device, but that seems to have disappeared as well? here's a screenshot of what my settings screen looks like: https://gyazo.com/90f9ab027357cea8009bdae1a0346690
Edit 2: I checked my IMEI, and it's weird...I see every digit except for the last one when I look for it via the *#06# dialer command (I know because I cross-referenced with the IMEI printed on the box the phone came in).
---------- Post added at 11:46 AM ---------- Previous post was at 11:24 AM ----------
R0gueThund3r said:
That and adding super Su
Click to expand...
Click to collapse
have you had any luck resolving the issue?
Mine did the same thing. Flashed TWRP and SuperSU. Then I copied a few apks and jars from /system for vendor blobs with root explorer. I don't see how anything changed there because system is read only (but it was ril related files).
After some digging I had my IMEI but my phone number was "Unknown". I went to AT&T for a new sim but that didn't fix it. I ended up going back to stock with this thread: http://forum.xda-developers.com/mo...dows-tool-moto-x-style-pure-edition-t3199905 and everything is working again.
TWRP and root again and so far still have network.
rwaterspf1 said:
Mine did the same thing. Flashed TWRP and SuperSU. Then I copied a few apks and jars from /system for vendor blobs with root explorer. I don't see how anything changed there because system is read only (but it was ril related files).
After some digging I had my IMEI but my phone number was "Unknown". I went to AT&T for a new sim but that didn't fix it. I ended up going back to stock with this thread: http://forum.xda-developers.com/mo...dows-tool-moto-x-style-pure-edition-t3199905 and everything is working again.
TWRP and root again and so far still have network.
Click to expand...
Click to collapse
I used that to reset but i still get the problem
R0gueThund3r said:
I used that to reset but i still get the problem
Click to expand...
Click to collapse
Did you solve your problem??
im getting no service after Unlock bootloader and flash TWRP.
rwaterspf1 said:
Mine did the same thing. Flashed TWRP and SuperSU. Then I copied a few apks and jars from /system for vendor blobs with root explorer. I don't see how anything changed there because system is read only (but it was ril related files).
After some digging I had my IMEI but my phone number was "Unknown". I went to AT&T for a new sim but that didn't fix it. I ended up going back to stock with this thread: http://forum.xda-developers.com/mo...dows-tool-moto-x-style-pure-edition-t3199905 and everything is working again.
TWRP and root again and so far still have network.
Click to expand...
Click to collapse
I also have lost service after flashing some ROMS on my VZ MXP. Reinserting the SIM, reflashing other ROMs or reflashing the radio haven't helped. I'll give this a try. Thanks.
What ROM are you using? Did you recently upgrade from lollipop to marshmallow or marshmallow to nougat? Have you ran fastboot erase all (if not DO NOT that causes the imei to be permenantly erased). Have you tried flashing files from the factory image? This is very strange.
thebaconbox said:
What ROM are you using? Did you recently upgrade from lollipop to marshmallow or marshmallow to nougat? Have you ran fastboot erase all (if not DO NOT that causes the imei to be permenantly erased). Have you tried flashing files from the factory image? This is very strange.
Click to expand...
Click to collapse
The loss of service occurred after flashing the 11/11/16 nightly of AICP, which I believe is Nougat. I had already had the 11/09 and 11/10 nightly installed. The 11/10 seemed to perform OK, except battery life was short. The 11/11 version caused a bunch of com.android.phone errors. I then reflashed the stock ROM posted here, but the problem persists. I haven't tried the factory image. Do you have a link to the process to do that?. I'm currently using my GS3 and that phone is way too slow, definitely would like to go back to my MXP.
rwaterspf1 said:
Mine did the same thing. Flashed TWRP and SuperSU. Then I copied a few apks and jars from /system for vendor blobs with root explorer. I don't see how anything changed there because system is read only (but it was ril related files).
After some digging I had my IMEI but my phone number was "Unknown". I went to AT&T for a new sim but that didn't fix it. I ended up going back to stock with this thread: http://forum.xda-developers.com/mo...dows-tool-moto-x-style-pure-edition-t3199905 and everything is working again.
TWRP and root again and so far still have network.
Click to expand...
Click to collapse
OK, I used this tool. It fixed the problem, and have restored service. Had to also do the wifi fix, which is discussed later in that thread. Thank you.
can u please me how you fix that , i have few units same issue no service
Gsm UK said:
can u please me how you fix that , i have few units same issue no service
Click to expand...
Click to collapse
Your units are not the same, they are XT1578 engineering units which were intended for Verizon specific service, but never came to fruition... those units are likely fancy paperweights now, no ROM or radios were ever released for them since they used a special chipset.
This may be a stupid question, but did you clean flash or dirty flash the stock ROM and/or aicp? Make sure you fully wipe/format system, boot, cache, data, and dalvik cache when flashing new ROMs.
I also have problems with the network, no signal, plus my appears the normal imei, Moto X Style Brazil.
{
"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"
}
Anyone from you guys with no service devices got the solution or not?
Related
I tried to update my 9020a to the 4.0.4, was somewhat successful except not cellular connection. I have blank bars for signal with an x in it.
My IEMI shows correct in the EFS folder
I tried flashing my radio many times, I have UCKF1. I tried the original one, it failed but was able to flash the new version. But, I still have the same problem and it shows my baseband ver as i9020xxki1
I then went back to the pixel rom I had on before, same thing, no mobile network.
Then i brought my phone back to GB, I had a rooted nandroid. Same issue
what the hell happened and how do I get it back.
im actually really glad i have the patience to wait for the official release of ICS and don't jump on every leak and spend hours trying to fix what could of been avoided.
THIS LEAK ISN'T FOR THE I9020A!
I know it was not for the 9020a, but there is others that were successful. I got it to run, and it worked great, except the radio issue.
Now Im all the way back on GB, and still cant get it to work.
I am tired of waiting. This is not my first android and I bought this phone for the updates. Well, its just like every other att devices, updates just dont come this way.
so, how do i get signal back
blackhemi4x4 said:
I know it was not for the 9020a, but there is others that were successful. I got it to run, and it worked great, except the radio issue.
Now Im all the way back on GB, and still cant get it to work.
I am tired of waiting. This is not my first android and I bought this phone for the updates. Well, its just like every other att devices, updates just dont come this way.
so, how do i get signal back
Click to expand...
Click to collapse
what is your radio version??flash your old radio maybe will fix it..
Flash working radio for i9020a.
UCKF1 is the radio, ive tried both versions.
screenshot
here is the screenshot of the status area. Not pictured is my IEMI, but it is correct. Its acting like the radio is off. Ive even toggled the radio off and on.
{
"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"
}
If you've made a backup of your EFS folder, repush it to your phone. That fixed my problems regarding radio a few times already.
1. Go to Dialer. Dial *#*#4636#*#*
2. Go to Phone information. Choose the preferred network to
"GSM Auto PRL" or "CDMA Auto PRL" or whatever you have.
3. Scroll down, deactivate and activate Phone Radio.
4. Press Menu button.
5. Select Phone frequency, then choose your country.
6. In the previous menu push the Home button to go back to Homescreen.
7. Reboot.
(By Brainmaster)
try this...
fixed had to replace efs folder and use a totally new radio.
stock 4.0.4 is way awesome
Thanks y'all
what radio did you end up using? I'm having the same problem on 4.0.4...
varandian said:
what radio did you end up using? I'm having the same problem on 4.0.4...
Click to expand...
Click to collapse
UCKE1 fixed it for me.
I put KD1 on for my 9020a on AT&T (I get better data speeds with an older radio for some strange reason) and DELETED /efs, rebooted, and it started working. To anyone else reading this, backup /efs before trying ANY of this.
varandian said:
I put KD1 on for my 9020a on AT&T (I get better data speeds with an older radio for some strange reason) and DELETED /efs, rebooted, and it started working. To anyone else reading this, backup /efs before trying ANY of this.
Click to expand...
Click to collapse
Did you replace your EFS folder or just delete it?
If you replaced it, what command did you use to replace it?
---------- Post added at 08:45 PM ---------- Previous post was at 08:11 PM ----------
I'm completely at a loss.
I tried deleting the contents of my EFS folder, replacing it with the backup files, rebooting and still no luck.
Still no signal.
Any advice?
iboj007 said:
Did you replace your EFS folder or just delete it?
If you replaced it, what command did you use to replace it?
---------- Post added at 08:45 PM ---------- Previous post was at 08:11 PM ----------
I'm completely at a loss.
I tried deleting the contents of my EFS folder, replacing it with the backup files, rebooting and still no luck.
Still no signal.
Any advice?
Click to expand...
Click to collapse
i replaced my whole efs folder with the one I had backed up.
What radio do you have installed now??
blackhemi4x4 said:
i replaced my whole efs folder with the one I had backed up.
What radio do you have installed now??
Click to expand...
Click to collapse
I have XXKB3 right now... can't seem to get UCKE1
iboj007 said:
I have XXKB3 right now... can't seem to get UCKE1
Click to expand...
Click to collapse
does KE1 not flash for you or not able to get it to download
blackhemi4x4 said:
does KE1 not flash for you or not able to get it to download
Click to expand...
Click to collapse
HA! flashed it via CWM and now its back!!!!! Anyone who has this issue, try flashing UCKE1 via CWM!
Sweet, that was the only one that worked for me. Now go and enjoy 4.0.4
Im still on my first charge from this morning. I love it!
Instable network connection on I9020XXKF1
Since I updated to 4.0.3 I've been having random network connection issues: Sometimes when waking the phone from sleep while connected to wifi the signal bar is empty only fix is to reboot the phone. I've updated to 4.0.4 on Wednesday and still have this issue. I was wondering if any of you have a suggestion for a better radio for the GSM/UMTS version of the i9020. I9020XXKF1 is supposed to be the most stable radio, unfortunately it isn't for me. Anyone else experiencing similar issues?
Hey all,
So i recently flashed back to stock and since my mobile radio has just stopped. Does anyone have this same problem, or can anyone help me fix this problem? Thanks!
Tgab100 said:
Hey all,
So i recently flashed back to stock and since my mobile radio has just stopped. Does anyone have this same problem, or can anyone help me fix this problem? Thanks!
Click to expand...
Click to collapse
You'll need to elaborate on how exactly you flashed back to stock.
Heisenberg said:
You'll need to elaborate on how exactly you flashed back to stock.
Click to expand...
Click to collapse
I flashed back to stock using the Nexus Root Toolkit by Wugfresh. I just flashed CM 13.0 to see if the problem was a hardware malfunction, but the mobile radio worked while running cyanogenmod. I am not downloading the factory image and I am going to attempt to flash it manually. Any ideas of comments? I really have not clue as to why the radio isn't working other than that it might be caused by flashing through the Nexus Root Toolkit.
Tgab100 said:
I flashed back to stock using the Nexus Root Toolkit by Wugfresh. I just flashed CM 13.0 to see if the problem was a hardware malfunction, but the mobile radio worked while running cyanogenmod. I am not downloading the factory image and I am going to attempt to flash it manually. Any ideas of comments? I really have not clue as to why the radio isn't working other than that it might be caused by flashing through the Nexus Root Toolkit.
Click to expand...
Click to collapse
Yeah, probably due to the toolkit. This is why I recommend people not use the damn things. Flash the factory images and you should be fine, I have instructions in my guide if you need them.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
Yeah, probably due to the toolkit. This is why I recommend people not use the damn things. Flash the factory images and you should be fine, I have instructions in my guide if you need them.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
So i was thinking that the system I'm running right now with the broken radio is corrupt so when i flash the factory image, is there a way I can erase everything? I want to make sure I'm flashing the image clean.
Tgab100 said:
So i was thinking that the system I'm running right now with the broken radio is corrupt so when i flash the factory image, is there a way I can erase everything? I want to make sure I'm flashing the image clean.
Click to expand...
Click to collapse
If you flash the factory images they overwrite what's already there.
Heisenberg said:
This is why I recommend people not use the damn things.
Click to expand...
Click to collapse
{
"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"
}
Heisenberg said:
If you flash the factory images they overwrite what's already there.
Click to expand...
Click to collapse
So I flashed the factory images using your method provided and I am still having the same issue Let me describe a little more in detail what exactly is going on. So obviously mobile data isn't working, including LTE 4G, 3G, and 2G, but I get calls and texts no problem. When I look at my status bar, LTE is not showing up, but if I pull down the quick toggles the phone says I have LTE connection but no data is coming in or going out. LTE also loses connection when I turn off "Enhanced 4G LTE Mode" (I'm on T-Mobile). Additionally, when I create a mobile hotspot, data works but only on 3G speeds. I honestly don't know what I'm doing wrong. Maybe i'm flashing the wrong factory image? I flashed MDB08M.
Same here with SkipSoft Toolkit, after unlock, root, busybox, wifi noproblem, but no LTE/3G on my phone, i try to relock bootloader and back to Factory image now.
Sigh!?!
Tgab100 said:
So I flashed the factory images using your method provided and I am still having the same issue Let me describe a little more in detail what exactly is going on. So obviously mobile data isn't working, including LTE 4G, 3G, and 2G, but I get calls and texts no problem. When I look at my status bar, LTE is not showing up, but if I pull down the quick toggles the phone says I have LTE connection but no data is coming in or going out. LTE also loses connection when I turn off "Enhanced 4G LTE Mode" (I'm on T-Mobile). Additionally, when I create a mobile hotspot, data works but only on 3G speeds. I honestly don't know what I'm doing wrong. Maybe i'm flashing the wrong factory image? I flashed MDB08M.
Click to expand...
Click to collapse
I honestly don't know what's going on there, it might be worth trying the L build instead of M.
Can you download latest nexus 6p android m image and flash each file manually? It's going to wipe everything but will return everything to stock. Let me know if you need help with flashing stock files via adb.
badboy47 said:
Can you download latest nexus 6p android m image and flash each file manually? It's going to wipe everything but will return everything to stock. Let me know if you need help with flashing stock files via adb.
Click to expand...
Click to collapse
I seem to have touched that issue I was on the L build and went to M build using toolkit but noticed my apns got screwy so I corrected them and I'm on pure nexus and a-ok now!
I'm having a similar but different issue, I bought a used 6p... Good ESN.... A 64 GB to upgrade from my current 32 GB 6p. Everything works (including mobile data and texts) except for phone calls, it won't call out and goes strait to voicemail when calling in.
I had unlocked the bootloader and installed chroma, but still no phone calls, so I flashed back to stock and relocked the bootloader. Still nothing. I read this thread suggesting that I shouldn't use the automated tool kits, so I backed up and manually flashed it back to the latest stock image via fastboot. But same issue.... Back to no phone calls in or out, everything else working though.
Any suggestions?
Justin
For those of you experiencing this, are your still able to see your imei number through settings>about phone>imei info?
kboya said:
For those of you experiencing this, are your still able to see your imei number through settings>about phone>imei info?
Click to expand...
Click to collapse
For me, yes. I can see my imei from the normal "about phone" settings menu.
Justin
Delete and readd your APN for your carrier.
Hi everyone, posting this as a information about something you should NOT try: upgrade your OTA rom with custom recovery installed, in my case TWRP.
I did this with ignorance of not think that (or search about) the custom rom could interfere at the normal process of OTA upgrade from Lollipop to MarshMallow. Actually I remembered that I was unlocked and rooted the phone but I did not remember I was using custom recovery. AFAIK at this device is impossible to root without unlocking and custom recovery.
{
"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"
}
If you are on TWRP don't do this!
For those don't know about TWRP and OTA updates, read this:
https://twrp.me/faq/officialota.html
In short terms: don't try OTA updates (official updates) if you installed custom rom such as TWRP. "Installing official updates from your manufacturer or carrier is not supported by TWRP." "[This] may result in unexpected behavior" "Most of the time the best way to get a new update onto your device is to simply wait a couple of days for ROM makers for your device to come up with ROMs that are based on the new update that you can safely and easily install."
But I did it. And now I'm reporting it for those who are curious. So, what's happened?
Fortunately the device is not bricked as I thought when it reboot to TWRP for flashing the OTA update instead of the stock recovery process! I thought that I messed everything when I see the frozen TWRP for something about 10 minutes or less. After the long 10 minutes of frozen TWRP image I got the recovery working and checked the log:
Of course, errors on the log.
Rebooted and got a frozen background image, after a while a permanent black. When the screen turn off the notification system shows the battery as dead (and it as not). But I could turn it off and gain access to the recovery holding power and volume down buttons.
After two failed reboots to the system with the same result I tried to make a screenshot using the hard buttons and it works (screenshoted the black screen) and suddenly the lock screen shows up. I got into, everything working slow meaning that there was a lot things working in the background. Got some error messages from google service and MMS/SMS communication and minutes later it automatically reboots and booted the TWRP again.
This turned to a loop. I stopped this by going to the system setup - about the device - check for updates. And got a message "the update has failed". Good. After a while the message offering the update shows again... No, thanks...
I rebooted to TWRP and fixed the permissions, maybe this solve some problems.
Right now the phone is working but the rebooting process has unexpected behaviors, some tries result in a normal fast process and other tries result in a long black image and the system/launcher just don't arm up for some minutes, but after a while it works. I'm not confident. Already backed up apps with Titanium backup.
I'm planning to restore everything from the stock using this guide:
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
And them, maybe, update the OTA to marshmallow. Before doing that, I will search and get to know if it is possible to re-root the phone with marshmallow in osprey (that means re-unlock and install TWRP again). Rooted device it's a need for me.
This is what happened to my device when tried to OTA update with TWRP. I had luck not bricking this.
+1 on the dumb attempt. Early morning, excited for the release, upgrade please! Yeah, no good. Is restoring our only option? Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery ?
Sent from my Nexus 6 using Tapatalk
Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
Click to expand...
Click to collapse
Yeah, DON'T proceed with the update! Deleting the downloaded files just break the process... My advise is to make a backup before deleting this.
sgloki77 said:
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery
Click to expand...
Click to collapse
Ok, sorry about the huge wall of text.
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
golgiapp said:
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
Click to expand...
Click to collapse
:good:
Good to know that a factory reset could fix the problems caused by the OTA update with TWRP. But after this it should remain with custom recovery and not possible to OTA update. for stock MM
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Not sure, but take a look at /cache
gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
/data/data/com.motorola.ccc.ota/app_download
hp420 said:
/data/data/com.motorola.ccc.ota/app_download
Click to expand...
Click to collapse
found it!!
thanks extracted ok !!
its a zip flashable,can it be converted to install like the oem recovery images using the adb method?
gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Thank you for the warning
---------- Post added at 12:58 AM ---------- Previous post was at 12:54 AM ----------
Thank you for the warning
I experience this today, I flashed a stock rom again so I can have the OTA update, but what I can't do is root my device, I flash the custom recovery and then I flash the beta version of SuperSU, and when I reboot my device it bricks in the Motorola Logo, anybody knows how to fix this, or should I wait a little bit longer to root my phone? as the OP I need root too
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
nelsonw said:
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
VicSanRED said:
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
Click to expand...
Click to collapse
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
hp420 said:
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
Click to expand...
Click to collapse
I tried with the latest version 2.66 and still the same issue. Don't know what to do now.
So its posible to root MM ?? Safe ,stable?
Supersu v 2.62??
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
nelsonw said:
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Can you post a little tutorial?, I wanna be sure I'm doing everything OK.
So yeah, I messed up big time.
I don't know what to do anymore, I tried a normal factory reset, didn't work.
For the moment, I switched my SIM to the second slot but I think I don't have 3G anymore.
I'm not rooted, have stock recovery and my bootloader is locked.
Also I don't have any backup of any partition.
Please help me I'm so screwed...
What did you do?
I went into the MTK test menu and pressed USA band.
It overwrote my baseband on my first SIM slot.
Also I'm on B06.
http://forum.xda-developers.com/showthread.php?p=70336140
I need to flash my phone?
What version do I need to flash?
Same one you are on now would be a good start.
Thanks for helping me, I'm gonna flash it tonight
Hope it works
Hey so I just flashed the B06 bootstack and system from DrakenFX but my problem on my first sim card slot is still present...
I found this thread but it is about the Moto X Play : https://forum.xda-developers.com/moto-x-play/help/network-band-changed-to-usa-t3278614
Can the same method be applied to the Axon 7?
I kinda need my first sim card slot back
PlexBender said:
Hey so I just flashed the B06 bootstack and system from DrakenFX but my problem on my first sim card slot is still present...
I found this thread but it is about the Moto X Play : https://forum.xda-developers.com/moto-x-play/help/network-band-changed-to-usa-t3278614
Can the same method be applied to the Axon 7?
I kinda need my first sim card slot back
Click to expand...
Click to collapse
Did you manage to get your 1st sim back to work?
Have u tried flashing a full .Zip that also contains the modem BLOB? Like the B09 zip
Gesendet von meinem ZTE A2017G mit Tapatalk
So yeah I managed to get it to work again, forgot to update the thread.
I zeroed the modemst1 partition with a dd as only my first sim tray was affected and after a reboot the problem was fixed.
Flashing a full zip didn't work, the partition was damaged and by zeroing it out, the modem hardware regenerated it.
Thanks for the concern!
Hello, can you please explain in steps what you did to fix it? I did the same thing by accident and now I have no connection to the carrier of the sim
No prob.
Save your EFS partition via TWRP beforehand.
Connect your phone to your PC and go to an APB window
Then type:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
That fixed for me. To be sure your IMEI are still there right?
Cause if you don't have your IMEI anymore I'm quite sure you're in bad luck because that method won't fix your IMEI but it will fix the baseband.
Thank you very much, i fixed it! First i unlocked the bootloader and installed TWRP, then i typed these commands in the TWRP advanced/terminal and they worked like a charm. Thanks again
You were fast!
No problem I've been here before, feels good to be able to help!
Hello.
I did the same thing :-/ went to secret menu with some code which I found ... and chose USA BAND. Now, I don't have 2G/3G on SIM1 slot.
LTE (4G) seems to work.
I moved my SIM-card in SLOT 2 and there I have 2G/3G/4G. But, in that second slot I use SD-CARD so I want to fix my first slot.
Is there any easy way to fix that?
I am on stock A2017G v.B10, no root, no twrp, and I don't want to lose my warranty
Thanks in advance for any help or info.
Best regards
Unlock, fix it, relock?
Sent from my ZTE A2017U using Tapatalk
thefiqs said:
Unlock, fix it, relock?
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
Yes, I unlocked it, rooted, and ended up with no IMEI [emoji15]
{
"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"
}
Any way to fix that?
Sent from my ZTE A2017G using Tapatalk
What twrp you have? Restored EFS? ?
Sent from my ZTE A2017U using Tapatalk
thefiqs said:
What twrp you have? Restored EFS? ?
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
TWRP 3.0.4.1 and NO EFS backup :-/
---------- Post added at 08:00 PM ---------- Previous post was at 07:49 PM ----------
Now I have successfully updated to LineageOS, but still no IMEI
Is it possible to somehow write new (my) IMEI to the phone?
Hello folks,
I have Galaxy S4, Play Edition, GT-I9505G, currently running SlimROM 7.1.2 build 1.17 (dated 20180115) and baseband version I9505GUEUDNL3.
Last stock I had on this phone was Android 5.0. If there was any OTA after that, I didn't install it.
(Sam Mobile does not list this device, hence no way of knowing firmwares, but https://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4/GT-I9505G lists mine as the last firmware.)
I have been trying to install Lineage 15/Oreo ROMs and with every ROM I am getting Error 7, which is supposedly Recovery error but every time I have used the recovery recommended by the ROM administrator. So its definitely not a recovery issue in my case.
I was wondering, those with same device, managed to install Oreo ROM, what is your baseband version? Most likely, this is the culprit, but to be sure, I would like to know at least one person with same device and different baseband version that managed to install Oreo ROM.
This page (https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624) list a lot of stock ROMs. Mine is half way through. Hence, I would like to see someone with newer baseband running Oreo ROM.
Many thanks in advance.
Did you check the updater script to ensure the phone's model # is included?
audit13 said:
Did you check the updater script to ensure the phone's model # is included?
Click to expand...
Click to collapse
Yes. All the ROMs I tried were for I-9505 of which I-9505G is a variant. I also removed that part of the script, just in case, but the same error occurred.
fuzzychicken said:
Yes. All the ROMs I tried were for I-9505 of which I-9505G is a variant. I also removed that part of the script, just in case, but the same error occurred.
Click to expand...
Click to collapse
Maybe you need to add the gt-i9505g to the list rather than removing it.
audit13 said:
Maybe you need to add the gt-i9505g to the list rather than removing it.
Click to expand...
Click to collapse
It was already there, so the ROMs were compatible but I removed just in case, thought if it is not working with the model number in it, maybe I can try without it, as recommended on some other blog posts on the web.
I guess the only other thing would be to try different versions of TWRP.
audit13 said:
I guess the only other thing would be to try different versions of TWRP.
Click to expand...
Click to collapse
I am sorry, thats what I said in the OP. I have tried every possible version of TWRP that was recommended for those ROMs and the error keep showing up. That indicates that its not recovery that is causing the problem.
Only thing left I can think of would be to flash the latest stock ROM, factory wipe, flash twrp, then wipe, and then flash the custom ROM.
audit13 said:
Only thing left I can think of would be to flash the latest stock ROM, factory wipe, flash twrp, then wipe, and then flash the custom ROM.
Click to expand...
Click to collapse
That is what I am thinking but I am not too sure which is the latest stock ROM.
https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 On this page, there are loads of stocks. Mine is half way through. Its I9505GUEUDNL3_FULL. Assuming that the list goes down as newer stocks, esp looking at the last 3 alpha-numerics, should I be flashing I9505GUEUDPF1_FULL?
If I flash, I9505GUEUDPF1_FULL will it write new bootloader and baseband? If yes, do I have to go through whole unlock bootloader thing? or just flash twrp via Odin and go ahead with newer ROM? This is the most sticky part as I don't remember how I did it in the past. I just don't touch something I am not very clear understanding on, but this time I would like to update to Oreo, primarily for security purpose and the cash is tight so if I brick this, I wouldn't be very happy to buy another device. Hence trying to dot all i's and cross all t's.
Thanks for all help in advance.
Flashing a stock ROM with Odin will update the bootloader and modem.
The bootloader is not locked and has never been locked on the gt-i9505.
audit13 said:
Flashing a stock ROM with Odin will update the bootloader and modem.
The bootloader is not locked and has never been locked on the gt-i9505.
Click to expand...
Click to collapse
Thank you.
Let me put it in steps, pls correct me if I am wrong.
1. Flash I9505GUEUDPF1_FULL using Odin. Once rebooted, confirm if newer baseband is present. Check if the calls and data works.
2. Flash TWRP recovery using Odin (it will revert to stock recovery, right?) If not, alls good as it is.
3. Install ROM of choice.
There is no data on the phone, I reflashed SlimROM after all attempts of Oreo failed.
Anything tricky stuff in between?
Thanks in advance.
To prevent the stock recovery from overwriting twrp, uncheck everything in Odin except for reset time, flash twrp, when you see the word "reset" in the status window, remove the usb cable from phone, remove the battery, replace the battery, boot into twrp.
audit13 said:
To prevent the stock recovery from overwriting twrp, uncheck everything in Odin except for reset time, flash twrp, when you see the word "reset" in the status window, remove the usb cable from phone, remove the battery, replace the battery, boot into twrp.
Click to expand...
Click to collapse
I am very sorry to be a PITA, mate, but I really need help here.
As per the suggestions, I tried flashing various images. In every image I flashed, the calling and wifi worked but cell data didn't work in any of those versions. Still I tried flashing Oreo with them but the error persisted. So probably, its something beyond I can do it with my little knowledge.
So finally, to give up I tried going to back to where I was before all this, to baseband version, I9505GUEUDNL3. I flashed NL3 image linked in the post https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 through Odin. While the OS shown in about phone is 5.0, the baseband version is stuck at OJ1, where the data does not work.
Any idea how I can go back to NL3 where data worked flawlessly?
Many thanks in advance.
Edit: I flashed NL3 modem from https://forum.xda-developers.com/showthread.php?t=2452034 but still the issue persists. I have nandroid backups from the very first time when I flashed another ROM. If I use that to restore, will it restore all the issues?
The bootloader and modem should be flashed in tandem to maintain compatibility with each other. Data may not be working due to a mismatch.
Flash the latest stock ROM from sammobile.com, updato.com, or samsung-firmware.org.
audit13 said:
The bootloader and modem should be flashed in tandem to maintain compatibility with each other. Data may not be working due to a mismatch.
Flash the latest stock ROM from sammobile.com, updato.com, or samsung-firmware.org.
Click to expand...
Click to collapse
Thank you.
Can you pls take a look at this thread? https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 Supposedly, these are factory images. I tried these images and my best guess is, they have right bootloader and modem. None of the sites you suggested carry stock images for GT-I9505G (Play Edition). They have GT-I9505 though.
What I tried so far.
- Flashed images linked above. Didn't work
(at one point, I even got OTA, when I was on OE1 baseband, it updated to OJ1. So in theory, in this OTA, it should fix this mismatch bootloader and modem, right?) When things didn't change after this update. I tried to flash NL3 image.
- Flashed NL3 image which I had. The baseband remained at OJ1. This was odd to me. So flashed NL3 modem. The issue persisted.
- I had taken nandroid backup before I started flashing custom ROMs. I tried to restore that back up through a custom recovery, TWRP. No help.
Screenshot of that backup, if it tells you anything
{
"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"
}
- I have EFS Backups, but I don't quite remember how I took that backup.
Screenshot attached. Any idea if this can be used to restore everything in one shot. I don't know if EFS contains bootloader as well.
You mentioned I should flash stock ROM. Assuming that ROM images linked on the XDA thread above are untouched, shouldn't that fix the issue? If not, is there any possibility one can find bootloader images (if such thing exists) because modem images are available in another thread. One can pick and choose a combination to flash. I am just speculating. I have no idea if such a thing can be done.
Thank you so much. Really appreciate you sticking around to share the ideas.
P.S. - Is there any option where you can delete both bootloader and modem just before flashing the stock ROM via Odin or TWRP?
There is no need to deal with the EFS at this moment as long as the phone is showing the correct IMEI and MAC address.
Yes, those look like factory images and you should try the latest ROM which is PF1. It's possible that the phone was running a newer bootloader than the one found in the NL3 ROM. Some boot loaders cannot be downgraded.
You cannot delete the bootloader from the phone. Without a bootloader, the phone would function. It's similar to the BIOS of a PC.
It is not TWRP that's the problem - it's the size of your system / user partitions on the 9505g.
@side said he would have a fix in version 4 OptLos for this.
His solution is not something I will be implementing in Resurrection Remix however.
audit13 said:
There is no need to deal with the EFS at this moment as long as the phone is showing the correct IMEI and MAC address.
Yes, those look like factory images and you should try the latest ROM which is PF1. It's possible that the phone was running a newer bootloader than the one found in the NL3 ROM. Some boot loaders cannot be downgraded.
You cannot delete the bootloader from the phone. Without a bootloader, the phone would function. It's similar to the BIOS of a PC.
Click to expand...
Click to collapse
So I flashed PF1 stock ROM, both bootloaders and modems are PF1. Made sure over the full day yesterday, there is no update and the problem persists. Can't flash Oreo and no cell phone data. Now, my interest in Oreo has pretty much died and only hoping to find a tweak to fix cell phone data. Fixed APN, made a factory reset just to be sure that its not the issue, tried SIM card in the different phone and other SIM in my phone that its not the SIM or the network thats the cause. So far I have not managed to find out what made the phone lose cell phone data.
Buff99 said:
It is not TWRP that's the problem - it's the size of your system / user partitions on the 9505g.
@side said he would have a fix in version 4 OptLos for this.
His solution is not something I will be implementing in Resurrection Remix however.
Click to expand...
Click to collapse
Dang man, your comment came a little late after I managed to fcuk up my phone very well trying to install Oreo. It will be great if you folks can make this comment in OP of the respective ROMs so that next I9505G user won't mess it up royally the way I did. If I remember correctly, I read both the threads start to the end and I didn't find any comment on this issue of I9505G.
Thanks both of you for chiming in and trying to help. If there is any idea to fix the loss of cell phone data, that will be of great help.