I received the update US Firmware XT1644 Moto G4 Plus MPJ24.139-64 ATHENE today and I am sure it is old news. I want to create a mirror for the update but I have not unlocked my device as of yet, so did not retrieve the update. If someone could send me the update so I can post it and any discussion on issues.
{
"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"
}
Where is this update located? I have it downloaded but cant find the zip
edit: The update I have is MPJ24.139-64
It could be a tar or zip. Unsure how motorola does there ota. Please if you have it, send me a link so I may upload it for everyone that has a US device. Thanks
The update can be found in the /cache folder after download. If you have something like Root Explorer, you can copy + paste the file to your internal or external storage from there.
It's located here:
Code:
/data/data/com.motorola.ccc.ota/app_download
That must be original cause my device Xt1644(US) is on build # MPJ24.139-49.
Original FW was MPJ24.139-48. The MPJ24.139-49 was a FW posted here only, supposedly shared by Moto with someone here - I have installed it too.
So the MPJ24.139-64 would be a newer one...
mikerowes69 said:
View attachment 3896100
Click to expand...
Click to collapse
Thread title has the wrong number.
Im having issuses with mine. the baseband reads (M8952_70009.08.03.45a ATHENE_RETUSA_CUST Ive been trying to find the right firmware but none are working. My IMEI is 0 so I cant get mobile signal
Your baseband is wrong, for XT1644 it should read M8952_70009.08.03.45R ATHENE_RETUSA_CUST. Don't know how you update the firmware, but you are doing it wrong - if you used the file XT1625-XT1644_ATHENE_RETUS_MPJ24.139-64_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Stop using random firmwares, it just messes up the phone more. Use only the ones that are for your phone.
Why does mine say 45a and not 45R?
Sent from my Moto G4 Plus using Tapatalk
Anyone got idea which filesystems are need to do a restore?
DDR
aboot
abootbak
boot
cache
cid
clogo
cmnlib
config
customize
devcfg
dip
dsp
frp
fsc
fsg
hw
hyp
hypbak
keymaster
kpan
limits
logo
logs
metadata
misc
modem
modemst1
modemst2
mota
oem
padC
persist
recovery
rpm
rpmbak
sbl1
sbl1bak
sec
sp
ssd
syscfg
system
tz
tzbak
userdata
utags
utagsBackup
ThaHaloMilitia said:
Why does mine say 45a and not 45R?
Click to expand...
Click to collapse
A is for amazon r is for retail from Motorola
I want to thank you for sharing the firmware with us
Related
Hello, I need help.
when I flash a custom kernel on my LT15a, said that the bootloader has encountered a bad block.
Now I can not flash any kenrel who is not the official.
how to fix this?
has a solution?
Thank you.
{
"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"
}
Try using the command 'fastboot erase boot', then boot a kernel again.
sinkster©
still with the bad block
but thanks for the help!
Try flashing the entire firmware!
Sent from my LT15i using XDA
As above. Use flashtool to flash a stock firmware, then try fastboot again.
I read something about, and said that this problem is hardware.
will be truth?
or should I try what you guys said before?
Thank you.
EDIT : - well, I did everything I said and did not work, continue with the bad block and not boot if you have a custom kernel. anyway, thanks.
i think the "bad block" means a bad sector.
no matter how many times you flash a kernel/firmware, a bad sector is still a corrupted sector the the storage media because it is a permanent damage.
heihei_ivan said:
i think the "bad block" means a bad sector.
no matter how many times you flash a kernel/firmware, a bad sector is still a corrupted sector the the storage media because it is a permanent damage.
Click to expand...
Click to collapse
In the case of bad sectors in flash drives, hard drives, etc... we are able to re-format the disk and avoid the bad sector from file system (with the drawback of decreased drive size). Is it possible with nand flash (used in smart phones)?
NEWS ?
Well I suppose to format the entire boot sector!
Does Relocking the boot loader and unlocking again does help?
no, already did that too.
anyway, thanks
is there any way to flash a custom kernel without being fastboot?
I discovered that badblock prevents only the fastboot flash
No you cant without fastboot!
u can use flashtool
gire.prasad said:
No you cant without fastboot!
Click to expand...
Click to collapse
flashtool>fastboot toolbox>select kernel to flash
I have same problem with my wt 19i...so did you fix your problem? that is a hardware malfunction?
I Have The same issue too! WT19i
Galaxy Nexus [I9250] easy to flash stock factoryImages without lost SDcard data
Everyone know flash factory images gotta lost sd card data in I9250
So we need backup sdcard,that be nausea
Here is the easy way to keep sd data
1 Go get your image from google factory images
2 Unzip tgz file which one you downloaded
Eg. yakju-jro03c-factory-3174c1e5.tgz ,unzip it and find the image-yakju-jro03c.zip
3 Open image-yakju-jro03c.zip, and delete the userdata.img
[This img using for cover your /data，sdcard mount on /data/media in i9250]
4 Begin flash,your can found flash-all.sh in unzip folder
don't use it
flash BL: fastboot flash bootloader bootloader-maguro-primelc03.img
flash baseband: fastboot flash radio radio-maguro-i9250xxlf1.img
OK point coming: fastboot -w update image-yakju-jro03c.zip
{
"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"
}
There is a -w in flash system command . check on fastboot ,-w will **** your /data
So we use fastboot update image-yakju-jro03c.zip to flash system
Cause didnt wipe data ,so flash a CWMrecovery which one wont wipe /data/media
then use CWM to wipe data
Everything done!
Enjoy!
Thank you for this useful post.. :good:
Is this method works with upgrading to 4.2.2? i read some articles about problems in this version with the SDCARD folder permissions and multi-user stuffs? have you tried it befor?
another question.. i had now a soft-break because of an App "Font Installer ★ Root ★" but i made backups using recovery to SDCARD folder, but i can't pull them out as you know without starting up the device in ADB mode.. and i had 4.2.1 (Officially with root access and unlocked boot-loader) is it safe to do your method without any lost of my data in SDCARD folder? or there's another method?
Best Regards.
I have been having an issue for some time now where if I install a new app, or upgrade an existing app, the .so files in the data/data/"app name"/lib folder get dated up to a month in the future. I first noticed this in Titanium Backup when sorting get by data freshness. For example, on 10/10 I downloaded an update to Google Earth from the Play Store. Titanium Backup shows the data changed 11/8/12:
{
"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"
}
And here is the data/data/com.google.earth/lib folder contents in ES Explorer:
If I use a terminal emulator and display the directory with BUSYBOX LS -AL, I get:
=/data/local/bin:$PATH <
-al /data/data/com.google.earth/lib <
drwxr-xr-x 2 system system 4096 Oct 10 23:37 .
drwxr-xr-x 8 app_334 app_334 4096 Oct 10 23:01 ..
-rwxr-xr-x 1 system system 18181840 Nov 8 2012 libearthmobile.so
[email protected]:/ $
The incorrectly dated .so files display a year instead of a time, which the correctly dated files display.
This issue has survived multiple stock roms (including a data wipe to FI03) and multiple versions of Agat's Source kernel. Does anyone have any idea what could be causing this or how I might fix it? Thanks!
The only way I have been able to deal with this issue is to redate the files in the lib/ folders, which is a loosing battle. Anyone have any idea what could be causing this?
it's in dd/mm/yy mode
supersaeed said:
it's in dd/mm/yy mode
Click to expand...
Click to collapse
Thanks... how do I get it out of that mode?
I've searched here and on Google and can't find anything about a dd/mm/yy mode? Can anyone help me with this? :banghead:
i haven't a clue lol sorry
supersaeed said:
i haven't a clue lol sorry
Click to expand...
Click to collapse
Yeah, lol, I had a feeling you didn't have a clue when I read your original original answer, but I am desperate... :banghead:
Issue still exists after upgrading to FI27 (not that I thought it wouldn't), still looking for an answer to this. Apparently, this 'feature' is UNIQUE to my phone, so if there are any collectors out there, I'll sell it to you for $999.98...
Hello,
Bootloop on my phone ...
I've a problem with my phone.
Impossible for a Refurbish / update / Partition DL via LGUP
Message : Error : 0x81000302, Please use latest DLL LAF Protocol version is not match DLL = 0 Device = 116342816
And on my phone on the Download Mode :
633A B67
Modified / E / L / RO
I think that flash boot_a and boot_b stock manually via Fastboot ?
For the Good update on LGUP ?
Sorry For my english, i'm french ^^
Best regards,
thanks
I think you got a wrong version of LGUP. Try this one : https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
If you get an error also with this one just update with LG MOBILE SUPPORT TOOL ( it can be downloaded from support section in the official LG website. For the recover process you only need YOUR IMEI or S/N).
@nicoilboss
Thanks a lot, I will test this, I'll let you know !
Edit : It's doesn't works ...
Olvers974 said:
@nicoilboss
Thanks a lot, I will test this, I'll let you know !
Edit : It's doesn't works ...
Click to expand...
Click to collapse
did you tried also with Lg Support Tool ?
You have to reboot your phone into the download mode and then use the IMEI for an advanced restore.
You can find the tool here : lg DOT com/fr/support/support-mobile/lg-LMG710EM
{
"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"
}
nicoilboss said:
did you tried also with Lg Support Tool ?
You have to reboot your phone into the download mode and then use the IMEI for an advanced restore.
You can find the tool here : lg DOT com/fr/support/support-mobile/lg-LMG710EM
Click to expand...
Click to collapse
Yeap ...
Solved !
Octoplus pro JTAG Software ...
One solution !
Olvers974 said:
Solved !
Octoplus pro JTAG Software ...
One solution !
Click to expand...
Click to collapse
How much?
I've got a 65-inch 4K Funai/Philips Android TV. Is this TV rootable or flashable? The OS is so laggy on this device it makes it almost unbearable to use. Opening specific screens takes seconds because of all the quirky animations. I'd much rather prefer flashing a different version of Android TV that doesn't lag any time I scroll to the next app on the home screen.
I have successfully unlocked the bootloader through fastboot. I'm not experienced to go any farther than that though.
Originally,
Code:
fastboot flashing get_unlock_ability
returned "(bootloader) lock"
After running
Code:
fastboot flashing unlock
it appears to unlock bootloader.
It factory resets tv after unlock, and persists through reboots.
{
"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'd love nothing more than to get root working on this TV! Any suggestions on what to do next from people smarter/more experienced than me, throw it out there.
OTA firmware: https://android.googleapis.com/packages/ota-api/package/374df80dffab69614dcb3d2b1f8c689d1ee96e23.zip
System, Vendor, boot, and magisk-patched boot .img files https://mega.nz/folder/MpwB3ISK#0CQFgDQhV2bbTL35XoKycw
So I believe as long as I'm on the OTA firmware that's linked above, I theoretically should be able to achieve root by:
Code:
fastboot flash boot magisk.boot.img
vincentanzalone said:
OTA firmware: https://android.googleapis.com/packages/ota-api/package/374df80dffab69614dcb3d2b1f8c689d1ee96e23.zip
System, Vendor, boot, and magisk-patched boot .img files https://mega.nz/folder/MpwB3ISK#0CQFgDQhV2bbTL35XoKycw
So I believe as long as I'm on the OTA firmware that's linked above, I theoretically should be able to achieve root by:
Code:
fastboot flash boot magisk.boot.img
Click to expand...
Click to collapse
any idea how i go about grabbing the ota firmware or any firmware for my tv ? it's the phillips walmart 75 inch model, i was able to unlock bootloader but mtk client doesn't work with it, no way to get to brom mode to test. want a proper dump before i start essing with anything. Thanks much
vincentanzalone said:
OTA firmware: https://android.googleapis.com/packages/ota-api/package/374df80dffab69614dcb3d2b1f8c689d1ee96e23.zip
System, Vendor, boot, and magisk-patched boot .img files https://mega.nz/folder/MpwB3ISK#0CQFgDQhV2bbTL35XoKycw
So I believe as long as I'm on the OTA firmware that's linked above, I theoretically should be able to achieve root by:
Code:
fastboot flash boot magisk.boot.img
Click to expand...
Click to collapse
well, I find myself in a soft brick situation. I cannot get the OTA zip to load from USB, do you happen to have the file as it came or is this it ?