Database Users

Rooted EVO stuck on white loader screen(need help)

Hey guys, first time poster long time lurker here lol, Anyways, today I rooted my EVO via the new Unrevoked version, everything went smooth, flashed Cyanogen from Rom Manager, all was good but I noticed maps/market were missing. I started messing with the phone to the point where is now sitting on the white htc evo 4g loader screen, and it wont go past that.
I have access to the hboot screen but aside from that that's it. I've tried pretty much all the options in recovery mode to no avail. I believe my problem is that I deleted the OS and my phone has nothing to boot to.
Any help will be greatly appreciated
Some info about the phone:
Hardware version 0003
2.15.00.11.19
3.70.651.1

Have you tried re-flashing the ROM? Or a different one? Or re-downloading the same one to make sure it didn't get corrupted? Have you done a full wipe (cache and data)?
If you can get into recovery, it usually is possible to get back in business somehow.

Try getting into recovery from the hboot screen. Then wipe everything twice and then reflash your rom.

Default
wiped everything and rom keeps giving me "intallation aborted"
here's what it says:
Copying files...
E:Can't symlink /system/xbin/zcip
E: Failure at line 64
symlink busybox SYSTEM:xbin/zcip
Installation aborted.

Lolwut... You shoukd be doing it in recovery...

I was doing it in the ClockwordMod Recovery, but now it wont even let me go into recovery, I just get a phone with a red triangle

im also an android noob and was in your same boat...this is what i did. i downloaded an ruu that was stock but left the root open. its a program that u can run on your pc that will program a stock rom to ur fone...i went into recovery on the fone, hit the fast boot option, connected the fone to the pc and the pc picked it up as "my htc". at that point i ran the ruu and that booted my fone into a stock rom. after that i reinstalled clockworkmod and uploaded a backup i had made w it...now im good..hope this helps

i think this is what i have to do.. im on the same problem and also a noob at this.. i have been banging my head to my desk all night lost out on major sleep.. lol this has to help.. any 1 have the link to the RUU stock?? thx in advance.. and are there any diff tips for linux ubuntu users??

Help! Stuck in ClockWork! E:Can't open /cache/recovery/log

Using: ClockworkMod Recovery v2.5.1.0
Completely powering off and/or rebooting system from recovery, keep getting stuck back into recovery and cannot get anything to boot, even after restoring the very first backup I made.
Error is: E:Can't open /cache/recovery/log
What I did:
1: Rooted using this: http://forum.xda-developers.com/showthread.php?t=808103
2: Booted into ClockWorkMod Recovery and made a backup.
3. Wiped cache/data and tried flashing midNIGHT midNIGHT ROM v3.2 CW3/EXT4 AIO (Build Your Own ROM Edition UPDATED) from here: http://lostandtired.com/android-development (it seemed to install just fine!)
4. Tried to boot but it would not go past the Samsung boot logo
5. Yanked battery, reinstalled, same problem.
6. Wiped again, tried to restore backup, now it automatically boots into recovery and shows this error at the bottom.
Please help!
EDIT:
When I try to restore a backup (that I made before doing anything) It says:
Checking MD5 sums...
Restoring system...
Restoring data...
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.
Restoring cache...
sd-ext.img not found. Skipping restore of /sd-ext.
Restore complete!
E:Can't open /cache/recovery/log

Please help me, I will pay you!
I just got this phone a few days ago... so I'm freaking out right now!
EDIT: I just installed Odin and booted into "download mode" -- downloading the stock tar now... I hope this takes care of it

Problem solved.
Odin FTW!!!

Your problem was that you flashed an ext4 only rom in rfs. You need to convert file systems to use midnight.
As you figured out, Odin puts everything back to stock.
Also, the nandroid backup and restore does not restore your kernel. If you are using to to restore, make sure you have a kernel on the sdcard to flash.

It must be going around
Man I am having the same problem you did I want to know where did you get your odin file from mine says it is installed but I dont see where to open it. I had my epic for about 3wks going crazy as well need your help but very optimistic

What are you trying to open?
If odin flashed your phone, then just turn the phone on and you have the rom that odin flashed.

relief
Prblem solved thanks guys

I've done the exact same thing. same phone same everything lol, but when i use odin, my computer doesnt recognize my samsung epic4g, i"ve restarted my computer and uninstalled and redownloaded my drivers twice. I'm trying the process with all the computers in my house, but in the meantime, could someone please give my some hints or tips as to what i could do otherwise?
EDIT: i almost get this driver error message "BlackArmor NAS 1D | no driver found"
Not quite sure why something so simple is turning out to be complicated. Also i run Windows7 32-bit

Fire n mage said:
I've done the exact same thing. same phone same everything lol, but when i use odin, my computer doesnt recognize my samsung epic4g, i"ve restarted my computer and uninstalled and redownloaded my drivers twice. I'm trying the process with all the computers in my house, but in the meantime, could someone please give my some hints or tips as to what i could do otherwise?
EDIT: i almost get this driver error message "BlackArmor NAS 1D | no driver found"
Not quite sure why something so simple is turning out to be complicated. Also i run Windows7 32-bit
Click to expand...
Click to collapse
Same problem here. I have to use a different computer. You very well may have a an internal USB problem like me. Has nothing to do with Windows. Hardware problem. Find another computer to do your flashing with.

h8uman said:
Same problem here. I have to use a different computer. You very well may have a an internal USB problem like me. Has nothing to do with Windows. Hardware problem. Find another computer to do your flashing with.
Click to expand...
Click to collapse
Alright thanks, i may have to use a friends computer at this point lol
EDIT: I've established a connection to one computer! =D so hopefully it'll flash fine
FIXED!!!

Cool
Fire n mage said:
Alright thanks, i may have to use a friends computer at this point lol
EDIT: I've established a connection to one computer! =D so hopefully it'll flash fine
FIXED!!!
Click to expand...
Click to collapse
Nice!! Welcome Back

OMG, I thought I bricked my phone... thankfully I stumbled across this thread and also this video on youtube: /watch?v=pleE_tzmiMo
I was trying to install midNIGHT ROM when this happened... I guess I need to read futher on how to properly install the ROM (Unless someone has a quick hint as to what I need to make it work)
With Odin, It will restore back to the factory firmware and work just fine, but If I re-root the phone and try to restore my nandroid backup it just hangs at the Samsung screen again. Any ideas?

just advanced restore /data and see if that gets around what is causing your phone to hang. Were you running a rom when you did the backup? You may need to reflash that rom, then advanced restore /data.
And get cwm 3 to flash midnight and other ext4 roms. There is a different one-click just for that after you do the one-click v2.5.5.

Do you have links to cwm3 and the one-click that you mentioned?
This is my first attempt at flashing the EPIC, so my backup was not a modified rom. (When I had my Hero I had no issues at all flashing a custom rom)
When this happens I am have to reflash with odin back to stock firmware, as my backups don't work for some reason. Strangely if I try to restore my nandroid backup after the stock firmware is back on there, I get the same results of it hanging on the samsung screen.

Yes, as has been mentioned, if you're going to a rom that uses the ext filesystem, you have to use the cwm3. I don't have the link., but if you look up "Randy Shear" on youtube, he has a video posted on how to install it.

[Q] cant mount /system cwm

I was running CM7.0.3 and had flashed on a different kernel. It started to run stably for a few days and then started locking up. I had it over clocked to 1.7ghz using setcpu. I decided to use Kernel Manager to put the original CM kernel back on. After it did it I got stuck in a boot loop so I went in to recovery and tried to restore the backup I had from a couple weeks before. It goes through it until it gets to /system and says cant mount /system status 1. I did a little searching and tried using PD15IMG. When I click update everything it goes through says FAIL-PU until it gets to Radio and then just sits there saying updating and never goes any farther. Can I fix this or is my phone ruined? Thanks for any help.

gamershadow said:
I was running CM7.0.3 and had flashed on a different kernel. It started to run stably for a few days and then started locking up. I had it over clocked to 1.7ghz using setcpu. I decided to use Kernel Manager to put the original CM kernel back on. After it did it I got stuck in a boot loop so I went in to recovery and tried to restore the backup I had from a couple weeks before. It goes through it until it gets to /system and says cant mount /system status 1. I did a little searching and tried using PD15IMG. When I click update everything it goes through says FAIL-PU until it gets to Radio and then just sits there saying updating and never goes any farther. Can I fix this or is my phone ruined? Thanks for any help.
Click to expand...
Click to collapse
This issue has cropped up a lot recently. I'm sorry to say it but you might have bricked it. There is a chance though. 2 questions:
1. did you use gfree to root?
2. do you have the engineering Hboot? (.85.2007?)

I did use gfree to root. and i dont have the engineering Hboot.

gamershadow said:
I did use gfree to root. and i dont have the engineering Hboot.
Click to expand...
Click to collapse
Unfortunatly at this time there is no way to fix your situation with out an eng spl. So I hate to be the bearer of bad news but the phone is done.
Sent from my Faux powered Glacier

mark manning said:
Unfortunatly at this time there is no way to fix your situation with out an eng spl. So I hate to be the bearer of bad news but the phone is done.
Sent from my Faux powered Glacier
Click to expand...
Click to collapse
Thanks even if it is bad news. I've only had the phone 10 days. Think tmo would exchange it?

gamershadow said:
Thanks even if it is bad news. I've only had the phone 10 days. Think tmo would exchange it?
Click to expand...
Click to collapse
Ya you shouldn't have a prob

Yeah, they should give you a brand new in the box, depending on which state you're in, you have either 14 days or 30 to return the phone
Sent from my HTC Glacier using XDA App

I'm stuck as well.
Don't know WTF happened. Was running Iced Glacier for a couple of months, then decided to try one of the new ROMs, so took CM7 for a spin, then went to RoyalGinger for a day or two. Things were working, but RG started freezing up, etc. so tried going back to CM7. Once I started through the flash process I hit an error when trying to format /system.
Now when I even attempt a wipe (or most anything) via CWM I continuously get errors like:
E:\Can't mount /cache/recovery/log
E:\Can't open /cache/recovery/log
E:\Can't mount /cache/recovery/last_log
E:\Can't open /cache/recovery/last_log
...and this latest time, I now got this as well:
E:\Can't mount /cache/recovery/command
I had CWM 3.0.2.4 through all of this, so should be able to flash 2.2 and 2.3 ROMs, as I understand. I can only get into CWMR and HBOOT.
I used gfree to root & have engineering HBOOT (.85.2007).
I can't get device listed in ADB, but can under fastboot. Tried flash command using fastboot to try and re-flash CWM (no idea if it would do any good), but it says cannot open the .img file.
The ONLY thing I got to work was mounting SD to USB in CWM and putting PD15IMG.zip in the root of the SD card, then rebooting and letting it run an auto update as it looks for this by default. That worked and took me back to stock...nothing else I tried would work.
Now I'm afraid of doing anything else or risk creating an expensive @ss paperweight.
Any help or suggestions appreciated as to HOW this happened, and next steps.

Recovery/Boot issue

Ok, so to start off, I have resolved this, I am just trying to find out why it happened to prevent future occurrences. I was running Calkulin's EViO 3 v1.0, HBOOT 0.76, 2.15 Radio, Stock Kernel.
So here is what happened that led up to the problem. I had just downloaded the Latest amazon App of the day (x-Scope browser pro), and used the Reboot app that comes prepackaged with Calkulin's rom to reboot the phone. Upon restarting the phone got hung at the HTC EVO 4G screen (I let it sit here for about 15 minutes). My thought was ok, something is wrong with this app. So I booted into recovery to attempt to fix the problem.
Upon booting into recovery (Ra Recovery 2.3), I was greeted with
E:\ Can't mount CACHE:recovery/command
E:\ Can't mount CACHE:recovery/log
E:\ Can't mount CACHE:recovery/log
It took several minutes for these 3 errors to process on the recovery screen, every time I navigated to a new menu they would appear again. The first thing I did was wipe my Cache, and Dalvik. This removed the errors from the recovery, however the phone still wouldn't boot. So I ran VR_Superwipe and restored my CM7 nandroid. All is good now, however I would really like to know what caused this to happen in the first place.
I tried to google it, however it appears to be a very uncommon error to get, and of the posts I found with the same error people claimed it was unrecoverable and they had to run the RUU to fix it(This was not the case).

Somehow, someway, I believe either by the install of the app, and/or you had a corrupted rom install and that you just had bad timing! I've had the same situation happen to me.
Sent from Looney Tunes Central!

tazman1963 said:
Somehow, someway, I believe either by the install of the app, and/or you had a corrupted rom install and that you just had bad timing! I've had the same situation happen to me.
Sent from Looney Tunes Central!
Click to expand...
Click to collapse
Appreciate the reaponse. Yeah that seems to be what it looks like. I've been back on cm7 since that post with zero issues.
Sent from my PC36100 using Tapatalk

[Q] What's Wrong with my Tab?

Whats up guys I have a Sprint Tab. It's not working anymore.
First off, I'm not an expert, or even half way expert. But I do follow walk through instructions well.
Initially, I was using the tab with GB 2.3 rooted and pretty much stock.
After a while I decided to put Cyanogenmod on it to improve my tab experience. It worked for about a month and a half, and then I ran into some problems with it. It started to reboot and get stuck at the boot screen and got no further. I tried upgrading to a newer build of Cyanogenmod but that kept getting stuck too. After trying different builds and a whole bunch of other things I realized that it wasn't going to work.
I figured it was an issue with Cyanogenmod and CWM.
Anyway, I decided to sell the tab and get a Galaxy S3 so I wanted to return it to stock.
I tried Heimdall one-click and Odin to get it back to stock. Guess what? No success.
The Tab initially had the Sprint Splash screen. And it is sitting here next to me stuck at the samsung screen just looping. Pretty useless.
What is the problem? Again I am far from an expert, I do NOT know what to try next.
Any suggestions?

Hey,
Your Tab did not work after new build is probably because of incorrect 'upgrade' procedures. The early CM9 build was based on a non-MTD partition system. The later build is based on an MTD partition system. You would need to restock to GB 2.3.3 going from a Non-MTD to an MTD rom.
Now that you want to re-stock, you will need
CDMA stock ROM 2.3.3 (preferable than the 2.3.5 or 6)
correct .pit file
dbdata.rfs
Flash the CDMA stock ROM while re-partition with the .pit file you have. (re-partition is a MUST going from ICS back to stock 2.3.3).
Once you are done flashing and re-partition, do a factory reset data wipe, cache wipe, dalvik wipe. see if you can do those successfully. If you get a mounting error message (most likely you will, and you will still be stuck at SAMSUNG boot loop), proceed.
Flash separately a dbdata.rfs from the CDMA stock rom you have (extract it from the ROM package and create a separate .tar for flashing or you can search in XDA). Reboot back to recovery and do another all wipes. This should take care of your problem (Hopefully).
you can do all those using heimdall or ODIN.
I hope this helps.

ill try that, thanks. But one thing.... I know you said improper installation of CM9 could cause this. But how come out of the blue it happened and not the first time I did the installation of it?
I definitely remember all the steps at least 9-10 times before I did the upgrade. So I don't think I missed anything at all. Maybe I did, maybe I didn't .
Not sure what to make of it.

ok guys I tried the dbdata.rfs flash
didn't work either.
when I booted into recovery mode, I keep seeing
E: failed to mount /cache
E: Can't mount /cache/recovery/command
E: copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
So those are the three error messages that I am getting.
What can cause these errors?

throwback1718 said:
ok guys I tried the dbdata.rfs flash
didn't work either.
when I booted into recovery mode, I keep seeing
E: failed to mount /cache
E: Can't mount /cache/recovery/command
E: copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
So those are the three error messages that I am getting.
What can cause these errors?
Click to expand...
Click to collapse
Try this. Follow the link provided.
http://forum.xda-developers.com/showpost.php?p=27096519&postcount=2

Make sure you tab isn't plugged into a dock, u had major problems trying to flash that way. Sometimes u can't even have it plugged into a charger.
Sent from my ADR6425LVW using Tapatalk 2