Database Info

[Q] samsung fasinate - bricked my phone - verizon tecs clueless

Hi, I am new to all of this, but Im a quick learner. I rooted my phone and have superuser permission. I have installed multiple applications that will help me to perform ROM installs all of which still do not help. I even tried the three button solution, however I am still getting the same message when I go into recovery mode. It is as follows: E: failed to varify whole-file signature then under that I get: E: signature verification failed, instalation aborted.
I tried applying sdcard update. zip, wiped out cache partition, factory reset, etc...
I have tried everything. I tried using Mod Manager, I get the downloads but then when i try to install after I make sure to click backup rom and clear cache, it boots to the rom screen, (not really sure what you guys call it, sorry) and I get that same message, the signature failed, et...
my phone info is as follows: SCH-I500, I500 Commercial Package_DL9 To EA28 (I think verizon automaticly updated for the emergency dial) code 200
hardware version i500.04 firmware version 2.1update.1, baseband version S:i500.04 V.EA28, kernel version 2.6.29 and last but not least build number SCH-I500.EA28
Now saying all of that, I tried all of the above steps prior to this automatic update and it still did not work. I still received the signature message.
I even tried Voodoo, as well as DL30, Superclean, none of which will pass the signature autentacation. I want to try to get past this as I am having my phone replaced due to burn in and want to get the steps right so I do not BRICK my phone after it has been replaced. If this one bricks, it wont matter to much because I will have the new one on Monday.
Any help would be greatly appreciated. I love this tecky stuff and want to be knowagable on how to get past this message so I can go full force on Monday.
Thanks,
EssyG

Also I checked the site and tried everything but still won't work.
Sent from my SCH-I500 using XDA App

You will need to flash a new Recovery via ODIN which you can find below for your Samsung Fascinate:
http://forum.xda-developers.com/showthread.php?t=782204
&
Also read this http://forum.xda-developers.com/showthread.php?t=790004

Thank you, up and running 2.2, will post screen latter! Now I need to get my old phone back to stock so I can send it back to veriazon. YOU ARE THE BEST!!
P.S. I love your idea about the 10 post allowence to post on other forums.
Essy G
If o.k. I will post what I did and that way new users will be able to follow directions. I am a newbe but have become addicted to this stuff. THANKS!!

now I bricked my phone... lol
Now let me start by saying I loved 2.2, no problems with it at all. but when battery ran out I wanted to clean stats in cwm green and the screen would not come up, sd would not mount any how I tried to start over, flashing oden, all the steps, but my drivers will not stay for some reason after flashing I need to uninstall the reinstall drivers or they are not recognized, really sucks, any how I got frustrated so while in odin I pulled the plug, lol literally, and now have a pic of a "phone" then ".." then triangle with (like my icon here)"!" then ".." picture of "computer". I called verizon and there sending me yet another phone. lol my question is, will they be able to unlock it and see that I had 2.2 on it? does anyone know what they do with the phones we send back? Basicly I want to know if they can unlock that being I can't. and if so, will they see the 2.2? Any sugestions?

Anyone there?
Any one there? Also I am debating, do I wait for official release. I heard it was coming out 2/22/11. If I put dl30 on new phone again and they release the update, will I still get the automatic update via verizon? If so will I lose root? Any comments on post #5? I can't believe I had it running I totally messed it up. Thank goodness when I called verizon I got two girls at tec support, lol while I am a girl, I am a tech lover, I acted like I had no idea what happened, well they didn't either, lol So just waiting on new phone to come in, yet again so I am getting everything ready to quickly install dl30 to new phone again. Hopefully I do not lose drivers again, as it seems that once I flash in odin, the hardware icon disappers as if drivers are not installed. any how, I was just wondering if anyone had an answer to post #5 so that when I return the phone, I am not caught, lol that would really stink! Plus I am board, took off of work because my kids are sick and now I have a bad cold also, so any comments would be great!! Besides I need to be here to sign for new phone.
Thanks,
Essy g

[Q] Help with ATRIX!!!

Ok, so i have a new Atrix that came stock with 2.3.4/4.5.91 from AT&T. I Rooted it, unlocked the bootloader, and installed this Recovery: recovery-en-goapk-0630-1029. Then I tried to flash CM& Beta, and all hell broke loose. on reboot, it got stuck on the Dual Core screen, and I can do anything else, because now i get battery to low to flash error. What mode does the phone need to be in so it will charge, and what do i need to do to fix this?

I have a Droid two global by Motorola and bricked it at one point in time. I had the same issue. I am not sure if this is the case with the atrix, but it very possibly could be. In his state often Motorola phones will not charge themeselves. There are a few options. The easiest is if you have a buddy that has the same phone as you. You can borrow the battery from his phone. You could also simply buy another battery. The honestly best, but hardest method is to buy or make your own Motorola factory cable. You can look that up online. After you have a charged battery simply find instructions to recover your phone via fastboot, or sbf. Hope you get it working
P.s. if this helped you, or you simply appreciate me taking the time out of my fourteen year old life then please press the thanks button

Well, I was able to rescue my phone lol. After the panic set in and I was calm again, I searched the house and found my microSD to SD adapter, and downloaded the "alien" ROM, entered recovery and was able to install it. After that phone booted up properly and went it charge mode....thank God lol. So now I'm left with another series of questions...why wouldn't the recovery install the backup I made, and wouldn't the CM7 beta not install, but the alien rom installed just fine? I might to go to the forum specific area for androids foe this one...

D150shorty said:
Well, I was able to rescue my phone lol. After the panic set in and I was calm again, I searched the house and found my microSD to SD adapter, and downloaded the "alien" ROM, entered recovery and was able to install it. After that phone booted up properly and went it charge mode....thank God lol. So now I'm left with another series of questions...why wouldn't the recovery install the backup I made, and wouldn't the CM7 beta not install, but the alien rom installed just fine? I might to go to the forum specific area for androids foe this one...
Click to expand...
Click to collapse
Gonna answer my own question here...I had the wrong recovery installed. For others wanting to install CM7, use rom manager, and install the most current version of clockworkmod recovery and make sure to update it. This was my golden ticket to CM7 love

[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.

[Q] How to root a Motorola Droid Maxx Dev Ed

I am currently running 4.4.4 but I want to go back to 4.2.2 stock rom that came with the phone and I want to root it. My bootloader is unlocked. And I did a recovery and wiped the phone within Android and it just went back to 4.4.4 not 4.2.2 like it did before. I went to fastboot and tried to go into recovery and wipe the cache but the phone just rebooted. I was able to wipe the cache before...maybe I did something wrong...I am very new to this and have downloaded so much stuff to do this but im sooooooo lost

Also Fastboot says that device is UNLOCKED, Status Code 3

Knight71 said:
I am currently running 4.4.4 but I want to go back to 4.2.2 stock rom that came with the phone and I want to root it. My bootloader is unlocked. And I did a recovery and wiped the phone within Android and it just went back to 4.4.4 not 4.2.2 like it did before. I went to fastboot and tried to go into recovery and wipe the cache but the phone just rebooted. I was able to wipe the cache before...maybe I did something wrong...I am very new to this and have downloaded so much stuff to do this but im sooooooo lost
Click to expand...
Click to collapse
factory resetting and wiping does nothing but remove data.
to get back to an older version, you will need to get the factory firmware file and flash it to the phone with rsd lite (tutorials can be found through google). afterwards, find a custom recovery that is compatible with the version you installed, install it, then grab the superuser flashable zip and flash in recovery to get your root back.

Sorry it took me so long to reply back. I drive truck OTR and I put in some long days. Ok I have some time to get this down and understood I will be going for my hometime at the end of this month for about 4 days because my phone is the only way that I can get online out here.
So I have a XT1080 Dev Ed. And I have a copy of a factory image from Motorola for my phone TMO_RETAIL_XT1053_4.2.2-13.9.0Q2.X-116-X-17-57_MR1_1FF.xml.zip. Now how do I flash it do I have to unzip it or put it in a folder or??? And also (custom recovery that is compatible with the version you installed) do you mean using TWRP. Also what does Status code 3 mean and do I have to turn of Write Protection and if so how.
I am so sorry for being a noob at all of this. My old phone was a Droid Global 2. It was ok until it got old and unresponsive I used FoxFi to get online while I was out on the road. Then I decided to go and get me a new phone and I hear about the Droid Maxx and the awesome battery life on it so I decided to get it...But I had to Pay full price for it. 650 plus 50 for tax 700 total. The reason behind that is that I have unlimited data and I did not want to lose it.

Knight71 said:
Sorry it took me so long to reply back. I drive truck OTR and I put in some long days. Ok I have some time to get this down and understood I will be going for my hometime at the end of this month for about 4 days because my phone is the only way that I can get online out here.
So I have a XT1080 Dev Ed. And I have a copy of a factory image from Motorola for my phone TMO_RETAIL_XT1053_4.2.2-13.9.0Q2.X-116-X-17-57_MR1_1FF.xml.zip. Now how do I flash it do I have to unzip it or put it in a folder or??? And also (custom recovery that is compatible with the version you installed) do you mean using TWRP. Also what does Status code 3 mean and do I have to turn of Write Protection and if so how.
I am so sorry for being a noob at all of this. My old phone was a Droid Global 2. It was ok until it got old and unresponsive I used FoxFi to get online while I was out on the road. Then I decided to go and get me a new phone and I hear about the Droid Maxx and the awesome battery life on it so I decided to get it...But I had to Pay full price for it. 650 plus 50 for tax 700 total. The reason behind that is that I have unlimited data and I did not want to lose it.
Click to expand...
Click to collapse
unzip the factory file to a folder, inside there is a "xml" file, that is the target file you load into rsd lite.
before you start with rsd you will likely have to edit the xml first. right click it and choose edit. you are looking for any lines that contain "getvar". if you see that, delete the hole line from end to end (may be more than 1), then close and save when prompted.
now you can flash with rsd as usual.
yes twrp or cwm
status code 3 just means that the bootloader is unlocked.
as far as i know that should be all there is to it, i dont have this device so im just stating general moto flash procedures. if you found something about write protection that im not aware of, post a link and ill have a look at it.
here is the su zip you will need to install root after you install twrp or cwm http://www.mediafire.com/download/nwxoj8b3k1u8xtv/UPDATE-SuperSU-v2.01.zip just flash as is in recovery.
btw, i have unlimited data too

Got to love Verizon. My bill would be so expensive if I got on there 10GB Tier plan...I would go way over that. But the things that we do to keep it...like buying a 700 dollar phone...LOL
What is getvar and also how do I see the partitions on my phone?
Well I have to hit the road but will be back on here tonight.

Knight71 said:
Got to love Verizon. My bill would be so expensive if I got on there 10GB Tier plan...I would go way over that. But the things that we do to keep it...like buying a 700 dollar phone...LOL
What is getvar and also how do I see the partitions on my phone?
Well I have to hit the road but will be back on here tonight.
Click to expand...
Click to collapse
i dont know what getvar is really, but if its there (occasionally not) and you dont remove it, rsd will fail. its nothing needed to flash, thats all i know.
not sure how you would look at the partitions. you can wipe them in recovery, but you really dont want to mess with anything you dont understand. if you wipe the wrong thing, you will be in big trouble, and a factory file cant fix it.

Ok...I downloaded the files. I did not know if there is more then one partition on my phone or not. I have never done this on a phone before...Its a learning curve for me. I cant do this now it will have to wait until I get home so that way I can get online and you can walk me threw all of the steps and commands I need to send to my phone.

Knight71 said:
Ok...I downloaded the files. I did not know if there is more then one partition on my phone or not. I have never done this on a phone before...Its a learning curve for me. I cant do this now it will have to wait until I get home so that way I can get online and you can walk me threw all of the steps and commands I need to send to my phone.
Click to expand...
Click to collapse
In the future, please quote me or I may miss your post like I just did.
Thanks
Sent from my G2 running SlimKat

S6 G920F stuck on boot logo

Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew

andrew88 said:
Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew
Click to expand...
Click to collapse
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.

I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
TerribleChoices said:
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.
Click to expand...
Click to collapse

andrew88 said:
I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
Click to expand...
Click to collapse
Oh dear.
Yeah it does sound like something got deeply ****ed up in this case. I had the luck to somehow get past the smart switch error when the phone died of low battery. As I attached it to the charger I quickly boot it into download mode before the screen would become a bootloop again and that's where I was able to reinstall the latest version of TWRP recovery. After that, I was able to flash a stock ROM of Nougat that didn't have a ****ed up bootloader like I had. Specifically the one from this thread: https://forum.xda-developers.com/galaxy-s6/help/device-5-binary-3-s6-sm-g920f-t3706025
by forumber2.
It's the Netherlands stock-ROM. Not sure if you're from the US and the carrier would be wrong with that CSC, but it was a good bet for me. I got my phone back to working normally now.
Worst case scenario I'd say see if you have a phone repair shop nearby and ask them an opinion on what could be wrong. I'm just an amateur like you.
Still, I wish you the best of luck with it. Maybe there's still some hope. :/