First of all, sorry if this is in the wrong place. I searched for awhile, but there is SOOO much information here I got a little lost.
I have a MT3G that was running Donut. I wanted to root it and upload a new ROM...so I came here.
I reverted to Cupcake using SAPPIMG.nbh
Then I rooted using the walkthrough and :flashrec-1.1.3-20091107-2.apk and recovery.img
I attempted to reboot after installing ZeroXd-5.0r2-sapphire.zip
everything appeared to work correctly, and upon rebooting my phone powered on as normal.
The green My Touch screen came up, then it flashed HERO, and cut to ZeroXD, and quickly goes to a black screen with casper the friendly ghost. It appears to be trying to load further but only loops from the HERO logo back to the ZeroXd, and back to casper....over and over.
ideas?
wrong area? no ideas?
I can get to the Android Recovery Screen, and enable mounting and unmounting of the SD card.
Related
Hello, I have an unrooted Hero from Orange (Spain) that enters in a boot loop. I have tryed everything to restore it but with no success. In the hboot menu it says "touch panel-fail" and even if I flash again the original rom from the hboot, it still gets in a boot loop.
First of all I will explain my case.
I had the Hero rooted, with custom roms etc, but when I bought a Nexus One, I gave my Hero to my brother. In September he told me that the official 2.1 had arrived to the Hero, so he wanted it instead of a custom rom, so I just proceeded to do so. I created a GoldCard, installed the 1.5 RUU of WWE, made the two OTAs and all OK. The last week (I think) he received a new small OTA, he updated successfully. My brother went to sleep with the Hero almost charged, but when he woke up, the Hero was off. Then, when he turned it on, and after a while (15mins or so) the Hero finally boot up, but the touchscreen wasn`t working and using it with the trackball the Hero was always prompting FC of android.process.acore (every 2 seconds more or less).
After watching that, I installed the official 1.5 of Orange hoping that it will fix it, but no way. Now it gets stuck in a loop while booting after the Orange bootscreen.
I tryed again to flash the WWE version, but with my old GoldCard doesn't seem to work (incorrect cid) and not being able to boot it up, I cannot create a new GoldCard or even root it.
I have tryed a lot of fastboot comands but I can do just little things because for the most useful things I need root.
Other thing that might be good to know is that when I plug the power to the Hero nothing happens, the led is not turning on, and I don't know how much battery I still have. Thank goodness that the battery was full before I moved the Hero to this infernal boot loop.
Please I will be so thankful if anyone can help me or just giving me any clue about how can I fix this.
I had the same problem on a refurbished hero I had. It had touchpanel fail in hboot and was in a constant loop.
I managed to get it to boot into android once by installing the ruu while in fastboot mode, however the touchscreen did not work and when I rebooted the phone it went back to the loop.
I sent the phone back for a replacement. If u check my previous threads ull see the thread icreated. In it I said that it had worked as that was when it finally booted but before I realised the sgreen didn't work
Sent from my HTC Hero using XDA App
Thank you for your reply, I will check your posts when I arrive home this evening.
hi.
I had the same problem and solve it by flashing this rom (goldcard needed)
http://shipped-roms.com/shipped/Her...io_63.18.55.06P_6.35.15.11_release_signed.exe
Ok, so before the general populace of the forum, looks over this post thinking it's some noob who cant read through the forums to solve there own problem, i would like to say thanks in advance to anyone who can seriously provide some help.
Problem is as follows:::
1,)Phone is working fine using mini-winmo+cyan droid
2,) -PROBLEM- My android stops working, so now im stuck using a lite version of winmo
3,) Tried formatting the sdcard with the lite version winmo built in sdcard formatter, doesnt solve anything, dont exactly know what i was trying to solve with this step.
4,) I decide to get a nice fancy version of winmo, figured it would be as easy as just flashing it once n done.
5,)Decided on going with Ozrom, looked the best at the time.
6,) Run the ruucustom as admin, everything goes fine.
7,) -PROBLEM- after flashing the first boot leaves me stuck on the bootscreen.
So after all that i took the advice and tried to get back to the stock Tmous ROM, but as im typing this im still stuck on the Stick together screen, and also just for a control group i downloaded the latest HD2 cell winmo rom release, and that left me hanging on there version of the boot screen.
Same problem, different roms.. stuck on the loading/boot screen.
But, with the stock rom after playing around with removing the battery, simcard,sdcard and what have you i got the stock rom to boot!!!! I was so excited, i skipped the "How to use the on screen keyboard" tut and was typing in my email info when the phone reset on its own and all my hopes went down the drain... hopefully i will get some help on the issue, and like i said previously in the first paragraph i appreciate any and all help.
thanks.
---UPDATE---
Phone is on and working, intermittently.
When i plug the phone into the charger and wait for the amber light, it will boot up and actually enter into windows, now heres the kicker, removing the charger and using the phone will result in the phone turning off and restarting itself, hanging on the stick together screen.
Removing the battery, and replacing the battery after i push all the buttons, the same way you would power cycle a TV remote, and then connecting it to a charger is the only way ive been able to maintain the operation of the device.
Any ideas?
Try doing task29 reinstall winmo Rom of choosing.. see if that helps.. also I flash everything from bootloader. Also check battery pins make sure they aren't bent..
Sent from my Mytouch HD2
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.
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
just flashed the new Android_Revolution_HD-One_5.2_GE ROM via CWM. appeared to install fine. finished all the steps of selecting my apps, options, etc. phone started booting up, made it to the language selection screen and the rebooted. it just keeps rebooting. the furthest it makes it to is the language selection screen, but sometimes not even that far. i also have the new kitkat 4.4 update saved on my phone. i couldn't get that to install via the OTA update, so i saved it in my "ROMs" folder on my phone. after one of the reboots, it started installing the updates, all 101 installed successfully (it appeared). i'm not sure if that was from the Revolution 5.2 ROM or my saved update, but i thought maybe it would be fine after that. however, it still continues to just reboot, sometimes making it to the language selection screen, sometimes the "Google" splash screen, and sometimes only to the "HTC" screen. i can still get into CWM recovery just fine though. can anyone help? i'm stuck between a rock and a boot loop place right now, and it sucks!!! any advice would be greatly appreciated! thanks!
Was your phone s-off? Off not then that's your problem right there
Sent from my HTC One using Tapatalk
Get yourself back into recovery and restore a back up ... You did make one, didn't you? If not, just flash a new ROM. Go with something known stable, just to get back on your feet and then try your ARHD flash again if you want.
Sent from my HTC One using Tapatalk