Rooted SM-N950U won't boot up (Please Help) :( - Samsung Galaxy Note 8 Questions and Answers

Okay I've had my phone rooted for awhile and I was trying to watch a movie and the movie kept buffering and apps were running very slow. So I decided I would try to remove some of the bloatware to see if it helped. I installed Root Uninstaller by KunKunSoft (GooglePlay Store) and selected a bunch of packages to remove that I thought would be safe enough to remove from my device... After the restart the phone never booted back up, it stays on the Verizon logo screen until phone dies, if I plug it up while it reboots it just keeps on Verizon logo screen with the 4 or 5 colored dots running at bottom and device get super hot.. I've left it going overnight and it never started up. I am thinking I screwed something up but I don't wanna lose my apps/data I have on device... I found out later that my internet was down and that was what was causing all the slowness on my device later which really has bummed me out about screwing my phone up.
Can anyone help me pls?
This is the root process I used back in December 2017 https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340
This is the app I installed this weekend that I somehow screwed my phone up with https://play.google.com/store/apps/details?id=com.kunkunsoft.rootuninstaller
Thanks in advance

Boot into recovery, Volume up, Bixby button and power button and then factory reset see if that helps

KevandLynds said:
Boot into recovery, Volume up, Bixby button and power button and then factory reset see if that helps
Click to expand...
Click to collapse
Couldn't get it in boot into recovery, tried that several times. Not 100% but I don't think it has a recovery with that root process but what do I know... I've messed up my phone
Even if recovery worked a Factory Reset would erase all data which I would like not to have to do if at all possible unless its a last resort and no other way to fix it. But thats (if) recovery boot would work.....

EBtestDroid said:
Couldn't get it in boot into recovery, tried that several times. Not 100% but I don't think it has a recovery with that root process but what do I know... I've messed up my phone
Even if recovery worked a Factory Reset would erase all data which I would like not to have to do if at all possible unless its a last resort and no other way to fix it. But thats (if) recovery boot would work.....
Click to expand...
Click to collapse
Can you go to download mode and flash stock? I believe using home_csc would not wipe, if I'm not mistaken.

sefrcoko said:
Can you go to download mode and flash stock? I believe using home_csc would not wipe, if I'm not mistaken.
Click to expand...
Click to collapse
Thank you for your help and reply.
Sorry been crazy busy lately. In a panic about this phone.. I have very important photos on this phone that I can not lose.
I lost my home and everything in it last year and I am in process of a claim with my insurance company. The phone has A LOT of photos of my home and the damage. I never backed up the photos or attached a cloud or anything so I'm in a mess.
Can anyone confirm that if I flashed the home_csc that it wouldn't wipe such data since sefrcoko isn't 100%? Hopefully if that is the only way I can learn how to do it without making any mistakes

sefrcoko said:
Can you go to download mode and flash stock? I believe using home_csc would not wipe, if I'm not mistaken.
Click to expand...
Click to collapse
Ok so no one has given any other suggestions or confirmations so I decided to take the plunge. I went into download mode and loaded my phones home_csc into Odin and flashed it. However there isn't any change. Phone wont boot up. Stays on Verizon logo with dots running across until phone dies of plugged in the phone just gets super hot and stays on that screen. Scared to leave it plugged in long with as hot as it gets. I've left it going about 4 hrs.
Please chime in if you know how to fix such issues (

EBtestDroid said:
Ok so no one has given any other suggestions or confirmations so I decided to take the plunge. I went into download mode and loaded my phones home_csc into Odin and flashed it. However there isn't any change. Phone wont boot up. Stays on Verizon logo with dots running across until phone dies of plugged in the phone just gets super hot and stays on that screen. Scared to leave it plugged in long with as hot as it gets. I've left it going about 4 hrs.
Please chime in if you know how to fix such issues (
Click to expand...
Click to collapse
Hi, did you load the other files in Odin too, or just home_csc? You should be loading the other files before flashing, along with either home_csc (which doesn't wipe data) or csc (which does wipe data).
In your case use home_csc, since you want to keep your data intact and are not changing csc. The regular csc file should usually only be used when you're flashing firmware that has a different csc than your current one (and therefore requires the wipe in order to avoid conflicts with the old csc).

sefrcoko said:
Hi, did you load the other files in Odin too, or just home_csc?
You should be loading the other files before flashing, along with either home_csc (which doesn't wipe) or csc (which wipes). In your case use home_csc, since you want to keep data intact are not changing csc.
The regular CSC file should usually only be used when you're flashing to firmware that has a different CSC than your current one (and therefore requires the wipe for the new csc to work properly without conflicting with the old one).
Click to expand...
Click to collapse
No I only loaded that single home_csc file. Okay, awesome! I didn't wanna experiment alone and risk screwing something up and losing anything. Thank you so much for your reply! I will be trying this first thing in the morning and will report back. Thank you again!!

EBtestDroid said:
No I only loaded that single home_csc file. Okay, awesome! I didn't wanna experiment alone and risk screwing something up and losing anything. Thank you so much for your reply! I will be trying this first thing in the morning and will report back. Thank you again!!
Click to expand...
Click to collapse
Sounds good...always best to be safe in a case like this. Keep us posted!

sefrcoko said:
Sounds good...always best to be safe in a case like this. Keep us posted!
Click to expand...
Click to collapse
Alright so I just finished using BL, AP, CP, home_csc and it passed. Only thing I didn't use anything on was USERDATA.
Phone is still on Verizon logo with dots running across like before... I will leave it for awhile and see if anything happens..
I hope I am using the correct files, I am using the factory firmware. As I mentioned before the phone was rooted WITH THIS PROCCESS back in December. I think I have messed up. Sucks being a newbie about all of this stuff.

EBtestDroid said:
Alright so I just finished using BL, AP, CP, home_csc and it passed. Only thing I didn't use anything on was USERDATA.
Phone is still on Verizon logo with dots running across like before... I will leave it for awhile and see if anything happens..
I hope I am using the correct files, I am using the factory firmware. As I mentioned before the phone was rooted WITH THIS PROCCESS back in December. I think I have messed up. Sucks being a newbie about all of this stuff.
Click to expand...
Click to collapse
What files are you flashing? Make sure you're not flashing anything that says U4 in the name or you will not be able to root again until a root method is found for Bootloader v4.
Also.....NEVER use any app that says unroot or anything of that sort without first asking the community. As you can see, it can lead to situations like this.

EBtestDroid said:
Alright so I just finished using BL, AP, CP, home_csc and it passed. Only thing I didn't use anything on was USERDATA.
Phone is still on Verizon logo with dots running across like before... I will leave it for awhile and see if anything happens..
I hope I am using the correct files, I am using the factory firmware. As I mentioned before the phone was rooted WITH THIS PROCCESS back in December. I think I have messed up. Sucks being a newbie about all of this stuff.
Click to expand...
Click to collapse
It might take some time at that screen but should work eventually. If it stays like that for over 30-40min though there's probably something wrong. Might be worthwhile asking in the SamFail thread as they might have more experience with this root method (I have an Exynos).

AP_N950USQS2BQK2_CL12461033_QB15680825_REV00_user_low_ship_MULTI_CERT_meta.tar
BL_N950USQS2BQK2_CL12461033_QB15680825_REV00_user_low_ship_MULTI_CERT.tar
CP_N950USQS2BQK2_CP8012179_CL12461033_QB15680825_REV00_user_low_ship_MULTI_CERT.tar
HOME_CSC_OYN_N950UOYN2BQK2_CL12461033_QB15680825_REV00_user_low_ship_MULTI_CERT.tar
These are the files I tried using.
I currently have phone plugged into wall charger to keep it on. Its still on Verizon loading boot logo screen.
Crossing fingers here.
Thanks for the help

EBtestDroid said:
AP_N950USQS2BQK2_CL12461033_QB15680825_REV00_user_low_ship_MULTI_CERT_meta.tar
BL_N950USQS2BQK2_CL12461033_QB15680825_REV00_user_low_ship_MULTI_CERT.tar
CP_N950USQS2BQK2_CP8012179_CL12461033_QB15680825_REV00_user_low_ship_MULTI_CERT.tar
HOME_CSC_OYN_N950UOYN2BQK2_CL12461033_QB15680825_REV00_user_low_ship_MULTI_CERT.tar
These are the files I tried using.
I currently have phone plugged into wall charger to keep it on. Its still on Verizon loading boot logo screen.
Crossing fingers here.
Thanks for the help
Click to expand...
Click to collapse
Hmm that seems right but I can't really figure out what's going on...if it is still hanging on that Verizon screen then it did not work as expected. Try posting in the SamFail thread and see if they can offer some extra help. They are more familiar with this particular root method, so there's probably some nuance that I'm missing here.
Edit: Check out this post from the SamFail thread, it basically summarizes what I said, so it looks like that should have worked... Are you using the latest Odin version? And are you using the right firmware (and bootloader version)? Maybe post a screenshot of the files you loaded in Odin and the log it shows once you flashed everything?
https://forum.xda-developers.com/showthread.php?p=76233727

Alright I'll take a picture now.
Never booted up but it didn't get as hot as normally if that matters..
Brb

Jammol said:
What files are you flashing? Make sure you're not flashing anything that says U4 in the name or you will not be able to root again until a root method is found for Bootloader v4.
Also.....NEVER use any app that says unroot or anything of that sort without first asking the community. As you can see, it can lead to situations like this.
Click to expand...
Click to collapse
sefrcoko said:
Hmm that seems right but I can't really figure out what's going on...if it is still hanging on that Verizon screen then it did not work as expected. Try posting in the SamFail thread and see if they can offer some extra help. They are more familiar with this particular root method, so there's probably some nuance that I'm missing here.
Edit: Check out this post from the SamFail thread, it basically summarizes what I said, so it looks like that should have worked... Are you using the latest Odin version? And are you using the right firmware (and bootloader version)? Maybe post a screenshot of the files you loaded in Odin and the log it shows once you flashed everything?
https://forum.xda-developers.com/showthread.php?p=76233727
Click to expand...
Click to collapse
Sorry had to plug up Home PC and figure out how to post pictures, was using work computer earlier.
About to check thread you referred me to, just making sure I got the screenshots up. Should I record my screen to show process or is it not necessary?
Using Odin3_v3.13.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I will try this computer and see if anything different happens.
I'm not 100% but I might be loading wrong ones because I think I remember AQ2 but not 100%...
Sorry I don't know how to check but I am very grateful for your patience and help.... ://

You cannot swap between Samfail and stock without wiping. IF you want to keep your data right now just redo the samfail method using hte samfail files.Since you are on blv1 just use samfail v1

Okay getting failed now
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> abl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

me2151 said:
You cannot swap between Samfail and stock without wiping. IF you want to keep your data right now just redo the samfail method using hte samfail files.Since you are on blv1 just use samfail v1
Click to expand...
Click to collapse
Okay will try.
Thank you

EBtestDroid said:
I'm not 100% but I might be loading wrong ones because I think I remember AQ2 but not 100%...
Sorry I don't know how to check but I am very grateful for your patience and help.... ://
Click to expand...
Click to collapse
You can check the bootloader revision when you are in download mode. It's the 3rd line up from the bottom that starts with rp swrev :. Mine says B4 because I'm on revision 4 witch is the newest.
View attachment 4504535

Related

[Q] Brick after trying to install Gingerbread

Hi i am on a captivate i896. I tried to install I897UCKF1. Everything was fine till it had to reboot after installation then i couldn't do anything. I can't install stock rom, the phone reboots with att logo and it doesn't do anything. I think its the bootloader that is messed up and i don't know how to install the older ones or just to be able to get back to rogers 2.1 stock or ATT 2.1 stock. I am always stuck at this screen :
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I897UCKF1_CL273832_REV02_user_low_ship.tar.md 5 is valid.
<OSM> MODEM_I897UCKF1_CL1017518_REV02.tar.md5 is valid.
<OSM> SGH-I897-CSC-ATTKF1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
When i try to install JF6 it stalls at File Analysis....
Please help.
try and get it into download mode. Its not bricked justyet.
accordztech said:
try and get it into download mode. Its not bricked justyet.
Click to expand...
Click to collapse
i tried to get in download mode and i can but i just can't get to install any stock roms i can't do anything. Do you know if i can install the booloaders or anything?
ramih2085 said:
i tried to get in download mode and i can but i just can't get to install any stock roms i can't do anything. Do you know if i can install the booloaders or anything?
Click to expand...
Click to collapse
Restart your computer and if running windows vista or 7 make sure you run Odin as an administrator and possibly even compatibility mode. I have had that problem before and a restart fixed it.
Sent from my GT-I9000 using XDA Premium App
tried it, still the same thing...
i read something about bootloaders are different for the gingerbread build than the normal eclair and froyo. I don't know if i have to do something different. I just wanna get back to stock 2.1 from there i can find my way out...
ramih2085 said:
i read something about bootloaders are different for the gingerbread build than the normal eclair and froyo. I don't know if i have to do something different. I just wanna get back to stock 2.1 from there i can find my way out...
Click to expand...
Click to collapse
Did you try the Odin 1 click for stock JF6 posted by Designgears in the development forum? It flashes both bootloaders that are need to get back to stock.
yes i did, and it stalls at file analysis....usually it works but now i don't know why!
ramih2085 said:
yes i did, and it stalls at file analysis....usually it works but now i don't know why!
Click to expand...
Click to collapse
Try a different usb port and/or cable.
jhernand1102 said:
Try a different usb port and/or cable.
Click to expand...
Click to collapse
I tried all the usb ports on my computers. Odin always detects my phone but for some reason i can't install anything on it.
ramih2085 said:
I tried all the usb ports on my computers. Odin always detects my phone but for some reason i can't install anything on it.
Click to expand...
Click to collapse
I has an issue like this once where it would get stuck during the flash and my screen would turn different colors. I got it to work by using the full odin where you can select the pda & pit files. Give it a try.
jhernand1102 said:
I has an issue like this once where it would get stuck during the flash and my screen would turn different colors. I got it to work by using the full odin where you can select the pda & pit files. Give it a try.
Click to expand...
Click to collapse
i did that too, nothing worked...
anyone has an idea of what to do?
ramih2085 said:
anyone has an idea of what to do?
Click to expand...
Click to collapse
Try using the Odin version provided in this thread:
http://forum.xda-developers.com/showthread.php?t=1127249
It should restore to stock 2.3.3 Gingerbread. Not sure if being a UCKF1 poses a problem in your device or location, but I suppose it's worth a shot. Note that the rest of the instructions is to root the device, you don't need to do all those other steps. Just download the Odin One-Click, and try it out. Regards.
ramih2085 said:
I tried all the usb ports on my computers. Odin always detects my phone but for some reason i can't install anything on it.
Click to expand...
Click to collapse
I have the same problem . Please help ! Thankss.
ramih2085 said:
i did that too, nothing worked...
Click to expand...
Click to collapse
my AT&T Captivate is 2.2 stock with root,unlocked . I flash Stock+voodoo-froyo I897 UCKB1.tar. it said FAIL. try to go back 2.1 stock but it can't do anything.Please help! Thanks
ramih2085 said:
i did that too, nothing worked...
Click to expand...
Click to collapse
what is PIT files ? and how can I get it ? I want to try it .Thanks .
Mr. Janderson said:
Try using the Odin version provided in this thread:
http://forum.xda-developers.com/showthread.php?t=1127249
It should restore to stock 2.3.3 Gingerbread. Not sure if being a UCKF1 poses a problem in your device or location, but I suppose it's worth a shot. Note that the rest of the instructions is to root the device, you don't need to do all those other steps. Just download the Odin One-Click, and try it out. Regards.
Click to expand...
Click to collapse
i tried that and here is the log:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
also for the pit file, it is usually included in the zip file with odin 3 click so if you download odin 1 click, u dont need that file.
captivate bricked
flashing power off charging logo when try to reboot . no down load mode cant do sh%t.help please
See the "Captivate Connection Issues and Download Mode Help" that is linked in my signature below.
If that does not help then...
Sounds like you are gonna need a JIG. See my signature link below for links to how to make one or where to buy one.
When you get back into download mode, you are gonna need to flash a Stock Firmware of your choice. There is a sticky thread in the Captivate Development Forum that you will need to see for those.

Bricked Tab :(

hi people,
So here is my issue, i rooted my tab after having it about a year and wanted to install a custom rom, installed RomManager from the market and installed the clockwork recovery mod, BUT i picked galaxy tab 10.1 when it asked me what phone i had, as there was no other option. I checked on google first and it seems other people with the 8.9 are using the clockwork recovery mod so i thought it was safe.
Now its dead and powers up to the samsung logo, and then dies again.
Help! (currently i am draining the battery as it is mentioned in another thread in this forum)
Thanks
(tried the APX thing in nvflash and it was a no go)
epictwiglet said:
hi people,
So here is my issue, i rooted my tab after having it about a year and wanted to install a custom rom, installed RomManager from the market and installed the clockwork recovery mod, BUT i picked galaxy tab 10.1 when it asked me what phone i had, as there was no other option. I checked on google first and it seems other people with the 8.9 are using the clockwork recovery mod so i thought it was safe.
Now its dead and powers up to the samsung logo, and then dies again.
Help! (currently i am draining the battery as it is mentioned in another thread in this forum)
Thanks
(tried the APX thing in nvflash and it was a no go)
Click to expand...
Click to collapse
It's alright. Go to the guide in my signature and read up about ODIN because you will use it to save your tablet. It's all there in FAQs, How-tos and the Toolkit at the end.
i highly recommend checking out nirogu325's guide for an explanation of ODIN. it should solve your problem
Download Odin
http://www.google.com/url?sa=t&rct=...IxHp1ISlP2fzGKhtw&sig2=4EbBRrWss7eeO2JNr8TzzA
Download the proper recovery
7310 and 7300
http://forum.xda-developers.com/showthread.php?t=1312218
i957
http://forum.xda-developers.com/showthread.php?t=1462770
Power on the tablet, you may need to charge it.
As it is powering on hold down the power and the vol down button
Go into download, not recovery
Connect your tablet to your computer with the USB cable
Open up Odin
You should see box that says PDA, click there and it will want you to find a file. Choice the recovery file
Make sure the box that says partition or repartion are NOT check
then check start and wait. DO NOT touch or disconnect the tablet while it works
bdfull3r said:
i highly recommend checking out nirogu325's guide for an explanation of ODIN. it should solve your problem
Download Odin
http://www.google.com/url?sa=t&rct=...IxHp1ISlP2fzGKhtw&sig2=4EbBRrWss7eeO2JNr8TzzA
Download the proper recovery
7310 and 7300
http://forum.xda-developers.com/showthread.php?t=1312218
i957
http://forum.xda-developers.com/showthread.php?t=1462770
Power on the tablet, you may need to charge it.
As it is powering on hold down the power and the vol down button
Go into download, not recovery
Connect your tablet to your computer with the USB cable
Open up Odin
You should see box that says PDA, click there and it will want you to find a file. Choice the recovery file
Make sure the box that says partition or repartion are NOT check
then check start and wait. DO NOT touch or disconnect the tablet while it works
Click to expand...
Click to collapse
So i dont need the clockwork recovery mod files? just the stock recovery? and it wont boot to download mode so i cant connect it to odin unless im missing something, let me read it again.....
Ok! i have managed to get to download mode, i discharged the tab overnight and plugged it in this morning and he booted past the samsung logo, i cant remember what thread i saw that idea in but it worked. awesome, now to try and flash stock recovery, hope i dont duck it up!
Thanks guys, ill post again if it doesnt work @)
nirogu325 said:
It's alright. Go to the guide in my signature and read up about ODIN because you will use it to save your tablet. It's all there in FAQs, How-tos and the Toolkit at the end.
Click to expand...
Click to collapse
all i get is:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> recovery.img.md5 is invalid.
<OSM> End...
Booooo, now what? im using an old version of odin, so maybe ill try and new one?
Solved! So i was putting the MD5 file and it wasnt working, so i put the whole .RAR file in and it worked! It wouldnt flash the clockwork recovery mod though so i had to put the stock one back on.
Still it works again, thanks guys.
epictwiglet said:
Solved! So i was putting the MD5 file and it wasnt working, so i put the whole .RAR file in and it worked! It wouldnt flash the clockwork recovery mod though so i had to put the stock one back on.
Still it works again, thanks guys.
Click to expand...
Click to collapse
I am glad you have your tablet back in working order.
Well now that you have the stock recovery, you can attempt to flash the Clockwork recovery again the right way if you want to. You now know how to recovery your tablet if you have a brick again so you don't have anything to lose
hi can someone help me with a brick i957. i am not seeing anything on the lcd its totally black however when i plug the usb to the pc its being recognized as Qualcom hs-usb diagnostics 9006. i thought well maybe i can flash it with odin but this is all i am getting:
<ID:0/155> Added!!
<ID:0/155> Removed!!
<ID:0/155> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CWMR5x_i957_recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/155> Odin v.3 engine (ID:155)..
<ID:0/155> File analysis..
<ID:0/155> SetupConnection..
and its been there for almost 45 mins with no response. any help will be greatly appreciated.
Linkzz said:
hi can someone help me with a brick i957. i am not seeing anything on the lcd its totally black however when i plug the usb to the pc its being recognized as Qualcom hs-usb diagnostics 9006. i thought well maybe i can flash it with odin but this is all i am getting:
Added!!
Removed!!
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
CWMR5x_i957_recovery.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:155)..
File analysis..
SetupConnection..
and its been there for almost 45 mins with no response. any help will be greatly appreciated.
Click to expand...
Click to collapse
If Odin recognizes the tab there is a chance to recover it. What rom are you trying to flash? Go to sammobile.com and get the stock gb rom.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
i am using a stock rom from sammy roms but same problem
<ID:0/155> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_I957UCLK4_CL1167230_REV02_user_low_noship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/155> Odin v.3 engine (ID:155)..
<ID:0/155> File analysis..
<ID:0/155> SetupConnection..
Try with odin ver 1.85. I haven't had luck with 3.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
Try with odin ver 1.85. I haven't had luck with 3.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
thats what i have been using; when i try with odin3 v3.07 its not recognizing the tablet
I know it doesn't make sense but keep trying to flash the rom. I've seen it not work for many tries and then it would for some reason. If odin recognizes the tab you are not hard bricked. You should be able to get it to operate again.
Also, use the gb Rom, uckj7
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

[OTA][11/24][SCH-I705] Verizon GTab 2 7" - J1 OTA Update - Pre-Rooted!

This the G3 to J1 OTA. A lot of people are still on the G3 build because of root issues. As some of you may have found out, the hard way, the J1 update does not allow the older root methods and a new method has not been found forcing people to not accept the OTA! This fixes that!
What I have done here is grab the OTA and neutered it so it would not install the "aboot" and not install the "recovery" partitions. On top of that I have pre-rooted it with the latest SuperSU and added my unsecure boot.img. So you get the following...
Features
New Radios / Appropriate firmware
New Kernel
OS changes from G3 to J1
Root will now be in the /system folder so if you wipe data root is still with you :highfive:
You must be on the 100% stock G3 base with root and Clockwork MOD Recovery. If you modified any files you need to restore them because the script checks the files on the /system partition to make sure it has not been tampered with! For example if you installed Gmail from the 4.2 build the script will error out and NOT flash!
If you need to return to stock G3 Base you can do it easy this way: http://forum.xda-developers.com/showthread.php?t=1885558. Thats what I had to do to root the tab so I know for a fact the OTA works 100% off the dump that MrHyde03 made!
Now for the official instructions
Instructions:
Must be at full stock G3 base with no modifications to the system files other than root!
Must have CWM recovery installed, must have the unlocked boot loader installed.
Uninstall Superuser (Yes, uninstall it!)
Copy Patch to Device
Reboot to recovery
Flash Patch. Takes about 3 to 4 minutes to patch.
Profit!
Thanks
Thanks out to MrHyde03 and RevosFTS for testing. Brave souls!
And thanks to other few people who tried but modified the system image therefore could not flash.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DOWNLOAD: HERE
MD5: 6FA20263C6DC961C7F3DFCE554D0BC9A
Please hit Thanks!​
Reserved
Excellent. Also added a reference to here in the root thread under Step 3.
I've been working with scott trying to flash this update..
I fixed the issue with the gmail 4.2 that I put on my tab.. so that is no longer an issue.. (and that was the only thing I changed in my /system partition)..
Now I'm getting an error status 7... with "assert failed: apply_patch_check (" /system/bin/debuggerd")".. when flashing this... not sure what that is? anyone know?
also I'm on the g3 build
Baseband Version: I705VRLG3
Build Number: IMM76D.I705VRALG3
Sounds to me like it's not finding the file at /system/bin/debuggerd. Open root explorer or equivalent and check to see if that file exists. If not, then I'd go through Step 1b (Method 2 - ODIN) on the root thread again to ensure your system is 100% stock.
nexttonomy said:
I've been working with scott trying to flash this update..
I fixed the issue with the gmail 4.2 that I put on my tab.. so that is no longer an issue.. (and that was the only thing I changed in my /system partition)..
Now I'm getting an error status 7... with "assert failed: apply_patch_check (" /system/bin/debuggerd")".. when flashing this... not sure what that is? anyone know?
Click to expand...
Click to collapse
This
|
|
\/
MrHyde03 said:
Sounds to me like it's not finding the file at /system/bin/debuggerd. Open root explorer or equivalent and check to see if that file exists. If not, then I'd go through Step 1b (Method 2 - ODIN) on the root thread again to ensure your system is 100% stock.
Click to expand...
Click to collapse
Agreed. This OTA tested perfect against your Odin stock so if there is an issue when someone tries to flash then they are not 100% stock system hence a quick odin flash will take care of that!
scrosler said:
This
|
|
\/
Agreed. This OTA tested perfect against your Odin stock so if there is an issue when someone tries to flash then they are not 100% stock system hence a quick odin flash will take care of that!
Click to expand...
Click to collapse
Ok.. I'll do that and try it out again... thanks for the help hyde and scott
EDIT: is this ok to do even though I'm already on G3? also do I need to unlock the bootloader and flash cwm again after doing this?
EDIT 2: I have all the drivers installed and adb recognizes my tab.. but everytime I try to flash this file via ODIN it fails.. this is the error message I get:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> system.ext4.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT 3: So I checked my /system/bin folder and I have two debuggerd files...
debuggerd which is 364 Bytes
debuggerd.bin which is 29.95K
Do you guys have both these files?
nexttonomy said:
Ok.. I'll do that and try it out again... thanks for the help hyde and scott
EDIT: is this ok to do even though I'm already on G3? also do I need to unlock the bootloader and flash cwm again after doing this?
EDIT 2: I have all the drivers installed and adb recognizes my tab.. but everytime I try to flash this file via ODIN it fails.. this is the error message I get:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> system.ext4.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Did you verify all antivirus and firewall programs on your computer are disabled?
Im thinking locked bootloader?
Did you flash the "aboot" like in Hydes thread?
I think its step #3 or 4?
Love it! Looking forward to more of your work.
Warren87 said:
Love it! Looking forward to more of your work.
Click to expand...
Click to collapse
Worked for ya?
Im on an unlocked bootloader... the samsung splash screen is less than a second like it says in mrhydes thread... but I flashed it again just to make sure...
I've been flashing this stuff since the OG droid.. I'm not a noob on this... i'm not sure what is going wrong..
I appreciate all the help.. I'll just keep playing with it to see if I can figure it out
nexttonomy said:
Im on an unlocked bootloader... the samsung splash screen is less than a second like it says in mrhydes thread... but I flashed it again just to make sure...
I've been flashing this stuff since the OG droid.. I'm not a noob on this... i'm not sure what is going wrong..
I appreciate all the help.. I'll just keep playing with it to see if I can figure it out
Click to expand...
Click to collapse
Hmmm. Odd.
The only time I got that messaage was when the bootloader is locked. I dont know then.
Let us know if you figure it out...
Also can you confirm the status of the current build you are on? And did you try a newer version of Odin? Maybe its just an Odin issue. What ver are you on?
scrosler said:
Hmmm. Odd.
The only time I got that messaage was when the bootloader is locked. I dont know then.
Let us know if you figure it out...
Also can you confirm the status of the current build you are on? And did you try a newer version of Odin? Maybe its just an Odin issue. What ver are you on?
Click to expand...
Click to collapse
Odin 3.04 is the version I use and have listed in the instructions. Think it could have something to do with your extra compressed version?
Try downloading the first link again and make sure your using the PDA section. You could even try running Odin "Run as administrator". Also can try rebooting your computer (had a similar issue a while back and a reboot of both my laptop and tablet solved it. Shut down your tablet completely then boot directly into Download (power + vol down). Plug it in AFTER it boots into Download and let us know.
MrHyde03 said:
Odin 3.04 is the version I use and have listed in the instructions. Think it could have something to do with your extra compressed version?
Try downloading the first link again and make sure your using the PDA section. You could even try running Odin "Run as administrator". Also can try rebooting your computer (had a similar issue a while back and a reboot of both my laptop and tablet solved it. Shut down your tablet completely then boot directly into Download (power + vol down). Plug it in AFTER it boots into Download and let us know.
Click to expand...
Click to collapse
No, its the not the file...
<OSM> Checking MD5 finished Sucessfully..
If it was that would have failed.
I am more than sure this is due to some sort of write protection.
Should I still be receiving the OTA install warnings after flashing this? I'm going to freeze SDM for now.
JelloB said:
Should I still be receiving the OTA install warnings after flashing this? I'm going to freeze SDM for now.
Click to expand...
Click to collapse
No, but what you need to do is tell it to check again and it will come back and say that it is already installed and there is no update.
scrosler said:
No, but what you need to do is tell it to check again and it will come back and say that it is already installed and there is no update.
Click to expand...
Click to collapse
I originally postponed it for an hour and then froze SDM. When I unfreeze and go into software update it only gives me the option to install deferred update now.
I'm not terribly concerned about this because I can just leave it frozen but it's curious that I'm receiving the update. All of my software matches those listed on your screenshot above.
JelloB said:
I originally postponed it for an hour and then froze SDM. When I unfreeze and go into software update it only gives me the option to install deferred update now.
I'm not terribly concerned about this because I can just leave it frozen but it's curious that I'm receiving the update. All of my software matches those listed on your screenshot above.
Click to expand...
Click to collapse
You have to ignore it then Select "Check Now"
That's what I had to do... Either that or do a factory reset. I know that will fix it for sure :angel:
And if you did let it go it would just fail immediately so no worries.
Ok cool. I'll check it after the original hour deferment expires and if I have to I'll factory reset.
Thanks for your work on this. Looking forward to future installments.

[Q] Problem with format data

I installed tablet metrics with xposed installer. Then I used my phone normally for a few days and it started...
The phone started to reboot without reason. It just went crazy. I couldn't use it. Every time it turned on, 15 secs later started to reboot again. So I tried to uninstall xposed installer but didn't work. After doing that, my phone didn't boot anymore. It stayed in the "samsung" part. Then I went to recovery mode and did all the wipes possible, wipe cache, wipe factory reset, etc. Did everything but one, format data. And didn't boot. And as a last hope I did format data.
I shouldn't have done that.
Now I don't know what to do. Need some help, please.
I have installed the TWRP recovery. When I try to reboot it says "no OS installed". There is no way to install from TWRP a new OS ?
If you don't understand me or want me to add some more information just put it in the comments.
I don't speak english very well as you might know. Sorry.
Lele123 said:
I installed tablet metrics with xposed installer. Then I used my phone normally for a few days and it started...
The phone started to reboot without reason. It just went crazy. I couldn't use it. Every time it turned on, 15 secs later started to reboot again. So I tried to uninstall xposed installer but didn't work. After doing that, my phone didn't boot anymore. It stayed in the "samsung" part. Then I went to recovery mode and did all the wipes possible, wipe cache, wipe factory reset, etc. Did everything but one, format data. And didn't boot. And as a last hope I did format data.
I shouldn't have done that.
Now I don't know what to do. Need some help, please.
If you don't understand me or want me to add some more information just put it in the comments.
I don't speak english very well as you might know. Sorry.
Click to expand...
Click to collapse
You are on stock JB? Flash stock firmware with Odin. Do not flash I9070 firmware on I9070P phone, do not flash I9070P firmware on I9070 phone - IT WILL HARDBRICK phone - no more going back.
Odin how to: http://forum.xda-developers.com/showthread.php?t=1985398
Firmwares: samsung-updates.com sammobile.com
Do factory reset after.
shut_down said:
You are on stock JB? Flash stock firmware with Odin. Do not flash I9070 firmware on I9070P phone, do not flash I9070P firmware on I9070 phone - IT WILL HARDBRICK phone - no more going back.
Odin how to: http://forum.xda-developers.com/showthread.php?t=1985398
Firmwares: samsung-updates.com sammobile.com
Do factory reset after.
Click to expand...
Click to collapse
It doesn't work...
The Odin get's stuck in this part:
<ID:0/020> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_I9070XXLPZ_I9070SERLPZ_660490_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/020> Odin v.3 engine (ID:20)..
<ID:0/020> File analysis..
<ID:0/020> SetupConnection..
Thanks for your comment
Lele123 said:
It doesn't work...
The Odin get's stuck in this part:
<ID:0/020> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_I9070XXLPZ_I9070SERLPZ_660490_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/020> Odin v.3 engine (ID:20)..
<ID:0/020> File analysis..
<ID:0/020> SetupConnection..
Thanks for your comment
Click to expand...
Click to collapse
Does the size of downloaded firmware match the size written on the page when you start download? I think XXLPZ is one of the oldest FW, try LQL for example.
shut_down said:
Does the size of downloaded firmware match the size written on the page when you start download? I think XXLPZ is one of the oldest FW, try LQL for example.
Click to expand...
Click to collapse
I've tried with XXLQUE and XXLPZ, gives me the same error. I will try with LQL when the download completes
Lele123 said:
I've tried with XXLQUE and XXLPZ, gives me the same error. I will try with LQL when the download completes
Click to expand...
Click to collapse
Try other version of Odin too. 3.0.7 for example.
shut_down said:
Try other version of Odin too. 3.0.7 for example.
Click to expand...
Click to collapse
I did it with LQL, didn't work...
Lele123 said:
I did it with LQL, didn't work...
Click to expand...
Click to collapse
Maybe your phone have some hardware issue, you told that it was rebooting every 15 seconds. Better go to some service centre.

[Q] PingPong Root -> TWRP -> Brick! :( Help!

TL;DR DON'T try to install a custom recovery yet. As of 5/12/15, the bootloader prevents you from doing that. At the moment, you can only root, which you can do through Ping Pong Root (google it). And if for some reason you goofed up and installed a custom recovery, go to AT&T and just say the bare minimum, that you "tried to update your phone" and it keeps telling you "this error message." If they prod more, you can say you "updated the firmware," but obviously withhold the words "flash," "recovery," etc.
So I greatly REGRET that I installed a custom recovery. I'd appreciate any help. I'm bricked in the "System software not authorized by AT&T has been found on your phone." Here's what I did leading up to it:
1. Installed Ping Pong Root party_beta5.7z. Unzipped, installed, rooted.
2. Root Checker verified root!
3. Determined my my phone is: G920AUCU1AOCE.
4. Downloaded TWRP 2.8.6.2 through Flashify for Samsung Galaxy S6 (zeroflte).
5. Flashed it through Flashify
6. Bricked (light blue screen with text) and bootloop.
Help!
EDIT: Steps I've taken so far:
1. Download Odin Tar files from http://forum.xda-developers.com/att-...g920a-t3103835
2. Connected phone to PC in download mode after installing USB drivers and ODIN 3.10.6
3. Put all 4 tar files into their corresponding spots.
EDIT2: No luck. Tried multiple ports, multiple computers, and used the official cable. Also Ran as administrator. After making sure my device is recognized as COM3 (blue box), and the tar files are plugged in, I keep getting the below error:
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT3: Played dumb, took it to at&t store with a tech support center, and they re-flashed a clean install for me. Whew.
I don't think u can use custom recoveries yet buddy..
Yeah, I goofed bigtime. I'm really regretting it.
It's telling me this:
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Let it be known root does not equel unlocked bootloader. I'd of wait or am for something like safestra to make it's way over.
aznkenshin said:
I'd appreciate any help. I'm bricked in the "System software not authorized by AT&T has been found on your phone." Here's what I did leading up to it:
1. Installed Ping Pong Root party_beta5.7z. Unzipped, installed, rooted.
2. Root Checker verified root!
3. Determined my my phone is: G920AUCU1AOCE.
4. Downloaded TWRP 2.8.6.2 through Flashify for Samsung Galaxy S6 (zeroflte).
5. Flashed it through Flashify
6. Bricked (light blue screen with text) and bootloop.
Help!
EDIT: Steps I've taken so far:
1. Download Odin Tar files from http://forum.xda-developers.com/att-...g920a-t3103835
2. Connected phone to PC in download mode after installing USB drivers and ODIN 3.10.6
3. Put Firmware into AP.
Praying this will work...
EDIT2: No luck. It tells me "Can't open the serial(COM) port." I'm thinking it's the drivers fault? Looking into it...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2711451
download odin 3.10.6 and just use all the tar files....MINE IS FINALLY ALIVE
plaxy+ said:
Let it be known root does not equel unlocked bootloader. I'd of wait or am for something like safestra to make it's way over.
Click to expand...
Click to collapse
So in the meantime, what should I do to at least have an operable phone? (
skylinegtr116 said:
http://forum.xda-developers.com/showthread.php?t=2711451
download odin 3.10.6 and just use all the tar files....MINE IS FINALLY ALIVE
Click to expand...
Click to collapse
OH! I was only using the "AP_****" files. I should plug in the CSC, CP, and BL too???????
aznkenshin said:
oh! I was only using the "ap_****" files. I should plug in the csc, cp, and bl too???????
Click to expand...
Click to collapse
yes all the files
skylinegtr116 said:
yes all the files
Click to expand...
Click to collapse
No luck
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_G920AUCU1AOCE_CL4351102_QB4488924_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_G920AUCU1AOCE_CL4351102_QB4488924_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_G920AUCU1AOCE_CL4351102_QB4488924_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_G920AATT1AOCE_CL4351102_QB4488924_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The link above is broken, where can I get these files?
PS: Why do they provide a custom recovery if it straight "bricks" your phone? How is that even considered a working release and why don't they (TWRP) post a damn warning about it?
plaxy+ said:
Let it be known root does not equel unlocked bootloader.
Click to expand...
Click to collapse
Just joined last month, this was their third post currently, and knew this :good:
OP joined late 2011 and thought that just by gaining root, we could install custom recoveries on a still locked bootloader...........
LEARN FROM THIS, people! Don't want to go through this? Follow instructions!
That being said, from what I know of soft bricks, you are doing the right steps to fix it, I just don't have any experience with them to be able to tell you what you're doing wrong. People who have unlocked bootloader phones and installed custom recoveries, tripping KNOX, were able to flash back to stock and get KNOX back to 0x0, but again, they have the unlocked bootloader to be able to do that.... don't know what else to tell you other than to bring it to an ATT service center, play dumb, and see if they'll swap you into a new one
hayateyoshida said:
The link above is broken, where can I get these files?
PS: Why do they provide a custom recovery if it straight "bricks" your phone? How is that even considered a working release and why don't they (TWRP) post a damn warning about it?
Click to expand...
Click to collapse
They do post a warning about it - they post what phones this IS for, and our phone is NOT listed! People, please learn how to read if you're going to screw around with your phones! You can't just say "I have an S6 Edge" and think they're all the same! TWRP clearly states the following two devices have recoveries available:
Samsung Galaxy S6 (zeroflte)
Samsung Galaxy S6 (Sprint) (zerofltespr)
Do you see zeroflteatt on that list? Do you think zeroflte = zeroflteatt? If you don't know what model phone you have and flash away, you're gonna have a bad day......
aznkenshin said:
So I greatly REGRET that I installed a custom recovery. I'd appreciate any help. I'm bricked in the "System software not authorized by AT&T has been found on your phone." Here's what I did leading up to it:
1. Installed Ping Pong Root party_beta5.7z. Unzipped, installed, rooted.
2. Root Checker verified root!
)
Click to expand...
Click to collapse
what??
ATT galaxy s6 has root ?
Have you tried recovery through smart switch
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
netnerd said:
what??
ATT galaxy s6 has root ?
Click to expand...
Click to collapse
yep. pingpong root
LeKtRiCzzz said:
Have you tried recovery through smart switch
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Click to expand...
Click to collapse
Yes, after going to update and software emergency setup, I plugged in Model and Serial number on the sticker of my phone, and it auto-closes.
Sent from my GT-I9505G using XDA Free mobile app
Agree 500%
KryptosXLayer2 said:
Just joined last month, this was their third post currently, and knew this :good:
OP joined late 2011 and thought that just by gaining root, we could install custom recoveries on a still locked bootloader...........
LEARN FROM THIS, people! Don't want to go through this? Follow instructions!
That being said, from what I know of soft bricks, you are doing the right steps to fix it, I just don't have any experience with them to be able to tell you what you're doing wrong. People who have unlocked bootloader phones and installed custom recoveries, tripping KNOX, were able to flash back to stock and get KNOX back to 0x0, but again, they have the unlocked bootloader to be able to do that.... don't know what else to tell you other than to bring it to an ATT service center, play dumb, and see if they'll swap you into a new one
They do post a warning about it - they post what phones this IS for, and our phone is NOT listed! People, please learn how to read if you're going to screw around with your phones! You can't just say "I have an S6 Edge" and think they're all the same! TWRP clearly states the following two devices have recoveries available:
Samsung Galaxy S6 (zeroflte)
Samsung Galaxy S6 (Sprint) (zerofltespr)
Do you see zeroflteatt on that list? Do you think zeroflte = zeroflteatt? If you don't know what model phone you have and flash away, you're gonna have a bad day......
Click to expand...
Click to collapse
---------- Post added at 11:25 AM ---------- Previous post was at 11:24 AM ----------
Smart Switch does NOT work in the AT&T version of the S6.
LeKtRiCzzz said:
Have you tried recovery through smart switch
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Click to expand...
Click to collapse
aznkenshin said:
EDIT3: Played dumb, took it to at&t store with a tech support center, and they re-flashed a clean install for me. Whew.
Click to expand...
Click to collapse
Great, I have just booked an appointment. But buddy, is it possible for you to upload Odin Tar?
Thanks!
nagnrik said:
Great, I have just booked an appointment. But buddy, is it possible for you to upload Odin Tar?
Thanks!
Click to expand...
Click to collapse
Read my OP
aznkenshin said:
Read my OP
Click to expand...
Click to collapse
ATT re-flashed the firmware, it is fine now. Thanks!

Categories

Resources