Can anyone help? I spent a big chunk of my hard earned money on a refurbed S6 for my daughter, she's had it about a week (she's Pokemon mad btw). The latest update for Pokemon Go came out and now she's blocked from the game as it appears the phone has been rooted. If I'd known, I wouldn't have bought it. Anyway, for the last 2 days my partner and I have been trying to unroot it. We've used various versions of Odin to no avail. I had a lot of trouble finding the right firmware because it looks like the phone was Polish according to the version and CSC numbers, and tbh I'm still not sure if we're trying the right one. Software is 5.1.1. right now. I've tried installing SuperSU but it won't run, it just crashes the phone and forces a reboot. We've tried manually unrooting with a file manager but the su files we need to delete reappear seconds after they're deleted. I'm at the end of my tether, does anyone have any ideas?
You won't be able to unroot it until you flash stock firmware. I don't know if the game checks the knox status.
Give this a go
http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/
Enjoy
Unforunately my partner spent almost all night trying to flash the firmware. According to him it 'nearly' worked, however, I now have a phone stuck in a boot loop. :crying:
Run emergency recovery on Smart switch
ccalixtro said:
Run emergency recovery on Smart switch
Click to expand...
Click to collapse
Do I need to have smart switch installed on the phone for this to work?
amber_1978 said:
Do I need to have smart switch installed on the phone for this to work?
Click to expand...
Click to collapse
No, run it on your pc.
Thanks, I'll give it a go after work.
ccalixtro said:
No, run it on your pc.
Click to expand...
Click to collapse
Smart switch won't work, says it doesn't recognise the device
I think I would give original firmware of your country and odin a try. One of possible ways is to download all needed files from the site of sammobile.
For me this way works every time when I stuck in boot loop. Odin functionates when you are in download mode. Switch off your s6, then start by pressing home-, powerbutton and Volume down at the same time.
Then start Odin on PC, then connect USB and so on.
Greetz JG
amber_1978 said:
Smart switch won't work, says it doesn't recognise the device
Click to expand...
Click to collapse
When you select emergency recovery theres an option where you have to write the device model and the serial number
Use kies 3 on your computer. When you get it do a "firmware upgrade and installation" it will ask for your serial number which you can get from download mode when pressing the home key. After that kies 3 will ask to boot your phone to recovery but instead boot to download and bow your phone will flash to stock. This method always work!!
fahad999 said:
Use kies 3 on your computer. When you get it do a "firmware upgrade and installation" it will ask for your serial number which you can get from download mode when pressing the home key. After that kies 3 will ask to boot your phone to recovery but instead boot to download and bow your phone will flash to stock. This method always work!!
Click to expand...
Click to collapse
Thanks for the reply. Unfortunately I've tried Kies already and I can't get it to work at all. I get a message telling me my device is not compatible and the whole thing just stops. I'll give it another go though, no harm in trying. Thanks
@amber_1978, Pokemon Go does not check for root. The only thing it does seem to check for is location spoofing via another app. I'm using it on a rooted, Knox tripped, Xposed installed phone with no issues.
If you want to return the phone back to stock, the best way IMO would be to use Odin to flash a stock image, such as the EPD1 firmware.
socal87 said:
@amber_1978, Pokemon Go does not check for root. The only thing it does seem to check for is location spoofing via another app. I'm using it on a rooted, Knox tripped, Xposed installed phone with no issues.
If you want to return the phone back to stock, the best way IMO would be to use Odin to flash a stock image, such as the EPD1 firmware.
Click to expand...
Click to collapse
Really? Did you do the latest update in the game and it still worked ok? This phone has definitley not been used for location spoofing by us and I'm pretty sure there were no apps of that nature on the phone. I downloaded a root checker when everything went wrong the other day, it said the phone was rooted. I'm totally at a loss tbh. Right now it's still in a boot loop. Trying to flash it with Odin as we speak.
Just an update. Tried Smart Switch. Tried the model and serial numbers on the back of the phone case, these weren't recognised so I went to the recovery screen and hit the home button and got a completely different set of numbers. Different IMEI, model number, you name it. I'm assuming this is why Odin won't work, I'm looking for the wrong firmware? I obviously have Frankenstein's phone. No idea what to do now.
Best thing to do is to flash TWRPP and try to flash a custom stock rom through the TWRP recovery which does not have root installed..... If that doesn't work try to find a generic stock firmware for Odin, meaning a firmware that can run in any country..... If all else fails update it to 6.0.1 stock firmware. Try the closest firmwares to your location.
And if you do manage to get to the Samsung logo let the phone sit there for a good 10 minutes even if it reboots....
When I bricked my Samsung I used masiks custom 6.0.1 rom based on stock, but had all the links to bootloaders cscs radios and what not so giv that a shot if you can find it.
---------- Post added at 12:08 AM ---------- Previous post was at 12:05 AM ----------
Link to rom that helped me http://forum.xda-developers.com/galaxy-s6/development/masik-marshmallow-1-0-jan-20-2016-t3297961
do you have lucky patcher playstore installed ?
Related
I have tried all of the below and am still stuck on the Galaxy S5 screen with "set warranty bit : kernel" in yellow at the top left. I've tried the stock firmware from the Samsung mobile site and cannot get it to go back to stock. Every time I go into download mode it still shows custom instead of original. When I've tried to flash the stock kernel I get a md5! binary error. I can get into download mode just fine, but can't get recovery to come up either. If anyone can help I would greatly appreciate it. I've tried everything I've seen in the forums and am very frustrated. My phone hasn't worked since Wednesday night. I'm fairly new at this, but have been doing things I've found in the forums but nothing has worked so far. Can anyone help?? Please....
Everything was fine with the phone until Wednesday when I pulled it out of my pocket and it was stuck on the screen with the kernel message. I think maybe an OTA update came up and somehow it was accepted when the phone was in my pocket. I'm not sure though because it had worked fine earlier that day.
Originally Posted by Joe0113 View Post
Some people seem to be having trouble, so I thought this might help you guys out.
1. DL Odin 3.09
2. DL this stock NCB tar. ----- Here is a faster/better DL mirror! Thanks to @ChaddyPaddy ----- And yet another mirror! Thanks to @roadrunnrr
3. Make a backup of your apps/data (TiBu/Helium/etc). MAKE SURE THE APP/DATA BACKUPS ARE TO YOUR EXT SD CARD!!!
4. Take out your EXT SD Card (if you have one).
5. Flash the stock NCB tar (put it in "AP/PDA" in Odin).
6. Do a factory reset in the stock recovery after you flash the tar (not necessary but deff won't kill ya!).
7. Reboot into Download Mode and make sure it says ROM type= OFFICIAL! If it says custom you will not be able to take the OTA.
8. Reboot, check for the OTA to "ND2" and wait for it to complete.
9. Your baseband and software should now end in ND2. If it does not, then you did something wrong, go back to step 1 and try a redownload, and reflash of stock NCB tar.
10. Re-root.
Also if someone that has SuperSU PRO version, can check if "Survival Mode" works for the GS5, that'd be awesome!
One person tried and said that it does not work.
There is now an Odin flashable tar of 100% stock ND2, no need to even go back to NCB to take it. Just flash the ND2 tar in Odin and you have the full ND2 update!
rleighska said:
I have tried all of the below and am still stuck on the Galaxy S5 screen with "set warranty bit : kernel" in yellow at the top left. I've tried the stock firmware from the Samsung mobile site and cannot get it to go back to stock. Every time I go into download mode it still shows custom instead of original. When I've tried to flash the stock kernel I get a md5! binary error. I can get into download mode just fine, but can't get recovery to come up either. If anyone can help I would greatly appreciate it. I've tried everything I've seen in the forums and am very frustrated. My phone hasn't worked since Wednesday night. I'm fairly new at this, but have been doing things I've found in the forums but nothing has worked so far. Can anyone help?? Please....
Everything was fine with the phone until Wednesday when I pulled it out of my pocket and it was stuck on the screen with the kernel message. I think maybe an OTA update came up and somehow it was accepted when the phone was in my pocket. I'm not sure though because it had worked fine earlier that day.
Originally Posted by Joe0113 View Post
Some people seem to be having trouble, so I thought this might help you guys out.
1. DL Odin 3.09
2. DL this stock NCB tar. ----- Here is a faster/better DL mirror! Thanks to @ChaddyPaddy ----- And yet another mirror! Thanks to @roadrunnrr
3. Make a backup of your apps/data (TiBu/Helium/etc). MAKE SURE THE APP/DATA BACKUPS ARE TO YOUR EXT SD CARD!!!
4. Take out your EXT SD Card (if you have one).
5. Flash the stock NCB tar (put it in "AP/PDA" in Odin).
6. Do a factory reset in the stock recovery after you flash the tar (not necessary but deff won't kill ya!).
7. Reboot into Download Mode and make sure it says ROM type= OFFICIAL! If it says custom you will not be able to take the OTA.
8. Reboot, check for the OTA to "ND2" and wait for it to complete.
9. Your baseband and software should now end in ND2. If it does not, then you did something wrong, go back to step 1 and try a redownload, and reflash of stock NCB tar.
10. Re-root.
Also if someone that has SuperSU PRO version, can check if "Survival Mode" works for the GS5, that'd be awesome!
One person tried and said that it does not work.
There is now an Odin flashable tar of 100% stock ND2, no need to even go back to NCB to take it. Just flash the ND2 tar in Odin and you have the full ND2 update!
Click to expand...
Click to collapse
Many different ways to tackle this 1.) flash recovery via odin, then restore nandroid, 2.) or go to sammobile get stock NCB firmware flash through odin, if you do this no worries it takes you back to complete stock but not rooted, your phone will be exactly the same as it was before restoring to stock...just not rooted lol mouth fullll. then reroot! By the way I don't think the phones can update unless you unroot, so jus flash stock NCB firmware take update then reroot if you want update, Its awesome its like dirty flashing! If you were trying ART instead of Dalvik before your phone took a poop, using ART causes the custom status everytime until you switch back to dalvik. Knox will always be 0x1 if you have rooted your S5 unless you haven't wait for an exploit, which is super not like gonna happen, cause S5 is locked up tighter then Fort Knox!
Iceburn1 said:
Many different ways to tackle this 1.) flash recovery via odin, then restore nandroid, 2.) or go to sammobile get stock NCB firmware flash through odin, if you do this no worries it takes you back to complete stock but not rooted, your phone will be exactly the same as it was before restoring to stock...just not rooted lol mouth fullll. then reroot! By the way I don't think the phones can update unless you unroot, so jus flash stock NCB firmware take update then reroot if you want update, Its awesome its like dirty flashing! If you were trying ART instead of Dalvik before your phone took a poop, using ART causes the custom status everytime until you switch back to dalvik. Knox will always be 0x1 if you have rooted your S5 unless you haven't wait for an exploit, which is super not like gonna happen, cause S5 is locked up tighter then Fort Knox!
Click to expand...
Click to collapse
I did go get the stock NCB firmware from sammobile, flashed through odin and the Samsung Galaxy S5 screen came up with "recovery booting" in blue and then "Set warranty bit: kernel" in yellow right under it. It won't go off of this screen. I can go back to download mode, but if I try recovery mode it goes right back to this screen. So then I flashed a recovery, I was using philz_touch_6.42.6-klte.tar. When this was flashed it want to the Samsung screen but had "set warranty bit: kernel" at the top in yellow. I haven't been able to get past this point as every kernel file I've tried in odin either had a binary error or froze and closed odin. I also tried openrecovery-twrp, and governaa, but had the same outcome with both of those. I haven't once had a problem getting into download mode, but can't get it to go into recovery to even try a backup. Oh, and I've been doing all of this with the sd card taken out of the phone, don't know if that makes a difference or not. I did try it with it in at first, but had no luck there either. The one post I read said it should be taken out, so I figured, what could it hurt? I am beyond frustrated. I'm new to this, this is the first phone that I rooted by myself, but it's my second rooted phone. Previously I had a GS3 and never had this kind of problem with that phone.
Also, how would I tell if I was using ART? Before the phone "died" I was playing a game on it. I closed out of the game, turned off the screen, and put it in my pocket. When I took it out of my pocket about an hour later it was on the Samsung Galaxy S5 screen with set warranty bit: kernel.
I just tried re-flashing the stock firmware and it's currently reading set warranty bit: recovery (in yellow) under the "recovery booting....." (in blue).
recovery
rleighska said:
I did go get the stock NCB firmware from sammobile, flashed through odin and the Samsung Galaxy S5 screen came up with "recovery booting" in blue and then "Set warranty bit: kernel" in yellow right under it. It won't go off of this screen. I can go back to download mode, but if I try recovery mode it goes right back to this screen. So then I flashed a recovery, I was using philz_touch_6.42.6-klte.tar. When this was flashed it want to the Samsung screen but had "set warranty bit: kernel" at the top in yellow. I haven't been able to get past this point as every kernel file I've tried in odin either had a binary error or froze and closed odin. I also tried openrecovery-twrp, and governaa, but had the same outcome with both of those. I haven't once had a problem getting into download mode, but can't get it to go into recovery to even try a backup. Oh, and I've been doing all of this with the sd card taken out of the phone, don't know if that makes a difference or not. I did try it with it in at first, but had no luck there either. The one post I read said it should be taken out, so I figured, what could it hurt? I am beyond frustrated. I'm new to this, this is the first phone that I rooted by myself, but it's my second rooted phone. Previously I had a GS3 and never had this kind of problem with that phone.
Also, how would I tell if I was using ART? Before the phone "died" I was playing a game on it. I closed out of the game, turned off the screen, and put it in my pocket. When I took it out of my pocket about an hour later it was on the Samsung Galaxy S5 screen with set warranty bit: kernel.
I just tried re-flashing the stock firmware and it's currently reading set warranty bit: recovery (in yellow) under the "recovery booting....." (in blue).
Click to expand...
Click to collapse
Did you try to flash recovery bro? Its on a separate partition, if you flash a recovery tar through odin maybe you can restore a nandroid. then go to developer settings in settings check to see if your using art or dalvik
damn need to stop skimming I see you tried, at a loss bro tryin!
Maybe your phone did update and you are using the wrong firmware, could b on nd2?
Did you try to use cf-auto root again just see what happens?
Iceburn1 said:
Many different ways to tackle this 1.) flash recovery via odin, then restore nandroid, 2.) or go to sammobile get stock NCB firmware flash through odin, if you do this no worries it takes you back to complete stock but not rooted, your phone will be exactly the same as it was before restoring to stock...just not rooted lol mouth fullll. then reroot! By the way I don't think the phones can update unless you unroot, so jus flash stock NCB firmware take update then reroot if you want update, Its awesome its like dirty flashing! If you were trying ART instead of Dalvik before your phone took a poop, using ART causes the custom status everytime until you switch back to dalvik. Knox will always be 0x1 if you have rooted your S5 unless you haven't wait for an exploit, which is super not like gonna happen, cause S5 is locked up tighter then Fort Knox!
Click to expand...
Click to collapse
Iceburn1 said:
Did you try to flash recovery bro? Its on a separate partition, if you flash a recovery tar through odin maybe you can restore a nandroid. then go to developer settings in settings check to see if your using art or dalvik
damn need to stop skimming I see you tried, at a loss bro tryin!
Click to expand...
Click to collapse
Any help is appreciated!!! I have no idea what to do next. I've done and re-done everything possible. For whatever reason it won't let me boot into recovery. It just goes straight to the Samsung screen with the warranty bit kernel at the top. I just reflashed the stock firmware and it booted up to the samsung screen showing "recovery booting" and "set warranty bit : recovery" at the top. If I flash a recovery (through odin, the same way I flashed the firmware) it will boot to the same screen, but will say "set warranty bit: kernel" instead, but will not go past that screen. I've tried several recoveries, all of them take me to the same screen when flashed. I feel like I'm in a boot loop myself with the things that I've been trying to get this thing to work.
A friend of mine said when I'm at the point that I'm on the samsung screen with the "set warranty bit: kernel" I should be able to boot to download and flash a stock kernel through odin. I haven't found one kernel file that worked. Every one I've tried either gives a md5 binary error or makes odin freeze and close.
I don't think I was using ART. When I got the phone all I did was root it, didn't even get a good ROM on it yet, but then again, I'm not exactly sure what "ART" is because I'm not 100% familiar with all of the terminology just yet, but I'm learning (or trying to).
At this point all I want to do is get it back to stock and re-root it.
Or, if there was a way to reinstate my warranty with Sprint, I'd take it back to them and get a new one.
s5 fix
Maybe your phone did update and you are using the wrong firmware, could b on nd2?
Did you try to use cf-auto root again just see what happens?
---------- Post added at 02:37 PM ---------- Previous post was at 02:13 PM ----------
Just flash custom recovery then use cf-auto root.
Iceburn1 said:
Maybe your phone did update and you are using the wrong firmware, could b on nd2?
Did you try to use cf-auto root again just see what happens?
---------- Post added at 02:37 PM ---------- Previous post was at 02:13 PM ----------
Just flash custom recovery then use cf-auto root.
Click to expand...
Click to collapse
I reflashed the stock firmware again, flashed philz recovery, and then did cf-auto root and got this...
recovery booting.... (in blue)
recovery is not seandroid enforcing (in red)
set warranty bit: recovery (in yellow)
When I got the phone all I did was root it. How am I able to tell if I'm using ND2 or something else? I can't boot to recovery. I wasn't even trying to update anything on it when it started giving the message set warranty bit: kernel. I was using it, turned the screen off, put it in my pocket for about an hour, and when I took it out it's been stuck on that screen ever since. That was Wednesday. Since then I've tried everything I could find and nothing has worked yet. I'm starting to think that this is un-fixable and now I have a very expensive paperweight. I have a variety of files I've downloaded, so if anyone has any idea, step-by-step what I can do to fix this, I'd be so grateful.
The stock files I got were from Sammobile's site, but I can't seem to get them to work correctly. I flash the stock firmware, then it gives me the set warranty bit recovery message, so I flash recovery (tried twrp, philz, cwm), and then it will boot as far as the Samsung screen, but changes to set warranty bit: kernel. I've tried flashing a new kernel, but can't find any that don't have md5 binary errors or freeze odin. Is there a certain "magic" order of flashing that I should do, like should the firmware be first, then recovery, then kernel (if it'd work), then root? Or firmware, then recovery, root, kernel? I think I've tried every combination imaginable.
xposed installed or gravity?
do you have xposed or gravity installed maybe that's whats causing bootloop, try safe mode. Turn phone off hold down volume down button and restart phone it will reboot into safe mode! uninstall mod.
---------- Post added at 06:21 PM ---------- Previous post was at 06:15 PM ----------
Are you 100% sure you were on ncb, I really want to know I mean as far as it goes now theres no coming back, might as well try to download the stock nd2 file and flash that it wont hurt that update can fix some bigs with phone like cameran stuff and you can still root!
Iceburn1 said:
do you have xposed or gravity installed maybe that's whats causing bootloop, try safe mode. Turn phone off hold down volume down button and restart phone it will reboot into safe mode! uninstall mod.
Click to expand...
Click to collapse
I think I did have xposed installed and gravity come to think of it. I tried holding volume down and power and it went to the samsung screen with:
recovery booting.....
recovery is not seandroid enforcing
set warranty bit : recovery
If I turn off, go back to download mode, flash recovery, let it reboot, it will then still be stuck on the samsung screen, but will have:
set warranty bit: kernel
I have not yet found a kernel that will flash successfully and I can't get it to go into recovery at all, just download. It keeps getting stuck on the samsung screen with either the set warranty bit : recovery, until I flash recovery, then it says set warranty bit : kernel.
Iceburn1 said:
do you have xposed or gravity installed maybe that's whats causing bootloop, try safe mode. Turn phone off hold down volume down button and restart phone it will reboot into safe mode! uninstall mod.
---------- Post added at 06:21 PM ---------- Previous post was at 06:15 PM ----------
Are you 100% sure you were on ncb, I really want to know I mean as far as it goes now theres no coming back, might as well try to download the stock nd2 file and flash that it wont hurt that update can fix some bigs with phone like cameran stuff and you can still root!
Click to expand...
Click to collapse
I'm not sure if I was on ncb or nd2. How do I tell? When I got it I rooted it with CF- auto root, but I didn't do anything else to it that I can recall. I was going to install a rom, but the file wouldn't transfer for me, so I gave up on that until there were other roms to try. The only other thing I did once rooted was download titanium backup, did a backup of everything, downloaded xposed, and was using some of the modules from there. I was using twrp recovery and now I can't get anything to come up that even says twrp.
rleighska said:
I reflashed the stock firmware again, flashed philz recovery, and then did cf-auto root and got this...
recovery booting.... (in blue)
recovery is not seandroid enforcing (in red)
set warranty bit: recovery (in yellow)
When I got the phone all I did was root it. How am I able to tell if I'm using ND2 or something else? I can't boot to recovery. I wasn't even trying to update anything on it when it started giving the message set warranty bit: kernel. I was using it, turned the screen off, put it in my pocket for about an hour, and when I took it out it's been stuck on that screen ever since. That was Wednesday. Since then I've tried everything I could find and nothing has worked yet. I'm starting to think that this is un-fixable and now I have a very expensive paperweight. I have a variety of files I've downloaded, so if anyone has any idea, step-by-step what I can do to fix this, I'd be so grateful.
The stock files I got were from Sammobile's site, but I can't seem to get them to work correctly. I flash the stock firmware, then it gives me the set warranty bit recovery message, so I flash recovery (tried twrp, philz, cwm), and then it will boot as far as the Samsung screen, but changes to set warranty bit: kernel. I've tried flashing a new kernel, but can't find any that don't have md5 binary errors or freeze odin. Is there a certain "magic" order of flashing that I should do, like should the firmware be first, then recovery, then kernel (if it'd work), then root? Or firmware, then recovery, root, kernel? I think I've tried every combination imaginable.
Click to expand...
Click to collapse
Try using another USB. For example if you are using the USB 3.0 then us the 2.0. Reason why is people from the T-mobile variant where having problem flashing files via odin with the USB 3.0. But damn this is one troubling problem
Try using this TAR filehttp://forum.xda-developers.com/showthread.php?t=2737112
Nyc1231 said:
Try using another USB. For example if you are using the USB 3.0 then us the 2.0. Reason why is people from the T-mobile variant where having problem flashing files via odin with the USB 3.0. But damn this is one troubling problem
Try using this TAR filehttp://forum.xda-developers.com/showthread.php?t=2737112
Click to expand...
Click to collapse
I have tried that TAR file, numerous times, same results as previously described. I didn't think to try a different USB cable, was using 3.0 as it came with the phone, but just now switched to the 2.0 and am also getting the same results.
safemode
I had seen you said u held volume down and power button to get into safe mode, you only hold down volume down and hit power button to turn on, let go power button continue hold volume down.
rleighska said:
I have tried that TAR file, numerous times, same results as previously described. I didn't think to try a different USB cable, was using 3.0 as it came with the phone, but just now switched to the 2.0 and am also getting the same results.
Click to expand...
Click to collapse
:crying: Let me give it a search on google and see what i can find.
Still nothing; all i can find is to restore to stock
Nyc1231 said:
:crying: Let me give it a search on google and see what i can find.
Still nothing; all i can find is to restore to stock
Click to expand...
Click to collapse
I'd be thrilled if I could restore to stock. At least then I could start fresh. I tried the method in my very first post on this thread and had no luck with that either.
xposed and gravity
Could b strong possibility that xposed and gravity causing bootloop, i would try n get to safe mode at all costs
Iceburn1 said:
Could b strong possibility that xposed and gravity causing bootloop, i would try n get to safe mode at all costs
Click to expand...
Click to collapse
I can't get it to boot to recovery. When it starts it shows the kernel message at the top in yellow, the samsung logo etc. and will not move from that screen. The only other thing I can do is put it in download mode.
safe mode
Safe mode is different from download and recovery it boots you into phone so u can disable xposed or gravity lossiboy the cause
rleighska said:
I'd be thrilled if I could restore to stock. At least then I could start fresh. I tried the method in my very first post on this thread and had no luck with that either.
Click to expand...
Click to collapse
Have you try using different version of odin when restoring to a stock firmware?
Sent from my SM-G900P using Tapatalk
Iceburn1 said:
I had seen you said u held volume down and power button to get into safe mode, you only hold down volume down and hit power button to turn on, let go power button continue hold volume down.
Click to expand...
Click to collapse
I tried that and it still goes right to the samsung screen with
recovery booting.... in blue
set warranty bit : recovery in yellow
Hi,
So I was trying to root my phone and it all went wrong. I have rooted tons of phones before, but never a Samsung (never again).
The phone will show the Samsung Boot screen, but then it either goes black, with a flashing blue LED, or it boots itself into recovery.
When I use ODIN, the flash fails at "system.img.ext4" whenever I use just the AP field. If I load all the fields in, it fails at "xbl.elf"
I got the firmware file from SamMobile, so I don't think that is the issue, but who knows. It's as if the phone no longer has an OS on it. I also tried using SmartSwitch as well, but I have no idea what the S/N on this phone is. It was originally a Sprint phone and was working fine, but I could never find the S/N. It is nowhere on the phone itself, and was not listed when I typed #*06#. All I have is the IMEI.
Finally, when it is in recovery, there is a message at the bottom that reads, "dm-verity verification failed".
Sorry for the bullet point style here, I am on mobile. If anyone can assist, I would be very grateful!
ebercon said:
Hi,
So I was trying to root my phone and it all went wrong. I have rooted tons of phones before, but never a Samsung (never again).
The phone will show the Samsung Boot screen, but then it either goes black, with a flashing blue LED, or it boots itself into recovery.
When I use ODIN, the flash fails at "system.img.ext4" whenever I use just the AP field. If I load all the fields in, it fails at "xbl.elf"
I got the firmware file from SamMobile, so I don't think that is the issue, but who knows. It's as if the phone no longer has an OS on it. I also tried using SmartSwitch as well, but I have no idea what the S/N on this phone is. It was originally a Sprint phone and was working fine, but I could never find the S/N. It is nowhere on the phone itself, and was not listed when I typed #*06#. All I have is the IMEI.
Finally, when it is in recovery, there is a message at the bottom that reads, "dm-verity verification failed".
Sorry for the bullet point style here, I am on mobile. If anyone can assist, I would be very grateful!
Click to expand...
Click to collapse
I'm new to the s7. long time lg man
on lg ussally means either ure trying to flash a non signed image or downgrade a qfused bootloader anti rollback which sprint is good for.
in dl mode after fail its not showing anything about binary and stuff in red is it
TheMadScientist420 said:
I'm new to the s7. long time lg man
on lg ussally means either ure trying to flash a non signed image or downgrade a qfused bootloader anti rollback which sprint is good for.
in dl mode after fail its not showing anything about binary and stuff in red is it
Click to expand...
Click to collapse
It does say something about binary in there. Binary 3 I believe. I'll have to try again to get the error.
ebercon said:
It does say something about binary in there. Binary 3 I believe. I'll have to try again to get the error.
Click to expand...
Click to collapse
sounds the firmware u are flashing is older than what you have on the device hence the fail
try to find newer firmware and try flashing it
download
Download official nougat from sam mobile then flash with Odin. It will definitely solve your problem
amol6630 said:
Download official nougat from sam mobile then flash with Odin. It will definitely solve your problem
Click to expand...
Click to collapse
I may try this as well. I flashed the newest firmware I could find other than Nougat and I now have it booting all the way up and then after about a minute, it loops again. It is at least further along than before.
I just remembered one detail: The original issue began when I flashed a modified boot.img to the phone during a rooting attempt. Could this be what is still causing the issue and preventing a reformatting of the phone from solving the issue? So lost with this thing...
Try with latest firmware + pit file + tick re-partition
ebercon said:
I may try this as well. I flashed the newest firmware I could find other than Nougat and I now have it booting all the way up and then after about a minute, it loops again. It is at least further along than before.
I just remembered one detail: The original issue began when I flashed a modified boot.img to the phone during a rooting attempt. Could this be what is still causing the issue and preventing a reformatting of the phone from solving the issue? So lost with this thing...
Click to expand...
Click to collapse
Sorry to revive this thread but did this work cause its currently happening to me
If your phone is an original, S/N may be engraved in the back... it's a little bit hard to note but put a spotlight near it so that you can identify it better.
hhh ^^
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
Hi! I have a Idol 3 (6045I variant) and everytime I try to restore to stock using Mobile Upgrade Q it gets to the part where it says "Searching the server for latest available software" then the phone turns on normally and it says "Download update software package failed. Please check your internet connection." and it does this on two computers that I have tried with two different upgrade Q versions. Could someone please help me identify the problem?
It seems Alcatel abandoned our device.
It seems Alcatel abandoned our device.
Ha, ha...
Look the reason you are getting the message is because you restored your phone once on IP 240.4.4.xx.x.xx.xx. If you use another IP address you would not get that message. So, use a vpn or change you IP or use someone else's internet connection. It has happened to me more then once and was very frustrating as until I figured it out. Go to google and type in "What is my IP address" and start their.
HEY OFF TOPIC but can you believe that XPOSED is finally released for Nougat!!!!
vq8acsxht said:
It seems Alcatel abandoned our device.
Ha, ha...
Look the reason you are getting the message is because you restored your phone once on IP 240.4.4.xx.x.xx.xx. If you use another IP address you would not get that message. So, use a vpn or change you IP or use someone else's internet connection. It has happened to me more then once and was very frustrating as until I figured it out. Go to google and type in "What is my IP address" and start their.
HEY OFF TOPIC but can you believe that XPOSED is finally released for Nougat!!!!
Click to expand...
Click to collapse
This doesn't seem to be the case because even after using a different internet connections and a vpn it still throws out an error message and after updating to a newer version of upgrade q it says "There is no greater version available to upgrade your phone" which doesn't make any sense.
chewyboy0 said:
This doesn't seem to be the case because even after using a different internet connections and a vpn it still throws out an error message and after updating to a newer version of upgrade q it says "There is no greater version available to upgrade your phone" which doesn't make any sense.
Click to expand...
Click to collapse
Good, it says "There is no greater version available to upgrade your phone" now do a factory reset of the phone. If you did not destory the recovery partition you should be good to go.
chewyboy0 said:
Hi! I have a Idol 3 (6045I variant) and everytime I try to restore to stock using Mobile Upgrade Q it gets to the part where it says "Searching the server for latest available software" then the phone turns on normally and it says "Download update software package failed. Please check your internet connection." and it does this on two computers that I have tried with two different upgrade Q versions. Could someone please help me identify the problem?
Click to expand...
Click to collapse
Use this program here ...
https://mega.nz/#!9UdDGJLI!9S87X0wH0OEc3nKSd7dZHCES7RpDW8iWpPnPSqCPLzs (I'm trying to think of how this goes by memory so bare with me)
make sure you have the drivers installed. extract the file and the password is in the txt file. I can't remember the exact steps, but I think it will do some type of update or you go to "get version" if you don't see 6045 in the device list. once it's there you can go to the grey box besides get version that says update or download or something. my brain heh I can't remember, but then you click that and it will bring you back to stock. I did it on my 6045O flawlessly. It brought me right into the latest update. also if you go into the program files and go to the Sugar software folder after it's downloading the latest firmware for your phone and you go to the bin folder you should see a downloaded folder with your model number plus some other numbers and letters. copy that to your desktop. once that's done find the file starting with "R" that is the recovery image. delete that and replace it with twrp recovery image and just name it recovery. go back into the main Sugar folder in the program files and replace the folder with your model number with that folder. you also see a folder named download. that is the downloaded firmware you can delete that folder and just leave the modded folder with your model number containing the twrp recovery image. meanwhile, go through the setup process on your phone and skip all the steps you can and go into the phone. go to the about device and tap on the build number to unlock the developer options. make sure the OEM bootloader unlock is toggled and I just changed the usb debugging also although I don't think that's necessary. go back into the Sugar program and then go to just the update or whatever it is beside the get version and click that and it will update the phone with the latest firmware and it will put the custom recovery on it. make sure once it's done downloading you unplug it and turn it off then go into recovery mode by holding the power down and volume up until the main logo comes up then let go of power and keep holding volume up until twrp boots up. make sure you already have the latest SuperSU zip on your sdcard. go to the terminal or sometimes one comes up from the beginning and enter the systemless supersu line/code or whatever you call it and then hit enter or if it will go straight into twrp first do a factory reset in the advanced wipe tab then the systemless supersu terminal line code and then install the supersu zip. that's it. your back to the latest firmware and rooted. oh and btw, I forgot if you have to be in download mode when you are using the Sugar program. I play around in several phones so forgot at the moment. If you need to go into download mode just plug in the usb as your holding power, volume up and down at the same time and then when it goes into the download mode screen hold volume up for 5-10 seconds until the screen goes black. I hope it helps and sorry if any of this is confusing. It can be a bit advanced for some.
Mobile Q doesnt work here too.
With or Without VPN cant download the update package :/
irinae said:
Mobile Q doesnt work here too.
With or Without VPN cant download the update package :/
Click to expand...
Click to collapse
Press and hold the Volume up button, then briefly press the Power button. Keep pressing the Volume up button. Scroll to the desired language using the Volume down button, then press the Power button. Scroll to wipe data/factory reset by pressing the Volume down button.
Then try to do an update OTA.
If you are running stock and have for the last 6 months or so, their are not any new updates???
Just curious why you would think their is an update??
Also, "There is no greater version available to upgrade your phone" chewyboy0 admitted that Mobile Q software does work because Mobile Q software had to go out to the Alcatel servers to check which version he had.
Finally, Also, you gave no reference of whether you are running stock ROM, Rooted?? TWRP?? or for that matter whether you Samsung Galaxy phone can be plugged into the Mobile Q software. In other words, your coming up a little short on details.
I am running a custom ROM and I wanted to go back to stock for various reasons but I will try one of the methods above.
Brian9285 said:
Use this program here ...
https://mega.nz/#!9UdDGJLI!9S87X0wH0OEc3nKSd7dZHCES7RpDW8iWpPnPSqCPLzs (I'm trying to think of how this goes by memory so bare with me)
make sure you have the drivers installed. extract the file and the password is in the txt file. I can't remember the exact steps, but I think it will do some type of update or you go to "get version" if you don't see 6045 in the device list. once it's there you can go to the grey box besides get version that says update or download or something. my brain heh I can't remember, but then you click that and it will bring you back to stock. I did it on my 6045O flawlessly. It brought me right into the latest update. also if you go into the program files and go to the Sugar software folder after it's downloading the latest firmware for your phone and you go to the bin folder you should see a downloaded folder with your model number plus some other numbers and letters. copy that to your desktop. once that's done find the file starting with "R" that is the recovery image. delete that and replace it with twrp recovery image and just name it recovery. go back into the main Sugar folder in the program files and replace the folder with your model number with that folder. you also see a folder named download. that is the downloaded firmware you can delete that folder and just leave the modded folder with your model number containing the twrp recovery image. meanwhile, go through the setup process on your phone and skip all the steps you can and go into the phone. go to the about device and tap on the build number to unlock the developer options. make sure the OEM bootloader unlock is toggled and I just changed the usb debugging also although I don't think that's necessary. go back into the Sugar program and then go to just the update or whatever it is beside the get version and click that and it will update the phone with the latest firmware and it will put the custom recovery on it. make sure once it's done downloading you unplug it and turn it off then go into recovery mode by holding the power down and volume up until the main logo comes up then let go of power and keep holding volume up until twrp boots up. make sure you already have the latest SuperSU zip on your sdcard. go to the terminal or sometimes one comes up from the beginning and enter the systemless supersu line/code or whatever you call it and then hit enter or if it will go straight into twrp first do a factory reset in the advanced wipe tab then the systemless supersu terminal line code and then install the supersu zip. that's it. your back to the latest firmware and rooted. oh and btw, I forgot if you have to be in download mode when you are using the Sugar program. I play around in several phones so forgot at the moment. If you need to go into download mode just plug in the usb as your holding power, volume up and down at the same time and then when it goes into the download mode screen hold volume up for 5-10 seconds until the screen goes black. I hope it helps and sorry if any of this is confusing. It can be a bit advanced for some.
Click to expand...
Click to collapse
Hey I think this is working its currently downloading at 27% I will let u know the progress. Thanks so much!!
chewyboy0 said:
Hey I think this is working its currently downloading at 27% I will let u know the progress. Thanks so much!!
Click to expand...
Click to collapse
This one work but it was way simplier to restore to factory default via the Mobile Q like before.
Bah i don't care anymore my 5.5 battery does strange things so i get a Xiaomi Mi5 from work to replace it.
I am from india, using 6045k, lost duel sim support duo to flashing of marionette's Rom. Still trying to get duel sim back, tried eluga firmware also, but unfortunately i didn't get any error at 45%. Now i am using flyos 2.0, its working like charm. But only one sim is there, i tried several software upgrader versions, but server is not connecting, its always stuck at 20%.
Pls help me.
Siraj Enriq said:
I am from india, using 6045k, lost duel sim support duo to flashing of marionette's Rom. Still trying to get duel sim back, tried eluga firmware also, but unfortunately i didn't get any error at 45%. Now i am using flyos 2.0, its working like charm. But only one sim is there, i tried several software upgrader versions, but server is not connecting, its always stuck at 20%.
Pls help me.
Click to expand...
Click to collapse
Currently Alcatel has disabled the posibility of reflashing a stock ROM with Mobile Upgrade Q, so the only way is by flashing via TWRP or Sahara tool.
I have a 6045Y in latest stock MM (Build 22) and i'm incapable of performing a flash with Mobile Upgrade Q in order to clean my modified /system, the worst thing is that there is no flashable zip of this version which contain many critical fixes. I'm too very annoyed with this change of policy of Alcatel/TCL, they want me to buy a new smatphone but I'll not give them that pleasure, the Idol 3 5.5 is the best smartphone i've ever had in terms of hardware, it's a shame...
ciclolars said:
Currently Alcatel has disabled the posibility of reflashing a stock ROM with Mobile Upgrade Q, so the only way is by flashing via TWRP or Sahara tool.
I have a 6045Y in latest stock MM (Build 22) and i'm incapable of performing a flash with Mobile Upgrade Q in order to clean my modified /system, the worst thing is that there is no flashable zip of this version which contain many critical fixes. I'm too very annoyed with this change of policy of Alcatel/TCL, they want me to buy a new smatphone but I'll not give them that pleasure, the Idol 3 5.5 is the best smartphone i've ever had in terms of hardware, it's a shame...
Click to expand...
Click to collapse
Did u tried sugar mtk tool??
Siraj Enriq said:
Did u tried sugar mtk tool??
Click to expand...
Click to collapse
No, could you share the link? Thanks in advance.
ciclolars said:
No, could you share the link? Thanks in advance.
Click to expand...
Click to collapse
Thank god, today I got my phone to stock rom, by using q5.1.8.
Actually, yesterday only i heard about q.5.1.8, its been a year that i was trying to do this. Appart from q5.1.8, i connected VPN to U. S. Now everything is fine.
I dont know which one helped me, that the q5.1.8 or the VPN. :laugh:
Thanks to all.
Siraj Enriq said:
Thank god, today I got my phone to stock rom, by using q5.1.8.
Actually, yesterday only i heard about q.5.1.8, its been a year that i was trying to do this. Appart from q5.1.8, i connected VPN to U. S. Now everything is fine.
I dont know which one helped me, that the q5.1.8 or the VPN. [emoji23]
Thanks to all.
Click to expand...
Click to collapse
How exactly did you managed to do it? Is it possible to reflash the stock ROM?
ciclolars said:
How exactly did you managed to do it? Is it possible to reflash the stock ROM?
Click to expand...
Click to collapse
Actually, software upgrader can do the job. But the problem was slow server speed. Use q. 5.1.8, simply connect your in switch off condition, and try upgrading, if its not working, try VPN. I tried psyphon VPN connected to USA. In india serveris very slow.
6045k still running on lilopop, thats why people go going for stock roms.
Siraj Enriq said:
Actually, software upgrader can do the job. But the problem was slow server speed. Use q. 5.1.8, simply connect your in switch off condition, and try upgrading, if its not working, try VPN. I tried psyphon VPN connected to USA. In india serveris very slow.
6045k still running on lilopop, thats why people go going for stock roms.
Click to expand...
Click to collapse
In my case, Mobile Upgrade Q display a message that says I'm currently in the latest software version so it doesn't allow me to reflash stock ROM. My device is a 6045Y build 22 MM.
ciclolars said:
In my case, Mobile Upgrade Q display a message that says I'm currently in the latest software version so it doesn't allow me to reflash stock ROM. My device is a 6045Y build 22 MM.
Click to expand...
Click to collapse
Try Sugar Mtk tool
https://mega.nz/#!9UdDGJLI!9S87X0wH0...8iWpPnPSqCPLzs
Details is there on this thread.
I never tried it, try it. Read above msg by member Brian9285
I have a Galaxy 7 G930P and i try to reset this phone for unlock a Google Account with Odin and other Boot Loader, but I bricked this phone and now only the phone restarts alone and does not turn up the system. I can put this phone in download mode and i need Help for Install all with the correct stock fimwares. Thanks and i hope fixed this...
billaboy said:
I have a Galaxy 7 G930P and i try to reset this phone for unlock a Google Account with Odin and other Boot Loader, but I bricked this phone and now only the phone restarts alone and does not turn up the system. I can put this phone in download mode and i need Help for Install all with the correct stock fimwares. Thanks and i hope fixed this...
Click to expand...
Click to collapse
Cannot help much if there is no details on what your phone bootloader/firmware versions were before flash, and what versions you were trying to flash.
If you were flashing a lower version of BL to your phone, you can flash your original firmware back to your phone.
If you were flashing a higher version of BL, you will need to find a new version of BL/firmware , such as the latest U firmware, to Odin into the phone..
billaboy said:
I have a Galaxy 7 G930P and i try to reset this phone for unlock a Google Account with Odin and other Boot Loader, but I bricked this phone and now only the phone restarts alone and does not turn up the system. I can put this phone in download mode and i need Help for Install all with the correct stock fimwares. Thanks and i hope fixed this...
Click to expand...
Click to collapse
yves31 said:
Cannot help much if there is no details on what your phone bootloader/firmware versions were before flash, and what versions you were trying to flash.
If you were flashing a lower version of BL to your phone, you can flash your original firmware back to your phone.
If you were flashing a higher version of BL, you will need to find a new version of BL/firmware , such as the latest U firmware, to Odin into the phone..
Click to expand...
Click to collapse
Read this thread
https://forum.xda-developers.com/sprint-galaxy-s7/help/bloat-free-firmware-930u-tried-t3428974
Since you mentioned a Google account, just make sure you know the user and password of the last working Google account on the phone. Sounds like you tried to flash a firmware with an older bootloader.
And if you don't know that info and were trying to carrier unlock it via some back door method, don't follow the thread that I just linked.
semi-bricked
this happened to me as well. dont have access to this device since november. flashing the phone with official samsung firmware doesnt seem to work either,cant boot into recovery
TormentedHeart said:
this happened to me as well. dont have access to this device since november. flashing the phone with official samsung firmware doesnt seem to work either,cant boot into recovery
Click to expand...
Click to collapse
Can you get into download mode? Power + home + volume down?
lvpre said:
Can you get into download mode? Power + home + volume down?
Click to expand...
Click to collapse
yes i can. flashing stock firmware doesnt seem to fix the probelm either
TormentedHeart said:
yes i can. flashing stock firmware doesnt seem to fix the probelm either
Click to expand...
Click to collapse
Do you receive an error message when flashing? Also, have you tried another USB cable and make sure you use an usb 2.0 port too.
lvpre said:
Do you receive an error message when flashing? Also, have you tried another USB cable and make sure you use an usb 2.0 port too.
Click to expand...
Click to collapse
no error message it flashes successfully with odin but when the phone itself starts to update the firmware after 33% it just reboots then fails. then i get a error screen and well no recovery. no one locally seemed to be able to fix the issue either so update: i sent it away to try to fix. https://imgur.com/a/knxKIKM