Develop Bugs

Rooting broke my SD card

I followed the idiot-proof root guide—guess it's not so idiot-proof.
I got up to the point where I was installing the stock rooted ROM (33b. After everything is wiped, navigate to "install zip from sdcard," then select "choose zip from sdcard."). However, when I chose to install the zip with the ROM in it, the screen just flashed a quick message and dumped me back to the main ClockworkMod screen. Puzzled, I hit "reboot" to see if it had actually done anything.
It booted back into full Android, but now it's not recognizing my SD card, saying it needs to be formatted. When I try and format it, it does nothing. Now, recovery is also saying "E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (Invalid argument)". My SD card reader won't recognize my card either to the point that I can't even format it using my Mac.
Help!

SD format tool can fix many sd card issues:
http://www.sdcard.org/consumers/formatter/

Same thing happened to me.
You got two problems. One which the phone is messing up, and the other which more than likely you.
1) Mine wanted to format too. When I clicked it, nothing.
What I did: Restarted my phone and tried to format again and VIOLA! worked perfectly fine. Then I was able to use it again.
2) The problem you're doing wrong is: when you are renaming the file on your computer to "update.zip" you're literally making it "update.zip", so the phone will read it as if it's "update.zip.zip". Try renaming it to JUST "update" and try again. If not, then the other way around.
Hope that helps.

1 - I've tried that several times, here's to trying it once more... :/
2 - Recovery mode won't even recognize the SD card, so that's not an issue until I get my SD card working. But since I was able to boot into update.zip once, I doubt that's the issue.
EDIT: Nope, won't format from within Android.
arozer said:
Same thing happened to me.
You got two problems. One which the phone is messing up, and the other which more than likely you.
1) Mine wanted to format too. When I clicked it, nothing.
What I did: Restarted my phone and tried to format again and VIOLA! worked perfectly fine. Then I was able to use it again.
2) The problem you're doing wrong is: when you are renaming the file on your computer to "update.zip" you're literally making it "update.zip", so the phone will read it as if it's "update.zip.zip". Try renaming it to JUST "update" and try again. If not, then the other way around.
Hope that helps.
Click to expand...
Click to collapse

Same thing happened to me. I just renamed the update.zip shut phone down took out battery and SD put SD and battery in and good to go! Hope it works for u.
-------------------------------------
Sent via the XDA Tapatalk App

When you were in the initial recover screen did you hit update.zip. my first go I didn't you can't boot custom roms without the update.zip unless you used toast full root method. I know u probley
knew already but I'm a noon and took me a sec to figure it out.
-------------------------------------
Sent via the XDA Tapatalk App

Trying a couple of other things that aren't working either:
Code:
mount -t fat32 /dev/block/mmcblk0 /sdcard
mount: No such device
I tried to force it:
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
This made my computer recognize the SD card as an unformatted 32MB disk, which is obviously wrong.
So: should I get a new SD card or something?
Not going to help as the SD card isn't being recognized no matter what I do. Can't do anything with it.
xxxgeooegxxx said:
Same thing happened to me. I just renamed the update.zip shut phone down took out battery and SD put SD and battery in and good to go! Hope it works for u.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse

Any other suggestions? I'm just about ready to go get a new microSD...

redct said:
Any other suggestions? I'm just about ready to go get a new microSD...
Click to expand...
Click to collapse
try and get/install the OTA with the sd card fix. you don't need the card to do that, i don't think. then reboot. see if that fixes it.

redct said:
Any other suggestions? I'm just about ready to go get a new microSD...
Click to expand...
Click to collapse
Go check out the EVO 4G Android Development forum. There's a thread in there from someone who broke the SD & USB and almost bricked their device. It contains a fix for SD card issues.

Nope. OTA doesn't show up.
timothydonohue said:
try and get/install the OTA with the sd card fix. you don't need the card to do that, i don't think. then reboot. see if that fixes it.
Click to expand...
Click to collapse

Well, it seems to be the SD card. Bought a new one and it all works perfectly.

android broke my micro sd card too!!! I didn't update my rom or anything. It just hangs and i need to reset by pulling out the battery. And this is what happens!
Blackberry and windows mobile are more friendly to memory cards.

[Q] HELP! Desire won't boot up, Clockwork mod recovery accessible

This is my first post on this forum (figures I'll jump head in when I have a serious issue,ha?)
Ok here goes:
My Issue: HTC Desire is stuck on boot-up screen with Green HTC logo forever.
How it happened: I tried flashing a script using ROM Manager that was supposed to correct some local language settings, over my current rom.
Phone state before action: Worked beautifully using Modaco R8 RC1 ROM. Phone is of course rooted.
Why I can't solve it myself: Well, this is my first serious issue (well, I hope it's not serious, actually!) with phone, which i've had for about a week , so I'm relatively a n00b.
-- I can access Clockworkmod recovery. However, under NANDROID RESTORE there are no files. I have no idea why, because I DID a full nandroid backup before that install. I have a copy of all the IMG files of the last working setup on my windows machine hard drive, and my assumption is that maybe I accidentally moved the files to the hard drive after i did that backup, instead of copying them.
Now -
1) Can I somehow restore the phone to a working state without the nandroid backup, using some other function of the CW Mod recovery?
2) Can I somehow connect the phone via USB to the computer and get it to read the Micro SD card so I could maybe move the IMG files I have back to SD Card (using a mounting option)?
3) Anything else I could try?
If nothing else, please just calm me down if you can and let me know the phone is fixable and not bricked because I can access recovery?! That would at least help me go through the night...
last note: Before I flashed the zip, ROM Manager said my CW Mod version is 2.0.5.7. Within the recovery itself, it says the version is only 2.0.5.1. Don't know why that is , and if it is important.

owolfson said:
2) Can I somehow connect the phone via USB to the computer and get it to read the Micro SD card so I could maybe move the IMG files I have back to SD Card (using a mounting option)?
Click to expand...
Click to collapse
You could read the SD Card directly with your computer. If you don't already have a microSD/USB reader, they are very cheap and will prove very useful in situations exactly like this one.

cmstlist said:
You could read the SD Card directly with your computer. If you don't already have a microSD/USB reader, they are very cheap and will prove very useful in situations exactly like this one.
Click to expand...
Click to collapse
You are right! Indeed they are very cheap, but, unfortunately it's going to be a game of patience for me, because it's late evening right now and the shops are closed.
That's why I Was wondering if there's an option to mount SD using HBOOT or Recovery so I could end this ordeal tonight...
Anyway, The fact I could get into CM Recovery means the phone was not permanently damaged, right?

Right, if you can boot into recovery it's a good sign.
I have an N1, not a Desire, but in my CM recovery menu under "partitions menu" there is a "mount USB storage" option. Try that?
Alternately if you own any other phone with a microSD slot that can mount it via USB, it could be your makeshift USB reader.

I have had a similar issue before! What I actually ended up doing was pushing the files using ADB. Its quite easy and I'm sure you can find lots of threads on how to use it. Once the files are pushed to your SD card you can then restore it

FIXED!
AdamLC said:
I have had a similar issue before! What I actually ended up doing was pushing the files using ADB. Its quite easy and I'm sure you can find lots of threads on how to use it. Once the files are pushed to your SD card you can then restore it
Click to expand...
Click to collapse
Problem solved! And yeah, that's how I ended up doing it.. no micro SD card reader was needed..
I installed HTC Sync for the device drivers... then connected the Desire with the USB cable .. and worked out of the problem using ADB commands..
luckily, the guy whose update I installed that caused the problem has the same ROM as myself, so I installed his framework.jar file , and the machine is fine yet again!

Unable to Flash ROM, asking for help

Hello all, I recently purchased a new GS4 tmobile variant and have rooted it via Odin. SU shows up in the app section and TWRP installed successfully. My problem is when I attempt to flash a new rom i.e. GE 4.3, I almost immediately get a FAILED message and cant get it installed. I created a backup and have been able to restore so its not been an issue however I really cant figure out where im going wrong. The zip file is on my SD card but no luck... I'm just looking for some direction,
Thanks Andrew

th3h0ff said:
Hello all, I recently purchased a new GS4 tmobile variant and have rooted it via Odin. SU shows up in the app section and TWRP installed successfully. My problem is when I attempt to flash a new rom i.e. GE 4.3, I almost immediately get a FAILED message and cant get it installed. I created a backup and have been able to restore so its not been an issue however I really cant figure out where im going wrong. The zip file is on my SD card but no luck... I'm just looking for some direction,
Thanks Andrew
Click to expand...
Click to collapse
if you installed the rom correctly to the sd card, using twrp, you should be able to do your wipe data factory reset, wipe cash and dalvik, then press install from sd card, choose zip from sd card and install. make sure the rom is on the root of the sd card. when i first started flashing i was having a issue because my device was mounted incorrectly and the rom was not going to the root of my sd card. i started using a card reader that i can mount as a disk drive and send the rom to that. that solved my issues. also i seemed to be having issues with twrp on my device so i started using it and installed clockwork mod touch recovery and things started working then.Also be sure you are trying to install the correct rom for your device variant.i hope this helps some. good luck

realsis said:
if you installed the rom correctly to the sd card, using twrp, you should be able to do your wipe data factory reset, wipe cash and dalvik, then press install from sd card, choose zip from sd card and install. make sure the rom is on the root of the sd card. when i first started flashing i was having a issue because my device was mounted incorrectly and the rom was not going to the root of my sd card. i started using a card reader that i can mount as a disk drive and send the rom to that. that solved my issues. also i seemed to be having issues with twrp on my device so i started using it and installed clockwork mod touch recovery and things started working then.Also be sure you are trying to install the correct rom for your device variant.i hope this helps some. good luck
Click to expand...
Click to collapse
The .zip file is in a folder called ROMS i created on the root of the internal memory. Right now im stuck without anything as my backup seems to have failed now as well. I've flashed many roms before and have never run into this so im stumped! I've tried using both CWM and TWRP but both through a "failed" error. I downloaded both the rom package from the Tmo variant GS4 forum so i think they should be right...

th3h0ff said:
The .zip file is in a folder called ROMS i created on the root of the internal memory. Right now im stuck without anything as my backup seems to have failed now as well. I've flashed many roms before and have never run into this so im stumped! I've tried using both CWM and TWRP but both through a "failed" error. I downloaded both the rom package from the Tmo variant GS4 forum so i think they should be right...
Click to expand...
Click to collapse
I think ive found your issue. You said you placed the roms in a folder, try this, put the rom DIRECTLY on the root of your sd card, NOT in a folder. Give this a try and let me know. I know when flashing with my last device, the rom could not be placed into a folder, it had to be placed directly onto the root of the sd card. So try going back to the computer and mount as disk drive and directly place the rom onto the sd card, then just scroll down to find the rom while in recovery and this SHOULD work. I had a issue mounting as a disk drive so I just used a micro sd card reader and placed my sd card into the card reader, this automatically is recognized as a external disk drive and I'm able to place rom directly to root of sd card this way. When I tried hooking up my device directly to the computer it mounted as a media device and would not allow the rom to be placed correctly on the root. So that's how I got around that. So keeping these issues in mind, try again and place the rom directly to the sd and NOT in a folder and see if your able to successfully flash after that. After I did these things I was able to flash without any problems. Luke I said when I first flashed these were some issues I encountered that was prohibiting me from flashing correctly. Now I don't have any problems flashing. Please let me know if this works out and enables you to successfully flash. Hope this helps

Hard Bricked Galaxy S3 i747 AT&T PLEASE HELP?

So I never got the 4.3 OTA BUT I did install the UCUEMJB Bootloader, but not the modem to use the 4.3 Dandroid Rom, about all month before that I was happily on CM11, and loved it. I try Dandroid because I hate Touchwiz so much, but thought this might cure my want to switch ROMs all the time.
I tried to port the Moto X 4.2.2 Rom, and decided to flash it. The phone came on once with the Samsung logo, Went off, and usually it would vibrate and vibrate meaning something is wrong, this time it just went off and didn't vibrate at all.
It is hard bricked from my understanding, but I have no way of getting a JTAG Done, and I'm waiting on a JIG I ordered, but this is becoming too long without a phone. I bought 3 100K Ohm resistors, and tried the method here: http://forum.xda-developers.com/showthread.php?t=889128 and I can't seem to get it to work.
I tried the USB Debrick img for the JB Bootloader, but that didn't work neither. The battery is good, and works and everything, Just trying to rule out everything so many you can help me a little better.
Does anyone have any idea what to do? I can't afford a Riff box neither.. if I can get it fixed I'll just stick with one Rom this time, lol.
is there any way to JTAG without the Riff Box, or anything I can do? I'm willing to try anything at my power.
Thanks in Advance.

lemonboi5 said:
So I never got the 4.3 OTA BUT I did install the UCUEMJB Bootloader, but not the modem to use the 4.3 Dandroid Rom, about all month before that I was happily on CM11, and loved it. I try Dandroid because I hate Touchwiz so much, but thought this might cure my want to switch ROMs all the time.
Click to expand...
Click to collapse
You should try http://forum.xda-developers.com/showthread.php?t=2549068 you were on 4.3 these files are for 4.3
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

theramsey3 said:
You should try http://forum.xda-developers.com/showthread.php?t=2549068 you were on 4.3 these files are for 4.3
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply!
I have been looking at that all morning, so even if I flashed the Moto X Rom that was ported, I shouldn't need JTAG?
Also, let me get this straight.. I use WinDiskImager to put the img file on the SD card, via my SD card reader, and then Pull the battery, put in the SD card, put in the battery, and turn on the phone? because I've tried that and it doesn't work at all for me.. unless I'm missing something here, I'd love to know!

You are using a 16GB or larger card right?
You aren't trying to get the phone to power on just yet. Only trying to get to recovery mode so you can flash stock 4.3 stuff and get going again.
With that said...
It appears it is only about 70 percent successful. I have had reports from folks that said they had to write the .Img file several times in a row in their SD card slot in the computer to get it to work.
You may have to get a debrick file from someone running the same rom you were trying to flash.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

When you plug your phone into your PC, do you get a box that pops up and reads something like "can't load drivers QHSUSB DLOAD"?? If so, this is what I did. I followed the instructions in this thread:
http://forum.xda-developers.com/showthread.php?t=2581166
I used the AT&T image from this thread (I was on Paranoid Android 4.3, FYI):
http://forum.xda-developers.com/showthread.php?t=2345860
Worked just fine.
Now, the link in the post above me mentions Odin'ing back to 4.1 so you don't have to boot from your SD card anymore. I didn't do that. When mine booted, it booted into Recovery and I flashed my Paranoid Android 4.3 ROM and GApps. That worked fine and all my data was intact, but yeah, it meant That I'd have to boot from SD card every time. To get past that, I plugged my phone in, copied the AT&T .img file from my PC (note, I copied...I didn't image it. When you image it, it pulls files from the .img file and writes a partition containing them. You don't want to do that in this case) to a random internal SD card file folder on my phone. I had to do it that way cause that AT&T .img was too big to fit on my SD card imaged with the debrick boot files. I then I opened my file manager app on my phone and moved the .img file to the /SDCARD folder. From there I used the terminal emulator and followed the instructions from the link I posted first, typing
su
dd if=/sdcard/debrick.img of=/dev/block/mmcblk0
Took my SD card out. Restarted. It booted into recovery again, I flashed my PA 4.3 ROM and at that point I was able to boot without the SD card and didn't have to Odin back to an older version. Finally, I used the SD formatter here:
https://www.sdcard.org/downloads/formatter_4/
And formatted my SD card back to allow full usage. Copied all my old files and pics back on it and I was straight!

theramsey3 said:
You are using a 16GB or larger card right?
You aren't trying to get the phone to power on just yet. Only trying to get to recovery mode so you can flash stock 4.3 stuff and get going again.
With that said...
It appears it is only about 70 percent successful. I have had reports from folks that said they had to write the .Img file several times in a row in their SD card slot in the computer to get it to work.
You may have to get a debrick file from someone running the same rom you were trying to flash.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Its an 8GB Sandisk D: Is there a difference in the way it performs? I'm flat broke atm, but if someone can point me in direction of a cheap 16GB or bigger card, I'll go after it for sure.
Charles: said:
When you plug your phone into your PC, do you get a box that pops up and reads something like "can't load drivers QHSUSB DLOAD"?? If so, this is what I did. I followed the instructions in this thread:
http://forum.xda-developers.com/showthread.php?t=2581166
I used the AT&T image from this thread (I was on Paranoid Android 4.3, FYI):
http://forum.xda-developers.com/showthread.php?t=2345860
Worked just fine.
Now, the link in the post above me mentions Odin'ing back to 4.1 so you don't have to boot from your SD card anymore. I didn't do that. When mine booted, it booted into Recovery and I flashed my Paranoid Android 4.3 ROM and GApps. That worked fine and all my data was intact, but yeah, it meant That I'd have to boot from SD card every time. To get past that, I plugged my phone in, copied the AT&T .img file from my PC (note, I copied...I didn't image it. When you image it, it pulls files from the .img file and writes a partition containing them. You don't want to do that in this case) to a random internal SD card file folder on my phone. I had to do it that way cause that AT&T .img was too big to fit on my SD card imaged with the debrick boot files. I then I opened my file manager app on my phone and moved the .img file to the /SDCARD folder. From there I used the terminal emulator and followed the instructions from the link I posted first, typing
su
dd if=/sdcard/debrick.img of=/dev/block/mmcblk0
Took my SD card out. Restarted. It booted into recovery again, I flashed my PA 4.3 ROM and at that point I was able to boot without the SD card and didn't have to Odin back to an older version. Finally, I used the SD formatter here:
https://www.sdcard.org/downloads/formatter_4/
And formatted my SD card back to allow full usage. Copied all my old files and pics back on it and I was straight!
Click to expand...
Click to collapse
is your SD card bigger than 8GB? That's what I have, and I'll try all of this and report back
My phone doesn't turn on at all, So You mean to copy the IMG file to the SD Card? or the files from the IMG File to the SD card? I am not able to get into any file managers and ADB can't read my phone at all :/

First off, you need a card larger than 8gb. It has to be at least 16gb. Mine was 32gb.
Second, to get it to turn on at all, you need to use the disk imager listed in the thread I posted. WinDiskManager or whatever it's called. Grab the AT&T .img file from the second link (that's the one that worked for me...not sure it will for you) and save it somewhere on your PC. Open the disk imager and choose the AT&T .img file, then use the drop down and select your SD card (whatever letter your PC assigned it) and finally, click "write". That will image the files contained in the .img file to your SD card and partition it as bootable. Put the SD card in your phone, turn it on, and it should turn on to recovery at least. Once we get there, we can tackle moving the .img file to where it needs to be on your phone so you don't have to boot from the SD card anymore.

Yes exactly it is mandatory that your card MUST be 16 gb or bigger. What we are doing is mimicking the internal storage on the phone and tricking the phone into booting into recovery to fix what we messed up. Walmart has fairly cheap SD cards. They're cheaper than $50 to get a jtag and faster too.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Oh okay I get it now. Thanks for the explanation. I'll be on the look out for a 16GB.

Oh okay I get it now. Thanks for the explanation. I'll be on the look out for a 16GB. I found some cheap on Ebay for $10 when I get paid I'll get one! (Living check to check... lol) I also went ahead and bought a jig for $1.89, I'm asking around if any of my friends have an extra 16GB SD, most likely not though. Thanks for the replies!
BTW, My phone is like. Dead. Doesnt even power on or anything, but I do get the QHSUSB DLOAD thing, and if I plug it in without a battery I get a Red LED indicator, is that how you guys have explained previous phone states?

I never had it plugged in without the battery, but yes, when I plugged it into my PC, I got what you're getting. We should be able to get you back in business. Hurry up and get an SD card. Hell, go buy one, use it, then return it.

Charles: said:
I never had it plugged in without the battery, but yes, when I plugged it into my PC, I got what you're getting. We should be able to get you back in business. Hurry up and get an SD card. Hell, go buy one, use it, then return it.
Click to expand...
Click to collapse
Holy crap sir, I like the way you think.
Edit:
So I was able to get my sister to loan me the money to get one and return it lol.
So now I flash it with the AT&T Debrick Img...
pull the battery, insert SD, insert battery, try to turn it on?
Or am I missing something? lol
Going to pick it up now, just wanted to retrieve the "What now" steps ahead of time! Thanks everyone!

Charles: said:
I never had it plugged in without the battery, but yes, when I plugged it into my PC, I got what you're getting. We should be able to get you back in business. Hurry up and get an SD card. Hell, go buy one, use it, then return it.
Click to expand...
Click to collapse
I got an SD card, I tried the img's and it still wont turn on D:
Its a Class 10 Samsung 16GB Micro SD card, Currently keep trying to write the Debrick-SGH-i747U-CUEMJB3.img, and trying it out, still not working. Is that the OTA Bootloader? JB3? Or just JB? Or maybe its the J2 Bootloader I have with a JB3 Modem... forgive me lol.
Dead phone still.. I think I wanna cry lol
Edit:
In addition this is what I'm getting..
qualcomm hs-usb qdloader 9008 (COM4)
No idea what that means, but it shows up in Device Manager.
I've been trying and trying to flash this img and get it to come on, still not working

Did you image the SD card with this program?:
http://sourceforge.net/projects/win32diskimager/
After you image it, check your SD card in Windows Explorer and verify there are files on it. There should be quite a few.
If you did and the image you tried to flash didn't work, did you try the AT&T image that I linked to in my first post? This one?
http://d-h.st/iEy

Charles: said:
Did you image the SD card with this program?:
http://sourceforge.net/projects/win32diskimager/
After you image it, check your SD card in Windows Explorer and verify there are files on it. There should be quite a few.
If you did and the image you tried to flash didn't work, did you try the AT&T image that I linked to in my first post? This one?
http://d-h.st/iEy
Click to expand...
Click to collapse
The files are on the SD card in a folder called "image".. that doesn't sound good. I browsed for the .img and wrote it to the sd and everything D: I've done this a lot, any idea?

lemonboi5 said:
The files are on the SD card in a folder called "image".. that doesn't sound good. I browsed for the .img and wrote it to the sd and everything D: I've done this a lot, any idea?
Click to expand...
Click to collapse
Yes...that's correct. My SD card had numerous files in a folder named "Image", so it seems you're doing that portion correctly.
Did you try the AT&T image that I linked to? That one was named different from the one you referred to in your previous post.
Just to cover your bases, try both AT&T images that were linked to in this thread. If it's still not working...don't know what to tell you.

Charles: said:
Yes...that's correct. My SD card had numerous files in a folder named "Image", so it seems you're doing that portion correctly.
Did you try the AT&T image that I linked to? That one was named different from the one you referred to in your previous post.
Just to cover your bases, try both AT&T images that were linked to in this thread. If it's still not working...don't know what to tell you.
Click to expand...
Click to collapse
Yes, I've tried that one, and the one that theramseys uploaded, I just don't know if I'm doing something wrong here.
I stick in the sd card, and try to turn it on? it doesn't power on still.

So stuck here I've done the 3 button combo, and everything. it just wont turn on :/ Any more ideas? Should I just try it with linux? but then again how bad can Windiskimgr actually be?
I miss my phone so much! lol

I dunno, man. I flashed the image I posted, put the SD card in and it turned on. Just pressed the power button.

Charles: said:
I dunno, man. I flashed the image I posted, put the SD card in and it turned on. Just pressed the power button.
Click to expand...
Click to collapse
No tricks to it? I even tried using dd in linux, still nothing. If all fails I hope the jig works that I ordered. I was porting that Moto X rom from a Cyanogenmod 10.1.3 Base, but had swapped out mostly permissions and framework, I didn't touch the boot.img or anything like that.. I did kind of touch up on the updater-script, but still I don't see how that'd brick it, usually it'd give me a status7 or something if it didnt work, or even vibrate, turn on, then vibrate twice and restart, till I'd put it back into recovery, but with that 4.3 Rom I was throwing root issues, and every time I re-flashed it, I had to re isntall CWM
Yeah, just uncovered a new chapter of the story.. lol Hopefully we can work with this at all.
I tried to downgrade to a 4.2.2 Version from 4.3, and had a 4.3 Bootloader,
before all of this I was happily on the CM11 Rom, and should have stuck with it.. Curiosity killed the kitkat.

I need to unbrick my S 3!!! HELP!!!

So, yea, i bricked my S3... it happened when I was installing a custom ROM HOLD UPP!! It was a ROM that was for my device, and it wasn't caused by flashing the ROM. I formatted /system by accident (yea, I was using TWRP), but the strange thing was, it allowed me to boot once. before I actually went into the 'bricked' state. When I realized I formatted the /sdcard directory, where the custom ROM was stored (yea, call me an idiot), I rebooted so I can reboot to use the browser to download the ROM, but it stayed at this screen, except it didn't say "I9300"
d38v16rqg5mb6e.cloudfront (dot) net/wp-content/uploads/2015/07/Samsung-Galaxy-S31 (dot) jpg
Then I realized that TWRP had an MTP feature so I can transfer the ROM from my computer. So I transferred the ROM, flashed it, and yes, I did a full NANDroid backup, and stored it on my PC. After I clicked reboot, it got into the bricked state. the only signs of life, is when the LED turned red when I plug it in, but that only happens when I take the battery out first, and the phone gets warm when I plug it in.
So I need to know how to unbrick, without a 16 GB SD card. i only have a 2 GB SD. Is there a method to debrick using SD cards less than 16 GB? Is there a way to transfer the boot files to the phone? The phone, when I plug it in to the computer, the computer actually recognizes it, but as qhsusb_dload. what does that mean?
Yea I tried to be as specific as possible, but if you need any more info, ask.

Do you have an i9300? I ask because this forum is for the i747/i747m.

audit13 said:
Do you have an i9300? I ask because this forum is for the i747/i747m.
Click to expand...
Click to collapse
no its a I747M rogers.

It sounds like you found the debrick thread so I won't go into that. To answer your questions though, aside from that debrick method, the only other option is a jtag repair. There may be a shop near you that can do this, but if not you'll have to send it somewhere.
As for the size of the SD card for the debrick.img, I think I remember hearing once or twice that an 8gb card worked, but I still question if that was true. The idea behind it is the SD card is supposed to be the same size as the devices internal storage, so nothing less than 16gb will work. Can't hurt it to try of course, but don't get your hopes up is all.
QHSUSB_DLOAD = Qualcomm Hi Speed USB Download
It's a definite indicator that a device is hard bricked.
For future reference, I recommend NEVER wiping /system. When you flash a rom that's the first thing that happens anyway, so doing so manually has zero benefit, but all the risk of ending up with a device that has no O/S to boot into.
Sorry to hear that happened. Good luck with it though!
Sent from my SGH-T999 using Tapatalk

MhikeiMPC12 said:
So I need to know how to unbrick, without a 16 GB SD card. i only have a 2 GB SD. Is there a method to debrick using SD cards less than 16 GB?
Click to expand...
Click to collapse
Debricked mine just yesterday.
The procedure recommends to use a class 10 16GB micro-SD card only, but I managed with a class 4. I really think you ought to try with your 2GB card, as the debrick image is only 80MB. The worst that could happen is that it simply won't boot off the SD card.
In all my browsing on XDA I couldn't make sure to find a certified I747M debrick image, so I made one from my wife's rooted S3 (I747MVLUFNE6) following instructions from this post, and used it to boot mine (I747MVLUFNK2). I used Win32DiskImager (link to it is in the post) to get the image on my SD card. After I got it to boot, I downloaded the stock firmware for my device and used Odin to flash it. It worked just as they said.
I recommend you use Win32DiskImager to backup your SD before writing the debrick image : this will save you 1) copying the files manually and 2) looking for some tool (e.g. SD Formatter) to restore it to its former size (after writing the image, Windows will think the capacity of the SD card is 80MB!).
If you need a I747MVLUFNE6 or I747MVLUFNK2 debrick image, PM me.
Best of luck :good:

Hello,
First you will need to download correct ATT ROM, and when you install that ROM, you will need to select correct option in ODIN.
To me its look like, you get stuck in boot...
Are you ATT customer?
Let me know, I will post link for Original ATT ROM.

placroix74 said:
Debricked mine just yesterday.
The procedure recommends to use a class 10 16GB micro-SD card only, but I managed with a class 4. I really think you ought to try with your 2GB card, as the debrick image is only 80MB. The worst that could happen is that it simply won't boot off the SD card.
In all my browsing on XDA I couldn't make sure to find a certified I747M debrick image, so I made one from my wife's rooted S3 (I747MVLUFNE6) following instructions from this post, and used it to boot mine (I747MVLUFNK2). I used Win32DiskImager (link to it is in the post) to get the image on my SD card. After I got it to boot, I downloaded the stock firmware for my device and used Odin to flash it. It worked just as they said.
I recommend you use Win32DiskImager to backup your SD before writing the debrick image : this will save you 1) copying the files manually and 2) looking for some tool (e.g. SD Formatter) to restore it to its former size (after writing the image, Windows will think the capacity of the SD card is 80MB!).
If you need a I747MVLUFNE6 or I747MVLUFNK2 debrick image, PM me.
Best of luck :good:
Click to expand...
Click to collapse
I flashed the image through my firends phone instead of a sd card reader
so my friend has a kyrocera rise, so i inserted my sd inside, and it showed up the sd card in my pc, and flashed the img, but it didnt work. yea i think the theory about the sd card having to be the same size as the internal storage is true. im going to try writing the img using the reader instead. yea i already backed up the few files i had so that wasnt an issue!

andoridone said:
Hello,
First you will need to download correct ATT ROM, and when you install that ROM, you will need to select correct option in ODIN.
To me its look like, you get stuck in boot...
Are you ATT customer?
Let me know, I will post link for Original ATT ROM.
Click to expand...
Click to collapse
Not to be rude or anything, but i know what to do about soft bricks. I'm not in that situation. and i have a i747M. that means its Canadian. i also stated earlier it is from rogers. what does having to be a at&t customer have to do with anything, if this is a 2012 phone? The warranty is gone already.

DocHoliday77 said:
It sounds like you found the debrick thread so I won't go into that. To answer your questions though, aside from that debrick method, the only other option is a jtag repair. There may be a shop near you that can do this, but if not you'll have to send it somewhere.
As for the size of the SD card for the debrick.img, I think I remember hearing once or twice that an 8gb card worked, but I still question if that was true. The idea behind it is the SD card is supposed to be the same size as the devices internal storage, so nothing less than 16gb will work. Can't hurt it to try of course, but don't get your hopes up is all.
QHSUSB_DLOAD = Qualcomm Hi Speed USB Download
It's a definite indicator that a device is hard bricked.
For future reference, I recommend NEVER wiping /system. When you flash a rom that's the first thing that happens anyway, so doing so manually has zero benefit, but all the risk of ending up with a device that has no O/S to boot into.
Sorry to hear that happened. Good luck with it though!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yea i wiped /system by accident. but, it allowed me to reboot AFTER i wiped /system, which was weird, and i thought you were supposed to wipe /system. I wonder why the option to wipe /system is there anyway? Also, i flashed the rom already, so wouldnt the /system be written to the parition already? i thought there was a /boot partition..

I can get my hands on a 16 gb sd cad by sunday, but i was just looking for a unbrick method for a 2 gb sd card. Even if it means i have to keep the (2gb)sd in my pone in order for it to boot, i was looking for a temporary method to unbrick my phone.

MhikeiMPC12 said:
Yea i wiped /system by accident. but, it allowed me to reboot AFTER i wiped /system, which was weird, and i thought you were supposed to wipe /system. I wonder why the option to wipe /system is there anyway? Also, i flashed the rom already, so wouldnt the /system be written to the parition already? i thought there was a /boot partition..
Click to expand...
Click to collapse
It's a very common mistake. I see it happen way too often. I don't know where or why it got started, but some folks always recommend wiping /system. (Maybe it was required on a specific older device and they carried over to others).
tbh, I can't think of any situation where it's beneficial, so I don't know why is still included in recovery options.
Not sure why it would've booted that one time. I've seen that happen before, but only when flashing the firmware, not just a rom.
If the flash was successful after transferring the new rom via twrp, then you are correct that that the /system partition wouldn't be empty anymore. Maybe the rom was corrupted during the download or transfer?
The boot partition is actually where the kernel is located.
MhikeiMPC12 said:
I can get my hands on a 16 gb sd cad by sunday, but i was just looking for a unbrick method for a 2 gb sd card. Even if it means i have to keep the (2gb)sd in my pone in order for it to boot, i was looking for a temporary method to unbrick my phone.
Click to expand...
Click to collapse
Like I mentioned before, don't get your hopes up using the 2gb card. But by all means give it a shot! Can't hurt anything to try.
Someone mentioned the class of the SD is important. It is recommended to use a class 10, brand name card, but it's not required. I've seen class 4 cards work where class 10 cards failed. I believe it has to do with the transfer speed if the individual SD card. Some class 4/6 cards can actually read/write much faster. Just like some class 10 cards just don't perform as advertised.
Still, the most successful ones have been class 10's, which is why I think many consider it a requirement. Many lower class ones do often fail, but not all. Just something to keep in mind...
Sent from my SGH-T999 using Tapatalk

ok thanks. Did anyone report success using a 2 gb card?

Not that I've ever heard. But I doubt many have even tried. I've only seen a couple of reports that it worked with an 8gb card, but as I think I mentioned before, I'm not quite convinced that it was even true.
Sent from my SGH-T999 using Tapatalk

MhikeiMPC12 said:
Even if it means i have to keep the (2gb)sd in my pone in order for it to boot, i was looking for a temporary method to unbrick my phone.
Click to expand...
Click to collapse
Flashing stock firmware to my phone after booting off the SD card into download mode restored the phone's bootloader, but I knew that it was the bootloader I'd messed up.
The posts I've read about debricking this way seemed to mention that the phone would use the bootloader from the SD card, but would finish the booting process from the phone's storage.
If it's really /system you wiped, I wonder what your phone could finish booting from.

placroix74 said:
Flashing stock firmware to my phone after booting off the SD card into download mode restored the phone's bootloader, but I knew that it was the bootloader I'd messed up.
The posts I've read about debricking this way seemed to mention that the phone would use the bootloader from the SD card, but would finish the booting process from the phone's storage.
If it's really /system you wiped, I wonder what your phone could finish booting from.
Click to expand...
Click to collapse
i think it was because it was given a direct command to be booted into recovery, instead of being booted into system. :silly:

Im worried when i use the 16gb sd card, THAT wont debrick my phone! All i did was formal /system by accident, and it booted again AFTER i deleted system.

Also. I'm a noob at Ubuntu and all the "of=/dev/block/mmblk1". I thought it was as simple as
1. insert 16gb SD card and open Win32DiskImager
2. select the debrick.img and flash it
3. insert the SD in the phone and attempt to start it in download mode
BTW i heard that the CPU varient (exynos, quallcom) matters when u debrick the device. i have a SGH-I747M rogers so what CPU variant do i have?

MhikeiMPC12 said:
Also. I'm a noob at Ubuntu and all the "of=/dev/block/mmblk1". I thought it was as simple as
1. insert 16gb SD card and open Win32DiskImager
2. select the debrick.img and flash it
3. insert the SD in the phone and attempt to start it in download mode
BTW i heard that the CPU varient (exynos, quallcom) matters when u debrick the device. i have a SGH-I747M rogers so what CPU variant do i have?
Click to expand...
Click to collapse
You have a dual core Qualcomm processor. As long as you are using the correct debrick image, or correct bootloader, modem, or ROM when flashing the processor worries take care of themselves.
You could use either method to flash the img to the sdcard. Win32diskImager could be used on Windows PCs. dd is a command line tool used in Linux to do the same. Brasero would be a GUI tool used in Linux if using the command line concerns you. Using the GUI tools you need to be sure you are 'burning' the image to the media instead of copying the image file. The same would apply to making a bootable usb thumb drive to create a live Linux drive.

MhikeiMPC12 said:
Im worried when i use the 16gb sd card, THAT wont debrick my phone! All i did was formal /system by accident, and it booted again AFTER i deleted system.
Click to expand...
Click to collapse
Unfortunately, it sometimes does not work. More unfortunate, there is no way to know if it will without trying it.
Earlier though, you described a classic hard brick. Red light, QHSUSB_DLOAD.... this method has fixed bricks just like yours plenty of times. More have succeeded than failed. But as I said, it doesn't always work. I think it's definitely worth trying though.
I am convinced that 90% of the failures were due to two things: the sdcard and/or user error. (Mostly the SD though.)
When you do try this method, keep in mind that many people don't get it to work the first few tries. So if it doesn't work, don't give up right away. Try at least 3 or 4 times. This actually happened to me twice! I did everything exactly the same way but it failed until my 3rd or 4th try! No idea why, but I have experienced this firsthand.
Let us know if you have any other questions!
Sent from my SGH-T999 using Tapatalk

MhikeiMPC12 said:
Im worried when i use the 16gb sd card, THAT wont debrick my phone! All i did was formal /system by accident, and it booted again AFTER i deleted system.
Click to expand...
Click to collapse
The SD card won't debrick your phone on its own : it will only allow you to boot into download mode. Successfully flashing stock firmware (which contains a bootloader) from download mode will.
DocHoliday77 said:
When you do try this method, keep in mind that many people don't get it to work the first few tries. So if it doesn't work, don't give up right away. Try at least 3 or 4 times. This actually happened to me twice! I did everything exactly the same way but it failed until my 3rd or 4th try! No idea why, but I have experienced this firsthand.
Click to expand...
Click to collapse
Yeah, I saw those warnings, too. Maybe I was just lucky it worked on the 1st try...
BTW, where did you find a I747M debrick image to flash on your 2GB SD? The only ones I could find were for I747 (US)...