I am trying to use flash tool and I keep getting errors at the end and my phone will not boot up after.
The most recent one said 'processing of modern.sin finished with errors'
Anyone know a way to fix this? I have tried downloading different regions but I haven't managed to get one to flash correctly. I tried running software repair after each try and it fails as well.
Thanks
nikekicks said:
I am trying to use flash tool and I keep getting errors at the end and my phone will not boot up after.
The most recent one said 'processing of modern.sin finished with errors'
Anyone know a way to fix this? I have tried downloading different regions but I haven't managed to get one to flash correctly. I tried running software repair after each try and it fails as well.
Thanks
Click to expand...
Click to collapse
Reinstall the drivers.
Use back panel to connect your device.
Related
After a horrid couple of days staring at a "system software unauthorized by verizon" screen and being unable to get to DL mode I have un-softbricked my phone by pushing
HOME_I535VRALF2_I535VZWALF2_618049_REV09_user_low_ship.tar.md5. That works fine.
However, pushing the boot image fails (Samsung-Updates.com-SCH-I535-VZW-I535VRALF2_Kernel.zip)
Evidently the Boot.img is perhaps optional.
After the boot image failed I tried rooting by using Samsung Galaxy Toolkit. That's failed a few times on two different computers, each time returning me to the "System software unauthorized by Verizon" screen. The phone reboots a few times (twice?). Odin launches and pushes the first file. When the second Odin flash starts it FAILS and I get the "unauthorized" message on the phone.
I've also tried to root by using GS3_debugfs-root_r2.zip (well, the files within actually). The latter requires Android SDK which I think I have set up correctly. Also no luck.
Of perhaps some relevance is that my Win 7 machine keeps telling me that the device drivers aren't installed properly (although I've done it several times and both the installer and Device Manage seems to think they are there). Samsung Toolkit can't read the device ID. However an XP machine does see the phone so maybe it is something about the Win 7 machine.
The root fail happens on both machines at the same point in the process so I assume their is an issue on the phone side.
And suggestions?
(Of course when the phone does come alive Verizon keeps trying to push this new search-crippling update. One more problem I don't need today).
Do I need some other boot.img or some other method or what?
maplewood said:
After a horrid couple of days staring at a "system software unauthorized by verizon" screen and being unable to get to DL mode I have un-softbricked my phone by pushing
HOME_I535VRALF2_I535VZWALF2_618049_REV09_user_low_ship.tar.md5. That works fine.
However, pushing the boot image fails (Samsung-Updates.com-SCH-I535-VZW-I535VRALF2_Kernel.zip)
Evidently the Boot.img is perhaps optional.
After the boot image failed I tried rooting by using Samsung Galaxy Toolkit. That's failed a few times on two different computers, each time returning me to the "System software unauthorized by Verizon" screen. The phone reboots a few times (twice?). Odin launches and pushes the first file. When the second Odin flash starts it FAILS and I get the "unauthorized" message on the phone.
I've also tried to root by using GS3_debugfs-root_r2.zip (well, the files within actually). The latter requires Android SDK which I think I have set up correctly. Also no luck.
Of perhaps some relevance is that my Win 7 machine keeps telling me that the device drivers aren't installed properly (although I've done it several times and both the installer and Device Manage seems to think they are there). Samsung Toolkit can't read the device ID. However an XP machine does see the phone so maybe it is something about the Win 7 machine.
The root fail happens on both machines at the same point in the process so I assume their is an issue on the phone side.
And suggestions?
(Of course when the phone does come alive Verizon keeps trying to push this new search-crippling update. One more problem I don't need today).
Do I need some other boot.img or some other method or what?
Click to expand...
Click to collapse
When did he update the toolkit for verizon phones?
piiman said:
When did he update the toolkit for verizon phones?
Click to expand...
Click to collapse
Not sure who you mean by "he" when you ask when the toolkit was updated. I downloaded it pretty recently.
mapleood said:
Not sure who you mean by "he" when you ask when the toolkit was updated. I downloaded it pretty recently.
Click to expand...
Click to collapse
Where did you get it from? If its the toolkit im thinking of he didn't have a vzw version. Also if he does have new vzw version I want it if he doesn't then that's your problem.
piiman said:
Where did you get it from? If its the toolkit im thinking of he didn't have a vzw version. Also if he does have new vzw version I want it if he doesn't then that's your problem.
Click to expand...
Click to collapse
Can't say I recall where I got it from.
But if the Toolkit ain't the solution then I need a plan C.
But I suspect that I still need to successfully flash the boot.img. Which so far I can't. Independent of evidence my guess is that if I could flash that boot.img then the rooting might work. Just a guess.
http://forum.xda-developers.com/showthread.php?t=1762709
This guide is a sticky for a reason and will be your best friend.
Sent from my Galaxy Nexus using xda app-developers app
maplewood said:
Can't say I recall where I got it from.
But if the Toolkit ain't the solution then I need a plan C.
But I suspect that I still need to successfully flash the boot.img. Which so far I can't. Independent of evidence my guess is that if I could flash that boot.img then the rooting might work. Just a guess.
Click to expand...
Click to collapse
Hmmmm so you dont even know if you flashed a boot.img for our phone or where the tools came from? Not good
If your guess is correct and your pc recognized the phone and you can use adb you could use the dd command to push the boot.img. but if you dont have the correct drivers none of the above will work. Good luck
Or you could follow that link you just got
---------- Post added at 05:20 PM ---------- Previous post was at 04:33 PM ----------
http://forum.xda-developers.com/showthread.php?t=1762204
This may also help you out as its very detailed.
Has anyone had this issue when attempting to do OTA updates?
I had an F510S and I got a prompt to download the V15 software. Upon receiving the message, I unrooted the phone completely using the option in Super SU, even tried a factory reset afterwards..The update will download, restart to go through the installation process, fail, then upon rebooting I would get the message.
The only explanation I can think of is that I uninstalled some of the bloatware that came with the phone using Titanium Backup... does LG check for changes in the system files when doing OTA updates?
I ended up switching over to an H959 rom instead as I realized that I'd need to flash a complete stock rom before trying an OTA update again but it would be nice to know in case I decide to uninstall system apps in the future.
Try updating via LG Pc suit
PC Suite kept saying that I had the latest version available, even though I had a prompt for an OTA update
Exactly the same problem here ! I also think it's caused by the uninstallation of some apps..
Must have all apps from factory bloatware and all. That's the only way i learned the hard way in the past . Flag stock tot
Managed to overcome that by updating using the LGMobile Support Tool. It's like the Sony Update Service but for LG instead.
Kidsnd274 said:
Managed to overcome that by updating using the LGMobile Support Tool. It's like the Sony Update Service but for LG instead.
Click to expand...
Click to collapse
I tried that.. Still no updates available but on my F510L there's the OTA... :crying:
Drissouille said:
I tried that.. Still no updates available but on my F510L there's the OTA... :crying:
Click to expand...
Click to collapse
Have you tried using 'upgrade recovery' from the support tool? When I try it with mine, I get 'no upgrade items to fix'
hbcdfpq said:
Have you tried using 'upgrade recovery' from the support tool? When I try it with mine, I get 'no upgrade items to fix'
Click to expand...
Click to collapse
Same thing here
put your device in download mode: power off then keep holding volume op while plugging in the usb cable
then go to the LG tool on your pc and click on upgrade recovery
ShadowRii said:
put your device in download mode: power off then keep holding volume op while plugging in the usb cable
then go to the LG tool on your pc and click on upgrade recovery
Click to expand...
Click to collapse
Tried that too... Still the same
that's strange that's how I fixed mine
Upgrade Recovery
Drissouille said:
Tried that too... Still the same
Click to expand...
Click to collapse
Mine said there are no items to fix when I tried this. I guess I will just be stuck with 4.4.2. I really wanted the lollipop
Has anyone been able to receive OTAs after flashing a KDZ?
Hi, I got an old Galaxy S3 to play around with today and I think I may have bricked it. It was on the latest 4.4.2 build and I attempted to downgrade it to unlock the bootloader. Obviously, it didn't work but I though I would just be able to flash back to stock. I have tried every tutorial I can find but I can not get back to stock. When flashing in ODIN it always fails. kies never connects to the device, and the Verizon repair tool doesn't detect the device.
When I try to boot the phone it says "firmware upgrade encountered an issue. Please use software repair assistant & try again"
I am still able to boot into download mode.
Does anyone have any idea how to fix this?
mpalomba3 said:
Hi, I got an old Galaxy S3 to play around with today and I think I may have bricked it. It was on the latest 4.4.2 build and I attempted to downgrade it to unlock the bootloader. Obviously, it didn't work but I though I would just be able to flash back to stock. I have tried every tutorial I can find but I can not get back to stock. When flashing in ODIN it always fails. kies never connects to the device, and the Verizon repair tool doesn't detect the device.
When I try to boot the phone it says "firmware upgrade encountered an issue. Please use software repair assistant & try again"
I am still able to boot into download mode.
Does anyone have any idea how to fix this?
Click to expand...
Click to collapse
If you are using Odin in attempts to flash stock 4.4.2 and that is failing I am at a loss. If Odin flashes of 4.3 are failing, then I would say use 4.4.2. I doubt you need to try debrick images, if one is available for the i535, since you can boot into download mode. I don't have any info about the VZW repair tool or Kies, I haven't used them.
http://forum.xda-developers.com/showthread.php?t=1734949
dawgdoc said:
If you are using Odin in attempts to flash stock 4.4.2 and that is failing I am at a loss. If Odin flashes of 4.3 are failing, then I would say use 4.4.2. I doubt you need to try debrick images, if one is available for the i535, since you can boot into download mode. I don't have any info about the VZW repair tool or Kies, I haven't used them.
Click to expand...
Click to collapse
landshark68 said:
http://forum.xda-developers.com/showthread.php?t=1734949
Click to expand...
Click to collapse
Thanks, I managed to figure out the problem. I thought I was flashing 4.4.2 images but I was actually flashing 4.3 images. I downloaded the latest image and managed to flash it in Odin without a problem.
Thanks again for responding
Hi,
So I was trying to root my phone and it all went wrong. I have rooted tons of phones before, but never a Samsung (never again).
The phone will show the Samsung Boot screen, but then it either goes black, with a flashing blue LED, or it boots itself into recovery.
When I use ODIN, the flash fails at "system.img.ext4" whenever I use just the AP field. If I load all the fields in, it fails at "xbl.elf"
I got the firmware file from SamMobile, so I don't think that is the issue, but who knows. It's as if the phone no longer has an OS on it. I also tried using SmartSwitch as well, but I have no idea what the S/N on this phone is. It was originally a Sprint phone and was working fine, but I could never find the S/N. It is nowhere on the phone itself, and was not listed when I typed #*06#. All I have is the IMEI.
Finally, when it is in recovery, there is a message at the bottom that reads, "dm-verity verification failed".
Sorry for the bullet point style here, I am on mobile. If anyone can assist, I would be very grateful!
ebercon said:
Hi,
So I was trying to root my phone and it all went wrong. I have rooted tons of phones before, but never a Samsung (never again).
The phone will show the Samsung Boot screen, but then it either goes black, with a flashing blue LED, or it boots itself into recovery.
When I use ODIN, the flash fails at "system.img.ext4" whenever I use just the AP field. If I load all the fields in, it fails at "xbl.elf"
I got the firmware file from SamMobile, so I don't think that is the issue, but who knows. It's as if the phone no longer has an OS on it. I also tried using SmartSwitch as well, but I have no idea what the S/N on this phone is. It was originally a Sprint phone and was working fine, but I could never find the S/N. It is nowhere on the phone itself, and was not listed when I typed #*06#. All I have is the IMEI.
Finally, when it is in recovery, there is a message at the bottom that reads, "dm-verity verification failed".
Sorry for the bullet point style here, I am on mobile. If anyone can assist, I would be very grateful!
Click to expand...
Click to collapse
I'm new to the s7. long time lg man
on lg ussally means either ure trying to flash a non signed image or downgrade a qfused bootloader anti rollback which sprint is good for.
in dl mode after fail its not showing anything about binary and stuff in red is it
TheMadScientist420 said:
I'm new to the s7. long time lg man
on lg ussally means either ure trying to flash a non signed image or downgrade a qfused bootloader anti rollback which sprint is good for.
in dl mode after fail its not showing anything about binary and stuff in red is it
Click to expand...
Click to collapse
It does say something about binary in there. Binary 3 I believe. I'll have to try again to get the error.
ebercon said:
It does say something about binary in there. Binary 3 I believe. I'll have to try again to get the error.
Click to expand...
Click to collapse
sounds the firmware u are flashing is older than what you have on the device hence the fail
try to find newer firmware and try flashing it
download
Download official nougat from sam mobile then flash with Odin. It will definitely solve your problem
amol6630 said:
Download official nougat from sam mobile then flash with Odin. It will definitely solve your problem
Click to expand...
Click to collapse
I may try this as well. I flashed the newest firmware I could find other than Nougat and I now have it booting all the way up and then after about a minute, it loops again. It is at least further along than before.
I just remembered one detail: The original issue began when I flashed a modified boot.img to the phone during a rooting attempt. Could this be what is still causing the issue and preventing a reformatting of the phone from solving the issue? So lost with this thing...
Try with latest firmware + pit file + tick re-partition
ebercon said:
I may try this as well. I flashed the newest firmware I could find other than Nougat and I now have it booting all the way up and then after about a minute, it loops again. It is at least further along than before.
I just remembered one detail: The original issue began when I flashed a modified boot.img to the phone during a rooting attempt. Could this be what is still causing the issue and preventing a reformatting of the phone from solving the issue? So lost with this thing...
Click to expand...
Click to collapse
Sorry to revive this thread but did this work cause its currently happening to me
If your phone is an original, S/N may be engraved in the back... it's a little bit hard to note but put a spotlight near it so that you can identify it better.
hhh ^^
Phone just went into a bootloop after installing an update.
Tried Sony's companion multiple times and it didn't work, i had the same bootloop although the the process finishes.
I'm trying Firmware tool now, but It failed, but I'm not sure if it was because I didn't fine a proper TFT and had to build one.
Any help, guides will be appreciated. especially with TFT.
aGoGo said:
Phone just went into a bootloop after installing an update.
Tried Sony's companion multiple times and it didn't work, i had the same bootloop although the the process finishes.
I'm trying Firmware tool now, but It failed, but I'm not sure if it was because I didn't fine a proper TFT and had to build one.
Any help, guides will be appreciated. especially with TFT.
Click to expand...
Click to collapse
Have you tried Flashtool? It should sort it out. If you need to keep your data, don't check any of the boxes under "Wipe" collumn. If that doesn't work, then do it again with checking all those boxes under Wipe, but you will loose your data.
Atrax2010 said:
Have you tried Flashtool? It should sort it out. If you need to keep your data, don't check any of the boxes under "Wipe" collumn. If that doesn't work, then do it again with checking all those boxes under Wipe, but you will loose your data.
Click to expand...
Click to collapse
I'll give it a try again.
I don't care about the data so wiping everything will not be an issue.
My problem was just trying to download the files from a website. Got them for xperiafirm, but I don't know if I did not build the files right.
Will give it a try after work.
aGoGo said:
I'll give it a try again.
I don't care about the data so wiping everything will not be an issue.
My problem was just trying to download the files from a website. Got them for xperiafirm, but I don't know if I did not build the files right.
Will give it a try after work.
Click to expand...
Click to collapse
That's why you should use Flashtool, it has Xperifirm built in, just pick your model and region (make sure it's Customized variant of the firmware, not carrier branded), and the Flashtool will build it properly.
Hope you sort it out, let us know.
Cheers.
EDIT: Oh, and disabling antivirus helps sometimes, my Nod32 doesn't like ADB and phone flashers in general, it would sometimes interrupt the flashing.
Nothing worked.
Tried multiple tft images, making my own and Xperia companion.
Any other suggestions?