Hello, I was reflashing a ROM (Sultan's CM10.2 w/ PMEM) but it seems to be stuck on Installing update...
It's been going for about 30 minutes now, much longer than the other times I've flashed it.
My question is, since it clearly isn't going anywhere, is it safe to remove the battery to start over again? I don't want to brick it.
(Not sure what went wrong, I think my SD card's going bad. I've flashed a few roms before successfully including this one, and I'm S-OFF'd and rooted already)
GoodOlTarvis said:
Hello, I was reflashing a ROM (Sultan's CM10.2 w/ PMEM) but it seems to be stuck on Installing update...
It's been going for about 30 minutes now, much longer than the other times I've flashed it.
My question is, since it clearly isn't going anywhere, is it safe to remove the battery to start over again? I don't want to brick it.
(Not sure what went wrong, I think my SD card's going bad. I've flashed a few roms before successfully including this one, and I'm S-OFF'd and rooted already)
Click to expand...
Click to collapse
HI
Greetings
i assume you have made a nandroid backup as if somthing goes wrong thats the thing which will help you
secondly you can try again just remove the battery and try againg
do a clean installation
Alright then. I took out the battery and reflashed it and nothing bad happened.
Thanks.
Related
I hope this hasn't been asked before, but I'm afraid it probably has.
Just unlocked and rooted my N1. After I rooted my device, I downloaded RomManager, then flashed the Clockwork Mod recovery and flashed the alternate recovery. I also downloaded Cyanogen Mod 6.1.1.
I rebooted and it has been stuck on the Cyanogen mod skateboard guy for the past 20 minutes or so. What did I do wrong?
it's hard to say. sometimes errors do occur while flashing a rom.
have you tried flashing the rom again?
Also, did you clear all data before flashing the rom the first time?
Well, crap the bed. I luckily figured it out.
I went into fastboot mode and cleared user data and it booted up just fine. I should have researched this a little more thoroughly before doing this. I knew I wanted my phone rooted, but the entire process wasn't quite as clear (to me) as it probably should have been. As far as I can tell, everything looks to be good to go.
My problem is when I turn on the phone, the Google logo stays stuck and after unknown minutes boots in with the software animation, but very slow! First a little history of my upgrades with this phone.
My friend bought me Nexus S T-mobile version for US 6 mounts ago, and the phone was with Gingerbread 2.3.4. After reading many post from here, I decided to upgrade because I can't upgraded 2.3.6 OTA. After many hours I finally upgraded it to 2.3.6.
Then ICS came out, and again, I upgraded to 4.0.3. Then, a few weeks ago, I got the 4.0.4 OTA notification. Happily I taped yes. And then before two days ago, my phone just died. I don't know how.
I have 115 installed application, no music inside, no ROOT - just pure stock. I was in my college room and I left my phone on the desk right in front of me and after few minutes when I looked at the phone, the Google logo was there. I didn't give the phone to anyone to picks or anything. When I get home, I turn the phone on and still the Google logo just was there doing nothing and like I said before, after unknown minutes the phone boots in with very slow animation of the ICS software. I decided to install Clockwork Mod recovery 5.0.2.0 and root the phone. After reading many tutorials I installed CWM recovery successfully. Then I tried to downgrade to 2.3.4 and successfully I did that to.
Now after doing all this things to this phone, after so many hours in pain, the phone is nothing like one week ago. The booting is very slow, the animation is veryyy slow, and I don't know what to do anymore... I think this is hardware problem.
Please help me solving this problem, I really expect someone here to know what is the problem and will help me in anyway. I'm desperate, and I don't know what to write here to tell you how desperate and sad I am...
Thank you in advance.
p.s. sorry for any grammar mistakes.
http://forum.xda-developers.com/showthread.php?t=1572307&highlight=factory+images
yeah, definitely flash the factory images, you'll have to reflash cwm after though
Do you reboot that often... that this is a problem?
I don't know how much time mine takes to boot... I don't remember the last time I've rebooted it ...
That's why changing boot animations, for me, is stupid... you only get to see them once in 6 months(worst case scenario)?!
muldy said:
Do you reboot that often... that this is a problem?
I don't know how much time mine takes to boot... I don't remember the last time I've rebooted it ...
That's why changing boot animations, for me, is stupid... you only get to see them once in 6 months(worst case scenario)?!
Click to expand...
Click to collapse
not if youre a crackflasher(flash stuff often). i see my boot animation 5+ times daily, if not much more
Yeah.. I forgot that...
When I had the Htc Magic, I used to flash it a LOT
I like Stock, the auto-updates...
dewaffelhaus8 said:
yeah, definitely flash the factory images, you'll have to reflash cwm after though
Click to expand...
Click to collapse
I flash with the official images from here and I reflashed cwm.
muldy said:
Do you reboot that often... that this is a problem?
I don't know how much time mine takes to boot... I don't remember the last time I've rebooted it ...
That's why changing boot animations, for me, is stupid... you only get to see them once in 6 months(worst case scenario)?!
Click to expand...
Click to collapse
I don't reboot that often, my phone itself reboots... I need to fix that problem, the slow booting, restarting, slow software... I need to know is it a hardware problem or software, because I did everything related to software problems...
A notification popped up in CM10 alerting me that there was a nightly build update available (stable & evita). I decided to go ahead and run the thing to see if it worked/what the deal was and it followed normal process.. Booted into recovery, attempted flash, rebooted to a black screen.
It appears that it attempted to update and subsequently failed so I booted into recovery and flashed the cm10.0.0.zip myself. Fortunately nothing was lost or bricked and even my phone settings were all there when I booted back up again after (what appeared to be) a successful flash. Any knowledge of this? Seems pretty weird to me so I figured I would ask.
THanks
Tom
tom0779 said:
A notification popped up in CM10 alerting me that there was a nightly build update available (stable & evita). I decided to go ahead and run the thing to see if it worked/what the deal was and it followed normal process.. Booted into recovery, attempted flash, rebooted to a black screen.
It appears that it attempted to update and subsequently failed so I booted into recovery and flashed the cm10.0.0.zip myself. Fortunately nothing was lost or bricked and even my phone settings were all there when I booted back up again after (what appeared to be) a successful flash. Any knowledge of this? Seems pretty weird to me so I figured I would ask.
THanks
Tom
Click to expand...
Click to collapse
Which One X do you have? I'm on the AT&T version and went through what you just said identically... however, after manually installing through recovery I'm still stuck in a boot loop/black screen. Unsure what to do at the moment. I don't know this stuff that well so I'm afraid to flash the build I had before without wiping (which I would really rather not do haha). I'd love to move to the stable version, although mine was pretty perfect as is. I just went ahead with the update for the hell of it, but that looks now like it was a mistake Any advice?
mittortz said:
Which One X do you have? I'm on the AT&T version and went through what you just said identically... however, after manually installing through recovery I'm still stuck in a boot loop/black screen. Unsure what to do at the moment. I don't know this stuff that well so I'm afraid to flash the build I had before without wiping (which I would really rather not do haha). I'd love to move to the stable version, although mine was pretty perfect as is. I just went ahead with the update for the hell of it, but that looks now like it was a mistake Any advice?
Click to expand...
Click to collapse
Cm10 stable works for me. But I installed it in recovery
Sent from my HTC One X-
I figured out the issue. I forgot that with the 2.20 firmware you have to flash the boot.img separately from the ROM. So after the update all I had to do was flash the boot.img and it was all ready to go again
From the beginning.
Unlocked
EVITA PVT SHIP S-ON RL
HBoot 1.14.002
Radio 0.19as.32.09.11_2
OpenDSP v29.1.0.45.0622
eMMC-boot
June 11 2012, 14:36:28
Click to expand...
Click to collapse
I was running a ViperRom my camera light was staying on, I tried everything to get it to turn off. I decided it been a few month it was time to get a new ROM anyways. I tried installing Gummy Nightly's was having problem with the install read about getting a different version of TWRP so I updated to 2.6.3.0 I believe I had 2.1.0.0. Gummy still won't work, so I changed plans and want for the Viper XL Rom 4.2.0 this led to a bootloop not getting past the Viper splash screen. I thought I might as well just with one of my backup. So, i wiped and loaded a backup. This is the problem, it will load up the ROM for about 30 seconds before the icon all appear it will reboot. I've now been working on this for 2 days. I've went through each post and tried the advice each person was given, I've tried to Flash a different Rom, the Viper Rom I had when I had the Camera Light Issue, each time I get about 30 second into the Rom Load and reboot. (One of the ROMs would let me access the SDCARD0 but found a work around that.) I've let the phone sit charged for 2 hours looping. I've turn it off and let it sit charging. The next thing I'm going to try to to downgrade the TWRP. If anyone can give me some advice, something new and different to try that would be great. Thanks!
Cheers
xDrFirefly
talked to one of my buddy and said the downgrade would be pointless so, i'm trying to flash a stock rom at the moment.
When you changed to TWRP 2.6.3.0 was it the official version or the unofficial modified version?
Sent from my Evita
Recovery: Custom TWRP 2.6.3.0 w/selinux support
And what errors did it give you when trying to install Gummy?
Sent from my Evita
The install failed. I tried it multi times, and even d/l it again to see if that would make a difference. Nope.
Here is what i've done so far. I factory reset everything. Found a stock rom flashed it on. For the two hours I used it seemed to work fine. I then flashed CleanRom everytime I would open Ti Backup the phone would reboot. I flashed another ROM, was getting the signal drop snagged the Beastmode Kernel it keep failing everytime I tried to flash it. Factory Wiped EVERYTHING again. Flashed the Stock, then Flashed ViperXL (then went to bed) in the morning still had signal bars, so far had two reboots, one when I was uninstalling apps using Manage apps feature, and another time when I was in the Venom HUB app. But at the moment the phone seems to be working. The battery life is ****. In the 30 mins I've had the phone unplug i've down to 89% and all I did was delete a few apps, and move some stuff to the home screens. Hopefully it will get better with time.
Side Note: To anyone reading this. I got the AT&T HTC XL preorder. I doubt I will ever do that again. In all the years I've been flashing and messing with phone. ( My first phone I messed with was a Sidekick ) I've never had so much trouble as I had with this phone. ( HTC Tilt, Fuze and Tilt 2 never had this kinda problem ) a friend of mine whom waited a year to get the XL has never had any of the problem I've had. Just my thoughts. Thanks and I hope I won't have to be asking anymore question.
When, I have more time and such I'm going to try to flash Gummy. If I get the same error message for it or anything else I will post it here.
Cheers
-Dr FF
I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita
You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.
jacobas92 said:
You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.
Click to expand...
Click to collapse
I will try this. Sounds like a very logical plan.
timmaaa said:
I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita
Click to expand...
Click to collapse
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".
xdrfirefly said:
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".
Click to expand...
Click to collapse
Computer always says no for a reason. You need the right recovery installed to flash KitKat ROMs, you also need to check the md5 of every ROM you download before you flash it. What I'm saying is there's no reason Gummy wouldn't install if you have done everything correctly.
Okay so i have TWRP 3.0.2.0 modded for multirom and multirom installed on my phone and it was working okay for a long time now all of a sudden my phone randomly reboots and ALL 7 roms in mutli rom boot loop when you try to boot them. so i erased all of them and reflashed the rom, the second i flash anything other than the rom, kernel,mods, stupid files, literally ANYTHING but the rom it bootloops again and it never did this before all of these files worked together before, so i rewrote the twrp and mutlirom and all, figuring maybe that would help, it did not. so i thought okay, fine i will do an RUU and go to stock. it says the firmware is mismatched? so because of S-ON i cant restore to stock now. ( same one ive been using to RUU it for over a year anytime necessary )
literally everything i try i just end up with Bootloops. if i flash ONLY the rom it boots fine but the kernels tend to kill the battery really bad so i usually flashed a custom one and i just dont understand how the same kernel and files ive been using for like the last 8 month now are bootlooping every time. i tried looking for new roms too, nothing works. i also tried plain stock TWRP and no mutlirom, same results, bootloops if anything more than the plain rom is flashed.
also my battery seems to be dying like a rock now, unplugged it and within like 10 min i had lost 18%
universelove said:
Okay so i have TWRP 3.0.2.0 modded for multirom and multirom installed on my phone and it was working okay for a long time now all of a sudden my phone randomly reboots and ALL 7 roms in mutli rom boot loop when you try to boot them. so i erased all of them and reflashed the rom, the second i flash anything other than the rom, kernel,mods, stupid files, literally ANYTHING but the rom it bootloops again and it never did this before all of these files worked together before, so i rewrote the twrp and mutlirom and all, figuring maybe that would help, it did not. so i thought okay, fine i will do an RUU and go to stock. it says the firmware is mismatched? so because of S-ON i cant restore to stock now. ( same one ive been using to RUU it for over a year anytime necessary )
literally everything i try i just end up with Bootloops. if i flash ONLY the rom it boots fine but the kernels tend to kill the battery really bad so i usually flashed a custom one and i just dont understand how the same kernel and files ive been using for like the last 8 month now are bootlooping every time. i tried looking for new roms too, nothing works. i also tried plain stock TWRP and no mutlirom, same results, bootloops if anything more than the plain rom is flashed.
also my battery seems to be dying like a rock now, unplugged it and within like 10 min i had lost 18%
Click to expand...
Click to collapse
Try a different twrp version worked for me awhile ago when I had it
Thank you for the suggestion but as it says above i have tried that. this phone will not let me restore or use anything without google play now so im probably just going to get rid of it or smash it because ive been trying for weeks and NOTHING works.
only android 7+ roms boot, cant RUU, no home button menus, notifications or anything work without google installed so my phone has some weird new firmware on it and is forcing me to use the most up to date android/google play or it just wont work at all.
Update: charger port just quit working, probably burned up from getting so hot with all the battery over use, phone is officially dead now.