Related
I just installed the cyanogen 10 mod to my blaze and tried it. i went to this file manager that told me to reroot my phone so that I may be able to use it better. I went to odin to reroot it again but i accidentally used the original blaze.pit file on it and when it rebooted it showed me the original samsung starter instead of the cyanogen mod starter. That wasn't the problem, the problem was it never went in to the phones home screen or apps. Instead it continues to show the samsung logo and the flying android over and over again. I tried using the SGH-T769-hitsquad tar file to fix it (i need to mention that i bricked it once before and used this tar file to fix it) but it keeps taking me to the samsung logo. I can't even try to factory restore it because it just starts acting strange when I go to the menu. I can still go into download mode, i've gone searching for a file or anything to help me fix it but i can't find anything. Please, any suggestions?!
Here's a link to stock Tmo Blaze tar's from GB to ICS. ICS is the UVLH5 file. I suggest download that one.. then flash that file through odin.. dont include a Blaze pit file. just PDA file which is the one you'll download.
EDIT:
They're the ones ontop of the page that says Firmwares for SGH-T769 - USA (T-Mobile)
Let me know if it works for you.
EDIT:
They're the ones ontop of the page that says Firmwares for SGH-T769 - USA (T-Mobile)
Let me know if it works for you. [/QUOTE]
Had to factory reset it and wipe the catches, but it worked in the end. THANK YOU !!
EDIT:
They're the ones ontop of the page that says Firmwares for SGH-T769 - USA (T-Mobile)
Let me know if it works for you.
Click to expand...
Click to collapse
Also, i want to know if i can still root it again?
crzye101234 said:
Also, i want to know if i can still root it again?
Click to expand...
Click to collapse
Yeah, all you need is to reflash cwm through odin or if you still have cwm just flash a superuser or supersu zip.
crzye101234 said:
Also, i want to know if i can still root it again?
Click to expand...
Click to collapse
Yeah. Just Odin reflash CWM. then flash the superuse.zip
anactoraaron said:
Yeah, all you need is to reflash cwm through odin or if you still have cwm just flash a superuser or supersu zip.
Click to expand...
Click to collapse
Which superuser.zip should i use?
This thread should help you.
Just use that superuser.zip file, unless you want SuperSU, which I think it's better,
unicorndust98 said:
This thread should help you.
Just use that superuser.zip file, unless you want SuperSU, which I think it's better,
Click to expand...
Click to collapse
alright, i flashed the super user but now my phone keeps getting slowed down and when it locks it won't turn on the screen for a while then everything just resets. it also freezes when starting. What happened now?
or do i have to wipe the caches and data again?
nvm, i did have to factory restore it. Thank you for the help
crzye101234 said:
alright, i flashed the super user but now my phone keeps getting slowed down and when it locks it won't turn on the screen for a while then everything just resets. it also freezes when starting. What happened now?
or do i have to wipe the caches and data again?
nvm, i did have to factory restore it. Thank you for the help
Click to expand...
Click to collapse
Yeah.. after EVERY PROBLEM... I'd recommend nandroiding, then wiping stuff.. if that doesn't help.. THEN start to ask. Glad I could help.
Sent from my SGH-T769 using xda app-developers app
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Boot into recovery and do a factory reset.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Boot into recovery and do a factory reset.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I've tried that a few times already. No luck thus far
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
What baseband are you on ?
jlyle said:
What baseband are you on ?
Click to expand...
Click to collapse
i was on vrbmf1 when i got it back but ive been trying to flash back to the stock to hopefully get out of the "unauthorized software" screen. when i tried to wipe system and data and then restart from the stock recovery menu, i got an error message saying that the directory /system didnt exist, yet ive tried flashing back to stock twice and both processes finished through odin
ImBarone said:
i was on vrbmf1 when i got it back but ive been trying to flash back to the stock to hopefully get out of the "unauthorized software" screen. when i tried to wipe system and data and then restart from the stock recovery menu, i got an error message saying that the directory /system didnt exist, yet ive tried flashing back to stock twice and both processes finished through odin
Click to expand...
Click to collapse
Are you 100% sure you was on MF1 and Verizon did not ship it to you with 4.3.
If you was on MF1 Odin should flash fine and resolve any issues. If you was on 4.3 than you have issues if you ran Odin
jlyle said:
Are you 100% sure you was on MF1 and Verizon did not ship it to you with 4.3.
If you was on MF1 Odin should flash fine and resolve any issues. If you was on 4.3 than you have issues if you ran Odin
Click to expand...
Click to collapse
1000% sure that it was 4.1.2 and MF1 because it was trying to push an OTA update that i kept canceling. should i attempt reflashing through odin again? and if so could you link me to something specifically i should flash and possibly some instructions because ive been without a phone for 2 weeks and wouldnt like to wait til october for another one....
thanks
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
If it was fixed or replaced by Samsung they usually update to newest software before returning it. If it was on 4.3 and you tried to unlock it is now bricked beyond our ability to repair at this time.Can't unlock, flash custom recovery or downgrade to 4.1.2 or lower or it will brick. If was on 4.1.2 just need to Odin stock tar.If it hangs then a Factory reset in stock recovery will usually fix it. Need more info on what build you were actually on when started.
prdog1 said:
If it was fixed or replaced by Samsung they usually update to newest software before returning it. If it was on 4.3 and you tried to unlock it is now bricked beyond our ability to repair at this time.Can't unlock, flash custom recovery or downgrade to 4.1.2 or lower or it will brick. If was on 4.1.2 just need to Odin stock tar.If it hangs then a Factory reset in stock recovery will usually fix it. Need more info on what build you were actually on when started.
Click to expand...
Click to collapse
im completely sure it was NOT 4.3 though. it flashed fine when i ran this http://forum.xda-developers.com/showthread.php?t=2046439 i just forgot to flash the bootloader unlock through recovery so then i tried reflashing stock and now im here. and where could you point me in the direction of a stock tar and some instructions because ive been using the ones on the original thread i linked with no luck
Remove .tar from zip and flash in Odin. If was on MF! it should fix with no more than a factory reset in stock recovery. Then run Beans casual to reroot and unlock.
http://www.androidfilehost.com/?fid=23134718111254196
http://forum.xda-developers.com/showthread.php?t=2332825
prdog1 said:
Remove .tar from zip and flash in Odin. If was on MF! it should fix with no more than a factory reset in stock recovery. Then run Beans casual to reroot and unlock.
http://www.androidfilehost.com/user/settings-dev-files.php?action=show-files&flid=7111#
http://forum.xda-developers.com/showthread.php?t=2332825
Click to expand...
Click to collapse
the androidfilehost link is giving me this
"Access Denied
Sorry!
It looks like you don't have permission to access that folder. Make sure the url you are trying to access is correct.
http://forum.xda-developers.com/showthread.php?p=48799846
If you feel this is in error, please contact us."
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
ImBarone said:
the androidfilehost link is giving me this
"Access Denied
Sorry!
It looks like you don't have permission to access that folder. Make sure the url you are trying to access is correct.
http://forum.xda-developers.com/showthread.php?p=48799846
If you feel this is in error, please contact us."
Click to expand...
Click to collapse
Try again with this link.
http://www.androidfilehost.com/?fid=23134718111254196
jlyle said:
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
Click to expand...
Click to collapse
im currently flashing the root66.tar through odin hopefully my problem will be solved afterwards
jlyle said:
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
Click to expand...
Click to collapse
ok so i no luck with the root66.tar file im going to try the other one now. should i be checking the nand erase all box?
ImBarone said:
ok so i no luck with the root66.tar file im going to try the other one now. should i be checking the nand erase all box?
Click to expand...
Click to collapse
Leave everything in odin as is..dont check or uncheck anything
Make sure u put in PDA
Make sure you have a solid connection with cable .. that will cause issues too
Your in download mode right ? HA / just checking
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
Boot into download mode and on the screen where the option to continue or restart phone, choose to restart your phone. This worked for me just this morning, for some reason it bypasses the check.
Sent from my SCH-I535 using XDA Premium 4 mobile app
jlyle said:
Leave everything in odin as is..dont check or uncheck anything
Make sure u put in PDA
Make sure you have a solid connection with cable .. that will cause issues too
Click to expand...
Click to collapse
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
ImBarone said:
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
Click to expand...
Click to collapse
Odin will reboot your phone.. are you getting Pass in Odin ??
ImBarone said:
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
Click to expand...
Click to collapse
Yes. It is common for it to reboot but bootloop. Pull battery and then boot into stock recovery and factory reset. Then it should boot.
Sprint s6 edge it was boot looping only staying in Android for maybe 3-5 mins at a time. So i tried to flash it. I may have flashed 5.0.x to it. Now when I try to flash I can flash cm.bin, sboot and it always dies on boot.img. I really need some guidance on what i should try next.
Looking around shows boot.img not flashing is possibly the kernel but I am having trouble finding one that it will let me flash.
peterm20 said:
Sprint s6 edge it was boot looping only staying in Android for maybe 3-5 mins at a time. So i tried to flash it. I may have flashed 5.0.x to it. Now when I try to flash I can flash cm.bin, sboot and it always dies on boot.img. I really need some guidance on what i should try next.
Looking around shows boot.img not flashing is possibly the kernel but I am having trouble finding one that it will let me flash.
Click to expand...
Click to collapse
Were you originally on 5.1.1?
If so, are you having a hard time Odin-ing the stock rom?
Robbie Doo said:
Were you originally on 5.1.1?
If so, are you having a hard time Odin-ing the stock rom?
Click to expand...
Click to collapse
yes, it is a phone of a friend though I was trying to repair it. I downloaded the 5.1.1 from that slow sammoble site.
peterm20 said:
yes, it is a phone of a friend though I was trying to repair it. I downloaded the 5.1.1 from that slow sammoble site.
Click to expand...
Click to collapse
Since you were on 5.1.1 I don't think you would have any trouble Odining the stock ROM onto the phone. I've done it a few times and it worked OK. After you push the stock ROM you can root it if you want to.
Robbie Doo said:
Since you were on 5.1.1 I don't think you would have any trouble Odining the stock ROM onto the phone. I've done it a few times and it worked OK. After you push the stock ROM you can root it if you want to.
Click to expand...
Click to collapse
Well the problem is it won't flash past boot.img
As soon as boot.img is started it goes a green bar on Oden about 3/4 of the way and then goes FAILED! and oden disconnects the device.
peterm20 said:
Well the problem is it won't flash past boot.img
As soon as boot.img is started it goes a green bar on Oden about 3/4 of the way and then goes FAILED! and oden disconnects the device.
Click to expand...
Click to collapse
If you went from 5.1.1 to 5.0.X it's most likely hard bricked.
Soooperstar said:
If you went from 5.1.1 to 5.0.X it's most likely hard bricked.
Click to expand...
Click to collapse
Even if i can get in to download mode?
peterm20 said:
Even if i can get in to download mode?
Click to expand...
Click to collapse
Yea.... You have to stay within the same android version, ex. Any of the 5.1.1 updates. The firmware version that you're trying to restore with, is it OF7?
Soooperstar said:
Yea.... You have to stay within the same android version, ex. Any of the 5.1.1 updates. The firmware version that you're trying to restore with, is it OF7?
Click to expand...
Click to collapse
I think it is OF7.
peterm20 said:
I think it is OF7.
Click to expand...
Click to collapse
It should say it on the tar file. It's worth a try but you're probably dead. Here is the file if you need it but like I said, most likely you're done.
http://forum.xda-developers.com/showthread.php?t=3154757
peterm20 said:
Well the problem is it won't flash past boot.img
As soon as boot.img is started it goes a green bar on Oden about 3/4 of the way and then goes FAILED! and oden disconnects the device.
Click to expand...
Click to collapse
Which version of the Odin are you using?
Soooperstar said:
It should say it on the tar file. It's worth a try but you're probably dead. Here is the file if you need it but like I said, most likely you're done.
http://forum.xda-developers.com/showthread.php?t=3154757
Click to expand...
Click to collapse
It worked for me. I have a friend who did the same thing and thought the phone was a gonner. I told her I'd give it a try and I was able to Odin (v.3.10.6) to OF7, took the OTA to OH1 and flashed Wicked One SS v.3.0 from @dazednconfused and she says it's running perfect.
Also, @Soooperstar Odin file here.
JediMindTrixx said:
It worked for me. I have a friend who did the same thing and thought the phone was a gonner. I told her I'd give it a try and I was able to Odin (v.3.10.6) to OF7, took the OTA to OH1 and flashed Wicked One SS v.3.0 from @dazednconfused and she says it's running perfect.
Also, @Soooperstar Odin file here.
Click to expand...
Click to collapse
Your friend went from 5.1.1 to 5.0.X? That's the link I just gave him
Yes she did. Sorry about that, saw that afterwards.
Sent from a Galaxy S6 Edge... Far, Far, Away...
JediMindTrixx said:
Yes she did. Sorry about that, saw that afterwards.
Sent from a Galaxy S6 Edge... Far, Far, Away...
Click to expand...
Click to collapse
Interesting
Robbie Doo said:
Which version of the Odin are you using?
Click to expand...
Click to collapse
the latest one. I've seen various other flashing posts saying you should use a slightly older Oden.
Also side rant. I did a chat with samsung support and they said the Smart Switch recovery doesn't work with the S6? I cannot get it to verify the serial number of my phone (s6) and the broken one (s6 e)
peterm20 said:
the latest one. I've seen various other flashing posts saying you should use a slightly older Oden.
Also side rant. I did a chat with samsung support and they said the Smart Switch recovery doesn't work with the S6? I cannot get it to verify the serial number of my phone (s6) and the broken one (s6 e)
Click to expand...
Click to collapse
3.10.6 is what I use
peterm20 said:
the latest one. I've seen various other flashing posts saying you should use a slightly older Oden.
Also side rant. I did a chat with samsung support and they said the Smart Switch recovery doesn't work with the S6? I cannot get it to verify the serial number of my phone (s6) and the broken one (s6 e)
Click to expand...
Click to collapse
I'm not sure which version you are referring to as the latest one, but the only version that will work with what you're trying to accomplish is 3.10.6
Soooperstar said:
It should say it on the tar file. It's worth a try but you're probably dead. Here is the file if you need it but like I said, most likely you're done.
http://forum.xda-developers.com/showthread.php?t=3154757
Click to expand...
Click to collapse
Well your file got me way further than I've got before. I can get it to write the system.img in "BL" but if i use AP it fails about 1/2 the way through
peterm20 said:
Well your file got me way further than I've got before. I can get it to write the system.img in "BL" but if i use AP it fails about 1/2 the way through
Click to expand...
Click to collapse
Like I said from my knowledge, you should be hard bricked, but if someone else went from 5.1.1 to 5.0.X and back, you might want to find out what they did. Don't think it's possible
Okay, so I'm having this problem where my phone get stucks in a bootloop when I flash back to stock.
The only way it gets out of bootloop, is if I install root. The problem is I'm trying to go back to stock firmware for now, but my phone refuses to get out of the Samsung logo every single time I try and run stock.
My guess is it might have something to do with the partition.
I notice when I'm doing a factory reset/wipe.
It has consistently said how it can't mount, and I'm guessing something is wrong with my partition, because I got the right firmware for my phone. It's N-902T.
If anyone has advice on this, I'd greatly appreciate it. Right now, I have no choice but to run a rooted phone until I figure out a way to get back to stock.
Ive never seen this before
[email protected] said:
Ive never seen this before
Click to expand...
Click to collapse
Yeah, I've never seen this before either. But I've tried multiple times to simply factory reset/wipe and flash stock.
It simply stays on the Samsung logo every single time. Correct firmware and everything... I even tried smart switch and it didn't help either...
Staying rooted is the best thing you can do did you flash the wrong firmware
Sent from my SM-N920T using Tapatalk
Anthony092 said:
Yeah, I've never seen this before either. But I've tried multiple times to simply factory reset/wipe and flash stock.
It simply stays on the Samsung logo every single time. Correct firmware and everything... I even tried smart switch and it didn't help either...
Click to expand...
Click to collapse
Do this:
Backup your stuff you need first!!!
Flash root
Flash TWRP
FULL WIPE!!! EVERYTHING. Every single partition that shows, cache, internal, system, data...everything. Do it x3.
ODIN stock firmware
Jammol said:
Do this:
Backup your stuff you need first!!!
Flash root
Flash TWRP
FULL WIPE!!! EVERYTHING. Every single partition that shows, cache, internal, system, data...everything. Do it x3.
ODIN stock firmware
Click to expand...
Click to collapse
I'll try and do it and let you know how it goes.
Anthony092 said:
I'll try and do it and let you know how it goes.
Click to expand...
Click to collapse
@Jammol is correct. This method should work. Going back to stock after being rooted almost always requires a full factory reset for our device. I had to do it on my phone.
Jammol said:
Do this:
Backup your stuff you need first!!!
Flash root
Flash TWRP
FULL WIPE!!! EVERYTHING. Every single partition that shows, cache, internal, system, data...everything. Do it x3.
ODIN stock firmware
Click to expand...
Click to collapse
Akw6190 said:
@Jammol is correct. This method should work. Going back to stock after being rooted almost always requires a full factory reset for our device. I had to do it on my phone.
Click to expand...
Click to collapse
I did it, didn't work for me. Still stuck at the Samsung logo, wiped everything too..
Just to add, a few more things I did notice.
After I flashed, My System Binary is listed as Samsung Official, but the System Status is still listed as Custom, this is after I flash Stock.
Then When I go back into Recovery, to another wipe just in case after flashing, it keeps saying.
DM-Verification failed......
Need to check DRK fist...
Also says E:failed to mount/preload (No such file or directory)
Anthony092 said:
I did it, didn't work for me. Still stuck at the Samsung logo, wiped everything too..
Click to expand...
Click to collapse
Alright, try this method:
Flash latest stock firmware in ODIN
Once it's done flashing, reboot to stock recovery
do a factory reset from stock recovery
It should boot after that. This is the method I used.
---------- Post added at 10:39 PM ---------- Previous post was at 10:35 PM ----------
Anthony092 said:
Just to add, a few more things I did notice.
After I flashed, My System Binary is listed as Samsung Official, but the System Status is still listed as Custom, this is after I flash Stock.
Then When I go back into Recovery, to another wipe just in case after flashing, it keeps saying.
DM-Verification failed......
Need to check DRK fist...
Also says E:failed to mount/preload (No such file or directory)
Click to expand...
Click to collapse
In this case, use the method I posted above, but try re-downloading the latest firmware for your device from sammobile.com and flash that. It should overwrite all of your partitions and then simply require a factory reset from stock recovery to boot. If that doesn't work, you may need to flash the PIT file for your device, which I'm sure can be found somewhere around here. I'm not sure the exact method to do that, however.
Akw6190 said:
Alright, try this method:
Flash latest stock firmware in ODIN
Once it's done flashing, reboot to stock recovery
do a factory reset from stock recovery
It should boot after that. This is the method I used.
Click to expand...
Click to collapse
I tried already, didn't work, but I'll keep looking to see if I can fix it. The minute I Put root back on my phone, it immediately started working, however every single time I try to go back to stock, it never gets past the Samsung Logo, No matter how many times I do a wipe. Plus, I don't understand why it keeps showing my device as custom, but the binary as samsung official, after I'm flashing stock...
Anthony092 said:
I tried already, didn't work, but I'll keep looking to see if I can fix it. The minute I Put root back on my phone, it immediately started working, however every single time I try to go back to stock, it never gets past the Samsung Logo, No matter how many times I do a wipe. Plus, I don't understand why it keeps showing my device as custom, but the binary as samsung official, after I'm flashing stock...
Click to expand...
Click to collapse
Hm. Unfortunately this is beyond my realm of comprehension. I've read that flashing the PIT file could help, but I don't know how to do that, unfortunately. I'd do some research on that if I were you.
Anthony092 said:
I tried already, didn't work, but I'll keep looking to see if I can fix it. The minute I Put root back on my phone, it immediately started working, however every single time I try to go back to stock, it never gets past the Samsung Logo, No matter how many times I do a wipe. Plus, I don't understand why it keeps showing my device as custom, but the binary as samsung official, after I'm flashing stock...
Click to expand...
Click to collapse
Try this. Go into developer mode and see if your oem unlocking is off. Turn it on. Make sure you have Odin version .7 and make sure you update to the latest firmware for you device.
Akw6190 said:
Hm. Unfortunately this is beyond my realm of comprehension. I've read that flashing the PIT file could help, but I don't know how to do that, unfortunately. I'd do some research on that if I were you.
Click to expand...
Click to collapse
Well you tried, thank you I appreciate the help nonetheless. I'll try and research it more, for now I'll just stay rooted and explore and find options to fix it, enjoy your day.
Anthony092 said:
Well you tried, thank you I appreciate the help nonetheless. I'll try and research it more, for now I'll just stay rooted and explore and find options to fix it, enjoy your day.
Click to expand...
Click to collapse
You too, buddy. If you figure it out, report back and let us know. It may help someone in the future.
guaneet said:
Try this. Go into developer mode and see if your oem unlocking is off. Turn it on. Make sure you have Odin version .7 and make sure you update to the latest firmware for you device.
Click to expand...
Click to collapse
My OEM is on, I'm downloading the lastest firmware. I'll report back with my results
Anthony092 said:
My OEM is on, I'm downloading the lastest firmware. I'll report back with my results
Click to expand...
Click to collapse
Here is a link to the latest firmware just in case. Really fast download compared to sammobile
http://forum.xda-developers.com/showthread.php?p=64366446
guaneet said:
Here is a link to the latest firmware just in case. Really fast download compared to sammobile
http://forum.xda-developers.com/showthread.php?p=64366446
Click to expand...
Click to collapse
Thank you, very much appreciated it. I'll download from there instead =)
I've been pondering this one all day. It shouldn't be a corrupt storage device that's now dead because it would work regardless of root or not. The pit file suggested earlier should do the trick as it writes over all partitions of your device.
Another thing. It says both official and custom in download mode is an indication that something get wiped. What firmware have you been trying to flash with odin
S?ent from my SM-N920T using Tapatalk
Jammol said:
I've been pondering this one all day. It shouldn't be a corrupt storage device that's now dead because it would work regardless of root or not. The pit file suggested earlier should do the trick as it writes over all partitions of your device.
Another thing. It says both official and custom in download mode is an indication that something get wiped. What firmware have you been trying to flash with odin
S?ent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
I was flashing N902TUVU2COI5, however I'm going to try and flash the latest firmware and see how it goes.
Unfortunately, I haven't found anything exactly telling me how to the pit file, so I'm for now going to stay away from that...just waiting for the latest firmware to download and I'll flash it and post my results.
I've looked everywhere and haven't found anything on rooting for the 930az. Found an xda rep that said his root or the root he got if from was for all s7 . Followed the instructions step by step till I reached flashing ,then my phone got stuck in a bootloop .luckily I found a post on the inputs of Oden to return to stock but I'm still persistent on finding a root for it please help!!!
Jay351 said:
I've looked everywhere and haven't found anything on rooting for the 930az. Found an xda rep that said his root or the root he got if from was for all s7 . Followed the instructions step by step till I reached flashing ,then my phone got stuck in a bootloop .luckily I found a post on the inputs of Oden to return to stock but I'm still persistent on finding a root for it please help!!!
Click to expand...
Click to collapse
When you say flashing, fhalsing what exactly got you the bootloop? Was it flashing the engineering Boot.img through Odin or the fix S7 zip through Flashfire... Or something else?
I don't have a Cricket branded S7, but always offering to help you research.
Sent from my SM-G930P using Tapatalk
POWerSUrgeSW3 said:
When you say flashing, fhalsing what exactly got you the bootloop? Was it flashing the engineering Boot.img through Odin or the fix S7 zip through Flashfire... Or something else?
I don't have a Cricket branded S7, but always offering to help you research.
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
Thanks for the help it was https://youtu.be/KawiIZ4bAV8
As soon as I got to the boot.img and downloaded it to my phone that when it started.
Jay351 said:
Thanks for the help it was https://youtu.be/KawiIZ4bAV8
As soon as I got to the boot.img and downloaded it to my phone that when it started.
Click to expand...
Click to collapse
Only a few things I can think to ask:
1) You are using the Odin version by PrinceComsy... not the original version of Odin?
2) When you download the engineering boot image, you're downloading it for your phone model (S7 for S7, S7 Edge for the S7 Edge)? Maybe you accidentally downloaded the wrong one?
3) When uploading the boot image through Odin, the boot image TAR file is in the AP slot of Odin?
4) Last thing I can think is easy, is the boot image is still a TAR file correct? Its not a ZIP or any other file extension?
Have you tried downloading the image again? I invite you to check out a thread I'm part of if you want another location to download the S7 engineering boot image, that thread located here and the boot image file can be downloaded directly from here
POWerSUrgeSW3 said:
Only a few things I can think to ask:
1) You are using the Odin version by PrinceComsy... not the original version of Odin?
Yes and I tried the original also
2) When you download the engineering boot image, you're downloading it for your phone model (S7 for S7, S7 Edge for the S7 Edge)? Maybe you accidentally downloaded the wrong one?
Correct s7 for s7
3) When uploading the boot image through Odin, the boot image TAR file is in the AP slot of Odin?
Yes
4) Last thing I can think is easy, is the boot image is still a TAR file correct? Its not a ZIP or any other file extension?
I made sure it was still a tar file.
Thanks for your help I'll check it out
Click to expand...
Click to collapse
Jay351 said:
POWerSUrgeSW3 said:
Only a few things I can think to ask:
1) You are using the Odin version by PrinceComsy... not the original version of Odin?
Yes and I tried the original also
2) When you download the engineering boot image, you're downloading it for your phone model (S7 for S7, S7 Edge for the S7 Edge)? Maybe you accidentally downloaded the wrong one?
Correct s7 for s7
3) When uploading the boot image through Odin, the boot image TAR file is in the AP slot of Odin?
Yes
4) Last thing I can think is easy, is the boot image is still a TAR file correct? Its not a ZIP or any other file extension?
I made sure it was still a tar file.
Thanks for your help I'll check it out
Click to expand...
Click to collapse
You're welcome, just trying to figure it out. Though I see this is a common thing, so I wonder what is different with the Cricket version?
And you're rooting the Nougat version of the phone? This seems to be a topic floating around with no one explaining it. I've tried looking to see if maybe the processor might be somehow a "reduced" version of the 820 compared to the others... but everything makes it look like it should work.
Only other thing I would say is go back through all the steps, and make sure you're not accidentally skipping one. I did that a bunch of times when I first started off. I ended up printing off instructions and making note edits. Took me a few different sets of instructions until I found a formula that worked for my G930P
Click to expand...
Click to collapse
POWerSUrgeSW3 said:
Jay351 said:
You're welcome, just trying to figure it out. Though I see this is a common thing, so I wonder what is different with the Cricket version?
And you're rooting the Nougat version of the phone? This seems to be a topic floating around with no one explaining it. I've tried looking to see if maybe the processor might be somehow a "reduced" version of the 820 compared to the others... but everything makes it look like it should work.
Only other thing I would say is go back through all the steps, and make sure you're not accidentally skipping one. I did that a bunch of times when I first started off. I ended up printing off instructions and making note edits. Took me a few different sets of instructions until I found a formula that worked for my G930P
Click to expand...
Click to collapse
I'm sorry no we haven't received the update yet I'm still on 6.0.1. Do you mean like mixing up the steps and finding which worked with your phone?
Click to expand...
Click to collapse
Jay351 said:
POWerSUrgeSW3 said:
I'm sorry no we haven't received the update yet I'm still on 6.0.1. Do you mean like mixing up the steps and finding which worked with your phone?
Click to expand...
Click to collapse
Oh I'll have to go back and do some rereading then, because I thought I saw some websites saying that phone was already on Nougat. If you're still on MM this should be easier I would think... hmmm
For me, it took me about 4 or 5 different threads of talking about how they rooted their Sprint S7 phone, for me to find the right instructions for myself to root my phone. But I know along the way I would miss a step, then my phone wouldn't boot or bootloop like yours. That's why I went back and printed out instructions and checked off to make sure I didn't skip anything. After awhile I could wrap my head around it.
Just saying we are all human, so it's easy to skip a step. Though it doesn't seem like you're the only one having this problem. But if all the branded US phones are pretty much rooted one way or another, I don't see why yours would be any different.
Click to expand...
Click to collapse
POWerSUrgeSW3 said:
Jay351 said:
Oh I'll have to go back and do some rereading then, because I thought I saw some websites saying that phone was already on Nougat. If you're still on MM this should be easier I would think... hmmm
For me, it took me about 4 or 5 different threads of talking about how they rooted their Sprint S7 phone, for me to find the right instructions for myself to root my phone. But I know along the way I would miss a step, then my phone wouldn't boot or bootloop like yours. That's why I went back and printed out instructions and checked off to make sure I didn't skip anything. After awhile I could wrap my head around it.
Just saying we are all human, so it's easy to skip a step. Though it doesn't seem like you're the only one having this problem. But if all the branded US phones are pretty much rooted one way or another, I don't see why yours would be any different.
Click to expand...
Click to collapse
Your probably right I'll try those steps again and see if anything changes. The only model I see that's close to g930az would be the at&t which is g930a. I know I got lucky with the last attempt to try with it in soft brick. I just don't want to try to many and it be completely screwed. Because on cricket you have to buy all of you phones up front well at least I had to with mine. I'll try it again and let you know if it worked or I have a paper weight haha. Thanks again
Click to expand...
Click to collapse
Jay351 said:
POWerSUrgeSW3 said:
Your probably right I'll try those steps again and see if anything changes. The only model I see that's close to g930az would be the at&t which is g930a. I know I got lucky with the last attempt to try with it in soft brick. I just don't want to try to many and it be completely screwed. Because on cricket you have to buy all of you phones up front well at least I had to with mine. I'll try it again and let you know if it worked or I have a paper weight haha. Thanks again
Click to expand...
Click to collapse
With following the steps you are and what you have happening, you should be OK with being able Odin back to factory firmware.
Yeah Cricket is kind of the double edge sword, you have to buy the phone up front, but they have CHEAP prices for good service. I had them when I first moved to Arizona and would have kept them, if I didn't travel so much.
Report back if anything changes.
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
Jay351 said:
I've looked everywhere and haven't found anything on rooting for the 930az. Found an xda rep that said his root or the root he got if from was for all s7 . Followed the instructions step by step till I reached flashing ,then my phone got stuck in a bootloop .luckily I found a post on the inputs of Oden to return to stock but I'm still persistent on finding a root for it please help!!!
Click to expand...
Click to collapse
hey can you help get my s7 g930az back to stock. i also happen to be stuck in a bootloop and i've searched everywhere and nothing
leonardo879 said:
hey can you help get my s7 g930az back to stock. i also happen to be stuck in a bootloop and i've searched everywhere and nothing
Click to expand...
Click to collapse
Do you have the stock firmware and Odin? Flash that will get you back to stock and functional. Does take awhile to flash the full imagine, but can pretty much fix any software brick issues.
Sent from my SM-G930P using Tapatalk
POWerSUrgeSW3 said:
Do you have the stock firmware and Odin? Flash that will get you back to stock and functional. Does take awhile to flash the full imagine, but can pretty much fix any software brick issues.
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
Yes i have the stock firmware and Odin but it always fails. is there any other way to fix it? i tried smart switch and it stops at 69% and it says error so idk what else to try.
leonardo879 said:
Yes i have the stock firmware and Odin but it always fails. is there any other way to fix it? i tried smart switch and it stops at 69% and it says error so idk what else to try.
Click to expand...
Click to collapse
What's the failure error? OEM Unlock in Android was turned on correct?
Sent from my SM-G930P using Tapatalk
POWerSUrgeSW3 said:
What's the failure error? OEM Unlock in Android was turned on correct?
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
It says "Encrypt Error" in smart switch. What does OEM Unlock mean?
leonardo879 said:
It says "Encrypt Error" in smart switch. What does OEM Unlock mean?
Click to expand...
Click to collapse
By default the phones are locked so someone can't steal your phone and Reimage it. If you boot your phone up after trying to flash do you get an FPR or some sort of error like that?
Sent from my SM-G930P using Tapatalk
POWerSUrgeSW3 said:
By default the phones are locked so someone can't steal your phone and Reimage it. If you boot your phone up after trying to flash do you get an FPR or some sort of error like that?
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
No it doesn't. The phone is just stuck in a boot loop after i tried installing a .tar file in Odin that i got from a youtube video showing how to root it but it doesn't work so now i'm stuck on he boot loop.
leonardo879 said:
No it doesn't. The phone is just stuck in a boot loop after i tried installing a .tar file in Odin that i got from a youtube video showing how to root it but it doesn't work so now i'm stuck on he boot loop.
Click to expand...
Click to collapse
Yes but if you try to Odin back to the stock firmware what happens then?
Sent from my SM-G930P using Tapatalk
POWerSUrgeSW3 said:
Yes but if you try to Odin back to the stock firmware what happens then?
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
It says "Fail. Model Mismatch fail" something a long that
leonardo879 said:
It says "Fail. Model Mismatch fail" something a long that
Click to expand...
Click to collapse
I would recommend going to sammobile or updato to get the firmware for your phone. Sounds like you have the wrong model. If you need help I can help in an hour or so when I get home.
Sent from my SM-G930P using Tapatalk