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!
Hi all,
I would like to start off by saying that I have spent many hours trawling the internet for the solution to this conundrum, and it's starting to sound a lot like the song "there's a hole in my bucket".
I own a HTC desire - my second one (the first is in a lake ) both of which have been rooted, s-off and with multiple roms tried on each. I have a nandroid backup of my current configuration stored on my computer, along with the contents of my sd card.
The problem(s):
I tried partitioning my sd card to have a2sd for insertcoin 1.0.5. I ran the alignment.zip in CWmod (alpharev version) and then installed insertcoin. It booted up fine, but the sd card wouldn't mount. I restarted, and removed it, checked it on my pc and the sd card works fine. The alignment log said it had changed the fdisk info, so I formatted the entire sdcard and tried it back in the phone - nothing. won't mount, comes up with the common "can't find ******blk0*" problem. Tried two more sd cards, neither of them work.
Then I made a big mistake, which in hindsight was very stupid. I did a factory reset to try and fix the problem.
So...now I have a desire that will not mount sd cards (even though hboot recognises hboot files on the sdcard) a desire that has no rom to start into, and I cannot get adb/fastboot to work. please give me at least the starting steps to go.
Any comments of "you're screwed" are not helpful.
I'm heading to bed now - i'm tired and sad and frustrated. Please help me - I don't like asking for help, and prefer finding solutions and posting my results.
Sounds like a usb brick..
Sent from HTC Desire via XDA App
... Which is easily fixable. There is even recovery with brick fix.
I tried searching into that, but are you able to point me towards any links, or the name of the recovery tool so that I can find it?
RMD Recovery. There is also tutorial for manual brick fix in dev section. Look for Desire index sticky thread.
Thank you everyone for helping me with this, I followed this guide:
[can't post because i'm a new user, but search for "USB brick/rickrolled/b0rked -> FIXED!" on android.monaco.com]
and it appears to have fixed my problems. I have just installed a froyo rom, and am waiting on it booting up. Thank you so much.
Seems that my enthusiasm was short lived. It worked to let me install froyo, but when I tried to install a system update I was unable to because I had the error back. I'm gonna have to redo it and hope it works again. At least I have a phone now though.
Hope you manage to get it sorted
Just put rmd recovery on your sd as a pb19img.zip and flash it in bootloader! Choose usbfix... Fixed!
If you want the zip just say.
backfromthestorm said:
Just put rmd recovery on your sd as a pb19img.zip and flash it in bootloader! Choose usbfix... Fixed!
If you want the zip just say.
Click to expand...
Click to collapse
I want the link please
I installed the latest CWM from [ACS][KERNEL] ClockworkMod Recovery v 5.0.2.6 // Latest Compiled Version, but when I boot into it, it says that it cannot mount the SD card. It can however, mount eMMC, which is where my downloads folder is. So I can install ROMs, but not back them up. Anyone know what went wrong?
Do you have an external SD card installed? If not, you need one to do CWM backups on that version. I'm guessing that's your issue anyways. I've seen it all over these forums lately.
Yup, have an SD
Oh yeah, I have an SD card. I watch these forums every day and am not the only one having this issue. I'm just fairly new to these forums, and can't post to the Dev thread yet.
I would also suggest trying a new/different SD card. I was having a similar issue. Would read normally once phone was booted, but could never mount it in cwm . Bought nice new class 6(class 4 is fine) card from a reputable supplier and its all good now. Mounts fine.
Solved
I feel like such a nubcake. The SD card wasn't seated correctly. It's working fine now.
Still on the subject of CWM, I'm having the issue where it will hang on the initial "Android next to an install icon" screen. If I power off the phone and turn it back on it will go into recovery just fine. That's a pretty ugly workaround though, and I understand that a few others have the same problem. Any news on that one?
I am a msee and have been using custom ROMS for years. Recently got real screwed up and broke my brand new SG3 (i747). The new bootloader (NE4) from AT&T really makes me mad. They are screwing customers with blowing fuses and semi locking bootloader with restrictions.
Sooooooo, what happned? I HARD BRICKED my phone. BLACK SCREEN of death. NOTHING shows up, no boot, no download, no recovery. DEAD ! ! !
Spent 1 week / 15hs each day trying new things such as CLONE a good G3, fixing bootloader, etc.... Found many "debrck.img" files for SG3 i747 on the internet an ONLY 1 works. (see link) . NEW Problem was that I could now boot up from external sdcard BUT no matter what I flashed from ODIN or from zip ROM files the phone was ALWAYS dependent on bootable scdard. Could not boot w/o card. This is a serious BOOTLOADER problem.
Enough of the bla bla bla.... now the fix:
1) Download debrick256.img web address: androidfilehost.com/?fid=23501681358551786
2) Use Win32DiskImager program to flash a sdcard CLASS 10 ONLY (card can be 16GB or 32GB), then insert sdcard into phone
IF you have a ROM already installed, boot phone an skip to step 5
IF you have a CUSTOM RECOVERY INSTALLED skip to step 5
3) Boot into download mode ( I am sure you are now a VERY VERY HAPPY PERSON NOW )
4) ODIN/flash a custom recovery
5) Download d2att_I747UCUFNE4_bootloader_modem_4.4.2_7-29-14.zip web address: androidfilehost.com/?fid=23578570567720263
6) Transfer d2att_I747UCUFNE4_bootloader_modem_4.4.2_7-29-14.zip to phone (use ADB or if phone boots just use PC)
7) Reboot into RECOVERY
8) Flash d2att_I747UCUFNE4_bootloader_modem_4.4.2_7-29-14.zip
9) Install CM11 or STOCK 4.4.2 or higher ROM
Remove sdcard. Enjoy....... your phone is back to normal
UPDATE NOTE:
MUST USE CLASS 10 SDCARD ! ! ! !
Good info to pay attention too: "There no reason to downgrade your bootloader; If you did it to be able to flash a ROM that doesn't recognize the newest bootloader version and therefore wouldn't let you flash, you should contact the ROM developer and tell them to add the newest bootloader version to their asserts. The latest bootloaders trigger eFUSEs within the device, no longer allowing it to boot from older bootloaders. These eFUSEs cannot be reset without Jtag equiptment and specific files." therefore..... NEVER DOWNGRADE YOUR BOOTLOADER
This is impressive...
Sent from AT&T Galaxy S5 running off Android 4.4.2
Never know when you might need this...(Thank you for the solution...)
holy crap. if this actually works to fix my other s3, i'll be soooooo happy.
i had bricked the phone installing a beta of TW4.4.2 a few months ago. we'll see what happens.
BAH! This didn't work for me. Oh well.
Card size
First of all thank you a bunch!!!! You are lifesaver.:laugh:
Only thing I want to add is about card size...
If you use 16GB be aware that not every one will work, I had lost hours with kingston one that has real capacity of 14,49GB which is NOT enough space to do place debrick image.
So I just used one 32GB class 4 kingston I have in tablet, deleted all partitions, created on partition of real 16GB and after that everything went smooth..
agota5 said:
First of all thank you a bunch!!!! You are lifesaver.:laugh:
Only thing I want to add is about card size...
If you use 16GB be aware that not every one will work, I had lost hours with kingston one that has real capacity of 14,49GB which is NOT enough space to do place debrick image.
So I just used one 32GB class 4 kingston I have in tablet, deleted all partitions, created on partition of real 16GB and after that everything went smooth..
Click to expand...
Click to collapse
If you use a 32gb card, do you NEED to make a 16gb partition for this to work, or will using all 32gb be ok?
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)...