Related
Okay so I seem to have run into a little problem I was planning on updating cleanrom up to 1.2.5 but was on cwm. I had managed to switch over successfully to twrp 2.2.0. I went ahead and used goo manager to download the updated zip of 2.2.1 and tried flashing it thru twrp. Now I am stuck in google bootloop and cant get into recovery or more importantly bootloader. I have been trying last 30mins to hold power and both volume buttons but it either keeps rebooting back to the google screen or not doing anything at all just have to repress to to turn it off but it will turn back on automatically. I tried hooking it up to my usb and labtop but it looks like it wont even recognize it. I just fully charged it so I am good for now just a little worried cant get out of this mess.
I ran into a problem like that with clockwork recovery it kept on rebooting in recovery but I could still go into download mode I was at work away from my computer so I had no choice but to keep trying that three button magic until it finally restored a backup I had on my external card.just keep on trying to pull the battery then try to go into recovery. You might 've gotten a bad download
Sent from my SGH-T999 using xda premium
problem is I cant get into recovery. or the green screen to get to bootloader. It just completely stuck in a bootloop on the google screen mocking me... I am really contemplating opening it up and taking out battery but is that a good idea? Or is there anything else I can do?
so I pulled off the back cover but really dont want o disconnect the battery might mess something up but I cannot get the device to shut off.
disconnecting the battery does nothing it shuts it off and keeps it off but when I connect it to the charger the battery symbol pops up for a second and then goes completely blank. I went ahead and tried again to boot into bootloader pressing power vol up + down and all combinations of power vol -, power vol +
power turbo press vol +/- but no luck still in google screen.
If you're in a bootloop you need to connect your Nexus 7 to a computer. Then you will be able to access recovery via the Power button and volume buttons.
is it going to make a difference that everytime i try to reboot it just the black google screen? I have tried it connected to the wall charger and connected usb to the labtop but nothing.
clago87 said:
is it going to make a difference that everytime i try to reboot it just the black google screen? I have tried it connected to the wall charger and connected usb to the labtop but nothing.
Click to expand...
Click to collapse
It's supposed to do that when you're trying to go to recovery from bootloader without the USB cable plugged into a computer, may need to have the drivers installed on said computer. It's an issue with the nexus 7 bootloader and every one of them does it. What your experiencing is perfectly normal if you tried to go to recovery from bootloader with the bolume buttons and then got the google screen bootloop.
If it doesn't work when you plug it in and try, then try unplugging it, manually rebooting with it plugged in first, or vice versa
Update: I can get on Team Viewer and remotely reboot you into recovery through the PC if you want, or at least give it my best shot.
ok so i disconnected battery and have the device off. I should then try connecting it to the pc and try booting up holding down all buttons?
clago87 said:
ok so i disconnected battery and have the device off. I should then try connecting it to the pc and try booting up holding down all buttons?
Click to expand...
Click to collapse
Have you installed the right drivers on the computer you're using, for ADB and the device drivers, when you unlocked and rooted?
Answer to your question is yes try that. But I wouldn't be disconnecting and reconnecting it, I can't recommend that and then learn tomorrow that static zapped something important.
yea I am getting nothing by connecting to pc. I have all the drivers adb and fastboot installed when I rooted and unlocked couple weeks back but it looks like device is not being recognized or read at all by the pc.
connecting to the pc holding the volume + button gets it recognized for a second and tries to install a driver apx but unsuccessfully.
I am not making any progress whatsoever kinda sucks starting the weekend like this. I have gone thru some bad stuff with my atrix but nothing like this were I cant even access my bootloader boot into recovery or even fastboot. Should I try and get it to just stay off and see if overnight it works its own magic? Hate going to sleep witht his on my mind but I think with a clear mind in the morning something good will happen.
I can get it to stay off by holding both vol+ and vol- but trying to turn it off with just the power button just keeps it turning back on/off...
so I slepted on it thru the night let the tablet rest but went back this morning and I still cant get into bootloader or recovery. Is there anything I can do?
Has anyone else had this problem where they cant boot into recovery or bootloader? It's like the power button and vol keys are unresponsive even though they still work to turn on the device.
are you sure that you flashed the right recovery? but you should still be able to get the bootloader. are you pressing power + volume down(volume down, not both volume buttons. i noticed you wrote both volume buttons) to get into the bootloader?
I think I chose the right recovery the first version downloaded thru goo manager but it was the 2.2.0 version. I had the option on the of downloading the 2.2.1 zip or the .img but i downloaded the .img to just to flash with the current version of twrp that was working. There have been times were I have not been able to get into recovery on my atrix or htc but I've always been able to get into the bootloader this is the first time I've been locked out of my device kind of got me scared its not even a month old. So you say to get into bootloader you dont have to hold down both volume buttons? I will try again to power back up using the volume down and power button at same time... Wish me luck
clago87 said:
I think I chose the right recovery the first version downloaded thru goo manager but it was the 2.2.0 version. I had the option on the of downloading the 2.2.1 zip or the .img but i downloaded the .img to just to flash with the current version of twrp that was working. There have been times were I have not been able to get into recovery on my atrix or htc but I've always been able to get into the bootloader this is the first time I've been locked out of my device kind of got me scared its not even a month old. So you say to get into bootloader you dont have to hold down both volume buttons? I will try again to power back up using the volume down and power button at same time... Wish me luck
Click to expand...
Click to collapse
good luck!
yea, only power button and the volume down button.
quick question before I connect the battery does it make a difference whether or not I have it plugged in charging or connected to the PC while trying to boot into bootloader?
Hi guys, just got a new Nexus 7, and I love it - or loved; 'cause it doesn't power on anymore.
When I took it out of the box, it told me it had to update to 4.3, which it succesfully did (I checked the about tablet section in the settings to make sure). After installing 4.3, I set it up and used it for a few days, until this afternoon. I was on the train and it said it had downloaded an update. I clicked it to see the changelog and was suprised to see that it said it had to upgrade to 4.3 again.
I ignored the update and stuffed the tablet in my bag.
Here's when the trouble starts. When I took it out, it was powered off. Holding the power button for a few seconds did nothing, neither did holding it long or pressing it shortly, or vol+ and vol- and power for fastboot. Suddenly it turned on again, but it was unusable because it kept spamming "unfortunately, process.gapps. has stopt. I rebooted it into safe mode, but this didn't help. After turning it off again, it now won't start again. I don't have USB debugging enabled and couldn't get to the setting so using fastboot commands won't work.
Could anyone please help?
Thanks a ton in advance!
It was stock? Sounds like it sit down in the middle of the update. I berry flashing the latest gapps would fix..
Sent from my Nexus 7 using xda app-developers app
markvdn said:
Hi guys, just got a new Nexus 7, and I love it - or loved; 'cause it doesn't power on anymore.
When I took it out of the box, it told me it had to update to 4.3, which it succesfully did (I checked the about tablet section in the settings to make sure). After installing 4.3, I set it up and used it for a few days, until this afternoon. I was on the train and it said it had downloaded an update. I clicked it to see the changelog and was suprised to see that it said it had to upgrade to 4.3 again.
I ignored the update and stuffed the tablet in my bag.
Here's when the trouble starts. When I took it out, it was powered off. Holding the power button for a few seconds did nothing, neither did holding it long or pressing it shortly, or vol+ and vol- and power for fastboot.
Click to expand...
Click to collapse
Isn't it volume down + power button to get into the bootloader?
BTW, it's not repeatedly updating TO 4.3, the updates are FOR 4.3. You'd see the build number in About changing, while version stays the same (4.3)
You do NOT need USB debugging on to use fastboot, only adb. Fastboot works independent of anything system related. That's the whole point of fastboot.
Where have you bought your device?
I think it's the best solution to return your device to the shop you bought it and request for a new one...
just power + vol down for fastboot (after power off)
than flash factory image.... lots of guides here.
Flashing the new gapps via cwm should fix it
Sent from my GT-I9505 using Tapatalk 2
meekrawb said:
Isn't it volume down + power button to get into the bootloader?
Click to expand...
Click to collapse
Yeah, some ****ty site got it wrong. I found out and unlocked the bootloader, which factory reset it. But now it won't boot at all.
Richieboy67 said:
It was stock? Sounds like it sit down in the middle of the update. I berry flashing the latest gapps would fix..
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
That might be the case, power button must have been pressed in my pocket.
I'll try a flash of the stock rom later. I unlocked the bootloader and now it won't boot at all.
di11igaf said:
You do NOT need USB debugging on to use fastboot, only adb. Fastboot works independent of anything system related. That's the whole point of fastboot.
Click to expand...
Click to collapse
Yeah, figured that one out today. Problem was, fastboot and adb needed to be updated to verify the device.
GoneTomorrow said:
BTW, it's not repeatedly updating TO 4.3, the updates are FOR 4.3. You'd see the build number in About changing, while version stays the same (4.3)
Click to expand...
Click to collapse
Ah right, that makes more sense. Probably a wonky translation or i've misread the text. It didn't make any sense to me
Maybe you can try to use "Nexus Root Toolkit 1.7.2" and install a stock rom 4.3 from Google's repositories. But I'm not sure your tablet will let the computer modify anything if you did not accepted his ID on debugging menu.
About 2 weeks ago after updates were installed for Android 7 my volume up and down keys stopped working. I down loaded a 3rd party app...problem solved. Well no...Tuesday my phone decided to go to Factory Hard Reset screen and since I cant used the volume key all I can do is #2 Factory reset over and over. I would like to go back to 6.0.1 or some other version to see if that will fix the problems but I cant get the phone in download mode because the volume keys dont work....Please help. It is a Verizon SM-N920V
[email protected] said:
About 2 weeks ago after updates were installed for Android 7 my volume up and down keys stopped working. I down loaded a 3rd party app...problem solved. Well no...Tuesday my phone decided to go to Factory Hard Reset screen and since I cant used the volume key all I can do is #2 Factory reset over and over. I would like to go back to 6.0.1 or some other version to see if that will fix the problems but I cant get the phone in download mode because the volume keys dont work....Please help. It is a Verizon SM-N920V
Click to expand...
Click to collapse
While the phone is on and developer options enabled and also OEM unlock enabled, connect the phone to a P.C. Make sure you have minimal adb and fastboot installed on your P.C. also and while you're in the adb folder open a command prompt window and type
adb reboot download
The phone will then boot into download mode..
MrMike2182 said:
While the phone is on and developer options enabled and also OEM unlock enabled, connect the phone to a P.C. Make sure you have minimal adb and fastboot installed on your P.C. also and while you're in the adb folder open a command prompt window and type
adb reboot download
The phone will then boot into download mode..
Click to expand...
Click to collapse
but OP will have another issue to face
as when we use odin to flash back to stock, we will always HAVE to press power up + home + power key to go to stock recovery to wipe again or else will forever stuck in boot animation
assuming if OP's phone is really a hardware issue, booting to download mode will be successful but after flashing stock, thats the problem OP has to face (if its a hardware issue)
leongzxc said:
but OP will have another issue to face
as when we use odin to flash back to stock, we will always HAVE to press power up + home + power key to go to stock recovery to wipe again or else will forever stuck in boot animation
assuming if OP's phone is really a hardware issue, booting to download mode will be successful but after flashing stock, thats the problem OP has to face (if its a hardware issue)
Click to expand...
Click to collapse
I really dont think its a hardware issue. nothing happened to the phone and the buttons are springy and not stuck they just dont adjust the volume. Thats why I hope going back to 6.0.1 will fix it.
Thanks!
leongzxc said:
but OP will have another issue to face
as when we use odin to flash back to stock, we will always HAVE to press power up + home + power key to go to stock recovery to wipe again or else will forever stuck in boot animation
assuming if OP's phone is really a hardware issue, booting to download mode will be successful but after flashing stock, thats the problem OP has to face (if its a hardware issue)
Click to expand...
Click to collapse
The phone will update itself automatically as long as there's a cache.img being flashed and it's usually in the firmware.. Just need to make sure odin is set to automatically reboot after flash.
MrMike2182 said:
While the phone is on and developer options enabled and also OEM unlock enabled, connect the phone to a P.C. Make sure you have minimal adb and fastboot installed on your P.C. also and while you're in the adb folder open a command prompt window and type
adb reboot download
The phone will then boot into download mode..
Click to expand...
Click to collapse
I get the error
device '(null)' not found
I can see my phone on the pc though......what did I do wrong
Thanks
[email protected] said:
I get the error
device '(null)' not found
I can see my phone on the pc though......what did I do wrong
Thanks
Click to expand...
Click to collapse
I got it to reboot in download....yeah!
Now to get to firmware installed
Thanks
Everything seemed to work good BUT.....
Now Im stuck on the Verizon screen...can you point me to a link for a Verizon SM-N920V firmware download. Preferably marshmallow. or tell me what I did wrong. I have the basic idea just missing a step or something I think.
Finally went to next screen. Back to factory reset...no volume buttons.....restarted again still in safe mode
Thanks
[email protected] said:
Everything seemed to work good BUT.....
Now Im stuck on the Verizon screen...can you point me to a link for a Verizon SM-N920V firmware download. Preferably marshmallow. or tell me what I did wrong. I have the basic idea just missing a step or something I think.
Finally went to next screen. Back to factory reset...no volume buttons.....restarted again still in safe mode
Thanks
Click to expand...
Click to collapse
Then it's unfortunately a hardware issue and if the phone is less than 1 year old Samsung would be willing to fix it free of charge so long as you didn't cause the damage..
Also trying pressing the buttons like a bit forceful and quickly that way if it is stuck under the actual button then it will maybe loosen up..
I was afraid you were gonna say that....I'm just out of warranty. Thanks
Hi
i bought before 2 weeks Xiaomi a1
it wored very good.
Today while I wanted to turn on the screen it did not respond.
The phone is not responding to any type of pressing.
I must say that the phone is new, did not get any kind of hit , and 5 min before this problem it used to work really good.
I think that the phone is in brick mode, and i can't enter to fastboot option because the phone is not responding....
Pls help my solve this problem.
Thanks
Try holding the pwoer button for more then 10 seconds, that should reset it... once you start it up aghain turn of ambient screen... Gave me troubles too... Hope that helps.
Has that still not been fixed with November update? I turned my ambient screen back on to see. So far, 2 days since update and no black screen after notification.
I'm guessing it's not dead. I have the same problem before as well. It was the buggy Ambient Display. Force restart your phone by pressing power button and holding it more than 10 second. First thing on boot up complete, go to Settings > Display and turn off Ambient Display.
micleftic said:
Try holding the pwoer button for more then 10 seconds, that should reset it... once you start it up aghain turn of ambient screen... Gave me troubles too... Hope that helps.
Click to expand...
Click to collapse
I cant even turn on the screen...
It's not showing any thing on the screen.
I tried to push the power but there is no respond
myself379 said:
I'm guessing it's not dead. I have the same problem before as well. It was the buggy Ambient Display. Force restart your phone by pressing power button and holding it more than 10 second. First thing on boot up complete, go to Settings > Display and turn off Ambient Display.
Click to expand...
Click to collapse
I tried forcing it. But it is still show black screen.
I think it is in brick mode
roy123456 said:
I tried forcing it. But it is still show black screen.
I think it is in brick mode
Click to expand...
Click to collapse
Just go in fastboot mode and reflash the firmware from MIUI.con
jack_21 said:
Just go in fastboot mode and reflash the firmware from MIUI.con
Click to expand...
Click to collapse
How can I enter the fastboot mode?
I cant even turn it on.
It is not respoding.
I tried to put it on this mode but the screen is still black.
roy123456 said:
How can I enter the fastboot mode?
I cant even turn it on.
It is not respoding.
I tried to put it on this mode but the screen is still black.
Click to expand...
Click to collapse
You must keep pressed vol down + power until the phone does show "FASTBOOT"
jack_21 said:
You must keep pressed vol down + power until the phone does show "FASTBOOT"
Click to expand...
Click to collapse
How long?
I tried it for 3 min ...
Is it enough?
roy123456 said:
How long?
I tried it for 3 min ...
Is it enough?
Click to expand...
Click to collapse
Well there is something strange.
Leave the phone discharge
Then let it charge
Then power on with vol down + power
Try these 2 things
1) charge your phone for 2-3 hours. if didnt switch on try this 2
2) Connect your data cable with pc. In mobile Press volume up + volume down and plug in the other end of usb cable to your mobile. you need to hold the keys. this will boot your phone into fastboot.
If boot steps didnt work then it might be a hardware problem or hard brick.
selvarajrajkanna said:
Try these 2 things
1) charge your phone for 2-3 hours. if didnt switch on try this 2
2) Connect your data cable with pc. In mobile Press volume up + volume down and plug in the other end of usb cable to your mobile. you need to hold the keys. this will boot your phone into fastboot.
If boot steps didnt work then it might be a hardware problem or hard brick.
Click to expand...
Click to collapse
What can I do if it is a hard brick?
roy123456 said:
What can I do if it is a hard brick?
Click to expand...
Click to collapse
Visit customer care(they will probably say motherboard problem as always) or try qfil method which is quite complex if this flashing things are new to you.
roy123456 said:
How long?
I tried it for 3 min ...
Is it enough?
Click to expand...
Click to collapse
you should press the power key while charging cable connected.If it doesn't work , unplug the charging usb and plug again reverse(type c's reversibility).If it can't, try with another AC source,another person,another location.
My A1 reborn by my gf's charging adaptor,hand and location.(she know nothing about android hard key combination)
Just thinking,don't know exactly.Sorry for my english.
My was hang.. so I restarted it.. but aftr tht.. phone is not turning on.. its just showing anroid one.. and nothhing else
ruhi maallivk said:
My was hang.. so I restarted it.. but aftr tht.. phone is not turning on.. its just showing anroid one.. and nothhing else
Click to expand...
Click to collapse
reflash phone with stock firmware in fastboot mode on MI FLASH TOOL
selvarajrajkanna said:
Try these 2 things
1) charge your phone for 2-3 hours. if didnt switch on try this 2
2) Connect your data cable with pc. In mobile Press volume up + volume down and plug in the other end of usb cable to your mobile. you need to hold the keys. this will boot your phone into fastboot.
If boot steps didnt work then it might be a hardware problem or hard brick.
Click to expand...
Click to collapse
I need help on urgent basis
I'm using Mi A1 rooted with custom kernel, My phone automatically received august update and it's installed automatically then i try to go in download mode to flash my phone with stock rom but i didn't press volume button properly and it's get restart and automatically start installing august update and i by mistake press power button and now my phone is not turning on even not responding
when i try to connect my phone with pc i can hear the connect sound but it's not going in fast boot
Shivam.S said:
I need help on urgent basis
I'm using Mi A1 rooted with custom kernel, My phone automatically received august update and it's installed automatically then i try to go in download mode to flash my phone with stock rom but i didn't press volume button properly and it's get restart and automatically start installing august update and i by mistake press power button and now my phone is not turning on even not responding
when i try to connect my phone with pc i can hear the connect sound but it's not going in fast boot
Click to expand...
Click to collapse
You switched off the phone in middle of installing ota, best bet is take it to the take it to the service center and tell them phone not switching back on after installing August ota update.
Or if not in warranty then try to install stock rom using qfil.
Unfortunately you have bricked your Mi A1
Shivam.S said:
I need help on urgent basis
I'm using Mi A1 rooted with custom kernel, My phone automatically received august update and it's installed automatically then i try to go in download mode to flash my phone with stock rom but i didn't press volume button properly and it's get restart and automatically start installing august update and i by mistake press power button and now my phone is not turning on even not responding
when i try to connect my phone with pc i can hear the connect sound but it's not going in fast boot
Click to expand...
Click to collapse
You have bricked your Mi A1, when you turned it off while installing/flashing the August update. Basically you should never turn a smartphone off, or disconnect the USB cable (if it is connected), while flashing its ROM.
There are various methods to unbrick it, I suggest you try this one since it's apparently not going into fast boot:
[Experimental]Recover Hard Bricked Xiaomi A1 Using SD Card
I got a replacement device from OP and I was unlocking the bootloader and rooting it. The guide i used had the incorrect patched boot image and everything went bad quick.
I can't go anywhere except fastboot now, can't boot to OS, no OS installed.
TWRP WAS booting from fastboot, I pushed the rom from there and flashed it...said no OS installed after, I installed it on both slots.
I can't get into EDL mode, the volume keys work...I think, but the second I let go of them when it's plugged in it defaults back to fastboot immediately. I tried the bat file that people use, says it worked, phone stays in fastboot.
I even tried holding the volume keys the entire time but the MSM tool wouldn't read it enough to flash anything, although it did read it enough to register some data, but was stuck on "waiting for device".
I am in need of some major help. Now I can't even temp boot to twrp, getting an error failed authorization. I'm afraid I really messed things up.
I have 5 days to send my old device back. Please help!
May be a longshot, but does the stock recovery work? Maybe try sideloading the full OTA zip from there?
Sent from my IN2025 using Tapatalk
For EDL mode, you need to hold the buttons then plug it in while continuing to hold the buttons. It won't work if the phone is already plugged into a usb port and then you try and get into EDL.
Really hard to brick a OnePlus device in my experience.
FernBch said:
May be a longshot, but does the stock recovery work? Maybe try sideloading the full OTA zip from there?
Click to expand...
Click to collapse
Recovery doesn't work. I was able to get to one of the steps to approve going into fastboot, advanced, reboot to fastboot, but not anymore.
Mike02z said:
For EDL mode, you need to hold the buttons then plug it in while continuing to hold the buttons. It won't work if the phone is already plugged into a usb port and then you try and get into EDL.
Really hard to brick a OnePlus device in my experience.
Click to expand...
Click to collapse
I was doing just that. It seemed to work initially but after I plugged it in and released the buttons it went back to fastboot and disconnected from MSM.
Make sure MSM is ready keep vol up/down pressed, connect cable and immediately press Start in the tool. Have done it like this 3-4 times with my Pro
Please read this https://forum.xda-developers.com/showpost.php?p=82508527&postcount=67
and this https://forum.xda-developers.com/showpost.php?p=82658631&postcount=85
both work for me.
lazyd2 said:
Make sure MSM is ready keep vol up/down pressed, connect cable and immediately press Start in the tool. Have done it like this 3-4 times with my Pro
Click to expand...
Click to collapse
I ended up using the fastboot ROM flash all.bat from this thread: https://forum.xda-developers.com/oneplus-8-pro/how-to/rom-stock-fastboot-roms-oneplus-8-pro-t4083997
I am now booting into the OS and the stock recovery came back. So good news is the phone isn't bricked.
Glad you sort it out
lazyd2 said:
Make sure MSM is ready keep vol up/down pressed, connect cable and immediately press Start in the tool. Have done it like this 3-4 times with my Pro
Click to expand...
Click to collapse
lazyd2 said:
Make sure MSM is ready keep vol up/down pressed, connect cable and immediately press Start in the tool. Have done it like this 3-4 times with my Pro
Click to expand...
Click to collapse
It work, thanks
You're a life saver