Related
Help needed please!
I'm trying to install Dexters Mod update and I keep getting the same results, it reads:
Finding update package...
Opening update package...
E: Can't open/sdcard/update.zip
(bad)
Installation aborted
Formatting misc...
I've formatted my SD card. I've tried renaming the file with a capital U, lowercase u, etc. I've wiped the unit....nothing works.
My SD card worked fine when I installed the Elocity update from their website.
What am I doing wrong? I really want to get that Marketplace installed....
Thanks for your help!
Did you do it from Recovery menu? It's necessary.
elocity
Hi, I need help with this too, I really want the market on my elocity. Thanks
Kentavr66X said:
Did you do it from Recovery menu? It's necessary.
Click to expand...
Click to collapse
Yes, I did it from the System Update option which puts the unit into the recovery menu. That's the correct way, yes?
It looks like all the Mod files from this site are damaged or corrupted...? I run a test on the download on my computer and there appears to be issues with the download. Has anyone else had this problem???
Any help is greatly appricated. Thanks!
I had trouble with the install also: i was able to enter the recovery mode but it would recognize the update then i would see the android logo and box with arrow then nothing from there this happened several times. I left the card in the unit turned it off then back on , then went to the system update and chose to update , which it did and rebooted then was locked in an Elocity loop. I reset the unit and the market and everything was there. I might of been close to bricking it ,but it works now. Be careful
esemelis said:
Yes, I did it from the System Update option which puts the unit into the recovery menu. That's the correct way, yes?
It looks like all the Mod files from this site are damaged or corrupted...? I run a test on the download on my computer and there appears to be issues with the download. Has anyone else had this problem???
Any help is greatly appricated. Thanks!
Click to expand...
Click to collapse
Sounds like your downloaded zip file was corrupted - this happens often. Try downloading it again and then try to install after that.
Recarr said:
I had trouble with the install also: i was able to enter the recovery mode but it would recognize the update then i would see the android logo and box with arrow then nothing from there this happened several times. I left the card in the unit turned it off then back on , then went to the system update and chose to update , which it did and rebooted then was locked in an Elocity loop. I reset the unit and the market and everything was there. I might of been close to bricking it ,but it works now. Be careful
Click to expand...
Click to collapse
This is quite normal. boot loop happens to 90% of users. Its well documented in the development thread. The Android logo you saw is also expected. From there, you're supposed to hit the Menu soft key and use the other soft keys to navigate the recovery console. Also well documented in the development thread.
sagggas said:
Sounds like your downloaded zip file was corrupted - this happens often. Try downloading it again and then try to install after that.
Thanks sagggas. I've tried to download it about 20 times and I get the same problem. When I run a test on the downloaded zip file my computer says it may be corrupted or incomplete. I don't get it. It's as if the something is wrong with the file, but others seem to have made it work. Any suggestions please??? I'm almost ready to get rid of this device....but since this is the only problem I've had I'm torn!
Click to expand...
Click to collapse
GetRight Download Manager
Hi
This reminds of a problem I had downloading a large software program a while back. Many people were having the same problem with corrupt files. The company recommended using a download manager called GetRight.
It worked great! It is free to use and you can get it at:
http://getright.com/get.html
Let us know if it works for you.
esemelis said:
sagggas said:
Sounds like your downloaded zip file was corrupted - this happens often. Try downloading it again and then try to install after that.
Thanks sagggas. I've tried to download it about 20 times and I get the same problem. When I run a test on the downloaded zip file my computer says it may be corrupted or incomplete. I don't get it. It's as if the something is wrong with the file, but others seem to have made it work. Any suggestions please??? I'm almost ready to get rid of this device....but since this is the only problem I've had I'm torn!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Jazzbone, that download manager worked perfectly! Once I was able to download the Dexter Mod without it getting corrupted the install went very smoothly.
Thank you sooo much for that suggestion! I can't wait to see what this tablet can do now.
Having the same problem. I did check out the website, but I saw nothing for Android,
Dealcloser73 said:
Having the same problem. I did check out the website, but I saw nothing for Android,
Click to expand...
Click to collapse
The getright manager is software for your PC to help you download large files from the internet. In our case, the functionality would then allow us to copy the newly downloaded file (apparently with a lower frequency of corruption) from our PC to our SD cards for use in our Android devices.
Just got a problem when im flashing a new Kernel
Can anyone tell me what should i do now?:crying:
can't post outside links
Nothing, an MD5 check is only so the PC can cross-reference the download to see if it has downloaded correctly.
For example, a download may have an MD5 of - 1122334455AA
If your download gets corrupted, it may have - 1122334455AB
Therefor the MD5 is wrong and the download is corrupt.
It will not affect your flash, it should just skip the check and carry on.
If the flash has gone wrong, perhaps the download is corrupt.
Wilks3y said:
Nothing, an MD5 check is only so the PC can cross-reference the download to see if it has downloaded correctly.
For example, a download may have an MD5 of - 1122334455AA
If your download gets corrupted, it may have - 1122334455AB
Therefor the MD5 is wrong and the download is corrupt.
It will not affect your flash, it should just skip the check and carry on.
If the flash has gone wrong, perhaps the download is corrupt.
Click to expand...
Click to collapse
thanks for reply
but when i finish the flash and press reboot system
it say "No OS Installed!Are you sure you wish to reboot?"
What are you trying to flash, how are you flashing it and which bits are you flashing?
Need more info :/
Wilks3y said:
What are you trying to flash, how are you flashing it and which bits are you flashing?
Need more info :/
Click to expand...
Click to collapse
I do not believe .....!
I deleted everything in RECOVERY what can I do now ...
I have no system on the device and the device does not connect to my computer!
This morning I was attempting to update the firmware on my i9505.
I downloaded and extracted the .tar.md5 file and opened Odin in administrator mode.
Stupidly I then added the downloaded file as Phone and not PDA and pressed start in Odin. Unsurprisingly it failed.
I downloaded and tried other firmware (as Phone) before I realised my error.
When I boot the phone "normally" I get the failed firmware update message and have tried Kies but it can't connect to the phone.
Download mode does work, but when I try with the firmware (stock and pre-rooted) as PDA it always fails.
Can someone please help to recover my phone? I'm feeling pretty stupid just now
floydart said:
This morning I was attempting to update the firmware on my i9505.
I downloaded and extracted the .tar.md5 file and opened Odin in administrator mode.
Stupidly I then added the downloaded file as Phone and not PDA and pressed start in Odin. Unsurprisingly it failed.
I downloaded and tried other firmware (as Phone) before I realised my error.
When I boot the phone "normally" I get the failed firmware update message and have tried Kies but it can't connect to the phone.
Download mode does work, but when I try with the firmware (stock and pre-rooted) as PDA it always fails.
Can someone please help to recover my phone? I'm feeling pretty stupid just now
Click to expand...
Click to collapse
do you have custom recovery that you can boot into it?
samersh72 said:
do you have custom recovery that you can boot into it?
Click to expand...
Click to collapse
djembey sent me a couple of files and a ROM passed in Odin.
I don't think it's loading though as it's stuck on the SAMSUNG logo (and has been for about 15 mins) ....
floydart said:
djembey sent me a couple of files and a ROM passed in Odin.
I don't think it's loading though as it's stuck on the SAMSUNG logo (and has been for about 15 mins) ....
Click to expand...
Click to collapse
remove battery then insert it, boot into recovery, wipe cache and data, reboot
samersh72 said:
remove battery then insert it, boot into recovery, wipe cache and data, reboot
Click to expand...
Click to collapse
I rebooted to recovery and did a wipe data then a wipe cache. Recovery crashed and the phone rebooted.
This time the boot sound played completely and my phone is back to initial setup screen - thank you :good:
floydart said:
I rebooted to recovery and did a wipe data then a wipe cache. Recovery crashed and the phone rebooted.
This time the boot sound played completely and my phone is back to initial setup screen - thank you :good:
Click to expand...
Click to collapse
Did you feel the adrenalin flowing? I thought I bricked mine earlier. We had a mini power cut half way through flashing and it booted up with "Connect to Kies to do emergency firmware upgrade" or something like that. lol
Felt the cheeks of my bum twitch a bit there. lol
Managed to reflash one of the few stock ROMS I have to hand.
artnada said:
Did you feel the adrenalin flowing? I thought I bricked mine earlier. We had a mini power cut half way through flashing and it booted up with "Connect to Kies to do emergency firmware upgrade" or something like that. lol
Felt the cheeks of my bum twitch a bit there. lol
Managed to reflash one of the few stock ROMS I have to hand.
Click to expand...
Click to collapse
Aye, you could say that
I would say that I won't try flashing again after 3 or 4 hours sleep, but knowing me I probably will ....
S4 bricked after freeze during unmount internal sdcard
Dear friends. I need your help!
I did the actualization on my S4 i9500 (I9500XXUAMDK with root) and after this, I was trying to put more space in my SDcard (editing vold fstab files). During this process, appeared a message on phone about one error in sdcard and it suggested me to unmount the sdcard to try solve the problem. So, when I click yes, the phone froze and then I turned it off, but now it dont pass to Sangung Logo and the phone just go in recovery mode. In recovery mode I tryied clear/mount/unmount some file, but return with error to mount any directories.
I think the phone have the files or some partition corrupted!!! I can access it through ODIN and adb shell as well. There is (in adb commands) a command to fix the partition? How can I do?
I can access the phone in ODIN, and I tried to re-install the original FW. It did well (OK for update), but the phone cant finish the instalation after, because it cant mount anything. And returns to recovery mode with many messages about it cant mount directories.
Every thing I try to do, the phones (in recovery mode) returns "cant mount... or error to mount". I as said, I cant clear cache, format /sdcard or other directory or reset to factory data as well (because I think, the system cant mount any directories).
Somebody had this problem or could help me to solve it, please!!!
Tks in advance!
Barros
rgbarros said:
Dear friends. I need your help!
I did the actualization on my S4 i9500 (I9500XXUAMDK with root) and after this, I was trying to put more space in my SDcard (editing vold fstab files). During this process, appeared a message on phone about one error in sdcard and it suggested me to unmount the sdcard to try solve the problem. So, when I click yes, the phone froze and then I turned it off, but now it dont pass to Sangung Logo and the phone just go in recovery mode. In recovery mode I tryied clear/mount/unmount some file, but return with error to mount any directories.
I think the phone have the files or some partition corrupted!!! I can access it through ODIN and adb shell as well. There is (in adb commands) a command to fix the partition? How can I do?
I can access the phone in ODIN, and I tried to re-install the original FW. It did well (OK for update), but the phone cant finish the instalation after, because it cant mount anything. And returns to recovery mode with many messages about it cant mount directories.
Every thing I try to do, the phones (in recovery mode) returns "cant mount... or error to mount". I as said, I cant clear cache, format /sdcard or other directory or reset to factory data as well (because I think, the system cant mount any directories).
Somebody had this problem or could help me to solve it, please!!!
Tks in advance!
Barros
Click to expand...
Click to collapse
Why on Earth would you mess around with stuff like that? I hope you get help here, and next time just flash it and don't mess around. Perhaps get an external SDCard to solve your "space" problem.
artnada said:
Why on Earth would you mess around with stuff like that? I hope you get help here, and next time just flash it and don't mess around. Perhaps get an external SDCard to solve your "space" problem.
Click to expand...
Click to collapse
hehehe... I agree totally with you. But, it wasnt brick because there is some mistake in vold.fstab edition (I suppose). My fault is to accept unmout sugestion in the phone message.
But, it has a soft brick now. I got the access thought adb and odin and I'm trying to find a valid pit to rebuild the partition, that I think is corrupted now (I cant mount anything there. I can access it, but not change anything there).
I found a post here that there is a pit file. I cant ask there because I dont have enough privileges to post in development topic. The links are http://forum.xda-developers.com/showthread.php?t=2217777 and http://forum.xda-developers.com/showthread.php?t=2214865
I´d like to know if this pit (the second link has a file attached), is a valid pit. If yes, I could fix the phone!!!
Tks
rgbarros said:
hehehe... I agree totally with you. But, it wasnt brick because there is some mistake in vold.fstab edition (I suppose). My fault is to accept unmout sugestion in the phone message.
But, it has a soft brick now. I got the access thought adb and odin and I'm trying to find a valid pit to rebuild the partition, that I think is corrupted now (I cant mount anything there. I can access it, but not change anything there).
I found a post here that there is a pit file. I cant ask there because I dont have enough privileges to post in development topic. The links are http://forum.xda-developers.com/showthread.php?t=2217777 and http://forum.xda-developers.com/showthread.php?t=2214865
I´d like to know if this pit (the second link has a file attached), is a valid pit. If yes, I could fix the phone!!!
Tks
Click to expand...
Click to collapse
i think it is the right pit file for I9500 "Adonis.pit"
samersh72 said:
i think it is the right pit file for I9500 "Adonis.pit"
Click to expand...
Click to collapse
+1
@rgbarros: That is for I9500. Do not try it for I9505
stress nsitylf
samersh72 said:
i think it is the right pit file for I9500 "Adonis.pit"
Click to expand...
Click to collapse
Tks samersh72. I'll try it and I'll give the feedback after. :fingers-crossed:
demlasjr said:
+1
@rgbarros: That is for I9500. Do not try it for I9505
Click to expand...
Click to collapse
Tks demlasjr. My phone is a i9500 (not the ...905).
I run the adonis.pit on pit magic and it generated a analisys report (attached). Before I put it to run on ODIN, you (or somebody) could give a feedback about the entry memory below:
----------------------------------------------------------
Entry Memory Address: 0x754
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 12
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 196.608
Block Count: 16.384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CDMA-RADIO
Flash FileName: modem_cdma.bin
FOTA FileName:
My doubt is about the Partition Name CDMA-RADIO. Is this correct for a i9500 S4? I just really confirm and just to avoid to brick totally my phone, because when I run this pit through ODIN, or fix it or break it (no more chances to revive it)!!!
Tks very much!!!
I've seen that you have the 9500 later, but the forum was down and I couldn't edit my post. On that thread is a discussion about it. Somebody days that may be from 9502. I just seen the art you posted there, try adding this info too, including the pit magic report. Kinda hard to get confirmation and a trustful pit yet.
Sent from my GT-I9300 using Tapatalk 2
demlasjr said:
I've seen that you have the 9500 later, but the forum was down and I couldn't edit my post. On that thread is a discussion about it. Somebody days that may be from 9502. I just seen the art you posted there, try adding this info too, including the pit magic report. Kinda hard to get confirmation and a trustful pit yet.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Dear demlasjr, the forum was down and I forgot to attach the pit magic report when the forum goes up. Im attaching the files now (magic pit report and the adonis.pit that I got in other topic about S4 forum).
If you (or somebody) could help me to analyse it and give us a feedback if this pit is a valid pit for samsung S4 i9500, I will thank a lot!!!
Ps.: I´m trying to solve the problem too, looking for a way to mount the files through adb shell, because I got access my phone with this way and I can see all the files inside there. I just cant to mount any drive yet. Is it possible the problem be only a vold.fstab file corruption or missed? And in this case, is only to solve this file (vold.fstab) to revive my phone?
Or there is a some command in adb shell that could repair the structure files (like scandisk for dos?). I'm newbie on linux and I'm trying to use fsck command, but it returns a error message (fsck: not found). I dont know if I'm putting a correct/complete command to scan and repair the system/drives/files (or if there is a error)...
So, I´m trying to solve it using 3 differents ways of thinking (finding a valid pit, edit/restore vold.fstab and find a correct adb command line to scan and repair eventually corrupt files/directories) and if I solve the problem, I'll be happy to post a tuto here to help some other guys in the future.
Until there, Im working to find a solution.
Tks for help me!!!
nothing worse than this feeling. I remember when I did this to my S2, felt a cold sweat instantly... :crying:
crimptool said:
nothing worse than this feeling. I remember when I did this to my S2, felt a cold sweat instantly... :crying:
Click to expand...
Click to collapse
I agree totally with you my friend!!! I put it down in the first day I bought it... Its terrible!!! hehehe I put other phones down too, but how the others were olds phones (more then 6 months in the market), always I found the cfw or pit's to revive...
S4 is a newest phone, so, there is not a consistent or many topics/files/cfw tested yet. I´m looking for 3 full days about this and I found a lot of topics in how to root/unroot the phone, but not yet about pits, commands, etc...
The problem is that phone has a corruption files inside (my first diagnostic) and this is avoid to flash any firmware there until I fix this problem.
I´m trying to keep calm to avoid to worst the situation. I can access the phone yet, so I see a light in the end of tunnel yet!!!
But, the feeling is terrible!!! hahaha
Until Odia or GSMCN came back to you, we can't help you my friend. Only them can confirm the .pit file comparing the one already published with his phone's pit file.
One question....what if you try Emergency recover in KIES. Connect your phone to pc, open KIES, open emergency recover and insert your phone serial number. I read that people messed some times with the partitions and KIES saved their phone. It will not hurt to try, KIES is a putty compared with the repartitioning.
demlasjr said:
Until Odia or GSMCN came back to you, we can't help you my friend. Only them can confirm the .pit file comparing the one already published with his phone's pit file.
One question....what if you try Emergency recover in KIES. Connect your phone to pc, open KIES, open emergency recover and insert your phone serial number. I read that people messed some times with the partitions and KIES saved their phone. It will not hurt to try, KIES is a putty compared with the repartitioning.
Click to expand...
Click to collapse
I tried to connect it in KIES, but KIES didnt recognizes the phone. I'll try once again!!! I think I really discovered what the problem is, reported by adb parted command in /dev/block/mmcblk0: "error: Both the primary and backup GPT tables are corrupt. Try making a fresh table, and using Parted´s rescue feature to recover partitions"
So, probably when the phone froze during unmounting sdcard, the partitions were corrupted. I'm really thinking to use the adonis.pit, due I think there is no other manner to solve the problem.
I'm waiting any reply from Odia, to see if him can help me. Otherwise, I'll cross fingers and press "enter", to see what happen!!!
My friend, tks for all!!! After I´ll post the results!!! :fingers-crossed:
I cannot do an OTA update i get following error
""/system/framework/core.odex" has unexpected contents. Installation aborted."
error 7
Plz Help!!!
plz!!! anyone.. m in need..
Well i really dont understand your problem...
So u are unable to update de phone, correct?
The System.img that i have are splited in 23 files and its only good for the flashing tool....
Lets try to figure this out...
1 - Check if you have that file "/system/framework/core.odex"
2 - Check the file size, if it's zero maybe it is corrupted
Make sure the update you are trying to do is compatible with your phone
I'm assuming that ur on Kitkat, and also you need to be rooted
Here is the kitkat file core.odex, paste it into the framework folder and try to update again
RSGI_PT said:
Well i really dont understand your problem...
So u are unable to update de phone, correct?
The System.img that i have are splited in 23 files and its only good for the flashing tool....
Lets try to figure this out...
1 - Check if you have that file "/system/framework/core.odex"
2 - Check the file size, if it's zero maybe it is corrupted
Make sure the update you are trying to do is compatible with your phone
I'm assuming that ur on Kitkat, and also you need to be rooted
Here is the kitkat file core.odex, paste it into the framework folder and try to update again
Click to expand...
Click to collapse
Thank you!!!
Yes i am on kitkat and rooted. When i randomly check if there is anymore update, too my surprise there was an 32mb ota waiting. Gionee's software updater download the file and when i pressed "upgrade" the phone restarted went into recovery and started the upgrade process, at 30% i got the above error msg. So, i googled a bit and found that i have lucky patcher and i did a patch to android thingy which messed up my core.odex file and if i flash system.img it should resolve my problem.
I hope this help to understand my problem.
freak_on said:
Thank you!!!
Yes i am on kitkat and rooted. When i randomly check if there is anymore update, too my surprise there was an 32mb ota waiting. Gionee's software updater download the file and when i pressed "upgrade" the phone restarted went into recovery and started the upgrade process, at 30% i got the above error msg. So, i googled a bit and found that i have lucky patcher and i did a patch to android thingy which messed up my core.odex file and if i flash system.img it should resolve my problem.
I hope this help to understand my problem.
Click to expand...
Click to collapse
also want to know will it mess it up phone if i replace the core.odex file...?
Hey guys i couldn't get in the beta so i was wondering if anyone has the Nougat update file that i can flash with odin.
Thanks
Join the club. No one has the VZW one for the flat s7 either....
Illogi.xbone said:
Join the club. No one has the VZW one for the flat s7 either....
Click to expand...
Click to collapse
Someone said they are going to try. I offered help if need be
billydroid said:
Someone said they are going to try. I offered help if need be
Click to expand...
Click to collapse
I cannot post outside links so please PM me if you would like to test the file. I will also upload it to Android File Host when I am approved.
jakemastaflash said:
I cannot post outside links so please PM me if you would like to test the file. I will also upload it to Android File Host when I am approved.
Click to expand...
Click to collapse
Hey, send me the link. Other than the files, the proccess should be the very basic odin proccess right?
diego97yey said:
Hey, send me the link. Other than the files, the proccess should be the very basic odin proccess right?
Click to expand...
Click to collapse
I believe it can be flashed from Recovery. It's being tested now, I will be checking for updates\consistency tomorrow with a clean flash and update.
jakemastaflash said:
I believe it can be flashed from Recovery. It's being tested now, I will be checking for updates\consistency tomorrow with a clean flash and update.
Click to expand...
Click to collapse
Keep us posted man
Footer and verification error so far
Same here
Sent from my SM-G930P using XDA-Developers mobile app
dgr581 said:
Same here
Sent from my SM-G930P using XDA-Developers mobile app
Click to expand...
Click to collapse
Sounds like it is throwing errors for everyone . I will be trying to grab a fresh copy today, or tomorrow. Link removed until we have a working update.
jakemastaflash said:
Sounds like it is throwing errors for everyone . I will be trying to grab a fresh copy today, or tomorrow. Link removed until we have a working update.
Click to expand...
Click to collapse
I tried using winrar to repair it but still got error code my recovery has been acting strange tho. It says install system update when i boot to it then gives me a dead droid with yellow triangle but then enters recovery like normal.
vegoja said:
I tried using winrar to repair it but still got error code my recovery has been acting strange tho. It says install system update when i boot to it then gives me a dead droid with yellow triangle but then enters recovery like normal.
Click to expand...
Click to collapse
I believe I have a solution. I am working on it now. Additionally, I'm getting close 10 posts!
jakemastaflash said:
I believe I have a solution. I am working on it now. Additionally, I'm getting close 10 posts!
Click to expand...
Click to collapse
Another update pull failed verification and resulted in another footer error. If installed without any modification it works, but after rooting and pulling the update.zip, trying to install it results in an error. It could be a security measure introduced to the update.zip to prevent installing on a phone without the matching signature assigned during the initial download.
Whenever i tried to follow the link it asked me for a security key ????
footer error
I read on another nougat beta thread that if you get a footer error then you should decrypt your SD and try agian
N3ksta said:
I read on another nougat beta thread that if you get a footer error then you should decrypt your SD and try agian
Click to expand...
Click to collapse
I did not have my SD Card encrypted. I have also noticed some discrepancies between the update.zip I am extracting and the working VZW update.zip. Things like: the boot.img is 0kb, and there are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
I have tried extracting it in several different ways\environments and get problems with every pull.
Other variants are working on the same thing with the same issues. I have the last pull I made, but I can't continue working on this as heavily since I'm using my daily driver. I'll try again as new info\solutions come up.
Seems like getting root (with current methods) may be disturbing the file structure. There may be something else at play here since all the pulls still come with a boot.img that is 0kb, and are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
Here is the link to the WIP update.zip. I'm going to stop working on this until someone can suggest a better way to root or pull the file without it coming out corrupt\incomplete. Good luck!
Link to the update.zip.
Here is the flashing method used by the VZW folks:
Originally Posted by zimgir124
A method has been found to install the beta without being accepted!
Thanks @jrkruse for finding this method!
1. reboot to download mode (power + volume up +home) and make sure phone says Official under system and binary.
2. If it does not then you must odin the PH1 firmware, use the pit file and the full csc not the home csc file
3. go through setup
4. enable developer options
5. turn OEM unlock off
6. enable USB debugging
7. place Update.zip on Ext sd card in folder named fota
8. power off phone
9. reboot to download mode make sure both system and binary are official.
10. reboot to recovery (Power + volume down + home)
11. choose apply Update.zip from SD card
12. find Update.zip in the fota folder you created on your Ext sdcard
13. click yes to apply
After this it should update to the Android 7.0 beta and hopefully will be able to download future beta OTAs.
You will not lose anything as this is an OTA
You do not want to be rooted. You must be stock for this to work!
There is no gear VR available on the beta.
Troubleshooting:
"E: footer is wrong" followed by "E: signature verification failed" : Decrypt SD Card and try again.
Click to expand...
Click to collapse
jakemastaflash said:
Seems like getting root (with current methods) may be disturbing the file structure. There may be something else at play here since all the pulls still come with a boot.img that is 0kb, and are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
Here is the link to the WIP update.zip. I'm going to stop working on this until someone can suggest a better way to root or pull the file without it coming out corrupt\incomplete. Good luck!
Link to the update.zip.
Here is the flashing method used by the VZW folks:
Click to expand...
Click to collapse
So should this method work for us?
jakemastaflash said:
Seems like getting root (with current methods) may be disturbing the file structure. There may be something else at play here since all the pulls still come with a boot.img that is 0kb, and are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
Here is the link to the WIP update.zip. I'm going to stop working on this until someone can suggest a better way to root or pull the file without it coming out
Here is the flashing method used by the VZW folks:
Click to expand...
Click to collapse
Is it for the flat or edge? also have you tried using adb to pull the file (you probably have, but just asking)
15jpenni said:
So should this method work for us?
Click to expand...
Click to collapse
Ideally it should. However, I have not been able to successfully reproduce the same results as installing the update file without modification.
---------- Post added at 09:04 PM ---------- Previous post was at 09:00 PM ----------
N3ksta said:
Is it for the flat or edge? also have you tried using adb to pull the file (you probably have, but just asking)
Click to expand...
Click to collapse
This is for the SM-G930P regular S7 (not edge). I have pulled it via filemanager app after full root, and via adb on linux and windows after eng kernel root and full root. All of them yielded an apropriately sized update.zip, but it seems to get corrupted during the rooting or extraction process.
Also, there may be a reason behind our update.zip not having a boot.img. We may not need a new boot.img after updating to PJ2, so it isnt packaged in our update. If someone can repackage the update.zip so it passes verification we may have more luck.