Related
Please help if you can, would really appreciate, dont know how to unbick my totally F$$$$### Nexus S Phone.
Even in recovery/fastboot mode on my Nexus S (Vol up+power), I cannot get my system to recognize the device....in fact, even in Windows, I am not able to get the system to recognize my device in Recovery mode/Fastboot mode....the only way it will recognize the device is if it is turned on the normal way, and hangs on the "Google unlocked icon" screen.
Some background info:
My power button recently stopped working...I thought it had to do with the fact that I updated NexusTools (was running a CyberGR rom...cant remember the name...had V4 Ultimate in it (downloaded from Rom Manager)).
So what I did was download/install (from the same developer) their hybrid ics rom....that did not brick it...but it also did not fix the power button...so after not liking the new rom, and the fact that it didnt fix my power button, I reflashed to the original rom I had installed (wiped everything, including doing a factory reset), and it just hung on "Google unlocked icon"
Now my phone does the following:
- First of all, the only way to power the device up is to plug it in (it automatically turns on and tries to boot without me pressing the non-functional power button)
- If I let it try to boot, it infinity hangs on the Google unlocked icon screen
- If I boot into recovery (by holding vol up button and plugging the phone into a power source), it hangs on the recovery screen...meaning the power button, as well as the volume buttons, as well as any buttons are non responsive.
- If I boot into recovery, the device doesnt even register on my system....
What am I doing wrong? What can I do to try and fix this?
I would truly appreciate if anyone reading this has some insights for me.
THANKS!!
Knightsage said:
Please help if you can, would really appreciate, dont know how to unbick my totally F$$$$### Nexus S Phone.
Even in recovery/fastboot mode on my Nexus S (Vol up+power), I cannot get my system to recognize the device....in fact, even in Windows, I am not able to get the system to recognize my device in Recovery mode/Fastboot mode....the only way it will recognize the device is if it is turned on the normal way, and hangs on the "Google unlocked icon" screen.
Some background info:
My power button recently stopped working...I thought it had to do with the fact that I updated NexusTools (was running a CyberGR rom...cant remember the name...had V4 Ultimate in it (downloaded from Rom Manager)).
So what I did was download/install (from the same developer) their hybrid ics rom....that did not brick it...but it also did not fix the power button...so after not liking the new rom, and the fact that it didnt fix my power button, I reflashed to the original rom I had installed (wiped everything, including doing a factory reset), and it just hung on "Google unlocked icon"
Now my phone does the following:
- First of all, the only way to power the device up is to plug it in (it automatically turns on and tries to boot without me pressing the non-functional power button)
- If I let it try to boot, it infinity hangs on the Google unlocked icon screen
- If I boot into recovery (by holding vol up button and plugging the phone into a power source), it hangs on the recovery screen...meaning the power button, as well as the volume buttons, as well as any buttons are non responsive.
- If I boot into recovery, the device doesnt even register on my system....
What am I doing wrong? What can I do to try and fix this?
I would truly appreciate if anyone reading this has some insights for me.
THANKS!!
Click to expand...
Click to collapse
yes, sounds like a dead power button(i have one myself).
try going back into your recovery, do a full data wipe(factory reset), then reflash the rom(and gapps). if still nothing, redownload the rom and try again. in your recovery, there is an usb option. use it to transfer your newly downloaded rom from your computer to phone.
Once I am in recovery mode it "freezes" though...as in not even the volume buttons work...they worked fine before, and even work to get into recovery mode...but once there they no longer work...nor does connecting the device in recovery mode to my laptop....so im kind of at a loss, as I cant even use Fastboot/adb to wipe/push anything on the Nexus S through my laptop
Knightsage said:
Once I am in recovery mode it "freezes" though...as in not even the volume buttons work...they worked fine before, and even work to get into recovery mode...but once there they no longer work...nor does connecting the device in recovery mode to my laptop....so im kind of at a loss, as I cant even use Fastboot/adb to wipe/push anything on the Nexus S through my laptop
Click to expand...
Click to collapse
im guessing that your using cwm recovery?
give your phone a few smacks on the back near the power button, your phone thinks its being pressed in.
yes, it definitely thinks it is being pressed in...thats for sure...and makes sense...ill try that haha!
Yes latest CWM Recovery...5.0.2 or something like that...just updated that before phone died...
Weird...so i "smacked" the phone a bit...when I do it in recovery mode, it reboots the phone into recovery....so it definitely thinks its being pressed down constantly...but I have found no way to make it "un-pressed"...only briefly by smacking it...
Knightsage said:
yes, it definitely thinks it is being pressed in...thats for sure...and makes sense...ill try that haha!
Yes latest CWM Recovery...5.0.2 or something like that...just updated that before phone died...
Click to expand...
Click to collapse
in twrp recovery, theres an option to not use the power button to select(thats what im using), is there a similar option in the newer cwm recovery? tr\y pressing the soft buttons). also, see if sticking a fingernail in between the power button helps, to pull out the button a bit.
After continuingto smack it...as well as "pulling" on the power button, I am not able to use volume buttons and power buttons within recovery...flashing a new rom now...will let you know if that fixes it...otherwise I will try unbickable in ubuntu again and see if that fixes it thanks for the pro-tip of smacking it, haha!
I have flashed the CWM from TF201 by accident. Now the tablet is stuck in that CWM mode. I can't connect to usb using adb mode. Power+volume down does not work anymore. Any way I can reflash the correct CWM?
THanks
If you can boot to OS - you can use fastboot to flash any recovery.. or flash TWRP from goomanager.
upd: sry..don't see about "stuck".
abe_cedar said:
I have flashed the CWM from TF201 by accident. Now the tablet is stuck in that CWM mode. I can't connect to usb using adb mode. Power+volume down does not work anymore. Any way I can reflash the correct CWM?
THanks
Click to expand...
Click to collapse
I have made the same mistake. Although I can get the device to fastboot USB mode. I have tried to use CWM with the restore I made before I put in Cyanogenmod 9, as well as putting on the Cyanogenmod experimental #2 for TF300. No error messages at all and it wipes data and cash without any problems.
But I get locked on the Asus boot screen and it does not continue ie I am stuck as well.
I have as well tried to use the TWRP 2.1.5. I get the Teamwin loggo screen, it wipes all the data and verifies all the filesystems and reboots. Still stuck.
Is the device bricked ?
upd:The TF300 can not be shutoff either. When you hold the power button the screen goes black, but after ~5 s the device is starting again and is still stuck on the Asus bootup screen.
if you reboot it holding vol down and power, can you get back into the boot menu, to reselect fastboot?
if holding the power button doesn't switch it off, what happens if you leave it to run out of batteries then do this?
then you can flash the correct recovery.img
cheedear said:
if you reboot it holding vol down and power, can you get back into the boot menu, to reselect fastboot?
if holding the power button doesn't switch it off, what happens if you leave it to run out of batteries then do this?
then you can flash the correct recovery.img
Click to expand...
Click to collapse
Yes, I can get access to the fastboot and I have already tried to flash with the recovery.img. I have as well let the battery run out and tried it once more with the same result.
Still stuck on the asus bootup screen.
power
Hare,
I have same problem.tab cannot power off. Just reboots into cwm.
I was thinking to drain bat. Thanks for sharing that info.
There are a lot of topics about people who broke their devices with TF201's recovery.
Afaik, no one recovered it. Send to Asus.
So the device is bricked then :'(.
Thanks for clearing it up.
Sent from my GT-I9100 using XDA
RMA..
Guillaume,
Thanks for clarification.
I have read that ASUS wants 700USD for replacing/reflashing the bootloader. That was for the tf201. Any way to nvflash it back to factory? I don't believe that they have to change the MB.
I have no warranty left, but I don't want to be gouged by them either.
Any thoughts, info?
Hi,
I've do the same mistake, but I can use adb.
Do youhave any news about our problem?
Thanks
Midyr
unable to power off
My issue is that I have the CWM for the tf201. I did the update from the CWM app in Android. Bad idea. So now the tab does not power off s.t. I can get into the power+vol down mode. Adb does not work since I cannot ( don't know how) to make it go into the usb debugging mode. I have tried several things none of which have worked. Still stuck.
I wanted some feedback for a RMA from ASUS, posted it here but sor far no answers.
Not sure if it would really work, but on my Evo, I don't have to completely power off the phone to do the recovery sequence. I can do it during a normal reboot. There is a point just before the device starts booting again where it is technically "off", and if I hold volume down (don't even have to hold power on my Evo; volume down seems to be the only necessary button) starting at this point, the phone will boot into the bootloader.
So, next time the device reboots, just start holding volume down (possibly power also, just in case) at the "off" point.
So, been running CM10 for a long time on tab. Decided to go back to stock, and downloaded the JB stock rom. Flashed via ODIN. Everything seemed to go OK, except that after the flash the screen went black for ages, and didn't reboot. So I hard powered it off. Probably what did it, but it wasn't going anywhere for about 15 minutes, so figured it was the next step.
Now, I get the battery charging icon. The system goes through the Galaxy Tab 2 7.0 white logo, the swirling then glowing Samsung logo, and then loops through that forever.
It wouldn't be such a problem if I could back into ODIN and do another flash, but I can't get into download mode (normally I do it via adb but that isn't working since there is no USB connection at all). Tried all combinations, power/up, power/down etc. It just boot loops as above. I'm pretty sure I bricked it, but just wanted some confirmation.
Been doing this on and off for a long time, and it's the first time I've ever got stuck like this.
Thanks in advance.
Plug USB charger, your device will boot into charge mode. From charge mode you can boot into recovery by keep holding VOLUME UP button and than press POWER button. Clear data and cache in recovery, reboot.
ketut.kumajaya said:
Plug USB charger, your device will boot into charge mode. From charge mode you can boot into recovery by keep holding VOLUME UP button and than press POWER button. Clear data and cache in recovery, reboot.
Click to expand...
Click to collapse
Thanks, but I tried all combinations of Power/Volume UP and Power/Volume DOWN, it just goes through a normal boot cycle until it starts looping.
I guess it's possible I'm not using the right timing. I'm assuming that you hold Volume UP or DOWN and then press and hold Power until the screen goes black, and then release? I've done it like that many times, and also continued to hold everything down as the logo appears, and then system goes back to the battery charging icon as if it powers off again. I sound like such a noob when I type stuff like that!
I saw ODIN successfully write system.img, boot.img, and recovery.img, so I'm thinking any CWM recovery I had on there is toast.
sl0ttedpig said:
Thanks, but I tried all combinations of Power/Volume UP and Power/Volume DOWN, it just goes through a normal boot cycle until it starts looping.
I guess it's possible I'm not using the right timing. I'm assuming that you hold Volume UP or DOWN and then press and hold Power until the screen goes black, and then release? I've done it like that many times, and also continued to hold everything down as the logo appears, and then system goes back to the battery charging icon as if it powers off again. I sound like such a noob when I type stuff like that!
I saw ODIN successfully write system.img, boot.img, and recovery.img, so I'm thinking any CWM recovery I had on there is toast.
Click to expand...
Click to collapse
You must pull usb cable before start.
You can try to re-flash.
tuxafgmur said:
You must pull usb cable before start.
You can try to re-flash.
Click to expand...
Click to collapse
Well, don't I feel like the idiot!
How did I not think to disconnect the USB before trying this? tuxafgmur, your first "Thanks" has been registered, I've got it from here!
P.S. Welcome to the forum!
it sounds strange. never heard of such a strange boot problem. anyway it could be that while transferring boot.img it became damaged due to some error. i know you probably tryed but you may try and connect it to linux or mac os x in order to check if you could retrive more data about the tab. for example the mac could find if it is totally corrupted. normally when i plug my samsung devices it ask me to add the samsung-modem also if they are turned off. meybe if it happens the same to you you can try to adb fastboot it also if i doubt myself about it working, but give it a shot
i hope my bad english is not preventing you to understand what i'm saying!
give us new feedback!
Ok Guys So I Shouldn't Have Done This But I Used Fastboot To Flash Recovery And I think I Did It Wrong. It Said "ok" And Finished And I Rebooted Phone It Resetted And Then Stuck On The Orange State Bootloader Message. I Do The Recovery Mode And Goes Black And Nothing Is Responsive For a While, Sometimes Longer Than Others. This Happens If I Start Phone Normal Or Try Fastboot Or Download.
Because Of My Mistake I Cannot Connect To Pc Software And Im Not Sure Of What I Can Do. I Feel Like Im Not Going To Like The Answer For This But I Got To Take The Blame For This.
Btw i Have A Samsung galaxy Note 20 Ultra Sm-N986u
I think your phone is hard bricked
so you can't get fastboot using volume up+power or via adb?
rescue from manufacturer site pos or just device not being recognised?
It isn't hard bricked it's just way of Samsung trying to make life of simple people more difficult, people who paid for Samsung phones lots of money.
To sort that screen issues what you can surely do is,
Simply press volup + voldown buttons at the same time, no matter if you're on that orange screen or whatever just press those those two buttons at the same time and keep pressing them while you connect your phone to pc. you will boot into download mode. Then flash stock firmware for your phone. After stock of flashed Reboot and start your phone, go to developer options see if oem unlock option is there if it is then oem unlock it if it is not then go back to settings manually change date to year ago, then go to updates disable auto update, connect to WiFi, and press on update several times untill window shows up saying no updates, then go to developer options you should see oem unlock, unlock it.
Then boot into download mode and make sure you have working copy of recovery.
And make sure you follow instructions of whoever recovery you installed on how to boot into recovery. I have S20 plus and too had troubles with it, and the only working recovery for my phone is twrp customised. To boot into it after flashing recovery from odin auto reboot disabled I pressed voldown and power, USB cable connected, then after screen goes off I changed from voldown to volup while kept pressing power button and cable connected. Orange screen with warning showed up for 5 sec I kept pressing and it bottled to twrp and then I was able to install custom rom beyond rom and while installing in aroma I was able ti choose option to remove orange screen.
That's it.
I ran into the same error. I mistakenly loaded twrp's recovery into userdata instead of ap section. The phone was stuck at the orange screen and nothing was happening whatever i pressed. I waited till the battery to dry out and with 0% battery, i directly connected to pc and was able to get into download mode. Then i flashed stock and everything is now back to normal.
Carl Johnson (Cj) said:
I think your phone is hard bricked
Click to expand...
Click to collapse
Absolutely not
Hi, I don't know what is happening, but I've been having issues with my phone. I was trying to enter recovery and pressed the button combination for fastboot instead. After that, I tried to get out of fastboot, but it kept going back to fastboot. I noticed holding up for a couple of seconds would boot me into my OS. When I try to enter recovery, the screen goes black and it restarts the phone. It will just keep going in a loop if I hold the buttons. My phone was rooted with magisk and I uninstalled to see if that would help, but it didn't.
I installed an update(I use lineage OS) out of curiosity to see if it would boot to recovery. It booted to fastboot, but after restarting and holding the recovery button combo it booted to twrp and installed the update, then restarted. Now my stupid mistake made my phone unusable. Everything is the same, except Lineage is stuck at the boot screen now. Sometimes it restarts to fastboot, but other times it stays there for possibly infinity.
I don't know what to do. All help is appreciated?
TL;DR Fixed, I think my volume down button was stuck.
Nevermind, I flashed with miflash and still had the problem, then for some reason it worked, but only once. I removed my phone from the case and found that it was booting to os. It is still kind of hard to enter the recovery. I think hitting volume up was cancelling the volume down which was stuck, or something. Now I'm pissed cause I wasted so much time on nothing