hey guys,
been looking for some answers to my question, but not been able to find one... apologies if i am posting in the wrong section, but it seems to be the right bit.
long story short, my phone wont boot after, it simply says 'powered by android' then has an illuminated black screen. i am able to get it into fastboot mode (but no other modes), ive tried to use commands from all three of my macs to flash the device but each one has the same issue, it simply shows 'waiting for device' and nothing else happens... even left it connected for 8hrs and nothing.
im lost as what to try next and any help would be appreciated... the phone is a vodafone smart 4 turbo (n990).
thanks in advance.
Related
Hey all,
Well i know i m a newbie here, but i did all my searching and tried everything, but nothing will work. I flashed WM6 (http://forum.xda-developers.com/showthread.php?t=367019) and all was working fine. I was simply adjusting a few things on the phone when it required me to restart. I restarted the phone and now it will go to the slash screen, and the windows circle thing will start spinning to load, then it basically dies, the screen just fades to white.
I have since then tried two methods of getting it fix, but since my computer wont recognize the phone ( i have vista and media center), I cant run RUU, i get code 266.
Is there anyone that has a solution to this? I can get my phone into bootloader mode.
Please help me!
-Matt
By the way, the phone is CID-Locked....is their a way to CID-unlock it while in Bootloader mode? it is a G4
I got it fixed!
Now if it can just get deleted....
Hey all,
I did my searching for the last several hours, and am feeling pretty weak. I know there are several other posts with this error - but please let me explain my situation.
Phone was running 2.3.6. I am unsure how it was originally unlocked (carrier unlocked) and bought it used. To my knowledge it did not have root access... (though the advert said it did - running SU in Terminal to show if it had access failed)
I tried doing a factory reset on the phone because it kept acting weird. Just rebooting 10 times a day, and wifi not working either.
Since the reset the phone has not made it past the M Dual Core screen.
Edit as I type: As I type this, I FINALLY got into recovery mode. It took a long time... is that normal? I mean.. loongggg. Now i see other posts state I just need to click the bottom right corner above the search key and I should be on the way to recovering the device...
This however is not working...
I will keep the phone plugged in over night and see if it just needed more time I suppose. Can you guys recommend anything?
I am on win7 - should have the device drivers installed (though, Windows doesn't seem to recognize this with a notification bubble). I know the phone was not on USB Debug Mode when I clicked 'factory reset'.. would it have retained this?
I will update as i have more information.. otherwise if I am missing something please let me know.
Thanks again,
-k
Try booting into recovery mode by holding volume down while turning on. When the menu appears keep pressing volume down until it says android recovery and then press volume up to select it. If an android Guy with a warning sign shows up, press volume down and up. A menu should appear soon. Try to do a data wipe and factory reset from there.
Sent from my MB860 using XDA App
Hi ar31791, thank you for the reply.
That worked to put me into a recovery mode - very nice. Is the button combo different depending on the version of android your'e running, or just phone dependent? I appreciate that.
Couple follow up questions if you guys don't mind and can help
- after the factory reset - my boot time is incredibly slow.... like 30 minutes to boot kinda thing. I tried to factory reset several times since, and its the same issue.
- my data is not working on the phone. I used the apn suggestions from all sites I've found, rebooted (took a while) tried data roaming, etc, but it just doesn't work. I have a decent idea that the apn's are correct because the mms apn worked fine with a test picture message.
My main concern is the incredible lengthy boot time and the data no longer working. The issue with wifi still showing 'error' when enabling it was not resolved by the reset (I didn't think it would - I was reading other posts where it is suspected as a hardware issue).
Thanks again for the reads, and replies. I appreciate the help!
-kenny
You need romracers or cwm. Unless yer going to stay stock.
Sent from my MB860 using xda premium
Is this an att or a rogers/international phone? Best bet would be to flash pudding and than cwm + custom roms
hey again- thank you for the replies.. seriously. much appreciated.
phalanx, i dont mind staying stock but would that not allow the data connection to work correctly? i found a few posts based on the romracer. i lack the hands on experience, but it looks like i just need to follow the steps for an adb push and then install eh?
you mention staying stock, is that an option? info on my setup below
crnkoj, i am running a bell phone on a fido network in canada. bought on ebay pre unlocked. i do not bekieve it is rooted. phone, mms and text work fine, it seems to be a problem finding a data network at this moment.
thanks again guys, ill be taking a look into the tutorials for romracer and cwm, and giver a shot. lemme know if you have any further ideas, questions or anything you think i might need to know.
edit.. also, whats the deal with the crazyyyyy long boot up time?
kenny
(send from a mobile.. please excuse any typos or punctuation errors)
No its just that with an unlocked bootloader you can flash a new.recovery and that makes it easier to flash roms and also kernels and radios. Kernels and radios can affect your ability to connect with data and can even affect the speeds.
Sent from my MB860 using xda premium
I had a similar situation. So, i did a full wipe installed the rom did another full wipe then installed the appropriate kernel and booted it up. I believe you nedd to install the right kernel per the instructions. It will mot boot if the kernel is not correct.
Sent from my MB860 using xda premium
Thanks again guys,
Man it's a funny issue. I am always able to get in and factory wipe the device, but it seems that sometimes that damn M screen will sit forever. I left it over the course of a movie and a half (probably 3 hours) and that screen was still just sitting there.
I get into the fastboot menu easy enough before that screen hangs, and sometimes i can get into the Boot Android (without BP) (I believe it's called) and sometimes it hangs, and sometimes it works.
Other times, like right now, it boots just fine and kinda fast.
I am having an issue with the RSDLite application recognizing my phone. It did once - then hung at 94% flash of the pudding tutorial. I didn't realize the tutorial says to keep the phone plugged in for 10 minutes even after a fail to see if it actually completes. I havent been able to have the software recognize the phone since- I've installed and reinstalled the motorola drivers, set the phone to usb debugging, and was able to try 2 computers, and 2 different cables. I'll giver another shot though.
I am pretty sure my boot loader was unlocked (as I said I had this all done from an ebay purchase) so I think I can just proceed to the flashing, but if there is a way to confirm that it is indeed locked, I'll take the advice.
The more I read though, it looks like I might just need to send this beast in for a service call with Motorola, because of that damn wifi "error" error. I'd hate to go through all this and realize it still will not work.
Thanks for the replies, I'll always take more suggestions, and if you guys think I'm on the wrong path, let me know. I'll keep searchin dem' forums
If your bootloader is unlocked it will say unlocked in white letters on that M boot logo screen. Did you run "fastboot oem unlock" after the rsd flash?
Sent from my MB860 using XDA App
Hello everyone.
I ran into a serious mishap with my brand new work phone. I was handed a HTC radar c110 with Windows phone 7.5 to work with, but the phone had a little issue with calls and I decided to do a factory reset to see if it would sort it out.
So I searched on how to do a factory reset, and took a quick run to the bathroom before I could complete it. But my friend decided to finish it off for me, and somehow mispressed some button I guess, because a screen saying "Omega system loader menu" came up instead, with "FFU method" and 2 options, "MTPz" and "TFTP protocol". She took a blind guess at TFTP protocol, and when I came back the phone wouldn't turn on, it keeps resetting every few seconds and only says "TFTP protocol" on the bottom of the screen. Sometimes an image asking to connect the phone to the pc comes up.
I have tried the factory reset after this a couple of times, but when the phone restarts, this TFTP protocol image still comes up and the phone won't start. My guess is I have effed up the OS. What do I do now? Any guess? I don't want to go to my new job on monday and say that I screwed up the phone they gave me yesterday :S.
Any help is very appreciated. Thank you very much.
EDIT: I can get to USB host mode screen (white screen with "enter usb host mode"), and the white screen where you can "image crc" and "factory reset", not sure if it's called bootloader screen? I'm pretty sure I can get somewhere from one of these screens, but I'm not familiar with rom flashing and bootloaders at all.
EDIT2: I have been investigating further and I can now access the bootloader mode (the factory reset one), update mode (the omega system loader one) and usb host mode. I just need to figure out how to flash a rom (preferably an official one, as it's a company phone) into it now.
EDIT3: I got it fixed, not really sure how, but trying different things ended up booting the phone as normal. I am back to having the same problem as before though, but better than having a bricked phone I guess.
any idea what the solution ended up being?
I think reverting back to my original stock rom might be the answer for me, how did you do it?
I've just managed to do the same..
Any help as to how to sort out this issue? TFTP Protocol appears at the bottom of the screen with all the other symptoms referred above.. PLEASE SOMEONE HELP.
Good night everybody! my dad got this phone a while ago, after like 2 months he told me the phone was going crazy, I checked and was getting FC´s everywhere so get into recovery mode to wipe everything and there´s where problems started. I downloaded stock firmware and installed it but phone wouldn´t boot up, so my dad gave it to a guy that ``fixed it´´ but the problem came back after two weeks or so, the guy ´´fix it ´´ again but when I looked into the phone had no IMEI so didn´t recognized the sim card, the third time the guy got back the IMEI, that was long ago and today when I booted up the phone is having a weird behavior, sometimes gets stucked at the bootloader unlock warning, I restart it and after a couple of times starts the boot up animation but gets stucked at the M and like waving part.
I´ve tried getting into recovery mode but when I press any of those options boots to the warning bootloader. I got it to completley turn on when I pressed the recovery option; not expecting that to happened, but again some force close windows and decided to reboot it to see if would fix it but again to the same place stuck at the warning.
I´ve read many posts here im xda and outside but can´t find a solution. I tried to side load the firmware but looks like the pc doesnt recognize the phone´, when i got it boot up I connected it to the pc but didn´t recognized it, I installed the drivers and still the same.
Guess I need to get it recognized by the pc in order to try to side load a firmware. Sorry for the long post and any mistake, if someone can help to bring back to life this little fella.
Hi,
So as you've seen my phone is bricked, I can't reboot it by ANY way, it just vibrate when I try PWR + VOL+/-.
I looked a bit everywhere, and I find this -> http://www.droidgyan.com/soft-brick-vs-hard-bricked-vs-broken/#
But I need to know :
-Anyone has ever tried this ?
-is it a good solution ?
-is-there any better or easier way to get my phone back to life ?
And I repeat, I tried everything I found on others threads, every combination of buttons, nothing worked. So if you know a way like this, be sure it's not on every soft/hard brick forums, I've done them all ;p
And sorry for my english, I just hope everything is understandable.
Same here Have you find one solution ?
From experience with other devices that looks logical, I wouldn't like to be the first to try it though!! Might be worth trying insurance or taking it back to the shop you bought it from to see if you can get it swapped using the playing dumb card (I turned my phone on today and it just had a blank screen) that worked for mine when it was pre loader busted like this!
Hi!
I'm in the same situation.... i've got an Honor 7 (PK-AL10), i tryed to recover it but when i do fastboot flash system SYSTEM.img the system replies with "error: cannot load 'SYSTEM.img': Value too large for defined data type".
Help me!!
Have anyone tried to connect the phone to a windows PC, and Power+lower volume?
Also you may try with the phone plugged to USB, Power until the phone vibes for booting, wait 5 seconds and then Power again. And then try to boot the fastboot USB connected.
I don´t know but I´ve read in 2~3 places that powering the phone while USB connected sometimes enables booting in dead-phone situations.