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.
Related
Hi out there looking for help with my G2 (D803) . I am new to all this rooting and TWRP stuff but been trying to learn and figure this out. I accepted some update after which the phone only boots into TWRP recovery project v2.6.3.2 now. Looks like I lost everything else (at least that is what I think has happened).
So I have been reading on the forums and learned about using ADB devices and getting the right rom from xda-developers (I am with Telus in Canada) - used http://forum.xda-developers.com/showthread.php?t=2432476 - downloaded LG support tool and flash tool and drivers for phone and installed them all on the computer.
I first had trouble pushing the rom on to my phone (using ADB devices and ADB push commands) because the phone would just turn off while transferring and I could only regain access when the battery is fully drained (happens really fast now?) and I recharge (which seems to take forever now?).
I took the phone to a store and they did some tweaking (says SIMULATING ACTIONS on the title now below TWRP and version number) after which I could push the ROM (I did rename it on the computer) successfully on to the phone using "ADB push" in command prompt.
I proceeded to install the rom and it says successful but clearly it did not work. What I see is:
Finished running boot script.
E:storage partition '//TWRP/BACKUPS/018bf7ce0f4c6fa0' not found
simulation actions ...
updating partition details ...
but then I reboot and it goes back into TWRP.
I tried going through flashtool as well and followed the steps to install the kdz file but it seems like the computer is not connecting to the phone. But if i go to device manager the device shows and says working properly (i installed the drivers already) and you also hear the beep when plugging in the USB cable into the phone. again it also seems to connect through command prompt because i can push a file successfully.
I am getting worried that I am out of luck with this phone . Can anyone help or provide suggestions as to what I am doing wrong? Would really appreciate it. Thanks.
brownbullet said:
Hi out there looking for help with my G2 (D803) . I am new to all this rooting and TWRP stuff but been trying to learn and figure this out. I accepted some update after which the phone only boots into TWRP recovery project v2.6.3.2 now. Looks like I lost everything else (at least that is what I think has happened).
So I have been reading on the forums and learned about using ADB devices and getting the right rom from xda-developers (I am with Telus in Canada) - used http://forum.xda-developers.com/showthread.php?t=2432476 - downloaded LG support tool and flash tool and drivers for phone and installed them all on the computer.
I first had trouble pushing the rom on to my phone (using ADB devices and ADB push commands) because the phone would just turn off while transferring and I could only regain access when the battery is fully drained (happens really fast now?) and I recharge (which seems to take forever now?).
I took the phone to a store and they did some tweaking (says SIMULATING ACTIONS on the title now below TWRP and version number) after which I could push the ROM (I did rename it on the computer) successfully on to the phone using "ADB push" in command prompt.
I proceeded to install the rom and it says successful but clearly it did not work. What I see is:
Finished running boot script.
E:storage partition '//TWRP/BACKUPS/018bf7ce0f4c6fa0' not found
simulation actions ...
updating partition details ...
but then I reboot and it goes back into TWRP.
I tried going through flashtool as well and followed the steps to install the kdz file but it seems like the computer is not connecting to the phone. But if i go to device manager the device shows and says working properly (i installed the drivers already) and you also hear the beep when plugging in the USB cable into the phone. again it also seems to connect through command prompt because i can push a file successfully.
I am getting worried that I am out of luck with this phone . Can anyone help or provide suggestions as to what I am doing wrong? Would really appreciate it. Thanks.
Click to expand...
Click to collapse
I'm not entirely sure, but it sounds like everything in TWRP is being simulated, which would mean that no files are actually written. Try going into Settings in TWRP, uncheck the "Simulate actions" checkbox, and run the rom installation again.
flutterguy317 said:
I'm not entirely sure, but it sounds like everything in TWRP is being simulated, which would mean that no files are actually written. Try going into Settings in TWRP, uncheck the "Simulate actions" checkbox, and run the rom installation again.
Click to expand...
Click to collapse
Thanks for the reply. It definitely did something because the installation process moves forward now. Now I get:
Zip signature verification failed: 1
Error flashing zip '/sdcard/telus.zip
also when i unclick zip file verification in setting i also see:
checking for MD5 file...
skipping MD5 check: no MD5 file found
So problem with the zip file? I downloaded it off xda-developers but I renamed the file to Telus.zip and pushed it on to the phone in the sdcard directory.
Download the whole Rom and flash it
Sent from my LG-D802 using XDA Premium 4 mobile app
brownbullet said:
Thanks for the reply. It definitely did something because the installation process moves forward now. Now I get:
Zip signature verification failed: 1
Error flashing zip '/sdcard/telus.zip
also when i unclick zip file verification in setting i also see:
checking for MD5 file...
skipping MD5 check: no MD5 file found
So problem with the zip file? I downloaded it off xda-developers but I renamed the file to Telus.zip and pushed it on to the phone in the sdcard directory.
Click to expand...
Click to collapse
you are a fxxxing genius thnx you so much
im going through the same thing
bigpappapuff said:
you are a fxxxing genius thnx you so much
Click to expand...
Click to collapse
Can you help me out? The same thing with my G2 and i have no idea how to fix it.
Chris2312 said:
Can you help me out? The same thing with my G2 and i have no idea how to fix it.
Click to expand...
Click to collapse
More info please.
bender_007 said:
More info please.
Click to expand...
Click to collapse
my g2 was was rooted and got an over the air update so now its just stuck in twrp and all of the memory got wiped so i dont know if its possible to fix it or if i have to get a new phone.
There are a lot of threads for your issue. Will search for one when I'm on lap.
Sent from my LG-D802 using Tapatalk
EDIT: There you go
bender_007 said:
There are a lot of threads for your issue. Will search for one when I'm on lap.
Sent from my LG-D802 using Tapatalk
EDIT: There you go
Click to expand...
Click to collapse
Thank you
flutterguy317 said:
I'm not entirely sure, but it sounds like everything in TWRP is being simulated, which would mean that no files are actually written. Try going into Settings in TWRP, uncheck the "Simulate actions" checkbox, and run the rom installation again.
Click to expand...
Click to collapse
Hi,
Was stuck with my HTC Butterfly x920d with the same. Thanks for your guidance, was able to recover.
Foolishly, I had SIMULATE option checked in the recovery settings. Though was able to boot into system but no account, no google & reset stuck into recovery.
Thanks a ton
(I was trying to reset this device for my father)
flutterguy317 said:
I'm not entirely sure, but it sounds like everything in TWRP is being simulated, which would mean that no files are actually written. Try going into Settings in TWRP, uncheck the "Simulate actions" checkbox, and run the rom installation again.
Click to expand...
Click to collapse
How do you get into settings when it goes straight to simulating actions?
Original links:
http://m.muzisoft.com/soft/80706.html
-
http://rom.htc.shoujifans.com/2014/10/11.html
Mirrors:
https://drive.google.com/uc?id=0Bwq9Di4bqEXkQjhTMmpsN1ZmTXM&export=download
-
https://www.dropbox.com/s/ay5y8s8dg...S_0.57_003_release_385969_signed_2_4.zip?dl=0
Tested and works on STOCK AND LOCKED BOOTLOADERS ONLY!
Your device CANNOT have the *tampered* or unlocked status.
WHEN S-OFF IS ACHIEVED; your device will be able to flash this and downgrade as well if it has been unlocked or tampered with.
-Boot up your device and just drop on your SD card / Internal Storage with the name 0P9CDIAG.zip
-Boot back into bootloader and it AUTOMATICALLY begins.
-Flash twice if uncertain to ensure file has written properly.
Hopefully this will help Single SIM variant development!
P.S.
More mirrors are appreciated!
Drive link gives a 403
Also I have contacted HTC and Virgin Mobile about a RUU, and currently at http://www.htc.com/us/support/htc-desire-816-virgin-mobile/ and http://www.htcdev.com/devcenter/downloads/ there is nothing about a RUU. So wherre did you find it because I have been looking for a RUU for the longest time.
FoxyDrew said:
Drive link gives a 403
Also I have contacted HTC and Virgin Mobile about a RUU, and currently at http://www.htc.com/us/support/htc-desire-816-virgin-mobile/ and http://www.htcdev.com/devcenter/downloads/ there is nothing about a RUU. So wherre did you find it because I have been looking for a RUU for the longest time.
Click to expand...
Click to collapse
Oh snap. Guess I'll have to upload it on dropbox instead. Google drive links tend to be kinked lol. Actually the same way these RUU's posted here from those Japanese, Chinese, Korean websites had listed it. I checked HTC and they have the kernel source but no RUUs for any of these devices US or international.
Sent from my 710C using XDA Free mobile app
Thank you. Was hoping for an RUU. Will Download as soon as you have it up somewhere.
Getting signature fail every time I try to flash.
jaysoblitzed said:
Here it is.
https://drive.google.com/uc?id=0Bwq9Di4bqEXkQjhTMmpsN1ZmTXM&export=download
NEW LINK/MIRROR
https://www.dropbox.com/s/ay5y8s8dg...S_0.57_003_release_385969_signed_2_4.zip?dl=0
Tested and it does work.
Remove all mods/apps that require root first.
Then remove all root files from the settings in SuperSU.
Follow up with a reboot and if the SuperSU app is still there then try to delete it like a normal app.
Go into bootloader and flash the stock recovery.
Then boot back up and just drop on your SD card / Internal Storage with the name 0P9CDIAG.zip
Boot back into bootloader and it AUTOMATICALLY begins.
Received Setup Wizard not responding issue on first initial flash.
Booted into bootloader again did it once more and fixed issue.
Hopefully this will help Single SIM variant development!
P.S.
Mirrors for this file are appreciated!
Click to expand...
Click to collapse
The file you uploaded is corrupted. After trying to flash, now nothing works. I re-unlocked the bootloader, flashed a recovery, and after a fresh wipe no ROM's boot, and my only backup refuses to restore data.
FoxyDrew said:
The file you uploaded is corrupted. After trying to flash, now nothing works. I re-unlocked the bootloader, flashed a recovery, and after a fresh wipe no ROM's boot, and my only backup refuses to restore data.
Click to expand...
Click to collapse
Before you flashed you did remove root from SuperSU, then uninstalled it completely, then flashed the stock recovery and relocked the bootloader right?
I had no idea what would happen if I didn't do those as a safety measure and although, I did notice when I used the RUU and booted up the SuperSU app was still there.
Now what I suggest is using the RUU that you posted to fix the system errors after using this one. I will post the link for the 154MB RUU on HTCDEV. Although I don't recommend anyone to use just one of these IF their rooted and has removed system apps from the device.
Also, it isn't corrupted as I tested it on my device before uploading. Here is where I got it from:
http://m.muzisoft.com/soft/80706.html
And here has the same thing
http://rom.htc.shoujifans.com/2014/10/11.html
Sent from my 710C using XDA Free mobile app
jaysoblitzed said:
Before you flashed you did remove root from SuperSU, then uninstalled it completely, then flashed the stock recovery and relocked the bootloader right?
I had no idea what would happen if I didn't do those as a safety measure and although, I did notice when I used the RUU and booted up the SuperSU app was still there.
Now what I suggest is using the RUU that you posted to fix the system errors after using this one. I will post the link for the 154MB RUU on HTCDEV. Although I don't recommend anyone to use just one of these IF their rooted and has removed system apps from the device.
Also, it isn't corrupted as I tested it on my device before uploading. Here is where I got it from:
http://m.muzisoft.com/soft/80706.html
And here has the same thing
http://rom.htc.shoujifans.com/2014/10/11.html
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
Yes I locked flashed stock recovery and relocked bootloader before flashing. I cant even flash the one you posted, it gives the verification error, and since it didn't flash, I tried to open it, and whenever I tried to open it or extract it it tells me the file is corrupt.
FoxyDrew said:
Yes I locked flashed stock recovery and relocked bootloader before flashing. I cant even flash the one you posted, it gives the verification error, and since it didn't flash, I tried to open it, and whenever I tried to open it or extract it it tells me the file is corrupt.
Click to expand...
Click to collapse
Should've flashed the recovery before locking...
And if your flashing in recovery mode there is a verification error. Flashing an RUU would not make this error appear. It wouldn't even load after extracting the files from the .zip and your saying it gave a signature error and verification error. Really?
Sent from my 710C using XDA Free mobile app
jaysoblitzed said:
Should've flashed the recovery before locking...
And if your flashing in recovery mode there is a verification error. Flashing an RUU would not make this error appear. It wouldn't even load after extracting the files from the .zip and your saying it gave a signature error and verification error. Really?
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
I did flash the recovery before locking.
And I didn't flash the RUU in recovery, at first I tried how you said in the OP, and after "checking..." for about 5 minutes it said press power to reboot, and when I did it brought me strait back into Hboot no matter what I did. Then I tried flashing the RUU using "fastboot flash zip "nameofRUUfile".zip, thats when the cmd gave me the "signature verify fail" message. After receiving that message, I tried to open the actual RUU file on my PC using WinRar, thats when it said that the actual file was corrupted.
FoxyDrew said:
I did flash the recovery before locking.
And I didn't flash the RUU in recovery, at first I tried how you said in the OP, and after "checking..." for about 5 minutes it said press power to reboot, and when I did it brought me strait back into Hboot no matter what I did. Then I tried flashing the RUU using "fastboot flash zip "nameofRUUfile".zip, thats when the cmd gave me the "signature verify fail" message. After receiving that message, I tried to open the actual RUU file on my PC using WinRar, thats when it said that the actual file was corrupted.
Click to expand...
Click to collapse
Then its exactly as it says, corrupted. You should re download.
When I open the file with WinRAR I get the following:
android-info.txt
boot_signed.img
dzdata_8g.hdr
dzdata_8g.img
tp_HMX852XD.img
Sent from my 710C using XDA Free mobile app
jaysoblitzed said:
Then its exactly as it says, corrupted. You should re download.
When I open the file with WinRAR I get the following:
android-info.txt
boot_signed.img
dzdata_8g.hdr
dzdata_8g.img
tp_HMX852XD.img
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
I re-downloaded 3 times, thats why I accused the file you uploaded as being the problem. And I get the same thing you do
android-info.txt
boot_signed.img
dzdata_8g.hdr
dzdata_8g.img
tp_HMX852XD.img
But when I try to open android-info.txt from withing the winrar window, or extracting the archive, thats when I get the corrupted message.
FoxyDrew said:
I re-downloaded 3 times, thats why I accused the file you uploaded as being the problem. And I get the same thing you do
android-info.txt
boot_signed.img
dzdata_8g.hdr
dzdata_8g.img
tp_HMX852XD.img
But when I try to open android-info.txt from withing the winrar window, or extracting the archive, thats when I get the corrupted message.
Click to expand...
Click to collapse
Are you sure it wasn't because you flashed the 154MB file you posted? What happened when you used that one before you posted it?
If my link doesn't work download it from the original source. I was just helping everyone out by uploading it to Dropbox seeing as the servers from those sites tend to move a little slow.
And yes the same uploaders from htcui posted this as well as all the other RUU's found on this devices forum.
Sent from my 710C using XDA Free mobile app
jaysoblitzed said:
Are you sure it wasn't because you flashed the 154MB file you posted? What happened when you used that one before you posted it?
If my link doesn't work download it from the original source. I was just helping everyone out by uploading it to Dropbox seeing as the servers from those sites tend to move a little slow.
And yes the same uploaders from htcui posted this as well as all the other RUU's found on this devices forum.
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
Im sure I wasn't flashing the other one, and the other file I posted isn't even a flashable file.
And I've been downloading that since you gave me the link it's just going very slow. But what I don't get is why attempting to flash that RUU broke my /data partition. I can't mount it or restore it from backups.
FoxyDrew said:
Im sure I wasn't flashing the other one, and the other file I posted isn't even a flashable file.
And I've been downloading that since you gave me the link it's just going very slow. But what I don't get is why attempting to flash that RUU broke my /data partition. I can't mount it or restore it from backups.
Click to expand...
Click to collapse
You posted it without testing it but tested mine and ran into issues? If someone tried your file they might be in the same situation your in now.
I think you should flash the one you posted on top of the one I did the same way you did for this file.
But retry the RUU posted as I got the same thing in the bootloader when it says press power to reboot but when I did the phone booted up but I ran into a "setup wizard is not responding" error when it fully booted up. Flashed again and was fixed.
As I said flash the HTC file now available to fix any issues with startup as this RUU may contain the files/apps but the RUU you posted organizes the files/apps for the system in the correct manner I believe.
Sent from my 710C using XDA Free mobile app
jaysoblitzed said:
You posted it without testing it but tested mine and ran into issues? If someone tried your file they might be in the same situation your in now.
I think you should flash the one you posted on top of the one I did the same way you did for this file.
But retry the RUU posted as I got the same thing in the bootloader when it says press power to reboot but when I did the phone booted up but I ran into a "setup wizard is not responding" error when it fully booted up. Flashed again and was fixed.
As I said flash the HTC file now available to fix any issues with startup as this RUU may contain the files/apps but the RUU you posted organizes the files/apps for the system in the correct manner I believe.
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
My file couldn't of hurt anyone's device, as I said, it wasn't even a flashable file. Your file is the one that has my phone not working. Your RUU WON'T flash, and as I stated the file I posted is not a RUU of any kind, I don't know why you insist on me flashing it.
FoxyDrew said:
My file couldn't of hurt anyone's device, as I said, it wasn't even a flashable file. Your file is the one that has my phone not working. Your RUU WON'T flash, and as I stated the file I posted is not a RUU of any kind, I don't know why you insist on me flashing it.
Click to expand...
Click to collapse
So you posted it and didn't even test it. You just assumed it would work for people?
Also, its not my file. It was put out there by a developer out in the world. I also used this to test on my device before uploading. I have no idea what you do/did with your device so I can't just try to recreate the issue your facing. I told you how I used it on mine and I was able to get it to work.
With any file you should be fully prepared and knowledgeable in what your using in the case an issue arrives. If CM bricked your device, you would be mad at the developer or yourself?
Your telling me its my files fault, yet your taking no responsibility for your actions. If you ran into an issue and me as the uploader stating explicitly that I have tested it and the methods I have used to get it to work what would you like me to do? I gave you the original source of the files so you could compare them to your leisure but its the exact same file.
The things your saying don't line up at all in short. I apologize if there was an issue with yours but mine works just as fine as day one after flashing the RUU. This RUU DOES flash just not in incapable hands it seems. Hopefully HTC will release an easier one to flash for anyone with difficulties.
Have you downloaded from the source as of yet?
Sent from my 710C using XDA Free mobile app
jaysoblitzed said:
So you posted it and didn't even test it. You just assumed it would work for people?
Also, its not my file. It was put out there by some developer out in the world. Which I also used to test on my device before uploading. I have no idea what you do/did with your device so I can't just try to recreate the issue your facing. I told you how I used it on mine and I was able to get it to work.
With any file you should be fully prepared and knowledgeable in what your using in the case an issue arrives. If CM bricked your device, you would be mad at the developer or yourself?
Your telling me its my files fault, yet your taking no responsibility for your actions. If you ran into an issue and me as the uploader stating explicitly that I have tested it and the methods I have used to get it to work what would you like me to do? I gave you the original source of the files so you could compare them to your leisure but its the exact same file.
The things your saying don't line up at all in short. I apologize if there was an issue with yours but mine works just as fine as day one after flashing the RUU.
This RUU DOES flash. Just not in incapable hands it seems. Hopefully HTC will release an easier one to flash for those with difficulties.
Have you downloaded from the source as of yet?
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
I wasn't calling you out because I thought it was your fault. You said I had uploaded a file without testing, when in reality your file is the only one to harm somones device, (wether it be your fault for uploading it or mine for flashing it) ,when my file couldn't hurt anyone. That's like saying if I claim a .jpg file is a Lollipop ROM it will brick people's phone.
I think my issue is deeper, my /data partition is clearly corrupted, as I can't format in recovery or through fastboot commands.
FoxyDrew said:
I wasn't calling you out because I thought it was your fault. You said I had uploaded a file without testing, when in reality your file is the only one to harm somones device, (wether it be your fault for uploading it or mine for flashing it) ,when my file couldn't hurt anyone. That's like saying if I claim a .jpg file is a Lollipop ROM it will brick people's phone.
I think my issue is deeper, my /data partition is clearly corrupted, as I can't format in recovery or through fastboot commands.
Click to expand...
Click to collapse
[Edited] So in short do you believe I uploaded something that could potentially harm a device when the device has specific security measures that will not allow certain actions to be taken?
[Deleted]
[Edited] Also, that's like saying I made the RUU myself. A great accomplish that would be only; If its supposed to be signed code ONLY FROM HTC that's accepted by the bootloader. If you try to put an UK RUU on your phone and its US it won't flash because of these signed codes and bootloader security measures.
[Deleted]
Sent from my 710C using XDA Free mobile app
jaysoblitzed said:
So in short your trying to make people believe I uploaded something that could potentially harm their device when the device has specific security measures that will not allow certain actions to be taken?
Also, your the only one with a complaint, and funny enough your the only one who has had an issue with me since I posted in CM a while back directing a comment to the developer and someone who was having an issue.
Also, that's like saying I made the RUU myself. A great accomplish that would be only; If its supposed to be signed code ONLY FROM HTC that's accepted by the bootloader how would I make an RUU or a "bad file"?
Tell me this. If you try to put an UK RUU on your phone and its US it won't flash. Do you know why? Do you know why this RUU works on this device and it won't work on any other device?
I suggest you keep your comments to yourself as I know you were hoping someone else would've posted this but never expected me to come across it first.
The things you've said thus far are enough to commit you to fraudulent claims so stop before you hurt yourself.
Its a link with a file bro.
Jealously is not in my persona.
& don't skip past half the stuff I said and comment on the points that made you "mad" because that is annoying.
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
This has nothing to do with any past issues between us get over yourself. My phone currently is 100% not working I could care less what you have to say I have not commited any fraudulent claims thus far but I'd love for you to try to prove I did somehow. I'd be perfectly fine with posting pictures/a video to show I am seriously having an issue with my device and your RUU is of no help. I skip things that you say that are childish and have no relation to the problem at hand.
Hi community
I have a Samsung Galaxy S7 SM-G930V with Android 7.0. I tried to get root but first I had to unlock bootloader. I flashed the "Engineer Bootloader" (a file named Samsung_G930x_QC_Rooted_BOOT.TAR) with Odin for engineering bootloader and no problem then the phone reboot. There comes the problem, the phone is on a bootloop, it shows the screen "Samsung Galaxy S7" and restart again, over and over.
People suggest to go to recovery mode and wipe data and factory reset, I already did that but it didn't work.
I'm sure that flash the complete ROM again will solve the problem but the ROM is 2.50 GB and my Internet connection is very very slow so I can't download it. Maybe flashing just the custom boot.img the problem gets solved, can somebody bring me just that file? Please I need it really much.
Thank you very much.
From the way the file name is written, it looks like the Marshmallow kernel, which is not the correct one for Nougat. Try flashing this in the AP slot in Odin. This is the correct root kernel for Nougat. The phone may bootloop a couple times after flashing this before completely booting.
Note: We are talking about engineering kernels, not bootloaders.
dude, THANK YOU VERY MUCH!!! you saved my life. I don't understand why people post tutorials with wrong files. THANK YOU VERY MUCH AGAIN.
CVertigo1 said:
From the way the file name is written, it looks like the Marshmallow kernel, which is not the correct one for Nougat. Try flashing this in the AP slot in Odin. This is the correct root kernel for Nougat. The phone may bootloop a couple times after flashing this before completely booting.
Note: We are talking about engineering kernels, not bootloaders.
Click to expand...
Click to collapse
Wow... I have searched high an low for this. Thank you.
CVertigo1 said:
From the way the file name is written, it looks like the Marshmallow kernel, which is not the correct one for Nougat. Try flashing this in the AP slot in Odin. This is the correct root kernel for Nougat. The phone may bootloop a couple times after flashing this before completely booting.
Note: We are talking about engineering kernels, not bootloaders.
Click to expand...
Click to collapse
Is there a version of this that's just stock, no root or special engineering version?
ItsKipz said:
Is there a version of this that's just stock, no root or special engineering version?
Click to expand...
Click to collapse
Hi I was just experimenting with the Verizon Recovery Utility tools on windows 10 on the computer and noticed it was temporary copying ALL BL, AP, CSC ext. Well I selected it and copied in another folder before it could erase the files when done flashing my S7 verizon back to stock. It worked! I got all the files straight from Verizon's official tool. Since windows will throw a error message to anything trying to delete files in use, when verizon tool tried to erase the temp stock files, it denied it since the file was in use by me. Aka copying to another folder as the verizon tool downloaded the files I was right there copying the files mid download and the computer let the files finish download complete and it ended up being I got the files. Im proud of myself. Lol! Being new at this.
So someone just tell me what I do to get you all a copy. They are the most current stock files from verizon. I uploaded them all into Onedrive already so files are safe just waiting for the moment someone needs them and tells me how to upload them. I see androidhostfile or something site. Can I use that one? Even though Im new at this?
Here is my screen shot of my new files.
Scottie32583 said:
Hi I was just experimenting with the Verizon Recovery Utility tools on windows 10 on the computer and noticed it was temporary copying ALL BL, AP, CSC ext. Well I selected it and copied in another folder before it could erase the files when done flashing my S7 verizon back to stock. It worked! I got all the files straight from Verizon's official tool. Since windows will throw a error message to anything trying to delete files in use, when verizon tool tried to erase the temp stock files, it denied it since the file was in use by me. Aka copying to another folder as the verizon tool downloaded the files I was right there copying the files mid download and the computer let the files finish download complete and it ended up being I got the files. Im proud of myself. Lol! Being new at this.
So someone just tell me what I do to get you all a copy. They are the most current stock files from verizon. I uploaded them all into Onedrive already so files are safe just waiting for the moment someone needs them and tells me how to upload them. I see androidhostfile or something site. Can I use that one? Even though Im new at this?
Here is my screen shot of my new files.
Click to expand...
Click to collapse
This is what the file looks like I have...
Hi everybody,
yesterday I found this news:
https://www.sammobile.com/2017/10/16/galaxy-j3-2016-android-7-1-1-nougat-update-released-att/
Here the official page:
https://www.att.com/devicehowto/tut...tep_KM1147672?make=Samsung&model=GalaxyJ32016
I googling for a bit and I found the file of that update, those 4 file are tar.md5 and it's possible to use them by odin. Unfortunate when odin try to install the new system it show this error: Rev. system incorrect magic string (or something very similar)
I extrac those file and try to install separately any img or bin partition using heimdall in ubuntu, but again system and sboot image give me this error: ERROR: Failed to confirm end of file transfer sequence!
I don't know why, considering that my phone it's exactly the model, it suppose to be easy install those file.
Anyone already try to install that update or someone can give me some advice about those error?
I really like to see my phone with nougat running and this lñooks like the best chance.
Hope someone can help with that.
Thanks
Root isn't working atm, not sure if it will without unlocking either. But it is downgradable back to mm... I only have the update.zip, ill upload it in a bit.
Where's the 4 files? I couldn't find it
DamienMc said:
Root isn't working atm, not sure if it will without unlocking either. But it is downgradable back to mm... I only have the update.zip, ill upload it in a bit.
Where's the 4 files? I couldn't find it
Click to expand...
Click to collapse
Hi @DamienMc, here a couple of link where find those filehope I can post those link without breaking any rules, if i do sorry and tell me please)
http://gsm-firmware.com/index.php?a=browse&b=category&id=10851 (paid)
https://androidfilehost.com/?fid=962021903579486981
I found the first link in the beginning so I've downloaded from there.
What do you mean with "Root isn't working atm"?
My phone it's already unlocked carrier. Witch version of android do you have for that update.zip?
The best I did was flashing the recovery, boot, param partition using the pit file inside of one of those 4 files. There also a folder with foto.zip file, but I can't use it for now.
Please let me know any ideas about how to flash that update.
I posted it here https://forum.xda-developers.com/galaxy-j3-2016/development/odin-j320a-j320az-links-t3631914
It's the ota zip, edited by me. You need to be rooted and use flashfire. My edits unroot your device then the original update takes over. Pita but that's all I have. I'll look at the full firmware or try to pull it from Samsung again.
But yeah, I wasn't able to root the thing. Haven't given up yet tho
@Iurop
Full firmware installed just fine here (besides an eof error on AP, prolly cause of the fota.zip)... are you sure you're not j320ag?
A and AZ have the same magic string, but AG is different. And can't crossflash with Odin.
@DamienMc
You right my it's a J320AG I was hoping that the firmware works fine for me, but my knowledge for now it's not enough to figured out how to flash those file. Do you know if there's any chance to do it in some way?
I will try your update.zip. In case you work around those nougat file and figured out how to use it on j320ag let me know.
Thanks.
I am afraid your stuck until you get the official update.
While your device can use the same system files here, it cannot use the kernel. And a new kernel is required for nougat.
On top of that your device is now two updates behind the j320a.
Here a couple of screenshot of the firmware version I had right now.
I don't know if Samsung will update this phone to nougat. Will be great.
After flashing the version of your update.zip and make the update, witch version of firmware will be present?
Flashing my phone with a at&t version of the firmware can help in some ways? Or at&t only manage J320A and AZ?
Thanks anyway.
AG = AQB1
AZ = AQG1
A = BQI5
The update.zip is BQI5.
Your best chance would be to try and dd the firmware you posted to see if it boots. I know i tried the system.img, not sure if I did the whole thing. Super dangerous tho...or just wait it out
[EDIT]
After further thought, a real rom.zip might just work on AG...a good test could be to boot a stock boot.img from A or AZ. Won't be 100%, but it'll be a good indication.
Or run it thru kitchen and try it out, if not I'll get to it when I have spare time
[/EDIT]
DamienMc said:
AG = AQB1
AZ = AQG1
A = BQI5
The update.zip is BQI5.
Your best chance would be to try and dd the firmware you posted to see if it boots. I know i tried the system.img, not sure if I did the whole thing. Super dangerous tho...or just wait it out
[EDIT]
After further thought, a real rom.zip might just work on AG...a good test could be to boot a stock boot.img from A or AZ. Won't be 100%, but it'll be a good indication.
Or run it thru kitchen and try it out, if not I'll get to it when I have spare time
[/EDIT]
Click to expand...
Click to collapse
@DamienMc, here what I've try until now:
-try to flash boot.img from this stock rom J320AZTUS3AQG1 using PIT file from my versios AG and also using PIT file from AZ version = can't be flashed in any ways.
-flash boot.img from J320A_J320AUCU3BQI5_AT&T_USA_7.1.1 using my PIT file = flashed but after the reboot hang on J3 logo
I don't understand what do yopu mean with "Or run it thru kitchen and try it out", can you explain please?
Also I don't know if Samsung release an update to Nougat for all J320 or it just the AT&T carier to do it. For that reason I've been trying to flash.
@Iurop
Well its good it doesnt fail with 7.1.1 boot....hopefully we can get it going.
I suggested that you create a rom.zip from the system.img a kitchen. But it wasnt that simple, i think i have a working zip now but cannot test it until later...i will pass it to you when its ready
I've probably messed this thing up just about as badly as I can.
Here's what I can tell you:
Update: I just figured out that you are supposed to put dload onto a separate sd card, So i'll be trying that when the phone comes out of it's coma XD anything else you can suggest is very welcome.
- The phone currently isn't turning on after messing around in twrp(tried to restart into bootloader)
- While trying to get it working, it is now showing up as CAN-L11(likely from trying some backups of others)
- I was unable to use ANY roms I tried. full update files didn't work. always error 7
- It seems in twrp that I'd often get this error: mountencrypt failed to mount /data, despite wiping /data many times
- I've tried using iso files extracted from some update.app, and using that to get system and data on there, as well as recovery too
- I was switching between twrp and default recovery to transfer files and then use dload to try to recover the system, never let me do it though. got to 5% then told me something like: "Getting package info failed". it would do this in the download and recover mode as well when I would hook up to the internet and it would also give me that error.
You are free to ask me any questions about the device.
I think I just need to drain the battery then I should be able to at least get something out of it, but until then, if anyone has any recommendations after it's functional again let me know. Any help is appreciated.
TheProgrammerEX said:
I've probably messed this thing up just about as badly as I can.
Here's what I can tell you:
- The phone currently isn't turning on after messing around in twrp(tried to restart into bootloader)
Click to expand...
Click to collapse
It isn't even charging?
- While trying to get it working, it is now showing up as CAN-L11(likely from trying some backups of others)
Click to expand...
Click to collapse
Yeah, that's why. The model name can be changed in build.prop, but you're still using a CAN-L11 ROM though.
- I was unable to use ANY roms I tried. full update files didn't work. always error 7
Click to expand...
Click to collapse
You haven't flashed the TWRP mentioned in the first post of their thread, hence you've got that error which is basically telling you that you're trying to flash the ROM on an unsupported device (the phone's codename / model is mentioned in TWRP and ROM checks for it), but actually it's working on all models.
- It seems in twrp that I'd often get this error: mountencrypt failed to mount /data, despite wiping /data many times
Click to expand...
Click to collapse
That occurs because TWRP doesn't support decryption. You have to format data, not wipe. You can format it from TWRP > Wipe > Format data.
- I've tried using iso files extracted from some update.app, and using that to get system and data on there, as well as recovery too
Click to expand...
Click to collapse
What happened after you've tried that?
- I was switching between twrp and default recovery to transfer files and then use dload to try to recover the system, never let me do it though. got to 5% then told me something like: "Getting package info failed". it would do this in the download and recover mode as well when I would hook up to the internet and it would also give me that error.
Click to expand...
Click to collapse
Try to unplug the cable from PC. Also, note that I've read in past somewhere that the firmwares from Firmware Finder has to be approved by Huawei and if it isn't, then the stock recovery will fail to flash it. Other Huawei phones has modified / patched stock recovery which allows to flash unapproved firmwares though.
You are free to ask me any questions about the device.
Click to expand...
Click to collapse
How do you guys end up like this? xD
Update: I just figured out that you are supposed to put dload onto a separate sd card, So i'll be trying that when the phone comes out of it's coma XD anything else you can suggest is very welcome.
Click to expand...
Click to collapse
Hah, here's the answer to the above question: not reading xD. Try to slap the phone to wake it from the coma ahahahah xD. When did it get into coma though?