Related
I know there are other posts that address a similar problem, but I've started this one because most of the others have had no activity in about two months or more. So, I apologize in advance for bringing up a problem that has been covered before to some extent. In addition, my problem may be somewhat unique.
So, here is a description -- sorry about the length.
1. I rooted my phone --
HTC Evo 4g EVT3
HBoot 2.10
Radio 2.15.00.11.19
Orgiinal OS: Froyo (2.2)
Current OS: Stock Froyo with addition of BusyBox.
-- with Unrevoked3 and got s-off and su.
2. Switched recovery to RA 2.3
3. Flashed MikG 2.5 and decided to go back to stock, but hadn't made an RA nandroid.
4. Used a stock image file I located.
All of the above was successful.
5. Tried to partition my sd card to get sd-ext. Tried RA, but it appeared not to take. I kept getting an error message about not being able to mount /dev/block/mmcblk0p or something like that.
6. Tried to partition the sdcard from Rom Manager Premium.
7. Got a message saying that I had to flash Clockworkmod in order for Rom Manager to do the partitioning (it appears that Rom Manager is merely a GUI for Clockworkmod recoveries).
8. Stupidly, as it turns out, I didn't do due diligence with respect to the compatibiity of my current Rom or whatever and the various versions of CWM nor did I realize that when Rom Manager flashed CWM, it would flash the latest version (5.0.2.2). Sooooo, I pushed the "Ok" button. And that began a cascading series of problems.
9. I went into bootloader but couldn't get to Recovery.
10. Tried to use HBoot to flash a new recovery (renamed "PC36IMG.ZIP" and then another renamed "PC36IMG.IMG"). However, the bootloader never recognized the files. Either it was not scanning the root directory of the sd-card or something else was wrong with the bootloader software.
11. The phone would boot up fine, but I couldn't get to Recovery to make a nandoid and, therefore, wanted to get a new recovery one the phone.
12. Decided to try to flash either from the terminal emulator or adb. But when I tried I got error messages. So, I used Root Explorer to try to find Flash_Image. And there was none as part of the ROM.
13. Found a copy of Flash_Image and transferred it to /data.
14. Tried to flash RA using the same file I had originally flashed, but this time from adb using Flash_Image. Got the message the file was bad.
15. I exited adb and tried to reboot the phone and got into bootloader, but could go no further. I then selected reboot from the HBoot/fastboot menu. And the phone froze at the htc splash screen (which it also does when choosing Recovery from HBoot).
So, now that you're worn out from reading all of that, is my phone bricked or can it be revived? (I don't know if the phone is recognized by my PC when in HBoot USB.)
Thanks for your help in advance.
Holy text wall batman. And you aren't bricked, but go to the development section, and download amon_ra 2.3 recovery [search] then place the file on the root of your sd card and flash it in the bootloader. Your phone probably didn't detect your previous PC36IMG because it most likely was missing something inside, or the recovery img wasn't named recovery.
The only thing I can think to try is an ruu to complete stock and then re-root and reflash recovery
teh roxxorz said:
Holy text wall batman. And you aren't bricked, but go to the development section, and download amon_ra 2.3 recovery [search] then place the file on the root of your sd card and flash it in the bootloader. Your phone probably didn't detect your previous PC36IMG because it most likely was missing something inside, or the recovery img wasn't named recovery.
Click to expand...
Click to collapse
When I tried that before, bootloader showed nothing at all, it just sat there. But all the posts I had read said to name the file PC36IMG.IMG. So, which is it, "PC36IMG.IMG" or "recovery.img"? Thanks.
---------- Post added at 03:57 PM ---------- Previous post was at 03:53 PM ----------
Evo4eva said:
The only thing I can think to try is an ruu to complete stock and then re-root and reflash recovery
Click to expand...
Click to collapse
Where do I find
a) the appropriate RUU file and
b) instuctions on flashing an RUU and
c) What if the bootloader doesn't "see" the file and just sits there like before?
You'll have to run the exe version of RUU from your computer with the phone in fastboot.
I don't have the link handy, but it's in the Dev section.
HEre's all you need to know: https://spreadsheets.google.com/spr...U2Mi1hNWU0LTRlNjEtYWMyOC1lZmU4ODg1ODc1ODI&ifq
then you can reflash recovery, use Amon Ra, don't use Rom Manager for anything other than fixing permissions.
Also, you may wanna back up your SD Card and format it in Windows. If you have partitions, there is a free program called MiniTool Partition Wizard that will remove the partitions and format your SD Card. Before you copy everything back, just put your ROM on there, get everything back up and running ,then copy your files back to the SD Card
HipKat said:
You'll have to run the exe version of RUU from your computer with the phone in fastboot.
I don't have the link handy, but it's in the Dev section.
HEre's all you need to know: {I've removed the link because as a new member I'm not yet permitted to post outside links}
then you can reflash recovery, use Amon Ra, don't use Rom Manager for anything other than fixing permissions.
Also, you may wanna back up your SD Card and format it in Windows. If you have partitions, there is a free program called MiniTool Partition Wizard that will remove the partitions and format your SD Card. Before you copy everything back, just put your ROM on there, get everything back up and running ,then copy your files back to the SD Card
Click to expand...
Click to collapse
I don't have partitions on my sd card. I was trying to create an sd-ext so I could move my apps there to conserve space (I have a lot of apps). Can MiniTool Partition Wizard do that and, if so, will it do it successfully withut problems?
Also, I know it depends on the RUU I use but, assuming I use the right RUU, will it restore the stock ROM? And do you know if there is a Gingerbread RUU that is not an OTA update?
BTW my phone is supposd to be permanently rooted so that I shouldn't have to reroot provided the RUU doesn't flash the radio also (I used Unrevoked3 to root and then Unrevoked forever to make it permanent.
Finally, you say not to use Rom Manager for anything except fixing permissions. I thought I saw an option in RA 2.3 to do even that? Is that correct and does it work? And, if it does, why did I buy Rom Manager (which a lot of people have recommended)?
Addendum: One thing I notice that I forgot to mention is that I tried at some point in my 15 point prccess in the original post that I tried to flash a new recovery from my sdcard, but for some reason the bootloader either wasn't scanning the card or didn't recognize the file or it was named wrong. All the instructions I've seen, including at the link you provided, say to name the file PC36IMG.zip. Yet, teh roxxorz in his pos above says it should be named Recovery. Even the download page accessed from a link in the RUU tutorial you provided calls the file "PC36IMG". So, now I don't know what it is supposed to be called. And, what do I do if the bootloader won't give me the prompt asking if I want to update?
The partition tool will do everything you need, even create and ext3 partiton, but you wanna use Amon Ra for that.
I forgot to go look, and I will now, for the RUU's for the phones. There's an exe version that you can use to run it from your computer
Here's one, but I'm not sure if this is the pc36img or the exe
http://forum.xda-developers.com/showthread.php?t=874251&highlight=official+ruu
Here's the search I did, so you may find something if that one doesn't work
http://forum.xda-developers.com/search.php?searchid=90954703
HipKat said:
You'll have to run the exe version of RUU from your computer with the phone in fastboot.
I don't have the link handy, but it's in the Dev section.
HEre's all you need to know: https://spreadsheets.google.com/spr...U2Mi1hNWU0LTRlNjEtYWMyOC1lZmU4ODg1ODc1ODI&ifq
then you can reflash recovery, use Amon Ra, don't use Rom Manager for anything other than fixing permissions.
Also, you may wanna back up your SD Card and format it in Windows. If you have partitions, there is a free program called MiniTool Partition Wizard that will remove the partitions and format your SD Card. Before you copy everything back, just put your ROM on there, get everything back up and running ,then copy your files back to the SD Card
Click to expand...
Click to collapse
Decent advice, and i DON'T think your sig is BIG enough.
HipKat said:
The partition tool will do everything you need, even create and ext3 partiton, but you wanna use Amon Ra for that.
I forgot to go look, and I will now, for the RUU's for the phones. There's an exe version that you can use to run it from your computer
Here's one, but I'm not sure if this is the pc36img or the exe
http://forum.xda-developers.com/showthread.php?t=874251&highlight=official+ruu
Here's the search I did, so you may find something if that one doesn't work
http://forum.xda-developers.com/search.php?searchid=90954703
Click to expand...
Click to collapse
I've done a search to and found two links. The first one took me to a page in chinese -- not much help. The second was for what my phone had originally and the file is downloading as we speak.
Now, back to some of my questions:
The instructions in the RUU tutorial used the sd card to flash AmonRA. What if my phone won't recognize the file -- as I mentioned above? And what is the file to be called PC36IMG.zip or Recovery.zip? And does case matter? So, what precisely should the file be called (as it should actually be typed)?
Then, what if when I go to run the exe, it doesn't see the phone (I do have the usb drivers on my computer -- or at least I did, including the one from Unrevoked)?
mjtaryan said:
I've done a search to and found two links. The first one took me to a page in chinese -- not much help. The second was for what my phone had originally and the file is downloading as we speak.
Now, back to some of my questions:
The instructions in the RUU tutorial used the sd card to flash AmonRA. What if my phone won't recognize the file -- as I mentioned above? And what is the file to be called PC36IMG.zip or Recovery.zip? And does case matter? So, what precisely should the file be called (as it should actually be typed)?
Then, what if when I go to run the exe, it doesn't see the phone (I do have the usb drivers on my computer -- or at least I did, including the one from Unrevoked)?
Click to expand...
Click to collapse
The should be named PC36IMG.zip. Windows hides file extensions by default, so just name it PC36IMG, not PC36IMG.zip.zip, and yes case matters. The bootloader will see the file because all the contents will be inside the zip file; just place on the root of your sd card, boot into the bootloader, and take it from there. You need to boot into the bootloader, select fastboot usb, then connect to the pc, and last run the exe; if you have all the drivers, you should have no problem.
teh roxxorz said:
Decent advice, and i DON'T think your sig is BIG enough.
Click to expand...
Click to collapse
You missed it before I resized it. It was like half a page big! lol
HipKat said:
The partition tool will do everything you need, even create and ext3 partiton, but you wanna use Amon Ra for that.
I forgot to go look, and I will now, for the RUU's for the phones. There's an exe version that you can use to run it from your computer
Here's one, but I'm not sure if this is the pc36img or the exe
http://forum.xda-developers.com/showthread.php?t=874251&highlight=official+ruu
Here's the search I did, so you may find something if that one doesn't work
http://forum.xda-developers.com/search.php?searchid=90954703
Click to expand...
Click to collapse
I've done a search too and found two links. The first one took me to a page in chinese -- not much help. The second was for what my phone had originally and the file is downloading as we speak.
Now, back to some of my questions:
The instructions in the RUU tutorial used the sd card to flash AmonRA. What if my phone won't recognize the file -- as I mentioned above? And what is the file to be called PC36IMG.zip or Recovery.zip? And does case matter? So, what precisely should the file be called (as it should actually be typed)?
Then, what if when I go to run the exe, it doesn't see the phone (I do have the usb drivers on my computer -- or at least I did, including the one from Unrevoked)?
HipKat said:
You missed it before I resized it. It was like half a page big! lol
Click to expand...
Click to collapse
NO, I saw it when it was half a page big.
Just for good measure, here's the link for Amon Ra that is already named correctly & has the correct components. You can find it here: http://db.tt/WP0beNa
I'll admit that I just scanned over the majority of the posting after the first post, so I'll read that over really quickly and if I can think of anything else I'll edit this post.
Also, does hboot scan and not find the file, or not scan for it at all?
Sent from my PC36100 using Tapatalk
teh roxxorz said:
Decent advice, and i DON'T think your sig is BIG enough.
Click to expand...
Click to collapse
I don't understand what you mean by "...I DON'T thnk you sig is BIG enough."??
---------- Post added at 12:16 PM ---------- Previous post was at 12:11 PM ----------
plainjane said:
Just for good measure, here's the link for Amon Ra that is already named correctly & has the correct components. You can find it here: http://db.tt/WP0beNa
I'll admit that I just scanned over the majority of the posting after the first post, so I'll read that over really quickly and if I can think of anything else I'll edit this post.
Also, does hboot scan and not find the file, or not scan for it at all?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Good question. I really don't know. When I boot into HBoot it just sits there. There are no messages of any kind, just the menu and above it (in red) instructions for using vol-up, vol-down and the power button. And, of course, at the top of the screen is the version information. And that's all it shows. So, I can't tell what it's doing.
The other thing I'm anxious about is that HBoot isn't scanning the card or can't find the file AND HBoot USB won't connect me to the PC. I'm assuming that, if that is the case, I'm dead in the water.
mjtaryan said:
I don't understand what you mean by "...I DON'T thnk you sig is BIG enough."??
---------- Post added at 12:16 PM ---------- Previous post was at 12:11 PM ----------
Good question. I really don't know. When I boot into HBoot it just sits there. There are no messages of any kind, just the menu and above it (in red) instructions for using vol-up, vol-down and the power button. And, of course, at the top of the screen is the version information. And that's all it shows. So, I can't tell what it's doing.
The other thing I'm anxious about is that HBoot isn't scanning the card or can't find the file AND HBoot USB won't connect me to the PC. I'm assuming that, if that is the case, I'm dead in the water.
Click to expand...
Click to collapse
Consider using a different SD card / Perhaps your SD is cooked ?!
So long you get to the bootloader you are fine
blandt said:
Consider using a different SD card / Perhaps your SD is cooked ?!
So long you get to the bootloader you are fine
Click to expand...
Click to collapse
My card seemed to work fine with regular apps before this mess. Would the sd card work with regular apps and be "cooked" when it comes to the bootloader?
plainjane said:
Just for good measure, here's the link for Amon Ra that is already named correctly & has the correct components. You can find it here: http://db.tt/WP0beNa
I'll admit that I just scanned over the majority of the posting after the first post, so I'll read that over really quickly and if I can think of anything else I'll edit this post.
Also, does hboot scan and not find the file, or not scan for it at all?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
I just tried the link you provided for the AmonRA using IE8. The link opened a blank page and the dowload never started. Will try Firefox.
Copied the URL to Firefox and it worked. Hopefully the checksums will be correct. Thanks.
---------- Post added at 07:50 PM ---------- Previous post was at 07:24 PM ----------
Another few questions before I try this.
What will happen if I run the RUU without first running the s-on tool?
What will happen if I run the s-on tool AFTER I run the RUU?
What will happen if I run the RUU without installing Amo_RA before hand (with or wihout having run the s-on tool?
I'm wondering because it's not like I'm returning the unit to Sprint or going to sell it. I just want to get it up and running again and was wondering, in case I can't get AmonRA installed, could I do the RUU, then run Unrevoked again without using the s-on tool. My thinking was along the lines that if I ran unrevoked again, it would also install Clockworkmod 2.6.0.1 recovery from which I switch to AmonRA. Of course there are other assumptions like being able to run the RUU exe. Which reminds me, how can I tell if HBoot USB is working and has made a successful connection with my pc?
Sorry about all the questions, but not asking the pertinent questions is what got me into this mess in the first place and I don't want to screw things up so that nothing at all can be done except replace the innards of the phone or get another one. Thanks to you all for your time and patience.
You don't need to Run S-On. The RUU should keep you rooted. After you run the RUU, then you want to flash the PC36IMG of Amon Ra and you should be all set.
HipKat said:
You don't need to Run S-On. The RUU should keep you rooted. After you run the RUU, then you want to flash the PC36IMG of Amon Ra and you should be all set.
Click to expand...
Click to collapse
OK. After running the RUU, can I run unrevoked again without running the s-on tool? (So that I have a recovery from which to install RA.)
Now, to repeat a couple of my questions in my last post.
How can I tell if HBoot USB is working and has successfully connected with my PC?
Can my sd card be cooked with respect to the PC36IMG files and yet the files I saved using some of my app appear to be fine?
Just though of another question. When my phone locked up USB debugging was on. So, am I correct in assuming that, even though it is in a bootloop, that HBoot will still see USB debugging as on? And when I go into HBoot USB, should the sd card show up on my PC like in Disk Drive mode when the phone was booted normally (before this problem)?
I have tried my best finding in forums etc and i have tried flashing any stock roms with Odin, factory reset, delete cache etc. i still get no luck on recovering my phone everything works fine expect for my internal storage with 0bytes (ihave dump a logcat text file) hope this helps i have tried flashing a pit file too
heartkeeper9 said:
I have tried my best finding in forums etc and i have tried flashing any stock roms with Odin, factory reset, delete cache etc. i still get no luck on recovering my phone everything works fine expect for my internal storage with 0bytes (ihave dump a logcat text file) hope this helps i have tried flashing a pit file too
Click to expand...
Click to collapse
Have you tried format internal memory? eg from Settings in phone or in CWM recovery? Id recommend doing it from CWM personally
bunglebp said:
Have you tried format internal memory? eg from Settings in phone or in CWM recovery? Id recommend doing it from CWM personally
Click to expand...
Click to collapse
Yeah Tired formatting no luck i guess my phone is good as dead
if no one could solve this
heartkeeper9 said:
Yeah Tired formatting no luck i guess my phone is good as dead
if no one could solve this
Click to expand...
Click to collapse
Strange would have though format in CWM would have worked,and ODIN didnt work either?
try flashing a stock ROM with Odin and using .PIT file for re-partitioning .....however ssh somebody mentioned the n7105 don't come or have .pit files anymore...I'm not sure..do the research and see...cause pit files tell the Odin how to format and layout the phone during the flashing process..
Sent from my GT-N7105 using Tapatalk 2
bunglebp said:
Strange would have though format in CWM would have worked,and ODIN didnt work either?
Click to expand...
Click to collapse
i tired odin and flash a stock rom and it still didn't work
dead soul said:
try flashing a stock ROM with Odin and using .PIT file for re-partitioning .....however ssh somebody mentioned the n7105 don't come or have .pit files anymore...I'm not sure..do the research and see...cause pit files tell the Odin how to format and layout the phone during the flashing process..
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
I have found a pit file (i guess) http://forum.xda-developers.com/showthread.php?t=2137008 so how do i use pit files with odin?
More info: Once i plug in my note 2 on a pc i cant transfer files to my external sd card it will just hang at transfering.
The strange thing is when am on my phone i go to | settings > Storage |my total space is 0.0b |Application 598mb| and when i hold my home button and i go to storage it shows my |system storage 817mb/10.22gb | sd card 4.72gb/7.41gb|
I remember before i had this problem i went to odin and i press nand erase all and a stock rom and flash them together and once i on my phone i cant pass through samsung logo and i when to samsung recovery( i hold the power button, home button and vol up button) and i went to press wipe data/factory reset and once i press reboot system now i got this error with no signal and internal storage 0.0 ... once i got this i panic and i went to flash wanamlite rom and i got my signal back and when i flash back a normal stock rom my signal will be lost again..
heartkeeper9 said:
i tired odin and flash a stock rom and it still didn't work
I have found a pit file (i guess) http://forum.xda-developers.com/showthread.php?t=2137008 so how do i use pit files with odin?
More info: Once i plug in my note 2 on a pc i cant transfer files to my external sd card it will just hang at transfering.
The strange thing is when am on my phone i go to | settings > Storage |my total space is 0.0b |Application 598mb| and when i hold my home button and i go to storage it shows my |system storage 817mb/10.22gb | sd card 4.72gb/7.41gb|
I remember before i had this problem i went to odin and i press nand erase all and a stock rom and flash them together and once i on my phone i cant pass through samsung logo and i when to samsung recovery( i hold the power button, home button and vol up button) and i went to press wipe data/factory reset and once i press reboot system now i got this error with no signal and internal storage 0.0 ... once i got this i panic and i went to flash wanamlite rom and i got my signal back and when i flash back a normal stock rom my signal will be lost again..
Click to expand...
Click to collapse
whenever you mess up your phone badly it's wise to go back to stock rather than flashing other ROMs cause other ROMs will be subjected to a messed up environment as they are generic and thus may complicate things further...Samsung ROMs on the other hand when used with.pit files can 're format / re partition the phone in a standard format.
answering your question on the pit file issue.... download Odin v 1.87 not the newer versions as sometimes they cause issues unless this version fails... put the .pit file in the pit section of Odin, place your stock ROM on the PDA section of Odin, you can add a csc as well I think it's related with regional settings of some sort..Google it I'm not sure but it's not very necessary, you can add a modem in the modem section also tick RE-PARTITION and tick reboot after Odin completes. however I'm just warning you...these are risky procedures proceed at your own risk
Sent from my GT-N7105 using Tapatalk 4
---------- Post added at 07:00 AM ---------- Previous post was at 06:59 AM ----------
oh forgot... then you need to put your phone in download mode....and start flashing.....
Sent from my GT-N7105 using Tapatalk 4
dead soul said:
whenever you mess up your phone badly it's wise to go back to stock rather than flashing other ROMs cause other ROMs will be subjected to a messed up environment as they are generic and thus may complicate things further...Samsung ROMs on the other hand when used with.pit files can 're format / re partition the phone in a standard format.
answering your question on the pit file issue.... download Odin v 1.87 not the newer versions as sometimes they cause issues unless this version fails... put the .pit file in the pit section of Odin, place your stock ROM on the PDA section of Odin, you can add a csc as well I think it's related with regional settings of some sort..Google it I'm not sure but it's not very necessary, you can add a modem in the modem section also tick RE-PARTITION and tick reboot after Odin completes. however I'm just warning you...these are risky procedures proceed at your own risk
Sent from my GT-N7105 using Tapatalk 4
---------- Post added at 07:00 AM ---------- Previous post was at 06:59 AM ----------
oh forgot... then you need to put your phone in download mode....and start flashing.....
Sent from my GT-N7105 using Tapatalk 4
Click to expand...
Click to collapse
Alright.. i change it to other ROMS because i need to have the signal i didnt know it would cause problem :crying: ===Testing it Right now===
Didn't work my phone internal storage is still at 0.0 with no signal unknown imei
heartkeeper9 said:
Alright.. i change it to other ROMS because i need to have the signal i didnt know it would cause problem :crying: ===Testing it Right now===
Didn't work my phone internal storage is still at 0.0 with no signal unknown imei
Click to expand...
Click to collapse
I've the same problem ! No IMEI, no baseband, no internal memory (sdcard). Only the external one is accesible. Over USB i can not copy any file to external sd and internal sd shows -104857600 Bytes. I've already tried to repartition with a pit file, flash stock with odin, flash tons of roms with cwm/twrp. Nothing is working.
pappschlumpf said:
I've the same problem ! No IMEI, no baseband, no internal memory (sdcard). Only the external one is accesible. Over USB i can not copy any file to external sd and internal sd shows -104857600 Bytes. I've already tried to repartition with a pit file, flash stock with odin, flash tons of roms with cwm/twrp. Nothing is working.
Click to expand...
Click to collapse
Haiii I dun think there is anyway to fix by our self :0 .this because I went down to Samsung shop and they fix it for me :0 gl
thus far this method will not work for any of your 4.4.2 ota bricks if you flashed the 4.4.2 modem on the mjb bootloader, the only way to fix those bricks is with a new emmc, motherboard or a new phone. Jtag won't save you this time the phone is now a glorious paperweight.
On 4.3 it will not work if you flashed a bootloader for the wrong model(E.G. AT&T I747 bootloader on a Bell I747M)
Read ALL of the first 2 posts,there is useful information and files in post 2.
This works for BOTH AT&T I747 and the I747M The files are located at the bottom of this post in the quote there are also more instructions and files/tools to download in the 2nd post of this thread.
First and foremost I take no credit for any of the work here, other people did most of the leg work. This is a DIRECT copy of -Mr.X-'s post from here namely page 17 that is being used with his permission, I have added to it after having to actually Unbrick my phone lastnight.
Thank you to all who contributed to the things that made this thread possible. -Mr.X-, Loserskater, upndwn4par, enewman17 and all who may have contributed to their work.
So what you have done is hard bricked your I747 AT&T or your I747M by whatever means. Most likely flashing something with a bootloader. Your phone won't do anything at all. You can't get to download mode or recovery mode. Perhaps this method will fix your phone? Give it a try what else do you have to loose? You might save some money on a Jtag?
I take no responsibility for anything that comes of you using this information.
IF YOU BRICKED YOUR PHONE BY FLASHING A DIFFERENT MODELS BOOTLOADER ON IT THIS METHOD WILL NOT WORK FOR YOU. ] YOU WILL NEED A JTAG.(THAT ALSO INCLUDES WHILE TRYING TO UNBRICK USING THIS METHOD.)
Be sure to get all the way to the bottom of the first 2 posts and PLEASE read everything before doing anything.
The Debrick Files are all the way at the bottom in the qoute below by -Mr. X- The Links Are Active.
Be sure to read the second post too. If you need clarification on anything please send me a PM
Here Is The Information You Came Here For HOW TO DEBRICK - Mr. X-'s post from This Is The Thread That The Below Quote Is From
Click below for the quote from where I got most of my information, do not just start doing things after you read the below quote, read the second post too.
-Mr. X- said:
How to UNBRICK:
Credit goes to these guys in this thread, I thought i was onto something origional, however after doign some searching i found others have figured this out for a different Variant of the S3
What you did:
Bricked downgrading the bootloader after upgrading to the 4.3 bootloader. The 4.3 bootloader appears to blow efuses that stop previous boot loaders from booting. Now your EMMC has non booting garbage on/in it. YAY! not...
What we are doing:
What we will be doing is writing the Partition layout (Partition.mbn) among other things to the SD so the phone will boot from it after it fails to boot from the EMMC. According to my research the CPU is designed to cascaded from one storage device to the other in the event of failure on the first device. This also means if your EMMC is smoked, you could technically run the whole rom and everything from the sd card, or that's my assumption.
What you need:
- A Micro SD card 16GB or larger. this will no work on smaller cards, i tried a 2GB 4 GB and 8GB for the sake of testing and it fails.
- A working Dump that includes the SBL1, SBL2, SBL3, aboot, TZ and RPM from a working device that matches your DEVICE MODLE ie: I747U or I747M If you wanto t create your own dump from a friends device the command in a rooted adb shell would be as follows but not exact depending where you want the dump file to end up being on your sd cards. "dd if=/dev/block/mmcblk0 of=/storage/sdcard1/debrick.bin bs=1024 count=81920" That is what I used my my co-workers CM 10.2 rom to get the 4.3 bootloader/debrick dump. NOTE: the device has to be rooted with a working busybox that supports the dd command.
- The ability to write the dump image to the micro sdcard.
What to do:
First:
I used "Win32DiskImage" Located here But you can also use dd to write the image to your sd card in Linux.
On Windows:
Open Win32DiskImage. Brows to the Debrick dump you have for your device. Select the drive letter if your micro sd in the drop-down, click write. Bam done.
On Linux:
For ease of example, and method. Open Gparted on your Linux install or live cd, check the dev your sd card is in the drop down menu. For example mine was /dev/sdb/ then use "dd if=/path/to/debrick/dump.img of=/dev/sdb/" This method also works. Be careful you are selecting the right dev or you will overwrite another disk on your system. YOU HAVE BEEN WARNED.
Second:
Put that SD card in your device insert the battery and if the SD card is written correctly with a proper debrick file. You can put a jig in the device and it will boot straight to download mode. If you dont have a jig hold Vol Down + Home + Power the device will boot to download. If it does not, either the image didn't write to the card properly ( I had to write it a few times with Win32DiskImager, DD worked fine the first try), the debrick dump is no good. Or your trying to debrink your 4.3 bootloader downgrade brick with a dump from 4.1.2 compatible bootloaders. this will not work the blown efuse will still prevent the bootloader from booting from the SD card as well as the EMMC. You will know pretty fast if it worked, as the device will vibe with the jig or it will vibe with the button combo almost immediately after being pressed and held.
Third:
Odin that thing back to the 4.3 stock rom. Yes you have to. You ain't getting 4.1.2 bootloaders back so dont think about odining that thing either. it wont boot, with out the SD with the 4.3 bootloader on it installed. Odining back is the best thing to do, it will get the right boot loader on your EMMC. If you are feeling adventurous and you had a custom recovery installed. You can boot to recover instead of download from the debricking SD boot, and install a 4.3 flashable zip bootloader there, if all goes well, you wont lose your data and the bootloader will be functional on the EMMC. Either method you choose after its done "flashing" what ever method. remove the sd and verify it boots on its own.
Note: a user stated that he flashed a bootloader via recovery and flashable zip, and he stated it appeared to flash the bootloadeerr to the micro sd. if this happens, ODIN back to the proper rom to get the internal EMMC rebuilt and booting.
If it does, do a dance or something.
Here is a flashable Bootloader for the i747M 4.3
Here is a debrick Dump from a I747M from the UEMK5 4.3 that works
Broken link I will update IF/AFTER it is fixed is an untested debrick dump for I747M from the DMF1 4.1.2 (WOuld be used to debrick a device that was bricked before or that has not updated to 4.3 bootloader only)
This one is for AT&T phones.
Here is a debrick file from the I747U on 4.3 thanks to theramsey3 I cannot test it obviously but it looks good in a hex editor. Should work for any one who has bricked the I747U by downgrading the boot loader.
Click to expand...
Click to collapse
The 16GB SD card is going to get formatted and partitioned if you have valuable data on it do a back up of it... You have been warned.MAKE SURE YOU USE THE CORRECT FILES FOR YOUR PHONE FAILURE TO DO SO WILL RESULT IN YOUR PHONE NEEDING TO BE JTAG'ED
YOU HAVE BEEN WARNED REPEATEDLY DO NOT FLASH THE WRONG BOOTLOADERS
Requirements(carrier specific)
For The AT&T SGH-I747
you will need two micro SD cards one 16GB (I read in a similar thread that the SD card must be 16GB no smaller and no larger if you get one bigger to work please let me know) and one 1GB or larger. You will need Odin v3.09(what I used), Samsung kies3 (you need the USB drivers it installs, a working custom recovery either CWM or TWRP(I prefer TWRP) and some patients.
For The SGH-I747M
you will need a 16GB micro SD card to put the debrick files on, Odin v3.09, Samsung kies3, the correct firmware TAR file for your phone and some patients.
If you need some of the things mentioned in the requirements please click under "Tools You May Need And File Downloads For AT&T and the SGH-I747M" .
You Need to Identify Your Phone Model Correctly and download the appropriate debrick file From the quote by -Mr. X- in the post above to place on your 16GB Micro SD Card with the Win32DiskImager (available for download below).
How to put the Debrick file on your SD card
Flash this Debrick file to your 16GB Micro SD card with Win32DiskImager (available below) by
*Insert your Micro SD card into your computer (backup any information you may have on it we are going to ERASE, FORMAT and PARTITION it.)
*Open win32DiskImager
*Navigate to the location where you downloaded the correct Debrick file
*Select your Debrick file by double clicking on it
*In the upper right corner of Win32DiskImager you should make sure that the drive letter assigned to your sd card is selected.
***Which ever drive that is listed will be erased, formatted, partitioned and have a small amount of data written to it***
*Click write in the bottom right hand side
You now have your debrick card
For the SGH-I747M
You need to put the Debrick SD card in the Phone, Pull and Replace the Battery, Put the Phone in download mode and flash your carrier specific 4.3 firmware (instructions and downloads Below) Via ODIN. Reboot the phone allow it to boot up, get in the phone, reboot without the debrick sd card in it, if it won't boot on its own see the link below.
If you are on AT&T
You will need to copy all of the files you are going to flash (you can download them below) onto your 1GB or larger SD card. You then Need Put your Debrick SD card in the Phone, Remove and reinstall the battery,Put the Phone in Recovery Mode (Must Be Either TWRP or CWM Instructions and TWRP Download Below), Dismount the Debrick SD card, Insert your SD card with your Bootloaders, ROM, kernel, and Modem into the Phone, Mount the SD card, Flash your files one at a time, wipe the cache and dalvik between each file, Once you are done reboot the system, You Might have to put the debrick SD back in and do another battery pull, boot up the phone, after you get in the phone reboot it without the Debrick SD card in. If it will not Boot on its own see the link below.
AFTER YOU FLASH IT MAY APPEAR THAT THE PHONE FREEZES ON THE BOOT SCREEN BE PATIENT 4.3 TAKES A LONG TIME TO BOOT THE FIRST TIME A ROM IS INSTALLED.
Tools You May Need And File Downloads For AT&T and the SGH-I747M
Here is a flashable Bootloader for the i747M 4.3
Here is a debrick Dump from a I747M from the UEMK5 4.3 that works
Broken link I will update IF/AFTER it is fixed is an untested debrick dump for I747M from the DMF1 4.1.2 (WOuld be used to debrick a device that was bricked before or that has not updated to 4.3 bootloader only)
Here is a debrick file from the I747U on 4.3 thanks to theramsey3 I cannot test it obviously but it looks good in a hex editor. Should work for any one who has bricked the I747U by downgrading the boot loader.
Debrick file mirrors use only if the links ^^^above don't work please.
AT&T debrick file Use this ONLY if you are on AT&T and after you have been on the 4.3 bootloaders
SGH - I747M debrick fileUse this ONLY if you have an SGH-I747M that was on the 4.3 bootloaders.
Win32 Disk Imager (used to write the debrick file to the sd)
Samsunk Kies
Go Here For Odin Pick Whichever One You Want To Use I Used 3.09
Do Not worry about downloading or installing root or KnoxRemover or SuperSU from the thread below yet focus on the task at hand you need to get your phone booting first then concern yourself with other goodies. You need TWRP and possibly ODIN if you want to take it from there. There are instructions in that thread on the installation of TWRP Skip the rest for now.
Go Here For TWRP Custom Recovery There Is Also A Link To ODIN There
Partition Wizard Free (There is a link with instructions below)
With AT&T you will have to download 4.3 bootloaders, a 4.3 rom, a 4.3 kernel and a 4.3 modem. I will post links to Threads where I retreived mine at and possibly a mirror download link with appropriate permissions.
AT&T info and link to roms, bootloader, kernel and modem I used to recover. Click below.
I got everything I flashed from here
Lately I have been running Looserskaters S3Rx, it is very stable and very functional Here is a link to it, I highly recommend it http://forum.xda-developers.com/showthread.php?t=2252932 I am not going to intentionally brick my phone again to test if you can flash this directly from a hardbrick so if anyone is successful or unsuccessful please let me know so I can update this thread.
Use this bootloader for the AT&T i747 ONLY https://www.dropbox.com/s/vbyeorrxapwrots/d2att_I747UCUEMJB_bootloader.zip the one in the tread where I got mine hasn't been working so use this bootloader it is the same one just hosted by a different person.
DO not use these files if you are not on AT&T you will simply be wasting your time by bricking your phone again. AND requiring a Jtag.
For the kernel I flashed the one in the middle d2att_Kernel_Stock_init.d_4.3_MJB_v1.0.zip which belongs to upndwn4par. I used loserskater's rom, bootloader and modem everything I used was linked in that thread. With proper permissions I would like to mirror those links as I know they work well.
This will have you rooted from jump Street. You might have to download supersu from the play store. I didn't have to. But YMMV.
Firmware downloadsFOR SGH-I747M USERS ONLY make sure you download the correct file. These are the TAR files that the I747M users can flash via the PDA button in ODIN
By clicking the button below to reveal links you acknowledge you are going to download the correct file.
WWW.Sammobile.COM (when I was still able to this was the site I downloaded my firmwares from)
If You Need Instructions For Download Mode, Recovery Mode or How to Flash TWRP Click Below
If You Need To Install TWRP Click Below For Instructions
If you don't already have a custom recovery installed on the phone.
* You will need to write your debrick file to your 16GB SD card and insert it into the phone,
* Perform a battery pull
*Reinsert the battery
*Access download mode
*Flash the TWRP file with ODIN
***Click Below For Instructions***
*First to access download mode (you should already have your Debrick SD card in your phone.)
*hold vol down, the home button and the power button for 4 seconds.
*The phone should vibrate.
*Release the power button followed by the remaining two.
*You may or may not have to have the USB cable plugged into your computer to do this? If it wont work with the cable plugged in unplug it and vise versa.
*When the warning screen pops up you need to press the correct button to continue.
***Follow the remaining Instructions EXACTLY***
*Now (if you havent done so yet) open ODIN on your pc (Kies MUST BE CLOSED)
*Click the PDA button, (In ODIN 3.09 it says AP)
*Navigate to where you downloaded the TWRP file,
*Select that file, Double Click To Select
### MAKE SURE that you do NOT have anything besides auto reboot checked ###
*** Once you are sure you have followed the direction ***EXACTLY*** click below to reveal the rest
Now That you are 100% Certain you have nothing more than auto reboot checked,
go to the bottom and click start.
it should write some files and say PASS and all threads finished (1 succeeded/ 0 failed).
you now have TWRP installed you can follow the rest of the guide.
If You Need Instructions To Access Download Mode Click Below.
*First to access download mode (you should already have your Debrick SD card in your phone and your battery removed.)
*Reinsert the battery
*Hold vol down, the home button and the power button for 4 seconds.
*The phone should vibrate.
*Release the power button followed by the remaining two.
*You may or may not have to have the USB cable plugged into your computer to do this? If it wont work with the cable plugged in unplug it and vise versa.
*When the warning screen pops up you need to press the correct button to continue.
If You Need Instructions To Access Recovery Mode Click Below
*First to access recovery mode (you should already have your Debrick SD card in your phone and the battery out.)
*Reinsert the battery
*Hold vol up, the home button and the power button for 4 seconds.
*The phone should vibrate.
*Release the power button followed by the remaining two.
*You may or may not have to have the USB cable plugged into your computer to do this? If it wont work with the cable plugged in unplug it and vise versa.
Your phone won't boot without the debrick SD card? Click below.
If you are on AT&T
When I first got mine booting again it would only boot with the micro SD card that has the .IMG file on it in the phone and only after a battery pull. What I did was boot back to recovery, remove my SD card and I had a spare SD card I used to flash the files with, I inserted it told TWRP to mount the new SD card, flashed the bootloader again and it seems to have cured my phones malfunctions. It now boots on its own like nothing ever happened. It may not happen like this for you???]
For the SGH-I747M
You have Two choices either flash the bootloader only via the 2 sd card method outlined for AT&T which requires flashing Custom recovery and VOIDING YOUR WARRANTYor you can reflash with odin and possibly try a factory reset in the samsung stock 3e recovery.
If your phone is booting now don't play with the bootloaders any more.
Make a nandroid backup of your phone if you are going to follow the instructions below.
You assume all risk associated with such...
Do you want to be able to use wifi, bluetooth or USB tethering? Click below. But read everything carefully before you do anything.
I contacted enewman17 and inquired about the link below \/ \/ \/ he advised me that it should be flashable via custom recovery to any AT&T I747 on 4.3 regardless of rom or kernel and possibly without root. He also said he thinks it may work on the I747M also.
If any I747M users flash it and are successful or unsuccessful please let me know so I can post whether this is effective for that as well.
http://forum.xda-developers.com/showpost.php?p=46804681&postcount=5 I flashed enewman17's tether hack with bluetooth enabled from there ^^^which allows wifi tethering through the roms native tethering app without the carrier getting their hands in your pocket.
Do you need instructions to install the above file? Click below
To install this you need to
*download this file^^^
*move it to your SD card
*put the SD card by k into the phone
*turn the phone off
*boot into recovery
*select install
*navigate to the location of the file ^^^
*select the correct file
*write the file to the phone
*clear the cache and wipe the dalvik
*reboot and enjoy, make sure you thank enewman17 for his fantastic work.
It works flawlessly for me buy your results may vary?
DO you want to get your 16GB micro SD card back to a use able state so you can store data on it again? Click below for details.
If you want to restore your sd card to a useable state after you get everything running again I used http://www.partitionwizard.com/free-partition-manager.html, After you install it and open it Insert your SD card into your computer and select the drive letter assigned to your SD card tell the partition wizard to delete all partitions then in the top left corner click apply. You now have a completly blank unformatted SD card. Now Insert it into your phone the phone will give you a notification that the sd card is unformatted and give you an option to format it. you now have a blank formatted SD card you can use again.
More to come in the near future.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Amazing! Thanks you!
This worked perfectly! I almost lost hope, but this has restored my faith in Android. So, does this mean that this is the end of Custom Roms that run versions <Android 4.3? That would be a shame...Is it the Android 4.3 update that caused all of this, or just Samsung's update?(Google or Samsung) I really loved custom roms of 4.1.2 and there were some things that I was able to do there that were ruined because of the update. It wasn't quite nice for Samsung to do this to those great devs.
theramsey3 said:
Put that SD card in your device insert the battery and if the SD card is written correctly with a proper debrick file. You can put a jig in the device and it will boot straight to download mode. If you dont have a jig hold Vol Down + Home + Power the device will boot to download. If it does not, either the image didn't write to the card properly ( I had to write it a few times with Win32DiskImager, DD worked fine the first try), the debrick dump is no good. Or your trying to debrink your 4.3 bootloader downgrade brick with a dump from 4.1.2 compatible bootloaders. this will not work the blown efuse will still prevent the bootloader from booting from the SD card as well as the EMMC. You will know pretty fast if it worked, as the device will vibe with the jig or it will vibe with the button combo almost immediately after being pressed and held.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This is interesting. If the other poster is correct, the phone's CPU will try to boot like the computer CPU, from boot device #1, to #2, #3, etc. In this case, the internal ROM is #1 device and the SD would be #2 root device.
If this is the case, then why do we need the SD card to hold the same bootloader? If the phone is totally hard-bricked, then it should just by-pass the internal ROM completely and boot through the SD directly. Then the phone should be able to boot from 4.1.2 or any older ROM.
So if the SD card has to have the same bootloader as the internal ROM, it means the phone still boots off the ROM bootloader, then continue to boot off the SD card since the internal ROM does not have the valid ROM to continue.
In my case, I have a really hard-bricked phone. I do not even know the original ROM version. I do not think its bootloader is locked. But the previous owner flashed with a wrong ROM from a different phone.
So I'd like to know from the folks who successfully fixed the hard-bricked phones with this method: Do you have to use the debrick.img from the existing bootloader, or you can use any generic debrick.img?
BaSingSe said:
This is interesting. If the other poster is correct, the phone's CPU will try to boot like the computer CPU, from boot device #1, to #2, #3, etc. In this case, the internal ROM is #1 device and the SD would be #2 root device.
If this is the case, then why do we need the SD card to hold the same bootloader? If the phone is totally hard-bricked, then it should just by-pass the internal ROM completely and boot through the SD directly. Then the phone should be able to boot from 4.1.2 or any older ROM.
So if the SD card has to have the same bootloader as the internal ROM, it means the phone still boots off the ROM bootloader, then continue to boot off the SD card since the internal ROM does not have the valid ROM to continue.
In my case, I have a really hard-bricked phone. I do not even know the original ROM version. I do not think its bootloader is locked. But the previous owner flashed with a wrong ROM from a different phone.
So I'd like to know from the folks who successfully fixed the hard-bricked phones with this method: Do you have to use the debrick.img from the existing bootloader, or you can use any generic debrick.img?
Click to expand...
Click to collapse
To be quite honest I have no clue if that would work? I am pretty sure if you left your debrick sd card in the phone you could do it like that but then you loose the ability to have expandable storage. Or atleast have to keep your boot.img sd card with you all the time incase you need to reboot the phone.
How this works is that: the phone can not boot from the internal bootloader/ROM. So it tries to boot off the SD card. The SD should not have to have the same 4.3 bootloader (technically). From the old/original thread (Sprint), even very old generic ROM should do it. But after you get to download mode, you'll have to flash the same 4.3 ROM (or whatever your last bootloader-locked ROM is). Or you get the same hard-bricked phone since the 4.3 bootloader can't be written over.
But again, I have a hard bricked phone someone flashed with a wrong S3 ROM, something like a GTI9300 ROM onto a Verison S3 phone. And I still can't get the phone to make any move, even after the following the exact instruction many times.
I really hope if someone DOES get this work with a really hard-bricked phone, provide some details, so we can understand this better.
A hard-bricked phone means, if you remove the battery and connect AC, the red light would turn on. Other than that, no boot, no sound, no vibrate, no download mode, no recovery. The phone would be totally dead, other than the red light.
theramsey3 said:
To be quite honest I have no clue if that would work? I am pretty sure if you left your debrick sd card in the phone you could do it like that but then you loose the ability to have expandable storage. Or atleast have to keep your boot.img sd card with you all the time incase you need to reboot the phone.
Click to expand...
Click to collapse
BaSingSe said:
How this works is that: the phone can not boot from the internal bootloader/ROM. So it tries to boot off the SD card. The SD should not have to have the same 4.3 bootloader (technically). From the old/original thread (Sprint), even very old generic ROM should do it. But after you get to download mode, you'll have to flash the same 4.3 ROM (or whatever your last bootloader-locked ROM is). Or you get the same hard-bricked phone since the 4.3 bootloader can't be written over.
But again, I have a hard bricked phone someone flashed with a wrong S3 ROM, something like a GTI9300 ROM onto a Verison S3 phone. And I still can't get the phone to make any move, even after the following the exact instruction many times.
I really hope if someone DOES get this work with a really hard-bricked phone, provide some details, so we can understand this better.
A hard-bricked phone means, if you remove the battery and connect AC, the red light would turn on. Other than that, no boot, no sound, no vibrate, no download mode, no recovery. The phone would be totally dead, other than the red light.
Click to expand...
Click to collapse
Mine was truley Hard Bricked The only response it would give is The red light with the charger plugged in and battery removed. also the QHUSB_DL message on the computer when connected. I recovered from it and created this How To Guide to try to help others.
Mine was recovered from the Debrick file that actually came off of my phone with the help of -Mr.X- to tell me the command lines to type to get the file extracted from my phone the day prior to me bricking my phone(which did not happen on purpose).
Never thought I would need it then 18 hours later I bricked my phone, and found out this is a Viable way to recover from it.
Perhaps your phone needs to be JTAG'ed?
theramsey3 said:
- A working Dump that includes the SBL1, SBL2, SBL3, aboot, TZ and RPM from a working device that matches your DEVICE MODLE ie: I747U or I747M If you wanto t create your own dump from a friends device the command in a rooted adb shell would be as follows but not exact depending where you want the dump file to end up being on your sd cards. "dd if=/dev/block/mmcblk0 of=/storage/sdcard1/debrick.bin bs=1024 count=81920" That is what I used my my co-workers CM 10.2 rom to get the 4.3 bootloader/debrick dump. NOTE: the device has to be rooted with a working busybox that supports the dd command.
Click to expand...
Click to collapse
What did you mean by stating that? So your phone was running CM 10.2?
BaSingSe said:
What did you mean by stating that? So your phone was running CM 10.2?
Click to expand...
Click to collapse
You're Qouting -Mr.X-'s post from a different thread. I didn't write that part of it. and explained such in the very begining of this thread.
Everything that is grayed out was written by him everything in white was written by me.
Hey man, how big are the Img files usually...do you mind uploading it? i am on i747m , accidentally flashed the AT&T 4.3 Bootloader (yea it was super late and i mis selected that file)
Can probably wait in a few weeks when i get a chance to meet a friend on 4.3 to get that dump
but if its not too big...would you mind uploading it?
---------- Post added at 06:12 AM ---------- Previous post was at 06:11 AM ----------
Hey man, how big are the Img files usually...do you mind uploading it? i am on i747m , accidentally flashed the AT&T 4.3 Bootloader (yea it was super late and i mis selected that file)
Can probably wait in a few weeks when i get a chance to meet a friend on 4.3 to get that dump
but if its not too big...would you mind uploading it?
FULLTIMEIT said:
Hey man, how big are the Img files usually...do you mind uploading it? i am on i747m , accidentally flashed the AT&T 4.3 Bootloader (yea it was super late and i mis selected that file)
Can probably wait in a few weeks when i get a chance to meet a friend on 4.3 to get that dump
but if its not too big...would you mind uploading it?
---------- Post added at 06:12 AM ---------- Previous post was at 06:11 AM ----------
Hey man, how big are the Img files usually...do you mind uploading it? i am on i747m , accidentally flashed the AT&T 4.3 Bootloader (yea it was super late and i mis selected that file)
Can probably wait in a few weeks when i get a chance to meet a friend on 4.3 to get that dump
but if its not too big...would you mind uploading it?
Click to expand...
Click to collapse
DO you mean these Debrick.img files that are in the first post?
-Mr. X- said:
Here is a debrick Dump from a I747M from the UEMK5 4.3 that works
Here is an untested debrick dump for I747M from the DMF1 4.1.2 (WOuld be used to debrick a device that was bricked before or that has not updated to 4.3 bootloader only)
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
DO you mean these Debrick.img files that are in the first post?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
o man my bad lol tired pretty hard to look for the link too...thanks!
Followed instructions still can not get phone into download mode.
I only have a 64 GB SD card could that be the problem?
Also I get no red light and no vibe.
When phone is plugged in Linux sees it as qhsusb_dload
Sent from my GT-N8013 using Tapatalk 4
dragonslayer73 said:
Followed instructions still can not get phone into download mode.
I only have a 64 GB SD card could that be the problem?
Also I get no red light and no vibe.
When phone is plugged in Linux sees it as qhsusb_dload
Sent from my GT-N8013 using Tapatalk 4
Click to expand...
Click to collapse
I could only get my phone to respond to button inputs to get into recovery if; I pulled the battery out with the USB cable unplugged, put the battery back in, plug the USB cable back in, then used the button combination. Otherwise it was a dead phone that did nothing.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Hi Op, tried to 4.3 file, didnt work for me , I can have red light on when plug in PC with no battery. using a 32 GB class 10 card , wrote the image a few times stil not getting the download mode...also tried to pull battery before combo thing...
Wanna try the 4.1.2 img..but the link is broken?
theramsey3 said:
I could only get my phone to respond to button inputs to get into recovery if I pulled the battery out with the USB cable unplugged put the battery back in then used the button combination. Otherwise it was a dead phone that did nothing.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Tried button combos still nothing plugged into PC and not plugged in
Sent from my GT-N8013 using Tapatalk 4
Read some of this thread which is where -Mr.X- gave credit to in his post. The op of that thread says you may have to try writing the file to the SD card several times and try booting to recovery or download mode several times to be successful.
There is also a post near the end of it that says the SD card must be exactly 16GB. Is that a fact? I don't know? The one I used was and the process worked for me.
If you guys are on AT&T make sure you are using the correct files.
If you guys have the Canadian I747M make sure you use the right file.
That link is messed up its not mine I will contact the rightful owner of it and request that he fix it if possible.
I did not create any part of this process I simply used some information that helped me Unbrick my phone with permission to write a how to guide. Perhaps the size of your SD cards are making a difference here??? I did observe when I was repartitioning my SD card to be able to use it for storage again that when you write the .IMG file to it, it creates several partitions on the SD card to look just like the internal storage of the phone. So if you're using a larger card than the phones internal storage perhaps that is conflicting with the process?
I was using my daily driver 16GB card that I normally keep in my phone for storage.
I am no developer just a concerned SGH-I747 owner. I became really concerned after I bricked my phone the night before last night at about 11pm I finally got it to boot again at about 8am.
This method has been proven to work on many different variants of the galaxy s3. Sprint, T mobile, the Canadian I747M, my phone (AT&T I747) and maybe others as well?
I personally debricked my phone with this method. The author of the post I quoted in the op who wrote all the files says he debricked an I747M with this method.
As with all things though perhaps it doesn't work in all situations?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have the i747 not i747m what debrick image should I use?
Sent from my GT-N8013 using Tapatalk 4
Unbricked and now hard bricked again
I used the debrick-SGH-I747U-CUEMJB3.img on my hard bricked (no signs of life except for red charging light when plugged into charger) At&T i747 that had the ota 4.3 update and was able to get into download mode ! from there I flashed TWRP through Odin and from there I flashed the I747UCUEMJ2 rom and it booted right up and was happy ! but then I went back into TWRP and decided to flash boot_CWM_I747MVLUEMK5 and when it was done flashing it said succeeded so I hit reboot then after that my phone was dead again and the sdcard debrick imgae no longer works..........any ideas?
dragonslayer73 said:
I have the i747 not i747m what debrick image should I use?
Sent from my GT-N8013 using Tapatalk 4
Click to expand...
Click to collapse
This is the one you should be using for an AT&T phone
-Mr. X- said:
Here is a debrick file from the I747U on 4.3 thanks to theramsey3 I cannot test it obviously but it looks good in a hex editor. Should work for any one who has bricked the I747U by downgrading the boot loader.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Team,
I have been researching for hours and am quite confused on which avenue to take to recover my soft brick. Information overload:crying:
Here is what happened and I will provide as much info as I can so please bare with me. After OTA upgrading to 4.3 and rooting successfully using the CF Auto Root. I was attempting to get my wifi hotspot working again using the Wifi mod and mucked around and installed the wrong mod (Odexed MK4). This rendered me stuck at the glowing samsung screen and it goes no further. Ive tried to factory reset, wiped cache and rebooted several times. Boots fine into recovery and download mode.
So after hours of searching, reading (its 3:50am est) and testing solutions I am no closer to a fix than I was when I started. I am currently waiting on a stock rooted rom to download in an attempt to flash back to stock but its taking hours to download.
However I just noticed, as I am typing this thread, that I can no longer
1. Mount as an usb external drive in recovery (TWRP v 2.3.1.0) I have Samsung drivers installed (1.5.14.0) so I get the indicator sound from windows that I sees the phone.
2. If I attempt to manually browse through my files using the recovery there are no files inside my internal sdcard directories.
/sdcard There are three directories there
/0 /obb /TWRP and the only folder that has files inside is the TWRP folder.
Im floundering here. I cannot even mount and install files on the phone to even attempt to flash back to stock. Can I get some fresh angles ladies and gents? I am at a loss.
signalsoldier said:
Team,
I have been researching for hours and am quite confused on which avenue to take to recover my soft brick. Information overload:crying:
Here is what happened and I will provide as much info as I can so please bare with me. After OTA upgrading to 4.3 and rooting successfully using the CF Auto Root. I was attempting to get my wifi hotspot working again using the Wifi mod and mucked around and installed the wrong mod (Odexed MK4). This rendered me stuck at the glowing samsung screen and it goes no further. Ive tried to factory reset, wiped cache and rebooted several times. Boots fine into recovery and download mode.
So after hours of searching, reading (its 3:50am est) and testing solutions I am no closer to a fix than I was when I started. I am currently waiting on a stock rooted rom to download in an attempt to flash back to stock but its taking hours to download.
However I just noticed, as I am typing this thread, that I can no longer
1. Mount as an usb external drive in recovery (TWRP v 2.3.1.0) I have Samsung drivers installed (1.5.14.0) so I get the indicator sound from windows that I sees the phone.
2. If I attempt to manually browse through my files using the recovery there are no files inside my internal sdcard directories.
/sdcard There are three directories there
/0 /obb /TWRP and the only folder that has files inside is the TWRP folder.
Im floundering here. I cannot even mount and install files on the phone to even attempt to flash back to stock. Can I get some fresh angles ladies and gents? I am at a loss.
Click to expand...
Click to collapse
Good morning (not really, I assume, sorry). So where are you at? Not sure what you mean that you cannot install files on the phone... Can you get into download mode and your computer recognizes the phone? If yes, can you do what you started to say - odin stock rooted? Or... if you can get into a custom recovery but your internal sd card has been wiped, can you put a stock rooted ROM in zip format on an external sd card, put that sd card into your phone, and flash in custom recovery?
erikalin said:
Good morning (not really, I assume, sorry). So where are you at? Not sure what you mean that you cannot install files on the phone... Can you get into download mode and your computer recognizes the phone? If yes, can you do what you started to say - odin stock rooted? Or... if you can get into a custom recovery but your internal sd card has been wiped, can you put a stock rooted ROM in zip format on an external sd card, put that sd card into your phone, and flash in custom recovery?
Click to expand...
Click to collapse
Here is the problem...the ROM I have is in zip format and based on what I have been reading I cannot install via Odin. Due to the fact that the phone refuses to mount as an external storage device I have no way of placing data on the the internal or external card. The only recourse I have now it to attempt to find an adapter to be able to mount this microsd card to my PC. I am out of town and have no idea where I could find one.....uggggh. Ill keep you posted.
signalsoldier said:
Here is the problem...the ROM I have is in zip format and based on what I have been reading I cannot install via Odin. Due to the fact that the phone refuses to mount as an external storage device I have no way of placing data on the the internal or external card. The only recourse I have now it to attempt to find an adapter to be able to mount this microsd card to my PC. I am out of town and have no idea where I could find one.....uggggh. Ill keep you posted.
Click to expand...
Click to collapse
Walmart. .. target. ... and most any office store you should be able to find one. http://forum.xda-developers.com/showthread.php?t=2538543 ... This thread gives you the stock unrooted rom in a flashable zip. To my knowledge no one has put out a stock rooted zip, but I will check around.
http://i.imgur.com/qrByUGN.jpg
signalsoldier said:
Team,
I have been researching for hours and am quite confused on which avenue to take to recover my soft brick. Information overload:crying:
Here is what happened and I will provide as much info as I can so please bare with me. After OTA upgrading to 4.3 and rooting successfully using the CF Auto Root. I was attempting to get my wifi hotspot working again using the Wifi mod and mucked around and installed the wrong mod (Odexed MK4). This rendered me stuck at the glowing samsung screen and it goes no further. Ive tried to factory reset, wiped cache and rebooted several times. Boots fine into recovery and download mode.
So after hours of searching, reading (its 3:50am est) and testing solutions I am no closer to a fix than I was when I started. I am currently waiting on a stock rooted rom to download in an attempt to flash back to stock but its taking hours to download.
However I just noticed, as I am typing this thread, that I can no longer
1. Mount as an usb external drive in recovery (TWRP v 2.3.1.0) I have Samsung drivers installed (1.5.14.0) so I get the indicator sound from windows that I sees the phone.
2. If I attempt to manually browse through my files using the recovery there are no files inside my internal sdcard directories.
/sdcard There are three directories there
/0 /obb /TWRP and the only folder that has files inside is the TWRP folder.
Im floundering here. I cannot even mount and install files on the phone to even attempt to flash back to stock. Can I get some fresh angles ladies and gents? I am at a loss.
Click to expand...
Click to collapse
You always have the Factory Reset/Wipe Data option inside your Recovery. But if that doesnt work use your downoad mode and Reset in KIES. but whatever you do, now that you have upgraded to 4.3 DO NOT try and dowgrade. it will cause a hard brick.
You did the ota update which put KNOX on your phone which is bad especially if you have a warranty. There is currently no way to get rid of it. I read a while ago the peoples phones has been getting bricked because they were trying stuff.
Anyway the only option I guess you have is to use your computer and reset your phone using kies. It will flash your phone back to stock in download mode.
Sent from my GT-N5110 using xda app-developers app
Ok team here is the latest
I was able to grab an adapter for my micro and I attempted to install the stock rom posted above located here
http://forum.xda-developers.com/showthread.php?t=2538543
That was a no-go and gave me the following error during installation.
assert failed: apply_rename_check("/system/app/ALLSHAREPLAY.apk","/system/app/ALLSHARECASTPLYER.apk","f90c86cf5423131dcd04f9a5b169df5f83ab9170" "81dbc5115c7c1121f70ada147f7297e192af4d38")
E: Error in /external_sd/cffb350e111c431bcd19eea86e0d0e6816950053.USER_L710_SPR_MD4_to_MK3_Update_FWD.zip
Click to expand...
Click to collapse
I attempted to connect to Kies 2.6.1 via download mode. Kies will timeout attempting to connect after about 8 to 10 mins.
"Device does not respond. Reboot to Resolved the Issue."
Click to expand...
Click to collapse
at this point I am still able to get into Recovery and Download. I really hosed this **** up
Here is the stock tar thread....You can use this to Odin back to stock. http://forum.xda-developers.com/showthread.php?t=2565972
Good luck!
http://i.imgur.com/qrByUGN.jpg
Thanks bro.....Ill download it and give it a try. I have nothing to lose at this point. Ill be back with praise or tears.
Problem resolved I was able to go back to stock using the link posted above by Bigpappa!!!
Thank you all so much for you help!
Congratulations
I am glad you were able to get use of your phone back. I wish I had seen this thread sooner. I was in exactly the same boat a couple of weeks ago, only mine lasted 3 days. I even bought a new GS4 when I thought my phone was dead. Took it back when someone finally helped me do what you did. It's a helpless feeling when you have been rooting and Romming for years safely. Sure seems like a sticky thread is in order for this specific issue. As you can see, I haven't got enough history for credibility on this forum since I rarely post. Oh well.
My phone is the Virgin Mobile edition of the Epic 4G Touch, with the GB28 Jelly Bean stock rooted Rom.
I was in the process of installing Cyanogenmod 11 via the instructions listed at the bottom of this page. I've done hours and hours of research over several days to make sure of the process. However, I did the noobiest of noob things. I committed an error that even the dumbest of the dumb wouldn't have done.
I forgot to copy the files to the SD card before flashing the EL26 Kernel.
Mock me. I will understand. I've been circling my room cursing out loud at my amazing stupidity and oversight. Nonetheless, I need your help. My current situation has me at a mismatched Kernel and Rom which, of course, won't boot.
Solution 1 [Failed]:
Flash back to the stock GB28 Kernel. I tried the One-Click off of rwilco12's repository, but I get an md5 sum mismatch error. I've downloaded the file multiple times, but it appears to be corrupted.
Solution 2 [Failed]:
Boot into the EL26 CWM recovery (which is successful!), then try mounting /data or /sdcard. Neither works, and my laptop will not recognize that an SD Card is connected.
Solution 3 [Failed]:
Plug SD Card into the printer (with a mirco SD card adapter), then use the printer to transfer files. Problem is, my printer is out of black ink, and I can't do anything without that ink cartridge. That's right, I can't read the SD Card without replacing the ink cartridge. Go f*** yourself Kodak.
And so, with a phone that cannot boot properly I need to transfer files to my SD card. I've read something about ADB, but I don't quite understand how it works. Is there a specific version of ADB I need to download? If so, where could I find it? Is there any other way to get the files onto my SD card so I can complete the process of upgrading to CM11?
Jin8 said:
My phone is the Virgin Mobile edition of the Epic 4G Touch, with the GB28 Jelly Bean stock rooted Rom.
I was in the process of installing Cyanogenmod 11 via the instructions listed at the bottom of this page. I've done hours and hours of research over several days to make sure of the process. However, I did the noobiest of noob things. I committed an error that even the dumbest of the dumb wouldn't have done.
I forgot to copy the files to the SD card before flashing the EL26 Kernel.
Mock me. I will understand. I've been circling my room cursing out loud at my amazing stupidity and oversight. Nonetheless, I need your help. My current situation has me at a mismatched Kernel and Rom which, of course, won't boot.
Solution 1 [Failed]:
Flash back to the stock GB28 Kernel. I tried the One-Click off of rwilco12's repository, but I get an md5 sum mismatch error. I've downloaded the file multiple times, but it appears to be corrupted.
Solution 2 [Failed]:
Boot into the EL26 CWM recovery (which is successful!), then try mounting /data or /sdcard. Neither works, and my laptop will not recognize that an SD Card is connected.
Solution 3 [Failed]:
Plug SD Card into the printer (with a mirco SD card adapter), then use the printer to transfer files. Problem is, my printer is out of black ink, and I can't do anything without that ink cartridge. That's right, I can't read the SD Card without replacing the ink cartridge. Go f*** yourself Kodak.
And so, with a phone that cannot boot properly I need to transfer files to my SD card. I've read something about ADB, but I don't quite understand how it works. Is there a specific version of ADB I need to download? If so, where could I find it? Is there any other way to get the files onto my SD card so I can complete the process of upgrading to CM11?
Click to expand...
Click to collapse
Try this if you can get into download mode. Install Odin on your laptop. Download the stock rooted restore for VMobile(GB28), tar version. Flash through pc Odin. Once you boot back up you should be able to copy the files you need top your sd card.
Since it appears all the download links for the VM recovery kernel are dead, you can use the GB27 kernel for the Sprint version. It won't cause any issues. To avoid the yellow triangle, flash the kernel through Mobile Odin. You can find Mobile Odin in the play store. Or, if you don't mind the yellow triangle warning on boot, you can flash the GB27 kernel with pc Odin. Once you have the recovery kernel flashed, you can reboot into recovery and continue your flashing.
By the way, you'll need to flash the Blasphemy kernel to get the proper recovery to flash any of the 4.4.2 roms. If you get the latest 4,.42 blasphemy kernel zip file, you can flash directly from the GB27 kernel recovery I linked. Then reboot into recovery, wipe and flash cm11 and gapps.
ODIN LINK http://www.rwilco12.com/Files/Misc Files/Odin3/Odin3 v3.07.zip
GB28 RESTORE LINK http://www.rwilco12.com/Files/Devic...-D710VMUB_GB28_1014481_Rooted_Restore.tar.md5
GB27 KERNEL LINK http://www.rwilco12.com/Files/Devic...s/JB/SXTP_Agat_GB27/SXTP_Agat_GB27-v0.3.0.tar
Blasphemy Kernel Thread LINK http://forum.xda-developers.com/showthread.php?t=2416620
Success!
Success! Your instructions worked flawlessly, and I managed to get Cyanogenmod 11 working perfectly.
You're an amazing person, riggerman0421. Don't ever let them tell you anything different. :laugh:
Just glad I could help. I've been in those types of situations before. Most of what I've learned about android has come from trial and error. The rest of it has been from the helpful people here and other forums, usually after one of those errors. We all learn from each other, and try to give back when we can.
If you or anybody needs it, here is the GB28 kernel with CWM recovery. I hope nobody has any issues with my posting it as all the old download links are broken.
https://www.dropbox.com/s/2f3h302khz8wwlz/SXTP_Agat_GB28-v0.5.0.tar
Thanks for the link! I've sent a message to rwilco12 to see if he'd like to add that to his repository. Whether or not he does, it's helpful to have that link for anyone searching the forums later. Thanks for taking the time to help and post.