Related
I'm wanting to unroot and return the number of custom flashed roms back to none. I've heard you can do this? I was planning on using this (http://forum.xda-developers.com/showthread.php?t=1342348) to unroot phone and then what would I use to return the custom rom count to none?
There is nothing that can set the custom binary to 0.
jc1337 said:
I'm wanting to unroot and return the number of custom flashed roms back to none. I've heard you can do this? I was planning on using this (http://forum.xda-developers.com/showthread.php?t=1342348) to unroot phone and then what would I use to return the custom rom count to none?
Click to expand...
Click to collapse
appdroid said:
There is nothing that can set the custom binary to 0.
Click to expand...
Click to collapse
I was following the unroot tutorial that I posted a link to in my first post and it just sits there and doesn't do anything after it gets to <ID:0/003> NAND Write Start!!
I watched a youtube video of a guy who was doing a visual step by step of that tutorial and he put his phone into debugging mode and I didn't because I didn't see anything about it in that post. Now my phone won't boot past that yellow exclamation point symbol... did I mess something up?
jc1337 said:
I was following the unroot tutorial that I posted a link to in my first post and it just sits there and doesn't do anything after it gets to <ID:0/003> NAND Write Start!!
I watched a youtube video of a guy who was doing a visual step by step of that tutorial and he put his phone into debugging mode and I didn't because I didn't see anything about it in that post. Now my phone won't boot past that yellow exclamation point symbol... did I mess something up?
Click to expand...
Click to collapse
debugging mode has no bearing whatsoever in download or recovery mode....debugging mode is for the OS only....
Pirateghost said:
debugging mode has no bearing whatsoever in download or recovery mode....debugging mode is for the OS only....
Click to expand...
Click to collapse
\
do you have any idea why it might not be working then? I'm using the .tar from that post about unroot i727 and it's not working. What I'm doing is
1. running odin as admin
2. selecting pda (the SGH-I727-UCKJ2-k0nane.tar)
3. while phone is off pressing both volume buttons and then plugging in usb (putting it into download mode)
4. making sure odin sees my phone
5. clicking start
and this is what it does and it won't go any further
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
I've let it sit there for about 30 minutes without it moving any further?
do you comprehend what root actually is?
why are you trying to 'unroot' your phone?
did you have a custom rom on your phone before this?
Pirateghost said:
do you comprehend what root actually is?
why are you trying to 'unroot' your phone?
did you have a custom rom on your phone before this?
Click to expand...
Click to collapse
I'm needing to return the phone to AT&T. Yes, I do comprehend what root is. And yes, I had a custom ROM on it before this.
sorry, i read this all the time about 'unrooting' your phone because so many people use the terminology incorrectly. this isnt about UNROOTING your phone as much as it is restoring STOCK...big difference. UNROOTING implies that you will be removing the su binary and superuser.apk from your /system, but leaving the rest of the system intact....regardless of what rom you are on.
are you using the samsung cable and not some other cable? i have seen bad cables do this. i have also seen front panel USB hubs do this, and you might have better luck finding another USB port to try
Pirateghost said:
sorry, i read this all the time about 'unrooting' your phone because so many people use the terminology incorrectly. this isnt about UNROOTING your phone as much as it is restoring STOCK...big difference. UNROOTING implies that you will be removing the su binary and superuser.apk from your /system, but leaving the rest of the system intact....regardless of what rom you are on.
are you using the samsung cable and not some other cable? i have seen bad cables do this. i have also seen front panel USB hubs do this, and you might have better luck finding another USB port to try
Click to expand...
Click to collapse
All I am really wanting to do is remove superuser stuff so if at&t checks they won't see it. An I am using the cable that came with the phone but I am using the front panel USB hubs so I guess I'll have to try plugging it into the back. Thank you very much for all of your help!
jc1337 said:
All I am really wanting to do is remove superuser stuff so if at&t checks they won't see it. An I am using the cable that came with the phone but I am using the front panel USB hubs so I guess I'll have to try plugging it into the back. Thank you very much for all of your help!
Click to expand...
Click to collapse
if you are on a custom rom, when you get that tar to load, you will be loading STOCK rom....not just removing superuser....that file is meant to restore your phone to STOCK, not 'unroot' it. root only applies within the OS. if you load a new OS that doesnt have root access, its not unrooting it, its loading a new rom.
Pirateghost said:
if you are on a custom rom, when you get that tar to load, you will be loading STOCK rom....not just removing superuser....that file is meant to restore your phone to STOCK, not 'unroot' it. root only applies within the OS. if you load a new OS that doesnt have root access, its not unrooting it, its loading a new rom.
Click to expand...
Click to collapse
I'm just trying to get the phone so that I can return it to at&t, how would you do it if you were me?
jc1337 said:
So, should I just try to find the stock rom online?
Click to expand...
Click to collapse
that k0nane.tar IS the stock rom.....
Pirateghost said:
that k0nane.tar IS the stock rom.....
Click to expand...
Click to collapse
Yeah, I noticed that I worded that wrong and changed it but I guess you'd already seen it. I'm just trying to get the phone so that I can return it to at&t, how would you do it if you were me?
jc1337 said:
Yeah, I noticed that I worded that wrong and changed it but I guess you'd already seen it. I'm just trying to get the phone so that I can return it to at&t, how would you do it if you were me?
Click to expand...
Click to collapse
with that exact file.
it will however, probably trip the download counter
Pirateghost said:
with that exact file.
it will however, probably trip the download counter
Click to expand...
Click to collapse
It is, I've gone from YES(4 counts) to YES(15 counts) I honestly have no idea what I'm doing wrong and why it won't go past NAND Write. I've been working on this for the past three hours though and they close in an hour an 15 minutes so I guess I may not make it tonight...
at this point I would be okay with just getting this phone working again.... I have to be up in a few hours and need to get to sleep
If you are under 30 days than return it to att... all you gotta say is that is getting hot and rebooting or just say you can't go pass the logo screen... if you are under the Samsung 1 year warranty just flast the stock firmware (search on xda on how to do it) and reset it to factory setting. Call Samsung center ask for a replacement or service ticket, send your phone and you'll get a working phone back in about 6 business days...
Hit the thanks button if I helped you with your question!
Thanks.
SkyIce 7.3 Speed
You WILL trip the counter using that stock .tar. I recently went back to stock via the same method your using and I did not have root. I had no SU access for TiBu etc. So no signs AT&T would see other than seeing the counter bring tripped if they boot into DL mode to check. I have since rooted again to freeze bloat in TiBu. My question is did you extract the 7zip file properly and actually flashing a .tar file and not the compressed .zip?
Sent from my SAMSUNG-SGH-I727 using xda premium
r3dp0is0n2012 said:
If you are under 30 days than return it to att... all you gotta say is that is getting hot and rebooting or just say you can't go pass the logo screen... if you are under the Samsung 1 year warranty just flast the stock firmware (search on xda on how to do it) and reset it to factory setting. Call Samsung center ask for a replacement or service ticket, send your phone and you'll get a working phone back in about 6 business days...
Hit the thanks button if I helped you with your question!
Thanks.
SkyIce 7.3 Speed
Click to expand...
Click to collapse
I am under 30 days, but I don't think that'll work if I can't get past the screen that says "Firmware upgrade encountered an issue. Please selecdt recovery mode in Kies & try again." and says I have a custom binary download of 16
hcyplr29 said:
You WILL trip the counter using that stock .tar. I recently went back to stock via the same method your using and I did not have root. I had no SU access for TiBu etc. So no signs AT&T would see other than seeing the counter bring tripped if they boot into DL mode to check. I have since rooted again to freeze bloat in TiBu. My question is did you extract the 7zip file properly and actually flashing a .tar file and not the compressed .zip?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
yeah I did. I'm trying to flash the .tar not the whole zip
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.
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.
Ok, here goes.
Have a SM-G930W8 (Canada, Rogers, S7). Was running a 7.0 ROM from XDA (ambassadii? sp?). I disabled developer options to check a possible issue transferring files from my PC to the S7's SD Card. I restarted the device.
Custom binary blocked by FRP lock. No problem, thought I. I'll boot into Download Mode, fire up Odin and flash the stock rom back to the device (also what I've read in most every thread I've come across). Launch ODIN as admin, see the device is connected, select the proper AP(also BL, CSC and CP...I'm thorough) file to flash (from Sammobile I think it was), make sure repartition is unchecked and hit Start.
Here's the result...wait I can't post them but I have the screen shots! The phone shows Secure Check Fail (PIT). Odin gives an error at that step as well.
I've tried Kies (there's no SN anywhere on my device or on the box) so that doesn't work. Smart Switch, same issue.
Does ANYONE out there have any clue what I can attempt next? Sending it in for service will likely cost as much as a new device, with the warranty void. Thank you very much in advance.
chewtoy0 said:
Ok, here goes.
Have a SM-G930W8 (Canada, Rogers, S7). Was running a 7.0 ROM from XDA (ambassadii? sp?). I disabled developer options to check a possible issue transferring files from my PC to the S7's SD Card. I restarted the device.
Custom binary blocked by FRP lock. No problem, thought I. I'll boot into Download Mode, fire up Odin and flash the stock rom back to the device (also what I've read in most every thread I've come across). Launch ODIN as admin, see the device is connected, select the proper AP(also BL, CSC and CP...I'm thorough) file to flash (from Sammobile I think it was), make sure repartition is unchecked and hit Start.
Here's the result...wait I can't post them but I have the screen shots! The phone shows Secure Check Fail (PIT). Odin gives an error at that step as well.
I've tried Kies (there's no SN anywhere on my device or on the box) so that doesn't work. Smart Switch, same issue.
Does ANYONE out there have any clue what I can attempt next? Sending it in for service will likely cost as much as a new device, with the warranty void. Thank you very much in advance.
Click to expand...
Click to collapse
Are you able to boot into recovery?
If not you could try to ONLY flash the stock recovery>boot recovery>wipe everything then boot to download mode and flash complete stock firmware via odin.
or flash stock firmware with the same CSC as your custom rom has/ flash "HOME_CSC" instead of "CSC..."
good luck
mrd0pe said:
Are you able to boot into recovery?
If not you could try to ONLY flash the stock recovery>boot recovery>wipe everything then boot to download mode and flash complete stock firmware via odin.
or flash stock firmware with the same CSC as your custom rom has/ flash "HOME_CSC" instead of "CSC..."
good luck
Click to expand...
Click to collapse
Can't get into Recovery no. Which file of the lot has the stock recovery in it?
chewtoy0 said:
Can't get into Recovery no. Which file of the lot has the stock recovery in it?
Click to expand...
Click to collapse
Try to only flash AP, I did have the same problem as you describe but I cant remember how I resolved it, I'm on G930F tho
Your S/N is on the rear of the phone it can be a pain to see but it is there. Use smart switch to restore the firmware. Just click emergency firmware restore.
It is? The IMEI is there but I didn't see the SN. Also my phone is black so that doesn't help.
I will have another look.
mrd0pe said:
Try to only flash AP, I did have the same problem as you describe but I cant remember how I resolved it, I'm on G930F tho
Click to expand...
Click to collapse
I did that. No dice.
I had the same issue as you. Used the same rom and disabled developer options. I downloaded stock firmware.. flashed it with odin. It actually took 2 tries. The first time I could see only 1/4 of the screen. The second time i flashed stock firmware from another country and it worked. You might actually have to do a hard factory reset if you cant unlock your phone.. for some reason. Then I let kies do its magic because I could then see my S/N. Right now I still feel my phone slightly different. Messenger is unstable for some reason also.
Ok.
Checked the back of the device for a SN#. Mine's black so I used a flashlight. It's not there. The Model #, IMEI, FCC ID# and IC# are all there. Does someone have a blurred out screeny of where THEY found their SN# on the back of the device?
Tried flashing with Odin the CSC(home) and AP files (stock MM from my region). Got: Custom Binary (Boot) blocked by FRP Lock.
Tried flashing TWRP again, to TRY to enter into recovery...same message.
With just the AP selected, ODIN seems to hang at "Get PIT for mapping" and fails. I'm running it again to make sure it's not a bad connection with the device.
Same result, hangs at "Get PIT for mapping".
chewtoy0 said:
Ok.
Checked the back of the device for a SN#. Mine's black so I used a flashlight. It's not there. The Model #, IMEI, FCC ID# and IC# are all there. Does someone have a blurred out screeny of where THEY found their SN# on the back of the device?
Tried flashing with Odin the CSC(home) and AP files (stock MM from my region). Got: Custom Binary (Boot) blocked by FRP Lock.
Tried flashing TWRP again, to TRY to enter into recovery...same message.
With just the AP selected, ODIN seems to hang at "Get PIT for mapping" and fails. I'm running it again to make sure it's not a bad connection with the device.
Same result, hangs at "Get PIT for mapping".
Click to expand...
Click to collapse
Try to flash Nougat firmware, as that was what your custom rom was on right? I dont think it really matters though as I downgraded from stock 7.0 to stock 6.0.1 via odin without errors... But you can try
As an absolute last resort I would try to check the "re-partition"-tab and provide odin with a .pit file, then load everything (BL, AP, CP...) with stock firmware <<<< do this at your own risk, if you are not careful, your phone will be bricked
I am trying to flash MM back to it .
I'm not sure I want to mess with the re partition table...But it's already soft bricked.
Mine is also black. The S/N Is immediately next to the imei number I had to use a flash light to see it but it's deffinatly there.
Matty39856 said:
Mine is also black. The S/N Is immediately next to the imei number I had to use a flash light to see it but it's deffinatly there.
Click to expand...
Click to collapse
I'd show you a photo if I could. The IMEI is by itself on a third line of stuff. There's nothing else around it.
chewtoy0 said:
I'd show you a photo if I could. The IMEI is by itself on a third line of stuff. There's nothing else around it.
Click to expand...
Click to collapse
I'm not sure then. Have you tried flashing the latest unlocked version for your region? I remember on my s6 I had a similar problem that was caused because I was trying to flash a lower version of Android than what I previously had. So ended up flashing the latest unlocked version BTU for my region and it worked. Sorry I can't be of more help. It looks like the latest firmware is still 6.0.1 that's why it's blocking it from downgrading.
Was sent a PM by a person. Was skeptical at first, but in 10 minutes using TeamViewer, they fixed the issue by reflashing the device (as well as repartitioning it properly). I can't thank them enough.
This is the person on Facebook...
Unlock Network FRP Lock Remote Service
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