Hello,
after updating to MM yesterday I am stuck with a strange behaviour of my phone. I already searched everywhere if anyone has the same problems but the suggested solution proposals did not work.
But let me explain the problem first:
If I don't have the phone plugged in it just doesn't want to start at all (neither vol- and power nor power alone worked).
If I plug it in however it goes straight into a bootloop but I am able to access the boot menu. The only problem is that if I want to access the recovery menu from there it just goes back to the bootloop instead of taking me to the recovery menu.
I thought about using adb or fastboot to make progress but neither of them is able to recognize the phone.
The phone is all stock, so no root or unlocked bootloader.
Any help is appreciated as I am pretty desperate to what to do with the phone as I don't have a backup of all the data on it.
Thank you!
It's better to consult the Motorola service center they can fix it
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
Hey guys. I'm kinda desperated so let's see if there is anything else I can do.
I was playing a game on my phone and it started rebooting alone.
At this point, I long pressed the power button, don't ask me why, but I did it. and bang. it is dead. No boot, no loading, nothing. It still vibrates when I try to turn it on.
I had 30% Battery left.
I have root and my phone for 3 months.
I had Nandroid backup.
Long press power button, volume up + power, volume down + power doesn't work.
When connected to PC, I get the QHSUSB_BULK device on.
Tried to ColorOS Method but:
I cannot install ColorOS drivers cause it doesn't detect them.
I tried Qualcomm drivers and they worked, so then I used the program Msm8974DownloadTool to install ColorOS.
It went okay, all finished and I got the green letters in the end.
Still doesn't boot up, nothing changed.
I cannot detect my phone via ADB. Tried with the drivers and without the drivers and with clean drivers.
What can I do? I always had such care for my phone in case of an emergency, but for some weird reason this happened. I wasn't even messing up with the phone, it just died cause I turned it off while booting up?
Okay so, for some reason, I managed to get my phone on fastboot.
I used this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
To reset my phone.
and the phone did all the new loadings and installs ETC....in the end?
My phone still doesn't boot.
Like wow?...
cyldman said:
Okay so, for some reason, I managed to get my phone on fastboot.
I used this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
To reset my phone.
and the phone did all the new loadings and installs ETC....in the end?
My phone still doesn't boot.
Like wow?...
Click to expand...
Click to collapse
I'm sorry I can't help but one bad move was probably resetting back to stock because now you lost your root and adb access..
jukiewalsh said:
I'm sorry I can't help but one bad move was probably resetting back to stock because now you lost your root and adb access..
Click to expand...
Click to collapse
What do you mean I lost my adb access? I can still find my phone there and it's still working. (aparrently)
I tried to use the command "fastboot reboot" and while it turns off the device from windows, it still doesn't boot back up.
cyldman said:
What do you mean I lost my adb access? I can still find my phone there and its still working. (aparrently)
I tried to use the command "fastboot reboot" and while it turns off the device from windows, it still doesnt boot back up.
Click to expand...
Click to collapse
Disregard that then, when the phone is booted you have to manually give adb access but you're right when it's in recovery or other modes it's already there.
Does your screen power on at all? Do you think your LCD/digitizer could've somehow just died on you?
I highly doubt it, it happened when I shut off the phone when it was rebooting. I dont hear anything when I turn on the phone and i cant press anything or slide to unlock. nothing. so ....yeah. Weird stuff is that I did fastboot reboot and now i can't get to fastboot again. sigh.
Read this thread:
http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696
Somewhere within it is the solution to your QHSUSB_BULK problem.
Already did bro, and I fixed it, did you even read my full post? I managed to install colorOS, but it's still not booting up.
Hello guys! Last update! My phone was not even vibratting when i pressed power button. I put it to charge and finnaly I got a screen. its not what I wanted...but its a small step!
Its the Low battery charge icon! So...I've heard about this other issue about the phone not charging. Could this be it? I will be trying some techniques like https://forums.oneplus.net/threads/...een-opo-not-booting-due-over-discharge.88107/.
Hopefully it will help, but it may take some days.
Good day ,
I've been looking around for solution in this forum for two days now and none has helped me solving the problem I'm having. Hopefully by posting more specific details on this thread, you guys could help me pinpoint what to do. My main goal is to backup all data from the internal storage if possible (the data in the SD cards are backed up fine) then proceed to possibly make the phone usable again.
The phone was initially somehow soft-brick (loop on bootloader - tampered, locked, security warning and S-ON). Tried all possible actions/options on the bootloader but none has worked out, it would just prompt me back to bootloader. I am really not sure, as to how it ended up soft-brick. The phone was bought through Vodafone Australia carrier and has never been rooted etc.
So following guide on from (forums.androidcentral.com/htc-one-m8/398427-htc-one-tampered-locked-security-warning-2.html), So from the guide I've done as followed:
- I understand I have to firstly unlocked the bootloader, which was done just fine. So after Unlocked, I could still boot to hboot and getting tampered, unlocked and S-ON (no security warning).
- Then I connect my phone to fastboot, flash twrp-2.8.5.0-k2_ul.img and clear the cache
- I then tried to access the recover mode
- The phone restarted and stuck on the HTC logo with "Starting recovery..." message at the top but nothing really loaded for a long while
- So then I tried to restart it but it just won't work, I then pulled out the battery and re-inserted it
- After that, the phone was just stuck on the battery symbol with solid orange light on (this occurs if the USB cable is connected to power or computer), I tried all button, buttons up/down power hold etc (I even tried that covering middle battery part and let the outer ones connected) but none helped
-- If I unplugged the USB cable, the battery symbol and the solid orange light would still persist until it runs out of battery
-- If I removed the battery then re-insert the battery without connecting to USB cable, it's not displaying anything regardless how long I pressed the buttons (I tried holding them for more than 3 minutes which I assumed enough?)
That's pretty much everything, I really hope someone could shed some light for me - the thing is the data is fairly crucial that it may even help me prove a legal case, where some physical threats were sent out to me. :crying:
Thanks for the assistance in advance!
Help anyone?
i guess that if you didn't break your phone as i did the datas are still there and so, have you a recovery installed like twrp ? if not do it with bootloader, all you have to do is access fastboot and recovery to use adb commands and copy datas, if you can't do that i'm afraid there is no much to do without erasing all..
colton49 said:
i guess that if you didn't break your phone as i did the datas are still there and so, have you a recovery installed like twrp ? if not do it with bootloader, all you have to do is access fastboot and recovery to use adb commands and copy datas, if you can't do that i'm afraid there is no much to do without erasing all..
Click to expand...
Click to collapse
Hi there,
Thanks for your response, so I could access fastboot before and installed TWRP, the phone became 'totally' unresponsive after I installed TWRP and restart the phone.
At first it's stuck on recovery screen loading screen, then it just won't show anything. At the moment, I am wondering if there is any way to recover the internal storage data. I have contacted local HTC service center about the issue and they recommended me to go back to Australia (where I bought the phone) since they don't sell this model here in Indonesia (nearest country selling this model would be Singapore or Malaysia) - so yeah not much help from them as well.
Any other thought?
One SV does not respond
sorry wrong topic...
so, after a long weekend of working i decided to downgrade from B328 to cm11. i dont really remember what i did but i somehow ended up no os, no recovery and i cant access fastboot. i spent most of my day trying to fix my phone but have had no luck. i have twrp and cwm backups from previous installs but since i cant access recovery they are of no use. when i power my phone up it just stays on the huawei logo. when i press up+power it just reboots. i really need my phone of school and work. please help!!! any help is greatly appreciated. thanks!
so it seems that my usb cable was faulty. once i used a new cable i was able to access fast boot and installed twrp. porblem solved! damn cable!
Hi all,
Im in a desperate and urgent need of help.
My Mrs pixel 7 pro is stuck in a boot loop that restarts 5 seconds after the google writing appears when starting. I wasn't home when it happened but she doesnt really make sure her phone has some battery before turning it on, as soon as she sees 2% she starts it, so im guessing maybe she bricked it while the phone was trying to apply an update when turning it on as she said that the external battery didnt have any juice left inside.
Anyway,
I know i can wipe the phone from recovery mode and make it into a factory reset phone. The issue here is we have over 6000 photos and videos of our son in that phone that she hasnt copied to the external hard drive i gave her for months due to her not liking that her little laptop is slow.
I tried recovery mode Reboot, i tried going into safe mode (no luck as it will go straight into fastboot mode). She doesnt care about a lot of things and obviously she never unlocked the developer setting or bootloader so device state is also locked.
I am begging you, anything any info or advice on how i can get those pictures out of the phone. Is there any way i can flash the stock firmware just to make the phone start and copy them after?
Any possibility or chance or retrieval?
I am willing to pay anyone that can guide me in the right direction as there are over 6 months worth of photos and memories.
Thanks in advance and may the luck be on my side.
andyysk said:
Hi all,
Im in a desperate and urgent need of help.
My Mrs pixel 7 pro is stuck in a boot loop that restarts 5 seconds after the google writing appears when starting. I wasn't home when it happened but she doesnt really make sure her phone has some battery before turning it on, as soon as she sees 2% she starts it, so im guessing maybe she bricked it while the phone was trying to apply an update when turning it on as she said that the external battery didnt have any juice left inside.
Anyway,
I know i can wipe the phone from recovery mode and make it into a factory reset phone. The issue here is we have over 6000 photos and videos of our son in that phone that she hasnt copied to the external hard drive i gave her for months due to her not liking that her little laptop is slow.
I tried recovery mode Reboot, i tried going into safe mode (no luck as it will go straight into fastboot mode). She doesnt care about a lot of things and obviously she never unlocked the developer setting or bootloader so device state is also locked.
I am begging you, anything any info or advice on how i can get those pictures out of the phone. Is there any way i can flash the stock firmware just to make the phone start and copy them after?
Any possibility or chance or retrieval?
I am willing to pay anyone that can guide me in the right direction as there are over 6 months worth of photos and memories.
Thanks in advance and may the luck be on my side.
Click to expand...
Click to collapse
If you can enter recovery mode try to sideload the same exact ota package of the rom she's running, maybe that can help. Good luck!
andyysk said:
Hi all,
Im in a desperate and urgent need of help.
My Mrs pixel 7 pro is stuck in a boot loop that restarts 5 seconds after the google writing appears when starting. I wasn't home when it happened but she doesnt really make sure her phone has some battery before turning it on, as soon as she sees 2% she starts it, so im guessing maybe she bricked it while the phone was trying to apply an update when turning it on as she said that the external battery didnt have any juice left inside.
Anyway,
I know i can wipe the phone from recovery mode and make it into a factory reset phone. The issue here is we have over 6000 photos and videos of our son in that phone that she hasnt copied to the external hard drive i gave her for months due to her not liking that her little laptop is slow.
I tried recovery mode Reboot, i tried going into safe mode (no luck as it will go straight into fastboot mode). She doesnt care about a lot of things and obviously she never unlocked the developer setting or bootloader so device state is also locked.
I am begging you, anything any info or advice on how i can get those pictures out of the phone. Is there any way i can flash the stock firmware just to make the phone start and copy them after?
Any possibility or chance or retrieval?
I am willing to pay anyone that can guide me in the right direction as there are over 6 months worth of photos and memories.
Thanks in advance and may the luck be on my side.
Click to expand...
Click to collapse
As @acuicultor said;
Here's Googles official OTA updates and instructions etc.
From what i've read briefly and as far as i can gather (still running a stock pixel 7 pro - for the first phone in god knows how long, so i'm not well read on this device but...) if you can sideload the latest OTA update via sideload then you should in theory be able to save the data and boot again. But if you flash full firmware then your device will be wiped in the process (if that's even possible with a locked bootloader).
Very best of luck
EDIT: hmm thinking about it, you won't have enabled USB debugging in dev options, hang on, i'll reboot direct to recovery to see if i can get the device recognised without USB debugging enabled. Sorry to be vague (hopefully someone more experienced with this device will chime in with more advice), like i say, i'm not rooted, flashed with custom rom - nothing, just plain old stock so i've not read up much on proceedures for this device. Bare with me!!
Had another thought, do you or have you been using Google photos to view your images on the device. If so, did you enable backup photos online when you first set the app up? If so, they could be backed up automatically...
Edit: my bad..
Try this link
If that fails just Google 'Google photos sign in'
Just tried from recovery to run some adb cmd's, no joy without enabling debugging 1st
There may be hope... If your photos aren't backed online already from above link...
EDIT:
1. From power off state (make sure the device is charged before apply any ota update) Press vol down and power together. As soon as it boots to google logo, let go of vol down, then power. That will put you in fastboot mode where you use the vol up/down to navigate to Recovery mode and power button to select.
2. Then when you have the screen that says 'no command', press power button and CLICK vol up (releasing vol up straight away but keeping power pressed). That'll take you a blue menu at top of screen.
3. Use vol buttons to navigate to 'apply update from adb'. I have checked using 'adb devices' and 'adb reboot sideload' cmd's on PC and the device is now recognised...
Will write further instructions shortly. (no guarantees this will work tho without losing data...or even if it'll work at all - i suspect the OTA update with just fail to transfer)
OR there is another option, using the same instructions above (1) in fastboot mode use the volume buttons to navigate the menu, power button to select Rescue mode. Then contact your service center for support who will advise/offer support - hopefully, which may end up having to send the device in and still offers no guarantee of preserved data
reg66 said:
@acuicultor said;
Here's Googles official OTA updates and instructions etc.
Click to expand...
Click to collapse
Following the link it's all explained there:
- no USB-Debugging needed
- booting recovery by key combo
- no loss of any data when using the OTA files
Also turning on USB-Debugging in developer options is not necessary for the recovery. It's enabled by default and moreover the recovery doesn't consider any system settings like disabled/enabled USB-Debugging.
WoKoschekk said:
Following the link it's all explained there:
- no USB-Debugging needed
- booting recovery by key combo
- no loss of any data when using the OTA files
Also turning on USB-Debugging in developer options is not necessary for the recovery. It's enabled by default and moreover the recovery doesn't consider any system settings like disabled/enabled USB-Debugging.
Click to expand...
Click to collapse
Ahh cool. I obviously didn't read much of it! Dunno what's happened to the chap, maybe his wife has killed him lol
reg66 said:
Ahh cool. I obviously didn't read much of it! Dunno what's happened to the chap, maybe his wife has killed him lol
Click to expand...
Click to collapse
yes, maybe...
FYI: Stock recovery only uses a minimal adbd with a very limited set of commands. That's why some known ADB commands won't work.
minadbd