How to recover my defy updated with official 2.2.2 SEA froyo - General Questions and Answers

Hey guys,
I need some help, this is my first time to post here(noobie). Anyway, I have learned plenty of things here in this forum..now my problem is I updated my defy with the official 2.2.2 froyo (singapore) it was ok at first though had some camera issues it kept shutting down before taking a shot. now was going to do a nandroid backup have it rooted,SetCPU and stuff..My mistake was when I used the clockworkmod for defy it installed then when I was about to go to recovery mode it got stock in a boot loop..I panic and used the hard reset (stupid enough) that i was looking for the menu (which I just read today if froyo:use + & - keys for it) to which I cannot do anything I went to boot load to flash my old firmware ver2.59 SEA18 now at RSD lite it says PASS..but did not restart my defy.. now I cant even get it to recognize even after charging my battery using universal charger. though i still see the white light at the top when I plug it on my PC..
Can anyone help..sorry for my bad posting..THANKS a lot for any help..

Related

Please help I am so screwed! SBF Issue

So from the beginning: I SBF'd my phone back to stock a couple days ago and it was working fine. I was rooted bootstraped all that I tried to flash one of the Liberty roms and I was stuck at the liberty fist screen.
I figured the problem was I was on stock 2.3 or whatnot and I tried to flash back to 2.2. SBF again right? Well little did I know my battery was semi low and during the flash process my battery fell below the threshold and now it has an error message on the phone bootloader update screen that says "CODE INVALID."
When I try to SBF it with RSDLite and the 2.3.20 SBF file I get an error that says: Phone is not compatible with multi-interface superfile. (0x703B)
It also doesn't detect what kind of phone it is when I plug it in either. It just says phone[0000].
Am I totally screwed?
boot into recovery (shutdown or remove battery, put battery back into place, press Power+X on the keybroard) and do a full data wipe then reboot.

galaxy s2 displays nothing after logo since flashing cm7

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.

[Q] Desire S stuck on boot - cant get to recovery

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

[HELP] Bootlooping Vortex

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?

[Q] vzw gs3 will not power on

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.

Categories

Resources