Related
Hi, i`ve owned an infuse for a couple months now and i`m loving it. I bought it off somebody and it came pre-rooted. Superuser was working great, i was running rooted apps and everything was pretty awesome. However, i`ve just recently wanted to try something new. Such as flashing a new rom. I downloaded the zeus rom (i also have others), went into rom manager and tried to install. That didn`t work. So i tried to manually boot into clockworkmod recovery and install. That didn`t work. I think the main problem is how do i get into clockworkrecovery? Whenever i boot into it i lack very many options that i keep seeing from others. Everytime i try to boot into it it says
Copying media files
Successfully copied meida files
Manual Mode
Appling Multi-CSC
Installing Multi-CSC
can't access to system/csc/RWC/system/
Successfully applied multi-csc
and the options are
Android system recovery <3e>
Samsung Recovery Utils for BML
Enter: Power Key, Select: vol up/ vol down
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
Everytime i try to apply update from sdcard it says:
Failed to verify whole-file signature
Installation aborted.
I can't remember all of it but you get the just of the idea
I can't seem to figure this out and i dont think this is clockwordrecovery. I've tried various methods of rebooting using the CWM app, Rom Manager app, and the button pressing.
All i want to do is flash a new rom! Can anyone help?
P.S. It isn't a typo when i put "Successfully copied meida files", they actually spelt it meida.
Xparks said:
Hi, i`ve owned an infuse for a couple months now and i`m loving it. I bought it off somebody and it came pre-rooted. Superuser was working great, i was running rooted apps and everything was pretty awesome. However, i`ve just recently wanted to try something new. Such as flashing a new rom. I downloaded the zeus rom (i also have others), went into rom manager and tried to install. That didn`t work. So i tried to manually boot into clockworkmod recovery and install. That didn`t work. I think the main problem is how do i get into clockworkrecovery? Whenever i boot into it i lack very many options that i keep seeing from others. Everytime i try to boot into it it says
Copying media files
Successfully copied meida files
Manual Mode
Appling Multi-CSC
Installing Multi-CSC
can't access to system/csc/RWC/system/
Successfully applied multi-csc
and the options are
Android system recovery <3e>
Samsung Recovery Utils for BML
Enter: Power Key, Select: vol up/ vol down
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
Everytime i try to apply update from sdcard it says:
Failed to verify whole-file signature
Installation aborted.
I can't remember all of it but you get the just of the idea
I can't seem to figure this out and i dont think this is clockwordrecovery. I've tried various methods of rebooting using the CWM app, Rom Manager app, and the button pressing.
All i want to do is flash a new rom! Can anyone help?
P.S. It isn't a typo when i put "Successfully copied meida files", they actually spelt it meida.
Click to expand...
Click to collapse
You don't have cwm recovery yet.
Don't use ROM manager.
I made a thread on "how to." It's a collection of some things I've learned.
Start there.
The link is on my signature line
So where should i start? At the flashing part?
Xparks said:
So where should i start? At the flashing part?
Click to expand...
Click to collapse
Start here:
[REF] [HOW TO] [ROM Installation] Where to start?
Xparks said:
So where should i start? At the flashing part?
Click to expand...
Click to collapse
yes..follow gtg's CWM instruction set
So. I already started with the odin UCKD5 one. http://forum.xda-developers.com/showthread.php?t=1092021
and i already started into download mode. However, it now says downloading. and my computer was like "installing new hardware" then "could not install new hardware" and now my phone is stuck in the downloading screen that says do not turn off target. Odin has yet to pick up my phone....what now?
if you have root you can flash a cwm enabled kernel with sgs kernel flasher.
if you have froyo use the defuse or community kernel. or use gtgs thread for cwm without flashing a kernel.
if you have gingerbread then you will need to flash one of the custom kernels such as entropy dd, hellraiser, or infusion. gtgs cwm thread will not work on gingerbread.
My phone is rooted and running on gingerbread. But um. i have a more pressing concern at the moment....this downloading screen is freaking me out...
okay well i can't seem to figure any of this stuff out. any noone has replied so i just reset my phone so i can actually use it.
Some more information for those who can help is that the firmware is 2.3.3
Baseband version is I997RUXKG3
Kernel version
2.6.35.7-I997RUXKG3-CL366622
Build number
Gingerbread.uxkg3
Xparks said:
okay well i can't seem to figure any of this stuff out. any noone has replied so i just reset my phone so i can actually use it.
Some more information for those who can help is that the firmware is 2.3.3
Baseband version is I997RUXKG3
Kernel version
2.6.35.7-I997RUXKG3-CL366622
Build number
Gingerbread.uxkg3
Click to expand...
Click to collapse
that's Rogers firmware. use kernel flasher (easiest) and flash one of the popular gingerbread kernels. entropy dd is popular. once the kernel is on there You will have red cwm. that will allow you to flash whatever.
if you flash a rom it will include a kernel so don't worry about the minor incompatibilities that exist with att based roms.
So i'm currently on this thread
http://forum.xda-developers.com/showthread.php?t=1212795
with this in the other tab
http://forum.xda-developers.com/showthread.php?t=1289460
I'm not sure which kernel to download. But i'll try flashing a couple anyway
also i tried using heimdall/odin or whatever. It wouldn't pick up my phone in download mode. and thus couldn't install drivers.
well. I tried flashing one of the kernels. specifically
DD_02162012_A.zip - [Click for QR Code] (5.16 MB, 118 views)
So i flashed it using SGS kernel flasher. it said flashing....rebooting. And now it's stuck at the rogers logo. I have no clue what to do and i think it might be bricked. So if i could get someones help, perhaps step-by-step as i obviously cannot do this following the other instructions.
Xparks said:
well. I tried flashing one of the kernels. specifically
DD_02162012_A.zip - [Click for QR Code] (5.16 MB, 118 views)
So i flashed it using SGS kernel flasher. it said flashing....rebooting. And now it's stuck at the rogers logo. I have no clue what to do and i think it might be bricked. So if i could get someones help, perhaps step-by-step as i obviously cannot do this following the other instructions.
Click to expand...
Click to collapse
You are stuck in bootloop. Not bricked or even close to it. Read infused rom and flash it. If you cannot figure that out you should not be flashing. It's dead simple. Promise. Search it. It's in the dev thread. Called infused by gtg
Sent from my SAMSUNG-SGH-I997 using Tapatalk
thanks for the help so far. but i went here. http://forum.xda-developers.com/showthread.php?t=1116251
and the link no longer works. so what now. I can't get the files and therefore can't put anything into odin.
sigh. so i downloaded the files from someone who uploaded it again. Did everything. Succesful. only to have it be stuck in bootloop and samsung screen. Did what it said. pulled battery, replace, vol buttons and power key until recovery shows up. That doesn't happen. Instead i notice that instead of a rogers screen it says at&t and then goes to samsung screen. and then restarts again by going back to at&t. If i let go of the buttons it goes back to begin stuck at the samsung one. This has made so many problems for me.... just by trying to get clockworkmod. what do i do now?
Xparks said:
thanks for the help so far. but i went here. http://forum.xda-developers.com/showthread.php?t=1116251
and the link no longer works. so what now. I can't get the files and therefore can't put anything into odin.
Click to expand...
Click to collapse
Xparks,
You really should read up a bit. If you looked toward the end of that thread,
you will see that the file has been uploaded by another user to another site:
http://forum.xda-developers.com/showthread.php?t=1116251&page=40
i got that one already. i've passed that step. I'm now stuck in bootloop with at&t and samsung logo. Bootloop was supposed to be a rare occurence...and the instructions to work around it aren't working right now. I can't access recovery mode. Or anything for that matter.
Xparks said:
i got that one already. i've passed that step. I'm now stuck in bootloop with at&t and samsung logo. Bootloop was supposed to be a rare occurence...and the instructions to work around it aren't working right now. I can't access recovery mode. Or anything for that matter.
Click to expand...
Click to collapse
Download the drivers for the phone on the computer. If it does not work then, try heimdale. If you can not do this, then just ask me for the jtag guy, ill give you the link to the website. Mobiletechvideos uses jtag to recover the phone (taking it apart, hooking it up with a ton of wires lol). Keeps personal data, just recovers rom, or you can pay a little extra for him just to install whatever rom. It worked for me, you may have a broken usb controller like me all of a sudden.
I have kies but when i start it up it says please connect your mobile phone. And it doesn't pick up my phone. It probably shouldn't seeing how my phone is stuck. But i went to menu in kies and pressed install driver. But i'm not sure how to download my exact driver if kies can't even pick up my phone. But i ran the "zazig" program. and i'm installing the drivers from there. And i'm going to attempt to reflash using that since Odin didnt work before. The link is this http://forum.xda-developers.com/showthread.php?t=1331381
And it did that. But i don't what to do. I've been on xda reading forums all day and the only thread i can see relevent to mine is someone advising them to bring it back under warranty. Mines rooted. no warranty for me. I hope if it ever works again i can use it on rogers still because it says AT&T.....and i'm afraid to try and unlock it. because we know the last time i tried to do something.....
Odin can still detect it and i tried reflashing the unbrick stuff. No dice.
Well, I must admit I am in over my head....I have owned an inspire for a few years and finally decided that I wanted to try and learn about rooting etc. I followed instructions using the advanced ace hack kit and flashed cyanogen mod7 rom and I was so proud....then some problems and some bad decisions by me. First, there was some sort of issue with the phone as I could place calls and hear but the mic did not work. Unsure of how to fix that problem, I tried a new rom (leedroid) which was still ok but upon starting I had no service. Clearly, I do not know enough to troubleshoot and I should have read more prior to beginning and this is where I began to get into deeper trouble. After trying to revert back to the cyanogen mod7.2 using rom manager, I have really messed things up. Right now, I have lost clockworkmod recovery so when I hold down the volume and press the power, my only option is hboot and it prompts me "do you want to start update"that goes nowhere...If I begin with the power button only it hangs on the HTC white screen. Iknow, I know I should be searching and reading. Believe me, I am but I could sure use someone to give a lost guy some help! I have been trying to learn and download my original RUU to perhaps get back on track that way...Thanks in advance for taking the time to read!
hocky88
hocky88 said:
Well, I must admit I am in over my head....I have owned an inspire for a few years and finally decided that I wanted to try and learn about rooting etc. I followed instructions using the advanced ace hack kit and flashed cyanogen mod7 rom and I was so proud....then some problems and some bad decisions by me. First, there was some sort of issue with the phone as I could place calls and hear but the mic did not work. Unsure of how to fix that problem, I tried a new rom (leedroid) which was still ok but upon starting I had no service. Clearly, I do not know enough to troubleshoot and I should have read more prior to beginning and this is where I began to get into deeper trouble. After trying to revert back to the cyanogen mod7.2 using rom manager, I have really messed things up. Right now, I have lost clockworkmod recovery so when I hold down the volume and press the power, my only option is hboot and it prompts me "do you want to start update"that goes nowhere...If I begin with the power button only it hangs on the HTC white screen. Iknow, I know I should be searching and reading. Believe me, I am but I could sure use someone to give a lost guy some help! I have been trying to learn and download my original RUU to perhaps get back on track that way...Thanks in advance for taking the time to read!
hocky88
Click to expand...
Click to collapse
First try taking out your SD card and using something to connect to the computer and take off the P981IMG or whatever that zip file is called. Then try booting back into recovery again. Also, next time try to not use rom manager and just flash it from recovery mode.
Sent from my SGH-I777 using Tapatalk 2 Beta-5
http://db.tt/Usbm7yCw
Here is the rooted stock from and radio just place in root of SD (not in any folder) boot up into hboot since you known how to do that let it find it will ask to install volume up for yes let it do its thing then reboot when asked. Make sure all roms and pd98 s are off SD card before you put this one on it. It will give you gingerbread from then you can install whatever custom from you want.
Have and enjoy the learning
Sent from my Desire HD using xda premium
Wow! First, thanks for the quick repsonses. Yes, my first lesson learned is to flash from recovery as it seems more direct and therfore less likely to create problems for me until I get up to speed. This morning I am at work, so not alot of time available, but I did take out the SD card and rebooted and I found it interesting (for me anyway) that I can now choose the clockworkmod recovery v5.0.2.0 with out my SD card inserted. So, I can see that I messed up something on my SD card. I think when I get some time today, I will download the rooted stock that Reinaldo offered, clear all the stuff off my SD card and put this file into the root directory and let hboot update with this file. I knew I came to the right place for help! Think I will spend the day reading the basics trying to understand how all these pieces work together...
U just have a PD98IMG.zip on ur sd card that u need to get off of it cuz hboot is trying to flash it as soon as it boots up. So when u remove ur sd card, it's not trying to flash that zip so u can get to recovery. So u need to plug ur sd into a pc & move or delete that zip. Or u can just move/delete it with a file explorer once it boots up, of course. Just be careful to never put a PD98IMG.zip on the root of ur sd card unless ur ready to flash it. Then be sure to move or delete it once ur done flashing. Did u download a radio or something?
hocky88 said:
....I have owned an inspire for a few years
Click to expand...
Click to collapse
??? release date 2/13/11. I guess time flies when you're having fun.
You're on the right track with your last sentence from your last post. Spend lots of time reading and educating yourself and you will be much better off.
This will be closed soon by a mod there is about 20 threads of the same issue..
My Inspire
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
Hi guys.
I posted a thread the other day asking for help with superoneclick, I have since taken on board the advice given, and scrapped the superoneclick route. Instead I followed this guide http://forum.xda-developers.com/showthread.php?t=1525100 , which was going really well, up to the point where I go into recovery, and try to install from sd card. I tried the method with the reaper v2.1, and now also with blind roms pacman rom, and neither show up when I go to install from the sd card. I downloaded the roms, and unzipped them in the sd card, not in a file, just into the card itself, they then show up, but only as "boot" and not as "boot.img" as I'm sure it should say, they also still say they are a "winzip file", which surely if they were unzipped, they wouldn't say this?
Seemingly everything else I did is working as it should, I have an unlocked bootloader, I have enabled adb and fastboot, it's just the putting the rom on the sd card and then locating it when I go into EXT4.
Can anyone please shed some light on to what I may be doing wrong?
4) Open the rom (.zip file) you downloaded in step 1 and put the ''boot.img'' file in ''C:\android-tools'' seems to be the part where it all goes wrong?
Thanks for now.
Geez, so many things done wrong.
I hope someone will have patience to explain all of them to you, I'll just tell you 2 things:
1) Guides assume that people can tell file names from file extensions, and know how to see both.
2) I highly suggest you leave your phone alone. You don't have enough knowledge to safely proceed, and definitely don't have enough knowledge to pull yourself out of trouble, which you'll eventually get into.
Jack_R1 said:
Geez, so many things done wrong.
I hope someone will have patience to explain all of them to you, I'll just tell you 2 things:
1) Guides assume that people can tell file names from file extensions, and know how to see both.
2) I highly suggest you leave your phone alone. You don't have enough knowledge to safely proceed, and definitely don't have enough knowledge to pull yourself out of trouble, which you'll eventually get into.
Click to expand...
Click to collapse
I appreciate any feedback or criticism, as long as the end result is me figuring out how to root my phone.
I THOUGHT I'd followed the guide pretty closely. I'm inexperienced,yes, buy so is everyone when they try doing something for the first time. I've been reading all I can to help give myself some much needed knowledge.
But guess I'm doing something not right, I'd very much appreciate someone being uber patient with me,and showing/telling me what it is I'm doing wrong.
Thank you.
What needs to be on the sd card is the zip file of the rom, not unzipped or anything. Then you can install the rom from recovery, assuming you did all the other steps right.
teadrinker said:
What needs to be on the sd card is the zip file of the rom, not unzipped or anything. Then you can install the rom from recovery, assuming you did all the other steps right.
Click to expand...
Click to collapse
He has unlocked bootloader, which means - telling him how to install it without explaining what to do after (flashing boot.img) is a great idea - if you want to get his phone not to boot anymore.
Jack_R1 said:
He has unlocked bootloader, which means - telling him how to install it without explaining what to do after (flashing boot.img) is a great idea - if you want to get his phone not to boot anymore.
Click to expand...
Click to collapse
^^^^ Which will be why my phone now wont go past the white screen displaying HTC.
But I can still boot into 4EXT recovery, but when I do the backup/restore, it does nothing, just comes back to 4ext, or if I reboot, the white htc screen.
As it will go into 4EXT, it's not bricked, I guess it cant find the stock rom in the system to restore back to.
Not sure where to go now....Ebay for a replacement perhaps :silly:
nixon. said:
^^^^ Which will be why my phone now wont go past the white screen displaying HTC.
But I can still boot into 4EXT recovery, but when I do the backup/restore, it does nothing, just comes back to 4ext, or if I reboot, the white htc screen.
As it will go into 4EXT, it's not bricked, I guess it cant find the stock rom in the system to restore back to.
Not sure where to go now....Ebay for a replacement perhaps :silly:
Click to expand...
Click to collapse
Sounds like if your tire goes flat to trash the whole car for parts lol
Jack_R1 said:
He has unlocked bootloader, which means - telling him how to install it without explaining what to do after (flashing boot.img) is a great idea - if you want to get his phone not to boot anymore.
Click to expand...
Click to collapse
He was following a guide which included flashing boot.img, so I (perhaps over optimistic) assumed the right boot.img had been flashed.
---------- Post added at 07:12 PM ---------- Previous post was at 07:07 PM ----------
nixon. said:
^^^^ Which will be why my phone now wont go past the white screen displaying HTC.
But I can still boot into 4EXT recovery, but when I do the backup/restore, it does nothing, just comes back to 4ext, or if I reboot, the white htc screen.
As it will go into 4EXT, it's not bricked, I guess it cant find the stock rom in the system to restore back to.
Not sure where to go now....Ebay for a replacement perhaps :silly:
Click to expand...
Click to collapse
Yes your problem now is that you haven't flashed the boot.img from the rom you've installed.
deleted
nixon. said:
Hi guys.
I posted a thread the other day asking for help with superoneclick, I have since taken on board the advice given, and scrapped the superoneclick route. Instead I followed this guide http://forum.xda-developers.com/showthread.php?t=1525100 , which was going really well, up to the point where I go into recovery, and try to install from sd card. I tried the method with the reaper v2.1, and now also with blind roms pacman rom, and neither show up when I go to install from the sd card. I downloaded the roms, and unzipped them in the sd card, not in a file, just into the card itself, they then show up, but only as "boot" and not as "boot.img" as I'm sure it should say, they also still say they are a "winzip file", which surely if they were unzipped, they wouldn't say this?
Seemingly everything else I did is working as it should, I have an unlocked bootloader, I have enabled adb and fastboot, it's just the putting the rom on the sd card and then locating it when I go into EXT4.
Can anyone please shed some light on to what I may be doing wrong?
4) Open the rom (.zip file) you downloaded in step 1 and put the ''boot.img'' file in ''C:\android-tools'' seems to be the part where it all goes wrong?
Thanks for now.
Click to expand...
Click to collapse
In step 1 you copied the ROM zip file from your PC to your phone.
In step 4, you should open the PC zip file, not the file on the phone's sdcard. X(
That's the only thing you did incorrectly!
Sent from my Nexus 7
BillGoss said:
In step 1 you copied the ROM zip file from your PC to your phone.
In step 4, you should open the PC zip file, not the file on the phone's sdcard. X(
That's the only thing you did incorrectly!
Sent from my Nexus 7
Click to expand...
Click to collapse
^^^ thanked
Thank you for pointing out my mistake, now at least I realise what I was doing wrong, although now my phone is beyond my own repair, I shall have to see if I can send it off somewhere to get fixed.
Thanks again
nixon. said:
^^^ thanked
Thank you for pointing out my mistake, now at least I realise what I was doing wrong, although now my phone is beyond my own repair, I shall have to see if I can send it off somewhere to get fixed.
Thanks again
Click to expand...
Click to collapse
Why is it beyond your repair? Have you flashed the boot.img from the ROM?
Exactly, just flash the boot.img from the rom you flashed and it should work fine.
And if "flashing boot.img" sounds too complicated, try googling "fastboot flash boot boot.img", and going to Youtube for tutorials.
Your mistakes that I referenced earlier weren't only unpacking the ROM - this wasn't the problematic part - but when you did unpack the ROM and didn't understand anything from the boot.img file you saw, it meant that you have no idea about files and extensions, which usually means that it would be a bad idea to expect you to be able to freely use command prompt without detailed directions (and the guides always assume some level of knowledge - some more, some less). If you were to follow a better guide, the one that gets you S-OFF, it wouldn't matter - but since you've unlocked the bootloader and forced yourself to have to flash boot.img by fastboot, I didn't count on a happy ending should you proceed. I hate to be right in these cases.
You need to learn several things:
1. What are file extensions and what do they mean (mostly for yourself, but also for further understanding of the issue).
2. How to enable your OS to show file extensions to you, so you can see them and understand what file you're looking at.
3. How to open command prompt (you already did that - when you unlocked. now you need to do it to communicate with the phone in the same way).
4. How to use fastboot to flash boot.img (kernel) from command prompt.
Not too complicated, but it would have been better to learn that in your free time while having a functional phone, rather than in a rush to bring a non-working phone back to life.
Good luck.
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.