I pulled my vortex out of storage the other day to tinker. It was rooted but fully updated stock 2.2.2
When I booted it up, it stayed on the boot animation 20+ minutes, until the battery ran out. I've tried booting it up again but it keeps bootlooping.
I figured I'd just flash a new ROM onto it, but I never put a custom recovery onto it and the only Vortex Recovery I found was this;
http://androidforums.com/getitnowmarketing/330813-all-one-recovery-thread.html
However, it says I need to do on-device commands and stuff to get it working, which obviously isn't an option.
Is there any other way you guys could think to resurrect my old Vortex? My Droid Charge is my phone now, this thing doesn't get much use anymore, but I'd still like to get it back in a usable form.
EDIT: FYI, already tried everything relevant in this thread: http://forum.xda-developers.com/showthread.php?t=1031596
If you flashed stock rom. Try hard reset.
Home+vol down / vol up+ power.
thank you! that button trick did the job!
EDIT:
well, it worked once, but the phone had been uncharged for a while so the battery died, and now i can't get the trick to work again >_<
is there a way to re-flash stock without a custom recovery?
Related
Hi guys, reasonable newbie here. My Galaxy S2 has stopped displaying anything after the initial logo. In fact it seems to turn the phone off as you can make repeated attempts to boot it within a few seconds.
I started by flashing an insecure sgs2 kernel from this site with odin, then used s2root.
I then played around with rom managed but found it wouldn't boot into clockworkmod (orange exclamation mark in a white triangle every time) I booted into it manually and started trying to flash cm7 which I had downloaded earlier.
I wiped the data etc and flashed the cm7 zip (plus the google apps zip). Rebooted and got into cm7 with everything seeming fine.
Next I thought I should probably flash back to the stock version of the insecure kernel. I rebooted the phone but got distracted and didn't start it up in download mode, I looked just in time to see the normal logo (with the yellow insecure triangle) and then nothing....just blank.
I tried rebooting afew times and nothing, even after yanking the battery. Then I tried getting back into clockworkmod to reflash cm7. Nope, same thing happens.
I can still get back into download mode but nothing I flash makes the slighest difference. Tried reflashing clockworkmod, insecure and stock kernels of various versions but I'm stuck.
This is almost a new phone and I can't believe I've already killed it I would be so grateful for any tips, I've included as much info as I can think of from the top of my head but I will do my best to answer anything you gurus might need.
Again, very grateful for any help...I don't want to have to explain to Orange how I've managed to brick this after 4 days
Ok after trying over and over again to get into recovery mode, it booted into the original (3e) recovery. I've just flash cwmod to it again and have just flash cm7.
After reading some posts about cyanogenmod sometimes not flashing correctly first time, I did it twice (and it did indeed take longer the second time) and twice for google apps.
Next I'll try to get back to the stock kernel. This is where it went wrong before but i'll cross my fingers.
Edit: Well, multiple reboots didn't cause a problem but flashing the stock kernel back does kill the handset again. I'm sure this stuff is all obvious to those with experience I guess I'll have to sit with an insecure kernel and the yellow triangle for the forseeable future. On a side note, s2root doesn't see the phone connected with cm7 (yes usb debugging was turned on). I'm hoping that it is pre-rooted but I haven't tested that yet.
Hi,
I will prefix this (as there are a few people around with this problem who can get into recovery mode) with the fact that holding down Vol- on boot is not getting me to the recovery / bootloader screen.
I have a rooted HTC Desire S (rooted it nearly a year ago, so info about the hboot etc is a distant memory).
Anyhoo, I decided to have a play about with one of the ICS roms but it was a bit buggy and the camera drivers still aren't working for video so I decided to go back to Endymion V3.4 - http://forum.xda-developers.com/showthread.php?t=1310845
I did a full wipe, installed base rom, installed optional addons and then upgraded to 3.4 - booted fine into the OS so set about getting my system set up the way I like it.
I noticed that endy came with a theme installer so clicked on one of them to have a look, it asked for root, said it was installed and would need to reboot to take effect...
SO
the problem is, it now won't boot and is stuck on the white HTC boot screen.
Holding vol+/- and power buttons reset it but it just ends up back hanging on the boot screen.
Have tried pulling battery and trying again.
Holding Volume Down when powering up is no longer doing anything
So, I either need a saviour to point me in the direction of a fix.. or a kindly sould to break it to me gently when they tell me my phone has gone to the USB Dock in the sky..
Any help will be greatly appreciated.
Thanks
update:
After pulling battery again, pulling out sim and sd cards, booting with vol- held down, i got into recovery. Am going to try and flash a different rom after doing a full wipe, I'll update once it's done but any insights in the meanwhile will still be appreciated
Sorted, cleared the thing out, stuck reaper CM rom on it, rebooted and everything is peachy for now.
Thanks me
Curious if anyone knows why this might have happened?
because you didnt flash the addon zip which was released alongside endymon and then tried to use the addons,it does say on the screen do not use these unless you have installed the addons
My sister said she spilled a little water on the screen of her phone the other day and it started boot looping.
Ive been trying to reflash it, but there are some issues...
If the phone is plugged in, it will cycle the charging battery on and off... unable to get into download or recovery.
If its not, it used to show the galaxy boot screen and turn on and off... now it just stays frozen on that screen. In either instance i was unable to get into recovery or download mode.
I got into recovery a couple of times when it actually booted the ROM, but everytime i would use the power button to try to make a selection the phone would just reboot and go into a cycle again.
I also got it into download mode once through the ROM but it cant get the ROM to boot anymore...
I might be able to get it into recovery but when i do it just reboots when i select anything.
and help would be awesome
thanks.
OH, when i actually got the ROM to boot it would throw an array of system errors and force closes. I also think the water had nothing to do with it and something she did after the water is what started causing the problems
I got recovery and i flashed a new kernal and ROM and erased everything and its still freezing at first Galaxy boot screen.
probably because the phone is water damaged?
See if the guide in the second link of my signature will help.
Thanks ill give it a shot.
But a major problem is that i am unable to get it to boot into download mode.
So i got CWM to boot, and i reflashed the kernal and ROM, with no luck.
CWM read catch error. Unable to mount... format... ect...
From what ive been reading the internal catch is fried....
Anyone have a motherboard they want to ship me? LOL :laugh:
Thanks lumin30, I finally found a way to get the phone into download mode. (take the battery out, Put it back in, hold buttons, plug USB in, press power button) after a few reboots it would finally go.
I followed the link and got it back to stock and it booted. Now letting it sit to settle in and hopefully it will be functional again.
This thread can be deleted! :good:
Sorry everyone... I tried one more time (my 5th attempt!) and it worked this time! I have no idea what happened with the earlier attempts. Thanks
Hello everyone. I'm having a problem with a Rogers Skyrocket here and hope someone can help. It was running a custom ROM, but I was given the task of returning it to stock. I don't recall which ROM was on it, but it worked nicely. I should have just kept it that way!
Thanks to vincom's super helpful posts, I got the info & file(s) needed to get this thing back to stock. I installed Odin 1.85, and extracted
I727RUXLF3_I727RRWCLF3_I727RUXLF3_HOME.tar.md5
from the zip. I started by doing a wipe/factory reset (from inside the custom rom) first, and rebooted to see that it showed the initial setup screen. Then pulled battery and booted the phone into ODIN mode. I made sure to kill Kies completely before connecting the phone to my laptop (WinXP). Then launched Odin, hit the PDA button, loaded up the above file, left the check-boxes as they were, and flashed. It was successful, and rebooted the phone.
The rogers logo appears, and the samsung galaxy bootanimation comes up, and it continues to animate.... forever (for the record, I waited 20 minutes, more than enough time). I can pull the battery and try to boot again but it still stays on the bootanimation. I'm not sure what else to do? I can still get into stock recovery or Odin mode. Can anyone help? Thanks
Hey guys,
I have my rooted, custom-ROMmed GS3 here. Was running Eclipse ROM for a while now (several months), decided that I wanted to re-ROM soon, and as I had to boot into recovery earlier today (Google Hangouts caused my phone to freak out and get caught in the bootloop) I figured now was as good of time as any. Did some research, decided to put LiquidSmooth on it, downloaded Liquid-JB-v2.9-OFFICIAL-i9305.zip and gapps-jb-20130301-signed.zip, put them on my external SD, booted into CWM recovery, flashed both on my phone. I did forget to wipe everything. And I think I may have tried to put the international ROM on it. Phone was at 94% battery at the start of this. (Didn't make a backup as my phone was running a backup.) Now, phone won't recognize the power button at all, either just to power on or to try to boot to recovery. It is recognized by my PC in Device Manager as QHSUSB_DLOAD, and plugging it into a charger (wall or USB) without the battery in gives me a red LED.
Help?
Thanks
Figured it out - hard bricked my phone due to a wrong ROM. Fixed it by sending it to brickedmyphone.com , he had it back to me in a week, back to stock, completely working.