I think I've hard bricked my gf's i747m to the point where there's no saving it, but I figured I would ask before I threw in the towel.
Short story is, after messing around with AOKP 4.4.4 (Kitkat) Task650 (9.10.2014), I would keep getting stuck in bootloop. I tried updating my bootloader via philz touch cwm and seemed to have bricked it.
I've tried a few different images in the debricking threads, is there any hope for me? I've tried numerous sd cards too and no luck.
Any help would be much appreciated.
What bootloader did you install? Does it boot into download mode at all?
audit13 said:
What bootloader did you install? Does it boot into download mode at all?
Click to expand...
Click to collapse
Bootloader was "boot_CWM_I747MVLUEMK5.zip"
It won't boot into download at all, without the battery in when I plug it into charge I just get a red led on the phone.
What stock ROM was on the phone before you tried to install a new bootloader?
You got the bootloader from here: http://forum.xda-developers.com/showthread.php?t=2321310 ?
audit13 said:
What stock ROM was on the phone before you tried to install a new bootloader?
You got the bootloader from here: http://forum.xda-developers.com/showthread.php?t=2321310 ?
Click to expand...
Click to collapse
Not sure if I got it from there or a different thread, but that was the bootloader. I think the stock rom was 4.4.2
The mk5 bootloader is a 4.3 bootloader. If you were running stock 4.4.2 bootloader and modem and flashed the 4.3 mk5 bootloader, you would wind up with a 4.4.2 modem on and 4.3 bootloader. From what I have read on this forum, this combination of bootloader and modem can only be fixed via jtag.
Which carrier is the phone with? If it's under warranty, maybe try and have it RMA'd.
audit13 said:
The mk5 bootloader is a 4.3 bootloader. If you were running stock 4.4.2 bootloader and modem and flashed the 4.3 mk5 bootloader, you would wind up with a 4.4.2 modem on and 4.3 bootloader. From what I have read on this forum, this combination of bootloader and modem can only be fixed via jtag.
Which carrier is the phone with? If it's under warranty, maybe try and have it RMA'd.
Click to expand...
Click to collapse
Debrick images don't work with that combination eh? It's a bell phone, well out of warranty.
tomlemange said:
Debrick images don't work with that combination eh? It's a bell phone, well out of warranty.
Click to expand...
Click to collapse
Not that I have seen on this forum.
I'm not sure where you are located but there are some jtag places I know of in Toronto that could probably fix the phone, but it would be expensive given the age of the phone.
here is a thread with jtag for $25 you can check on.
http://forum.xda-developers.com/showthread.php?t=2874113
cheapest i've seen.
good luck
err on the side of kindness
mrrocketdog said:
here is a thread with jtag for $25 you can check on.
http://forum.xda-developers.com/showthread.php?t=2874113
cheapest i've seen.
good luck
err on the side of kindness
Click to expand...
Click to collapse
Thanks for the head up, I couldn't find any cheaper either.
audit13 said:
Not that I have seen on this forum.
I'm not sure where you are located but there are some jtag places I know of in Toronto that could probably fix the phone, but it would be expensive given the age of the phone.
Click to expand...
Click to collapse
I'm in Halifax so there really isn't too many options here, if I can find one at all...
If I ordered a replacement motherboard online, would it need to be for the 747m specifically?
tomlemange said:
Thanks for the head up, I couldn't find any cheaper either.
I'm in Halifax so there really isn't too many options here, if I can find one at all...
If I ordered a replacement motherboard online, would it need to be for the 747m specifically?
Click to expand...
Click to collapse
If you order the motherboard, you should make sure it is for the i747 or i747m because you need to re-use the lcd screen, antenna, mic, etc.
You should also make sure you have the correct tools for assembling the parts into the new board. From what I have seen on ebay, the motherboard is not too cheap either. I suggest getting some quotes before ordering a new board.
Motherboard is the only fix here. 4.4.2 modem plus 4.3 firmware is an unfixable brick in nearly every case I'm afraid.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Related
Hey guys... Looking for 2 answers...
Can the baseband of an M919 be downgraded?
If so, can you point me to a tutorial or Instructions?
It all depends. If you're still on the MDL bootloader you can Odin flash the MDL baseband. If you're already on the MK2 bootloader you can not go back.
☞ Sent from here☜???
baseballfanz said:
It all depends. If you're still on the MDL bootloader you can Odin flash the MDL baseband. If you're already on the MK2 bootloader you can not go back.
☞ Sent from here☜???
Click to expand...
Click to collapse
Already bought unlock codes from FastGSM... so, no need to downgrade now... But, for reference... How do I know which bootloader Im on? or how would one preserve an old bootloader if updating a ROM
You will get the new bootloader if you a) took the OTA update or b) update via kies or c) Odin flashed the whole 4.3 firmware.
In Settings/More/About device, look at your baseband. The last 3 digit should be MDL or MK2.
That's your modem.
Bootloader you need to go into Download mode I believed.
☞ Sent from here☜???
RBThompsonV said:
Already bought unlock codes from FastGSM... so, no need to downgrade now... But, for reference... How do I know which bootloader Im on? or how would one preserve an old bootloader if updating a ROM
Click to expand...
Click to collapse
To be honest, I've found the best thing to do is not jump on the band-wagon and flash an update until you research what the Devs suggest before flashing away. It has saved me a ton of grief and aggravation. They know these updates in and out. For instance, they were warning people to hold off on the MDL to MK2 because of the bootloader and KNOX issue but people didn't research and now some are having problems and it is too late, you can't go back. If you did the OTA update or through Kies you are stuck with MK2 and KNOX. For most people it's no big deal, but if you enjoy modding your phone it can be a pain in the rear.
grncherry said:
To be honest, I've found the best thing to do is not jump on the band-wagon and flash an update until you research what the Devs suggest before flashing away. It has saved me a ton of grief and aggravation. They know these updates in and out. For instance, they were warning people to hold off on the MDL to MK2 because of the bootloader and KNOX issue but people didn't research and now some are having problems and it is too late, you can't go back. If you did the OTA update or through Kies you are stuck with MK2 and KNOX. For most people it's no big deal, but if you enjoy modding your phone it can be a pain in the rear.
Click to expand...
Click to collapse
Picked it up with the MK2... was trying to do a SIM UNLOCK without paying $30US (The IMEI unlock is $30, the USB/software unlock is $15... and the debug unlock is free...but it looks like the debug is done away with in MK2)...
Should have probably mentioned, this is a Metro PCS flashed with TMo rom (did that to try to get the debug menu to work correctly as there has been some luck with it)... Anyway, now the fun part of getting back to MPCS...
On a side note... you guys know about the Re-Partition flag in Odin? You guys here in XDA make it sound as if its a good way to brick a phone... in the MPCS forum (on a dif. site)... has that mark checked when flashing back to the MPCS rom (stock) from a TMo rom... any ideas?
RBThompsonV said:
Picked it up with the MK2... was trying to do a SIM UNLOCK without paying $30US (The IMEI unlock is $30, the USB/software unlock is $15... and the debug unlock is free...but it looks like the debug is done away with in MK2)...
Should have probably mentioned, this is a Metro PCS flashed with TMo rom (did that to try to get the debug menu to work correctly as there has been some luck with it)... Anyway, now the fun part of getting back to MPCS...
On a side note... you guys know about the Re-Partition flag in Odin? You guys here in XDA make it sound as if its a good way to brick a phone... in the MPCS forum (on a dif. site)... has that mark checked when flashing back to the MPCS rom (stock) from a TMo rom... any ideas?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2492557
Don't know if you can gain any info from here, I didn't read through the thread. Hope something there helps you. By the way you are permanently unlocked so no worries there
RBThompsonV said:
Picked it up with the MK2... was trying to do a SIM UNLOCK without paying $30US (The IMEI unlock is $30, the USB/software unlock is $15... and the debug unlock is free...but it looks like the debug is done away with in MK2)...
Should have probably mentioned, this is a Metro PCS flashed with TMo rom (did that to try to get the debug menu to work correctly as there has been some luck with it)... Anyway, now the fun part of getting back to MPCS...
On a side note... you guys know about the Re-Partition flag in Odin? You guys here in XDA make it sound as if its a good way to brick a phone... in the MPCS forum (on a dif. site)... has that mark checked when flashing back to the MPCS rom (stock) from a TMo rom... any ideas?
Click to expand...
Click to collapse
If your phone is rooted just use RegionLockAway app.
☞ Sent from here☜???
baseballfanz said:
If your phone is rooted just use RegionLockAway app.
☞ Sent from here☜???
Click to expand...
Click to collapse
I tried, it didnt work.
RBThompsonV said:
I tried, it didnt work.
Click to expand...
Click to collapse
Is your phone rooted? Peoples here saying it work fir their metro pcs phone.
http://forum.xda-developers.com/showthread.php?t=2381821
☞ Sent from here☜???
baseballfanz said:
Is your phone rooted? Peoples here saying it work.
http://forum.xda-developers.com/showthread.php?t=2381821
☞ Sent from here☜???
Click to expand...
Click to collapse
Is the phone paid for in full?
If so the carrier that sold it to you HAS to give you the unlock code.
baseballfanz said:
Is your phone rooted? Peoples here saying it work fir their metro pcs phone.
http://forum.xda-developers.com/showthread.php?t=2381821
☞ Sent from here☜???
Click to expand...
Click to collapse
oh, hell... you know what... I think I didnt root the TMo rom after flashing from Metro...
HA!!! I think that was the issue
Skipjacks said:
Is the phone paid for in full?
If so the carrier that sold it to you HAS to give you the unlock code.
Click to expand...
Click to collapse
Yeah, try having that conversation with AT&T...
My friend decided to use the EZ-Unlock app(link below) that unlocks the bootloader for the verizon galaxy s3 on my i747 and well it is now a brick, is there anything i can do to fix this without a JTAG?
omeadsthename said:
My friend decided to use the EZ-Unlock app(link below) that unlocks the bootloader for the verizon galaxy s3 on my i747 and well it is now a brick, is there anything i can do to fix this without a JTAG?
Click to expand...
Click to collapse
yes, take him outside and beat the crap out of him. Then take his money and go get a new phone.
Other than that, I don't know.
Can you access download mode or recovery?
jack man said:
yes, take him outside and beat the crap out of him. Then take his money and go get a new phone.
Other than that, I don't know.
Can you access download mode or recovery?
Click to expand...
Click to collapse
No I cannot, my friend(parklane79) and I actually found a method, it seems promising but i need to try it out first.
im not afforded the link rights yet but the title is "Fixing a bootloader-bricked Galaxy S3 using an SD card (Qualcomm SGS3 variants)" and a more simpler guide for n00bs(although not a complete n00b been doing this for a few years now :good: ) like myself, "[GUIDE]Unbrick a Hard Bricked SPRINT Galaxy S3 (Without JTAG)" but for the second guide you need to grab the i747 debrick.img off the first page of the first guide.
omeadsthename said:
No I cannot, my friend(parklane79) and I actually found a method, it seems promising but i need to try it out first.
im not afforded the link rights yet but the title is "Fixing a bootloader-bricked Galaxy S3 using an SD card (Qualcomm SGS3 variants)" and a more simpler guide for n00bs(although not a complete n00b been doing this for a few years now :good: ) like myself, "[GUIDE]Unbrick a Hard Bricked SPRINT Galaxy S3 (Without JTAG)" but for the second guide you need to grab the i747 debrick.img off the first page of the first guide.
Click to expand...
Click to collapse
Yea tried with a class 10 16g micro sd like a million times and it wont work.and i think its because i dont have the 4.4.2 img if some one could help me out by uploading it. u et the img via busybox dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=70
So the phone won't power on at all? Can't get into download or recovery?
are you %100 certain it's the AT&T 4.3 debrick.img? did you put it on the SD card using win32diskimager?
audit13 said:
So the phone won't power on at all? Can't get into download or recovery?
Click to expand...
Click to collapse
The phone won't even vibrate. Wish i could get to DL/Recovery mode. :/
yowski said:
are you %100 certain it's the AT&T 4.3 debrick.img? did you put it on the SD card using win32diskimager?
Click to expand...
Click to collapse
im 100% sure. the issue is tho that i was on 4.4.2 and dont know it an i747(AT&T) 4.3 debrick.img has the same handshake/protocol whatever you want to call it as a 4.4.2 debrick.img I tried it out tho anyways. but in short yes im 100% sure it was a 4.3 debrick img. And yes I did use win32diskimager. I tried once on linux mint but i believe the file corrupted so i just ended up using win32DM. I mean they are supposed to do the same thing, if im not mistaken
omeadsthename said:
The phone won't even vibrate. Wish i could get to DL/Recovery mode. :/
im 100% sure. the issue is tho that i was on 4.4.2 and dont know it an i747(AT&T) 4.3 debrick.img has the same handshake/protocol whatever you want to call it as a 4.4.2 debrick.img I tried it out tho anyways. but in short yes im 100% sure it was a 4.3 debrick img. And yes I did use win32diskimager. I tried once on linux mint but i believe the file corrupted so i just ended up using win32DM. I mean they are supposed to do the same thing, if im not mistaken
Click to expand...
Click to collapse
when you plug it into the computer does anything come up? also, when you plug it in with no battery do you get a red LED?
yowski said:
when you plug it into the computer does anything come up? also, when you plug it in with no battery do you get a red LED?
Click to expand...
Click to collapse
Yes my comp tries to install that one qualcomm driver. and when i plug in without battery a red LED comes on.
omeadsthename said:
Yes my comp tries to install that one qualcomm driver. and when i plug in without battery a red LED comes on.
Click to expand...
Click to collapse
Then you should be able to use a debrick.img. are you using an sd card the same size as your phone's internal memory? if you had it on 4.4.2 then you might need a debrick.img from someone with the same phone on the same network running 4.4.2?
yowski said:
Then you should be able to use a debrick.img. are you using an sd card the same size as your phone's internal memory? if you had it on 4.4.2 then you might need a debrick.img from someone with the same phone on the same network running 4.4.2?
Click to expand...
Click to collapse
yes i am using same size card. and i have been asking all over for a 4.4.2 debrick img but no one has uploaded.
omeadsthename said:
yes i am using same size card. and i have been asking all over for a 4.4.2 debrick img but no one has uploaded.
Click to expand...
Click to collapse
sounds like you're stuck until you get that .img file. If you know someone with the same phone you could maybe get them to install 4.4.2 and get the file from them? otherwise keep asking around or wait until 4.4.2 is released for the s3, which might take a while.
yowski said:
sounds like you're stuck until you get that .img file. If you know someone with the same phone you could maybe get them to install 4.4.2 and get the file from them? otherwise keep asking around or wait until 4.4.2 is released for the s3, which might take a while.
Click to expand...
Click to collapse
Unfortunately kids at my high school are afraid of rooting, so xda is basically my only bet. Im just surprised that some sr member hasnt added a debrick img to their threads. I mean its 4.4 and this is android central!
omeadsthename said:
yes i am using same size card. and i have been asking all over for a 4.4.2 debrick img but no one has uploaded.
Click to expand...
Click to collapse
i would help you out but my S3 is currently hard bricked on stock 4.3 and im sending it back to the insurance company once my S4 arrives tomorrow.
yowski said:
i would help you out but my S3 is currently hard bricked on stock 4.3 and im sending it back to the insurance company once my S4 arrives tomorrow.
Click to expand...
Click to collapse
Cant they find out that you are root and hard bricked? like doesnt that void warranty. and if its a 4.3 h brick cant u just use the sd method?
omeadsthename said:
yes i am using same size card. and i have been asking all over for a 4.4.2 debrick img but no one has uploaded.
Click to expand...
Click to collapse
I did, it was on CM 10.2 when i had flashed improper bootloaders and bricked it. I used the sd card to install 4.3, unroot+ reset flash counter then took it out so it went back to bricked. My only fear is that they may some how get it into download mode instead of just replacing the board and see the warranty bit: 1 which isnt able to be reset as it is an e-fuse which is blown when you install firmware without knox.
yowski said:
I did, it was on CM 10.2 when i had flashed improper bootloaders and bricked it. I used the sd card to install 4.3, unroot+ reset flash counter then took it out so it went back to bricked. My only fear is that they may some how get it into download mode instead of just replacing the board and see the warranty bit: 1 which isnt able to be reset as it is an e-fuse which is blown when you install firmware without knox.
Click to expand...
Click to collapse
Are you using the samsung warranty of AT&T? And also if the sd card is working for u cant you just use odin to flash? Or does the sd card not fix any bootloader issues?
omeadsthename said:
Are you using the samsung warranty of AT&T? And also if the sd card is working for u cant you just use odin to flash? Or does the sd card not fix any bootloader issues?
Click to expand...
Click to collapse
im sending in it through bell mobility. it was a replacement phone that i paid the $150 deductable on and has a 90 warranty. I said it was having issues/defective so they sent an s4 as free replacement on the 90 day. I prefer it to be bricked to fit the defective description as well as to decrease the chances of them finding out i had messed with it, the only real sign being "warranty bit: 1" in red on the download screen. I did use odin to flash the current 4.3 stock that it has right now, and i might be able to get it to boot without the card if i flash the bootloaders some more despite having done it twice and the card still being required. Like i said though, i prefer it hard bricked and i've erased every sign other than warranty bit: 1 that i messed with it by installing stock, unrooting, and resetting flash counter.
yowski said:
im sending in it through bell mobility. it was a replacement phone that i paid the $150 deductable on and has a 90 warranty. I said it was having issues/defective so they sent an s4 as free replacement on the 90 day. I prefer it to be bricked to fit the defective description as well as to decrease the chances of them finding out i had messed with it, the only real sign being "warranty bit: 1" in red on the download screen. I did use odin to flash the current 4.3 stock that it has right now, and i might be able to get it to boot without the card if i flash the bootloaders some more despite having done it twice and the card still being required. Like i said though, i prefer it hard bricked and i've erased every sign other than warranty bit: 1 that i messed with it by installing stock, unrooting, and resetting flash counter.
Click to expand...
Click to collapse
hmm i wish i could do that to my phone too. i mean, i dont even know how i would unroot without getting my phone on. but if im this hard bricked they probs cant tell anyways. im guessing?
uz unlock HARD BRICKING S3'S
omeadsthename said:
My friend decided to use the EZ-Unlock app(link below) that unlocks the bootloader for the verizon galaxy s3 on my i747 and well it is now a brick, is there anything i can do to fix this without a JTAG?
Click to expand...
Click to collapse
I DID THE SAME THING ! but i used debrick (i535 vzw 4.3 ) and it pattially worked at least it will recovery and odin but i think it needs to be the 40 mbps type card the black micro would not work for me , then i flashed the wrong recovery and am starting all over but the debrick still getting me into odin thats ware you will sideload the right recovery and firmware ,rom what ever hope ( i even paid for cdma work shop and it aint did jack ) debrick then odin sideload look it up thats the best i got
Need someone to verify this for me. It says here that you can use a program called "EZ Unlock" to unlock the bootloader on the Galaxy S 3.
Can someone verify if this app would unlock my GS3 bootloader? I'm on 4.3 so mine is updated unfortunately. I would just get the bootloader unlock code from Samsung but I don't have an international model, that's the only one they would give you the BL code for.
EXTRA CREDIT I heard rumor of something called a "golden backup" supposedly a backup that exist on the phone of the older version you upgraded from, anyone?
drago10029 said:
Need someone to verify this for me. It says here that you can use a program called "EZ Unlock" to unlock the bootloader on the Galaxy S 3.
Can someone verify if this app would unlock my GS3 bootloader? I'm on 4.3 so mine is updated unfortunately. I would just get the bootloader unlock code from Samsung but I don't have an international model, that's the only one they would give you the BL code for.
EXTRA CREDIT I heard rumor of something called a "golden backup" supposedly a backup that exist on the phone of the older version you upgraded from, anyone?
Click to expand...
Click to collapse
No joy there, I'm afraid. Ol' Sam knew what he was doing with the 4.3 bootloader thing and a BL with EZ Unlock is a No-No. I just tried it now and whilst the whole process went well enough, the outcome was a hard brick. It, therefore, doesn't seem possible to 'unlock' your bootloader, at least, not for now.
The 'golden backup' is an option you see in the service menu. Not sure what it does though.
Larry2999 said:
No joy there, I'm afraid. Ol' Sam knew what he was doing with the 4.3 bootloader thing and a BL with EZ Unlock is a No-No. I just tried it now and whilst the whole process went well enough, the outcome was a hard brick. It, therefore, doesn't seem possible to 'unlock' your bootloader, at least, not for now.
The 'golden backup' is an option you see in the service menu. Not sure what it does though.
Click to expand...
Click to collapse
Really you tried it out? why?!?! also any information on the golden backup? how about accessing the service menu on android 4.3?
drago10029 said:
Really you tried it out? why?!?! also any information on the golden backup? how about accessing the service menu on android 4.3?
Click to expand...
Click to collapse
Yeah. Just to see if there was any way I could add to the body of knowledge... I'm aware EZ Unlock works with older firmware versions of the VZW model. The instructions on the site, however, suggested it works with the i747 as well. Apparently, this must be with older firmware versions as well and not the 4.3. After powering off the phone following the process, the phone just wouldn't power back on again. At least, not until, I'd inserted my debrick card and done a firmware restore.
I know I've seen the golden back function when accessing the service menu via *#197328640#. Never had to use it though so I wouldn't know if it does back up from older firmware.
Larry2999 said:
Yeah. Just to see if there was any way I could add to the body of knowledge... I'm aware EZ Unlock works with older firmware versions of the VZW model. The instructions on the site, however, suggested it works with the i747 as well. Apparently, this must be with older firmware versions as well and not the 4.3. After powering off the phone following the process, the phone just wouldn't power back on again. At least, not until, I'd inserted my debrick card and done a firmware restore.
I know I've seen the golden back function when accessing the service menu via *#197328640#. Never had to use it though so I wouldn't know if it does back up from older firmware.
Click to expand...
Click to collapse
Well, your failure has become my knowledge lol. I'm still really interested in the learning about the "golden backup" though. I wonder if the Galaxy S4 unlock procedure would work for us? I may play around with it.
and glad you knew about the SD De-brick. I thought you just haphazardly tried used EZ unlock :silly: so the SD-Debrick works on 4.3?
Honestly, I've read a lot of stickies but most of the OP's don't mention things supporting 4.3 or not, so it makes trying things out a little tougher. Is there a "back to stock" 4.3 guide? I assumed that's what you did when you bricked. Every 4.3 forum/guide I find is all like (4.3 beware this and beware that!) lol
Back to stock
drago10029 said:
Well, your failure has become my knowledge lol. I'm still really interested in the learning about the "golden backup" though. I wonder if the Galaxy S4 unlock procedure would work for us? I may play around with it.
and glad you knew about the SD De-brick. I thought you just haphazardly tried used EZ unlock :silly: so the SD-Debrick works on 4.3?
Honestly, I've read a lot of stickies but most of the OP's don't mention things supporting 4.3 or not, so it makes trying things out a little tougher. Is there a "back to stock" 4.3 guide? I assumed that's what you did when you bricked. Every 4.3 forum/guide I find is all like (4.3 beware this and beware that!) lol
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2658486 As close as it gets for now...at&t
drago10029 said:
Well, your failure has become my knowledge lol. I'm still really interested in the learning about the "golden backup" though. I wonder if the Galaxy S4 unlock procedure would work for us? I may play around with it.
and glad you knew about the SD De-brick. I thought you just haphazardly tried used EZ unlock :silly: so the SD-Debrick works on 4.3?
Honestly, I've read a lot of stickies but most of the OP's don't mention things supporting 4.3 or not, so it makes trying things out a little tougher. Is there a "back to stock" 4.3 guide? I assumed that's what you did when you bricked. Every 4.3 forum/guide I find is all like (4.3 beware this and beware that!) lol
Click to expand...
Click to collapse
Oh! I wouldn't risk "bricking" my phone if I wasn't reasonably sure I could recover. In fact, I've "intentionally" bricked this particular device in every way you can imagine just for learning purposes. I really think an unlock exploit is possible and we may be closer to one now than we know. Indeed I feel Touchwiz 4.3 has been unduly vilified because of the secure bootloader and other than the absence of a free unlock option, it's a major improvement on previous versions. I haven't seen the S4 unlock procedure. Can you send me a link to any thread on this?
There are a couple of threads dealing with recovery and return to stock for the 4.3. The first is a guide on how to recover from a hard brick caused by flashing the wrong bootloader. That was where I got my debrick file from ...
http://forum.xda-developers.com/showthread.php?t=2549068
Whilst the second is a guide on returning to factory stock (4.3) firmware via custom recovery ...
http://forum.xda-developers.com/showthread.php?t=2658486
pckarma112 said:
http://forum.xda-developers.com/showthread.php?t=2658486 As close as it gets for now...at&t
Click to expand...
Click to collapse
Larry2999 said:
Oh! I wouldn't risk "bricking" my phone......
Click to expand...
Click to collapse
"I REPLIED TO THIS AT WORK FRIDAY, WONDER WHAT HAPPENED"
Thanks both you guys, I'm actually not concerned with warranty though. I'm ultra careful so I've never used once so far for something I broke on a phone lol.
And thanks for the stock guide pckarma, probably wouldn't of found that on my own. also would you 2 know if flashing any i747 rom with cmw/twrp would work on my phone with updated bootloader? (being that I don't flash a different bootloader of course lol)
drago10029 said:
"I REPLIED TO THIS AT WORK FRIDAY, WONDER WHAT HAPPENED"
Thanks both you guys, I'm actually not concerned with warranty though. I'm ultra careful so I've never used once so far for something I broke on a phone lol.
And thanks for the stock guide pckarma, probably wouldn't of found that on my own. also would you 2 know if flashing any i747 rom with cmw/twrp would work on my phone with updated bootloader? (being that I don't flash a different bootloader of course lol)
Click to expand...
Click to collapse
Yes, it should work - as long as you are not flashing a non-compatible bootloader. I noticed also from the development threads that someone has now put together an Odin flash-able image for 4.3
Larry2999 said:
Yes, it should work - as long as you are not flashing a non-compatible bootloader. I noticed also from the development threads that someone has now put together an Odin flash-able image for 4.3
Click to expand...
Click to collapse
The only compatibility problem I had was with the old TWRP version which I knew doesn't work with KK ROMs, just updated to the new TWRP and Kit Kat flashed fine. And "development thread"? You mean one of the stickies their?
drago10029 said:
The only compatibility problem I had was with the old TWRP version which I knew doesn't work with KK ROMs, just updated to the new TWRP and Kit Kat flashed fine. And "development thread"? You mean one of the stickies their?
Click to expand...
Click to collapse
I was referring to the one posted in this thread by enewman...
http://forum.xda-developers.com/showthread.php?t=2722660
Larry2999 said:
I was referring to the one posted in this thread by enewman...
http://forum.xda-developers.com/showthread.php?t=2722660
Click to expand...
Click to collapse
When the time comes hopefully it works.
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.
Hi all,
I have a Bell Canada Samsung Galaxy S3 that I can't get the modem to work on. I have Philz recovery on it and have tried a few modem files but neither the wireless or the mobile carrier works.
I have tried putting cyanogenmod on it but am back on a stock ROM at this point. I am at a bit of a loss as to what to do.
The phone boots fine, looks all normal but I just can't get on the mobile network(tried multiple SIM's).
I am really hoping you can help!
Does your phone display the correct imei when you dial *#06#??
It does, it shows my IMEI with a /5 at the end.
At this point, I am running I747MVLUEMK5_I747MOYCEMK5_BMC
I also do show cellular signal but can't seem to connect. When I scan wireless networks, I pick nothing up.
Any ideas?
Thanks again!
audit13 said:
Does your phone display the correct imei when you dial *#06#??
Click to expand...
Click to collapse
Is the phone blacklisted?
I don't think so, how can I verify that? I did buy it used just over a year ago and it only broke about a month ago?
audit13 said:
Is the phone blacklisted?
Click to expand...
Click to collapse
You can check your imei here: http://www.protectyourdata.ca/check-the-status-of-your-device-in-canada/
All clean on there!
audit13 said:
You can check your imei here: http://www.protectyourdata.ca/check-the-status-of-your-device-in-canada/
Click to expand...
Click to collapse
You've had the phone for a while so I didn't think it would be blacklisted.
Since you have the 4.3 bootloader, you need to have a compatible modem and, from my experience, only the mk5 modem will work.
Did you use Odin to flash back to stock?
Yes, that is how I put the current stock firmware on it. I had cyanogenmod on it at one point...
audit13 said:
You've had the phone for a while so I didn't think it would be blacklisted.
Since you have the 4.3 bootloader, you need to have a compatible modem and, from my experience, only the mk5 modem will work.
Did you use Odin to flash back to stock?
Click to expand...
Click to collapse
I am at a loss as to why you cannot connect to a network. Which carrier do you want to connect with?
audit13 said:
I am at a loss as to why you cannot connect to a network. Which carrier do you want to connect with?
Click to expand...
Click to collapse
Hello i hope i can help i have to ran into this problem before and here is what i did to fix it.
Flash the modem using the dl from this forum
http://forum.xda-developers.com/showthread.php?t=2745607
also once you are done you will need the nv writer and the i747 dl froim teh same forum that will get you all fixed up i promise. Just follow the steps and ready the whole thing first. I looked for three days and finally resolved it with Larrys help
scoeas1982 said:
Hello i hope i can help i have to ran into this problem before and here is what i did to fix it.
Flash the modem using the dl from this forum
http://forum.xda-developers.com/showthread.php?t=2745607
also once you are done you will need the nv writer and the i747 dl froim teh same forum that will get you all fixed up i promise. Just follow the steps and ready the whole thing first. I looked for three days and finally resolved it with Larrys help
Click to expand...
Click to collapse
Is the i747 modem compatible with the i747m?