Database Users

So I think I (soft bricked) my phone

I just bought a T-Mobile variant of the SGS3. I then successfully rooted it with the Toolkit from here:
http://forum.xda-developers.com/showthread.php?t=1746682
Then, when I used to toolkit to remove the boot animations. This is when trouble starts. Now the phone flashes the Samsung Logo when I try and turn it on, but nothing else happens. I can get into download mode still.
What should I do next? I tried re flashing through Odin the insecure boot, but that hasn't work. I'm in the proscess of downloading the stock firmware tarball (from here: http://forum.xda-developers.com/showthread.php?t=1737855 ) but its PAINSTAKINGLY slow. Do you expect flashing back to stock via Odin to unbrick me?
I'm used to flashing roms and whatnot but I'm not a dev... this caught me totally off guard since I thought I was using the S3 toolkit properly (and yes, it is the correct toolkit. I rooted successfully).
I made a nandroid right off the bat, but I can't boot into recovery and I don't think I can access the files any other way.
Thanks for any help. I'm in a panic right now

andham95 said:
I just bought a T-Mobile variant of the SGS3. I then successfully rooted it with the Toolkit from here:
http://forum.xda-developers.com/showthread.php?t=1746682
Then, when I used to toolkit to remove the boot animations. This is when trouble starts. Now the phone flashes the Samsung Logo when I try and turn it on, but nothing else happens. I can get into download mode still.
What should I do next? I tried re flashing through Odin the insecure boot, but that hasn't work. I'm in the proscess of downloading the stock firmware tarball (from here: http://forum.xda-developers.com/showthread.php?t=1737855 ) but its PAINSTAKINGLY slow. Do you expect flashing back to stock via Odin to unbrick me?
I'm used to flashing roms and whatnot but I'm not a dev... this caught me totally off guard since I thought I was using the S3 toolkit properly (and yes, it is the correct toolkit. I rooted successfully).
I made a nandroid right off the bat, but I can't boot into recovery and I don't think I can access the files any other way.
Thanks for any help. I'm in a panic right now
Click to expand...
Click to collapse
Btw, I have the original build.prop backed up

Try this. http://forum.xda-developers.com/showthread.php?t=1762204
Should get you back to stock rooted. Grab file, put on desktop, extract here, fire Odin up, click pda an find the .tar file and hit start. Should get you back to stock rooted.
EDIT: OPPS! I just noticed this is for tmobile.. anyhow just grab a stock rooted .img/.tar file and run it in Odin. should get you back to stock rooted.

eastwood1 said:
Try this. http://forum.xda-developers.com/showthread.php?t=1762204
Should get you back to stock rooted. Grab file, put on desktop, extract here, fire Odin up, click pda an find the .tar file and hit start. Should get you back to stock rooted.
EDIT: OPPS! I just noticed this is for tmobile.. anyhow just grab a stock rooted .img/.tar file and run it in Odin. should get you back to stock rooted.
Click to expand...
Click to collapse
Thanks for the reply, but I already got it working! I got it back in to recovery after I flashed the insecure boot image via Odin again (the one that came with the S3 toolkit) and restored my nandroid.
And (to all) sorry for the newb post, I was in total panic mode, heart pounding, adrenalin rushing, it was intense haha. Its hard to think straight like that.

[Q] HELP !!! MF3 Root Fail Bricked

I just followed this thread and successfully rooted my S4
http://forum.xda-developers.com/showthread.php?t=2387577
I think i deleted some core apps thru titanium backup and the phone could not display normally (keep Blinking)
then I tried to downloaded Goo Manager and installed TWRP Recovery on my S4. when I restart my phone can only boot to ODIN mode. I fixed this by using
http://forum.xda-developers.com/showthread.php?t=2360859
Now the phone can boot up but stuck at ATT logo Screen. Any body can help me?
PS. I try KIES emergency recovery and it keep telling me there is a error of updating.

I bricked my s4 (i337 Canadian, bell) the day I bought it, TWRP 2.6.0.0 was what bricked my phone (I think, or improper use of TWRP) and it wouldn't boot whatsoever (even my recovery was bricked), I managed to fix it by flashing stock firmware from ODIN 1.85 on PC to the phone (couldn't access recovery, so I flashed from PC) , make sure you download a stock firmware that is .tar to use with the PC version of ODIN, the second thing I had to do was flash CF Auto Root again using ODIN 1.85 from PC to phone, since I still couldn't boot my phone or recovery (other root flashing methods wouldn't unbrick my phone, but CF Auto Root did, download the MF3 version of CF auto root).
after all this crap I installed TWRP 2.5.0.0 as my recovery and haven't had any issues since :victory:
this was done on a I337MVLUAMG1 which I believe is the bell equivalent of the MF3 (update that blocked rooting by most methods like motochopper ect)

Thanks
Amb669 said:
I bricked my s4 (i337 Canadian, bell) the day I bought it, TWRP 2.6.0.0 was what bricked my phone (I think, or improper use of TWRP) and it wouldn't boot whatsoever (even my recovery was bricked), I managed to fix it by flashing stock firmware from ODIN 1.85 on PC to the phone (couldn't access recovery, so I flashed from PC) , make sure you download a stock firmware that is .tar to use with the PC version of ODIN, the second thing I had to do was flash CF Auto Root again (other root flashing methods wouldn't unbrick my phone, but CF Auto Root did, download the MF3 version of CF auto root).
after all this crap I installed TWRP 2.5.0.0 as my recovery and haven't had any issues since :victory:
this was done on a I337MVLUAMG1 which I believe is the bell equivalent of the MF3 (update that blocked rooting by most methods like motochopper ect)
Click to expand...
Click to collapse
Thanks for your reply.
I have the same problem as this guy
http://forum.xda-developers.com/showthread.php?t=2407950
Any Idea how to fix it?

jerryhuanginusa said:
I just followed this thread and successfully rooted my S4
http://forum.xda-developers.com/showthread.php?t=2387577
I think i deleted some core apps thru titanium backup and the phone could not display normally (keep Blinking)
then I tried to downloaded Goo Manager and installed TWRP Recovery on my S4. when I restart my phone can only boot to ODIN mode. I fixed this by using
http://forum.xda-developers.com/showthread.php?t=2360859
Now the phone can boot up but stuck at ATT logo Screen. Any body can help me?
PS. I try KIES emergency recovery and it keep telling me there is a error of updating.
Click to expand...
Click to collapse
Dont thinknthere is antthing you can do. We have no return to stock method at this point in time. This is why it is important to follow forum rules and read and search before doing something youll regret, im nkt saying this to be mean...but there has been at least 5 people these past few days who have done the exact same thing as you and have gone in here looking for help...
My best advice, throw in some money for the bootloader unlock bounty and hope somethung happens soomer than later
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

jerryhuanginusa said:
I just followed this thread and successfully rooted my S4
http://forum.xda-developers.com/showthread.php?t=2387577
I think i deleted some core apps thru titanium backup and the phone could not display normally (keep Blinking)
then I tried to downloaded Goo Manager and installed TWRP Recovery on my S4. when I restart my phone can only boot to ODIN mode. I fixed this by using
http://forum.xda-developers.com/showthread.php?t=2360859
Now the phone can boot up but stuck at ATT logo Screen. Any body can help me?
PS. I try KIES emergency recovery and it keep telling me there is a error of updating.
Click to expand...
Click to collapse
If you read through the threads it specifically stated that the MF3 boot loader is locked and you cannot install twrp or custom ROMS on it. I have seen so many posts regarding this it makes me sick. It's kies seeing the device? But is falling to recover? Or is it not seeing it?
Tylor
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

http://forum.xda-developers.com/showpost.php?p=44570305&postcount=366

Fail to recover
Tylorw1 said:
If you read through the threads it specifically stated that the MF3 boot loader is locked and you cannot install twrp or custom ROMS on it. I have seen so many posts regarding this it makes me sick. It's kies seeing the device? But is falling to recover? Or is it not seeing it?
Tylor
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
the Kies can detect the phone buy it fail to recover it. the progress bar runs a little and stopped. error message pop out on PC screen says "Emergency recovery failed, Please contact Samsung Customer Service"

Can't get into recovery...

Had a Goldeneye ROM installed, wanted to try something different. I'm on MLD baseband. Managed to load a Nexus ROM, but couldn't get wifi to work. Tried Goldfinger ROM, same result. Somewhere along the way, I lost the ability to get into TWRP recovery. I can get to the fallen android recovery menu, but whenever I try to reboot it goes to directly to the ROM (prior to this, if I tried to reboot to TWRP, it would first go to the fallen android, but then selecting reboot got me to TWRP). I have a nandroid backup, but don't know how to try it out without first going to recovery? Alternatively, I could try this method, but don't have a windows box and can't figure out which files I need to flash using heimdall. Thanks for the help...

Do not flash the link on your device. You can get the stock mdl firmware at sammobile.com. Flashing what you linked to will put the mk2 firmware on your device and you'll no longer be able to use twrp. Sorry I can't help you on heimdall though, I've never used it.
Sent from my Nexus 5 using XDA Free mobile app

Have you tried reflashing twrp? I would install flashify from playstore and go from there.

Airtioteclint said:
Have you tried reflashing twrp? I would install flashify from playstore and go from there.
Click to expand...
Click to collapse
OK, well, I managed to get back into recovery. Installed towelroot, then just reinstalled the safestrap recovery apk. Was able to restore my backup, and all was well. Tried reinstalling goldfinger, and wifi was gone again, as was my recovery (again). Weird.

nola mike said:
OK, well, I managed to get back into recovery. Installed towelroot, then just reinstalled the safestrap recovery apk. Was able to restore my backup, and all was well. Tried reinstalling goldfinger, and wifi was gone again, as was my recovery (again). Weird.
Click to expand...
Click to collapse
Meh, forgot to RTFM when installing the ROM. Needed to flash the ATT modules. In my defense, that info was buried pretty deep in the FM

nola mike said:
Meh, forgot to RTFM when installing the ROM. Needed to flash the ATT modules. In my defense, that info was buried pretty deep in the FM
Click to expand...
Click to collapse
Sigh. I just need to quit while I'm ahead. After messing with some xposed modules, I eventually became unable to boot into recovery again, and am stuck at the bootloader screen. I think I need to reinstall firmware via odin (but I have no windows PC, so I'm going to try heimdall).
Is this method the correct one?
I have this file as my firmware: I337UCUAMDL_I337ATTAMDL_ATT.zip

nola mike said:
Sigh. I just need to quit while I'm ahead. After messing with some xposed modules, I eventually became unable to boot into recovery again, and am stuck at the bootloader screen. I think I need to reinstall firmware via odin (but I have no windows PC, so I'm going to try heimdall).
Is this method the correct one?
I have this file as my firmware: I337UCUAMDL_I337ATTAMDL_ATT.zip
Click to expand...
Click to collapse
...And, we're back in business! Multiple problems, one of which was the wrong firmware version--the above is MDL, not MLD
I flashed back to stock MK2 firmware, then upgraded using towelroot and safestrap.
Had a bunch of problems trying to figure out Heimdall, and couldn't figure out what was going wrong (turned out to be the USB cable--I saw posts about this, and went through FIVE cables before I could find one that worked. It was a kindle cable, FWIW).
Tried ODIN in the meantime using my wife's old XP box. What a PITA. Had all kinds of issues trying to get kies to install. Anyway, I'll write up exactly what worked for me. A lot of the info I used was fragmented, old, and contradictory.
EDIT: Re-borked, and tried upgrading again, and ended up with the same errors using the new cable. Then used a different computer, and didn't have any trouble with multiple flashes. I think my USB controller is touchy on the original computer...

Bricked note 4 with CF- Auto-Root, can i revive it?

Ok here's what i did wrong. Tried rooting my SM-N910H with CF-Auto-Root, using the wrong d/l ( CF-Auto-Root-tre3g-tre3gxx-smn910h )
My phone was 6.0.1 and i foolishly flashed this file onto it using Odin ( correct me if i'm wrong but it is an earlier version yes? )
So the upshot is my phone will no longer boot up or boot into recovery as i have the "recovery is not seandroid enforcing" error.
Have looked all over the net to find the solution, but no joy. Have tried d/ling latest stock firmware for my phone and flashing with Odin, but it fails everytime.
I think my biggest prob is trying to find THE RIGHT firmware to fix this. Am i on the right track to try and fix this? Any help would be much appreciated.

Blu3sman said:
Ok here's what i did wrong. Tried rooting my SM-N910H with CF-Auto-Root, using the wrong d/l ( CF-Auto-Root-tre3g-tre3gxx-smn910h )
My phone was 6.0.1 and i foolishly flashed this file onto it using Odin ( correct me if i'm wrong but it is an earlier version yes? )
So the upshot is my phone will no longer boot up or boot into recovery as i have the "recovery is not seandroid enforcing" error.
Have looked all over the net to find the solution, but no joy. Have tried d/ling latest stock firmware for my phone and flashing with Odin, but it fails everytime.
I think my biggest prob is trying to find THE RIGHT firmware to fix this. Am i on the right track to try and fix this? Any help would be much appreciated.
Click to expand...
Click to collapse
Instead of flashing any firmware , try to flash the correct cf auto root file.
Reporting Via N910G

Blu3sman said:
Ok here's what i did wrong. Tried rooting my SM-N910H with CF-Auto-Root, using the wrong d/l ( CF-Auto-Root-tre3g-tre3gxx-smn910h )
My phone was 6.0.1 and i foolishly flashed this file onto it using Odin ( correct me if i'm wrong but it is an earlier version yes? )
So the upshot is my phone will no longer boot up or boot into recovery as i have the "recovery is not seandroid enforcing" error.
Have looked all over the net to find the solution, but no joy. Have tried d/ling latest stock firmware for my phone and flashing with Odin, but it fails everytime.
I think my biggest prob is trying to find THE RIGHT firmware to fix this. Am i on the right track to try and fix this? Any help would be much appreciated.
Click to expand...
Click to collapse
Download firmware from sammobiles. com
http://www.sammobile.com/firmwares/database/SM-N910H/

yashthemw said:
Instead of flashing any firmware , try to flash the correct cf auto root file.
Reporting Via N910G
Click to expand...
Click to collapse
Ok well i tried that and that didn't work. However after double checking its seems that i had the correct file in the first place. So what went wrong?
One thing i need to ask. Does your phone NEED to be unlocked in order to root it?
Trex i went to Sammobiles and what my problem is there is WHICH country firmware to i d/l??? there are so many!!! Should any one of them do the trick?

Blu3sman said:
Ok well i tried that and that didn't work. However after double checking its seems that i had the correct file in the first place. So what went wrong?
One thing i need to ask. Does your phone NEED to be unlocked in order to root it?
Trex i went to Sammobiles and what my problem is there is WHICH country firmware to i d/l??? there are so many!!! Should any one of them do the trick?
Click to expand...
Click to collapse
try flashing a custom recovery specific for your phone model and from within flash superSU.

its_me_Sandy said:
try flashing a custom recovery specific for your phone model and from within flash superSU.
Click to expand...
Click to collapse
Ok Sandy thats worked, however i'm stuck on how to install SuperSU. Obviously i want the right ver but my phone will still not bootup,
so how do i get the right ver SuperSU onto my phone? Do i use ADB?

Blu3sman said:
Ok Sandy thats worked, however i'm stuck on how to install SuperSU. Obviously i want the right ver but my phone will still not bootup,
so how do i get the right ver SuperSU onto my phone? Do i use ADB?
Click to expand...
Click to collapse
This is the current supersu 2.78-sr1. It's systemless root for all samsung marshmallow firmware.
http://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
1 Download to phone.
2 Boot into recovery.
3 Click install, and find zip that you downloaded.
4. Reboot, All done
Phone will boot loop once. That is normal.
P.S. If this is first time you installed Twrp, I would make a full backup and save it some where.
:good: if that helped.

aaron74 said:
This is the current supersu 2.78-sr1. It's systemless root for all samsung marshmallow firmware.
http://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
1 Download to phone.
2 Boot into recovery.
3 Click install, and find zip that you downloaded.
4. Reboot, All done
Phone will boot loop once. That is normal.
P.S. If this is first time you installed Twrp, I would make a full backup and save it some where.
:good: if that helped.
Click to expand...
Click to collapse
Well Aaron thats my problem, i can't download it to my phone. The one constant through all this is that i can't turn my phone on as such.
My pc doesn't even recognize it, in fact the only thing that does is Odin, not Kies, not ADB, nothing lol.
I can get the phone into the custom recovery i have flashed (TWRP) and get into "download" mode, but thats it. So where do we go from here?
Ok i have an update on this. PC now sees the phone but only as a modem.

Blu3sman said:
Well Aaron thats my problem, i can't download it to my phone. The one constant through all this is that i can't turn my phone on as such.
My pc doesn't even recognize it, in fact the only thing that does is Odin, not Kies, not ADB, nothing lol.
I can get the phone into the custom recovery i have flashed (TWRP) and get into "download" mode, but thats it. So where do we go from here?
Ok i have an update on this. PC now sees the phone but only as a modem.
Click to expand...
Click to collapse
Oh, I misunderstood.
If that's the case. If you can goto download mode, download stock firmware, then flash with Odin.
To get your csc, since you can go in twrp. Use twrp file explorer. copy the file in /efs/imei folder. Thinks it's called mps_code. Copy to ext sd. Now that file should have your csc region code written in it. Read file in pc. That should be firmware you want to download.
See if that helps.

Blu3sman said:
Ok Sandy thats worked, however i'm stuck on how to install SuperSU. Obviously i want the right ver but my phone will still not bootup,
so how do i get the right ver SuperSU onto my phone? Do i use ADB?
Click to expand...
Click to collapse
Find the correct version of superSU from the above post..put it in a pen drive or in the memory card via card reader.
Flash it via OTG cable or put back the card n flash

ALRIGHT!!!! Ok guys just a heads up. As you can probably guess my phone is WORKING!!!....so far. Was able to do as you suggested and found the txt file, Using TWRP file browser ,that told me what ver firmware i have, inserted an sd card i had in my Tab S, copied file to that, read in my pc card reader, downloaded and installed said firmware and BADA BING BADA BOOM, all good!! I still am unsure on how this happened. I've rooted 3 HTC phones and my Galalxy Tab S successfully, so it's not like i didn't know what i was doing, 1 question that hasn't been answered though is, must the phone be network unlocked in order to root it? Because thats the one thing i didn't do that i did on the others. Want to thank all you guys for all your help. This was doing my head in and without your direction i probably would not have been able to do this.
Many Thanks.
PS: any one suggest a good rooting method for this phone??? lol

hi. i have the exact problem. can you please help,, i dont have twrp or supersu. [email protected] please if anyone can help

Might have Bricked S7 Edge SM-935FD. Need Help to recover

Hello guys
My phone is Galaxy S7 Edge Duos- SM935FD. I seem to have bricked the device.
Below are the actions I have performed.
1. Flashed TWRP using ODIN as described on https://www.the***********.com/root-samsung-galaxy-s7-edge/
2. Booted successfully into the OS. Found superuser app installed.
3. When I went to back to Flash ROM i erased multiple things such as internal storage/dalvik/cache/system after which device got stuck in bootloop. Showing NO OS.
4. I tried flasing Custom ROM Zip files through OTG. The process failed showing package corrupt and still stuck in bootloop.
I can enter recovery/download mode however cant seem to get the device booted. How can I get the device to work either Custom or stock ROM.
I will be going through some threads in the meantime, your guidance is very much appreciated.

Flash stock rom with Odin: This shouldnt be posted on Development Forum but rayher questions and Answers.
Find what your Stock Firmware for your phone is using Sammobile and flash stock then re do rooting and TWRP Process

zzThrain is right -- I wouldn't risk flashing custom ROMs at this stage, especially because many contain new bootloaders or other stuff that might make this even worse for you. Just pick up the relevant Samsung stock ROM file (from, for example, SamMobile) and see if it boots normally again. Once it does, re-do the process *after checking all MD5s of the files you used* -- I, too, have had it happen before that a download went corrupted and I flashed it. If all is well, get into Download Mode and let Odin rip.

rixon.d9 said:
Hello guys
My phone is Galaxy S7 Edge Duos- SM935FD. I seem to have bricked the device.
Below are the actions I have performed.
1. Flashed TWRP using ODIN as described on https://www.the***********.com/root-samsung-galaxy-s7-edge/
2. Booted successfully into the OS. Found superuser app installed.
3. When I went to back to Flash ROM i erased multiple things such as internal storage/dalvik/cache/system after which device got stuck in bootloop. Showing NO OS.
4. I tried flasing Custom ROM Zip files through OTG. The process failed showing package corrupt and still stuck in bootloop.
I can enter recovery/download mode however cant seem to get the device booted. How can I get the device to work either Custom or stock ROM.
I will be going through some threads in the meantime, your guidance is very much appreciated.
Click to expand...
Click to collapse
Go to recovery mode & transfer rom to phone using pc. wipe cache, delvikcache, data only. No need to wipe internal sd. Install rom & reboot.
if you phone goes to recovery or download mode, no need to worry. If it doesn't go to neither recovery nor download mode, them your phone might have probably bricked.

It's my pleasure to help you if you still facing this problem

zzThrain said:
Flash stock rom with Odin: This shouldnt be posted on Development Forum but rayher questions and Answers.
Find what your Stock Firmware for your phone is using Sammobile and flash stock then re do rooting and TWRP Process
Click to expand...
Click to collapse
Hi
I tried flashing stock rom from sammobile. I could find for SM-935FD hence downloaded SM-935F.
It got stuck at 90% showing System in ODIN.
From the ZIP file which is the file that needs to be flashed among below ? I tried AP.
AP_G935FXXU2DRB6_CL12365438_QB16944063_REV00_user_low_ship_meta.tar
BL_G935FXXU2DRB6_CL12365438_QB16944063_REV00_user_low_ship.tar
CP_G935FXXU2DRAG_CL648265_QB8691891_SIGNED.tar
CSC_OJV_G935FOJV2DRAG_CL12785220_QB16560277_REV00_user_low_ship.tar
HOME_CSC_OJV_G935FOJV2DRAG_CL12785220_QB16560277_REV00_user_low_ship.tar
Now when I try again it immediately shows FAIL. Am i Flashing the right stock rom ?

It Worked. Thanks to all who helped.
I wasn't running ODIN as Admin and also was using an slightly older version V3.10.7.