Database Info

Don't think it's bricked...But?

Hey guys, this is going to be my first post up here, usually just read up and find what I need no problem but today my first problem arose with my G1. I'll wrap it up quickly:
-Just got a new G1 through an insurance claim.
-Rooted no problem running SuperD v1.9.2
-Curiosity got the best of me and I attempted to try out CaNNoN Complete Eclair
-Didn't work correctly so I restored back to my most recent backup of SuperD v1.9.2
Once I restored, I found that all I had were the apps the SuperD includes built-in to his rom. Not one downloaded app was found on my phone. When I check in the market it still says all of them are installed, wont let me open them at all though. So of course I try to fix it myself and now my SD card just says Lost.Dir on it. Also now it goes through the T-Mobile G1 screen, begins the Super D boot image, and then goes black. I still have access to recovery, what happens now?

Mini update: Partitioned my SD again and now I get past the boot image, still no apps and I can't even reinstall them! Any help would be appreciated.

Mini update: Partitioned my SD again and now I get past the boot image, still no apps and I can't even reinstall them! Any help would be appreciated.

joe.kerwin said:
Mini update: Partitioned my SD again and now I get past the boot image, still no apps and I can't even reinstall them! Any help would be appreciated.
Click to expand...
Click to collapse
I cant remember exactly but I think theres something like repair ext or something like that, I think that is the thing to do when u cant install apps,
Dont take my word on it though , wait for someone more knowledgable to help i guess

I had the same problem as you but i've downgraded my phone and now my phone is urooted and the problem is still the same. when appears the android logo, the screen goes black. is there any soltion?
Any help for me?
thank you

jpjpr said:
I had the same problem as you but i've downgraded my phone and now my phone is urooted and the problem is still the same. when appears the android logo, the screen goes black. is there any soltion?
Any help for me?
thank you
Click to expand...
Click to collapse
joe.kerwin said:
Mini update: Partitioned my SD again and now I get past the boot image, still no apps and I can't even reinstall them! Any help would be appreciated.
Click to expand...
Click to collapse
both of you wipe data, dalvik, and sd: ext partition. repair ext partitions and reflash. you're not bricked if you can get past the t-mobile g1 screen or can get into recovery or bootloader.

Thank you r3s-rt, for giving me hope but honestly, i didn't understood what I need to do.
Thank you

I'm unrooted now and i can't pass the android logo, I can't get access to the operating system. How can I do the partitions, repair and reflash?

you can try to start over and get it to 1.6 again by following this sites guide
upgrade.android.32teeth.org

already done that, but with 2 updates. No success

jpjpr said:
already done that, but with 2 updates. No success
Click to expand...
Click to collapse
Buddy you need to first get a plain ( original ) 1.6 Rom as an update.zip on your sdcard boot into recovery , do a wipe THEN apply the update THEN reboot and wait , it will take a while to boot. DO NOT WIPE AFTER THE UPDATE is applied , you must let it *first boot* so it can rewrite the missing files..

where can I get that file? i've tried some but says no signature

I've already done that, nothing happens, the problem is still the same, I will try to flash HardSPL and see what happens

i was reading the topic of SPL and my phone is now unrooted, i can't do anything, i don't know what to do with my phone!

If you are un_rooted then you need to find a original un_rooted Rom , that was not signed with the test keys , ,if you are rooted you need to find a rooted Rom signed with the test keys , if you try to modify any of these roms before flashing them YOU NEED TO RE_SIGN THEM with the right keys , or you will get that no signature error ..

do you know where can I get that? Sorry about all the questions. Thank you

Everything that you need is in the link at the bottom of dan0zone's post right above you (#15). That is a walkthrough specifically geared toward G1's. The original image file for 1.5 is one of the first links he includes. He's even got the links for RC29 (US) as well as RC7 (UK)!
Remember! First boot takes FOREVER!!!! Let it sit for at least 5-10 minutes before doing anything.
Good luck!

I've already done that but nothing happens...what happens if I try to flash UK rom in USA phone? I don't know what should I try more.

is there any cupcake update or any way to don't need to slide the keyboard when ask for sign in or create a new google account? I can now access to the Operating system in Safe mode when I got almost bateryless but when i need to slide the keyboard to sign in my google account, the phone shutdown again. Any sugestion? I'm almost there.
Any help for me?

jpjpr said:
is there any cupcake update or any way to don't need to slide the keyboard when ask for sign in or create a new google account? I can now access to the Operating system in Safe mode when I got almost bateryless but when i need to slide the keyboard to sign in my google account, the phone shutdown again. Any sugestion? I'm almost there.
Any help for me?
Click to expand...
Click to collapse
sorry, man. i have a tendency to just disappear and forget where i posted. are you using cyanogens or amon_ras recovery? i suggest amon_ra's. select the "wipe" option. then choose the first three options that appear. then flash super d 1.9.2.
or just follow the rooting process all over again. if you can't get into recovery.
(recovery is accessed by holding the home key while powering the phone on.) if you need anything else, please pm me. i'll always respond to a pm, but very rarely to a post. sorry.

[Q] samsung galaxy player 50

My sister have a Galaxy Player 50 with eclair...this PMP seems to be the same as the galaxy 3 (same resolution...and some other things) so can I flash lestatious or other rom on it ?
This hardware is not a phone...but maybe ?
Maybe I can try to flash...but if the pmp become soft bricked...it's over since i can't found an galaxy's 50 firmware...

Darius, I'm stuck with a brick galaxy player. I can try to flash with a galaxy 3 firmware if you want
Do you know how to make a dump of your device so you can share with me the original firmware?
http://forum.xda-developers.com/showthread.php?p=14493414

I don't know...but I'll try to find

Thanks!
I tried the firmware of galaxy 3, but didn't work

I dont think that its possible, first of all, despite being an android device, it doesnt have radio features, gsm 3g etc, only wifi, there are features that our phone does not support

Anyone found a solution for this yet? Not being able to test this device to it's full potential is really frustrating. Games are laggy and apps just do not run smooth on this one.
Has anyone tried z4root on this? I did and it freezes at "acquiring root shell".
@fedeff: how did you brick it?

Darius_AWS said:
My sister have a Galaxy Player 50 with eclair...this PMP seems to be the same as the galaxy 3 (same resolution...and some other things) so can I flash lestatious or other rom on it ?
This hardware is not a phone...but maybe ?
Maybe I can try to flash...but if the pmp become soft bricked...it's over since i can't found an galaxy's 50 firmware...
Click to expand...
Click to collapse
First root using One click root.
Give these commands in Terminal emulator
su
mount
Check for system partition.Suppose it is stlx (x=6,7,8 etc depending on system partition)
give this command to dump system...
dd if=/dev/block/stlx of=/sdcard/factoryfs.rfs
Copy it from sdcard and upload. I need to check it then i can help u out.

arunmcops said:
First root using One click root.
Give these commands in Terminal emulator
su
mount
Check for system partition.Suppose it is stlx (x=6,7,8 etc depending on system partition)
give this command to dump system...
dd if=/dev/block/stlx of=/sdcard/factoryfs.rfs
Copy it from sdcard and upload. I need to check it then i can help u out.
Click to expand...
Click to collapse
I'd gladly try it as long as Samsung gives me firmware, don't want to end up with a nice looking little brick here.
Is there any way that that an installer/firmware file could be saved in the device for backup purposes or something?

anon3524 said:
I'd gladly try it as long as Samsung gives me firmware, don't want to end up with a nice looking little brick here.
Is there any way that that an installer/firmware file could be saved in the device for backup purposes or something?
Click to expand...
Click to collapse
factoryfs.rfs is ur firmware backup....

@arunmcops: Thanks for the instructions. If someone try this and upload it'd be great for me.
@anon3524: I accidentally reseted the device to factory, trying to fix a problem with wifi (it suddenly stopped working one day).

arunmcops said:
factoryfs.rfs is ur firmware backup....
Click to expand...
Click to collapse
Ok, I am down to do this process you just explained as long as you or anyone explains to me how to recover the device with this "factoryfs.rfs" in case it gets bricked. You'd have to explain with detail how to grab this file and what to do with it etc. Also, if you could give further details on the initial process, that'd be great since a few things are unclear (to a brave noob like me).
Other than that, I am willing to try it to see the results.
BRING IT OON! *warface*

@arunmcops - I've got one of these, so have uploaded the file you wanted here - sorry, not allowed to post links yet:
dl.dropbox.com/u/6491656/Samsung/factoryfs.tar.gz (please don't flash this, its not a full rom)
I haven't made any changes to the base firmware other than renaming a couple of the phone.apk's to .old (cell standby was eating battery, and this device doesn't have a sim).
For fun, i've also uploaded a dmesg log
dl.dropbox.com/u/6491656/Samsung/dmesg.log
One other thing, i think the partition layout might be slightly different on this (might be wrong, don't have the phone) in that the internal sd card is mounted as /sdcard and the external one is /sdcard/sd.
Hope this helps!
Chris

@ctaylr Thanks for uploading the file.
I tried to load it using Odin, but it get stuck while uploading the file. The device is detected, but I think it's not transfering anything.
Is it possible to restore it form sd card?

fedeff said:
@ctaylr Thanks for uploading the file.
I tried to load it using Odin, but it get stuck while uploading the file. The device is detected, but I think it's not transfering anything.
Is it possible to restore it form sd card?
Click to expand...
Click to collapse
Hi...thats probably because it isn't intended as a flashable rom. Its just a dump of the stock firmware so that arunmcops asked to see to see if it had any resemblance of the galaxy 3 f/w, to see what we'd have to do to get a working custom ROM on this device..
Please don't attack it with any kind of Norse God ...especially until there is a confirmed route back to stock. All thats contained in the files is what you have on your device already - so there is also absolutely no point (for now).
If your having trouble with your device now, you could try doing a factory reset or playing about in Kies - i've fixed my device once after I got curious and flashed a custom ROM on here (which fyi completely messed it up - something like E:multi_csc: error: open /efs/imei/mps_code.dat because we dont have an IMEI code on this device) and then got it back working again - unfortunately i can't remember exactly what I did. Otherwise if this doesn't work I'll see if i can make a working stock package for Odin.

@ctaylr, yes I'm having problems with my device. It got soft bricked. I couldn't make it work using Kies. The only thing I can do is to start it in Download mode. If you can make a working package for oding that'd be great
This might help
http://forum.xda-developers.com/showpost.php?p=9515709&postcount=14
Thanks!

@fedeff Ok. i'll have a look over the weekend and see if i can make something that flashes.
Quick questions
1) do you have the 8gb or 16gb version?
2) have you tried going into recovery utils and doing a "wipe data/factory reset?" - you can do this by holding down home, volume down and volume up while turning the unit on - i seem to remember this fixed it for me, but it probably depends on how far Odin got while flashing. If your unit is already bricked, i can't see it doing much further harm
Thks

ctaylr said:
@fedeff Ok. i'll have a look over the weekend and see if i can make something that flashes.
Quick questions
1) do you have the 8gb or 16gb version?
2) have you tried going into recovery utils and doing a "wipe data/factory reset?" - you can do this by holding down home, volume down and volume up while turning the unit on - i seem to remember this fixed it for me, but it probably depends on how far Odin got while flashing. If your unit is already bricked, i can't see it doing much further harm
Thks
Click to expand...
Click to collapse
1) I have the 8gb version
2) By doing "wipe data/factory reset" is how I got it soft bricked. (the device wifi suddenly stopped working, and I thought that would help) After that it kept entering in the recovery mode. Then I tried to flash it with odin, now the only thing I can do is enter the download mode
Thanks again for helping me!

News?
Hi! I also like the others I am interested because my Galaxy player has 50 brick and I need someone to do dump the firmware so I can flash through odin! Please would you be my salvation and many other who have this player and would like to fix without waiting for the assistance of a month
Waiting for an answer I greet and thank all users who want to help me
sorry if English is not correct, but I'm using google translator (I'm Italian)
EDIT:
listen to me: http://forum.xda-developers.com/showthread.php?t=726673 This is the guide on how to get the dump of your fimrware if someone kindly did this process with its galaxy player 50 and then upload the file . tar obtained would help all

I don't think it is as simple as that.
If you fully read that topic above, it tells you. That will ONLY tarball the files in the /system folder. It doesn't dump the the bootloaders, efs or produce the initrd, which is also part of the firmware.
In fact that backup is exactly what i linked to earlier here, and doesn't flash properly through Odin. I don't know Odin very well (i use a ZTE Blade and clockworkmod normally ) but i'm going to take an educated guess it needs all of this information to successfully flash the player, and trying to flash without all of that probably won't work so well.
If i'm wrong, please let me know and i'll do what i can to help.

ctaylr said:
I don't think it is as simple as that.
If you fully read that topic above, it tells you. That will ONLY tarball the files in the /system folder. It doesn't dump the the bootloaders, efs or produce the initrd, which is also part of the firmware.
In fact that backup is exactly what i linked to earlier here, and doesn't flash properly through Odin. I don't know Odin very well (i use a ZTE Blade and clockworkmod normally ) but i'm going to take an educated guess it needs all of this information to successfully flash the player, and trying to flash without all of that probably won't work so well.
If i'm wrong, please let me know and i'll do what i can to help.
Click to expand...
Click to collapse
ok then I'm sorry I read the topic in a hurry and did not realize that you can not do what I say but re-reading now I understand!
ctaylr what do you advise me to do then? wanted to try an get into recovery and restore but I think the 3 keys are disabled enters only download ..
Google traductor sorry

[Q] HTC One S(ville) black screen, thats it... just a black screen, what can i do???

I was working fine, enjoying my new HTC One S with CM9 rom installed. Well the battery life wasnt the best on it, and i didnt install the custom kernel. So I looked for the custom kernel download(on my phone, not on my computer) and i found a .zip file. Well I thought that you could just download the kernel straight to my phone and open it up with "Rom Manager" which i did, it than said i needed to reboot the phone in recovery to continue the installation, so I did... it took me to recovery "to continue the installation" well than I looked away, looked backed down and it was black.... and i have tried powering up, booting into boot loader, booting into recover, and nothing... its just BLACK! nothing works, its literally useless ATM. I really messed up, is there anyway to fix this? Thanks in advanced!
----EDIT----
I think I accidentally flashed the kernel like i would normally flash a rom.... cause i downloaded the .zip file(directly to my phone, not using a computer), than i tapped the download and it asked me if i wanted to open it up with rom manager, so i did. and i think rom manager thought i was flashing a rom, when i wasnt, it was a kernel.... am i screwed? or is there anyway out of this?

Do you know the exact kernel you flashed--where did it come from
Some you need to extract and push
Assume you just tried to boot into bootloader thru phone buttons
Does your pc recognize your phone when plugged in, if so can you open a command window and try to access phone as in adb devices then adb reboot bootloader
assuming you are familiar with sdk adb/fastboot comands
otherwise i don't know what else to say--may be bad--sorry

Came from an XDA thread
Here is where it came from: http://forum.xda-developers.com/showthread.php?t=1708676 from "sun90" (half way down the page "CM9 KERNEL remix edition.zip - [Click for QR Code] (5.53 MB, 9 views) ")
i downloaded that straight to my phone and opened it up with Rom Manager, which i think the app took it as a rom, and installed it like a rom even though it was not a rom. I just tried to access it through adb, it comes up with no devices my PC does recognize it when i plug it in though...
Ive tried to get into bootloader tons of times, it just stays black... :'(
Thanks for your answer!

You flashed a galaxy s2 kernel on your one s? why would you ever think that was a smart thing to do?
Looking at the updater script in that zip it seems it wipes some partitions, the partitions on a SGS2 and the ONE S are different, so if that script accidentally wiped say the hboot partition, or some other critical-for-boot partition, you have a fully bricked phone.
For any devs that may know what partitions are what on the One S, the script wiped
mmcblk0p7, and wrote a zimage to mmcblk0p5
---EDIT---
Normally this is a cwm flashable zip on the Samsung Galaxy S II, which is why rom manager flashed it, as it met all the requirements, the only issue is, it was not made for the ONE S and probably overwrote some important things.

I tried for hours and hours to fix the same issue on a friend's One S (same symptoms, not same cause) to no avail. I tried QPST and telnet and a ridiculous amount of things. Had to bring it to the store and get a new one.
Good luck, but I don't believe there's anything you can do to fix it.

Just answered your question in the help thread, Didnt see this thread too !
Im afraid its not looking good, I think your best bet would be to call your provider and blame it on an OTA update.
And hope for the best

Alright, thanks for the help!
Well it looks like i bricked my phone than.... I thought that CM9 was only on the One S, so I just looked for the CM9 kernel, which obviously was for the sg2, i feel like such a dumb ass now! haha well thanks for all the help guys! ill be heading to the t-mobile store today to blame it on a OTA:]

yeah, others wont agree with what your about to do but........
just act like a complete noob, dont mention anything about software / firmware / ROMs / bootloader etc ect
just say your phone made a noise, you selected update and it died lol

good luck--I know it is heartbreaking
not sure of your situation with carrier, but you could go thru Retention if needed

Hi peeps.
i'm very new to all this but sort of know the basics
i'm running on Axiom now but tried to flash cm10 but after install i got a black screen so had to do a restore.
Today i just flashed venom and after the instal process is done, i hear the start up music but nothing on the screen.
I have had 3 other roms on my phone and never had a problem!
these are the steps i do
download rom - place on sd
put phone in recovery
reset factory
reset cache
install from sd
when it finish's reboot
blank screen.
Am i missing something?
Any help would be great and i can't post on the thread because i'm a noob with less than 10 and dont want to spam my way to the 10 :silly:

you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe

rugmankc said:
you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe
Click to expand...
Click to collapse
Thanks but i think that is now the least of my problems!
I used Goomanager and installed CM10, When I did it i installed teamwin recovery. It started to do a lot of strange things, when it finally rebooted i got a load of errors "phone is not working" nearly every 10 seconds?
it will not connect via usb, i discovered the the SD was not mounted.
I tried to mount the SD but it doesnt work, so i rebooted to recovery and tried to mount there but its coming up with - error unable to mount? ive tried everything but no joy
please please help
Thanks:crying:

see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands

rugmankc said:
see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands
Click to expand...
Click to collapse
I've got a mac
not sure what fastboot is.
I'll check out the link, and thank you very much for trying to help:good:
sorry i do know what fastboot is, yes can get in to it. but ive gone from CWM to teamwin recovery if i go in to the recovery section but that wont let me do anything because the mount. cant even load the phone up

I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track

rugmankc said:
I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track
Click to expand...
Click to collapse
im going to use someone elses alp top with windows. i'll ytry the all in one thing because thats how i rooted it in the first place. thanks for helping it means alot

good luck on it

Can my Nexus be fixed?

Hello all
I suspect that either my Nexus has a hardware fault (internal memory) or I bricked it somehow.
For the past few weeks the phone has been getting stuck on the google boot screen quite a lot - It takes several attempts
to start up each time so I've been trying to keep the battery from running down.
The other day while I was attempting to switch roms I put the stock img on my SD card but when I went to flash it CWM
couldnt mount my (internal) SD Card. Senior forum member Caliban2 suggested that it could be my recovery so I installed CWM 6.0.0.7 non-touch using fastboot and, like magic, the phone started up -though I suspect this may have been luck.
I rebooted the phone out of curiosity and it got stuck on the google boot screen - no amount of battery pulling and restarting could coax
it back to life, so I went into CWM again to discover that it could not mount the SD Card, I was getting the 'cannot mount' and 'E:Unable to open ums lunfile(no such file or directory)' error messages. My windows 7 PC could see the phone but said that their was non memory inserted. Out of curiosity I installed CWM 5.0.2.0 but that produced the same results.
So now my phone appears dead, is the internal memory or something related to it is broken? I have seen things on here about using an unbricking tool in Debian Linux or flashing stock using odin but I confess that I have not tried these solutions and don't fully understand them (yet).I wussed out and dropped the phone into a local repair workshop, I imagine they will be trying these same steps themselves and they say it will take them a few days to get back to me.
My problem is that I need a phone for work and I gave my backup phone (HTC Hero) to my dad recently. Should I just take the plunge
and go out today and buy a new phone? Or is there a reasonable chance that these guys can fix my nexus s, or that I might be able to?
I'm a relative 'noob' at this so I thank you all for your advice in advance, it's much appreciated.
Derek

Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.

Thanks, will do. It's in the shop at the moment, I suspect this is probably what they're doing now.
Perhaps subconsciously I'm just looking for someone to tell me it's irreparable so I can rush out
and pick up a Galaxy Nexus.
Harbb said:
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Click to expand...
Click to collapse

Hey Harbb
Just wanted to give you an update on this, got it back from the shop who said they would need to send it to Samsung for a hardware repair, didn't expect it to work but fastbooted the stock bootloader, radio and image to the device and it's now working!
I've already moved onto a Galaxy Nexus on contract but at least now I can make a bit of money back off my old phone.
Thanks again for the advice
Derek
Harbb said:
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Click to expand...
Click to collapse

[Q] Mishandled ROM Upgrade

I am relatively new at ROMs and I installed CyanogenMod 10 on my AT&T HTC One X (US) a couple of months ago. Recently, I tried upgrading to the M2 release of CM10.1 using the evita package which I understand is the US version of the ROM. I followed the same instructions I used to install 10.0 for 10.1. However, the installation froze and did nothing for a few minutes and gave me the message "no MD5 file found". I shut the phone down and restarted, but the phone would no longer start. I did a "system wipe" to get ride of the OS so I could re-install it, but now, my computer won't recognize my phone when I connect them and I can't move the CM10.1 zip file from my desktop to my phone. I have nothing already on the phone I can flash besides Team Win Recovery Project which is what I use for Recovery. I have no recovery files.
Did I just paperweight my phone, or is there a way to salvage this situation.

sliceroo said:
I am relatively new at ROMs and I installed CyanogenMod 10 on my AT&T HTC One X (US) a couple of months ago. Recently, I tried upgrading to the M2 release of CM10.1 using the evita package which I understand is the US version of the ROM. I followed the same instructions I used to install 10.0 for 10.1. However, the installation froze and did nothing for a few minutes and gave me the message "no MD5 file found". I shut the phone down and restarted, but the phone would no longer start. I did a "system wipe" to get ride of the OS so I could re-install it, but now, my computer won't recognize my phone when I connect them and I can't move the CM10.1 zip file from my desktop to my phone. I have nothing already on the phone I can flash besides Team Win Recovery Project which is what I use for Recovery. I have no recovery files.
Did I just paperweight my phone, or is there a way to salvage this situation.
Click to expand...
Click to collapse
Are you able to get into recovery?

joelrwise said:
Are you able to get into recovery?
Click to expand...
Click to collapse
Yes. I can get into recovery and the screen that tells you the root status of the phone.

sliceroo said:
Yes. I can get into recovery and the screen that tells you the root status of the phone.
Click to expand...
Click to collapse
If you can get into recovery then you aren't bricked just yet! If you have an sd card reader on your computer or know somebody who does thats one way you could get a new rom on your phone to flash. Most recoveries have a way to let you connect your phone to your computer for file transfer while in recovery. I believe in TWRP the option is in the Mount are. I could be wrong though. You just need to figure out how to get a new Rom on your phone. If none of the above work, one trick that has always worked for me, would be to put your sd card into someone elses phone, and download a known working rom onto your sd card via theyre phone, and just put it back into your phone. Hope i helped. Let me know how it goes man. I've been here before haha

joelrwise said:
If you can get into recovery then you aren't bricked just yet! If you have an sd card reader on your computer or know somebody who does thats one way you could get a new rom on your phone to flash. Most recoveries have a way to let you connect your phone to your computer for file transfer while in recovery. I believe in TWRP the option is in the Mount are. I could be wrong though. You just need to figure out how to get a new Rom on your phone. If none of the above work, one trick that has always worked for me, would be to put your sd card into someone elses phone, and download a known working rom onto your sd card via theyre phone, and just put it back into your phone. Hope i helped. Let me know how it goes man. I've been here before haha
Click to expand...
Click to collapse
I went into TWRP Mount and it allowed me to mount the phone. I went ahead and did that, but Windows told me that I had to format the disk. I agreed and Windows formatted it. Afterwards, I successfully copied over the CM10.1 Evita M2 zip file and the lates Gapps zip file. I then went to TWRP's install section and flashed both zips. TWRP told me both happened succesfully. However, while flashing over the CM10.1 file, it told me that no MD5 file was found and that it was just going to skip that. Then, it formatted some mke5 partition and then went ahead and finished. I wiped the Dalvik cache and the system Cache and restarted the phone. It is currently stuck at the "HTC Quietly Beautiful" intro screen and won't boot past that. Is there something I missed?

If that 10.1 already failed because of an MD5 problem, I wouldn't have tried to flash it again - the file probably has some problems in itself and either needs to be re-downloaded or just won't work.
Just flash the stock firmware or something - and use an MD5 checking program.

Pennycake said:
If that 10.1 already failed because of an MD5 problem, I wouldn't have tried to flash it again - the file probably has some problems in itself and either needs to be re-downloaded or just won't work.
Just flash the stock firmware or something - and use an MD5 checking program.
Click to expand...
Click to collapse
The thing is TWRP returned the status as successful despite missing the MD5 file. I'll try flashing over another package and if that doesn't work, I'll try flashing over CM10. If that still doesn't work, I'll just do stock firmware if I can find it somewhere, I guess.

In the future, making a backup is really awesome. Not saying that like "I told ya so" - but I've used them so many times myself, it's really great to say, "oops, I overlooked something" and then be able to just go back to a perfect snapshot of how things were before.
Also, how long did you let the phone sit at the boot screen ? It can hang for quite a while on the first boot.

Pennycake said:
In the future, making a backup is really awesome. Not saying that like "I told ya so" - but I've used them so many times myself, it's really great to say, "oops, I overlooked something" and then be able to just go back to a perfect snapshot of how things were before.
Also, how long did you let the phone sit at the boot screen ? It can hang for quite a while on the first boot.
Click to expand...
Click to collapse
Yeah I would just reflash a ROM that you've used before and that you know works. Chances are if the cm10.1 didn't work the first time its probably not going to the second time. And he has a point. First boot always takes forever. I've flashed a couple ROMs and thought I was bootlooped but I let it sit for a good 5-10 minutes and the setup screen finally came up.

joelrwise said:
Yeah I would just reflash a ROM that you've used before and that you know works. Chances are if the cm10.1 didn't work the first time its probably not going to the second time. And he has a point. First boot always takes forever. I've flashed a couple ROMs and thought I was bootlooped but I let it sit for a good 5-10 minutes and the setup screen finally came up.
Click to expand...
Click to collapse
I had no idea that it could take that long. I guess I'll just turn my phone on and see if it wants to start. I'll leave it going for a good five to ten minutes this time. Shutting the phone down while its still in the intro screen doesn't damage the OS, does it? Thanks for the advice so far guys, I really appreciate it.