Hello every one,
I am new to the forums and have been looking around for some time. I have a major issue that I need some assistance with if possible.
I am running, well was running, gingerbread 2.3.3 on my HTC Evo 4g phone until yesterday night. Here is some info about what happened. I rooted my phone with revolutionary and everything was going good til I tried to install a new ROM on the phone. The ROM I was downloading was CyanogenMod7, When it finished downloading, the phone booted itself into recovery to install the ROM. Well this is when the problem started, it just sat at the install screen and when it got down with the install it just continued to boot itself into a loop.
I turned the phone off and tried to boot it into recovery, which it did by the way. I did a complete restore of the stock ROM and rebooted the phone, when the phone turned back on is when the phone just continued to restart itself over and over again. So, I did a complete wipe: Recovery, Clear storage etc and nothing seemed to work but instead of it restarting itself, it just sits at the recovery screen and wont go any further. Just like it doesn't have any OS installed to boot from.
I would like some help and see what I can do to fix this problem.
When I go to recovery and boot from the fastboot-bootloader it says:
SD checking "No Image" Loading...
No Image,
loading.....
No image,
Loading....
No image or wrong image....
Click to expand...
Click to collapse
on top of that the sd card well not mount to the phone. I am so lost right now.
Some one pelase help or point me in the right direction.
Which recovery are you using for this? Maybe you can actually get it together by doing a complete wipe and cleaning cache/dalvik and then do the recovery.
I am using the clockwork recovery v3.0.0.5.
Every time I try to wipe the Dalvik Cache it tells me
E:unknown volume for path [/sd-ext] Dalvik Cache wiped
Click to expand...
Click to collapse
I still get the same thing. The one issue that I have encountered was that the sd card is not mounted to the phone. I have android sdk tools installed but the program can't seem to find my phone when I run the command prompt. The other things is now my phone just randomly shuts down and the the battery light just blinks, like its in stand by mode or something. The only thing I can do is take the battery out and what, then replace the battery and see if it works.
Try to charge the battery without using the phone that way you can work with it. My suggestion is to use Amon-RA recovery. Works a whole lot better that Clockwork. And try from there if you can install the ROM right.
It might be problems with your SD card. If is not reading it then that would be the message.
I tried that and nothing, I gave up on trying to save the phone that I went and got a replacement for it.
Related
Hey guys,
I went to flash a new stable build of Froyo on my Desire this morning.
And i backed up using Clockwork, and then the ROM all installed fine. But once the phone had booted up, it stayed on the custom boot logo, despite the keypad lighting up, the green charge LED coming on and me being able to lock and unlock the phone.
So i figured that this was a problem and went to back to restore my old ROM and carry on like i have done many times before. However once i have booted into Clockwork, and gone to the recovery section, i select my most recent backup and the device then says "No Files Found" in the recovery zip.
And when i try to install update.zip from my SDCard the device just flashes up with installation text for about 2 seconds then vanishes and goes back to the clockwork menu having done nothing
What can i do?
i wouldnt worry about it too much
your phone completely works and youre not restricted of any access
seeing that clockwork is not finding any files have you tried making a new backup?
have you tampered with the recovery lately?
if recovery is not finding any files then maybe there is a problem with it, and if i were you i'd reroot my phone with unrevoked to re-install recovery.
if your recovery actually just does not work it could mean that the recovery image is corrupt, this can be fixed by installing a RUU (note that this will unroot your phone but re-install the recovery image).
if this is not the case then im sure im soon to be corrected by someone more knowledgeable than me
Well, i wiped the Cache and Data and now the phone boots up and functions fine, however both mobile internet and Wi-Fi both dont work, but i figure this is just the rom i am using.
So i'm just gonna reroot, sideload clockwork and what not and then try putting the Desire HD rom on it haha.
Thanks for the help
I flashed the incredibly re-engineered v2.2 rom a week or so ago and it worked great till today it was giving me a force close on a bunch of apps, so i restared it and it still didn't help. Did a *228 and when it restated it just goes to the black screen that says htc incredible Loading then after several seconds it flashes blank for half a second then says same thing. I used rom manager to flash it. I've also used virtuous and skyraider 3.5. I'm good at computers but android is new to me as i've only had this fon 2 months. I have to do a battery pull to restart it. Any Ideas on how to fix this? I can boot into recovery but havn't been able to do anything... Never used it so not sure what to look for but like when i click recovery or factory reset, nothing happens. Oh, and i did a search but didn't come up with similiar problem.
htc incredible s-off
radio 2.15.00.07.28
Flash a different rom.
sent from my Dinc
How do I do that? When I boot in recovery mode I have option of fastboot, recovery, clear storage, simlock, and factory reset. When I select recovery it goes to bootloader, reboot, reboot bootloader, and power down, with reboot highlighted. Wen I select that it boots like normal than gets stuck on boot up screen.
Try fixing permissions through Rom Manager first, if not I would reinstall the rom. Be sure to do a full wipe, don't just flash over your previous rom.
If neither of those work, I would follow this thread
http://forum.xda-developers.com/showthread.php?t=786436
Flash back to stock 2.2 and see if your phone starts acting the same way. If so I would take it back to verizon. If everything seems ok, re-root and flash JUST the rom and apps that you want, no kernel, themes, anything extra yet. See if that fixes the problem.
I made sure I did full wipe when I installed it so that shouldn't b problem. The issue Is i can eve get to rom manager because he Fon wont load past the boot image. And its out of warany so vzw prolly wuldnt be much help.
mennotech said:
I made sure I did full wipe when I installed it so that shouldn't b problem. The issue Is i can eve get to rom manager because he Fon wont load past the boot image. And its out of warany so vzw prolly wuldnt be much help.
Click to expand...
Click to collapse
I would re-download a different ROM (making sure you don't have a corrupt download), check the MD5 SUM's to verify integrity of your download, mount USB Storage in Recovery to transfer the file to your USB card (when phone is off, hold down the Power and Volume Down buttons at the same time), wipe all user data/factory reset and Dalvik, and then reflash the ROM of your choice.
mennotech said:
I made sure I did full wipe when I installed it so that shouldn't b problem. The issue Is i can eve get to rom manager because he Fon wont load past the boot image. And its out of warany so vzw prolly wuldnt be much help.
Click to expand...
Click to collapse
Go to that link in my post, download the PB31IMG from the 2.2 Stock OTA, put it on the root of your SD card, boot into the bootloader and let it update. You will go back to being completely stock and unrooted. Root it and then try installing the rom again.
My desire keeps on rebooting when trying to turn it on, going to recovery mode, or when im updating a lot of applications on the phone.
there are times that i can enter recovery, but it is very seldom that i can enter it.
im using amonra, when i was able to enter the recovery i tried to wipe everything. but the files are still there even if i wipe them. so i tried flashing a new rom to fish the problem. after flashing the new rom successfully it goes to the lock screen and then restarts again..
the problem started after flashing my rom to leedroid which was a month ago.
what can i do?..
hope my phone isnt bricked
Try this:
Do the "CLEAR STORAGE" option in the HBOOT menu.
Enter recovery
Wipe ALL userdata
Wipe dalvik-cache
Reflash LeeDrOid ROM
That is what I did when the same thing happened to me when I flashed my first ROM (which happens to be LeeDrOid lol).
Also, try following up with this thread.
this isn't my first time flashing.
i already tried doing clear storage and problem still exists.. keeps on rebooting and can't enter recovery.
did wipe all already.. still having same problem
just finished reformatting my sd card and reflashing a new rom.. still having same problem..
senkai16 said:
this isn't my first time flashing.
i already tried doing clear storage and problem still exists.. keeps on rebooting and can't enter recovery.
did wipe all already.. still having same problem
just finished reformatting my sd card and reflashing a new rom.. still having same problem..
Click to expand...
Click to collapse
I didn't mean to offend you, I just listed the steps I took when it happened to me a while back, hoping that it would work with you.
You can un-root the device and return it to factory condition by using the official RUU, then start all over =/.
wasn't offended
yah, right now im downloading the RUU and trying to unroot.. hope it works *crosses fingers*
thanks for the help though.
No problem =).
cant run the original RUU. because i can't even go to the original screen. kept getting error saying check the cable etc..
is there any other way?.
update:
now i can't even go to recovery manager again..
tried to clear everything.. still same problem.. any ideas on how to fix this?..
any help would be very much appreciated..
thanks..
update again:
now my phone is going till the lock screen and then restarts...
update on what i am doing.
i letted my desire rest for a couple of minutes and then tried opening it again. i was able to go to the lock screen w/o restarting. but sometimes it still does
When i was able to go past the lock screen i runned the asia RUU to unroot my phone but i got an error at the end of the process. now what i do have is an HTC logo in the middle of the screen and four exclamation point inside a triangle on the corners.
any help guys?..
I used the GN Toolkit V2.2 to unlock the bootloader, after installing the adb drivers via PDANet. I flashed Clockwork Mod on as well, and was going to install the Android Revolution ROM. I thought I had already copied the zip file to the internal storage, but when I tried to flash it from inside CWM, it said no files were found. (May have copied it before wiping device, I can't remember). So I restarted so I could copy the zip file again and then flash it. However when starting, it seemed to be stuck on the startup screen, with all the flashing blocks of color fading in and out. After a while stuck on there I couldn't do anything so I did a battery pull to restart. At this point, I can start normally or into recovery mode. If I try to start normally, (or go into recovery mode and choose restart from the submenu), it shows the black screen with the white Google logo, and the unlocked icon, stalls for a few seconds, then does a short vibrate and reloads the logo again. It will keep doing this and not go any further. I tried doing an additional data wipe from recovery mode but that didn't help, and I tried to do USB mount from recovery mode, hoping to copy the Revolution zip file and flash it over, but it couldn't mount. I'm starting to panic a little bit, did I brick or otherwise mess my phone up? What can I do? Any help is REALLY appreciated.
Thanks so much and I hope this is the right forum.
I dont have the answer but I wanted to post to calm you. This happens a lot.....multiple times to me on my android devices. You live and learn next time, do a backup in cwm before wiping data and flashing new stuff
Im sure someone will post shortly to solve your problem
Well ok that is reassuring thanks. I downloaded the Google factory ROM from the code.google.com and was able to flash that on my phone with GN Toolkit. It is trying to boot right now, still on the colorful screen. I think maybe I didn't give it enough time last time around? At least I'm past the black and white logo screen. So I'll let it sit for a few minutes and see what happens.
Edit: I let it run for a couple minutes, and it blacked the screen for a sec, showed the white Google logo again, and then went into the colorful startup screen again. I think it's working now so that's a relief.
If someone finds this thread in the future with a similar issue: Don't battery pull during start up and be patient if you don't want to freak yourself out haha. But as spitefulcheerio said, it will be okay so just don't panic. Thanks again.
Make sure you do a Factory Reset in STOCK recovery after unlocking the bootloader. THEN install CWM. learned that one the hard way. skipped a step after doing the oem unlock.
Yes, first time will take awhile on the boot animation.
And, as long as you see the google logo, you are ok, even if it freezes on that. They designed this phone to be easy
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#6
Guess all I needed was a psychological confidence boost, thanks for everyone for being supportive I thought I just threw a few hundred bucks away. But I got Revolution installed, phone and rooted and runs like a dream. Thanks all around!
mynameismolotov said:
I used the GN Toolkit V2.2 to unlock the bootloader, after installing the adb drivers via PDANet. I flashed Clockwork Mod on as well, and was going to install the Android Revolution ROM. I thought I had already copied the zip file to the internal storage, but when I tried to flash it from inside CWM, it said no files were found. (May have copied it before wiping device, I can't remember). So I restarted so I could copy the zip file again and then flash it. However when starting, it seemed to be stuck on the startup screen, with all the flashing blocks of color fading in and out. After a while stuck on there I couldn't do anything so I did a battery pull to restart. At this point, I can start normally or into recovery mode. If I try to start normally, (or go into recovery mode and choose restart from the submenu), it shows the black screen with the white Google logo, and the unlocked icon, stalls for a few seconds, then does a short vibrate and reloads the logo again. It will keep doing this and not go any further. I tried doing an additional data wipe from recovery mode but that didn't help, and I tried to do USB mount from recovery mode, hoping to copy the Revolution zip file and flash it over, but it couldn't mount. I'm starting to panic a little bit, did I brick or otherwise mess my phone up? What can I do? Any help is REALLY appreciated.
Thanks so much and I hope this is the right forum.
Click to expand...
Click to collapse
cancerouspete said:
Yes, first time will take awhile on the boot animation.
And, as long as you see the google logo, you are ok, even if it freezes on that. They designed this phone to be easy
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#6
Click to expand...
Click to collapse
mynameismolotov said:
Guess all I needed was a psychological confidence boost, thanks for everyone for being supportive I thought I just threw a few hundred bucks away. But I got Revolution installed, phone and rooted and runs like a dream. Thanks all around!
Click to expand...
Click to collapse
To provide some technical details on why it takes longer the first boot and appears to "hang" at boot animation ...
During the boot animation, the /data/dalvik-cache directory is built up for each application loaded on the device. This occurs during the very first boot. If the /data partition is wiped, the dalvik-cache directory is also wiped and will have to be rebuilt on the first boot. All subsequent boots will be quicker as this directory has already been populated.
Whenever loading a new ROM or performing the fastboot oem unlock command, the /data partition is generally wiped which takes with it dalvik-cache and results in the delayed initial boot time while the dalvik-cache directory is re-populated.
Hope that makes sense and fills in a few blanks on the why Android appears to "hang" at the boot animation during first boot after the /data partition is erased or the /data/dalvik-cache directory is erased.
Hi. I was trying out Blisspop on this tablet and decided I preferred CM11 so decided to restore a backup. After rebooting, nothing turned on, only download mode worked so I just flashed stock firmware using Odin (which I had used successfully previously). Now it boots but gets stuck at the Samsung Logo. I can still get to download mode, but nothing else. I've read that if factory reset in the stock recovery, it'll work itself out but I can't even get to it. Any suggestions? Thanks.
jalchemyst said:
Hi. I was trying out Blisspop on this tablet and decided I preferred CM11 so decided to restore a backup. After rebooting, nothing turned on, only download mode worked so I just flashed stock firmware using Odin (which I had used successfully previously). Now it boots but gets stuck at the Samsung Logo. I can still get to download mode, but nothing else. I've read that if factory reset in the stock recovery, it'll work itself out but I can't even get to it. Any suggestions? Thanks.
Click to expand...
Click to collapse
Dont panic really common problem happened to me.
1. Boot into recovery, if not flash one with odin coz your gonna need something...like philz touch or team win or whatever.
2. Wipe cache and dalvik, reboot and wait, samething might appear to happen but it should boot.
Basically ive noticed a few times now on my t805 that the cache wouldnt format propperly and became corrupt and caused this.
I knew this because in the recovery a bunch of errors appeared saying couldnt acces log from cache/blah zt each time i navigated the menu of revoveryand so i wiped cache and they stopped
Booted and viola...if you see any other errors in recovery tell us here.
Good luck m8.
pdolton2000 said:
Dont panic really common problem happened to me.
1. Boot into recovery, if not flash one with odin coz your gonna need something...like philz touch or team win or whatever.
2. Wipe cache and dalvik, reboot and wait, samething might appear to happen but it should boot.
Basically ive noticed a few times now on my t805 that the cache wouldnt format propperly and became corrupt and caused this.
I knew this because in the recovery a bunch of errors appeared saying couldnt acces log from cache/blah zt each time i navigated the menu of revoveryand so i wiped cache and they stopped
Booted and viola...if you see any other errors in recovery tell us here.
Good luck m8.
Click to expand...
Click to collapse
The problem was that I couldn't even get into recovery. But found thread on xda that mentioned if you turn off the tablet from download mode (pressing power and volume down) then you can use the normal three button method to get to recovery. And then yes, I wiped everything I could and it finally booted back up. Thanks for the help mate.
jalchemyst said:
The problem was that I couldn't even get into recovery. But found thread on xda that mentioned if you turn off the tablet from download mode (pressing power and volume down) then you can use the normal three button method to get to recovery. And then yes, I wiped everything I could and it finally booted back up. Thanks for the help mate.
Click to expand...
Click to collapse
No worries pal glad all went well in the end m8