I wanted to update my S3 from whatever version it was on to the newest one available. I essentially wanted to start with a blank phone I went into the TWRP recovery and wiped cache, system, data, etc. I guess that was the entirely wrong way to do it because after that I installed the dirty unicorn rom (DU_d2att_5.1.1_20150723-1444.v9.4-UNOFFICIAL), and it got stuck on the boot screen. Thinking there was something wrong with the install I tried a factory reset and reflashing. It got stuck on "patching system image unconditionally" because there was something wrong with the system partition I think. I let it sit overnight and it stayed on this part.
The next day I read a bunch of things and thought it was just a bad ROM file or something. I went and downloaded the newest stable cyanogenmod (cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-d2att) to try and make it work. It installed without error and looked like it was going to work, i even wiped dalvik cache to up the chances of success. It also hung on the boot screen. I left it alone for a few hours and it still didn't progress.
After some more research I found a post that I thought would correct my partitions and make it bootable again. It was using adb commands to do something:
adb shell
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
I did this from recovery and the first two commands worked. The third shot back an error. I tried modifying it according to other users who have found success and it didn't work for me. I went ahead and hit reboot anyway and now the phone doesn't respond. It doesn't power on, it only has a charging light when plugged in without the battery.
I have tried to fix this as well, I tried a slew of different debrick.img files on a 16gb sd card formatted with Win32 Disk Imager. None of those were able to get me back to download mode. This is where I'm stumped. Is there a debrick.img I'm supposed to use and haven't found yet? Or am I just SOL with this method?
Thanks in advance
Have you tried using different SD cards?
audit13 said:
Have you tried using different SD cards?
Click to expand...
Click to collapse
I've tried two 16gb, an 8gb, and 64gb.
Not sure why the images didn't work. Did you try the recommended SD cards? The phone is an i747 according to the label under the battery?
audit13 said:
Not sure why the images didn't work. Did you try the recommended SD cards? The phone is an i747 according to the label under the battery?
Click to expand...
Click to collapse
Yes, I've tried the recommended SD cards and the phone is i747. I'm thinking maybe I need to find a debrick image from the android versions I was trying to upgrade to?
scyther3989 said:
Yes, I've tried the recommended SD cards and the phone is i747. I'm thinking maybe I need to find a debrick image from the android versions I was trying to upgrade to?
Click to expand...
Click to collapse
I think it would be more successful to use a debrick image made for the bootloader and modem on your phone rather than that matches the Android version of the ROM you were trying to flash.
Both of the ROMs you mentioned were Android 5.1.1, but the highest bootloader you could have is 4.4.2 on the i747. To get more precise, for the i747 there would be three different 4.4.2 bootloaders; NE4, NJ1, or NJ2. I'm fairly certain that I have seen a debrick image for at least one of these. Do you recall what bootloader is on your phone?
dawgdoc said:
I think it would be more successful to use a debrick image made for the bootloader and modem on your phone rather than that matches the Android version of the ROM you were trying to flash.
Both of the ROMs you mentioned were Android 5.1.1, but the highest bootloader you could have is 4.4.2 on the i747. To get more precise, for the i747 there would be three different 4.4.2 bootloaders; NE4, NJ1, or NJ2. I'm fairly certain that I have seen a debrick image for at least one of these. Do you recall what bootloader is on your phone?
Click to expand...
Click to collapse
I don't remember any of the specs on what version it was before I started tinkering with it. But if it's down to those three bootloaders, can't I just find debricks for all three of them and try them out?
Another thing I'm curious of is I think I had a i747m rom installed as they were very similar when I was using the s3 is it possible to have a i747m bootloader on an i747 device?
scyther3989 said:
I don't remember any of the specs on what version it was before I started tinkering with it. But if it's down to those three bootloaders, can't I just find debricks for all three of them and try them out?
Another thing I'm curious of is I think I had a i747m rom installed as they were very similar when I was using the s3 is it possible to have a i747m bootloader on an i747 device?
Click to expand...
Click to collapse
The ROMs should be interchangeable, but I don't think the bootloaders are. I expect using the other bootloaders would brick a working phone.
There would be a lesser chance of problems using the debrick image with the newest bootloader you can find. (Best would be the one that matched your bootloader, but not possible in this case.) One with an older bootloader than you were running probably wouldn't fix your phone.
dawgdoc said:
The ROMs should be interchangeable, but I don't think the bootloaders are. I expect using the other bootloaders would brick a working phone.
There would be a lesser chance of problems using the debrick image with the newest bootloader you can find. (Best would be the one that matched your bootloader, but not possible in this case.) One with an older bootloader than you were running probably wouldn't fix your phone.
Click to expand...
Click to collapse
So my best bet would be to find the newest i747 and i747m debricks around until one works?
scyther3989 said:
So my best bet would be to find the newest i747 and i747m debricks around until one works?
Click to expand...
Click to collapse
I don't know if the i747M images would work on the i747. But the normal method of using a debrick image would have you booting from the external sdcard and then installing the bootloader and modem. Even if you could boot from a i747M debrick image, I think loading the bootloader and modem from one would be bad. I guess you could boot from the i747M debrick image and then be certain that it is an i747 bootloader and modem you install.
So, I would say the newest i747 that you can find. What say you @audit13 ?
Please keep in mind that I have not used a debrick image of any kind, I am only making suppositions from what I have read and recall from the relevant threads. (Although, it looks like I will be using on to resurrect the i535 I bought for hacking and modding. :fingers-crossed: )
---------- Post added at 02:32 AM ---------- Previous post was at 02:07 AM ----------
See if this post helps. He was in your same predicament.
The only life the phone had was remove battery and plug charger in and the red light came on.
Click to expand...
Click to collapse
dawgdoc said:
I don't know if the i747M images would work on the i747. But the normal method of using a debrick image would have you booting from the external sdcard and then installing the bootloader and modem. Even if you could boot from a i747M debrick image, I think loading the bootloader and modem from one would be bad. I guess you could boot from the i747M debrick image and then be certain that it is an i747 bootloader and modem you install.
So, I would say the newest i747 that you can find. What say you @audit13 ?
Please keep in mind that I have not used a debrick image of any kind, I am only making suppositions from what I have read and recall from the relevant threads. (Although, it looks like I will be using on to resurrect the i535 I bought for hacking and modding. :fingers-crossed: )
---------- Post added at 02:32 AM ---------- Previous post was at 02:07 AM ----------
See if this post helps. He was in your same predicament.
Click to expand...
Click to collapse
After a few more hours of trying a bunch of different debrick images, I haven't been able to make it work. I have about 15 debrick images from anyone who said "this one worked for me." I think at this point I'll just look for some of the newer images around to see if that helps. Also, I see some debrick files coming in 256 and 512 variants, what is that about?
Related
I was updating an s3 running cyanogenmod 10.2.1 to 11. I realized that the bootloader needed to be updated long story short i accidentally flashed the i9300 bootloader instead and now my phone is hard bricked. I heard about a method using the sd card to allow the phone to enter boot recovery so i could get into download mode could someone help me to do this?
The only fix that I personally know of is using a jtag service. If there is an sd card fix floating around out there, you'll need to search for it. If you fail, mobiletechvideos.com can help. Expect a week to 10 day turn around time
Sent from my SAMSUNG-SGH-I747 using Tapatalk
purelight97 said:
I was updating an s3 running cyanogenmod 10.2.1 to 11. I realized that the bootloader needed to be updated long story short i accidentally flashed the i9300 bootloader instead and now my phone is hard bricked. I heard about a method using the sd card to allow the phone to enter boot recovery so i could get into download mode could someone help me to do this?
Click to expand...
Click to collapse
You are probably referring to the method posted in the thread below ....
http://forum.xda-developers.com/showthread.php?t=2549068
You have nothing to lose in giving it a try. Doubtful if it will work, however, since it is specifically for recovering from a brick caused by flashing an older bootloader after 4.3 upgrade. As BrianRay advised, when you have a brick caused by flashing a different model's bootloader, a JTag operation may be required.
Larry2999 said:
You are probably referring to the method posted in the thread below ....
http://forum.xda-developers.com/showthread.php?t=2549068
You have nothing to lose in giving it a try. Doubtful if it will work, however, since it is specifically for recovering from a brick caused by flashing an older bootloader after 4.3 upgrade. As BrianRay advised, when you have a brick caused by flashing a different model's bootloader, a JTag operation may be required.
Click to expand...
Click to collapse
Thanks, you wouldn't happen to have a 4.1.2 debrick.img?
purelight97 said:
Thanks, you wouldn't happen to have a 4.1.2 debrick.img?
Click to expand...
Click to collapse
Sadly, no, I don't. You could create one, however, if you know someone who has a similar device running 4.1.2. If you need further instructions on how to do this, you would need to contact the author of the original post. He is the expert there. A JTag may still be your best option, however.
Hey, try to get the phone into a download mode by using at USB jig. You can buy one for 3 bucks from ebay. If that doesnt do it, then you can go to the method of using the debrick image.
Once you exhaust all of these possibilities, then you can try the JTAG. But the Jtag service is expensive too. Good luck.
as many people have hard bricked their i747m on 4.4.2 including me therefore i decided to make a thread to discuss the solution and ask for 4.4.2 debrick file from those who have official 4.4.2 rooted rom
There's already a thread for this. Splitting it up doesn't really do a lot of good imo. Its best for all support and info to be in the one place. Multiple threads for one subject makes it harder to follow, to help others, to find information etc. Plus, when someone needs the info in the future, they may go to one thread, not realizing the answers they seek are in a different one.
DocHoliday77 said:
There's already a thread for this. Splitting it up doesn't really do a lot of good imo. Its best for all support and info to be in the one place. Multiple threads for one subject makes it harder to follow, to help others, to find information etc. Plus, when someone needs the info in the future, they may go to one thread, not realizing the answers they seek are in a different one.
Click to expand...
Click to collapse
well i agree with u dear but got nothing useful from there
Saqib Mushtaq 74 said:
as many people have hard bricked their i747m on 4.4.2 including me therefore i decided to make a thread to discuss the solution and ask for 4.4.2 debrick file from those who have official 4.4.2 rooted rom
Click to expand...
Click to collapse
I have but I was told by technicians here that i need to replace the board, I still think that once there is life in my phone (S3 seen in Device Manager as QHSUSB_DLOAD). I read somewhere that that indicates there is not enough power to initiate some resurrection and a jtag or combination of that and some bootloader flashing needs to be performed. Can you help me?
QHSUSB_DLOAD is just a low level bootloader used by Samsung and Qualcomm to write to all areas of the device. It depends on how you bricked it if you want to know if it can be fixed.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
u should try changing ur emmc
still cant get an i747m 4.4.2 debrick img as yet??????????????? i really need one plz
you can check here....
http://forum.xda-developers.com/showthread.php?t=2598240
err on the side of kindness
mrrocketdog said:
you can check here....
http://forum.xda-developers.com/showthread.php?t=2598240
err on the side of kindness
Click to expand...
Click to collapse
i have tried it an it didnt work........because it is for the i747 and my is the i747m canadian version from rogers 4.4.2
I747m
Hey did you get that debrick image I am looking for the same one.
DocHoliday77 said:
QHSUSB_DLOAD is just a low level bootloader used by Samsung and Qualcomm to write to all areas of the device. It depends on how you bricked it if you want to know if it can be fixed.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
my computer shows the same mesage. In my case i have a telcel 747m. running stock latest 4.3 but wanted kk so i flashed in mobile odin a canadian kk. My phone booted good everything was smooth just because i didnt had root. Amd a unknown baseband. I downloaded nk2 modem to flash in recovery. So when i decided to install in odin twrp it never turn on againg. So if i flash a 4.4.2 i747m forma canadian will it work?? I had to buy a verizon s3 motherboard for the meantime..
Enviado desde mi GT-I9505 mediante Tapatalk
I have a collection of imgs i strongly advise you guys to try. PM me is the links die. It goes to my email, which i check every few hours
Try this one
debrick.img
debrick256
Debrick MK5
Debrick NK2
Debrick MK5 4.3
I747M NE6 512
bighleo114312 said:
my computer shows the same mesage. In my case i have a telcel 747m. running stock latest 4.3 but wanted kk so i flashed in mobile odin a canadian kk. My phone booted good everything was smooth just because i didnt had root. Amd a unknown baseband. I downloaded nk2 modem to flash in recovery. So when i decided to install in odin twrp it never turn on againg. So if i flash a 4.4.2 i747m forma canadian will it work?? I had to buy a verizon s3 motherboard for the meantime..
Enviado desde mi GT-I9505 mediante Tapatalk
Click to expand...
Click to collapse
Never flash firmware intended for another device, no matter how similar. (Though im not sure what youre asking exactly since your device is the canadian model. You said it's an I747M right?)
Luckily Mobile Odin doesn't flash the full firmware.
You will need a debrick.img created using your model device with the same or newer firmware. Hopefully one of the ones above will work for you.
Sent from my SGH-T999 using Tapatalk
yea, i also advise installing firmwares OTA or with kies because it will get the right firmware for your device and you will have a smaller chance of screwing up. If you get it manually at sam-mobile, you might get the wrong one which can mess up your phone
DocHoliday77 said:
Never flash firmware intended for another device, no matter how similar. (Though im not sure what youre asking exactly since your device is the canadian model. You said it's an I747M right?)
Luckily Mobile Odin doesn't flash the full firmware.
You will need a debrick.img created using your model device with the same or newer firmware. Hopefully one of the ones above will work for you.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I had trouble flashing an image and yes my Model is i347m Telcel and canadian carriers use same s3 Model. I had to buy another motherboard a verizon one. I was tould i needed a class 10 16gb card. I tried with 3 different class 4 cards and didnt worked.
bighleo114312 said:
I had trouble flashing an image and yes my Model is i347m Telcel and canadian carriers use same s3 Model. I had to buy another motherboard a verizon one. I was tould i needed a class 10 16gb card. I tried with 3 different class 4 cards and didnt worked.
Click to expand...
Click to collapse
Using any SD cards other than class 10 have a higher fail rate. That doesnt mean that it wont work at all. Try a class 10 card. In your case, it wont work with class 4.
---------- Post added at 01:17 PM ---------- Previous post was at 01:15 PM ----------
Also, what build of KK did you flash? You need someone on that build, to create one for you.
Hello people, I am a noob here.
I have T999 and i had it working on 4.3 then i wanted to downgrade to 4.1.1 so i can unlock it with region lock away (thats what i did with my S4)
but then after i was done, i wanted to upgrade to 4.3 and since i cant do that through OTA (tried triangle away, no luck) i thought i can just flash 4.3 through clockwork recover. thing is i think i flashed the wrong one, and i bricked my phone.
after following instructions and got it to boot up to recovery mode, eject SD and do all ODIN work, phone still doesn't turn on without the Unbrick sd
please help:crying:
So it does boot with the sdcard in it, right?
What firmware are you trying to flash with Odin? What version of Odin?
What does it say in the message box? (Copy into a post)
DocHoliday77 said:
So it does boot with the sdcard in it, right?
What firmware are you trying to flash with Odin? What version of Odin?
What does it say in the message box? (Copy into a post)
Click to expand...
Click to collapse
tried these two
T999UVUEMJC_T999TMBEMJC_TMB.zip
T999UVDLJC_T999TMBDLJC_TMB.zip
sorry cant post outside links in here i guess
even tried flashing pit file with the whole process and am still stuck, one weird thing i noticed is the back of the battery says I747 which is ATT
but recovery and ABOUT say its T999. tried Kies to restore but i get an error too
You probably just need to use the NC2 firmware. And if the I747 is printed on the casing (not the sticker), that's normal. If it wasn't a T999, the debrick for it wouldn't work.
DocHoliday77 said:
You probably just need to use the NC2 firmware. And if the I747 is printed on the casing (not the sticker), that's normal. If it wasn't a T999, the debrick for it wouldn't work.
Click to expand...
Click to collapse
have to clarify it says I747 behind the battery ON the back of the phone, not the case or box. but when going into recovery mode it says T999, am guessing someone changed things around before i bought it? the weird part is when i install i747 it takes att sim and works, and when i flash t999 firmware it takes tmobile fine too.
am still stuck at this roadblock, i even tried stock bootloader files like
aboot.mbn
dd
rpm.mbn
sbl2.mbn
sbl3.mbn
tz.mbn
i believe this should fix the issue but not yet
Dont flash partitions individually. Very good chance of a very hard to fix brick....trust me.
If it says I747 on the sticker, I might wonder, but if its printed on the inner casing, on the plastic middle housing, alk T999's have that. Its just usually covered by the sticker.
Have you tried fladhing NC2 firmware? If you're using an NC2 debrick.img, that's the ONLY firmware that'll work.
I have tried nc2 and even tried kies firmware update. still only turn on by sd
Ill put together a recovery flashable NC2 firmware package you can try. Might be a little later before I can get to it though...
---------- Post added at 11:25 AM ---------- Previous post was at 11:23 AM ----------
Just re-read the OP, can you let me know exactly what it was you flashed that caused the brick?
If I know exactly what was flashed I might be able to give you exactly what you need to fix it...maybe.
DocHoliday77 said:
Ill put together a recovery flashable NC2 firmware package you can try. Might be a little later before I can get to it though...
---------- Post added at 11:25 AM ---------- Previous post was at 11:23 AM ----------
Just re-read the OP, can you let me know exactly what it was you flashed that caused the brick?
If I know exactly what was flashed I might be able to give you exactly what you need to fix it...maybe.
Click to expand...
Click to collapse
idk whats the OP is, sorry and i honestly don't know what have i flashed. all i know it was 4.3 (plus i am not advanced at all this)
if the unbrick sd turns on the phone everytime, can i somehow duplicate it with the mmcblk0? assuming thats power management files partition
The debrick sd card has 14 separate partitions on it. So one of those was overwritten when you flashed whatever it was you flashed. Had it been something in the stock firmware, flashing that would've fixed it. So without knowing which partition was overwritten, we won't know what you need. It depends on which it was whether or not we can actually do anything more to help.
And you can't just copy the sd to your device. It doesn't work that way and if you forced it you'd end up with all sorts of problems and probably an unusable, unfixable device.
Hello people, I randomly tried to flash internation model rom on my i747 model s3
it gave wrong model error so i went and modified asserts in the update file and made it pass the check. but phone wont turn on now. i do get red led when charging it. I know it sounds stupid but i just wanted to give a try (was assuming I would unlock the phone :laugh
anyways i do know that 16gb sd un-brick method. but i was wondering if there's a possible different method.
thanks for your time.
Only paying for a jtag service
looks like SD Unbrick method isn't working either, it's not turning on with unbrick sd. i did do a backup before all this. can anyone help here?
Dont give up. Many people have to run through the sd creation process several times before it worked.
It could also be the sd card you are using.
DocHoliday77 said:
Dont give up. Many people have to run through the sd creation process several times before it worked.
It could also be the sd card you are using.
Click to expand...
Click to collapse
the thing is, all debrick img's posted on threads are for 4.3 and up. my phone was on 4.1.2 with an i747 bootloader.
going to order a usb jig (since diy's failed)
If you are on pre-4.3 firmware, it shouldn't matter what debrick.img you use. But if you do get it to boot it will not let you flash anything older than what the image is.
---------- Post added at 03:31 AM ---------- Previous post was at 03:31 AM ----------
Of course it wouldn't hurt to have a 4.1.2 image.....
troolplay1 said:
the thing is, all debrick img's posted on threads are for 4.3 and up. my phone was on 4.1.2 with an i747 bootloader.
going to order a usb jig (since diy's failed)
Click to expand...
Click to collapse
It is a good idea to have a jig handy. But you many not even need it for that one. The exact same thing happened to me (I747m - Fido).
Just make sure the SD card is the same size as your phone for the image.
I am assuming you already found all the steps? You can pm me if you need the necessary files.
distorsun said:
It is a good idea to have a jig handy. But you many not even need it for that one. The exact same thing happened to me (I747m - Fido).
Just make sure the SD card is the same size as your phone for the image.
I am assuming you already found all the steps? You can pm me if you need the necessary files.
Click to expand...
Click to collapse
I have tried many many debirck img's. both for t999 and i747, for 4.3 and whatnot. today i got the jig in the mail but the try failed, still wont turn on. i lost hope and i feel like sending it to ebay service is my only resort. the sd card i was using was a pixar class 10 16GB. idk what would go wrong with that.
the reason that i bricked it, again, is flashing wrong bootloader.
any help would be appreciated.
Idk bro the international s3 is a whole nother phone, it has a quad core exynos processor while we got a dual core snapdragon, it's got a gig of ram we got 2.... That's too name a few differences.....I think the only way to fix it is by a JTAG.......sorry bout the luck bro
O don't think he's got an international version. Thought he mentioned having an I747 before??
Sent from my SAMSUNG-SGH-T999 using Tapatalk
If you don't mind shipping to Canada I have a riffbox and could fix the issue for you.
The debrick method should work though. If it were me I wouldn't give up just yet. I'd at least try a few more times on every sdcard I could get a hold of. Often doesn't work on the first couple of tries, and AFAIK there's no way to know which sdcards will or won't work. Just gotta keep trying.
It is possible that for some reason this method simply won't work, but it has worked in the past for similar types of bricks.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Hey all, Was wondering if anybody had some time to help me troubleshoot why I cannot for the life of me get this method to work and maybe explain to me a few things that are confusing to me...
Basically my phone is hard bricked:
Samsung Galaxy S3 SGH-i747 (AT&T)
- Began with Stock 4.1.2 (almost %100 positive)
- Attempted flash to 4.4.4 Task650's AOKP ROM (Flashed ok but stuck at boot animation) via CWM
- Attempted reverting back to stock with the file below via Odin but I must have missed a step...
I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5
Now I am hard bricked and don't know where to go from here. I've tried several solutions:
- Homemade Jig (didn't work)
- 3 button combo / download mode (doesn't work)
- Odin does not read phone
- Connected to a pc (red power light appears but nothing else)
- SD card method - Using Win32DiskImager to write images to a 16gb class 10 micro sd
- Debrick images used: 4.1.2, 4.1.1, (should i try 4.0.4, 4.3, or even 4.4?)
- How do I tell if the image is writing correctly and partitioning the drive right?
- When the sd card is seen in the computer I see a folder on it named "image" with several files inside it but I don't know how to see partitions
I have screenshots too if you'd like to see them. Let me know if you have any suggestions or have seen anyone with this same issue able to fix it. I'd appreciate it. Thanks.
- Chris
not very knowledgeable about this stuff , but here is a thread (hardbricked 4.1.1) with link to debrick images 4.3/4.4.
http://forum.xda-developers.com/showthread.php?t=2880002
thanks to @DocHoliday77
hopefully someone will come along with some real help.
good luck.
err on the side of kindness
If that firmware was the full firmware, and it appeared to flash, you'll probably need to use the 4.3 debrick.img. also try different sd cards. Many just don't work, where others will.
Look at Tmobiles debrick thread stickied in the development section there. It tells you how to use a Linux liveCD to partition and check the card. The method will work, just use the files from here if you try it.
Chances are, if it doesn't work with the 4.3 image, you'll need a different sd card though.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
If that firmware was the full firmware, and it appeared to flash, you'll probably need to use the 4.3 debrick.img. also try different sd cards. Many just don't work, where others will.
Look at Tmobiles debrick thread stickied in the development section there. It tells you how to use a Linux liveCD to partition and check the card. The method will work, just use the files from here if you try it.
Chances are, if it doesn't work with the 4.3 image, you'll need a different sd card though.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Ok thanks. I'm going to attempt this again tonight using an SD card adapter instead of using another mobile device as the adapter to see if that makes a difference. If that doesn't do the trick I will try the LinuxLiveCD method. I'm using a Lexar 16gb Class 10 micro sd card so I don't think it that is the issue but I guess it wouldn't hurt to try a different brand.
Just curious, has anybody here successfully debricked their phone using another mobile device as the sd card adapter?
Not sure about using the mobile device, but you'd be surprised about the sd cards! I've seen Samsung 16GB Class 10 fail for some people, but work for others. It's really odd as there is no rhyme or reason to it. More of a crap shoot than anything from what I can tell.
I've seen generic 32GB class 4 cards work for people who couldn't get a name brand class 10 one to work at all.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Not sure about using the mobile device, but you'd be surprised about the sd cards! I've seen Samsung 16GB Class 10 fail for some people, but work for others. It's really odd as there is no rhyme or reason to it. More of a crap shoot than anything from what I can tell.
I've seen generic 32GB class 4 cards work for people who couldn't get a name brand class 10 one to work at all.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Good to know, but just to clarify when you say it "fails"... what exactly fails - writing the image file, partitioning the card, or does it write everything to the card ok and then just not boot up? I'm just asking so I know what to look for if it ever happens.
Thanks for the responses as I'm still new to this process and this phone and every little thing helps!
It usually appears to create the debrick sd card just fine. It just doesn't work when you try to boot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
It usually appears to create the debrick sd card just fine. It just doesn't work when you try to boot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
So, it appears that the issue was using the mobile device as the sd card reader. After writing the debrick file to the same sd card with an actual sd card reader, I am able to boot into the stock recovery. From here, I should just be able to flash a stock ROM to it correct or no?
Ok, which debrick.img did you end up using? If you used 4.3, you must flash the MJB firmware. If it was an older image, you will have a choice.
Either way, if you're ready to update to 4.3, and the recovery you are able to boot into is Twrp or cwm, you can flash this:
https://www.androidfilehost.com/?fid=23269279319197285
It is the full mjb base firmware. does not include recovery or system. After flashing this, you should be able to boot at least recovery and download mode without the sd card. If your rom is intact, you'll be able to boot it as well. If not, choose one and flash it.
If you are not ready to update to 4.3, we will have to find another, older version of what I linked above. Or I can make one if required.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Ok, which debrick.img did you end up using? If you used 4.3, you must flash the MJB firmware. If it was an older image, you will have a choice.
Either way, if you're ready to update to 4.3, and the recovery you are able to boot into is Twrp or cwm, you can flash this:
https://www.androidfilehost.com/?fid=23269279319197285
It is the full mjb base firmware. does not include recovery or system. After flashing this, you should be able to boot at least recovery and download mode without the sd card. If your rom is intact, you'll be able to boot it as well. If not, choose one and flash it.
If you are not ready to update to 4.3, we will have to find another, older version of what I linked above. Or I can make one if required.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Ok, after playing with the phone for awhile I have found out that I can boot into download mode now. After rebooting, I was able to boot into the stock 4.3 ROM but I noticed I lost root access. Now the problem is I cannot enter the recovery to even flash the file you mentioned above (I flashed CWM via Odin but I can't boot into it). The phone can be seen in Odin now as well. I've done a little bit of research on achieving Root access again but I came across a post that mentioned I could ruin my IMEI number by flashing a "CF-Autoroot" file, should I be worried about doing this now that I'm on 4.3 or am I ok since I didn't use the OTA 4.3 ??
Again, thank you so much for the advise! I'm so glad this phone isn't a brick anymore.
Ok. Since you can get download mode, that changes things.
Boot download mode, remove the sdcard and flash the MJB firmware in Odin. Download here:
http://forum.xda-developers.com/showthread.php?t=2722660
Then, use Towelroot to root the device. (I posted a good guide for this. It should be on page 1 in the Tmobile General section: http://forum.xda-developers.com/showthread.php?t=2793071)
Towelroot is by far the easiest root you'll ever use! Just make sure you read the first two posts before starting!
At this point you should be fully recovered and running stock rooted MJB.
Now before anything else, since you mentioned the imei, backup your NV Data. Very easy!
Install and open Terminal Emulator from the store and enter this:
Code:
su
reboot nvbackup
It'll reboot and create a hidden, permanent, on device backup of your NV data. If corruption is ever detected it'll auto restore during boot, so it essentially protects you from ever losing your imei!
After that, you can do as you wish! If you want to update to 4.4.2 though, I recommend doing that before you root. After flashing MJB, reboot and you should be able to get the official OTA. Then continue with the rest if the instructions above.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Ok. Since you can get download mode, that changes things.
Boot download mode, remove the sdcard and flash the MJB firmware in Odin. Download here:
http://forum.xda-developers.com/showthread.php?t=2722660
Then, use Towelroot to root the device. (I posted a good guide for this. It should be on page 1 in the Tmobile General section: http://forum.xda-developers.com/showthread.php?t=2793071)
Towelroot is by far the easiest root you'll ever use! Just make sure you read the first two posts before starting!
At this point you should be fully recovered and running stock rooted MJB.
Now before anything else, since you mentioned the imei, backup your NV Data. Very easy!
Install and open Terminal Emulator from the store and enter this:
Code:
su
reboot nvbackup
It'll reboot and create a hidden, permanent, on device backup of your NV data. If corruption is ever detected it'll auto restore during boot, so it essentially protects you from ever losing your imei!
After that, you can do as you wish! If you want to update to 4.4.2 though, I recommend doing that before you root. After flashing MJB, reboot and you should be able to get the official OTA. Then continue with the rest if the instructions above.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I flashed the files from the link you posted in Odin and now I am golden! I attempted to upgrade OTA to 4.4.2 and it's saying that I'm up to date and that there are no updates available for my phone and to check back in 24 hrs. After seeing that, I checked the system status and it says "OFFICIAL" so I don't really understand why I can't upgrade OTA. I noticed that something I've done has tripped the warranty bit But whatever, I am perfectly fine with staying on 4.3 for now - I didn't see too much to really need to upgrade to 4.4.2 quite yet... although I might try to upgrade again tomorrow and see what happens. I don't really need root at the moment but if I attempt to flash to anything else in the future, I'll give towelroot a shot.
Again, thanks for your help - I owe ya one DocHoliday
CornfedChris said:
.... I attempted to upgrade OTA to 4.4.2 and it's saying that I'm up to date and that there are no updates available for my phone and to check back in 24 hrs.
... although I might try to upgrade again tomorrow and see what happens.
Click to expand...
Click to collapse
I've seen reports of this more than once where someone going back to stock initially receives the no updates available msg and then after 24 hrs or so it becomes available. So, your plan sounds good.
CornfedChris said:
I flashed the files from the link you posted in Odin and now I am golden! I attempted to upgrade OTA to 4.4.2 and it's saying that I'm up to date and that there are no updates available for my phone and to check back in 24 hrs. After seeing that, I checked the system status and it says "OFFICIAL" so I don't really understand why I can't upgrade OTA. I noticed that something I've done has tripped the warranty bit But whatever, I am perfectly fine with staying on 4.3 for now - I didn't see too much to really need to upgrade to 4.4.2 quite yet... although I might try to upgrade again tomorrow and see what happens. I don't really need root at the moment but if I attempt to flash to anything else in the future, I'll give towelroot a shot.
Again, thanks for your help - I owe ya one DocHoliday
Click to expand...
Click to collapse
Right on! Glad to hear you got it all fixed up! If that update does become available later, please let us know. I've been telling several people to wait a day, but I haven't heard if it actually came through for any of them yet.
If you do decide to root in the future, just don't forget about that backup!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
So tonight while I was watching TV I looked down at my phone and noticed it decided to just go ahead and update itself to 4.4.2, haha. So apparently there's an auto-update defaulted in the settings somewhere. I haven't really noticed too many differences yet but I'm liking it so far. :good: