Hi,every time my phone switches off and I try and switch it back on it just goes straight to the fastboot screen. Pressing the reboot just brings me back here. Doing a factory reset does exactly the same thing, and does not reset. It has been doing it for a while now, and if i reboot enough times it eventually reboots normally, and functions fine until I run out of battery or something, then it takes ages to get it up and running again.
I haven't unlocked it in any way, it's completely stock. Htc are trying o get me to install an update, but as soon as it starts to install it switches off, and goes straight to the fastboot screen.
It's driving me mad, and is obviously just outside the warranty period.
Any help or advice on what to try would be much appreciated.
Cheers, Tom
I had the same problem a year ago but was still on warranty then, so I sent it in. When they returned it to me, there was no sign of them having opened up the phone so I guess it can be fixed software-side, but I'm not sure. You could probably try flashing a fitting RUU in fastboot and see if that fixes your problem (I guess that was what HTC has done when my device showed a similar behavior). Just be sure you're on the right version, as KitKat e.g. has a new partition layout and this could lead to problems with your phone not booting up properly.
Is your phone unbranded? What version are you currently on (Android, hboot)?
Related
I've been running a ROM I built from the consolidated kitchen this weekend without any problems. Today I updated the radio to 2.69.11 from the cingular 2.25.11. After the flash the phone froze on the windows mobile screen. After some time I tried to reset the phone and it froze again, a few more tries and it finally boots up. I didn't pull the memory card when I flashed and thought that might have been the problem so I flashed again even though the phone was showing 2.69.11. I don't remember everything after that but it wouldn't boot up and I have tried flashing the original Cingluar ROM & T-mobil 2.26 without any luck.
The phone is stuck in bootloader now and is getting a error code 302 I think it's because the phone doesn't stay on when the USB cable is attached. It gets to about 15% and the phone resets and the error 302 pops up. When connected and not trying to update the phone turns on and off in the bootloader screen. I have pulled the battery, rebooted the laptop, tried using mtty,and pulled the sim. I thought the original problem might have been because I flashed at 52% battery. I put a older battery in after that appeared to have a good charge. Right now I put the phone on charge with the newer battery to see if this helps. I am not sure if it is charging because the orange light is not on, I can't get the phone to stay turned off when plugged into the charger and the bootloader screen is on.
And yes I have been searching for hours for a solution to this problem.
Also looking for a post I read about doing a master reset, I have tried holding the 2 soft keys when turning on, didn't help.
I think this says it all I have tried everything, does anyone anything else to try?
Thanks
UPDATE: went out for a few beers and some food. Not sure it the battery charged (bootloader screen on the whole time it was plugged into the charger)
Tried flashing again with cingular ROM, got about 20% and phone shut off and turned on again in bootloader. Flash gave 302 error again. Tried again and phone reset (on and off) every 5 seconds when connected to laptop with USB.
I'm hopping someone out there has a answer for this problem.
Back from the dead HALLAULA!!!!
This morning I spent more hours searching still didn't out find anything.
I tried mtty again and noticed that I never got to the screen that shows USB>
to enter the command "set 14 0"
I came up with a thought and this is what I did. Created a new ROM, OS only. Thinking it will load faster than any other ROM. It reached 100% in 3 minuets the whole I'm coaching come on baby don't restart and than going (don't know how to explain the feeling) waiting the next 2 minuets to get to finished. But it got there booted fine. I don't know why it stayed on this time and didn't restart, maybe having the battery out all night had something to do with it. After I flashed the Cingular ROM than the original I created and lastly Radio 2.69.11
I hope this helps someone in the future,
i need your help
hi man I had a prophet s200 and give me the same error 302 but, with the diference in my case got 98% adn then stuck in boot screem, please help me if you can...and sorry for my english
Guys,
It may help checking out this thread!
http://forum.xda-developers.com/showthread.php?t=294107
Can you help me out?
How did you create a new ROM - OS only? I'm having the same problem..can you walk me through this?
Thanks
How did you create another ROM (Operating System only)? I'm having the same problem and I have tried for the past 2 weeks - but no luck. Can you walk me through it?
Thanks
I used the consolidated kitchen (sticky at the top of this forum)
Uncheck everything on Build OS.
My problems started from a version of battery status that caused the original problem and not having enough of a charge on my battery.
Make sure you are CID unlocked (if you have a G3) and your battery is charged.
Umm, you can't uncheck everything in build OS or you will have problems, especially if you don't check a tuchflo or non touch flo dll or choose a commanager and probably a few others things. I don't have build OS up in front of me to check. The whole point to this msg is that you can check everything in build OS (besides the ones that say choose only 1) and it will build an OS only rom for you. That's the whole point behind build OS.
You are correct, I was kind of going from memory since I had built the striped down ROM awhile ago.
I was following the nice little wiki (http://wiki.xda-developers.com/index.php?pagename=Wizard Windows Mobile 6 for newbies) and got down to installing the button ROM to downgrade the IPL to 1.05. Started off fine, but it's stopped at 57%. For over an hour already. I wasn't running anything, but did have Firefox open the whole time (was reading ahead in the instructions).
I guess the question is, am I screwed, or will I be able to end task on this update and restart it? I haven't turned them off yet, but I'm guessing that if I do my phone will be a fancy paperweight.
I did notice that ROMUpdateUtility_Wizard_NOID.exe has maxed out one of my cores (13% utilization, 8-core computer--I.E one core is pegged at 100%), so I'd say it's crashed or in a loop.
I'm going to leave it running--overnight perhaps--and see what happens. Any other suggestions?
er.. if this is the wrong forum, I apologize. I forgot which forum I was reading before I hit 'new topic'.
First, don't use Vista to update if you can.
If the flashing stops, just reboot or use another computer to try again, your Wizard should enter bootloader automatically when you reset it. That should not brick the device (Unless you are installing Button's ROM to a G4 device).
If Wizard stuck at IPL boot screen (not bootloader), press camera+reset can let it enter bootloader directly.
Ok, I am on XP.
Well, I went ahead and killed the locked process and yanked the battery from the phone and was pleasantly surprised it came back up straight into the bootloader mode. These little phones are more resilient than I thought.
I also discovered my problem was that the ROM updater will freeze if activesync is running and connected to the phone. Knowing that, I was able to work around it and got everything on the phone updated, and am now running WM6 on it.
Thanks.
Now I can start using Visual studio.
Love Wizard
One thing that makes me love the wizard is it does rarely brick...
You must be joking...rarely does brick? Shoot, look at the Wizard wrong and BAM! Brick you shall have!
My Thunderbolt is locked somehow, and I have no way to restore it to factory defaults. What I mean by "locked" is as follows:
I remove two apps from the device, change the wallpaper and delete a contact. Then, I restart the device - when it boots back all of the changes I made are gone. It's like in read-only mode, the changes look like they take affect but after a reboot everything is restored to it's current FC'ing on everything state.
I've tried factory resetting the device but instead of booting to recovery it just boots to the picture of a phone with the red caution symbol showing, it does not do anything else.
I've tried flashing over a stock RUU image but the flash either 1) looks like it works then boots back to the state it was before, 2) hangs on part of a flash and reboots to the normal state.
The device is not rooted, I've tried revolutionary and get the following error:
"rawadb_handle_msg" and then it loses connection.
Any ideas would be appreciated, I've never seen anything like this.
Turn it on and let it boot up if it can then pull the battery while its on and leave power off for 5 minutes then try again.
Also can try, with power off, hold power button and volume down button together for a few seconds and when it gets to the white screen wait for about 10 seconds then select reboot from there
Latest OTA patched the Revolutionary exploit (so it won't work). You may want to root using ADB and flash the rooted RUU. Can't say I've ever seen R/O behavior; but then again, I've been rooted for months - currently on AOSP (ShiftAo5p 2.8) and waiting for an ICS with data
I know, not too helpful, but there are still ways to root.
Any feedback from VZW or a "real" corporate store? They're actually quite helpful here with tech junkies.
OK, one more suggestion - early on, I couldn't do anything either (Market, etc) and the fix was to pave (format) my SD card. I know it sounds weird, but I was going to exchange my phone (ordered, then sent back replacement). I figured, what the heck. Took the uSD card out, put it into my PC's USB port and formatted it FAT32, popped it back in and VOILA - happy happy joy joy.
Granted I copied all the data off of it before paving - then copied back selectively (highly recommend AirDroid, by the way, no more cables). Might give this a shot.
Hey guys, thanks for the suggestions - unfortunately no luck on my end with that
nautical34 said:
Hey guys, thanks for the suggestions - unfortunately no luck on my end with that
Click to expand...
Click to collapse
I inserted the card freshly formatted (I wasn't rooted at that point) - nothing on it, and I booted up, I was able to install Market apps (which I couldn't do before) - Note - AFTER I also did (multiple) a factory reset, I was good.
That didn't work for you? Maybe try again? Or just No-Go?
Also helps prove every 'Bolt has its own personality
Good luck on your CLNR ...
I have no idea what errant app or corrupted data may have been on the card, but totally paving and starting over "fixed it". Soon after, I rooted Then I had choices Granted I've had times I've had to do a factory reset (but not pave the SD) and set up all again - I've found the larger games (haven't determined which yet) cause my phone to get into reboot fits if I do actually reboot (which I need to do sometimes to get the radios to get data again); so, boring maybe, but very few games installed. That's OK, I prefer to learn or listening to music during idle time. Good luck.
I've had my Oneplus One since the beginning of 2015, up until now it's been honestly fantastic, with very few issues whatsoever, certainly nothing that has bothered me at any rate. That's up until last night;
My phone was lying on my desk next to me with the screen on updating some applications whilst I was writing on my computer - suddenly, it starts to vibrate, one continuous long note, I naturally picked it up and looked at it, at which point the phone turn itself off in my hand. That was unfortunately the last I ever saw of my phone alive. This happened at about 6PM yesterday evening, since then I've tried everything within my power to get it to work. I can't access the bootloader, in order to get to fastboot (which would allow me to fix all my issues by enabling me to refresh the device), nor can I access my recovery. The phone turns on and displays nothing, it vibrates, but that's it.
The phone was running the latest COS13.1.1 update (X1) which I had flashed the day before, it was running the stock kernel for the ROM, the ROM was however rooted.
I know a fair amount about android, I also know a fair amount about the OPO, to me, I think something about the LOGO partition has gone wrong. The LOHO partition being responsible for the images shown in the bootloader, fastboot, splash screen etc.... I'm just not sure how that would have happened.
Either way, I don't know what to do, the one doesn't register to my computer in fastboot or adb , so both those routes seem closed. I primarily use a Mac for my work, I'm yet to try plugging the phone into a PC.
I've submitted a ticket to OP, and have spoken to an adviser who moved my case to a 'specialist', but I'm yet to hear back on that one.
Any help would be massively useful, because I need this phone for my work, and just general communication.
Thanks for reading,
Ben
Here, try this http://http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Gday everyone.
I just got this phone and since it was first powered on I've had issues. I will likely be going back to the carrier tomorrow and asking for a replacement, but wanted to put my experience down here. Ive looked at a lot of other threads, but all of them involve unlocking of bootloader, flashing etc - I havent done ANY of this (yet). Its fresh out of the box.
Location: Australia
Carrier: Optus
Model: MHA-L09 (cant access extended model number)
So first up, had issues connecting to the carriers in-store wifi, which uses a captive portal.
When I finally got it going I was presented with a Chinese site - id accept this usually considering it is Huawei.
This phone is a replacement for my dead Note4 and as such I wanted to restore apps, as I had no internet, I skipped the process.
Got back to my office and connected to my wifi fine, so decided to factory reset to get a fresh start.
Noticed that after reset the initial process was in a different order. Restored from Google and all apps downloaded, happy days for a couple of hours, just waiting for my service to port over.
2 hours later, I decide to restart the phone, it gets hung up on the Optus logo which is displayed before the reboot starts.
Hard reboot.
System loads, I figure I may as well see about a firmware update. Get 'Package installer isn't responding' errors. Try again, works, no updates available.
Go to google photos, get 'Package installer isn't responding' error.
At this point I think, f**k - what is going on here.
So I reboot into recovery to wipe the cache. This processes fine, but then the option to reboot the phone doesn't work.
Hard reboot.
Boots into recovery without me touching it.
Hard reboot. - happens again.
So then I think, fine ok, I've upset the balance, lets do a factory reset.
Factory reset hangs on 99% for over 30 minutes.
Against better judgement - hard reboot.
Now I have the EMUI logo with a nice round 0% under it... and that's where its staying.
Thoughts?
I have to fly interstate on the weekend and cant really afford unreliable comms. Should I ditch the Huawei?
Thanks all.
So - it seems that nowhere did i find a mention of the fact that if i plug it into my PC and goto the recovery mode, it loads eRecovery. Whilst this didnt actually work (I believe it only works for CN firmware) It did give me a shutdown option. I shut it down and started it again and im back into a fresh install.
Lets see how I go now...
Never restore backups from other phone.
Wow, helpful.
I didn't restore the backup from another phone, just apps, ie google downloaded the apps I selected.
The device is still performing poorly, even a standard reboot does not succeed, instead it hangs on the carrier logo before actually rebooting.
Ill take it back to the store tomorrow and ask for another one, im hoping Ive just gotten a dud.