Database Info

[Q] [HELP] cyanogen 10 reroot gone wrong on galaxy s blaze

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

My phone refuses to go back to stock, it only works if I stay rooted, please help....

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.

S6 - Boot Loop - No Recovery - HELP!!!

Hi All,
I a strange thing happened yesterday. My S6 got stuck and when I did a force restart it ended up in a boot loop. To worsen the problem my device had reactivation enabled. I found out that my recovery is not loading also. I guess its due to the reactivation security.
So far I have tried the following:
1. Tried to install the stock firmware
2. Tried to install new stock firmware (marshmellow)
3. Tried Kies and Smart Connect (did not do anything)
I'm pretty much clueless at this point. Any help is appreciated.
Thanks in advanced...

Any captains to help?

Maybe try flashing ONLY the 'recovery.img' inside the firmware file, and if you can get into the stock recovery after that then clear cache and wipe, then try to flash firmware again

emcardle660 said:
Maybe try flashing ONLY the 'recovery.img' inside the firmware file, and if you can get into the stock recovery after that then clear cache and wipe, then try to flash firmware again
Click to expand...
Click to collapse
Thank you very much for the input. Do you feel that when I flash the original firmware it did not apply the recovery.img that was inside the tar ball? I could manage to create a tar ball with only the recovery image but in that case will it trigger the knox counter and void warranty?
Again, I really appreciate your feedback. Thanks mate

BTW I tried with both Odin and smart connect. Nothing helped. They both complete and say it went well but after restart its simply another boot loop

When you flash stock with odin it should say pass and should boot or visit Samsung for fix

tazaga said:
When you flash stock with odin it should say pass and should boot or visit Samsung for fix
Click to expand...
Click to collapse
It does say PASS. But when it reboots I end up with the boot loop again.
BTW Reactivation lock is ON. Could this be a problem?

Hi Dude
I just flashed my other halfs S6 loads and discovered a working Recovery was Arter97's after MUCH soft bricks etc
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/
Flashable via odin
For me tho if worst comes to worst getting a fresh rom from sammobile worked okay
Hope you get sorted bro

Jonny5isalivetm said:
Hi Dude
I just flashed my other halfs S6 loads and discovered a working Recovery was Arter97's after MUCH soft bricks etc
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/
Flashable via odin
For me tho if worst comes to worst getting a fresh rom from sammobile worked okay
Hope you get sorted bro
Click to expand...
Click to collapse
Thank you very much. I will surely try this tonight. I will post my findings here.

Jonny5isalivetm said:
Hi Dude
I just flashed my other halfs S6 loads and discovered a working Recovery was Arter97's after MUCH soft bricks etc
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/
Flashable via odin
For me tho if worst comes to worst getting a fresh rom from sammobile worked okay
Hope you get sorted bro
Click to expand...
Click to collapse
One quick question before I flash this and trip knox. On your device was Reactivation set to ON?

I was not worried about Knox so much so did not pay attention to it. What Warranty Custom ROMs FTW
Where does it mention Reactivation ? In Download mode ?
I can check later when the misses gets home for ya
One thing I did notice is every recovery I have tried the ones that work now say "recovery not selinux enforcing" or something along those lines..(when entering recovery)

Jonny5isalivetm said:
I was not worried about Knox so much so did not pay attention to it. What Warranty Custom ROMs FTW
Where does it mention Reactivation ? In Download mode ?
I can check later when the misses gets home for ya
One thing I did notice is every recovery I have tried the ones that work now say "recovery not selinux enforcing" or something along those lines..(when entering recovery)
Click to expand...
Click to collapse
Ha ha, very true about Knox. And yes in download mode it shows if Reactivation is ON or OFF. The purpose is to not allow anyone to factory reset the device if this is turned on. Hence the unavailability of the recovery mode.
I would really appreciate it if you could check and let me know. Thanks in advance mate

OK will do but she at work till 5

Jonny5isalivetm said:
OK will do but she at work till 5
Click to expand...
Click to collapse
No worries mate, thanks for been available and the guidance...

Jonny5isalivetm said:
OK will do but she at work till 5
Click to expand...
Click to collapse
Any updates please?

I just got the phone lol soz
turns out download mode in MM has no information is there somewhere else I could find out what you need to know ?

Jonny5isalivetm said:
I just got the phone lol soz
turns out download mode in MM has no information is there somewhere else I could find out what you need to know ?
Click to expand...
Click to collapse
Sorry for the silence on this. But I decided to hand over the device for warranty claim. At no point I did trip Knox so they accepted for warranty claim process. Ideally I should get it back end of this week.
I will update you all on this matter as soon as I have more details.

MAHASONA said:
Sorry for the silence on this. But I decided to hand over the device for warranty claim. At no point I did trip Knox so they accepted for warranty claim process. Ideally I should get it back end of this week.
I will update you all on this matter as soon as I have more details.
Click to expand...
Click to collapse
hello i had the same problem after updating to marshmallow was stuck in boot loop what i did to fix it is go into recovery power home button and volume up factory reset and wipe cache rebooted phone and it worked hope it works for you

huzi7868 said:
hello i had the same problem after updating to marshmallow was stuck in boot loop what i did to fix it is go into recovery power home button and volume up factory reset and wipe cache rebooted phone and it worked hope it works for you
Click to expand...
Click to collapse
Thanks for the info. But as mentioned recovery is not available in Reactiation - ON mode. Its a security feature they provide to prevent people from stealing your phone.

Can't you disable reactivation lock by deleting your Samsung account ? : http://androiding.how/unable-to-disable-reactivation-lock-on-galaxy-s6-try-this-fail-safe-trick/

Unbrick image for Marshmallow 6.0.1 PD1

Can someone who has updated to the new PD1 firmware please make an unbrick image for me?
Odin hard bricked my phone last night when I was trying to update. It went through, froze on the Verizon slash screen, then shut off with the red notification LED blinking. I pulled out the battery and tried to restart it, but with no luck. I've tried the PB1 unbrick image from another thread but I can't make it work so I think my phone might be stuck on the new firmware, but I don't know.
I need my phone back! Any help is appreciated.

akaplo said:
Can someone who has updated to the new PD1 firmware please make an unbrick image for me?
Odin hard bricked my phone last night when I was trying to update. It went through, froze on the Verizon slash screen, then shut off with the red notification LED blinking. I pulled out the battery and tried to restart it, but with no luck. I've tried the PB1 unbrick image from another thread but I can't make it work so I think my phone might be stuck on the new firmware, but I don't know.
I need my phone back! Any help is appreciated.
Click to expand...
Click to collapse
I am in the same boat. Please let me know if you get an unbrick image..

So is this a soft brick or a hard brick. It sounds like a soft brick, try re-flashing PB1 kernel, or at worst odin a complete PB1 Stock re-flash. I have had lots of trial and error experience so just try flashing PB1 firmware only without bootloaders and this should fix your issue. If it is a hard brick all I need to know is if you are running a dev edition phone or retail. I just booted up sixperiences s7 edge rom so I can dump files from the new PD1 image, bootloaders and all.
Chay555 said:
I am in the same boat. Please let me know if you get an unbrick image..
Click to expand...
Click to collapse

akaplo said:
Can someone who has updated to the new PD1 firmware please make an unbrick image for me?
Odin hard bricked my phone last night when I was trying to update. It went through, froze on the Verizon slash screen, then shut off with the red notification LED blinking. I pulled out the battery and tried to restart it, but with no luck. I've tried the PB1 unbrick image from another thread but I can't make it work so I think my phone might be stuck on the new firmware, but I don't know.
I need my phone back! Any help is appreciated.
Click to expand...
Click to collapse
Good news! I was able to get the phone booted up again. Bad News: Its back on Lollipop firmware (BP1.) So what I did was I used the files from jrkuses working root method 3/4/16 and flashed them through Odin. First I flashed the PB1 unbrick image in his OK3 file, then I flashed the Nk2 kernel also included in the OK3 file, and last I flashed a file called VZW_BPB1_KERNEL_ONLY.tar.md5 also in the folder. Flashing those got me booted back on 5.0 safely.
---------- Post added at 08:57 PM ---------- Previous post was at 08:55 PM ----------
stellar0322 said:
So is this a soft brick or a hard brick. It sounds like a soft brick, try re-flashing PB1 kernel, or at worst odin a complete PB1 Stock re-flash. I have had lots of trial and error experience so just try flashing PB1 firmware only without bootloaders and this should fix your issue. If it is a hard brick all I need to know is if you are running a dev edition phone or retail. I just booted up sixperiences s7 edge rom so I can dump files from the new PD1 image, bootloaders and all.
Click to expand...
Click to collapse
Thank You very much for the offered help. I just found a fix using jrkuses files in his root method and am now up and running again. Again Thank You.

stellar0322 said:
So is this a soft brick or a hard brick. It sounds like a soft brick, try re-flashing PB1 kernel, or at worst odin a complete PB1 Stock re-flash. I have had lots of trial and error experience so just try flashing PB1 firmware only without bootloaders and this should fix your issue. If it is a hard brick all I need to know is if you are running a dev edition phone or retail. I just booted up sixperiences s7 edge rom so I can dump files from the new PD1 image, bootloaders and all.
Click to expand...
Click to collapse
It's definitely a hard brick. I can't boot into recovery, download mode, or anything! I've got a retail phone. You'd be a lifesaver if it works!

Chay555 said:
Thank You very much for the offered help. I just found a fix using jrkuses files in his root method and am now up and running again. Again Thank You.
Click to expand...
Click to collapse
Were you able to boot the phone during your ordeal? I can't get mine to do anything.

akaplo said:
Were you able to boot the phone during your ordeal? I can't get mine to do anything.
Click to expand...
Click to collapse
I was able to boot and I kept freezing at the Verizon splash screen. I did not realize that you couldn't even boot up. It was just a softbrick on my end. I hope you can get everything sorted out
---------- Post added at 09:55 PM ---------- Previous post was at 09:34 PM ----------
stellar0322 said:
So is this a soft brick or a hard brick. It sounds like a soft brick, try re-flashing PB1 kernel, or at worst odin a complete PB1 Stock re-flash. I have had lots of trial and error experience so just try flashing PB1 firmware only without bootloaders and this should fix your issue. If it is a hard brick all I need to know is if you are running a dev edition phone or retail. I just booted up sixperiences s7 edge rom so I can dump files from the new PD1 image, bootloaders and all.
Click to expand...
Click to collapse
Question. Everytime I flash the PD1 firmware on my phone it always gets stuck on the Verizon splash screen. Am I doing something wrong?

Chay555 said:
I was able to boot and I kept freezing at the Verizon splash screen. I did not realize that you couldn't even boot up. It was just a softbrick on my end. I hope you can get everything sorted out
---------- Post added at 09:55 PM ---------- Previous post was at 09:34 PM ----------
Question. Everytime I flash the PD1 firmware on my phone it always gets stuck on the Verizon splash screen. Am I doing something wrong?
Click to expand...
Click to collapse
Just flash stock PD1 using Odin and factory reset in stock recovery afterwards. Once you get used to it, softbricks won't scare you anymore

Nandr0idC0nsumer said:
Just flash stock PD1 using Odin and factory reset in stock recovery afterwards. Once you get used to it, softbricks won't scare you anymore
Click to expand...
Click to collapse
When I flash stock PD1 using Odin and factory reset it still freezes at Verizon splash screen. Any other way I flash PD1 whether it be Kies or Odin outputs the same result.Freeze at Verizon splashscreen

Chay555 said:
When I flash stock PD1 using Odin and factory reset it still freezes at Verizon splash screen. Any other way I flash PD1 whether it be Kies or Odin outputs the same result.Freeze at Verizon splashscreen
Click to expand...
Click to collapse
Reset using stock recovery. it usually takes about 20min on the vzw screen

Only problem is that I have a developer model, keep scouting the community I'm pretty positive someone has retail pit file with partitions. I have hard bricked my phone before I repaired it using win32img creator using an sd card. I never messed with partitions ever again after that.
akaplo said:
It's definitely a hard brick. I can't boot into recovery, download mode, or anything! I've got a retail phone. You'd be a lifesaver if it works!
Click to expand...
Click to collapse

stellar0322 said:
Only problem is that I have a developer model, keep scouting the community I'm pretty positive someone has retail pit file with partitions.
Click to expand...
Click to collapse
Darn. Thanks though! @Nandr0idC0nsumer, is there any way you might be able to get this for me? I posted on your debrick thread but haven't heard from anyone, so I started this thread in hopes to catch someone's (ANYONE'S) eye
In order for someone to do this, they'd have to be on a rooted version on PD1, yes?

akaplo said:
Darn. Thanks though! @Nandr0idC0nsumer, is there any way you might be able to get this for me? I posted on your debrick thread but haven't heard from anyone, so I started this thread in hopes to catch someone's (ANYONE'S) eye
In order for someone to do this, they'd have to be on a rooted version on PD1, yes?
Click to expand...
Click to collapse
Alright. I'm confused
EDIT: looked through the thread now. That's a hardbrick. Nobody has created a debrick image for PD1, so just try the PB1 debrick.
Re-explain what's going on. Unless your device is 100% dead, my debrick thread will not be of any use.

Nandr0idC0nsumer said:
Nobody has created a debrick image for PD1, so just try the PB1 debrick.
Re-explain what's going on. Unless your device is 100% dead, my debrick thread will not be of any use.
Click to expand...
Click to collapse
From the beginning:
Yesterday, I was on rooted OE1, using muniz_ri's build from months ago. I decided to use his thread that had been updated the other day to update my phone to PD1 (Android 6.0). I updated the ROM and the bootloader.
It got stuck on the Samsung boot screen, and after about 40 minutes, I decided to flash the PB1 (Android 5.0) stock ROM. I downloaded the full tar from sammobile and flashed using odin. It went successfully, as far as I could tell. My phone froze on the Verizon boot screen as expected, and after about 10 minutes the screen went black and the notification LED started blinking red. I pulled the battery, put it back in, and tried to power the phone on. It has been completely unresponsive every since. Neither recovery mode nor download mode is accessible.
Obviously, I have a hard brick. I've tried using the PB1 debrick image you (@Nandr0idC0sumer) gave in your other thread with my 16GB external SD card. I followed the steps given there exactly. I've had no luck in getting my phone to respond. I thought that maybe my flash went bad and that my bootloader is still on PD1 while my ROM is PB1, and I would therefore need a PD1 debrick image. Thus, this thread was born.

akaplo said:
From the beginning:
Yesterday, I was on rooted OE1, using muniz_ri's build from months ago. I decided to use his thread that had been updated the other day to update my phone to PD1 (Android 6.0). I updated the ROM and the bootloader.
It got stuck on the Samsung boot screen, and after about 40 minutes, I decided to flash the PB1 (Android 5.0) stock ROM. I downloaded the full tar from sammobile and flashed using odin. It went successfully, as far as I could tell. My phone froze on the Verizon boot screen as expected, and after about 10 minutes the screen went black and the notification LED started blinking red. I pulled the battery, put it back in, and tried to power the phone on. It has been completely unresponsive every since. Neither recovery mode nor download mode is accessible.
Obviously, I have a hard brick. I've tried using the PB1 debrick image you (@Nandr0idC0sumer) gave in your other thread with my 16GB external SD card. I followed the steps given there exactly. I've had no luck in getting my phone to respond. I thought that maybe my flash went bad and that my bootloader is still on PD1 while my ROM is PB1, and I would therefore need a PD1 debrick image. Thus, this thread was born.
Click to expand...
Click to collapse
Unplug your device and open device manager on windows. now plug it in. does device manager refresh as if it detected a new device?
Because sdcard mode will only work if you can get the device into qhsusb_bulk mode.

Nandr0idC0nsumer said:
Reset using stock recovery. it usually takes about 20min on the vzw screen
Click to expand...
Click to collapse
Is good now. Thank You

Chay555 said:
Is good now. Thank You
Click to expand...
Click to collapse
Congrats! You get a cookie.

Nandr0idC0nsumer said:
Unplug your device and open device manager on windows. now plug it in. does device manager refresh as if it detected a new device?
Because sdcard mode will only work if you can get the device into qhsusb_bulk mode.
Click to expand...
Click to collapse
No, it does not. Is there some sort of button combo I should be pressing to get the device into that mode? I've tried long-holding the following combos:
1. Power
2. Power, volume down, and home
3. Power, volume up, and home

akaplo said:
No, it does not. Is there some sort of button combo I should be pressing to get the device into that mode? I've tried long-holding the following combos:
1. Power
2. Power, volume down, and home
3. Power, volume up, and home
Click to expand...
Click to collapse
I've read up on the Snapdragon 80x boot ROMs, and there appears there is only 1 way to get into qhsusb_bulk mode, which is to have the bootloader corrupted and it is automatically triggered.
If it's not in that mode, it's a brick, go to Verizon and tell them it randomly died
there is nothing that can be done from now. good luck dealing with verizon/samsung and I hope you're still in warranty.

PD1 unbrick image.
https://www.androidfilehost.com/?fid=24562946973631519

Help rooting cricket s7 g930az

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