Related
Basically neither adb reboot recovery nor ROM Manager/QuickBoot will boot me into recovery. The device just reboots as normal. So I'm unable to flash new CWM or Prime :\
The device has root (su is installed and showing prompts for superuser access).
Is there something I should do which I'm not or I am, in fact, booted into recovery and just don't realize it?
None of those work to get you into recovery.
You can look for Gnufabio's boot to recovery app or
Hold volume down plus power button, soon as you see two lines of words appear at the to left corner, press volume up within 5 seconds, that will take you into recovery.
Thank you. It worked.
do you know of a way to do this without root i can bairly get my transformer to boot normally let alone recovery...
AFAIK you don't need root to boot into recovery.
I'm still wondering why these forums provide misleading and clearly wrong directions of getting into recovery...
drksilenc said:
do you know of a way to do this without root i can bairly get my transformer to boot normally let alone recovery...
Click to expand...
Click to collapse
The above method will get you into stock recovery if you're not rooted.
... the reason i posted this is because this method DOES not work for me... those programs require root. i do not have root. i am trying to get root. i have been rooting rom loading since my htc touch way back the only reason i want to root is so i can get netflix cause asus didnt update that lib file...
drksilenc said:
... the reason i posted this is because this method DOES not work for me... those programs require root. i do not have root. i am trying to get root. i have been rooting rom loading since my htc touch way back the only reason i want to root is so i can get netflix cause asus didnt update that lib file...
Click to expand...
Click to collapse
The button combo method is the default way of getting into recovery stock or custom. To get root you have to follow one of the many way to root.
How are you rooting by getting into stock recovery?
what i am saying is the default button combo isnt working for me to get into recovery mode.
i cannot get the device into apx mode at all
i need a way to do this
the default button combo is not working.
drksilenc said:
what i am saying is the default button combo isnt working for me to get into recovery mode.
i cannot get the device into apx mode at all
i need a way to do this
the default button combo is not working.
Click to expand...
Click to collapse
The APX mode is different, the combo above is for recovery.
For APX you need to power off the tablet.
-Plug the tablet to pc with your usb cord.
-Hold volume up while powering on
-Your screen will stay off but you should hear a "Ding" on your PC (or what ever noise your PC make when USB device is plug in)
well... they really should post that... i guess i did have apx working properly
Hey guys,
I have a buddy who has a Nexus S (GSM on Tmo) on 4.0.4 and he has never rooted. I'm vary familiar with the process of rooting/installing ROMs as I have a Galaxy S (Captivate).
Here's the problem. He recently upgraded to 4.0.4 from 4.0.3. After about a few weeks of doing so, his power button just stopped working. I've been looking around and this has been reported to be possible a hardware issue. We've seen some reports that this has happened to a few other people after upgrading to 4.0.4.
Now, one of the possible/temporary fixes people have mentioned would be to clear the dalvik cache. Well, we cannot do this as the power button is broken.
Really, I'm just trying to find a way to unlock the bootloader and or root it without using a power button. There was a guide that was feasible when using 4.0.3 as their was a one-click root without using the power button. That doesn't seem to be the case for 4.0.4, at least what I've seen.
So, in short. Is there a way to root or unlock the bootloader without a power button? Or is it possible to remap the power button to the search button in 4.0.4 so you can use it in recovery? I know this may be a longshot as the software to remap is in the Android OS and wouldn't be running when in recovery.
I'm starting to run out of ideas... hoping someone might be able to chime in and get us going in the right direction.
Thank you.
When my power button gave out I downloaded FIX BROKEN POWER BUTTON and TURN OFF THE LIGHTS. Neither one remedied the issue (had to send it in to get main circuit board replaced), but by using the combination of both apps together, I was able to turn on and off my screen easily at least
Sent from my Nexus S using XDA
http://forum.xda-developers.com/showthread.php?t=1589251
That being said, I had a similar problem, and ended up having to send my phone to Samsung for a repair, so maybe it IS a hardware problem?
take a look at this,http://forum.xda-developers.com/showthread.php?t=1524858 you can find solutions to do lot of tasks that require the power button, including remaping the search key to be your power button.
TheUnlockr.com (appears to be not working right now) has a great guide specifically for the Nexus S. You can use fastboot/adb commands to reboot into fastboot mode, unlock the phone using fastboot, root, flash, etc.. Just search fastboot commands on google. All you have to do is install the android sdk, download the platform-tools, and install PDA-Net driver.
If you remove the battery, the phone will shut off. Once you replace the battery can you turn on the phone with the power button? That's how you'll find out if it's a hardware issue. Of course if it is, you won't be able to power it back up.
Poriotis said:
If you remove the battery, the phone will shut off. Once you replace the battery can you turn on the phone with the power button? That's how you'll find out if it's a hardware issue. Of course if it is, you won't be able to power it back up.
Click to expand...
Click to collapse
Lol! if i put the battery back it gets on automatically
mayankchopra said:
Lol! if i put the battery back it gets on automatically
Click to expand...
Click to collapse
I have the same problem...
Now what? When I load into bootloader it gets stuck so I cant reflash using the toolkit.
Same problem for me, around the internet seems that many people have this issue. I don't think this is a hardware bug because my phone sometimes open itself the menu without long press the button and if i select "turn off" the phone doesn't do it and the screen goes blocked so I have to remove the battery and once I replace it the phone goes on. I am rooted with stock rom and kernel, does anyone have this problem with a mod rom? strange that google doesn't say anything about that, there are too many people's with the same problem...
I am also having the same problem but my phone is already rooted. How can I unroot so I can send back to Samsung?
Unrooting is as easy as just downloading an app called ES file explorer, enabling root permissions in settings, and then deleting superuser under system/app/superuser.apk and also delete the su binaries under system/bin/su and also che k in xbin as well.
Sent from my Galaxy Nexus using xda app-developers app
So I have my TF101, updated to the ICS release when it came out, rooted of course.
Since then it was kind of unstable. When not using the device it would appear to power off, but pressing the power button for about 10 seconds would bring it back up.
I noticed the recovery was not available after the update, but paid it no mind for that time.
Then out of nowhere the device screen will not turn on. After long pressing the power button a click noise can be heard, it's supposed to be the camera. Since it wasn't responding, I though it was bricked.
Then connecting it to the PC will let me access all the files on the device, something very weird.
I have tried various combinations of things after a very long and tedious search, nothing seems to work.
Here are the symptoms:
-The device is turned on, but no backlight or sound.
-When long pressing the power button click sound is heard.
-When connected to the PC via usb the files on the device can be accessed.
-ADB is accessible and the device can be rebooted via it.
-After rebooting the device via the power button or ADB usb comes up almost immediately, I don't think this happens when booting normally.
So basically, is the device bricked? Why can I access files from it? How can I push a working recovery for the TF101? Is it possible to flash a ROM from ADB?
I know these are a lot of questions, but I tried, and failed. Haven't found a case like this online, and my ADB experience is limited to adb shell and reboot
Thanks in advance for the help!
Hi Cronoadvan,
looks like your screen is dead, if you check q&A you see that more people have the same thing lately.
Is your device SBK1? so, are you able to use nvflash?
Cronoadvan said:
So I have my TF101, updated to the ICS release when it came out, rooted of course.
Since then it was kind of unstable. When not using the device it would appear to power off, but pressing the power button for about 10 seconds would bring it back up.
I noticed the recovery was not available after the update, but paid it no mind for that time.
Then out of nowhere the device screen will not turn on. After long pressing the power button a click noise can be heard, it's supposed to be the camera. Since it wasn't responding, I though it was bricked.
Then connecting it to the PC will let me access all the files on the device, something very weird.
I have tried various combinations of things after a very long and tedious search, nothing seems to work.
Here are the symptoms:
-The device is turned on, but no backlight or sound.
-When long pressing the power button click sound is heard.
-When connected to the PC via usb the files on the device can be accessed.
-ADB is accessible and the device can be rebooted via it.
-After rebooting the device via the power button or ADB usb comes up almost immediately, I don't think this happens when booting normally.
So basically, is the device bricked? Why can I access files from it? How can I push a working recovery for the TF101? Is it possible to flash a ROM from ADB?
I know these are a lot of questions, but I tried, and failed. Haven't found a case like this online, and my ADB experience is limited to adb shell and reboot
Thanks in advance for the help!
Click to expand...
Click to collapse
Since no ASUS logo is displayed, it is likely a hardware problem. Maybe you can try to bring it into recovery mode by pressing power + vol down button.
nlheiz said:
Hi Cronoadvan,
looks like your screen is dead, if you check q&A you see that more people have the same thing lately.
Is your device SBK1? so, are you able to use nvflash?
Click to expand...
Click to collapse
I am not sure, how do I check that? nvflash, at least the version I'm trying to use, won't run on win764? It's rather confusing.
tingtan said:
Since no ASUS logo is displayed, it is likely a hardware problem. Maybe you can try to bring it into recovery mode by pressing power + vol down button.
Click to expand...
Click to collapse
The screen does not light up at all, and USB is accessible after around 4 secs of long pressing power and hearing the click noise(camera?) which is not normal since no device boots so fast. This tablet never did anyway, taking from 20 to 30 secs.
After USB is available I can adb shell from windows but that's pretty much it, I don't know what to do afterwards.
Cronoadvan said:
I am not sure, how do I check that? nvflash, at least the version I'm trying to use, won't run on win764? It's rather confusing.
Click to expand...
Click to collapse
Check your serial number. If its below B70 you got SBK1.
Goatshocker said:
Check your serial number. If its below B70 you got SBK1.
Click to expand...
Click to collapse
Yes it is, it's B50. Is that a bad thing?
Cronoadvan said:
Yes it is, it's B50. Is that a bad thing?
Click to expand...
Click to collapse
Hi Cronoadvan,
thats not bad, this means that you could use nvflash to put a new image on your TF if you want to to make sure that it is working. If you use this forum:
http://forum.xda-developers.com/showthread.php?t=1558170
then it wil be stock again, and if needed you can then send your TF back for repair.
If you look and search in development you will find some ways how to use nvflash. like this one
http://forum.xda-developers.com/showthread.php?p=22465766
Hope this helps.....
nlheiz said:
Hi Cronoadvan,
thats not bad, this means that you could use nvflash to put a new image on your TF if you want to to make sure that it is working. If you use this forum:
http://forum.xda-developers.com/showthread.php?t=1558170
then it wil be stock again, and if needed you can then send your TF back for repair.
If you look and search in development you will find some ways how to use nvflash. like this one
http://forum.xda-developers.com/showthread.php?p=22465766
Hope this helps.....
Click to expand...
Click to collapse
Thank you so much! That was my last resort and sadly was clueless on how to do that too!
Hopefully it's just some kind of weird software coma, but now even if it's a hardware problem there is still hope!
Thank you very much good Sir, may life repay you thrice as much
Your welcome......please read the apx and nvflash option really well. It is rather straightforward but you have to install the apx drivers correct and use power and volume + (together) to enter apx mode. Voor drivers maybe you can use this forum below:
http://forum.xda-developers.com/showthread.php?t=1185104
it had an option for installing apx drivers for win 7 64 bit.
Hope your screen will work again, and if not you can send it back without warrant loss...
good luck!!!!!
So today I bought the Insignia tablet from bestbuy(Ns-14T004) I rooted it successfully and I was curious about flashing a rom to the device, which led me to wonder about the bootloader status on this device. I found that shutting the device off then holding Power + Volume UP until the Insignia logo appears then release the power button but holding the Volume up button brings up a tiny menu in the left hand corner which you cycle through with the Volume DOWN button and select with the volume UP button, The menu is as follows-
Boot Normally
Fastboot Protocol
Recovery Kernal
Forced Recovery
Fastboot Protocol has these sub categories inside it,
Bootloader
Contiune
Reboot-bootloader
Reboot
Poweroff
I was just curious if anyone had this tablet and knows anything about porting roms or unlocking bootloaders has looked into this tablet. For the price of a 10.1 tablet with JB I cannot complain, (I work at Bestbuy so I get the employee discount) plus its just for school right now. I think this tablet could be more with a good quality rom placed on it, CM or AOKP are the two ive used mostly. Maybe it wouldn't be too hard to port a rom over to this device and if there was an easy stupid proof guide id try it out, anyways thanks for reading and replying.
For anyone that read this and wondered the same thing, the tablets bootloader is UNLOCKED already, I tried the OEM unlock command in adb and of returned already unlocked. As for download mode, I cannot seem to find a way to enter it, not even through adb commands
Sent from my SGH-I747 using xda app-developers app
Can you share how you root it.i cant even get the drivers for this tab
Sent from my SAMSUNG-SM-G900A
vda0323 said:
Can you share how you root it.i cant even get the drivers for this tab
Sent from my SAMSUNG-SM-G900A
Click to expand...
Click to collapse
Use Kingo Root. I had to install PDANet to get the drivers, but after that, it worked a charm.
thanitos said:
So today I bought the Insignia tablet from bestbuy(Ns-14T004) I rooted it successfully and I was curious about flashing a rom to the device, which led me to wonder about the bootloader status on this device. I found that shutting the device off then holding Power + Volume UP until the Insignia logo appears then release the power button but holding the Volume up button brings up a tiny menu in the left hand corner which you cycle through with the Volume DOWN button and select with the volume UP button, The menu is as follows-
Boot Normally
Fastboot Protocol
Recovery Kernal
Forced Recovery
Fastboot Protocol has these sub categories inside it,
Bootloader
Contiune
Reboot-bootloader
Reboot
Poweroff
I was just curious if anyone had this tablet and knows anything about porting roms or unlocking bootloaders has looked into this tablet. For the price of a 10.1 tablet with JB I cannot complain, (I work at Bestbuy so I get the employee discount) plus its just for school right now. I think this tablet could be more with a good quality rom placed on it, CM or AOKP are the two ive used mostly. Maybe it wouldn't be too hard to port a rom over to this device and if there was an easy stupid proof guide id try it out, anyways thanks for reading and replying.
Click to expand...
Click to collapse
What method did you use? I want to root my Insignia - Flex - 8" tablet NS-P16AT08
Hi Guys,
So the story is that I was updating my Xperia Z3 (details below) from TWRP 2.8.6 to 'twrp-3.0.2-0-yuga' using the instructions androidnewsbox.com/2016/02/08/how-to-install-and-update-to-twrp-3-0-0 and after flashing the new TWRP the phone can no longer enter recovery mode and I get no other booting/loading screens.
I had 100% battery when I started the process.
It does still do the little vibrate thing when I hold down the power button but nothing happens after that.
When I plug it into the PC the LED flashes red, then green then goes off.
Reading the instructions twrp.me/devices/sonyxperiaz.html I did use the 'install' function not the 'recovery' function. Is that likely to be the mistake I made? If so is there any way to recover?
Any and all help will be greatly appreciated.
Model: D6653
Previous TWRP: 2.8.6
Android version: 5.0.2
Software version: 23.1.A.0.726
Use flashtool to reflash a new system image (ftf). You're using stock so probably your kernel doesn't support FOTA-Kernel partition flashing.
Great to hear back from someone.
Unfortunately I don't think that I can just flash a new ftf using flashtool as I cant get into fastboot mode.
I have been working through the following online tutorial
engineerthink.com/blog/2015/11/how-to-unbrick-hard-bricked-android-phone/
I have installed the USB drivers on my PC from here
androidmtk.com/download-sony-xperia-usb-driver
And i can get the ftf file from here (mine is 1288-6090)
xpericheck.com/device/D6653
Unfortunately I am unable to put the phone into fastboot mode by holding down the power and down buttons. Nothing happens.
The tutorial above also tells me "If phone not going to Fastboot mode than connect it to PC by USB. Hold Volume Up and Power button until you get company logo or backlight."
This also does nothing and I get no backlight or company logo.
FYI if it helps about a year ago I rooted my phone using a tutorial very similar to this
oneandroid.gs/root-xperia-z3/
I will keep working on the problem and post any updates as they come up.
h3llcat said:
Great to hear back from someone.
Unfortunately I don't think that I can just flash a new ftf using flashtool as I cant get into fastboot mode.
I have been working through the following online tutorial
engineerthink.com/blog/2015/11/how-to-unbrick-hard-bricked-android-phone/
I have installed the USB drivers on my PC from here
androidmtk.com/download-sony-xperia-usb-driver
And i can get the ftf file from here (mine is 1288-6090)
xpericheck.com/device/D6653
Unfortunately I am unable to put the phone into fastboot mode by holding down the power and down buttons. Nothing happens.
The tutorial above also tells me "If phone not going to Fastboot mode than connect it to PC by USB. Hold Volume Up and Power button until you get company logo or backlight."
This also does nothing and I get no backlight or company logo.
FYI if it helps about a year ago I rooted my phone using a tutorial very similar to this
oneandroid.gs/root-xperia-z3/
I will keep working on the problem and post any updates as they come up.
Click to expand...
Click to collapse
First hard shut down your phone by using combo, after that, download the ftf for your phone (1288-6090 is the customization, what you need is an ftf that its compatible with your phone model, download flash tools, install the drivers that come with it, and using xperifirm (Included in flashtools) you download the firmware) After you have all settled up, proceed to flash your phone, select firmware and then it'll ask you to connect your phone in flash mode not fastboot mode, you can do that by pressing vol up + power (press them and while pressing them connect the usb to the pc). Then the flashing process will start. You can find many tutorials around here in xda. Do not use external tutorials, go find stuff here. It's way more reliable as many are made just for your phone.
Hi and thanks again.
This gives me plenty to learn about and go forward with thanks heaps.
I will give this process a go later today but I have a few questions if you dont mind.
hard shut down your phone by using combo
Click to expand...
Click to collapse
I am not familiar with any combo and without visual ques from the screen or LED I cant tell if it is off. I have a button that says 'off' near the sim card is that sufficient?
connect your phone in flash mode not fastboot mode, you can do that by pressing vol up + power
Click to expand...
Click to collapse
Do I need to continue to hold down the buttons during the flashing process?
You can find many tutorials around here in xda
Click to expand...
Click to collapse
I do feel a little out of my depth here and am a bit confused about what to even search for to find a tutorial on what you are suggesting. If you can point me to an example tutorial that would be fantastic.
h3llcat said:
I am not familiar with any combo and without visual ques from the screen or LED I cant tell if it is off. I have a button that says 'off' near the sim card is that sufficient?
Click to expand...
Click to collapse
Yes that one, If you press it enough (about 5-10 secs) the phone will shutdown and It wont try to restart. This is what you need first.
h3llcat said:
Do I need to continue to hold down the buttons during the flashing process?
Click to expand...
Click to collapse
No, only when connecting the phone to start flashing the system software, you will see a green light in the notification led that will then shut off and flashing process will start.
h3llcat said:
I do feel a little out of my depth here and am a bit confused about what to even search for to find a tutorial on what you are suggesting. If you can point me to an example tutorial that would be fantastic.
Click to expand...
Click to collapse
This is a great almost-up-to-date guide http://www.xperiablog.net/2015/03/1...peria-lollipop-using-xperifirm-and-flashtool/
XperiFirm is included in flashtools now so you don't have to download it, but to get your firmware you have to do the same steps but opening xperifirm from inside flashtool.
You can download flashtool here http://www.flashtool.net/downloads.php
Seems to be a success!
Thanks heaps for all your great assistance.
Did you get the Z3 D6653 going again?
Hi H3llcat,
Jumping through some hoops with the D6653 myself... did you get it to boot up? Not sure how far you went with it, if still an issue charge it back up and let's try a couple of things; I realize it'll just be sitting there all dumb and dark like, but do it anyway. So let us know.
h3llcat said:
Hi Guys,
So the story is that I was updating my Xperia Z3 (details below) from TWRP 2.8.6 to 'twrp-3.0.2-0-yuga' using the instructions androidnewsbox.com/2016/02/08/how-to-install-and-update-to-twrp-3-0-0 and after flashing the new TWRP the phone can no longer enter recovery mode and I get no other booting/loading screens.
I had 100% battery when I started the process.
It does still do the little vibrate thing when I hold down the power button but nothing happens after that.
When I plug it into the PC the LED flashes red, then green then goes off.
Reading the instructions twrp.me/devices/sonyxperiaz.html I did use the 'install' function not the 'recovery' function. Is that likely to be the mistake I made? If so is there any way to recover?
Any and all help will be greatly appreciated.
Model: D6653
Previous TWRP: 2.8.6
Android version: 5.0.2
Software version: 23.1.A.0.726
Click to expand...
Click to collapse
Not sure if this is worth mentioning but this thread is 2 years old.
Yes I did get everything working, xkeita was a great help and the guide he sent me was useful.
Have you got issues yourself?