Hey guys I am in a frustrating situation right now, but i cant for some reason undo the loop whenever i turn on my phone it keeps popping up the warning and loops by powering off my phone and going back to that warning screen. Does anyone know how to fix this by any chance? I only unlocked my bootloader and flashed twrp and its driving me insane that whenever i press the volume down and power button it does this so i cant even enter the fastboot mode.
Swagthoo said:
Hey guys I am in a frustrating situation right now, but i cant for some reason undo the loop whenever i turn on my phone it keeps popping up the warning and loops by powering off my phone and going back to that warning screen. Does anyone know how to fix this by any chance? I only unlocked my bootloader and flashed twrp and its driving me insane that whenever i press the volume down and power button it does this so i cant even enter the fastboot mode.
Click to expand...
Click to collapse
Unbrick. Using Msmdownload tool. Thread under guide [TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)
Related
hello frnds,
i am from india (duh) ...my friend bought a galaxy nexus s two days ago..
she had it up an running and it was working as it should.. but yesterday when she woke up..what she saw was that the phone won't boot up and a it shows a lock sign on the boot screen below google and that it was heating up badly... even the pc is not detecting it..i have the phone right now and i promised her that i'll fix it...
what should i do to keep up my promise!
bootloader is locked, phone won't boot
Hello,
The lock simply means that the bootloader of the phone is currently locked (as it is from the factory).
If it won't boot past the Google screen, try removing the battery of the phone for 10 seconds, then trying again.
If this fails, remove the battery again, replace the battery, hold down the UP volume button while pressing power until you see a green android screen. If you can see this screen, then use One Click Root 5.1 in the Development Thread for Nexus S or Nexus S 4G.
hmmm..
thank for the relpy,
well i have tried all that stuff i.e removing the battery for 10 sec..(didn't work)...
wen't to recovery mode(the green android thingi...) and tried recovery option won't work..
do you mean i should flash the firmware again by using one click?
thanks in advance!!:angel:
The lock sign means that the bootloader is UNLOCKED. If you didn't see the lock it would mean that the bootloader is locked (stock). The recovery option won't work because you haven't flash any custom recovery. In fastboot mode (volume up+ power button) it should say: LOCK STATE - UNLOCKED. This means that bootloader is unlocked. Use the toolkit (found in nexus s android development) to flash stock image.
Someone tried to do stuff to the phone and messed up.
thanks
i will try this let you know.:fingers-crossed:
thanks for the help:good:
What causes this though? I have codename jb And cwm 6 on my device and it randomly gets stuck on the boot screen through out the day
I think I may be in brick mode, but if someone has an answer I would sure appreciate it.
On boot I'm stuck in "No Command". I do the volume down and power and I'm able to get the menus recovery, shut down etc and the only thing that works is to shut down. Recovery just loops me to "no command". Is there a possible solution to get back to goodness. I had my bootloader unlocked and tried to install TWRP recovery but started having issues so in using SkipSoft toolkit I relocked my bootloader and that's where the issue began.
Big thanks in advance if I can possible recover my device.
:crying:
tiger505 said:
I think I may be in brick mode, but if someone has an answer I would sure appreciate it.
On boot I'm stuck in "No Command". I do the volume down and power and I'm able to get the menus recovery, shut down etc and the only thing that works is to shut down. Recovery just loops me to "no command". Is there a possible solution to get back to goodness. I had my bootloader unlocked and tried to install TWRP recovery but started having issues so in using SkipSoft toolkit I relocked my bootloader and that's where the issue began.
Big thanks in advance if I can possible recover my device.
:crying:
Click to expand...
Click to collapse
When you get to the no command screen, press and hold the power button and then push volume up. That should boot it into recovery.
robocuff said:
When you get to the no command screen, press and hold the power button and then push volume up. That should boot it into recovery.
Click to expand...
Click to collapse
Thanks, but I've tried that a few times and it still loops me back to the "no command" screen...
Well I was able to get to the recovery screen, thanks...I tried to do a factory restore and did not work. Called Google and was able to return. Bootloader says locked so I'm hoping there will not be a hiccup when they get the replacement.
I had a similar issue (phone had unlocked bootloader, rooted, phone shut off unexpectedly and wouldnt charge after that. Had the same issue of not being able to get into recovery mode, would just bootloop after selecting recovery) and ended up doing an RMA through google. I have a question in terms of recovering data from a Pixel phone in this state, is it possible? I was unable to recover my data, just curious if it is possible.
llong31 said:
I had a similar issue (phone had unlocked bootloader, rooted, phone shut off unexpectedly and wouldnt charge after that. Had the same issue of not being able to get into recovery mode, would just bootloop after selecting recovery) and ended up doing an RMA through google. I have a question in terms of recovering data from a Pixel phone in this state, is it possible? I was unable to recover my data, just curious if it is possible.
Click to expand...
Click to collapse
I cannot answer that question but I'm glad you were able to get your data. My Pixel was toast so not a chance to get data back!!!
:cyclops:
Hello, I recently came on a pixel phone to build and use lineageOS on. Upon rebuilding, I believe I performed adb sync wrong the device and damaged system. After that, my adb keys became unauthorized and I am unable to access the bootloader menu(I press power and volume, but phone boots into Bootloop). I tried the steps to get to bootloader menu, but the phone doesn't power completely off, and when I press the power button it gives me the launch screen saying press power to pause/continue boot, not allowing me to go into bootloader
My bootloop goes like this: Bootloader integrity screen(bootloader unlocked, cannot be verified) --> Google loading screen --> Android recovery. This shows 2 options with the message, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device". The two options are to try again or data reset.
I press try again, and the same bootloop ensues, sometimes getting to lineage loading logo, but then back to the same recovery error regardless. If I press the buttons(power and vol up), to go into recovery, it just shows an android with a warning sign above it, giving a message saying "Error!" on the bottom. My adb on the computer shows as unauthorized, so I don't know how I can fix this. Google has said the warranty is expired and cannot do anything to help. Ideas to fix? Thanks for help in advance!
Use power and volume down (not up) to go into Fastboot mode. Then flash the stock images
NZedPred said:
Use power and volume down (not up) to go into Fastboot mode. Then flash the stock images
Click to expand...
Click to collapse
I tried that, but whenever I press any button, the phone is never turning completely off unless it dies. Even after that, it goes to the screen showing the secure boot integrity(Press power to continue/stop boot)
How can I completely shut off the device and restart it? And if system is messed up, will that leave my bootloader intact(I'm assuming so as boot is a different partition?)
mycalculations said:
I tried that, but whenever I press any button, the phone is never turning completely off unless it dies. Even after that, it goes to the screen showing the secure boot integrity(Press power to continue/stop boot)
How can I completely **** off the device and restart it? And if system is messed up, will that leave my bootloader intact(I'm assuming so as boot is a different partition?)
Click to expand...
Click to collapse
Does holding down the power button for 5-10 seconds turn it off? Or if you do that does it appear to turn off and then restart?
If that fails to turn it off, try just holding power and volume down for 5 seconds, and if the screen flashes (goes off and then on) let go of the power button but keep holding volume down and hopefully it goes into Fastboot.
That should work unless you have a dodgy power or volume button. The bootloader is completely separate to the boot partition, and the fact that it's doing anything at all suggests that it's still functioning.
Only other option I can think of is trying ADB commands when it's in recovery mode, e.g. adb reboot bootloader. However, if you have the stock recovery, that may not work.
NZedPred said:
Does holding down the power button for 5-10 seconds turn it off? Or if you do that does it appear to turn off and then restart?
If that fails to turn it off, try just holding power and volume down for 5 seconds, and if the screen flashes (goes off and then on) let go of the power button but keep holding volume down and hopefully it goes into Fastboot.
That should work unless you have a dodgy power or volume button. The bootloader is completely separate to the boot partition, and the fact that it's doing anything at all suggests that it's still functioning.
Only other option I can think of is trying ADB commands when it's in recovery mode, e.g. adb reboot bootloader. However, if you have the stock recovery, that may not work.
Click to expand...
Click to collapse
Thank You!!! It didn't work in the bootloop, so I had to let the phone drain its battery and shut itself off, then I was able to enter the bootloader and reinstall lineage. Thanks so much!
mycalculations said:
Hello, I recently came on a pixel phone to build and use lineageOS on. Upon rebuilding, I believe I performed adb sync wrong the device and damaged system. After that, my adb keys became unauthorized and I am unable to access the bootloader menu(I press power and volume, but phone boots into Bootloop). I tried the steps to get to bootloader menu, but the phone doesn't power completely off, and when I press the power button it gives me the launch screen saying press power to pause/continue boot, not allowing me to go into bootloader
My bootloop goes like this: Bootloader integrity screen(bootloader unlocked, cannot be verified) --> Google loading screen --> Android recovery. This shows 2 options with the message, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device". The two options are to try again or data reset.
I press try again, and the same bootloop ensues, sometimes getting to lineage loading logo, but then back to the same recovery error regardless. If I press the buttons(power and vol up), to go into recovery, it just shows an android with a warning sign above it, giving a message saying "Error!" on the bottom. My adb on the computer shows as unauthorized, so I don't know how I can fix this. Google has said the warranty is expired and cannot do anything to help. Ideas to fix? Thanks for help in advance!
Click to expand...
Click to collapse
Similar problem when i try to flash pixel dust rom through adb sideload... After successful installation reboots to system through twrp it shows no os installed then after i cant get to bootloader only black screen shows no display and now on pc phone not detecting .... connect and disconnect sound is there but nothing on screen
LANDTESTER said:
Similar problem when i try to flash pixel dust rom through adb sideload... After successful installation reboots to system through twrp it shows no os installed then after i cant get to bootloader only black screen shows no display and now on pc phone not detecting .... connect and disconnect sound is there but nothing on screen
Click to expand...
Click to collapse
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
mycalculations said:
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
Click to expand...
Click to collapse
Oh so after that i can get to bootloader .....hmm let me try thanks bro
mycalculations said:
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
Click to expand...
Click to collapse
My bootloader is unlocked but phone not detected on pc only black screen nothing else.... Red light flashes whenever connect to charger
I use this forums a lot for info but in this case i can't find any leads of whee to go with this, so wondering if someone can chip in some ideas?
I flashed a ROM via flashtool but wasn't happy with it, so i thought i'd just go back to stock and so used flash tool AKA emma to flash one of the options given there.
First attempt to flash it said "flash failed" or something like that and had the "flashing failed, connect to computer" note in the phone when booting it. (I'm sort of making up the terms, not that much into the tech ). Anyway, i tried flashing the same FW again and this time it went through really quick being 'completed' in a few seconds.
Now when i try to boot it gets stuck in the 'Sony' logo. Can go into Fastboot but no Flash Mode (nothing happens using the vol down key), and USB debugging seems to be off now as well.
Emma only works in Flashmode so can't do anything with that. Flashtool doesn't offer anything useful in Fastboot and Xperia Companion recognises the phone when in Fastboot but asks that i unlock the screen and enter MTP...
Any help of where i can go with this?
Thanks
P.s. While keeping buttons pressed randomly it went once into flash mode, but trying to flash a ROM with flashtool it got stuck at "reding device data" and i haven't been able to enter the mode again. Is there an alternative key press combination that i stumbled on by chance? I think i just kept vol up and power held for a while and let go at a random number of phone vibrations
Just tried: Flashed twrp via fastboot and then rebooted into recovery. Same thing. It still opens to Sony splash screen and stays there
Ok, i'm kind of talking to myself here, but mild success and something that might help someone.
Managed to get back in flash mode. Don't know if it's a fluke, unique to this phone, or how it's actually meant to work, but the sequence is:
From the freezed up splash screen, and the USB connected, press and keep pressed power+vol up (hard restart/shutdown)
You get a single vibration, if you let go here it restarts. Keep pressing
You get a triple vibration, if you let go here it shuts down. Keep pressing
You get a single vibration, if you let go here it starts in fastboot. Keep pressing
You get a second single vibration, if you let go here it starts in flash mode.
Possibly a fluke but don't want to have to try again!
Anyway, i managed to flash the last working firmware and it's all good, yet this is the unwanted one. So issue is i still need to downgrade the phone to 7.1.1
I've tried to install new system in my Xiaomi Redmi Note 4 MTK.
From the system that I downloaded (I downloaded the correct version) I picked in TWRP to install from boot.img.
Unfortunately the system didnt boot but I could still enter recovery or fastboot.
Then I chose preloader.img and clicked reboot because I thought that at the worst case I'd jsut enter fastboot and fix it.
After this the screen doesnt lit up at all.
The only response is the vibration.
It keeps rebooting over and over again.
Is there any way to save it?
It seems to stop bootlooping when I hold all the buttons at once for a while but when I hold the power button the bootloop starts again.
Re-flash Stock ROM
Is it possible in my situation when I can't access recovery and fastboot?
Can you please tell how can I do that?
Have you tried: With phone off, hold volume up, and insert usb cable. This should turn the phone on and go into download mode or something like that.
TouchOdeath said:
Have you tried: With phone off, hold volume up, and insert usb cable. This should turn the phone on and go into download mode or something like that.
Click to expand...
Click to collapse
I believe its called the fastboot mode and as I said I unfortunately can't go there :/
Yes, we are talking about Mi logo stuck problem during boot. ... OR mobile goes in bootloop where every time shows Mi logo on the screen and shut House Cleaning Services Dubai
While installing your stock rom for your mediatek phone using sp flash tool just click the format all + downlaod option. This may blank out your imei and personal phone specific info
guys plz, you're talking like if I had any access to my phone.
I think I wrote it quite clearly that the only response that I get are vibrations and I dont see Mi logo. It's on for like a split second. Can't go to fastboot or recovery.
I talked about it with a guy on discord and it's loading preloader before boot that should go first so it can't be helped without valid tools. Makes sense to me, already bought a new phone.