Hello all!
I have a OnePlus One that will not boot. I cannot get into fastboot or adb. My phone has been unlocked and is rooted / has custom recovery. When trying to use the ColorOS tools, this is what I get when I press the big button: http://i.imgur.com/2SL4EE5.png
I already sent in an RMA, but that won't get a response for a couple of days. Anything I can do?
Related
Hello, friends at XDA!
My dad has a MyTouch 4G Slide. I didn't want to root it because, ironically, I wanted him to have better support and not end up with a bunch of questions from T-Mobile, should he ever need support. I'm now regretting that decision; his future devices will be rooted out of the box...
The phone, in its current state, will get as far as the splash screen. It will sit there for about 20 seconds, and then turn the screen off. After another ten seconds or so, the phone goes back to the splash screen again.
I can get myself into the bootloader, which is still S-ON. That works reliably, but it's still a bit of a dead end. It checks for a baseband update on the phone, and upon not finding an applicable file on the SD card, spits me back into the fastboot menu. Naturally, I went for the recovery environment. I was able to get to it last night, but even that was a bit shallow in that I got to the red triangle screen, but no menu options were presented. Still, I figured that the recovery environment would allow me to run Unrevoked or similar, but when I came home the phone was camping out on the "waiting for device..." screen, to no avail.
My goal was to root in order to install a recovery environment; I know that ClockWorkMod and TWRP both allow for data to be backed up from within the recovery environment. There are call logs and contacts (no, they're not synced with Exchange or Google) that would be greatly appreciated if I could recover before I perform a factory reset as T-Mobile has instructed me to do.
Is there a way I can flash a recovery environment onto this phone using only the access provided by the phone's search for a baseband update from the bootloader?
Thank you for your time and assistance in this matter.
Joey
Unfortunately no, if you can't boot to os and have stock recovery then you have no adb access which means chances of recovering any data is nil
The red triangle is stock recovery, some combo of buttons (like volume up and down) will bring you options but I forget which ones
Hopefully a factory reset will bring your phone a live as you need to get to the os just to unlock your bootloader so you can flash a custom recovery and root the phone
Sent from my Nexus 4 using xda premium
I always root my phone so I'm not sure but,
You can try to start the device by pressing the power and volume - key at the same time.
Then connect to the pc and try the toolkit.
Maybe others can comment if this wil work.
Sent from my HTC One X using xda app-developers app
No Solution
Hey guys,
by some miracle I managed to get the phone working JUST long enough to run a MyBackup Pro task on it; T-Mobile performed a warranty swap on the phone. There was no consistent solution to it though, but thanks for the input everyone.
Joey
Looked around a lot and found no solution so here it goes.
I was trying to update to KitKat and at the Pwr Volume- screen I mistakingly hit the wipe data. I wasn't on a custom ROM before, I used the clockwork mod app to install TWRP. Now I'm stuck on the screen where it says This Device is Unlocked and won't do anything else. I've tried every restart button combo but it always goes back to that screen. Can anyone help me out please or is this a lost cause.
Also the computer does not recognize it since it won't get past the opening screen and fastboot/adb wont do anything either
Wipe data in bootloader mode when unlocked = bricked for good unless you have nvflash backups
Or, if you can get back into bootloader mode, follow busters method to unbrick
Sent from my GS3 on AOSB 4.4.2 using Tapatalk 4
Don't have NVFlash backups and I cant get to the boot loader so I guess I'm boned. Was good while it lasted, was running slow towards the end so I guess it was about that time lol
Hi I tried going back to stock on my phone using RSD LITES and after it saying successful it is now stuck on "Warning Bootloader Unlocked Screen"
I cannot get it into recovery mode tried method Poer and holding + & - buttons but no joy I tried hard resetting the phone Power and - buttons
but reset onto a black screen with a green charge light.
I was using a custom rom with Philz bootloader on it. I did attempt to back-up my phone but failed. Is there any hope in reviving this phone at all. I have looked I think everywhere on here and found similar results but not the results im looking for.
Is there a way of forcing the phone into fastboot mode without using the phone directly and just a PC over ride?
I have sdk tools, adb and fastboot also Droid HD Utility but none have found my device as its not in fastboot mode.
I wish I didnt start the stock downgrade at stupid o'clock in the morning and wish any of you guys can help with my situation.
Hello my friend. Were you rooted before? If you were , then u must have taken a back up
Yesterday I got my knew phone and unlocked the bootloader. I did this, because I want to root it (when I have more time). But today the phone downloaded Android 10 update and I installed it. After installing, the phone is "bricked" and in boot loop. I cannot turn it off. Volume down and power keys won't help. I cannot get into recovery mode either. The only option is download mode. But in download mode, the USB is not recognized by my PC. Already downloaded the newest Samsung USB driver. I flashed my old phone (Samsung S7) by Odin several times, with the same PC.
Is it in bootloop, because I installed the Android 10 update with an unlocked bootloader?
Any advice?
No advice, but I did exactly the same thing, and mine also bricked, so yeah, it seems like upgrading to Android 10 on an unlocked phone causes a bootloop. I returned mine, didn't want to deal with this on a brand new device.
Somehow I managed to make a good USB connection and flashed the Android 10 firmware by Odin. Tried the CSC_home option, but then after boot it was stuck at "SAMSUNG" screen for more than 30 minutes. Killed the phone by using volume down + power buttons. After this I could enter recovery mode and did a factory reset.
Best thing is, like you said, to return the phone. But I didn't want to wait that long
So people, be warned. Do not update from Android 9 to 10 with an unlocked bootloader!
hi everybody. there was the same situation, friends, please tell me what to do? what can I do to bring my phone back to life?
acid umbrella said:
hi everybody. there was the same situation, friends, please tell me what to do? what can I do to bring my phone back to life?
Click to expand...
Click to collapse
Read the comment above
Hi all.
I read that my oneplus 9 was able to test the beta of android 12 and found that I could do so in developer options and choose the dsu loader. Did that and now my device won't work at all. I can't get into recovery and factory reset it or anything it just restarts itself and i get an error message saying the device is corrupted and won't boot. Is it any way to fix this or have my own foolishness killed this phone? Please help
Illusions_887 said:
Hi all.
I read that my oneplus 9 was able to test the beta of android 12 and found that I could do so in developer options and choose the dsu loader. Did that and now my device won't work at all. I can't get into recovery and factory reset it or anything it just restarts itself and i get an error message saying the device is corrupted and won't boot. Is it any way to fix this or have my own foolishness killed this phone? Please help
Click to expand...
Click to collapse
Not all hope is gone. If there is an msm tool for your variant your in luck. I have the global unlocked op9 and there isn't one yet. Although you can use a fastboot rom from xda. And there is always last resort of calling OnePlus customer service and getting a remote session . Explain to them you tried the beta release and now phone is unuseable . Hope you get it fixed as I bricked my op8 a month or so ago and it's a bad feeling. I also read the developer previews were not for north American devices. Maybe you saw that as well.
Illusions_887 said:
Hi all.
I read that my oneplus 9 was able to test the beta of android 12 and found that I could do so in developer options and choose the dsu loader. Did that and now my device won't work at all. I can't get into recovery and factory reset it or anything it just restarts itself and i get an error message saying the device is corrupted and won't boot. Is it any way to fix this or have my own foolishness killed this phone? Please help
Click to expand...
Click to collapse
If you can boot to fastboot mode. Then fastboot format userdata I think
Didn't work. Think my bootloader is locked as well since I haven't unlocked it at all. Just read online that you could test the android beta by using that dsu thing and now my phone is gone. It was completely stock hadn't touched a thing except that I got into developer options. I didn't think i could brick a phone without mixing with ROMs and stuff.
Can you get it to bootloader?
Power off completely, then 3-button hold (vol up + vol down + power) till bootloader screen.
If you can, and you can get fastboot to recognize the device, you might have a shot at fastboot oem unlock, and then possibly a fastboot rom.
If not, then you might ask Oneplus support for an MSM tool
reaper000 said:
Can you get it to bootloader?
Power off completely, then 3-button hold (vol up + vol down + power) till bootloader screen.
If you can, and you can get fastboot to recognize the device, you might have a shot at fastboot oem unlock, and then possibly a fastboot rom.
If not, then you might ask Oneplus support for an MSM tool
Click to expand...
Click to collapse
No luck with OEM unlock. Contacted oneplus here in sweden and will send the phone to them on Monday hoping they can fix it. Never thought i could mess upp a phone so much by just tinkering with settings within the phone but you live and learn all the time i guess. Bit sad since I got the phone two days ago