I downloaded the file, MD5 (I537UBUAMG2_I537TCEAMG2_I537UBUAMG2_HOME.tar.md5) just waiting to see if it has worked?
And where did you happen to acquire this file from since afaik there's no flashable version of MF2 floating around out there. MF2 is what was installed on most GS4A's from the factory which then upgraded to MF3 by OTA (again, afaik).
An MD5 "file" is just a very tiny text file with a line of info, usually the MD5 checksum and then the name of the file that checksum is associated with - we're talking about a file that's less than 100 bytes in size most of the time whereas the actual ROM file would end up being several hundred to at least 1.1-1.3GB in size.
Are you sure you understand what it is you might have downloaded?
MF2
brekstar said:
I downloaded the file, MD5 (I537UBUAMG2_I537TCEAMG2_I537UBUAMG2_HOME.tar.md5) just waiting to see if it has worked?
Click to expand...
Click to collapse
http://samsung-updates.com/device/?id=SGH-I537
This is where...
It's the Mexican version of the firmware... someone here tried it... wasn't successful though.
First of all this file is MG2 not MF2. A little misleading and furthermore this MG2 has indeed been tried and verified to not work.
GT-i9295(i537) running SafeStrap
Related
I downloaded a zip file from sammobile.com's OTA files section. The ZIP contains the following files:
debug_info ==> 1kb (size)
delta.hidden ==> 856kb
delta.modem ==> 1kb
delta.platform ==> 84455 kb
delta.Sbl ==> 1280kb
delta.ua ==> 241 kb
delta.zImage ==> 4936kb
the ZIP file won't install using Mobile Odin, Odin, and CWM. In mobile Odin, it says that the file is not an OTA / Update ZIP file, and merely extracted the contents.
the filename of the downloaded file is GT-N7000_SMA_93970111.zip.
any idea how i can install the OTA file?
I have tried searching this forum and google, but to no avail. it appears that nobody knows how to use the ZIP file.
Any leads would be greatly appreciated.
Thanks in advance for your help.
What was your purpose in downloading this OTA file anyway? A firmware zip file either contains a single file with "tar.md5" as the extension or 3 files for CSC, Modem/phone and PDA file all of which are recognized automatically by mobile odin or can be loaded on PC odin. I don't think sammobile has files for CWM. No idea about the several files that are contained on the one you downloaded. From the size of the files alone we can conclude that this is NOT firmware as normal size is 600-900 MB.
What I understand from the word OTA is Over The Air and as such can only be used either within the device itself to update or thru kies.
Good luck!
I think it is a very specific scenario to use ota.
The ota file probably need you to have previous released versions of csc installed.
Dont know much about mobile odin.
I think ota is a new feature in mobile odin. Best to check cf mobile odin thread.
Sent from my GT-N7000 using Tapatalk 2
when Mobile Odin extracts the zip file you'll get a.md5 file. After the extraction just select this md5 file in Mobile Odin and you're good to go
According to the OP there is no md5 file contained on the zip file.
As per sammobile:
OTA files
This section is specially for the die-hard Samsung owner.
The person who love to tweak with their device fully on their own RISK!
If you dont know what to do with these files, you probably shouldn't touch them.
Let those who knows do it insead.
Not all OTA updates are officially released to public! Samsung may use OTA firmwares as tests first.
SamMobile will not help you with all kind of OTA updates.
Using OTA updates is fully at your own risk.
Feel free to use our forums for any kind of question regading update with the OTA files.
Click to expand...
Click to collapse
AFAIK OTA updates are firmware specific.You must be on certain firmwares to flash the OTA.For exampleTA update yyy may need you to be on xxx firmware for it to work.But sadly I dont know how to flash it....
Could it be that you have to be totally stock unrooted to be able to flash it via stock recovery (3e)? If that's the case the OTA .zip must be stored in external sd. I don't think need to rename it to update.zip, because we can still flash any .zip with the right signature on 3e. Thinking of trying on my Note but it has been 'out of flashed' for close to a month!
kopitalk said:
Could it be that you have to be totally stock unrooted to be able to flash it via stock recovery (3e)? If that's the case the OTA .zip must be stored in external sd. I don't think need to rename it to update.zip, because we can still flash any .zip with the right signature on 3e. Thinking of trying on my Note but it has been 'out of flashed' for close to a month!
Click to expand...
Click to collapse
So we just need to sign the file - any idea?
chikess said:
So we just need to sign the file - any idea?
Click to expand...
Click to collapse
No, it's not necessary (and it's not what I meant about the whole thing).
kopitalk said:
No, it's not necessary (and it's not what I meant about the whole thing).
Click to expand...
Click to collapse
then tell us what do you want to do? the 3e recovery wont take the file even if it is renamed or not... I've got totally unrooted and on stock.
Hi All,
I'm relatively new to Android (had the Nexus 7 for about a year). My questions is this:
I have 4.2.2 currently loaded. When I orinally got the nexus 7, I used a toolkit to unlock the bootloader and root the device, so I could install SixAxis and a few other apps that required root.
What is the easiest way for me to now update to 4.3? Will the OTA update that is bound to show up on the device shortly work?
BTW This is the WiFi only Nexus 7, 16 GB and my main PC at home is a Mac.
Thanks.
Foxman2k said:
Hi All,
I'm relatively new to Android (had the Nexus 7 for about a year). My questions is this:
I have 4.2.2 currently loaded. When I orinally got the nexus 7, I used a toolkit to unlock the bootloader and root the device, so I could install SixAxis and a few other apps that required root.
What is the easiest way for me to now update to 4.3? Will the OTA update that is bound to show up on the device shortly work?
BTW This is the WiFi only Nexus 7, 16 GB and my main PC at home is a Mac.
Thanks.
Click to expand...
Click to collapse
Get it locked and unrooted to get OTA possiblt easiest way.
Otherwise flash the factory images:thumbup:
Sent using Nexus 7
basuraunak said:
Get it locked and unrooted to get OTA possiblt easiest way.
Otherwise flash the factory images:thumbup:
Sent using Nexus 7
Click to expand...
Click to collapse
Do you have a link of a guide that I could follow on how to flash the factory image?
Can I download the zip and then use the clockwork recovery i have installed to load the zip?
I don't think that having the bootloader locked or unlocked will really affect the OTA..
Am I right or am I right?
Foxman2k said:
Do you have a link of a guide that I could follow on how to flash the factory image?
Can I download the zip and then use the clockwork recovery i have installed to load the zip?
Click to expand...
Click to collapse
Just use wug's toolkit. Its over in the android development in the n7 section...
---------- Post added at 10:04 AM ---------- Previous post was at 10:00 AM ----------
drake90001 said:
I don't think that having the bootloader locked or unlocked will really affect the OTA..
Am I right or am I right?
Click to expand...
Click to collapse
I dont think having it unlocked will effect the ota (it hasnt in the past for me), but it sounded like he wanted to flash the factory image. I actually have a nandroid of it on my unlocked n7. Gonna flash the official and see if I can get the ota later...
I've taken OTAs no problem on an unlocked, rooted device with TWRP recovery. So you're fine.
Sent from my Nexus 7 using Tapatalk 4 Beta
Here you go for flashable zip :
http://forum.xda-developers.com/showthread.php?t=2376522
Sent from my Nexus 7 using xda premium
So I downloaded what I believe to be the right file, ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07 (1).zip.
I then reboot my nexus 7 into clockworkmod revovery and select install zip, choose zip from sdcard, browse to the aboev file but then get an error:
It ends in (Status 7) Installation aborted.
What am I missing?
Also, just tried via adb sideload and that didn't work either.
Foxman2k said:
So I downloaded what I believe to be the right file, ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07 (1).zip.
I then reboot my nexus 7 into clockworkmod revovery and select install zip, choose zip from sdcard, browse to the aboev file but then get an error:
It ends in (Status 7) Installation aborted.
What am I missing?
Click to expand...
Click to collapse
Did you install the aosp browser and rename the default browser apk and odex files or modify the buildprop file? Those must be as original to take the update. Also, you should have gotten a message about what failed when you get the Status 7 error. What else did it say?
Groid said:
Did you install the aosp browser and rename the default browser apk and odex files or modify the buildprop file? Those must be as original to take the update. Also, you should have gotten a message about what failed when you get the Status 7 error. What else did it say?
Click to expand...
Click to collapse
No to all of the above. I don't know what odex files or buildprop file would refer to, so I defintely haven't modified them.
It says:
Warning: No file_contextsVerifying current system...
assert failed: apply_patch_check("/system/bin/debuggerd", "a whole bunch of letters and numbers", "a whole bunch of letters and numbers")
E:Error in /sdcard/0/update rom/ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi - JWR66V - from - JDFQ39.ab67ca07 (1).zip
(Status 7)
Installation aborted.
Groid said:
Did you install the aosp browser and rename the default browser apk and odex files or modify the buildprop file? Those must be as original to take the update. Also, you should have gotten a message about what failed when you get the Status 7 error. What else did it say?
Click to expand...
Click to collapse
Foxman2k said:
No to all of the above. I don't know what odex files or buildprop file would refer to, so I defintely haven't modified them.
It says:
Warning: No file_contextsVerifying current system...
assert failed: apply_patch_check("/system/bin/debuggerd", "a whole bunch of letters and numbers", "a whole bunch of letters and numbers")
E:Error in /sdcard/0/update rom/ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi - JWR66V - from - JDFQ39.ab67ca07 (1).zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Does it make a difference that my current build number in "about tablet" shows as JDQ39 and not JDFQ39 as above?
The problem file is 'debuggerd' in the /system/bin folder as it says in the error message. I had the same issue previously on the last N7 update. I had to get the original file from someone since the file had been replaced by another app (possibly Stickmount) or it can be extracted from the previous update to 4.2.2. I don't know about the JDFQ39 compared to the download file showing JDQ39, but that is the same file I downloaded. The (1).zip means you had previously downloaded the file and this is an additional d/l. That shouldn't be a problem, but you can delete the (1) if you want.
I'll try flashing through CWM and let you know if mine worked. If so, I can send you the right 'debuggerd' file.
Groid said:
The problem file is 'debuggerd' in the /system/bin folder as it says in the error message. I had the same issue previously on the last N7 update. I had to get the original file from someone since the file had been replaced by another app (possibly Stickmount) or it can be extracted from the previous update to 4.2.2. I don't know about the JDFQ39 compared to the download file showing JDQ39, but that is the same file I downloaded. The (1).zip means you had previously downloaded the file and this is an additional d/l. That shouldn't be a problem, but you can delete the (1) if you want.
I'll try flashing through CWM and let you know if mine worked. If so, I can send you the right 'debuggerd' file.
Click to expand...
Click to collapse
Ok great. I do have stickmount installed...
Well, I got the debuggerd error also. I'll try the backup debuggered file I used in the last update. Otherwise, I'll have to find the debuggerd file from 4.2.2. Any help out there?
Groid said:
Well, I got the debuggerd error also. I'll try the backup debuggered file I used in the last update. Otherwise, I'll have to find the debuggerd file from 4.2.2. Any help out there?
Click to expand...
Click to collapse
Glad I'm not alone lol
Still no joy. I think someone will have to get the right debuggerd file and get it to one us on a pm or email. Also, I noticed on my update try that the file was listed as JDQ39. ... and not the JDFQ39. ... that you saw.
Groid said:
Still no joy. I think someone will have to get the right debuggerd file and get it to one us on a pm or email. Also, I noticed on my update try that the file was listed as JDQ39. ... and not the JDFQ39. ... that you saw.
Click to expand...
Click to collapse
once we get the file, how do I replace the file with the debuggerd that is currently on the nexus?
What I will do is to copy the debuggerd file to the N7 internal storage root folder from my pc. Then I will rename /system/bin/debuggerd to debuggerd.bak (or whatever extension you want to add). Then I will copy the correct debuggerd file from sdcard to /system/bin and try the update again. I started a new thread asking for someone with an unaltered 4.2.2 debuggerd file to send it to me. If I get it I'll pass it along to you.
Groid said:
What I will do is to copy the debuggerd file to the N7 internal storage root folder from my pc. Then I will rename /system/bin/debuggerd to debuggerd.bak (or whatever extension you want to add). Then I will copy the correct debuggerd file from sdcard to /system/bin and try the update again. I started a new thread asking for someone with an unaltered 4.2.2 debuggerd file to send it to me. If I get it I'll pass it along to you.
Click to expand...
Click to collapse
Are you using a tool like ES File Manager to do the moving and renaming of files etc?
Is there another place I can find the 3.04.651.2 RUU zip other than on here, because the post that has it doesn't work I get Sprint_HTC_One_m7wls_3_04_651_2_RUU.zip: The archive is either in unknown format or damaged. The person who posted the file hasn't fixed it yet either. I already did a google search the only other place was Android Central, but it has the exact same broken file as on here so I'm completely stuck as I can't just take a non-RUU and put it on my phone through fastboot, because it fails at the signature check.
goldenninja said:
Is there another place I can find the 3.04.651.2 RUU zip other than on here, because the post that has it doesn't work I get Sprint_HTC_One_m7wls_3_04_651_2_RUU.zip: The archive is either in unknown format or damaged. The person who posted the file hasn't fixed it yet either. I already did a google search the only other place was Android Central, but it has the exact same broken file as on here so I'm completely stuck as I can't just take a non-RUU and put it on my phone through fastboot, because it fails at the signature check.
Click to expand...
Click to collapse
Download it from the (VT) Mirror #10
http://m10.androidfilehost.com/download.php?fid=23203820527945238
It downloaded just fine and the MD5 Checksum verified.
Thank you for trying, but I still get the message: Sprint_HTC_One_m7wls_3_04_651_2_RUU.zip: The archive is either in unknown format or damaged when I go to extract the file from the zip.
Have you looked here?
http://forum.xda-developers.com/showthread.php?t=2508907
if u are getting this msg on every download, then clearly the trouble is on your end, as it has been verified by many to extract fine...try a different pc
O.M.J said:
if u are getting this msg on every download, then clearly the trouble is on your end, as it has been verified by many to extract fine...try a different pc
Click to expand...
Click to collapse
Thank you for the suggestion to try it on another computer, I was able to extract the zip and complete what I needed to do.
can someone confirm md5 and sha1 hashes for following files on
filefactory.com/folder/c6cdedc45a775d27
edit found another link:
mega.co.nz/#F!29RX1L6I!gfxcXgqkAhf5GDhr_aPGYg
the files took 2 hrs each on regular download for me so just want to confirm they completed fully.
RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip
SHA1=da0b082ebf453170cf9141c961b33b6278c12e31
MD5 =b44ffe73058ebb8b85c853151f8c3e36
RETUAWS_XT1064_4.4.4_KXB21.85-23_cid9_CFC.xml.zip SHA1=615e4331c8cd77b96aa29c280d539214c79cc714
MD5=fc2eb59808fed31a5df81c3f039da4c6
RETUAWS_XT1064_5.0.2_LXB22.46-28_cid9_CFC.xml.zip
SHA1=e77f7bad0feb5a52963f36e1d1bd2220b606dd6f
MD5=c1e6f2c875da36147d468b178d22a1e9
Click to expand...
Click to collapse
edit: it seems to work just fine (i only tried 5.0.2 version, hashes from both links are the same)
Can those of you who have been successful rooting the Sprint LG G4 post the MD5 hash for LS991ZV5.tar.gz?
I can't finding it at the download site or the [Root] thread and would like to verify it with a know good.
Sorry for being redundant but I'm under a time crunch atm.
Well, out of time. I guess I'll be without root for a while more :crying:
Thanks
I'll get around to it when I can get back to a PC
http://forum.xda-developers.com/showthread.php?p=62062521
Sent from my LGLS991 using Tapatalk
Ok.... I'm lost and i apologize but copy the command where?
MDHarper said:
Can those of you who have been successful rooting the Sprint LG G4 post the MD5 hash for LS991ZV5.tar.gz?
I can't finding it at the download site or the [Root] thread and would like to verify it with a know good.
Sorry for being redundant but I'm under a time crunch atm.
Click to expand...
Click to collapse
Use my android file host
http://forum.xda-developers.com/showthread.php?p=62062521
Sent from my LGLS991 using Tapatalk
Shell after connecting to the appropriate COM port when your phone is in download mode
Jessooca said:
For Sprint... 53FAB3EF537C3917AB96AA219D1AC32C (be sure you extract the img file from the tgz file you downloaded before copying it to the root of your INTERNAL and do NOT rename it) After you've extracted it, (use 7zip, winrar, etc) you can verify your # using this http://onlinemd5.com/ select "choose file" at the top and select your IMG file that's extracted from that tgz file and you should have the same # as mine. It should take about 3 minutes
Click to expand...
Click to collapse
I'm not sure the md5 value you're showing is correct, because the checksum generator in the link you posted has a max file size of 4GB and the image file size is 4.565,499,904 bytes.
ES File Explorer shows an MD5 checksum of bba2f6e3342db0ca171ddfde8286c0da for that file on my phone.
Jessooca said:
The Sprint G4 ls991zv5.tar.gz file is less than 2gb.
Click to expand...
Click to collapse
We're not talking about the ls991zv5.tar.gz file, we're talking about the system.rooted.LS991ZV5.img file.
The MD5 checksum value you posted is the one generated for the system.rooted.LS991ZV5.img file by the MD5 & SHA1 Hash Generator found in your link. Go ahead and try it again with that same file and you'll get the same value you posted. What I'm saying is that value is wrong because the file is too big for that Hash Generator to handle.