Just a fair warning, I've had to return two new Axon 10 Pros because the EDL tool caused bootloops when trying to unlock. I took every possible backup and on both phones and had OEM Unlock enabled in the Developer settings. I was unable to restore back to the original state by restoring from backup. This is not a knock on UnjustifiedDev, I'm just sharing my own personal experience, and from the look of a lot of recent posts others have the same issue. It may be an issue with the latest patch (both phones were up to date before attempting unlock). The other issue is that there's no reliable North American EDL backup that works with bricked phone restore tools like MiFlash, so you end up having to us the only known good one which is the EU G variant, which is less than ideal for NA phones. Luckily the place I bought them from had liberal return policies.
Agree it's risky to use at the moment, but it does seem that there's a solution to a common source of the bootloop problem . It is discussed in the main tool thread, but to shorten it - if you're bootlooped and you have a stock backup, put the phone into the BL / fastboot mode and flash a/b stock bootloaders and a/b boot images.
Still, good for people to know it's not perfect... I spent a lot of time I didn't plan for figuring out how to get out of being stuck in EDL mode (which is worse than the bootloop).
I've been stuck on the EU rom for months. It sucks. ? Wish there was a way to fix it. I did flash something(can't remember what it was off the top of my head) and I got my service back but I lost the fingerprint scanner.
ufo8mymunky said:
I've been stuck on the EU rom for months. It sucks. Wish there was a way to fix it. I did flash something(can't remember what it was off the top of my head) and I got my service back but I lost the fingerprint scanner.
Click to expand...
Click to collapse
If you have your original backups, what happens when you flashed them back on via the EDL tool?
If you feel comfortable experimenting a little, I can suggest some things to try.
bobthenormal said:
If you have your original backups, what happens when you flashed them back on via the EDL tool?
If you feel comfortable experimenting a little, I can suggest some things to try.
Click to expand...
Click to collapse
I do not have my original back ups. They did not work to fix the issue anyway. I messed up somewhere when I was originally correcting the bootloop issue and I was getting a corrupt error as soon as the phone was booted. The only thing that fixed my phone was the European rom so I've just been making it work for almost 3 months.
ufo8mymunky said:
I do not have my original back ups. They did not work to fix the issue anyway. I messed up somewhere when I was originally correcting the bootloop issue and I was getting a corrupt error as soon as the phone was booted. The only thing that fixed my phone was the European rom so I've just been making it work for almost 3 months.
Click to expand...
Click to collapse
Did you try @rafyvitto 's EDL backup? I haven't tried flashing the EU ROM, but
If you're running Win10 I can send you some powershell scripts I've made, they'll collect information you can paste back here and I can use to make a suggestion on fixing it.
From what I've seen the problems (for me) come from a mismatch of various pieces of the firmware., so I'd have to identify if you're working with something I can fix. The EDL backup won't have all the files but the other files shouldn't really change.
bobthenormal said:
Did you try @rafyvitto 's EDL backup? I haven't tried flashing the EU ROM, but
If you're running Win10 I can send you some powershell scripts I've made, they'll collect information you can paste back here and I can use to make a suggestion on fixing it.
From what I've seen the problems (for me) come from a mismatch of various pieces of the firmware., so I'd have to identify if you're working with something I can fix. The EDL backup won't have all the files but the other files shouldn't really change.
Click to expand...
Click to collapse
Yes I tried it. I believe it was after I had the EU rom installed. It also said that my device was corrupt on boot. I do have Windows 10. I downloaded what I had thought was someone else's (not sure of the name off the top of my head) but they had said they modified some of that rom to get their phone back up and running. I downloaded their version and visually it looked the same, so idk. I can't get miflash to work on my laptop so I can't go that route either.
Attach the powershell script and let me know whatcha need. Thank you for helping me with this btw.
ufo8mymunky said:
Yes I tried it. I believe it was after I had the EU rom installed. It also said that my device was corrupt on boot. I do have Windows 10. I downloaded what I had thought was someone else's (not sure of the name off the top of my head) but they had said they modified some of that rom to get their phone back up and running. I downloaded their version and visually it looked the same, so idk. I can't get miflash to work on my laptop so I can't go that route either.
Attach the powershell script and let me know whatcha need. Thank you for helping me with this btw.
Click to expand...
Click to collapse
Happy to try to help :good: I'll think about it a bit and post up some instructions and script tomorrow, have to make sure I think through what all I need to check.
bobthenormal said:
Happy to try to help :good: I'll think about it a bit and post up some instructions and script tomorrow, have to make sure I think through what all I need to check.
Click to expand...
Click to collapse
Awesome. No rush. It would be nice to solve this issue since there are a few of us still stuck on the European rom and we have no idea how to get back to the US rom. Thank you.
So, I was messing around with the edl tool and I was finally able to unlock my bootloader. IDK if that changes anything. I would assume if I tried to install twrp and flash a rom it would still be stuck on the European variant or I'd mess everything up again and have to start off all over again. Idk
ufo8mymunky said:
So, I was messing around with the edl tool and I was finally able to unlock my bootloader. IDK if that changes anything. I would assume if I tried to install twrp and flash a rom it would still be stuck on the European variant or I'd mess everything up again and have to start off all over again. Idk
Click to expand...
Click to collapse
With it unlocked you might have an easier time with not bricking, but it still happens a lot even to me... I've been trying to put together a "bulletproof" EDL backup that other people can download and for sure work no matter what, I've probably had to unbrick my phone 4-5 times the last two days. Fairly straightforward process for me now, but still running into some surprises. Like today I'm bricked again... I was kinda pushing for it... long story... but I'll probably get it unbricked in a few hours. I'm just doing it very slowly to try to identify the culprit causing it.
Point being - make sure to do lots of backups when you're messing around with anything. The usefulness of the EDL tool's backup goes far beyond what you can do in the tool - it has a limited capacity to unbrick you just by applying EDL backups, even the EU version might not work anymore if you get the right conditions set up. But with good backups I could still fix it.
Well, with one caveat - you need to fix a typo in the EDL tool's "all.xml" file first, otherwise it misses a very important file. I'll get to that in the instructions I'm about to post...
---------- Post added at 09:49 PM ---------- Previous post was at 09:47 PM ----------
Alright, first thing of course this isn't my job or anything and my knowledge is very limited, just another person figuring it out - so although I'm trying to help this is all AT YOUR OWN RISK.
First - fix the typo - go to your EDL tool directory, and in the "tools" subdirectory there is a file named "all.xml". Edit the file in notepad. Do not accidentally change ANYTHING except what I say. Find the line where it says 'label="aop_b"'. Before that it will say 'filename="aop.mbn"'. Change aop.mbn to aop_b.mbn.
EDIT: Well, I found another one just in the time since I posted this haha. It's less critical (why I didn't notice it). But there's a line with 'label="uefisecapp_b"'. Add the "_b" to the filename in front of that too!
That just fixes a small typo that whenever the ALL backup was run it would overwrite the first backup (aop_a) with the second (aop_b). A FULL backup did not have this issue, but it would only backup the aop_a and not aop_b.
As it turns out.. a bad AOP file will stop the bootloader from loading. (ie. EDL loop)
Anyway, next do these:
1) With your current, working EU ROM boot into EDL
2) Run an ALL backup in the EDL tool (with fixed all.xml)
3) Move that "ALL" backup to another folder (preferably name/dated)
4) Save this code as a powershell script file and run it in the backup directory:
Code:
# Creates a hash log of all files in this directory
$backupLocations = ,@(
(Get-Item ".\")
)
# Define a maximum file size to use hashing to compare (in MB)
$maxHashCheckFilesize = 1000000
# Clear variables
$hashValues = $null
$fileList = $null
### Get Hashes
foreach ($loc in $backupLocations) {
Write-Host ("-- Hash Location: " + $loc)
$literalLocName = ("\\?\" + $loc.FullName + "\")
$fileList += @{ ($loc.FullName) = (gci -Force -File -LiteralPath $literalLocName) }
$hashValues += @{ ($loc.FullName) = $null }
foreach ($file in ($fileList[$loc.FullName]) ) {
if ( $file.Length -gt ($maxHashCheckFilesize*1024*1024) ) {
Write-Host ("Skipping " + $file.Name)
$hashValues[$loc.FullName] += @{ $file.FullName = "Skipped (file size over max)" }
}
else {
$literalFileName = ($file.FullName)
Write-Host ("Hashing " + $file.Name)
$hashValues[$loc.FullName] += @{ $file.FullName = (Get-FileHash -LiteralPath $literalFileName).Hash }
}
}
}
Write-Host "Finished Hashing Files"
### Build Data Output
# If statement to turn XML output on and off
if ( $false ) {
$saveXML = (".\" + $saveName + " " + (Get-Date -Format "(MM-dd-yy hhmmss)") + ".data")
Export-Clixml -InputObject $data -Path $saveXML
Write-Host "Finished XML Export"
}
# If statement to turn hash data output on and off
if ( $true ) {
Set-Content -Value ( "Hashes for directory: ", ($backupLocation.FullName) ) -Path ($hashPath = (".\" + "Hash File Results- " + (Get-Date -Format "(MM-dd-yy HHmmss)") + ".txt"))
foreach ($loc in $backupLocations) {
Add-Content -Value ( "Hash Location: ", ($loc.FullName + "\") ) -Path ($hashPath)
if(($fileList[$loc.FullName]).Length -eq 0 ) {
Add-Content -Value ( "No files" ) -Path ($hashPath)
}
else {
foreach ($file in $fileList[$loc.FullName]) {
Add-Content -Value (($hashValues[$loc.FullName][$file.FullName] | % { $file.Name, (" Last Write: " + $file.LastWriteTime), $_ })) -Path ($hashPath)
}
}
}
Write-Host "Finished Hash Output"
}
Pause
5) Go to the A2020U backup that you are trying to apply (which you can't get to boot) and run the hash script there.
Send me those two hash lists.
If you want to try installing the backup now that you have the BL unlocked, you might be successful. The error you mentioned before about something being corrupt - that warning is because the BL was locked and detected tampering. So that should, at least, not be your problem.
I would guess is you get stuck in a loop, either boot or EDL. But you're welcome to try, it might just work. I've had success booting from the EDL backup @rafyvitto posted. There's a -chance- that doing this gets you stuck to where even trying to re-apply the EU firmware won't work. But it's less likely, and if you have your backup from above you should be able to get out.. eventually.. it just might require some number of days for me to help do that.
bobthenormal said:
With it unlocked you might have an easier time with not bricking, but it still happens a lot even to me... I've been trying to put together a "bulletproof" EDL backup that other people can download and for sure work no matter what, I've probably had to unbrick my phone 4-5 times the last two days. Fairly straightforward process for me now, but still running into some surprises. Like today I'm bricked again... I was kinda pushing for it... long story... but I'll probably get it unbricked in a few hours. I'm just doing it very slowly to try to identify the culprit causing it.
Point being - make sure to do lots of backups when you're messing around with anything. The usefulness of the EDL tool's backup goes far beyond what you can do in the tool - it has a limited capacity to unbrick you just by applying EDL backups, even the EU version might not work anymore if you get the right conditions set up. But with good backups I could still fix it.
Well, with one caveat - you need to fix a typo in the EDL tool's "all.xml" file first, otherwise it misses a very important file. I'll get to that in the instructions I'm about to post...
---------- Post added at 09:49 PM ---------- Previous post was at 09:47 PM ----------
Alright, first thing of course this isn't my job or anything and my knowledge is very limited, just another person figuring it out - so although I'm trying to help this is all AT YOUR OWN RISK.
First - fix the typo - go to your EDL tool directory, and in the "tools" subdirectory there is a file named "all.xml". Edit the file in notepad. Do not accidentally change ANYTHING except what I say. Find the line where it says 'label="aop_b"'. Before that it will say 'filename="aop.elf"'. Change aop.elf to aop_b.elf.
EDIT: Well, I found another one just in the time since I posted this haha. It's less critical (why I didn't notice it). But there's a line with 'label="uefisecapp_b"'. Add the "_b" to the filename in front of that too!
That just fixes a small typo that whenever the ALL backup was run it would overwrite the first backup (aop_a) with the second (aop_b). A FULL backup did not have this issue, but it would only backup the aop_a and not aop_b.
As it turns out.. a bad AOP file will stop the bootloader from loading. (ie. EDL loop)
Anyway, next do these:
1) With your current, working EU ROM boot into EDL
2) Run an ALL backup in the EDL tool (with fixed all.xml)
3) Move that "ALL" backup to another folder (preferably name/dated)
4) Save this code as a powershell script file and run it in the backup directory:
Code:
# Creates a hash log of all files in this directory
$backupLocations = ,@(
(Get-Item ".\")
)
# Define a maximum file size to use hashing to compare (in MB)
$maxHashCheckFilesize = 1000000
# Clear variables
$hashValues = $null
$fileList = $null
### Get Hashes
foreach ($loc in $backupLocations) {
Write-Host ("-- Hash Location: " + $loc)
$literalLocName = ("\\?\" + $loc.FullName + "\")
$fileList += @{ ($loc.FullName) = (gci -Force -File -LiteralPath $literalLocName) }
$hashValues += @{ ($loc.FullName) = $null }
foreach ($file in ($fileList[$loc.FullName]) ) {
if ( $file.Length -gt ($maxHashCheckFilesize*1024*1024) ) {
Write-Host ("Skipping " + $file.Name)
$hashValues[$loc.FullName] += @{ $file.FullName = "Skipped (file size over max)" }
}
else {
$literalFileName = ($file.FullName)
Write-Host ("Hashing " + $file.Name)
$hashValues[$loc.FullName] += @{ $file.FullName = (Get-FileHash -LiteralPath $literalFileName).Hash }
}
}
}
Write-Host "Finished Hashing Files"
### Build Data Output
# If statement to turn XML output on and off
if ( $false ) {
$saveXML = (".\" + $saveName + " " + (Get-Date -Format "(MM-dd-yy hhmmss)") + ".data")
Export-Clixml -InputObject $data -Path $saveXML
Write-Host "Finished XML Export"
}
# If statement to turn hash data output on and off
if ( $true ) {
Set-Content -Value ( "Hashes for directory: ", ($backupLocation.FullName) ) -Path ($hashPath = (".\" + "Hash File Results- " + (Get-Date -Format "(MM-dd-yy HHmmss)") + ".txt"))
foreach ($loc in $backupLocations) {
Add-Content -Value ( "Hash Location: ", ($loc.FullName + "\") ) -Path ($hashPath)
if(($fileList[$loc.FullName]).Length -eq 0 ) {
Add-Content -Value ( "No files" ) -Path ($hashPath)
}
else {
foreach ($file in $fileList[$loc.FullName]) {
Add-Content -Value (($hashValues[$loc.FullName][$file.FullName] | % { $file.Name, (" Last Write: " + $file.LastWriteTime), $_ })) -Path ($hashPath)
}
}
}
Write-Host "Finished Hash Output"
}
Pause
5) Go to the A2020U backup that you are trying to apply (which you can't get to boot) and run the hash script there.
Send me those two hash lists.
If you want to try installing the backup now that you have the BL unlocked, you might be successful. The error you mentioned before about something being corrupt - that warning is because the BL was locked and detected tampering. So that should, at least, not be your problem.
I would guess is you get stuck in a loop, either boot or EDL. But you're welcome to try, it might just work. I've had success booting from the EDL backup @rafyvitto posted. There's a -chance- that doing this gets you stuck to where even trying to re-apply the EU firmware won't work. But it's less likely, and if you have your backup from above you should be able to get out.. eventually.. it just might require some number of days for me to help do that.
Click to expand...
Click to collapse
I will work on that in a few hours. It's currently 6:30am here and I need to wake up a bit more. Yesterday, after unlocking the bootloader, I was able to install TWRP. It didn't go so well because I ended up getting excited and I tried to flash lineage but that resulted in boot loops. I tried flashing the EU rom and it boot looped also. I had to flash the same rom like three times to get it to work. IDK why. My backups never restore with the tool and that may be because of the typos. Hopefully we can get to the bottom of this because I really miss my fingerprint scanner. Lol
ufo8mymunky said:
I will work on that in a few hours. It's currently 6:30am here and I need to wake up a bit more. Yesterday, after unlocking the bootloader, I was able to install TWRP. It didn't go so well because I ended up getting excited and I tried to flash lineage but that resulted in boot loops. I tried flashing the EU rom and it boot looped also. I had to flash the same rom like three times to get it to work. IDK why. My backups never restore with the tool and that may be because of the typos. Hopefully we can get to the bottom of this because I really miss my fingerprint scanner. Lol
Click to expand...
Click to collapse
TBH Don't even try with the LOS builds yet! lol.. I'll let you know if I figure out how to successfully flash them... they are definitely a lot more difficult to get up and running versus a stock TWRP/magisk build... ultimately LOS is my goal too, or a GSI like Havok... I hate stock ****. Just trying to get to a place where my installing it and getting it working isn't like balancing a house of cards.
I think maybe the LOS install must assume/rely on a certain conditions that I haven't yet hit upon. Once I have a set of backups that I know I can *for sure* flash to get myself to any specific firmware build#, I'll try going through each one and installing until it works. In the mean time flashing LOS seems like just an absolutely guaranteed way to brick my phone...
bobthenormal said:
...
First - fix the typo - go to your EDL tool directory, and in the "tools" subdirectory there is a file named "all.xml". Edit the file in notepad. Do not accidentally change ANYTHING except what I say. Find the line where it says 'label="aop_b"'. Before that it will say 'filename="aop.elf"'. Change aop.elf to aop_b.elf.
EDIT: Well, I found another one just in the time since I posted this haha. It's less critical (why I didn't notice it). But there's a line with 'label="uefisecapp_b"'. Add the "_b" to the filename in front of that too!
That just fixes a small typo that whenever the ALL backup was run it would overwrite the first backup (aop_a) with the second (aop_b). A FULL backup did not have this issue, but it would only backup the aop_a and not aop_b.
As it turns out.. a bad AOP file will stop the bootloader from loading. (ie. EDL loop)
...
Click to expand...
Click to collapse
Thanks for your write-up. However, for both "aop" and "uefisecapp", did you mean the ".mbn" rather than ".elf"?
Also, during my search I noted what seems to be the same issue with "abl". Should we also update the "abl.elf" to "abl_b.elf" in the line with "label="abl_b"?
Thanks
I have attached those hash files. I actually fixed my phone while messing around again. I used a payload dumper to extract the images from the SD installable rom on ZTE's site and I copied and pasted them into the european 1.6 full edl file. I made sure to grab the non_hlos.bin file from the B12 full and then I flashed away. I am now back to normal functionality. I think the issue was that I tried to unlock my bootloader and all that nonsense when I was on android 10. I'm not sure why the european rom worked because it was android 9 but every time I flashed anything other than the A2020G 1.6, it would bootloop. Either way, I'm back on A2020U and I don't even care if I'm stuck with Android 10 because at least all my stuff works again.
eKeith said:
Thanks for your write-up. However, for both "aop" and "uefisecapp", did you mean the ".mbn" rather than ".elf"?
Also, during my search I noted what seems to be the same issue with "abl". Should we also update the "abl.elf" to "abl_b.elf" in the line with "label="abl_b"?
Thanks
Click to expand...
Click to collapse
I assumed he meant .mbn. I'm not sure if it worked properly or not.
---------- Post added at 12:53 PM ---------- Previous post was at 12:49 PM ----------
bobthenormal said:
TBH Don't even try with the LOS builds yet! lol.. I'll let you know if I figure out how to successfully flash them... they are definitely a lot more difficult to get up and running versus a stock TWRP/magisk build... ultimately LOS is my goal too, or a GSI like Havok... I hate stock ****. Just trying to get to a place where my installing it and getting it working isn't like balancing a house of cards.
I think maybe the LOS install must assume/rely on a certain conditions that I haven't yet hit upon. Once I have a set of backups that I know I can *for sure* flash to get myself to any specific firmware build#, I'll try going through each one and installing until it works. In the mean time flashing LOS seems like just an absolutely guaranteed way to brick my phone...
Click to expand...
Click to collapse
Oh I just now saw this. Im back on Android 10 but I attached those hash files to my other message. I tried flashing lineage before fixing my phone but it always ended in boot loops. I'm so glad its working again though
eKeith said:
Thanks for your write-up. However, for both "aop" and "uefisecapp", did you mean the ".mbn" rather than ".elf"?
Also, during my search I noted what seems to be the same issue with "abl". Should we also update the "abl.elf" to "abl_b.elf" in the line with "label="abl_b"?
Thanks
Click to expand...
Click to collapse
Oh thanks! I'll edit my post regarding the ".elf" / ".mbn" stuff....
I've mostly lost track of the extension names. They don't really matter for anymore (for me) because as long as I use the same XML to restore/backup it's fine. As long as none of the files are named the same (= overwriting).
EDIT: Be careful here - I did go back and check, in my version of the EDL Tool (3.2.5) there were no more typos than the two - the abl and abl_b filenames are correct. Make SURE if you're fixing it it's actually the on the line with label="abl_b". Maybe an older version of the tool had a problem with that?
As for yours having the abl_b overwrite - YES fix that. I'm a little surprised? Mine for sure didn't have that because my first backups definitely have abl and abl_b... Maybe I'll go unzip the EDL tool again and make sure I look at the true original.
Make absolutely sure the label on the line you're correcting is in fact abl_b though!
---------- Post added at 09:19 PM ---------- Previous post was at 08:40 PM ----------
ufo8mymunky said:
I have attached those hash files. I actually fixed my phone while messing around again. I used a payload dumper to extract the images from the SD installable rom on ZTE's site and I copied and pasted them into the european 1.6 full edl file. I made sure to grab the non_hlos.bin file from the B12 full and then I flashed away. I am now back to normal functionality. I think the issue was that I tried to unlock my bootloader and all that nonsense when I was on android 10. I'm not sure why the european rom worked because it was android 9 but every time I flashed anything other than the A2020G 1.6, it would bootloop. Either way, I'm back on A2020U and I don't even care if I'm stuck with Android 10 because at least all my stuff works again.
Click to expand...
Click to collapse
Nice! Glad to hear you're happy with things. After a few reboots do an "all" backup! I've noticed that there's an issue that the B-Partition can be absolutely unbootable junk and just sitting in the background waiting to screw things up when you try to do anything like custom ROMs or TWRP/Magisk. If anything goes wrong with the flashing on A there isn't really a fallback, unless you have your backup.
As for making sense of your situation - were you using the EDL tool to restore the EU ROM? Because if you were using another tool like MiFlash or QPST, those do a few extra things that the EDL tool doesn't when flashing that might have made the difference. (I haven't tried the EU ROM)
You make it sounds like after you flashed the EU ROM you were still on A10 btw? Maybe just reading that wrong... any of the "all" A9 ROMs should have reverted you to A9. The reason they bootlooped wasn't to do with A10->A9 if they were full ROMs. Could be a number of other issues.. one of which could be if they were from an unlocked bootloader and therefore incompatible with your locked state. The EU ROM being official would definitely work with a locked AND unlocked state - hence why everyone seems to fall back on it.
That's why I'm trying to put together a "locked" state ROM from my own stuff, it would be a safe fallback I could use anytime anything goes wrong. And of course then anyone here could use it too, to get back to A2020U. It is proving extremely difficult! Well... I guess I do have one but I'm still poking at it because I still don't understand why my original stock image doesn't work as a fallback, that bugs me.
bobthenormal said:
Oh thanks! I'll edit my post regarding the ".elf" / ".mbn" stuff....
I've mostly lost track of the extension names. They don't really matter for anymore (for me) because as long as I use the same XML to restore/backup it's fine. As long as none of the files are named the same (= overwriting).
EDIT: Be careful here - I did go back and check, in my version of the EDL Tool (3.2.5) there were no more typos than the two - the abl and abl_b filenames are correct. Make SURE if you're fixing it it's actually the on the line with label="abl_b". Maybe an older version of the tool had a problem with that?
As for yours having the abl_b overwrite - YES fix that. I'm a little surprised? Mine for sure didn't have that because my first backups definitely have abl and abl_b... Maybe I'll go unzip the EDL tool again and make sure I look at the true original.
Make absolutely sure the label on the line you're correcting is in fact abl_b though!
---------- Post added at 09:19 PM ---------- Previous post was at 08:40 PM ----------
Nice! Glad to hear you're happy with things. After a few reboots do an "all" backup! I've noticed that there's an issue that the B-Partition can be absolutely unbootable junk and just sitting in the background waiting to screw things up when you try to do anything like custom ROMs or TWRP/Magisk. If anything goes wrong with the flashing on A there isn't really a fallback, unless you have your backup.
As for making sense of your situation - were you using the EDL tool to restore the EU ROM? Because if you were using another tool like MiFlash or QPST, those do a few extra things that the EDL tool doesn't when flashing that might have made the difference. (I haven't tried the EU ROM)
You make it sounds like after you flashed the EU ROM you were still on A10 btw? Maybe just reading that wrong... any of the "all" A9 ROMs should have reverted you to A9. The reason they bootlooped wasn't to do with A10->A9 if they were full ROMs. Could be a number of other issues.. one of which could be if they were from an unlocked bootloader and therefore incompatible with your locked state. The EU ROM being official would definitely work with a locked AND unlocked state - hence why everyone seems to fall back on it.
That's why I'm trying to put together a "locked" state ROM from my own stuff, it would be a safe fallback I could use anytime anything goes wrong. And of course then anyone here could use it too, to get back to A2020U. It is proving extremely difficult! Well... I guess I do have one but I'm still poking at it because I still don't understand why my original stock image doesn't work as a fallback, that bugs me.
Click to expand...
Click to collapse
Thanks for your comprehensive response! Unfortunately it seems that I sent you too far down the rabbit hole...
I am on stock A10 and unrooted. My current goal is to make the best possible backups before I go further.
I reinstalled the Tool on another device and did not see the "able" typo! I must have confused myself! I did correct the other two.
I successfully unlocked the bootloader and made all backups capable with the tool.
My next goal is to root. I took the boot.img backed up by the tool, transferred it to my device and patched with Magisk. I have transferred the patched boot image back to my PC. But don't know how to get to fastboot. I understand that I can flash the patched image with the tool but prefer to understand by executing via CLI. I know this is off-topic for this thread, but can you direct me to information on getting the device into fastboot mode?
Thanks!
Sent from my PH-1 using Tapatalk
---------- Post added at 01:00 AM ---------- Previous post was at 12:57 AM ----------
ufo8mymunky said:
I have attached those hash files. I actually fixed my phone while messing around again. I used a payload dumper to extract the images from the SD installable rom on ZTE's site and I copied and pasted them into the european 1.6 full edl file. I made sure to grab the non_hlos.bin file from the B12 full and then I flashed away. I am now back to normal functionality. I think the issue was that I tried to unlock my bootloader and all that nonsense when I was on android 10. I'm not sure why the european rom worked because it was android 9 but every time I flashed anything other than the A2020G 1.6, it would bootloop. Either way, I'm back on A2020U and I don't even care if I'm stuck with Android 10 because at least all my stuff works again.
Click to expand...
Click to collapse
Can you direct me to info on that "payload dumper"?
Sent from my PH-1 using Tapatalk
eKeith said:
Thanks for your comprehensive response! Unfortunately it seems that I sent you too far down the rabbit hole...
I am on stock A10 and unrooted. My current goal is to make the best possible backups before I go further.
I reinstalled the Tool on another device and did not see the "able" typo! I must have confused myself! I did correct the other two.
I successfully unlocked the bootloader and made all backups capable with the tool.
My next goal is to root. I took the boot.img backed up by the tool, transferred it to my device and patched with Magisk. I have transferred the patched boot image back to my PC. But don't know how to get to fastboot. I understand that I can flash the patched image with the tool but prefer to understand by executing via CLI. I know this is off-topic for this thread, but can you direct me to information on getting the device into fastboot mode?
Thanks!
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
If you used the EDL tool to unlock the bootloader it will have installed a bootloader with fastboot enabled. Unplug the phone and restart while holding vol+/-, once the bootloader menu is up plug the phone back in and use fastboot.
bobthenormal said:
If you used the EDL tool to unlock the bootloader it will have installed a bootloader with fastboot enabled. Unplug the phone and restart while holding vol+/-, once the bootloader menu is up plug the phone back in and use fastboot.
Click to expand...
Click to collapse
Oh. I unlocked when on A9. Then OTA failed although I was still stock. I subsequently did the official A10 update via SD card. So now I have what appears to be a stock recovery.
Is there a temp bootloader that I can use with fastboot enabled? Or should I just redo the BL unlock via the toot although the BL is unlocked. Will that reinstall a custom recovery?
Sent from my PH-1 using Tapatalk
Related
HOW TO get your HTC One M8S back to Factory / stock.
Attention 1: This is NOT for the regular HTC One M8.
Attention 2: This is for the HTC One M8S also known as the M8_QL_UL
(The One M8S does not have a separate subforum on XDA.)
Hi everyone! I saw that many people who have a HTC One M8S have problems with restoring the stock HTC RUU. It is a little bit difficult. So here I'll supply you again with steps that worked for me.
Most of this is a copy from a post I made earlier. But I saw that many of you still have some problems. So here is a dedicated thread.
I have used this method multiple times to restore my phone back to factory defaults. I hope it works for you too!
Warning. You will lose your settings. Everything will be reset to the defaults.
Read these important notes before you begin!
When you need fastboot: only HTC's own fastboot program will work. You will use fastboot, for example, when you want to flash a custom recovery.
Other fastboot applications will not work correctly in my experience! So be sure you use HTC's.
If you need it: HTC will send you a link when you unlock your bootloader. But you can also find fastboot via the same page as where you can find the RUUs.... see below.
Do you have an SDCard ready? You must have one to get this to work and it must be big enough. ADB sideload will NOT work!
Is your phone relocked? It must be! If not, relock it, then come back.
Most of the problems happen because people read too fast. This stuff just takes a long time.. so don't do it if you are in a hurry. And do read carefully.
Are you ready? Ok! Here we go.
Download the RUU zip you want to use. I have used ...HTC_Europe_1.16... BUT later I found this did not allow the newest OTA update (as of august 30th, 2015). Maybe I will test 1.11 some day later.
However, I think that 1.11 is the right version. Not sure where to download the RUU or fastboot? Click the button.
For me, I downloaded the RUU zip via the generous hosting by @El-Conkistador. You can find it via his post here. On his page there is a directory called Firmware (Expert). In there is a directory called Firmware Crypted (Original HTC). In that directory are multiple directories containing RUUs. Choose one for your device, download it, then come back here.
Open your sdcard. It must be fat32 or exFAT formatted.
Copy the RUU zip file onto the root of the sdcard. Do NOT extract it. Just copy it.
You must now rename it to: 0PKVIMG.zip. The first character is the number 0 (zero), not the letter O!
If you know how to do this, take the md5sum from the RUU zip on your computer, and 0PKVIMG.zip on your SDcard. They must be the same! If not, there can be a problem with your SDCard.
Safely unload and remove the SDCard from your computer.
Power off your phone.
Are you sure you want to continue? Then insert the SDCard into the phone..
Take a deep breath..
Boot the phone to the bootloader: hold Volume Down. Press the power button. Release both buttons when you are inside the bootloader.
When you are in the bootloader, press power once to enter fastboot mode.
The restoration process should will now start. Confirm on the screen when it's asked. Then wait patiently, it takes a long time!
Nice detail: there is a small sidebar at the top right side of the screen that will show you progress. Sometimes it will go back to 0; it will fill up more than once.
In case of failure
In my case it failed the first time. Probably because a sector on my SDCard was faulty. I found out by verifying the md5sum of the file on the sdcard, it was not the same as the RUU zip on my computer, but it has to be.
To fix it, I copied the RUU zip to the sdcard for the second time, *then* deleted 0PKVIMG.img, and *then* renamed the RUU zip to 0PKVIMG.zip. Then I looked at the md5sum again. Now it was the same as on my computer... and then the restoration worked.
Still need help?
If you have questions, ask and wait patiently. I am not on this page 24/7, no one is. Just don't panic. Don't demand help. Maybe read this stuff again and see if you made a mistake somewhere.
It is logical that you are annoyed if this stuff doesn't go how you want, sure, it is not the easiest thing to do. I have tried to make it easier, but again, if it still fails, just ask your questions and wait patiently. Treat others like how you want to be treated yourself. :angel:
Good luck!
-voidzero.
(reserved)
voidzero said:
(reserved)
Click to expand...
Click to collapse
Exactly what RUU do you need and when i click hboot in the bootloader it fails finding the 0PKVIMG.zip. so idk what to do
Alex-M8 said:
Exactly what RUU do you need and when i click hboot in the bootloader it fails finding the 0PKVIMG.zip. so idk what to do
Click to expand...
Click to collapse
The exact filename of the RUU I used:
Code:
0PKVIM[email protected]50311_15.00_016_F_release_430101_signed.zip
Do you see a few green lines that say "searching for 0pkvimg.zip" when you go to hboot? They disappear pretty quickly.
voidzero said:
The exact filename of the RUU I used:
Code:
0PKVIM[email protected]50311_15.00_016_F_release_430101_signed.zip
Do you see a few green lines that say "searching for 0pkvimg.zip" when you go to hboot? They disappear pretty quickly.
Click to expand...
Click to collapse
Yeah i saw the green lines but nothing happend after they disappear
Alex-M8 said:
Yeah i saw the green lines but nothing happend after they disappear
Click to expand...
Click to collapse
Is it a fat32 or exfat sdcard? Is the md5sum for 0pkvimg.zip correct? It should be 70eece34781f0b1449f98f03e842f249
voidzero said:
Is it a fat32 or exfat sdcard? Is the md5sum for 0pkvimg.zip correct? It should be 70eece34781f0b1449f98f03e842f249
Click to expand...
Click to collapse
i checked and it is fat32 and i still don't get where the md5sum is located and where i should put it .-.
the md5sum is a long string of characters called a checksum. It scans a file and calculates what number it should get. Other types of checksums are SHA-1, SHA-256, RIPE-MD160 and so on.
MD5 is fairly lightweight so that's why we usually choose md5 for files.
md5sum itself is a program that you can run from the command line. If you use linux, it should be on your computer already, so just do 'md5sum 0pkvimg.zip'. On windows, well, you need md5sum.exe and run that from a command line. But I have not used Windows in so many years that I don't know where to find md5sum.exe. I'm sure you can find it easily... I would google for this, but you can do that too so I'll leave that part up to you.
So: you don't put the md5sum anywhere.. you calculate an md5sum and compare it with the number I gave you previously. Hope this makes sense, keep asking if you need more help.
Hi guys,
Im new to all this I just want to ask for little help here my m8s has unlocked bootloader and modified (unofficial) software (says in bootloader)
Im running 5.0.2 soft ver
Soft number 1.16.401.10
Custom recovery TWRP
Phone is rooted but i need to send it back to htc as its dropping calls randomly within 25secs. All i need is the right ruu so its stock again and says relocked (i know how to relock) official soft and that OTAs would work.
Also do i leave this custom recovery there or before the ruu will i put in the stock one, relock the BL and then the ruu?
Any help is much appreciated.
Sent from my HTC One M8s using XDA Free mobile app
Just relock. The Ruu does the rest! I used 1.11, the exact filename is in my OP. If you have a vendor phone I'm not sure but I think you can still use the same RUU as I have; if not, you will be notified from hboot. Does that answer your question?
Yes thank you.
Sent from my HTC One M8s using XDA Free mobile app
Tried on windows twice then got a blue screen (on the pc) did the 1.11 on my macbook and phone is now back to official and relocked!
I owe you a pint of beer sir. Thank you!
Sent from my HTC One M8s using XDA Free mobile app
Great! Glad to hear.
Cyanogenmod is still in the works. I have finally gotten a preliminary version to boot, so to those of you who are interested, head over to the CyanogenMod 12 on M8s thread...
HTC One M8S: Cyanogenmod 12 Discussion
hi all,
I give up, downloaded three zips from this link:
http://forum.xda-developers.com/htc-one-m8/help/make-custom-recovery-htc-one-m8s-t3114245
1.03
1.11
1.11 - combined signed
and every time I get error "no image or image wrong....no gift file....loading image 0Pkvidiag.zip - No image! loading 0PKVIDIAG.nbh...no image or wrong image"
...inside the zip file there is no 0PKVIMG.img file so dont realy know what to rename . . .
...yes checked md5 sum and they are OK
...sd card is fat32 (tried copying zip file from two different laptops , no difference)
...Custom recovery TWRP
this is m8s european version which was rooted , fastboot shows now RELOCKED and this images just dont work ,
this phone is giving all sort of issues, no custom roms with updates, SIM_Card error sometimes 10+ times a day causing call disconnections and reboots, cant update to lates htc soft as on custom rom it just dont work.....
what I am doing wrong here? probably something stupid easy :laugh: help please
Thanks in advance !
new-noob said:
what I am doing wrong here? probably something stupid easy :laugh: help please
Click to expand...
Click to collapse
Hiya. Ugh I get how frustrating this can be!! But you're close, so we'll get you sorted out. FYI on saturday and sunday I'm not around much (family comes first ), so replies might take me a while... but we'll figure it out.
You need this exact file:
Code:
0PKVIM[email protected]50311_15.00_016_F_release_430101_signed.zip
Copy that to the sdcard and rename it to 0PVKIMG.zip, don't extract it just rename it. The md5sum should be:
Code:
70eece34781f0b1449f98f03e842f249
If that won't work, we need to figure out why. That comes next. :good:
voidzero said:
Hiya. Ugh I get how frustrating this can be!! But you're close, so we'll get you sorted out. FYI on saturday and sunday I'm not around much (family comes first ), so replies might take me a while... but we'll figure it out.
You need this exact file:
Code:
0PKVIM[email protected]50311_15.00_016_F_release_430101_signed.zip
Copy that to the sdcard and rename it to 0PVKIMG.zip, don't extract it just rename it. The md5sum should be:
Code:
70eece34781f0b1449f98f03e842f249
If that won't work, we need to figure out why. That comes next. :good:
Click to expand...
Click to collapse
HI voidzero and thanks for taking the time and replaying!
I ended up installing Android Pandora 1.2 and ...waiting on feedback re: SIM errors, hopeful they are gone with new ROM,
I'll post quick update tomorrow.
Thanks again and enjoy ur weekend !
new-noob said:
HI voidzero and thanks for taking the time and replaying!
I ended up installing Android Pandora 1.2 and ...waiting on feedback re: SIM errors, hopeful they are gone with new ROM,
I'll post quick update tomorrow.
Thanks again and enjoy ur weekend !
Click to expand...
Click to collapse
You should use Cyanogenmod, not Pandora. Pandora is old, is not updated, and contains a very problematic security issue with libstagefright. Use cyanogenmod for your own good!
voidzero said:
You should use Cyanogenmod, not Pandora. Pandora is old, is not updated, and contains a very problematic security issue with libstagefright. Use cyanogenmod for your own good!
Click to expand...
Click to collapse
hey, yeap, pandora gives same SIM card error!
Thanks for advise, I will definitely try Cyanogenmmod, think this is the link : http://forum.xda-developers.com/htc-one-m8/general/htc-m8s-cyanogenmod-t3142668
?
Thank you!
hello.
i need help. my htc m8s is relock, my sd card is format fat 32, md5sum match, but still not recognize when i restart in fastboot.
this one was more of a proof of concept but it works. you will get the red triangle but don't worry about it. BUUUUUT if you wanna run it. Here's how:
DISCLAMER: first and foremost, I take NO responsibilities for the possibility of a bricked phone(none whatsoever). if you brick it, it's YOUR fault, not mine.
ALWAYS BACKUP YOUR DATA BEFORE YOU DO ANYTHING
1.your phone has to be fully running ZV4. DO NOT DELETE YOUR DATA (but do back it up in case something does happen)
2. Make sure you have LGUP working. if not, refer to here
3. Download the edited ZV4.tot from here, and extract the zip.
4. Put phone in download mode ( Phone off, vol up while plugging in usb from PC).
5. Start LGUP
6. Make sure you see a com # and phone model
7. At the bottom where it says BIN, select it, at which point you should see 3 dot on the right, select it and choose the tot file that you downloaded from here
8. make sure you select "update" and none of the others. if you select any of the other options it will bootloop the phone.
If you bootloop your device:
1. Put phone in download mode ( Phone off, vol up while plugging in usb from PC).
2. Start LGUP
3. Make sure you see a com # and phone model
4. At the bottom where it says BIN, select it, at which point you should see 3 dot on the right, select it and choose the original ZV4 .tot file that you got from Honestly Annoying that he has listed here
5. select "refurbish", then "start" and wait for the magic.
I give creds to Honestly Annoying, and Tungkick for providing the original ZV4 tot file
schizoidd said:
this one was more of a proof of concept but it works. you will get the red triangle but don't worry about it. BUUUUUT if you wanna run it. Here's how:
DISCLAMER: first and foremost, I take NO responsibilities for the possibility of a bricked phone(none whatsoever). if you brick it, it's YOUR fault, not mine.
ALWAYS BACKUP YOUR DATA BEFORE YOU DO ANYTHING
1.your phone has to be fully running ZV4. DO NOT DELETE YOUR DATA (but do back it up in case something does happen)
2. Make sure you have LGUP working. if not, refer to here
3. Download the edited ZV4.tot from here
4. Put phone in download mode ( Phone off, vol up while plugging in usb from PC).
5. Start LGUP
6. Make sure you see a com # and phone model
7. At the bottom where it says BIN, select it, at which point you should see 3 dot on the right, select it and choose the tot file that you downloaded from here
8. make sure you select "update" and none of the others. if you select any of the other options it will bootloop the phone.
If you bootloop your device:
1. Put phone in download mode ( Phone off, vol up while plugging in usb from PC).
2. Start LGUP
3. Make sure you see a com # and phone model
4. At the bottom where it says BIN, select it, at which point you should see 3 dot on the right, select it and choose the original ZV4 .tot file that you got from Honestly Annoying that he has listed here
5. select "refurbish", then "start" and wait for the magic.
I give creds to Honestly Annoying, and Tungkick for providing the original ZV4 tot file
Click to expand...
Click to collapse
What exactly does this do? I'm very interested in this... It has some potential
Also, what is the red triangle? Does it not let you boot?
Honestly Annoying said:
What exactly does this do? I'm very interested in this... It has some potential
Also, what is the red triangle? Does it not let you boot?
Click to expand...
Click to collapse
it lets you boot fully. you just get a warning that your device can't be verified
schizoidd said:
it lets you boot fully. you just get a warning that your device can't be verified
Click to expand...
Click to collapse
Damn... great job with this! Can you please explain (with as much detail as you can) how you did this? This is extremely promising and I'm trying out some stuff now
Honestly Annoying said:
What exactly does this do? I'm very interested in this... It has some potential
Also, what is the red triangle? Does it not let you boot?
Click to expand...
Click to collapse
Honestly Annoying said:
Damn... great job with this! Can you please explain (with as much detail as you can) how you did this? This is extremely promising and I'm trying out some stuff now
Click to expand...
Click to collapse
well, simply I used a hex editor
schizoidd said:
well, simply I used a hex editor
Click to expand...
Click to collapse
But what parts did you edit? This could be very helpful
@autoprime Anything here?
Is this a pre-rooted tot file?
newbreedsoftware said:
Is this a pre-rooted tot file?
Click to expand...
Click to collapse
no. all it does is make your device show userdebug. nothing else is done, no root, no nothing. this one was a proof of concept to see if editing the .tot file would work.
What the crap @schizoidd. I live in Boise too.
I'd possibly be down to help out.
A thing about signatures, if it's a md5 type signature, you can make changes and not trigger failed verification if all characters are in there. Moved around but not changed. Like string "abcdef" can be changed to "fedcba" because it still evaluates the same. So maybe change a tot's security directory to the reverse and the phone won't be able to find it. I think I read that somewhere on these boards.
Would this work with the dirtysanta exploit from the LG v20?
i am not sure if this is an actual debug firmware.. it almost seems he took a stock zv4 tot and simply used a hex editor to say its a debug firmware?
eagleeyered said:
mostly. took a lot more than that. only used the hexeditor to extract the images for edit and to put them back in.
Click to expand...
Click to collapse
my point was, just because it was modded to "look" like a debug doesnt make it a debug.. if it was youd have fastboot enabled and you could simply unlock the bootloader..
---------- Post added at 01:24 AM ---------- Previous post was at 01:24 AM ----------
essentially that makes this thread misleading as you dont have sprint user debug
eagleeyered said:
who said it was me that created that file. that was all schizoidd. but i can tell you that there was a lot more than "just edited to look like userdebug". if it was edited to look like that, it wouldn't say that it was edited on boot, nor would it boot at all. it would just brick your device. now as he said, "this one was more of a proof of concept". in other words, it was made to see if the TOT for ZV4 (and others) could be picked apart and edited and put back together.
you do realize that the userdebug/eng ZV4 boot.img that tunkick released was used to make that even bootable. and it was schizoidd that realized that it was a userdebug boot, not an eng boot. if it wasn't for schizoidd, the userdebug on ZV4 would have never been released. it was only a proof of concept(i.e. bugs). fastboot is one and adb root is the other. but if you also look around, there was a ZV4 fastboot that was released. which kind of worked. and as we get close to releasing a good modded tot for the latest version of the software for our device, another one gets released. And as there are only 5 (yes 5) give-or-take people working diligently on attaining root for the LS992 with only 2 test devices, that stuff takes time, especially when one has to be replaced. for the record, 8 phones have been fried while attaining root (and that is out of pocket for the cost of those devices). so until we can get more people on the project, either as testers or as devs, it will take a while.
Click to expand...
Click to collapse
before you get panties in a bunch no one ever said you released anything.. was just going based off his posts and clearly saying all he did was use a hex editor and you guys not having any actual ddbug features it doesnt appear to be a debug firmware.. if it did youd have an unlocked BL already with fastboot
eagleeyered said:
just to give you a heads-up. ALL of the fastboot areas have been disabled and aren't in the aboot.img at all for the LS992. the only one that has fastboot that is close to what is needed is the tmobile version. and integrating 2 boot and 2 aboots and tring to get it to boot is hard. especially since an improper edited aboot results in bricked device.
And i was only pointing out the facts. i aint at all mad.
Click to expand...
Click to collapse
just a heads up, if you had debug firmware the aboot would have the necessary fastboot commands.. thats what im tryna tell you lol
we got a debug firmware on the lg v20 and debug aboot was already unlocked and had fastboot working
---------- Post added at 03:45 AM ---------- Previous post was at 03:44 AM ----------
not to mention the OPs account was disabled lol.. i wonder why
eagleeyered said:
as we dont have an actual userdebug device, we have to build the bootloader from the ground, up from source (kind of a pain).
although the QSEC_HASH key is the same from the LS992 and the V20. so might be able to pull some things from that, and they are based on the MSM board. i just want to make sure before saying the V20 root method will work, i wanna check to make sure that the aboot and boot is compatiblle
Click to expand...
Click to collapse
lol if you are making it from the ground up then it will never be a debug firmware.. debug firmwares come directly from the device manufacturer/carrier.. not something domeone just whips up..
youre not creating a debug anytjing, you guys are trying to find a way to unlock/root the device is all lol
eagleeyered said:
no one said it was easy.
Click to expand...
Click to collapse
i know.. but op sayin he got userdebug isnt true lol he has a slightly modified rom that if anything is only visually a userdebug
eagleeyered said:
oh, and do you wanna know why Schiziodd was banned? he was banned for the simple fact that him and one other person got into an arguement and due to that person using a technicallity in words and also trapping, he got banned. if he had known that what he had was what it was, he would have deleted it and added it for everyone and then left it at that.
Click to expand...
Click to collapse
lol sorry but this comment confuses me.. he was banned due to a technicality in words?? wht does that even mean lol.. he was trapped on xda??
and if he knew what he had was what it was he could have deleted it and add it for everyone then left? why would he delete and readd?
it sounds like he took someone elses work and got banned for it but who knows, im not a mod lol but doesnt seem to be a trustworthy fellow at all...
elliwigy said:
lol sorry but this comment confuses me.. he was banned due to a technicality in words?? wht does that even mean lol.. he was trapped on xda??
and if he knew what he had was what it was he could have deleted it and add it for everyone then left? why would he delete and readd?
it sounds like he took someone elses work and got banned for it but who knows, im not a mod lol but doesnt seem to be a trustworthy fellow at all...
Click to expand...
Click to collapse
Please check PMs, ignore eagleeyered...
Also you are very right about this only being hex edited. there is no official userdebug anything in this TOT, as I have tested this and flashed myself. Thread is misleading.
eagleeyered said:
[/COLOR]i have a ZV4 userdebug that boots and has the system set to RW. the only reason it's not released is due to the fact that not a lot of people are on ZV4.
Click to expand...
Click to collapse
So, less than a month ago, you're telling people on 4 not to update because IT'S COMING!! within a month. Now you're saying you've got it, it works, AND ON TIME, but you're not going to release it because, what, the "not a lot of people" who would want it, wouldn't want it now?
Hell, if I was actually able to deliver on something that big, ESPECIALLY within the time frame I set for it, I'd be paying Google to get my work to the top of search results. I'd be going door to door with it. I'd set up shop in front of Sprint stores until they stop selling the device, crowing about my ability to get RW to ANY build of this thing. But, that's just me, I guess.
You see how incredibly fishy that seems?
Hey everybody,
I was on CM14.1, no issues, but decided to flash back to 6 and made the stupid mistake of trying to go straight with the standard motorola image. Now I am able to load the bootloader mode but cant do much after that. None of the partitions work, nor I can get data from bootloader info (tried retreieving flashing info to no avail). I am trying to find something I can use. Anyone has a suggestion?
Would you mind detailing which steps you took to flash? I think I know what your problem is, but I want to be sure first.
zstricky said:
Would you mind detailing which steps you took to flash? I think I know what your problem is, but I want to be sure first.
Click to expand...
Click to collapse
Sure!
- Got unlocked bootloader and installed cm14.1
- Decided to revert back to stock so downloaded 6.0 system image.
- instead of deleting the got.bin line from flashfile.xml I went to rsd and tried flashing it. It errored out and this took me where I am.
There is a flashable stock rom zip, but assuming you want to just use the official image that you already have you'll need to flash with fastboot. I saw that you posted on the thread 'return to stock etc'. Follow those fastboot steps, but be aware that there is a major omission: the instructions only go to system.img_sparsechunk.8, but there are 9 of those files and the phone will not boot if you only flash 8. As you go through fastboot flashing I think there will be a couple files that will give errors. Do an internet search on the error output line, but if I remember correctly the files that won't flash are no big deal and didn't affect my phone when I went ahead and ignored the errors.
I did man... The problem is... Something trully god messed up here. I am now getting hard stops related to aboot failures. I saw something similar on the xt1033 forums but we miss those same files.
Coming from an iPhone I'm used to connecting the phone to iTunes via USB, downloading a fresh version of the OS and restoring the phone. Then I have the option of setting up as new or restoring a backup.
I would like to know if there's a way to do something like that with my Note 8. I realize I can reset everything from within the settings app but I would like to wipe it clean and install a fresh copy of Nougat 7.1.1.
Is this possible? Also just in case it comes up I'm not interested in rooting at this point in time.
Thanks!!
rocknblogger said:
Coming from an iPhone I'm used to connecting the phone to iTunes via USB, downloading a fresh version of the OS and restoring the phone. Then I have the option of setting up as new or restoring a backup.
I would like to know if there's a way to do something like that with my Note 8. I realize I can reset everything from within the settings app but I would like to wipe it clean and install a fresh copy of Nougat 7.1.1.
Is this possible? Also just in case it comes up I'm not interested in rooting at this point in time.
Thanks!!
Click to expand...
Click to collapse
Pretty sure there is a ton of posts on here discussing Odin and what it is used for, as well if you look under guides I have posted the stock firmware and links to odin.
Go here for that stuff: https://forum.xda-developers.com/sp...stock-restore-odin-recovery-software-t3668888
Basics : Odin is like ITunes , you select the firmware to install to the device and push it to phone, it wipes phone and installs the software selected.
There are only a few limitations of ODIN, that being that if the firmware is set to Anti-Rollback you can not go back to any version older then the 1st revision of that rollback version.
Example : N950USQU1AQI5 This is the latest version for sprint currently there are 3 parts of this explained below.
The QI5 is the version identifier.
N950U is the variant the software is designed to be used with.
The number 5 spots from the end determines the bootloader revison and will be the Anti-rollback version. All versions matching that number can be flashed without bias, so any version labeled ( 1 ) can be flashed to the note.
Now hypothetically if this was the software that comes next: N950USQU2AQL9
Once you were to install this version you could NEVER flash anything lower then ( 2 ) to the device, the bootloader on the phone will refuse it and tell you the version is older and will not install.
Thank you for the detailed reply. Your right in that I've seen a lot about Odin. What I'm somewhat concerned about is that whatever I've managed to find and read about doing this is that it will void the warranty? Is this accurate or am I misunderstood something?
Also, the reason I wanted to do this is because something screwed things up after I moved apps to the SD card. And yes I moved them using the built-in settings app. So obviously I was only able to move apps that the OS allowed me to. Basically even though it showed that the apps were on the external storage they just disappeared. If I tried to reinstall Google Play would immediately crash.
So my thought was that if I did a clean install it would wipe out any crud that might be left behind by doing a hard reset built into the phone. Am I completely wrong about this or is it possible some stuff might be left behind?
Thanks again for taking the time to post your reply.
rocknblogger said:
Thank you for the detailed reply. Your right in that I've seen a lot about Odin. What I'm somewhat concerned about is that whatever I've managed to find and read about doing this is that it will void the warranty? Is this accurate or am I misunderstood something?
Also, the reason I wanted to do this is because something screwed things up after I moved apps to the SD card. And yes I moved them using the built-in settings app. So obviously I was only able to move apps that the OS allowed me to. Basically even though it showed that the apps were on the external storage they just disappeared. If I tried to reinstall Google Play would immediately crash.
So my thought was that if I did a clean install it would wipe out any crud that might be left behind by doing a hard reset built into the phone. Am I completely wrong about this or is it possible some stuff might be left behind?
Thanks again for taking the time to post your reply.
Click to expand...
Click to collapse
Odin does NOT effect the warranty bit, even with the new root method the Knox warranty status does not get effected.
I actually had mine rooted, some pixels in my screen were messed up ( not related to root ) used ODIN to go back to stock and sent it in to Samsung for a warranty repair and it was approved, fixed and sent back for free so no fret.
The warranty status shows up when you put your phone into Download mode ( Holding Bixby + Volume Down and power button together during a boot up ) It shows warranty bit 00x00
If it were to effect it the status would go to 00X01 and so on as you continue to modify things. The status only changes if the phone is compromised with custom boot files witch we do not have access to due to having the bootloader locked.
This is a routine process to recover the phone if it wouldn't boot,
furthermore you can essentially do the same procedure using Samsung smart switch on desktop, but i'm not fluent with using it as ODIN is a better method and more robust and less dumb ware.
as for moving apps to sd, you could also try deleting them off the sd, or possible that the sd card is messing up and not fast enough for the device to read and run those apps so if you redo and it happens again id avoid putting them on sd if you can.
hope this helps. No fret on using odin, just take your time and pay attention to the options you use. Do not confuse NAND ERASE ALL ( that is the same has a hard reset) with ERASE EFS ( this deletes the serial number and should never be done! )
Again, thank you so much for the detailed reply. Just one more thing. Can you please supply me a link to the correct stock ROM. I apologise for all the noob questions but it's been more than 7 years since I've messed with Android. Some of the links I found took me to download did where I had to pay or else the fire was too big for free.
I believe this is the exact one I need for my Sprint Note 8
N950USQU1AQI5. This is what I have on my phone now.
As for the SD card issue there were just a few apps I found. The others just seemed to disappear. In any case I bought a new 256GB U3 card by Samsung so there should be no questions now on whether it's too slow or bad. I moved a couple apps and so far so good.
Thanks again and best regards!!
rocknblogger said:
Again, thank you so much for the detailed reply. Just one more thing. Can you please supply me a link to the correct stock ROM. I apologise for all the noob questions but it's been more than 7 years since I've messed with Android. Some of the links I found took me to download did where I had to pay or else the fire was too big for free.
I believe this is the exact one I need for my Sprint Note 8
N950USQU1AQI5. This is what I have on my phone now.
As for the SD card issue there were just a few apps I found. The others just seemed to disappear. In any case I bought a new 256GB U3 card by Samsung so there should be no questions now on whether it's too slow or bad. I moved a couple apps and so far so good.
Thanks again and best regards!!
Click to expand...
Click to collapse
The 1st link I sent you at top is the link to find most current firmware for the Sprint note 8. QI5 is the latest as of today. The one you posted is the correct one. The post also has Odin available to dl as well.
But here is the direct link to QI5: https://www.androidfilehost.com/?fid=745849072291677290
Pretty much with Odin
Take the firmware zip and unzip it.
Then put phone into dl mode as explained above holding power, volm down and bixby. Once on green screen click up to start dl mode and it's ready.
Side note:
That key combo is also soft reset. Holding vol up instead would bring you to recovery where you can do a full hard reset as well. If you accidentaly get into dl mode trying to soft reset because phone got frozen just soft reset out of it and you'll be back to booting up as normal.
Plug phone in and open Odin.
Odin should show the phone and it's com port once driver on pc have installed.
Click each box ( bl, ap, cp, csc) and select the matching files.
The csc you'll use is the one with OYN in it's name.
Under options have f.reset time.. auto reboot and nand erase all checked. Nothing else. Again I say nand erase all.. remember what I said about the efs one and never checking it....
Once each loads up.. ( ap will take forever it will act like it has gotten stuck and may show it's not responding ) this is normal just wait it out as it's a huge package being loaded...
Click start and drink a coffee..
Once done, it will auto reboot, wipe and then boot up
Re setup and test. Just be aware all data on device will be gone.
Otherwise you will be good to go!
I added to generic photos of what it looks like when phone is connected and com port is showing up. As well what options are to be selected. I put a big pointing finger to the correct erase all option as well lol
Thank you for all the detailed replies!!! You rock dude. Things are slowly coming back to me. The EVO 4G was the last Android phone I had before jumping to iPhone. I used to install different ROMs almost weekly and tried all sorts of stuff back then. Had no fear
I guess after being away for so long it just takes time and reading through all the different threads.
Thanks again!!!
Team DevDigitel said:
Plug phone in and open Odin.
Odin should show the phone and it's com port once driver on pc have installed.
Click each box ( bl, ap, cp, csc) and select the matching files.
The csc you'll use is the one with OYN in it's name.
Click to expand...
Click to collapse
Okay so I was all set to do this but when I unzipped the firmware.zip and there are more files in there that I'm not sure what to do with.
First there are 2 CSC files and both have OYN in the name.
First one is : CSC_OYN_N950UOYN1AQI5_CL12173876_QB14907525_REV00_user_low_ship_MULTI_CERT.tar
Second is: HOME_CSC_OYN_N950UOYN1AQI5_CL12173876_QB14907525_REV00_user_low_ship_MULTI_CERT.tar
There's also a file called USERDATA_SPR_N950USQU1AQI5_CL12173876_QB14907525_REV00_user_low_ship_MULTI_CERT.tar
Is there anything I need to do with this particular file?
Also all the files are xxx.tar.MD5. Am I right in guessing that Odin with verify the MD5 checksum?
Thanks again!!!
rocknblogger said:
Okay so I was all set to do this but when I unzipped the firmware.zip and there are more files in there that I'm not sure what to do with.
First there are 2 CSC files and both have OYN in the name.
First one is : CSC_OYN_N950UOYN1AQI5_CL12173876_QB14907525_REV00_user_low_ship_MULTI_CERT.tar
Second is: HOME_CSC_OYN_N950UOYN1AQI5_CL12173876_QB14907525_REV00_user_low_ship_MULTI_CERT.tar
There's also a file called USERDATA_SPR_N950USQU1AQI5_CL12173876_QB14907525_REV00_user_low_ship_MULTI_CERT.tar
Is there anything I need to do with this particular file?
Also all the files are xxx.tar.MD5. Am I right in guessing that Odin with verify the MD5 checksum?
Thanks again!!!
Click to expand...
Click to collapse
use the CSY OYN, i touched this in a earlier response, and dont worry about the user data one and yes they are verified by md5 before a push occurs, this can be turned off in odin if you wanted and skip md5 verification.
Team DevDigitel said:
use the CSY OYN, i touched this in a earlier response, and dont worry about the user data one and yes they are verified by md5 before a push occurs, this can be turned off in odin if you wanted and skip md5 verification.
Click to expand...
Click to collapse
Once again...thank you!!!
If you don't mind I have a question about restoring from backup. If I backup to Samsung cloud then it will restore the apps that I currently have installed, is that correct?
If I backup to Google and then restore from Google backup it will only restore data and if I install an app that I had prior to the wipe/restore it will then restore the data for that particular app. Is that correct?
Also is it possible to choose which apps to restore if I restore from Samsung backup?
Thanks again!!
Can someone please with ATT android Q build 30E send me both A and B boot.img
nikothebarber said:
Can someone please with ATT android Q build 30E send me both A and B boot.img
Click to expand...
Click to collapse
Niko, yer asking everywhere for this, but u already have it right? Your phone is att updated to 30e right?
So, just like anyone else would have to do, use qfil and get it? I mean, if you're going to root and get twrp on the device, you're going to have to install and learn to use, qfil.
As I mentioned in another thread, if you post your boot_a image, I'll twrp patch it for u and post it back.
Do you need help using / installing qfil?
No I believe im mismatched I accidentally flashed a and b boot ing ive got it working but boot imgg is older then 30e, I get the error on start up saying current version is not available for user can't find match carrier NT code FFFFFF: 84
nikothebarber said:
No I believe im mismatched I accidentally flashed a and b boot ing ive got it working but boot imgg is older then 30e, I get the error on start up saying current version is not available for user can't find match carrier NT code FFFFFF: 84
Click to expand...
Click to collapse
Okay, since you did an OTA update (right?) then the other boot image would be the previous version OS for att. Maybe to get the newest one u can do the update again? (I don't know, I"m asking, I don't have a carrier specific phone so no way to test that).
Also, that NT error code is usually only going to occur when u 'cross flash'. Which makes me wonder... what boot partition are u really using? It sounds like it **may** not even be an att one?
I better understand your situation now, sure does make it obvious why you want to do a backup before any modifications right? sorry, I'm sure you've learned that lesson now, but maybe others can benefit from your tough lesson.
Here's the first thing I'd do if u; Make A COPY OF EA boot partition, as they are now. At least you'll have a backup of ea one from here (whatever they happen to be).
One of the easiest ways to do that would be (assuming you have twrp injected), would be to boot recovery, connect to pc with usb cable, and type in 'adb shell'.
Then use the following dd commands (modify for your directory structure on sd card);
dd if=/dev/block/bootdevice/by-name/boot_b of=/external_sd/backup/current_att_boot_b.img
this assumes you have a directory on your sd card called 'backup'. Replace it with whichever you may have. Do the same for boot_a also (change boot_b to boot_a), and change the output name to reflect what you're backing up.
So with these backups, you **could** decide to copy your boot_b backup tot he boot_a partition and see what happens? I mean it sounds like you're not sure what is on either one of your boot partitions, so trying that may be the only way to have some idea of what's there.
*If** it turns out that the device boots okay with boot_b copied over, then at least you'll have a boot partition that could be twrp injected and not have the nt_error code?
good luck
I mixed up the active side and replaced one with the other already . I never did OTA and unfortunately it does not work. I have back ups now of boot a and b with qfil, my firmware is 30e and boot img is 30b. I need boot.img 30E
I've got 30e boot.bin can.you add twrp to it
nikothebarber said:
I've got 30e boot.bin can.you add twrp to it
Click to expand...
Click to collapse
Well I have no way of knowing which one is 30e and which is att prior version. But I can tell you the 30e_a u posted here is identical to the 30e_a posted in this thread.
cheers