Related
First: Yes I've looked at other threads my problem is slightly different and, yes it is my fault for trying stuff beyond my level of skill but I know XDA members are helpful so I'm trying my luck.
Problem: I rooted the device (HTC Desire) and was running LeeDrOiD V2.2 until I came across the new senseHD ROMs for the HTC Desire and this is where the problems started. In short, I tried to upgrade to the SenseHD ROM and in the process wiped my SD and phone memory. the device can still boot into recovery but it gets the following message when trying to access the SD;
E:Can't mount /dev/block/mmcblk0p0 (or /dev/block/mmcblk0p1)
(Invalid argument)
E:Can't mount /sdcard
The card is 2GB and reads fine on my windows machine. I've tried formatting and placing ETX3 and ETX2 partitions, I've also tried just copying all the old data that was on the SD before I started playing but the device just hangs with a black screen reading "android". The trouble is that all the solutions I have come across for similar problems are solved from "inside" the ROM either through ROM manager or by changing settings. Obviously these are not options for me.
I would like to install the senseHD ROM (RCMixHD v0.11) (or anything at this point) so please could you help to fix this and have a working phone again.
please please please help out if you can, I'll be eternally grateful for any advice.
many thanks in advance!
SOLUTION
I managed to fix it in the end. I got a hold of another SD card from a friend, put a ROM on it and booted up the phone. Made sure the phone could boot up without the borrowed SD card. Then I took the original SD card and deleted all the partitions (DID NOT FORMAT) in windows using (MiniTool Partition Wizard) placed it back in the phone and booted up using the ROM that had just been installed.
In the phone settings go to Phone and SD storage, mount the SD card (don know why it manages to mount here) and then format it.
Now the SD card is fixed!
You could try repartitioning the sdcard from recovery.
good luck.
I had the same problem. I needed to update my version of Clockwork Recovery. I used the ROM Manager to install the latest version. Now its working for me.
Thanks I managed to fix it in the end. I got a hold of another SD card from a friend, put a ROM on it and booted up the phone. Made sure the phone could boot up without the borrowed SD card. Then I took the original SD card and deleted all the partitions (DID NOT FORMAT) in windows using (MiniTool Partition Wizard) placed it back in the phone and booted up using the ROM that had just been installed.
In the phone settings go to Phone and SD storage, mount the SD card (don know why it manages to mount here) and then format it.
Now the SD card is fixed!
I have the same problem you did however my desire will not mount any sdcard I put in it. Can anyone help?
NYRican said:
I have the same problem you did however my desire will not mount any sdcard I put in it. Can anyone help?
Click to expand...
Click to collapse
same here... happened yesterday.. and i am searching my guts out to fix it since
OrionDelgado said:
same here... happened yesterday.. and i am searching my guts out to fix it since
Click to expand...
Click to collapse
I'm also in the same boat and the fastboot command to re-enable the SD card didn't work for me.
Background:
I thought I would try to install stock 4.3 leak for i747, forgetting that I had i747M! I totally HARD bricked my phone.. not a whimper, except the familiar recognition of a new device type on windows.. but no charging, booting, or even response.
I turned to the 'Unbrick via SD Card' thread from the Sprint S3 forum:
http://forum.xda-developers.com/showthread.php?p=43305728
I managed to find a debrick.img for the i747M. With that in hand, first using the method utilizing Cygwin, I was able to boot into Download Mode. Hurray! I downloaded the Stock 4.1.2 i747M Bell Image, and fully restored the phone using ODIN.
All seemed great until I removed the debrick SD card, and rebooted. Dead again. With the SD card in, I can reboot. I have tried restoring multiple times, writing a new PIT from another i747M, reinstalling the bootloader... nothing. If the SD Card isn'tin the phone, it's bricked. I am happy my phone is up and running, but it's nasty not having my 16 Gig SD card available, and also, I really need to ensure the battery doesn't die! Can anyone suggest what might be going wrong? Shouldn't I simply need to flash the stock image, and be good!?!
Thanks!
Can you get into Download / recovery mode w/o the SD card ?
Did you try the stock image from this thread ? :
http://forum.xda-developers.com/showthread.php?t=2363882
dwolder said:
Background:
I thought I would try to install stock 4.3 leak for i747, forgetting that I had i747M! I totally HARD bricked my phone.. not a whimper, except the familiar recognition of a new device type on windows.. but no charging, booting, or even response.
I turned to the 'Unbrick via SD Card' thread from the Sprint S3 forum:
http://forum.xda-developers.com/showthread.php?p=43305728
I managed to find a debrick.img for the i747M. With that in hand, first using the method utilizing Cygwin, I was able to boot into Download Mode. Hurray! I downloaded the Stock 4.1.2 i747M Bell Image, and fully restored the phone using ODIN.
All seemed great until I removed the debrick SD card, and rebooted. Dead again. With the SD card in, I can reboot. I have tried restoring multiple times, writing a new PIT from another i747M, reinstalling the bootloader... nothing. If the SD Card isn'tin the phone, it's bricked. I am happy my phone is up and running, but it's nasty not having my 16 Gig SD card available, and also, I really need to ensure the battery doesn't die! Can anyone suggest what might be going wrong? Shouldn't I simply need to flash the stock image, and be good!?!
Thanks!
Click to expand...
Click to collapse
the.teejster said:
Can you get into Download / recovery mode w/o the SD card ?
Click to expand...
Click to collapse
Unfortunately, no. Hard Bricked without the SD card
the.teejster said:
Did you try the stock image from this thread ? :
http://forum.xda-developers.com/showthread.php?t=2363882
Click to expand...
Click to collapse
I hadn't tried this one. I used the one from SAMMOBILE. I'll try this one right now.
Thanks!
dwolder said:
Unfortunately, no. Hard Bricked without the SD card
I hadn't tried this one. I used the one from SAMMOBILE. I'll try this one right now.
Thanks!
Click to expand...
Click to collapse
If you want to maintain ROOT access be sure to grab the root.zip and flash AFTER you flash the image and BEFORE you reboot.
As an FYI, the 16Gig Bell image worked great for me.
the.teejster said:
If you want to maintain ROOT access be sure to grab the root.zip and flash AFTER you flash the image and BEFORE you reboot.
As an FYI, the 16Gig Bell image worked great for me.
Click to expand...
Click to collapse
Tried everything.. flashing the recommended version above from internal disk won't work. Flashes of Odin compatible versions complete, and still need the SD card in. I have rooted, installed Clockwork recovery, tried to install the firmware from internal drive... it would fail. Install from ODIN (Samsung Recovery) it succeeds, but won't boot without the SD Card in. (Familar QD Loader). I just don't get it. I might have to go to ADB level, and see if I can have any success there?
dwolder said:
Tried everything.. flashing the recommended version above from internal disk won't work. Flashes of Odin compatible versions complete, and still need the SD card in. I have rooted, installed Clockwork recovery, tried to install the firmware from internal drive... it would fail. Install from ODIN (Samsung Recovery) it succeeds, but won't boot without the SD Card in. (Familar QD Loader). I just don't get it. I might have to go to ADB level, and see if I can have any success there?
Click to expand...
Click to collapse
You my friend as you said are HardBricked, need to be flashed by jtag. I tried on a friends to use a debrick image to fix, but in the end I have to use the riff box to fix it. You may also have luck with this http://forum.xda-developers.com/showthread.php?t=2439367 but remember to replace the file/files with the proper ones for YOUR phone.
Good Luck
dwolder said:
Background:
I thought I would try to install stock 4.3 leak for i747, forgetting that I had i747M! I totally HARD bricked my phone.. not a whimper, except the familiar recognition of a new device type on windows.. but no charging, booting, or even response.
I turned to the 'Unbrick via SD Card' thread from the Sprint S3 forum:
http://forum.xda-developers.com/showthread.php?p=43305728
I managed to find a debrick.img for the i747M. With that in hand, first using the method utilizing Cygwin, I was able to boot into Download Mode. Hurray! I downloaded the Stock 4.1.2 i747M Bell Image, and fully restored the phone using ODIN.
All seemed great until I removed the debrick SD card, and rebooted. Dead again. With the SD card in, I can reboot. I have tried restoring multiple times, writing a new PIT from another i747M, reinstalling the bootloader... nothing. If the SD Card isn'tin the phone, it's bricked. I am happy my phone is up and running, but it's nasty not having my 16 Gig SD card available, and also, I really need to ensure the battery doesn't die! Can anyone suggest what might be going wrong? Shouldn't I simply need to flash the stock image, and be good!?!
Thanks!
Click to expand...
Click to collapse
I had the exact same issue, took all the same steps you did, and had all the same frustrations. The last thing I tried though was to dd the debrick img to the internal memory of the phone via a terminal session running from my sdcard booted phone. figured I had nothing left to lose. It worked. I got the phone booted to download mode without the card in and restored my phone. I will add that I am no expert so this might be the worst idea ever. but my phone has been running since the 31st.
Bradkirk said:
I had the exact same issue, took all the same steps you did, and had all the same frustrations. The last thing I tried though was to dd the debrick img to the internal memory of the phone via a terminal session running from my sdcard booted phone. figured I had nothing left to lose. It worked. I got the phone booted to download mode without the card in and restored my phone. I will add that I am no expert so this might be the worst idea ever. but my phone has been running since the 31st.
Click to expand...
Click to collapse
How did you make the connection to the phone memory.. ADB? I brought mine to the shop. They said two groups tried to fix it and couldn't. I am going to keep trying (glutton for punishment).
dwolder said:
How did you make the connection to the phone memory.. ADB? I brought mine to the shop. They said two groups tried to fix it and couldn't. I am going to keep trying (glutton for punishment).
Click to expand...
Click to collapse
forgive me, I'm no expert but I'll try to list what I did.
booted the phone via SD card and restored a backup so that I was running a rooted custom 4.3 ROM. I also had the terminal emulator program installed on the phone. so everything worked great at this point except I needed the SD card in the phone to boot.
the image I used for the SD card boot is a 16GB (version not file size) Bell I747M dump of a stock phone, called debrick.img. Sorry I cant remember where I got it but it was here on XDA. To get it on the SD card to begin with I used the terminal emulator on my old i9000(m) and the dd command.
So, to reverse the process I opened the terminal emulator on my SD booted, running I747M. typed: su <enter> to give the app superuser access (allowed root access when prompted) then changed to the directory on the sd card containing the debrick.img file just to save me typing the full path in the command. the internal SD of my phone is found at /dev/block/mmcblk0 as opposed to mmcblk1 for the external SD.
so , moment of truth. I used; dd if=debrick.img of=/dev/block/mmcblk0 <enter> This was the part I mentioned could be the worst idea ever because from what I think I understand, you are writing directly to the boot partition of the SD and could completely screw up all the partitions and whatnot.
after that, crossed my fingers and turned the phone off, pulled the SD card out and luckily booted right up into download mode. Used Odin to get back up and running. Hope that helps or at least doesnt make anything worse for you.
help me please
hey friend, you could climb the debricked.img of i747m to a download server or give me the link where obtubiste, I'm going through a hard brick on the terminal for the same reasons as you, please appreciate what you really so
aisakblack said:
hey friend, you could climb the debricked.img of i747m to a download server or give me the link where obtubiste, I'm going through a hard brick on the terminal for the same reasons as you, please appreciate what you really so
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2345860&page=18 2nd post down has the link I used. Reading the whole thread would be a good idea.
It worked for me
Bradkirk said:
forgive me, I'm no expert but I'll try to list what I did.
booted the phone via SD card and restored a backup so that I was running a rooted custom 4.3 ROM. I also had the terminal emulator program installed on the phone. so everything worked great at this point except I needed the SD card in the phone to boot.
the image I used for the SD card boot is a 16GB (version not file size) Bell I747M dump of a stock phone, called debrick.img. Sorry I cant remember where I got it but it was here on XDA. To get it on the SD card to begin with I used the terminal emulator on my old i9000(m) and the dd command.
So, to reverse the process I opened the terminal emulator on my SD booted, running I747M. typed: su <enter> to give the app superuser access (allowed root access when prompted) then changed to the directory on the sd card containing the debrick.img file just to save me typing the full path in the command. the internal SD of my phone is found at /dev/block/mmcblk0 as opposed to mmcblk1 for the external SD.
so , moment of truth. I used; dd if=debrick.img of=/dev/block/mmcblk0 <enter> This was the part I mentioned could be the worst idea ever because from what I think I understand, you are writing directly to the boot partition of the SD and could completely screw up all the partitions and whatnot.
after that, crossed my fingers and turned the phone off, pulled the SD card out and luckily booted right up into download mode. Used Odin to get back up and running. Hope that helps or at least doesnt make anything worse for you.
Click to expand...
Click to collapse
Your method worked for me. Very clever and thank you. I did have to do some modifications of the partitions to fit the 145MB debrick.img file. I also had to mount it as a 2nd partition from the sdcard. Once, was in dowload mode without original debrick sdcard, I flashed the clockworkmod recovery then restored one of my previous back thus retaining root.
Mind sharing the i747m Debrick.img?
Seems like the link from the post you linkd us to is not working, clicking download does nothing :/ currently have a bricked Bell S3 and need a debrick.img
Bradkirk said:
http://forum.xda-developers.com/showthread.php?t=2345860&page=18 2nd post down has the link I used. Reading the whole thread would be a good idea.
Click to expand...
Click to collapse
Same for me, I really need that link to be working:good:
I have an LG Optimus Pro E980 with 4.4.2, rooted with towel root.
In an attempt to install TWRP recovery today I lost access to my external sd card. Not sure what I did but earlier today I could view, copy files or delete files to my sd card from my phone or from my computer when hooked with usb and media transfer.
I had a lot of trial and error trying to get a custom recovery installed on my phone and in the process I noticed my sd card quit working.
I have rebooted, removed it, reformatted (from my computer) and still nothing changes. ES File Manager sees it (I think) but when I try to create a folder on the external sd it just says it can't. It works when I put it in another android phone so I don't think the sd card is the problem. I also tried the app on google sdfix that makes kitkat have the settings to write to the sd card. Still didn't fix my problem. It will mount or erase from the settings menu. I don't see a format or unmount option at all.
I would like to flash a new copy of 4.4.2 to my phone but I can't find instructions of how to do this that I understand . I figure this will fix my problem and I was wanting to do a wipe and clean install anyway.
Can someone please advise me? TY
Certain twrp can't access the SD disk. I know this because I have installed twrp 2.8 and I notice immediately that it can't access the external SD disk, as normally be in the directory/storage/sddisk1. Don*t ask me which twrp to use because I don't know. I've heard that some twrp can access the external SD disk and some can't without some modification. Try this one
http://forum.xda-developers.com/showthread.php?t=3144369
Its been modified, so it should work without any problem. BTW, as I have said on your other topic, why are you trying to reinstall the stock KitKat that you already have? If you have issues, a factory reset, as you've already figure out, should take care of thing, unless you've erase system files. Don't take the process of flashing tot files lightly, because if one of many things go wrong, you may wish you have never know how to flash the tot file.
hawkwind212 said:
Certain twrp can't access the SD disk. I know this because I have installed twrp 2.8 and I notice immediately that it can't access the external SD disk, as normally be in the directory/storage/sddisk1. Don*t ask me which twrp to use because I don't know. I've heard that some twrp can access the external SD disk and some can't without some modification. Try this one
http://forum.xda-developers.com/showthread.php?t=3144369
Its been modified, so it should work without any problem. BTW, as I have said on your other topic, why are you trying to reinstall the stock KitKat that you already have? If you have issues, a factory reset, as you've already figure out, should take care of thing, unless you've erase system files. Don't take the process of flashing tot files lightly, because if one of many things go wrong, you may wish you have never know how to flash the tot file.
Click to expand...
Click to collapse
I just responded to your other post.
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)...
Huston, we have a problem. Since day 1.
(& please refrain from mentioning warranty, not an option)
I never had access to my microSd card.
I thought it was a stock Rom problem, so I waited until root, maybe with another rom, the problem would disappear.
Sadly, no.
The thing is, a 200 MB partition always mounts as my SD card.
I don't have a clue on how to solve it.
Any suggestions?
Thanks in advance! :fingers-crossed:
The bastard partition is the one mentioned below, and below that one, the untitled, is my 64GB micro Sd card.
I used Diskinfo app to get the data.
* SD card (EFI System Partition) [mmcblk1p1] (/mnt/media_rw/sdcard1, /storage/sdcard1) [vfat]
Used: 3.1 MB, Free: 196 MB, Total space: 200 MB
* Untitled [mmcblk1p2] Not mounted
If interested, the attached pdf has the full list of the internal storage (MMC) partitions
XLR8_2K said:
Huston, we have a problem. Since day 1.
Click to expand...
Click to collapse
hi,
what device do you have?
before you answer elephone p8000, i mean which version as in which 4g bands does it have access to? normal or version b?
is the phone working operation?
what current rom are you on?
is your phone ever recognised by the computer when you switch it on while connected to the usb and pc as an mtk preloader device?
my suggestion would be to re use an official rom update with a scatter file method. this should repartition your device properly.
this is why its super imoprtant to know which version you are on.
I'm quite positive it's normal version, I live in Portugal, Europe.
Besides from the mentioned problem, the phone is working properly, is that what you mean with "is the phone working operation?"
Right now I'm on Eragon 9.5, before today, stock unrooted original rom.
Regarding usb cable connection:
I'm a Mac user, and the phone is recognized and i can use Android file transfer app on my mac while on android sys.
If I'm on recovery mode, i can't mount the "sd card" to my computer.
Hope this helps
El_Nino9 said:
hi,
what device do you have?
before you answer elephone p8000, i mean which version as in which 4g bands does it have access to? normal or version b?
is the phone working operation?
what current rom are you on?
is your phone ever recognised by the computer when you switch it on while connected to the usb and pc as an mtk preloader device?
my suggestion would be to re use an official rom update with a scatter file method. this should repartition your device properly.
this is why its super imoprtant to know which version you are on.
Click to expand...
Click to collapse
XLR8_2K said:
Huston, we have a problem. Since day 1.
(& please refrain from mentioning warranty, not an option)
I never had access to my microSd card.
I thought it was a stock Rom problem, so I waited until root, maybe with another rom, the problem would disappear.
Sadly, no.
The thing is, a 200 MB partition always mounts as my SD card.
I don't have a clue on how to solve it.
Any suggestions?
Thanks in advance! :fingers-crossed:
The bastard partition is the one mentioned below, and below that one, the untitled, is my 64GB micro Sd card.
I used Diskinfo app to get the data.
* SD card (EFI System Partition) [mmcblk1p1] (/mnt/media_rw/sdcard1, /storage/sdcard1) [vfat]
Used: 3.1 MB, Free: 196 MB, Total space: 200 MB
* Untitled [mmcblk1p2] Not mounted
If interested, the attached pdf has the full list of the internal storage (MMC) partitions
Click to expand...
Click to collapse
why don't you just format the sd card ? put the sd card in your pc and use MiniTool Partition Wizard Free Edition and delete every partition on the sd cad. and then create a new, FAT32 and if you want to have files biger then 4GB then exFAT, but then you need to flash this zip, to get it working right on phone (you need to use a custom rom, eragon or mine nexus, because of init.d)
The multiple partitions are on the MMC, not the SD. You misunderstood. The mmcblk1p1 mounts as the SD card. But it's a partition from the MMC. Mounts with or without a physical SD in the slot.
I think I'll try and investigate the scatter method. Don't have a clue, yet.
Seems like a fluked MMC partitioning somewhere in time.
With the original stock OTA
XLR8_2K said:
I think I'll try and investigate the scatter method. Don't have a clue, yet.
Seems like a fluked MMC partitioning somewhere in time.
With the original stock OTA
Click to expand...
Click to collapse
you said you have a mac? i'm not sure you can use the flash tool for mediatek devices on that.
i only know the windows method and i know that works. i did it yesterday again.
can you get hold of a windows machine?
are you okay with flashing the december firmware on the device or do you need some guidance?
hopefully you get the device sorted
XLR8_2K said:
I think I'll try and investigate the scatter method. Don't have a clue, yet.
Seems like a fluked MMC partitioning somewhere in time.
With the original stock OTA
Click to expand...
Click to collapse
oh sorry, i misunderstood you. ok then you need to backup NVRAM. you can do it for example with TWRP. after that, just look here and copy the official rom files. this could solve your problem
Thanks for the help and suggestions guys
Yesterday I used a web downloaded version of aparted app, and deleted the infamous partition. And after the reboot, my 64GB sd card finally appeared!
For now I think I won't go into the scatter process. Will keep the info for future research thou, thanks!
XLR8_2K said:
Thanks for the help and suggestions guys
Yesterday I used a web downloaded version of aparted app, and deleted the infamous partition. And after the reboot, my 64GB sd card finally appeared!
For now I think I won't go into the scatter process. Will keep the info for future research thou, thanks!
Click to expand...
Click to collapse
firstly, you are very brave for deleting a partition you saw and didn't know what it did. what if it was the bootloader and you kill it? was very risky.
secondly, you don't know how this efi partition appeared on your device, it just wouldn't let you use your sd card? sometimes on SD cards they have a partition from the factory for some bs software but you say yours was the internal storage.
this brings me onto the fact that your seller has flashed your phone with something that enabled this? you openly trust the seller that they haven't modified the device to collect personal information or anything? i mean i would be worried and would have flashed the scatter file method. again this is why i also say you are brave.
dr root has provided you with a method for non pc version which i didn't know existed.
it's your device at the end of the day and you can do whatever you want.
good luck and enjoy your device