I just got the google nexus s 4g phone and im trying to root it but i cant get into bootloader mode? Ive tried both volume up and power and volume down and power and it just boots to main screen. Is there something i have to do first to get into bootloader mode that i missed or something?
Nop, just press volume up, and while keeping it pressed hit power.
To add to that, make sure you keep them held down because even letting off slightly early just brings up the Google screen. At least in my case.
Not to mention the phone needs to previously be off
Since you're going to be unlocking it you're going to be using fastboot once you get there. Boot the phone up normally and make sure usb debugging is on if it isnt. adb reboot bootloader
Related
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.
Hello all,
Slight problem...i just rooted my phone (ATT) did all that good stuff...and then when and flashed cleanROM's rom....cleared all the cashe etc....and now it seems that all my phone does it show the HTC start up page and go black. if i hold the power button, the lights on the bottom flashes about 7-8 times and then goes to the HTC start up page again. can someone help me get my phone working again?
Fastboot install the boot.img included in the Rom.zip
Sent from my HTC One X using Tapatalk 2
or even better still, s-off then you won't need to worry about flashing boot.img ever again!
i can't get the phone into the bootloader or recovery. Is there another way i can get into that?
Azn_Noob said:
i can't get the phone into the bootloader or recovery. Is there another way i can get into that?
Click to expand...
Click to collapse
To get into bootloader hold vol- while holding the power button. Don't let go until it reboots. It will now be in bootloader
Sent from my HTC One X using xda premium
unforseenenemy said:
To get into bootloader hold vol- while holding the power button. Don't let go until it reboots. It will now be in bootloader
Click to expand...
Click to collapse
You need to let go of power, but keep holding vol down. If you don't let go of power, nothing will happen (except the phone shutting off).
The most surefire way (works in just about any situation) is to hold power and volume down. Don't let go of volume down until I say so later. The capacitive buttons will flash after about 5 seconds. Then the buttons will stop flashing, the screen will turn off (if it was on). After that, release the power button, but keep holding volume down until the white bootloader screen shows up.
If the screen turns on at all, the phone will always be able to go to bootloader. Failure to get into bootloader is almost always a matter of the user not performing the button sequence properly, rather than an issue with the phone.
First of all sorry for my english
I have bricked my inspire 4g eng s-off i was just trying to root my inspire 4g without unlocking bootloader noob i just know nothing about unlocking bootloader i used htc quick root software when the process start the software requested me an hboot image and unfortunatly i located to recovery image and phone turned off now when ever i try to turn it on it gives three vibrates vol down +pwr five vibrates please help m
volume up +voldown+pwr button five vibrates and a stable green led vol down +pwr three vibrates and red blinking led just pwr on button three vibrates red blinking led
If your bootloader wasn't unlocked, I don't see how you could have bricked it. Also, do you know if you had usb debug mode turned on? You couldn't have flashed an image with a locked bootloader and the scripts won't work either since the adb/fastboot utilities cannot talk to your phone if debug mode is off.
At any rate, pull out the battery for a few minutes, reseat the battery, connect the phone to your pc, hold down vol- and power and see if you can get to a bootloader screen. Even if it seems to boot but hangs at the green htc logo, you should still be able to issue adb commands and recover.
Once the phone boots, on your pc, open a command prompt and type the command "adb devices" without quotes to see if your phone is recognized. Let us know the status then.
turboyoshi said:
If your bootloader wasn't unlocked, I don't see how you could have bricked it. Also, do you know if you had usb debug mode turned on? You couldn't have flashed an image with a locked bootloader and the scripts won't work either since the adb/fastboot utilities cannot talk to your phone if debug mode is off.
At any rate, pull out the battery for a few minutes, reseat the battery, connect the phone to your pc, hold down vol- and power and see if you can get to a bootloader screen. Even if it seems to boot but hangs at the green htc logo, you should still be able to issue adb commands and recover.
Once the phone boots, on your pc, open a command prompt and type the command "adb devices" without quotes to see if your phone is recognized. Let us know the status then.
Click to expand...
Click to collapse
the bootloader was lock but eng s-off and there is is no adb no fastboot boot i have tried all methods putting battry out for 15 mints i have checked with another battery with no luck when ever i try to turn on my phone it give three vibrates and my pc recognize it as QUALCOMM DIAGNOSTIC 900e when i press vol down +pwr it gives three vibrates vol down +up+pwr five vibrates is there any way to flash the rom in qualcomm diagnostic mode and the usb debug was on last time kindly help me !!
Branded badmash said:
the bootloader was lock but eng s-off and there is is no adb no fastboot boot i have tried all methods putting battry out for 15 mints i have checked with another battery with no luck when ever i try to turn on my phone it give three vibrates and my pc recognize it as QUALCOMM DIAGNOSTIC 900e when i press vol down +pwr it gives three vibrates vol down +up+pwr five vibrates is there any way to flash the rom in qualcomm diagnostic mode and the usb debug was on last time kindly help me !!
Click to expand...
Click to collapse
Qualcomm mode is what happens when you hold volume down instead of up while booting. A common issue with the inspire is the volume rocker malfunctioning and becoming "stuck". Usually it is volume up that gets stuck. Either way you will have to probably repair the volume rocker by replacing it. With the age of the device though I don't think it's worth it to spend any money on repairs. It's almost 3 years old now. I know it seems concidental to happen at the same time your trying to unlock it but it can happen. If it is something that went wrong while you were trying to unlock it your pretty much in the same boat. If it only goes to Qualcomm mode there is nothing you can do.
Gizmoe said:
Qualcomm mode is what happens when you hold volume down instead of up while booting. A common issue with the inspire is the volume rocker malfunctioning and becoming "stuck". Usually it is volume up that gets stuck. Either way you will have to probably repair the volume rocker by replacing it. With the age of the device though I don't think it's worth it to spend any money on repairs. It's almost 3 years old now. I know it seems concidental to happen at the same time your trying to unlock it but it can happen. If it is something that went wrong while you were trying to unlock it your pretty much in the same boat. If it only goes to Qualcomm mode there is nothing you can do.
Click to expand...
Click to collapse
i have checked the volume rocker and replaceed it with no luck
Branded badmash said:
i have checked the volume rocker and replaceed it with no luck
Click to expand...
Click to collapse
Then something happened when you tried to unlock it. If you can't access the device via fastboot or adb then it is not fixable. Reflashing a boot img or hboot would be what you would want to do if you could gain access.
OK I'm stumped.
I was sick of the OTA updates bugging me so I set about flashing to 4.4.2 on my XT1034. All went along fine till I got to the part where I had to flash system with sparsechunk. It kept giving me a permissions error. I wasn't sure what to do so I decided to try rebooting, clearly that was not the answer. Now my phone shows the unlocked boot loader screen for a few seconds and goes to a black screen. I can tell the screen is on, it's just that the screen itself is showing all black. My computer recognizes that something in there and installs the drivers for the ADB interface and USB composite, but not the MTP device. All commands to adb or fastboot just says waiting for device.
Anyone have any idea?
Edit: Not sure if it makes a difference, but I was on stock 4.3, trying to go to 4.4.2 or in firmware terms...
from Blur_Version.14.14.16.falcon_umts.AWSRetail.en.US
to Blur_Version.172.44.4.falcon_umts.AWSRetail.en.US
If your phone even does not start in fastboot mode then i would say you are pretty much fu***d.
Fastboot Cable?
I just had a thought. I have a fastboot cable from my Droid Razr XT912. I wonder if that might force it into fastboot mode?
I'll have to wait till I get home to try it but I'll update it I make any progress.
Hold power button until phone turns off. Turn phone on while holding volume down.
tapman said:
I have a fastboot cable from my Droid Razr XT912.
Click to expand...
Click to collapse
You have a fastboot cable :fingers-crossed::laugh:
Thats really great!
No my friend, your USB cable will not help you to access fastboot mode.
The first way to access Fastboot is to press Volume Down + Power when the phone is switched off.
The second way to access Fastboot is to boot the phone into Android and then
Code:
adb reboot bootloader
But as you have no operating system on your phone there is only option one for you.
So your fastboot cable will not help you. Try several times to get in fastboot with option one.
lost101 said:
Hold power button until phone turns off. Turn phone on while holding volume down.
Click to expand...
Click to collapse
No luck. When I power it off it just power's itself back on a few seconds later whether I and holding the power button or not and regardless of if it's plugged in or not. I've tried the following combinations:
power off then hold volume down while it powers itself on
power off then power back on while holding volume down
hold power and volume down till it reboots
All have the same result, reboot, unlocked bootloader screen, blank, windows detects new hardware and tries to install drivers but fails on the MTP
So also if there is no cable connected it switches on itself?
Actually when it comes to the bootloader screen you missed already the fastboot entrance point.
Give it some more tries.
mokkami said:
So also if there is no cable connected it switches on itself?
Actually when it comes to the bootloader screen you missed already the fastboot entrance point.
Give it some more tries.
Click to expand...
Click to collapse
Correct. I'll keep trying :/
Edit: Sweet Jebus it worked! I'm back into fastboot
Thank you so very much!
Could be a coincidence but after taking off my case(otterbox defender) and trying again it worked. Maybe the membrane was causing me to press both volume buttons? Weird but I'll take it.
Glad to hear. Yeah i had also an Otterbox for my HHTC HD2 and i had also this problem.
Now you can go on to restore your Moto G
mokkami said:
Glad to hear. Yeah i had also an Otterbox for my HHTC HD2 and i had also this problem.
Now you can go on to restore your Moto G
Click to expand...
Click to collapse
Yup back up and running now, no idea why I was getting those permission errors. *shrug*
Thanks again
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