Hello, i currently own a HTC EVO 3D GSM, fully rooted and S-OFF'd.
I'm running stock rom, without any major modifications.
Earlier today i was doing a nandroid backup, just before wanting to try out LeeDroid ROM. The nandroid went through just fine, then i rebooted the phone on to do a titanium backup & sync to my dropbox.
Now i used my app "Hot Reboot" to simply do a reboot into bootloader.
The app didn't work (dont know why), so i closed it down and did a manual shut down and then battery pull.
When i put the battery in, and tried to boot the phone into bootloader, it didn't start.
I tried to do a normal boot, didn't start.
I tried to plug it into my charger. The light didn't turn on.
I removed the back cover, removed battery, SIM card, SD card and tried to get rid of any possible dust (i was kind of panicing here).
Put it all back in, same result.
I tried switching SD card to my old stock 8gb sdc4 sandisk. This time it finallly booted and everything worked like before.
I turned the phone off, and replaced the 8gb SD card with my 32gb SD card. Now this also worked fine.
I have no idea how or why this happened, but if anyone could shed some light on why/how it happened? Maybe i could avoid it happening again, because i was kinda freaking out when i thought i had a possible brick.
- Moon
Continuum Brick?
I have been reading since 2pm today. I'm lost in threads and advice about a bricked phone. I have a Continuum that shows a fuzzy screen. I can't see to get a download mode. The options are off or pixelated/fuzz screen. Is soldering still required? I was attempting to use CWM. I am not sure bad cable or what but it went down hill. My Win7 PC shows 0bytes free on the Continuum. I apolgize if this is the wrong area for my questions. I successfully rooted an Epic and a Kyocera Echo without too much trouble. I appreciate any thoughts, comments, and suggestions. Thanks in advance!!
This is my sister's phone so I may not be alive in the morning j/k
Today I have downloaded Ubuntu, Android SDK, One Click Unbrick, Resurrection, Java, and a host of other Android related files. I was SO sure all my clicking would bring me back to stock.
Related
Here's my story.
Rooted my phone about a month ago (used the PBI one, you know what I mean?) and when I did I loaded it in the root folder, rebooted, held END+VOL DWN, hit action, and away it went. Since then I've tried a few times to update to Evil Eris 4.0 using the same methods (I'm 100% newb when it comes to all the terminology) and long story short I followed all the instructions and it just sat there like a brick with the "Green Droid and big triangle with a ! in it" screen (which I interpret as death) but found that if I just plugged it into a computer (Mac or PC) it'd load back up into whatever rom I was using fine. This morning I got jazzed about KaosFroyo V. 34 and tried to install that the same way (END+ VOL DWN) and again got the "!" screen making me run to school to plug it in ASAP.
With all that said, what am I doing wrong? I'm such a crazy newb about all this its ridiculous so please don't reply with a lot of jargon, step by steps would be greatly appreciated. I don't HATE my current rom (the maps crash a lot but they do work) but I just wanna be one of the cool kids
Would a bought Rom Manager app help? I've heard lots of negative stuff about the clockwork mode and that it can ruin your phone.
GreenLanternBatman said:
Here's my story.
Rooted my phone about a month ago (used the PBI one, you know what I mean?) and when I did I loaded it in the root folder, rebooted, held END+VOL DWN, hit action, and away it went. Since then I've tried a few times to update to Evil Eris 4.0 using the same methods (I'm 100% newb when it comes to all the terminology) and long story short I followed all the instructions and it just sat there like a brick with the "Green Droid and big triangle with a ! in it" screen (which I interpret as death) but found that if I just plugged it into a computer (Mac or PC) it'd load back up into whatever rom I was using fine. This morning I got jazzed about KaosFroyo V. 34 and tried to install that the same way (END+ VOL DWN) and again got the "!" screen making me run to school to plug it in ASAP.
With all that said, what am I doing wrong? I'm such a crazy newb about all this its ridiculous so please don't reply with a lot of jargon, step by steps would be greatly appreciated. I don't HATE my current rom (the maps crash a lot but they do work) but I just wanna be one of the cool kids
Would a bought Rom Manager app help? I've heard lots of negative stuff about the clockwork mode and that it can ruin your phone.
Click to expand...
Click to collapse
It sounds like you don't have Amon's recovery flashed yet.
This is probably the easiest thing you can do.
http://forum.xda-developers.com/wiki/index.php?title=How_to_flash_Recovery_Image
or this
http://forum.xda-developers.com/showthread.php?t=742228
In either case, you need to read, and educate yourself.
Precursor - If you run a back up program like Titanium Back Up or MyBackUp Pro, now would be a good time to do that.
I think your main problem is that to get into Recovery mode, you need to hit Volume Up + Power (End). Once there, I'd suggest going to Back Up/Restore and doing a Nandroid Back Up. This will save the entire state of your phone just as it is before you went into Recovery. Exactly as is. Next, go to Wipe, and select options 1 - Factory/Data Reset and 2 - Dalvik Cache. If you don't already have the KaosFroyo-v34.zip file on the root (meaning NOT in a folder) of your card, you can go back to the main Recovery screen and select 2 - USB MS Toggle which will mount your SD card to the computer and you can drag and drop the file from there. Once you've followed these steps, now you are ready to choose option Flash Zip from SD card. Select the zip you need and let it do its thing. You didn't mention if you had apps2sd set up not. If you don't, ignore this next part, if you do, pay attention. IF and only IF you were using apps2sd then you will need to reformat your card to work with Froyo roms. Froyo already has the benefit baked into it but it utlilizes it in a different way. To reformat, you will want to copy everything from your SD card to your computer, then in Recovery, go to Partition card. For Ext and Swap sizes select "0" and then hit ok for partition the rest of the card in FAT32 format. Done. You can add back on contents from the SD card in Recovery through the USB Toggle mode or after you boot everything up, it does not matter (the only difference being that your computer will ask if you want to copy and merge folders if you do it after you boot because it will remake some of the folders for you on booting) . With that being said, now it's time to try out KaosFroyo! The first boot WILL take awhile and the phone will be very slow once it does boot as it has to Sync all of your info and applications back from the Market. Once that gets finished, then you can restore your data if you saved it through Titanium or MyBackUp. I usually like to give it a reboot after all this fun stuff, just to give it a chance to gather itself, if you will. After that, you should be good to go with learning the ins and outs of Froyo Hope this helps!
Did you make a amon backup before you first rooted you phone? I had that same problem when I flashed Kaosfroyo v34. I would boot up in recovery (Vol up+end) and I would have the android with the ! above him. I started freaking out. What I did was restore my nand backup back to 2.1. Then I re-rooted back to KaosFroyo v34. Then went into recovery and everything was good. My advice, unroot then root again. Maybe its not the best/easiest way, but it did the trick for me. And as always, search the forums, there is a post for almost anything. Hope that helps.
I've checked the other threads for solutions and I've tried many different things today but my phone still doesn't work, so I guess I should make a thread and ask you guys directly.
Ok, so my phone stopped working last night. It was running stock everything. Only upgraded to Froyo through Kies Mini a long time ago. Anyway, when I powered up the phone, it gets to the Galaxy S logo and then the screen dies. It's technically still on, since the four keys light up when I tap the screen. I took the battery out for a bit and put it back in, same thing. Logn story short, I tried to odin it back to stock JFD this morning and it didn't change anything. The screen goes to black right after the logos. Then I tried Eugene's Vibrant_Full_Froydin_AND_2E_Recovery_+SD_Fixed. It sorta worked. By that I mean, the phone loads up the OS and I got the home screen, but now it doesn't recognize the internal SD card. In fact, the notification gives me "Blank Internal SD card." In the Settings area, the phone storage read as either unavailable or 0.0 space. I tried to odin back to stock but then it gets stuck on Galaxy S logo again. I've tried this back and forth multiple times and it's still the same. Either it gets stuck on the logo or it doesn't recognize the internal sd card. I've tried it with repartition on and repartition off, but no difference.
So, are there any trick to fixing this? Thanks in advance!
Could you post the links to the files you are flashing? Honestly ODIN should have fixed it.
kawika said:
Could you post the links to the files you are flashing? Honestly ODIN should have fixed it.
Click to expand...
Click to collapse
Hi. I got the stock JVD from the Noob Guide (http://forum.xda-developers.com/showthread.php?t=849028). I followed the steps there to flash to stock through ODIN and I got the black screen/lighted buttons. Then I downloaded and flashed it with the one that came with the toolbox (http://forum.xda-developers.com/showthread.php?t=954509). same thing, black screen with lighted buttons. I also tried Eugene's ROMs (Eugene_SD+2E_JK2_Froyo - http://www.multiupload.com/12QAKU043I and the Froyo ~That does not Brick! - http://www.4shared.com/file/dJiyRz3v/EUGENE373_SamsungS_Froyo_PDA.html). Both links are from Eugene's forum page.
The only "success" I have so far is using Eugene_SD+2E_JK2_Froyo, but whenever it's loaded, I always get the "Blank internal sd card" notification and the phone storage is shown as unavailable. :\
Bump. I'm still trying to get this phone to work. :\
Give the following a try..
http://forum.xda-developers.com/showthread.php?t=1230059
Alex9090 said:
Give the following a try..
http://forum.xda-developers.com/showthread.php?t=1230059
Click to expand...
Click to collapse
Didn't quite work for me unfortunately.
1. When it's in recovery mode, I can't get adb to connect. I can only do it when it's loaded up.
2. When I tried to do print in parted, I get this error
Error: /dev/block/mmcblk0: unrecognised disk label
Click to expand...
Click to collapse
.
Do you have external card in the phone? First try taking it out and then reboot without it and see what happens. If that doesn't do anything..try the cleaning and repartitioning method posted by Br1ck'd ..
I have posted about it in several threads, including my own, so I figured I would finally put it in a central location. This is my FTDNB method for starting with a fresh, clean phone, without any ghosts of roms past popping up to cause you issues.
Download this first, and flash through Odin with your standard 512 pit file
http://eb-productions.proboards.com/...splay&thread=8
Then when it reboots to the recovery screen, pull your battery, reinsert it and boot up to dl mode, and flash the following, with your same pit file, and selecting repartition in Odin this second flash only:
http://eb-productions.proboards.com/...splay&thread=3
The first link there is Eugene's Froyo That Does Not Brick, but it doesnt work that well as a driver. As an eraser its great though! The second link is the Froyo JK2 leak, with fixed recovery and already rooted. If the first one didnt, the second flash will definitely put you back on Froyo bootloaders.
Thats my whole secret to keeping a clean phone and wiping out any ghosts. You can proceed from there in your desired direction (back to ZD or GZ preferrably) in a safe manner. Its always worked for me to clear up any oddness, and literally takes 15 minutes tops once you have the files downloaded.
Click to expand...
Click to collapse
I've tried that before. Eugene's Vibrant_Full_Froydin_AND_2E_Recovery_+SD_Fixed (Froyo JK2 leak) is the one that lets me load the system all the way through (better than running stock JVF which only gets me to the logo and then gets stuck). The internal sd card problem remains however. I get the "Blank internal sd card" notification. The phone can't function properly.
EDIT: I finally got the external sd card to work. Is there any program for me to fix my internal sd through my external sd card?
I'm having similar problems. Flashed back to stock Froyo using Heimdall (Mac only here), everything seemed fine, but when it all came back to life, I have no service and my Internal SD card is blank and cannot be reformatted.
It won't mount in the recovery tools, and so unable to format.
Any thoughts on how to restore functionality??
Bump. I'm still trying to get my phone working again. Thanks in advance!
If it just "happend" one day, then you're looking at a hardware failure. Flashing firmware can only make it worse.
xoxo1001 said:
I've checked the other threads for solutions and I've tried many different things today but my phone still doesn't work, so I guess I should make a thread and ask you guys directly.
Ok, so my phone stopped working last night. It was running stock everything. Only upgraded to Froyo through Kies Mini a long time ago. Anyway, when I powered up the phone, it gets to the Galaxy S logo and then the screen dies. It's technically still on, since the four keys light up when I tap the screen. I took the battery out for a bit and put it back in, same thing. Logn story short, I tried to odin it back to stock JFD this morning and it didn't change anything. The screen goes to black right after the logos. Then I tried Eugene's Vibrant_Full_Froydin_AND_2E_Recovery_+SD_Fixed. It sorta worked. By that I mean, the phone loads up the OS and I got the home screen, but now it doesn't recognize the internal SD card. In fact, the notification gives me "Blank Internal SD card." In the Settings area, the phone storage read as either unavailable or 0.0 space. I tried to odin back to stock but then it gets stuck on Galaxy S logo again. I've tried this back and forth multiple times and it's still the same. Either it gets stuck on the logo or it doesn't recognize the internal sd card. I've tried it with repartition on and repartition off, but no difference.
So, are there any trick to fixing this? Thanks in advance!
Click to expand...
Click to collapse
'I had a similar problem but later learned tht the SD card was actually damaged some how during flashing'
so try using a new SD card and Odin back to stock
Since I've lurked the forums for a few days and found no solution I'm doing an update to a post my brother posted about my phone a few weeks ago:
I was running Bionix 1.31 on my Vibrant, everything was wonderful! Smooth speed, GPS working great and everything, so I decided to flash DoW14 kernel v1.1.1 HD so I could have voodoo color, sound and BLN. First few weeks phone was working great! Then started to act strangely… sometimes it rebooted or turned off by itself and no matter what earphones I plugged to listen to some music, randomly stopped playing just as if I unplugged the headphones. Then two weeks ago I was using my phone and I put it in my pocket… when I pulled it out to use it again, it was off. Turned it on and it was stuck on the booting screen, after like 10 minutes I realized it was soft-bricked. I can get to download mode, though, so I used AIO Toolbox and flashed back to stock with Odin, flash was successful but when I turned my phone on shortly after the Vibrant screen it rebooted and did the same over and over again. Tried to flash back to stock a few times now and I get the same.
I ended up hard-bricking the phone, so I took it to a guy with a Riffbox and even after restoring the bootloader and all, still the same problem.
Thought it might be Voodoo Lagfix, flashed Eugene’s FTDB and flashed JFD, when it is loading up after the “Vibrant” screen it just turns off, I slide my external SD card in and I get this: youtube /watch?v=7Vhp1B3g_2w. Flashed Eugene’s again and rebooted with adb, after the galaxy S animation the screen goes black with the softkeys on (they turn off as I touch them). I can get to the phone with adb, on the system partition everything looks fine but on /data there is only 1 folder called “dontpanic” and it is empty… I tried to reach my internal SD card but it says “permissions denied” and the su command doesn't work.
The internal SD card might be dead or something, but I have no idea on how to confirm that.
Your help is very much appreciated!
FIXED!! Or something like that.
Using Odin, I flashed this version of Eugene's Froyo: mediafire /?dc2ngbbgsjgpc00 it booted into recovery so it gave me the chance to wipe data and cache, rebooted into system and voilá!
There's still a problem: The phone does not detect my internal or external SD cards... it says that it has 0.00B of space. I think there is a solution for that somewhere around XDA, will try to find it. If you know it, I would very much appreciate your help.
And I can't flash back to stock, if I do, I go back to where I was. :/
Taking a stab in the dark here, but perhaps it needs to be repartitioned? I believe there's a selectable option for that in ODIN.
Yeah, when I flashed this ROM I checked the repartition box and I still have the problem... :/
I also get the RIL reset error, like this: http://forum.xda-developers.com/showthread.php?t=835513
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
texnote said:
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
Click to expand...
Click to collapse
I would try popping it open and unplugging the internal battery then plugging it back in. Also hit the internal reset button while you're in there. It's pretty hard to actually kill one of these tablets. PM me if you need any other help.
help
Started my own thread, didnt mean to hijack. =)
Thanks, I will try removing the battery and let you know.
As for NVflash, I believe the latest version is here:
http://www.slatedroid.com/topic/171...-using-either-11-or-12-based-images-g-tablet/
However in my case I have no idea whether I have 1.1 or 1.2 and there is no way to determine this. Which one should I choose?
Paul
Doesn't matter for NVFlash, just download all of the flash files again because it might be that you have a bad download. Also make sure you have the right drivers installed since the drivers that automatically install when you plug it in sometimes don't work.
I'm pretty sure that if it boots past the birds, the hardware is working okay, so you should run the FORMAT version for NVFlash and then I'd run just a CWM flash setup and see if you can get into CWM and delete the partitions from within that.
The best thing to flash as far as ROMs would be Bekit's 1105 which is stock OTB with a few key changes. If you can't get the 1105 to play nice, you might really have some hardware problems.
I would go with the 1.2 BL, it will give you access to the newer roms as it appears that dev for the 1.1 BL seems to be dwindeling. I upgraded mine to 1.2 the other day and it worked great.
I have an Evo 3D on Sprint that I had downgraded to 1.4 s-off and I was running the AOKP milestone 5 rom with 4ext recovery. So yesterday I got a new 32 GB sd card to replace the 8GB one that came with the phone. I copied the data on the old SD card to my computer, powered off the phone and swapped sd cards, then booted back into android. I went to storage settings and erased the SD card, and I got a notification saying the SD card was blank or had an unrecognized file format. So I figured I would boot into recovery and see if there were any format options for the SD card to make sure it had the right file format. So I chose to reboot into recovery from the power menu, and instead of booting into recovery, the phone just turned off.
So now I can't turn the phone on and I've tried all the things I've already found here to get it back. I tried pulling the battery for a few minutes, tried doing the option to power on while holding down the camera button, and tried hooking it up to the computer only to be shown "qhsusb_dload" as the device, so I'm pretty sure it is bricked. I also don't think I can use the unbricking project since I think that is only for s-on devices.
Has anyone recovered from a brick like this? Do I have any options to resurrect my phone or is it completely dead? For repairs, I don't have insurance on my phone and I'm not going to take it into a Sprint store and lie about what happened. I'll own up to my mistake if I have to. Has anyone had a brick repaired by Sprint, and if so, how much did it cost? I figure my options are to have Sprint fix my phone, which might cost me a bit, or maybe now might be a good time for me to break my contract with Sprint and look at the unlocked Galaxy Nexus so I don't have to hack my phone to get the AOSP experience for ICS.
Thanks in advance for any helpful advice or suggestions, and hopefully I can get this thing figured out one way or another.
moleary04 said:
I have an Evo 3D on Sprint that I had downgraded to 1.4 s-off and I was running the AOKP milestone 5 rom with 4ext recovery. So yesterday I got a new 32 GB sd card to replace the 8GB one that came with the phone. I copied the data on the old SD card to my computer, powered off the phone and swapped sd cards, then booted back into android. I went to storage settings and erased the SD card, and I got a notification saying the SD card was blank or had an unrecognized file format. So I figured I would boot into recovery and see if there were any format options for the SD card to make sure it had the right file format. So I chose to reboot into recovery from the power menu, and instead of booting into recovery, the phone just turned off.
So now I can't turn the phone on and I've tried all the things I've already found here to get it back. I tried pulling the battery for a few minutes, tried doing the option to power on while holding down the camera button, and tried hooking it up to the computer only to be shown "qhsusb_dload" as the device, so I'm pretty sure it is bricked. I also don't think I can use the unbricking project since I think that is only for s-on devices.
Has anyone recovered from a brick like this? Do I have any options to resurrect my phone or is it completely dead? For repairs, I don't have insurance on my phone and I'm not going to take it into a Sprint store and lie about what happened. I'll own up to my mistake if I have to. Has anyone had a brick repaired by Sprint, and if so, how much did it cost? I figure my options are to have Sprint fix my phone, which might cost me a bit, or maybe now might be a good time for me to break my contract with Sprint and look at the unlocked Galaxy Nexus so I don't have to hack my phone to get the AOSP experience for ICS.
Thanks in advance for any helpful advice or suggestions, and hopefully I can get this thing figured out one way or another.
Click to expand...
Click to collapse
One of these may help you out:
http://forum.xda-developers.com/showthread.php?t=1627917
http://forum.xda-developers.com/showthread.php?t=1547695
moleary04 said:
I have an Evo 3D on Sprint that I had downgraded to 1.4 s-off and I was running the AOKP milestone 5 rom with 4ext recovery. So yesterday I got a new 32 GB sd card to replace the 8GB one that came with the phone. I copied the data on the old SD card to my computer, powered off the phone and swapped sd cards, then booted back into android. I went to storage settings and erased the SD card, and I got a notification saying the SD card was blank or had an unrecognized file format. So I figured I would boot into recovery and see if there were any format options for the SD card to make sure it had the right file format. So I chose to reboot into recovery from the power menu, and instead of booting into recovery, the phone just turned off.
So now I can't turn the phone on and I've tried all the things I've already found here to get it back. I tried pulling the battery for a few minutes, tried doing the option to power on while holding down the camera button, and tried hooking it up to the computer only to be shown "qhsusb_dload" as the device, so I'm pretty sure it is bricked. I also don't think I can use the unbricking project since I think that is only for s-on devices.
Has anyone recovered from a brick like this? Do I have any options to resurrect my phone or is it completely dead? For repairs, I don't have insurance on my phone and I'm not going to take it into a Sprint store and lie about what happened. I'll own up to my mistake if I have to. Has anyone had a brick repaired by Sprint, and if so, how much did it cost? I figure my options are to have Sprint fix my phone, which might cost me a bit, or maybe now might be a good time for me to break my contract with Sprint and look at the unlocked Galaxy Nexus so I don't have to hack my phone to get the AOSP experience for ICS.
Thanks in advance for any helpful advice or suggestions, and hopefully I can get this thing figured out one way or another.
Click to expand...
Click to collapse
Or, you can try this one:
http://forum.xda-developers.com/showthread.php?t=1648703
freeza said:
One of these may help you out:
http://forum.xda-developers.com/showthread.php?t=1627917
http://forum.xda-developers.com/showthread.php?t=1547695
Click to expand...
Click to collapse
Thanks for these links. I wasn't sure if the unbricking project would be helpful since it says it is only for devices that were bricked by turning s-on and I didn't even think about using Unknownforce's method. I'll give both a shot when I get home.
tgruendler said:
Or, you can try this one:
http://forum.xda-developers.com/showthread.php?t=1648703
Click to expand...
Click to collapse
I thought about posting this there, but I figured this was more of a broad subject and not really a specific question so I put it here instead. If it needs to be moved then that is fine with me.
I couldn't get either Unknownforce's or the unbricking tool to recognize my device. I guess this means my options for getting this thing going are severely limited. I'll be contacting Sprint tomorrow to see what they can do and I'll probably start exploring the option of selling this thing for as much as I can get to help pay to break my contract with Sprint.