Related
My phone downloaded an OTA and keeps bugging me to install it, which I actually want to do. Trouble is, when it reboots it goes into the recovery menu where I installed my root from. It asks where I want to install the update from. Can I point this to where the OTA was downloaded? If so, where is that? Otherwise, how can I get this update installed so it will stop bugging me?
I rooted but kept everything stock so I thought I can use the OTA updates....
sponge14 said:
My phone downloaded an OTA and keeps bugging me to install it, which I actually want to do. Trouble is, when it reboots it goes into the recovery menu where I installed my root from. It asks where I want to install the update from. Can I point this to where the OTA was downloaded? If so, where is that? Otherwise, how can I get this update installed so it will stop bugging me?
I rooted but kept everything stock so I thought I can use the OTA updates....
Click to expand...
Click to collapse
The short answer is yes you can accept OTA Updates while rooted, I know this because I have accepted 3 different OTA's on my GS3 while being rooted. However you can never accept an OTA when you have a custom recovery. Anytime you want to accept an OTA you need to hop on over to Odin, and flash the stock recovery, otherwise the OTA will fail.
Head on over here http://www.epiccm.org/2012/06/sprint-sgs3-stock-restore.html
and read up on how to restore your stock recovery, this will allow you to accept the OTA, and then just reroot.
US Cellular
I'm on US Cellular and rooted. I installed TWRP and the phone won't install the update from it, if it helps anyone, this is what TWRP is showing.
Installing update...
assert failed: getprop("ro.product.device") == "d2usc" ||
getprop("ro.build.product") == "d2usc"
E:Error in /cache/fota/update.zip
(Status 7)
Installation aborted.
Install with custom recovery and before u reboot just flash the team root zip file that work for sprint galaxy s 3 hope this helps
Sent from my SPH-L710 using xda premium
luisortega17 said:
I'm on US Cellular and rooted. I installed TWRP and the phone won't install the update from it, if it helps anyone, this is what TWRP is showing.
Installing update...
assert failed: getprop("ro.product.device") == "d2usc" ||
getprop("ro.build.product") == "d2usc"
E:Error in /cache/fota/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Again as mentioned in my post above yours, if you are trying to install an OTA update, you cannot do so with a custom recovery, you must be on a stock recovery to install an OTA update. Custom recoveries are only for custom flashes. So as a rule, Custom installs Custom, Stock installs Stock.
Apparently I can not do this because I have to use my company's email on my phone. When I added the account it for some unknown reason had to encrypt the phone's internal memory, so when I try to use the bootloader to run that program, it can not see the phone's internal storage.....
So my question now is, is there a file I can delete or something I can do to make the message stop popping up that there is an update ready to install?
sponge14 said:
Apparently I can not do this because I have to use my company's email on my phone. When I added the account it for some unknown reason had to encrypt the phone's internal memory, so when I try to use the bootloader to run that program, it can not see the phone's internal storage.....
So my question now is, is there a file I can delete or something I can do to make the message stop popping up that there is an update ready to install?
Click to expand...
Click to collapse
Make a backup and take a look here http://forum.xda-developers.com/showthread.php?t=1829706
ETA: Don't you have a password set to decrypt it? My company email doesn't do that so confused as to how that worked.
Foreverme89 said:
Make a backup and take a look here http://forum.xda-developers.com/showthread.php?t=1829706
ETA: Don't you have a password set to decrypt it? My company email doesn't do that so confused as to how that worked.
Click to expand...
Click to collapse
It does ask for the password, however, the password is not asked for until after the bootloader would appear.
sponge14 said:
It does ask for the password, however, the password is not asked for until after the bootloader would appear.
Click to expand...
Click to collapse
Also, I'm not seeing a System folder when I hook the USB up to the PC and try to browse it there...
sponge14 said:
Also, I'm not seeing a System folder when I hook the USB up to the PC and try to browse it there...
Click to expand...
Click to collapse
I can't see the system folder on the computer. Either in astro or ES file emplorer, if you go to the root of the phone it should show.
{
"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"
}
Sent from my SPH-L710 using xda premium
Last attempt before I report the phone stolen and get a new handset.
In need of help and getting frustrated by the forum software:
I get this:
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
When trying to add this reply:
I used the root method as published on Jul 2, 2012 by qbking77 on youtube (How to Root the Sprint / AT&T / T-Mobile Samsung Galaxy S III)
Am I using a stock recovery?
To this post:
http://forum.xda-developers.com/newreply.php?do=newreply&p=30346020
Despite the fact that I am NOT posting any links, outside or not (whatever outside may mean.)
EDIT:
It worked! I posted!
Apparently the problem with posting stems from quoting other users, even if I have no links.
That's really messed up when one needs to quote to reply and you happen to be new. Your forum software is not kind to new users who lack the patience to try to post upwards of 10x (like myself.)
EDIT CONTINUED:
Now I can't save my edit
"To prevent spam to the forums, new users must wait five minutes between posts. All new user accounts will be verified by moderators before this restriction is removed."
I have a question i currently have my sprint galaxy s3 flashed to Metro pcs which is also rooted, and the ota keeps popping up. I would like to install the ota but it keeps failing. Can i flash back to the stock like mentioned in the previous post and not lose my metro pcs flash because i would hate to pay for the flash again. Thanks
I am not entirely sure what all goes into flashing to another carrier although I do believe the flash to metro would stay intact. Having said that, rather than downgrading it and trying to accept an ota I would first do a nandroid backup and flash the latest build using odin or custom recovery
NOTE: If anyone has any further questions about bootloaders on the S3, please note that I have moved on to another device. Sorry!
Hi everybody,
As you may or may not know, the latest builds of CyanogenMod 10.1 (and many other ROMs which use CM as a base) refuse to install without an updated bootloader on your device. Even if you bypass this requirement, the ROM won't boot. I haven't seen any clear-cut instructions on updating the bootloader except for a single post buried in the CM10.1 nightly thread, posted by Jiangyi, but that update also changes your modem, so I thought I'd throw together a thread dedicated to bootloaders only.
Step 1 - Identify your model
This subforum supports 2 different models; The I747 and the I747M. You can find your device's model in a few different ways:
While Android is running
In Settings, under About Phone, the Baseband version shows the currently installed modem firmware version. If your phone currently works on mobile networks, then you've probably got the right modem firmware for your model, and the Baseband version will start with either "I747" or "I747M". This is your model.
{
"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"
}
While the phone is off
Underneath your battery is a sticker showing your IMEI and other information, including the model number.
Step 2 - Download the correct update
You can install this updated bootloader in a couple different ways; Most people should be comfortable flashing ZIPs in their recovery (CWM or TWRP both work fine) while others may want to install the update via Odin. Choose your model and preferred method, and download the matching file from below.
I747U (AT&T)
I747UCALG1 - Jul 1, 2012 - boot_CWM_I747UCALG1.zip - 1.13 MB
I747UCDLK3 - Nov 3, 2012 - boot_CWM_I747UCDLK3.zip - 1.13 MB
I747UCDMG2 - Jul 2, 2013 - boot_CWM_I747UCDMG2.zip - 1.13 MB
I747UCUEMJB - Oct 11, 2013 - boot_CWM_I747UCUEMJB.zip - 1.14 MB WARNING: Do not attempt to downgrade from this bootloader. Doing so will brick your device. Use extra caution when flashing anything via Odin, as many Odin packages will attempt to flash the bootloader.
I747M (Canada and overseas) (Updating this list shortly...)
I747MVLUEMK5 - Nov 5, 2013 - boot_CWM_I747MVLUEMK5.zip - 1.14 MB WARNING: Do not attempt to downgrade from this bootloader. Doing so will brick your device. Use extra caution when flashing anything via Odin, as many Odin packages will attempt to flash the bootloader.
Check my Dropbox if d-h.st is giving you issues.
Step 3 - Flash the update
Depending on which type of update package you downloaded, follow one of the following steps:
Flashing with Odin
Download Odin: [link]
Put your phone into download mode. Some ROMs have this option in the Power>Reboot menu, otherwise just hold "Volume Down" and "Home" while powering on your device.
Launch Odin, then connect the USB cable to your device.
Click the "PDA" button and select the package you downloaded in step 2.
Click "Start" in Odin and wait for the process to complete. Your device should reboot automatically when the flash is complete, and you're done.
Flashing in recovery
If you've downloaded a flashable .ZIP from above, copy it to your SD card or internal storage. Reboot your phone into recovery mode (you can do this by holding "Volume Up" and "Home" while powering on your device; let go of the buttons when you see "Recovery booting..." in blue text in the top left of the screen) and install the .ZIP as an update. Reboot, and you're done.
Note: After flashing in recovery, you need to reboot before you (and ROM installers) actually see the new version number.
Did you brick your phone attempting to downgrade your bootloader?
There really is no reason to downgrade your bootloader; If you did it to be able to flash a ROM that doesn't recognize the newest bootloader version and therefore wouldn't let you flash, you should contact the ROM developer and tell them to add the newest bootloader version to their asserts. The latest bootloaders trigger eFUSEs within the device, no longer allowing it to boot from older bootloaders. These eFUSEs cannot be reset, but @-Mr. X- has come up with an unbricking method that may help you out. Check it out here.
If you're looking to update your modem as well, check my signature for a link to the modem thread.
Look forward to seeing a recovery flashable zip that updates the bootloader. Never have I seen that before. I have always used Odin for that. Thanks and looking forward to trying it out.
Sent from My Spiderman Themed I747
So you created a thread for bootloader only updates, but there are no bootloader only updates available?
What files are available for download? Is that the full firmware or the files created by Jiangyi?
upndwn4par said:
So you created a thread for bootloader only updates, but there are no bootloader only updates available?
What files are available for download? Is that the full firmware or the files created by Jiangyi?
Click to expand...
Click to collapse
Currently I've linked to Jiangyi's files, I'm working on bootloader-only updates right now. I just wanted to get this thread up ASAP because I've had a few different people PM me asking for help. As a temporary option, you could just use the Odin update and then flash another modem on top of that.
dstruct2k said:
Currently I've linked to Jiangyi's files, I'm working on bootloader-only updates right now. I just wanted to get this thread up ASAP because I've had a few different people PM me asking for help.
Click to expand...
Click to collapse
Instead of posting links to someone else's work, you could have just directed them to Jiangyi's post in the CM10.1 thread.
upndwn4par said:
Instead of posting links to someone else's work, you could have just directed them to Jiangyi's post in the CM10.1 thread.
Click to expand...
Click to collapse
The link in my first paragraph does just that, but since this is affecting a lot more ROMs than just CM, people are going to need this information and a single post on a random page of a massive thread usually gets overlooked by 99% of people. The point of this thread is to make information easy to find and ensure that people are able to update their bootloaders and run new ROMs.
Like I said, the links to his work are temporary while I get my own files uploaded. Not exactly on the fastest of connections right now.
Added recovery-flashable bootloaders to OP.
i found this post very helpful and informative i think i would have been MORE confused having just been linked to a single post. the pictures and instructions are so awesome!
thanks man the community appreciates your work, you can ignore the rent a mods
If your phone came with DLK3 when purchased from AT&T this is not necessary correct?
SHOstock3
Jeboo 2.2
mcala said:
If your phone came with DLK3 when purchased from AT&T this is not necessary correct?
SHOstock3
Jeboo 2.2
Click to expand...
Click to collapse
Depends on whether they updated just the modem to DLK3 or the entire system. If you have issues flashing ROMs, try flashing this first.
thanks! :good:
saves me the hassle of going thru 2k+ pages
If your unsure about which bootloader you have, check >>HERE<<
So if I flash this, my flash counter will increase to 1, right? I've been avoiding the bootloader update because of this.
When I got my phone, I upgraded to 4.1.1 (which is what this bootloader update is based on, right?), then rooted, installed CWM, and flashed ROMs. But with that Triangle Away reset the counter to 0 only until a reboot, after reboot it incremented to 1. So to resolve I Odin flashed 4.0.4, rooted, installed CWM, used Triangle away, then flashed ROMs... and my counter stayed at 0 after reboot.
Just trying to hedge warranty concerns versus being a nightly flashaholic....
Correct, the 4.1.1 bootloader does have the newer flash counter. It will increase your flash counter when you reboot if your not running stock (I think it checks the type of recovery installed and something with the kernel. I think.)
robbieas said:
So if I flash this, my flash counter will increase to 1, right? I've been avoiding the bootloader update because of this.
When I got my phone, I upgraded to 4.1.1 (which is what this bootloader update is based on, right?), then rooted, installed CWM, and flashed ROMs. But with that Triangle Away reset the counter to 0 only until a reboot, after reboot it incremented to 1. So to resolve I Odin flashed 4.0.4, rooted, installed CWM, used Triangle away, then flashed ROMs... and my counter stayed at 0 after reboot.
Just trying to hedge warranty concerns versus being a nightly flashaholic....
Click to expand...
Click to collapse
Using a recovery-flashable ZIP will not increase your flash counter.
And I take it you got his permission To post his work right?
Wayne Tech Nexus
I think it's ok to post links to other people's work, and to improve on it by creating another method of flashing, is it not?
Not without their permission it's not.
Wayne Tech Nexus
dstruct2k said:
Using a recovery-flashable ZIP will not increase your flash counter.
Click to expand...
Click to collapse
This is incorrect. Simply having a custom recovery period with the 4.1.1 bootloader will always increment your counter to 1 after a reboot. Triangle Away will reset your counter to 0, but upon reboot it will be back to 1.
This was my experience when I rooted from 4.1.1. Then I Odin`d back to 4.0.4, rooted, CWM, flased ROMs and my counter stayed at 0 through multiple flashes. As soon as I flashed this bootloader patch my counter went to 1 ater reboot. Triangle Away will reset to 0, but on reboot it goes back to 1.
Not sure it really matters, not sure why I even care about the flash counter... guess just want to hedge my bets in case I need warranty and can't Odin to stock before returning.
dstruct2k said:
Added recovery-flashable bootloaders to OP.
Click to expand...
Click to collapse
What does "OP"means?
Hey guys,
I have a few questions regarding the Marshmallow update to the One (M8). First of all, I own an international M8 on stock, rooted, with TWRP KitKat firmware version 3.32.707.9. I have not updated either my Sense Home (still have Sense 6 mainly), and most of my apps are the Sense 6 versions, which I prefer to the colourful Sense 7 versions. So, my questions:
I still haven't received the Marshmallow update at all. Do I need to update to Lollipop or will I receive a Marshmallow notification even while on KitKat?
If the above is not possible, then can I install the OTA onto my phone after downloading the zip file from a mirror directly?
Can I backup all the Sense 6 apps that I want, like HTC Clock, HTC Blinkfeed and such with Titanium Backup, update to Marshmallow and restore them, and expect them all to work properly?
Thanks.
1. You need to have lollipop 4.19.707.4 stock ROM to receive Marshmallow update. Won't get it on KitKat, lollipop lower than 4.19.707.4 won't get it too.
2. No
3. Yes & No ... but mostly No unless it's a full KitKat ROM running on Marshmallow firmware.
ckpv5 said:
1. You need to have lollipop 4.19.707.4 stock ROM to receive Marshmallow update. Won't get it on KitKat, lollipop lower than 4.19.707.4 won't get it too.
2. No
3. Yes & No ... but mostly No unless it's a full KitKat ROM running on Marshmallow firmware.
Click to expand...
Click to collapse
That's a bummer... Ah, it was time I cleaned out my phone and clean-installed all my apps and stuff anyway. Thanks for the help. I was hoping I could get the nice globe HTC Clock from Sense 6 in Marshmallow, it was quite useful...
Some updates - I realised that I deleted some system apps without making backups, and now I can't update to Lollipop (and thence to Marshmallow). Big mistake, yes. How do I find which apps were deleted, and how do I restore them? Or is it more prudent to simply make a Titanium Backup of my data, flash a TWRP backup of the new Marshmallow ROM and just restore my data?
SRSR333 said:
Some updates - I realised that I deleted some system apps without making backups, and now I can't update to Lollipop (and thence to Marshmallow). Big mistake, yes. How do I find which apps were deleted, and how do I restore them? Or is it more prudent to simply make a Titanium Backup of my data, flash a TWRP backup of the new Marshmallow ROM and just restore my data?
Click to expand...
Click to collapse
If you want the official OTA, none of that will work. OTA requires stock never rooted ROM.
You can restore a stock nandroid 3.32.707 from ckpv5's collection (link in his signature), and corresponding stock recovery, then do OTAs, all the way up to Marshmallow (if or when its released for your version).
Alright, I successfully flashed an un-rooted TWRP nandroid backup of 3.32.707.9, updated to Lollipop and thence to Marshmallow. I performed a factory reset and then restored all my apps and settings, and proceeded to flash TWRP and the SuperSU binary.
Lo and behold, my phone is now stuck in a boot loop. It gets to the 'One' screen, and then just locks up. I have to press Power + Volume Up to reboot it and switch it off. Any fixes? Also note that my USB port is, for some reason, also dysfunctional now. I can only connect to my PC in 'Fastboot AC' mode, and I've tried three cables already, two different PCs and all the USB ports in both PCs.
Edit: I restored my Kit Kat nandroid backup that I made. My phone has been saved, but now I have to do this gruelling update process all over again. Isn't there a faster way?
SRSR333 said:
Edit: I restored my Kit Kat nandroid backup that I made. My phone has been saved, but now I have to do this gruelling update process all over again. Isn't there a faster way?
Click to expand...
Click to collapse
If you try to do the steps in your first paragraph (Post #6), I'm pretty sure it won't work. Even though the ROM is back to KitKat, all the other firmware (hboot, radio, etc.) is still on MM, so the OTA won't allow you to update back to MM again.
Did you make a TWRP backup before you tried to flash SuperSU (you should always make a backup before applying mods; especially a backup of the unrooted, stock ROM)? If so, restore it. Otherwise, you may need to find a nandroid of the MM "707" stock ROM, or ask someone to upload it.
What version SuperSU did you flash? Versions before 2.51 or so don't work for MM, and will cause the no-boot condition. Also, TWRP should be latest version 2.8.7.0.
redpoint73 said:
What version SuperSU did you flash? Versions before 2.51 or so don't work for MM
Click to expand...
Click to collapse
This is where I messed up. I flashed 2.46.
I'll see if the OTA works, or else I'll just RUU Kit Kat, and then OTA.
SRSR333 said:
This is where I messed up. I flashed 2.46.
Click to expand...
Click to collapse
I suspected as much. In the future, keep in mind that new builds usually require a new SuperSU version.
SRSR333 said:
or else I'll just RUU Kit Kat, and then OTA.
Click to expand...
Click to collapse
That should work. I assume there is RUU for 707 version (can never keep straight which versions do/no not have RUU)? If there is a LP RUU for your version, it would be easier to run that (skip the step of the OTA).
redpoint73 said:
That should work. I assume there is RUU for 707 version (can never keep straight which versions do/no not have RUU)? If there is a LP RUU for your version, it would be easier to run that (skip the step of the OTA).
Click to expand...
Click to collapse
Now, my phone's USB port has stopped working. I can only charge it through my PC, and not get any sort of MTP connection. Something's wrong.
Slide down the notification then in the drop down select file transfers (for MTP) instead of charging
I don't get any notification. It's as if the phone doesn't even realise it's plugged into a PC, and just charges.
SRSR333 said:
I don't get any notification. It's as if the phone doesn't even realise it's plugged into a PC, and just charges.
Click to expand...
Click to collapse
You don't have these ?
{
"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"
}
What ROM that you have now on your device ? You already updated to MM, right ?
If it is your old KitKat ...
Install TWRP 2.8.7.0
Boot to TWRP recovery then enable MTP to transfer files from PC to device
Restore a non-rooted MM
SRSR333 said:
Now, my phone's USB port has stopped working. I can only charge it through my PC, and not get any sort of MTP connection. Something's wrong.
Click to expand...
Click to collapse
What do you mean "Now"? Which did you end up doing? Stock kitkat nandroid? KK RUU? LP RUU?
Try to go to Windows Device Manager, find the device, and manually pick the generic Android MTP drivers. See if that makes MTP or fastboot/adb work properly.
redpoint73 said:
What do you mean "Now"? Which did you end up doing? Stock kitkat nandroid? KK RUU? LP RUU?
Click to expand...
Click to collapse
I haven't done anything yet. I tried to connect my phone previously to try and enter fastboot USB mode before all this, and I noticed that my phone was only connecting as fastboot AC. I could not, and still cannot get any computer to recognise my device. I've tried a few other cables, too.
Edit: I have fixed this issue. It was a case of loose USB contact between my device and the cable. Tweaking some of the gold contacts on the cable helped, and my PC now shows my One M8 connected. Fastboot is connected as Fastboot USB, too. I'm going to perform a Titanium Backup, and then restore the Lollipop RUU and proceed with updating to Marshmallow. Hope it works out fine this time.
Thanks for the help, everyone.
New updates - I found an RUU for 4.19.707.2, and attempted to apply it, only to receive an error 159, stating that the RUU image size was different compared to the device image size. What's wrong?
SRSR333 said:
New updates - I found an RUU for 4.19.707.2, and attempted to apply it, only to receive an error 159, stating that the RUU image size was different compared to the device image size. What's wrong?
Click to expand...
Click to collapse
You can't use lower version RUU 4.19.707.2 when your current firmware is 6.14.707.1
SRSR333 said:
Edit: I restored my Kit Kat nandroid backup that I made. My phone has been saved, but now I have to do this gruelling update process all over again. Isn't there a faster way?
Click to expand...
Click to collapse
Save all the hassle to restore a KitKat or Lollipop RUU/backups ... just restore non-rooted backup 6.14.707.1 - check my thread linked in my signature, you should find it on post #3
ckpv5 said:
You can't use lower version RUU 4.19.707.2 when your current firmware is 6.14.707.1
Click to expand...
Click to collapse
Of course, but I saw in several places that if the M8 is S-OFF then this rule doesn't apply...
SRSR333 said:
Of course, but I saw in several places that if the M8 is S-OFF then this rule doesn't apply...
Click to expand...
Click to collapse
So .. your device is S-Off ?
What you read is correct for lollipop and below.
When it comes to RUU exe when you have Marshmallow firmware on your device or running a Marshmallow RUU exe, it works differently ..
That's the reason why I wrote "You can't use lower version RUU 4.19.707.2 when your current firmware is 6.14.707.1" as I know you tried RUU exe
Good luck...
Please help me my mobile not open after update
SRSR333 said:
Hey guys,
I have a few questions regarding the Marshmallow update to the One (M8). First of all, I own an international M8 on stock, rooted, with TWRP KitKat firmware version 3.32.707.9. I have not updated either my Sense Home (still have Sense 6 mainly), and most of my apps are the Sense 6 versions, which I prefer to the colourful Sense 7 versions. So, my questions:
I still haven't received the Marshmallow update at all. Do I need to update to Lollipop or will I receive a Marshmallow notification even while on KitKat?
If the above is not possible, then can I install the OTA onto my phone after downloading the zip file from a mirror directly?
Can I backup all the Sense 6 apps that I want, like HTC Clock, HTC Blinkfeed and such with Titanium Backup, update to Marshmallow and restore them, and expect them all to work properly?
Thanks.
Click to expand...
Click to collapse
Please help me
After update and mobile reboot and install update when it comelete it go to recovery and not open like the photo in attachment
Just got myself a TMO M919 on the cheap today. M919 only got Kitkat while M919V (Canadian) got Lollipop. Figured I could be adventurous and try a M919V firmware on it... And voila, it actually boots!
Not without some modifications to the original firmware though, or Odin will fail at checking authenticity of bootloader or modem (model doesn't match). I used a TAR repackaging tool to remove all the bootloader and modem parts from the firmware, and flashed the repackaged TAR via Odin.
So basically it's a Lollipop TW firmware booting on top of the Kitkat bootloader. Call, SMS, LTE, camera, everything I tested in the brief time I used it works fine. Makes sense, the V variant is even more similar to M919 than i9505.
I know it's kinda late, since most people here should already be on an AOSP-based custom firmware by now (I'll also flash LOS soon), but nevertheless I think it could be a refresher for people who have it on stock for using at home, etc.
I'll upload the repackaged stuff if there are still people actually interested in it.
Screenshot as proof below (note that the baseband is from M919):
{
"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"
}
Hi there, I'm interested in your repackaged M919V Firmware. Can you upload it? Thanks ill be waiting. Cheers
MysticBlueDragon said:
Hi there, I'm interested in your repackaged M919V Firmware. Can you upload it? Thanks ill be waiting. Cheers
Click to expand...
Click to collapse
https://androidfilehost.com/?a=show&w=files&flid=239650
I've also tried repackaging the latest i9505G (S4 GPe) firmware and flashing and the experience is also good, though I haven't extensively tested either. They are both in the folder.
it's the wifi calling that's the main problem running a lollipop ROM on SGH-M919
found a solution wifi
kalan1988 said:
found a solution wifi
Click to expand...
Click to collapse
Just install this kernel
https://androidfilehost.com/?w=file...2674a1a5ca61e20aa2c0b1cf1f6c99f1a46298b244ca6
heres is the xda link:
https://forum.xda-developers.com/galaxy-s4-tmobile/general/i9505oa7tw5-0leak-t3045729
AndyYan said:
Just got myself a TMO M919 on the cheap today. M919 only got Kitkat while M919V (Canadian) got Lollipop. Figured I could be adventurous and try a M919V firmware on it... And voila, it actually boots!
Not without some modifications to the original firmware though, or Odin will fail at checking authenticity of bootloader or modem (model doesn't match). I used a TAR repackaging tool to remove all the bootloader and modem parts from the firmware, and flashed the repackaged TAR via Odin.
So basically it's a Lollipop TW firmware booting on top of the Kitkat bootloader. Call, SMS, LTE, camera, everything I tested in the brief time I used it works fine. Makes sense, the V variant is even more similar to M919 than i9505.
I know it's kinda late, since most people here should already be on an AOSP-based custom firmware by now (I'll also flash LOS soon), but nevertheless I think it could be a refresher for people who have it on stock for using at home, etc.
I'll upload the repackaged stuff if there are still people actually interested in it.
Screenshot as proof below (note that the baseband is from M919):
Click to expand...
Click to collapse
Can you flash this thru recovery mode?
I found that the LP kernel needed to get WiFi breaks Widevine L1 (gets set to L3), which would partially defeat the purpose of using a Touchwiz stock rom anyway. I am trying a few other kernels and will see if one works. GPE edition 5.1 flashes fine including WiFi but Widevine L1 does not actually work despite showing up in DRMINFO.
AndyYan said:
Just got myself a TMO M919 on the cheap today. M919 only got Kitkat while M919V (Canadian) got Lollipop. Figured I could be adventurous and try a M919V firmware on it... And voila, it actually boots!
Not without some modifications to the original firmware though, or Odin will fail at checking authenticity of bootloader or modem (model doesn't match). I used a TAR repackaging tool to remove all the bootloader and modem parts from the firmware, and flashed the repackaged TAR via Odin.
So basically it's a Lollipop TW firmware booting on top of the Kitkat bootloader. Call, SMS, LTE, camera, everything I tested in the brief time I used it works fine. Makes sense, the V variant is even more similar to M919 than i9505.
I know it's kinda late, since most people here should already be on an AOSP-based custom firmware by now (I'll also flash LOS soon), but nevertheless I think it could be a refresher for people who have it on stock for using at home, etc.
I'll upload the repackaged stuff if there are still people actually interested in it.
Screenshot as proof below (note that the baseband is from M919):
Click to expand...
Click to collapse
Does this mean you're going to Dev for the s4? We would love to have you!
I installed your repackaged tar successfully and also flashed the kernel you suggested. Wifi worked after flashing the kernel but if I reset the phone, the saved wifi info is lost so I have to re-enter wifi info all over again. Any advice on this? Should I be looking for a different kernel or any advice you guys can give? Greatly appreciated.
AndyYan said:
https://androidfilehost.com/?a=show&w=files&flid=239650
I've also tried repackaging the latest i9505G (S4 GPe) firmware and flashing and the experience is also good, though I haven't extensively tested either. They are both in the folder.
Click to expand...
Click to collapse
Hey man, can't thank you enough for this. In the process of updating the device (GT-I9505G), I managed to screw up somewhere and now the cell phone data does not work. This is the screenshot of my firmware(s). Everything else, like calling, wifi etc works. Before I realized I tried to update install ROM, as it has happened in the past, but still things are the way they are, no cell phone data. APN is correct. I made that sure.
The screenshots of the firmware are below. CSC and PDA version are missing.
Screenshots taken using https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en_US
I was wondering if I flash your I9505GUEUDPF1_Boot+Rec+Sys.tar.md5 to this device, will it address the issue and put back PDA and CSC version?
If yes, how do I flash it in Odin, as what do I choose or extract the file and flash everything separately?
Thanks a million again. You saved my rear end a big time.
Edit: I have realized you can not flash the file as is. So I have extracted the image in *.ext4 format. I need guidance which folders to extract and how to proceed thereon. Thank you very much.
fuzzychicken said:
I was wondering if I flash your I9505GUEUDPF1_Boot+Rec+Sys.tar.md5 to this device, will it address the issue and put back PDA and CSC version?
Click to expand...
Click to collapse
I don't get it - what's stopping you from flashing the *full* firmware available around the web? That's the surefire way to fully recover.
AndyYan said:
I don't get it - what's stopping you from flashing the *full* firmware available around the web? That's the surefire way to fully recover.
Click to expand...
Click to collapse
There is another thread where all ROMs are listed. I have tried flashing those stock ROMs but I have not been successful.
So I went back to 5.0.1 stock ROM and let the phone update by itself, still I have not been successful. I am super confused why repeated updates could not fix this problem.
I have EFS backups from 5.0.1 stock (before I started flashing business). Do you think I can use that? I am not too sure of CSC and PDA are in the efs partition, hence the question.
Thanks again.
fuzzychicken said:
There is another thread where all ROMs are listed. I have tried flashing those stock ROMs but I have not been successful.
So I went back to 5.0.1 stock ROM and let the phone update by itself, still I have not been successful. I am super confused why repeated updates could not fix this problem.
I have EFS backups from 5.0.1 stock (before I started flashing business). Do you think I can use that? I am not too sure of CSC and PDA are in the efs partition, hence the question.
Thanks again.
Click to expand...
Click to collapse
For what I know you *have* to use the full firmware for those partitions...
AndyYan said:
For what I know you *have* to use the full firmware for those partitions...
Click to expand...
Click to collapse
Yes, I totally understand that. Since I9505G firmware is hard to come by and att Galaxy S4 is similar in hardware as that of S4 Play Edition, Is it worth giving a shot to that. I am on att MVNO so, in theory, it should work.
---------- Post added at 11:49 AM ---------- Previous post was at 11:20 AM ----------
AndyYan said:
For what I know you *have* to use the full firmware for those partitions...
Click to expand...
Click to collapse
I found these files. Do they constitute *full* firmware with approx correct file sizes?
These are not the newest files so I will not be able to update the bootloader but assuming that I update after flashing these, it *should*fix it.
Thanks again for help.
fuzzychicken said:
I found these files. Do they constitute *full* firmware with approx correct file sizes?
These are not the newest files so I will not be able to update the bootloader but assuming that I update after flashing these, it *should*fix it.
Thanks again for help.
Click to expand...
Click to collapse
Looks "full" to me, though you don't need that PIT file unless the device is actually bricked.
AndyYan said:
Looks "full" to me, though you don't need that PIT file unless the device is actually bricked.
Click to expand...
Click to collapse
Thanks mate.
My Bootloader and baseband is 2 versions updated to this one. So I don't want to flash those. In that case, there is a mismatch. What troubles should I expect?
At the moment, the phone is working just fine except the cellular data. Worth the risk of going ahead?
ninjamuffinBV said:
Just install this kernel
https://androidfilehost.com/?w=file...2674a1a5ca61e20aa2c0b1cf1f6c99f1a46298b244ca6
heres is the xda link:
https://forum.xda-developers.com/galaxy-s4-tmobile/general/i9505oa7tw5-0leak-t3045729
Click to expand...
Click to collapse
how would I install this kernel?
I just started having problems with wifi in the stock SGH-M919 and custom roms. (Not sure what I did, radio problem, I think) This rom installed fine and the kernel fixed the wifi. Its connected and downloading updates now. The only thing I see so far (I just installed it), is that the camera crashes. I flashed twrp right off the bat. I will reinstall it all to check when I get a chance. Thanks
Update:
Odin 3.12,
flash the full (sammobile) M919UVUFOK3, wipe data, and the wifi doesnt work but camera does
flash the M919VWXUGOL1_Boot+Rec+Sys.tar.md5, wipe data, and wifi doesnt work but camera does
flash twrp-3.2.3-0-jfltexx.img.tar, still no wifi
TWRP,
install Lolli-Test-TW-07.02.2015.zip, and now wifi works but camera crashes
M919UVUFOK3 and Lolli-Test-TW-07.02.2015.zip dont work (just thought i would check)
I dont have an active sim card for this phone so I cant really test it completely. That kernel does fix wifi though.
Im not sure what is going on. I just did Odin the stock firmware (samsung-firmware) three times as well. I can get wifi to turn on like normal now but it will not connect to 2.4Ghz wifi. It seems like its in a loop. It works fine with 5Ghz though. I tried 3 different custom ROMs too. I have 3 other Samsung phones (and 3 printers) that work fine on my 2.4Ghz. I see that both stock firmwares flash modem, aboot, boot, recovery, system, sbl1, sbl2, sbl3, cache, hidden, rpm, tz and hlos. I dont know what Im missing here.
It works fine with 5Ghz so it has to be something in my software, right? I am really bummed that i didnt dd this phone before I started messing with this one. I wont ever skip that step again, lol.
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.