Hello,
I'm trying to get the timeshift video mod working on my Z1 C6603, android version 4.2.2. The last step is to install the mod via recovery mode, which I can't boot to. I've tried the power + volume button method but it boots the phone into safe mode. Any ideas how I could get to recovery mode?
varsketis said:
Hello,
I'm trying to get the timeshift video mod working on my Z1 C6603, android version 4.2.2. The last step is to install the mod via recovery mode, which I can't boot to. I've tried the power + volume button method but it boots the phone into safe mode. Any ideas how I could get to recovery mode?
Click to expand...
Click to collapse
Yes, no problem!
If you're rooted (which I expect that you probably are), just open up (or download and install if you need to) Terminal Emulator and execute this command:
Code:
su
reboot recovery
Alternatively, if you don't have/don't want Terminal Emulator, if you connect your device to your PC via ADB, this command will get you into recovery mode, too:
Code:
adb shell
reboot recovery
Hope this helps! :good:
ИΘΘK¡€ said:
Yes, no problem!
If you're rooted (which I expect that you probably are), just open up (or download and install if you need to) Terminal Emulator and execute this command:
Code:
su
reboot recovery
Alternatively, if you don't have/don't want Terminal Emulator, if you connect your device to your PC via ADB, this command will get you into recovery mode, too:
Code:
adb shell
reboot recovery
Hope this helps! :good:
Click to expand...
Click to collapse
Thanks for your help.
Yes, the phone is rooted.
Terminal Emulator only rebooted the phone after a long pause and ADB tool says "operation not permitted". It's a work phone so it might have theft protection which blocks me from accessing recovery mode. Anything else I could try?
Try
adb reboot recovery
varsketis said:
Thanks for your help.
Yes, the phone is rooted.
Terminal Emulator only rebooted the phone after a long pause and ADB tool says "operation not permitted". It's a work phone so it might have theft protection which blocks me from accessing recovery mode. Anything else I could try?
Click to expand...
Click to collapse
Try:
Code:
adb shell
su
reboot recovery
root-expert said:
Try:
Code:
adb shell
su
reboot recovery
Click to expand...
Click to collapse
Hi,
Phone gets rebooted normally after doing this. Maybe it needs to get a custom recovery installed?
varsketis said:
Hi,
Phone gets rebooted normally after doing this. Maybe it needs to get a custom recovery installed?
Click to expand...
Click to collapse
When you type "su" does it changes the $ symbol to # ?
If you have # means that you have root access if not you don't have...
@varsketis, yes, a custom recovery should resolve your problem. I'd recommend either ClockworkMod or TWRP (TeamWin Recovery Project).
@root-expert, if varsketis didn't have root, when he executed these commands:
Code:
su
reboot recovery
-OR-
Code:
adb shell
su
reboot recovery
...he would have gotten an "Access denied" error. However, since he was able to get his device to reboot in some way or another using the shell, it means that he does have a root shell (#) usable.
Related
I've had my Sprint Hero rooted for the past few months and decided today to try out a custom ROM from Modaco. In November I rooted using the method described in these forums by theresthatguy.
The reoccurring problem I am having is that I can't enter recovery mode, after flashing the img, or just on a normal reboot using Home-End. The device just stalls out at the black HTC screen (for hours). I can backtrack to the Sprint 1.29.651.1 RUU, and from there I have no problems entering recovery mode. Of course, my phone isn't rooted either. So, if I follow the aforementioned procedure and root again, after I install the recovery image I can't get into recovery mode. I've also tried bypassing the img file used in the rooting procedure, and going directly to the Modaco img, but that doesn't work either and I get stuck at the black HTC screen.
I've seen many mentionings here that I am not allowing the img to fully flash to the device. I've tried waiting up to 3 hours, and I don't think this is the problem.
Any thoughts on how I can resolve this?
Which recovery image are you using? Is your hero a "with Google" hero?
when you do this command:
adb push recovery-RA-heroc-v1.5.2.img /sdcard
as a part of the rooting guide/process what response do you get back from your computer?
should say something to the effect of how much data was transferred and how fast it copied.
after that and you get to the part where you enter the following into the adb shell prompt:
flash_image recovery recovery-RA-heroc-v1.5.2.img
what response do you get then? This could take a minute or two, no longer to finish.
once those two things are done completely.... turn your phone completely off and then hold the home button while turning it on to get into recovery.
What happens when you run these commands:
Code:
adb remount
adb reboot recovery
?
Kcarpenter said:
Which recovery image are you using? Is your hero a "with Google" hero?
Click to expand...
Click to collapse
I'm using recovery-RA-heroc-v1.5.2.img, and yes, on a "with Google" Hero.
obelisk79 said:
when you do this command:
adb push recovery-RA-heroc-v1.5.2.img /sdcard
as a part of the rooting guide/process what response do you get back from your computer?
should say something to the effect of how much data was transferred and how fast it copied.
[/QUOTE
After pushing the image I get "1699 KB/s (3356672 bytes in 1.929s)"
obelisk79 said:
after that and you get to the part where you enter the following into the adb shell prompt:
flash_image recovery recovery-RA-heroc-v1.5.2.img
what response do you get then?
Click to expand...
Click to collapse
Following the flash_image command, my response, after ~2-3 seconds is:
flash_image recovery recovery-RA-heroc-v1.5.2.img
#
obelisk79 said:
once those two things are done completely.... turn your phone completely off and then hold the home button while turning it on to get into recovery.
Click to expand...
Click to collapse
This works, as it did previously. Th RA-heroc-v1.5.2 build and rooting is successful. After I boot, I power down, and then power on and into recovery mode. This works, but I don't think it was case before, even though there is no difference in the process between now and then.
If I continue, and use this procedure to apply the Modaco custom ROM (created via kitchen), it fails and I can't enter recovery mode
Procedure:
cmd
cd c:\android-sdk-windows\tools
adb devices
adb push c:\android-sdk-windows\tools\2.2-update-heroc-modacocustomcustomrom-signed\boot.img /sdcard
response: "1303 KB/s (2265088 bytes in 1.697s)"
adb shell reboot
after reboot..
adb shell
su
cd /sdcard/
flash_image recovery boot.img
response, after 2-3 seconds:
flash_image recovery boot.img
#
power off
note: USB cable still connected
power on via recovery mode (home-power buttons)
Does not enter recovery mode - stalls at black HTC screen.
After 2 minutes, reset battery and power on.
Reboots normally.
gu1dry said:
What happens when you run these commands:
Code:
adb remount
adb reboot recovery
?
Click to expand...
Click to collapse
When I try to remount, I get the following error message:
remount failed: Operation not permitted
At this time, I noticed HTC Sync was not able to connect. Wondering if there was some sort of relationship, I uninstalled the ADB Interface from the Device Manager, disconnected the USB cable, and rebooted. After reboot, I reinstalled the ADB Interface using the HTC Sync drivers and tried the remount again - failed.
Click to expand...
Click to collapse
you are flashing wrong.
go into recovery mode and from the menu select:
flash zip from sdcard....
select the modaco rom zip file and then it should flash....
you shouldn't be flashing any more .img files after you;ve rooted and isntaled recovery. let the recovery menu install zipped rom files for you.
the modaco custom rom signed zip fil e is a custom signed zipfile that allows you to flash the files held withiin via your recovery menu. so again, the only thing you should try to flash from adb using the flash_image command will be the recovery image which is pretty much a one time deal.
Seriously, no offense to any one here but... I can't believe you don't have a brick on your hands. I guess are phones really are very difficult to brick.
as long as you don't mess with the radio you should almost always be able to recover with the sprint RUU.
obelisk79 said:
you are flashing wrong.
go into recovery mode and from the menu select:
flash zip from sdcard....
select the modaco rom zip file and then it should flash....
you shouldn't be flashing any more .img files after you;ve rooted and isntaled recovery. let the recovery menu install zipped rom files for you.
Click to expand...
Click to collapse
Well hot piss! That definitely takes care of it! I certainly felt a little unsure of the img vs. zip file, as well as the use of the recovery parameter. Thank you much for clarifying this!
Kcarpenter said:
Seriously, no offense to any one here but... I can't believe you don't have a brick on your hands. I guess are phones really are very difficult to brick.
Click to expand...
Click to collapse
No offense taken - I'd done enough research to know now to mess with the radio, and thought I had a clear enough understanding of the procedure I needed. Regardless, I am glad I don't have a brick. Thanks for your help as well!
Kcarpenter said:
Seriously, no offense to any one here but... I can't believe you don't have a brick on your hands. I guess are phones really are very difficult to brick.
Click to expand...
Click to collapse
After reading many posts on this forum I feel like many people shouldn't be allowed to root their phones.
begginers make mistakes. gotta start somewhere
bddc said:
I'm using recovery-RA-heroc-v1.5.2.img, and yes, on a "with Google" Hero.
obelisk79 said:
when you do this command:
adb push recovery-RA-heroc-v1.5.2.img /sdcard
as a part of the rooting guide/process what response do you get back from your computer?
should say something to the effect of how much data was transferred and how fast it copied.
[/QUOTE
After pushing the image I get "1699 KB/s (3356672 bytes in 1.929s)"
Following the flash_image command, my response, after ~2-3 seconds is:
flash_image recovery recovery-RA-heroc-v1.5.2.img
#
This works, as it did previously. Th RA-heroc-v1.5.2 build and rooting is successful. After I boot, I power down, and then power on and into recovery mode. This works, but I don't think it was case before, even though there is no difference in the process between now and then.
If I continue, and use this procedure to apply the Modaco custom ROM (created via kitchen), it fails and I can't enter recovery mode
Procedure:
cmd
cd c:\android-sdk-windows\tools
adb devices
adb push c:\android-sdk-windows\tools\2.2-update-heroc-modacocustomcustomrom-signed\boot.img /sdcard
response: "1303 KB/s (2265088 bytes in 1.697s)"
adb shell reboot
after reboot..
adb shell
su
cd /sdcard/
flash_image recovery boot.img
response, after 2-3 seconds:
flash_image recovery boot.img
#
power off
note: USB cable still connected
power on via recovery mode (home-power buttons)
Does not enter recovery mode - stalls at black HTC screen.
After 2 minutes, reset battery and power on.
Reboots normally.
When I try to remount, I get the following error message:
remount failed: Operation not permitted
At this time, I noticed HTC Sync was not able to connect. Wondering if there was some sort of relationship, I uninstalled the ADB Interface from the Device Manager, disconnected the USB cable, and rebooted. After reboot, I reinstalled the ADB Interface using the HTC Sync drivers and tried the remount again - failed.
Click to expand...
Click to collapse
I think this may help. A friend of mine wanted to know how to flash custom ROMs to his phone. I wrote a document (complete with screenshots) that will take you step-by-step through the process.
Just click here: http://www.darktremor.com/howto.html
Hopefully, that will help you.
Click to expand...
Click to collapse
[Q] what to do if my volume up down button doesnt work how to get in recovery mode when i use adb i keep getting the message cant find device
godemzelve said:
[Q] what to do if my volume up down button doesnt work how to get in recovery mode when i use adb i keep getting the message cant find device
Click to expand...
Click to collapse
drivers?
debugging mode on?
Reboot into recovery using Terminal emulator.
how to reboot with terminal emulator
mon_iker said:
Reboot into recovery using Terminal emulator.
Click to expand...
Click to collapse
and how do i do this
Type
su
reboot recovery
In terminal emulator.
reboot menu app google play
mon_iker said:
Type
su
reboot recovery
In terminal emulator.
Click to expand...
Click to collapse
or use app from play store like this one reboot menu
I HAVE AN XPERIA E (C1504) . NOT ROOTED!!! BOOTLOADER NOT UNLOCKED!!! SO,.... THE PROBLEM IS THAT MY POWER BUTTON IS COMPLETELY BROKEN... (COMPLETELY) . ALTHOUGH MY PHONE IS ON RIGHT NOW... (AS I HAVE INSTALLED GRAVITY SCREEN APP).... BUT STILL I NEED TO RESTART MY PHONE IF IT GETS BUGGY IN THE FUTURE..... SO MY QUESTION IS HOW CAN I RESTART MY PHONE WITHOUT POWER BUTTON.... SOME APPS DO RESTART BUT THEY REQUIRE ROOT... IVE READ OF SOMETHING LIKE TURNING ON THE USB DEBUGGING OPTION... AND USING A REBOOT COMMAND.. SOMETHING LIKE THAT... PLEASE TELL ME COMPLETE PROCEDURE AS I AM A BIG NOOB... I M EVEN READY TO DONATE MONEY IF YOU HELP...
It's simply "adb reboot"
USB Debugging must be on
Or via Terminal Emulator: "reboot"
Well dont know how???
Lars124 said:
It's simply "adb reboot"
USB Debugging must be on
Or via Terminal Emulator: "reboot"
Click to expand...
Click to collapse
ACTUALLY PLEASE GUIDE ME WHAT TO DOWNLOAD AND INSTALL ON PC I am super noob at androiding:crying:..... AND DO I NEED A CUSTOM RECOVERY INSTALLED.. cause if i need then i dont have....
also how to use terminal emulator app method??? does it require root??
Get the ab tools from here and install them:
http://forum.xda-developers.com/showthread.php?t=2588979
Moreover you can search on the internet how to use adb tools.
Or download the Terminal Emulator apk from PlayStore, open it and enter "reboot"...
You don't need a custom recovery for that.
Lars124 said:
Get the ab tools from here and install them:
http://forum.xda-developers.com/showthread.php?t=2588979
Moreover you can search on the internet how to use adb tools.
Or download the Terminal Emulator apk from PlayStore, open it and enter "reboot"...
You don't need a custom recovery for that.
Click to expand...
Click to collapse
Actually if you want to reboot your phone via temrnal emulator your phone must be rooted. You can't run reboot command without su permissions.
On my Rooted Pixel 4a, I can use:
Fastboot - I flashed the latest update firmware as well as the rooted boot image
ADB Over WiFi - This is the most comnon way I connect for ADB
ADB While the Android OS is running
What I cannoit get woirking is ADB while in recovery mode,
If I go to recovery and connect via a high quality cable, I can see the device with
Code:
adb devices
C:\Java\x86\Android\android-sdk\platform-tools>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
091????????490 rescue
Click to expand...
Click to collapse
But none of the below works
Code:
>adb shell
error: closed
>adb connect 091XXXXXXXX490
cannot resolve host '091XXXXXXXX490' and port 5555: No such host is known. (11001)
>adv shell 091XXXXXXXX490
error: closed
What am I doing wrong? how can I connect in recovery?
Stock recovery?
WillisD said:
Stock recovery?
Click to expand...
Click to collapse
Yes.
DiamondJohn said:
What I cannoit get woirking is ADB while in recovery mode
Click to expand...
Click to collapse
I always thought that adb from recovery was a TWRP thing?
I did adb reboot recovery. My phone has an Android on its back, with "No command" on the screen.
Code:
$ adb devices
List of devices attached
xxx unauthorized
$ adb shell
adb: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
I got the same thing booting to recovery by holding Vol down at boot.
Booting to rescue (another option on the boot menu) got me the same thing on my screen and the same symptom you saw.
Code:
$ adb devices
List of devices attached
xxx rescue
$ adb shell
error: closed
Are you sure this is supposed to work with the stock recovery?
a1291762 said:
Are you sure this is supposed to work with the stock recovery?
Click to expand...
Click to collapse
Actually no, i guess it was an assumption, and the response to adb devices, gave me further hope.
However,, it does respnod to ADB. As is seen, it provides a list of devices. But, maybe one can't shell out while in stock recpvery. Which goves me an idea, maybe we can send commands from the command window in windows/linux. eg adb shell ls But it wouldn't make sense that it would allow root, which negates what I wanted to be able to do in the first place. ie recovery from a bootloop by selectively editing the data partition. in my previous case, it was to disable a single magisk module.
DiamondJohn said:
It wouldn't make sense that it would allow root, which negates what I wanted to be able to do in the first place. ie recovery from a bootloop by selectively editing the data partition. in my previous case, it was to disable a single magisk module.
Click to expand...
Click to collapse
Yeah, it certainly seems to be speaking adb...
I didn't think to try...but maybe adb push and pull work?
So my screen broke on my Note 10+, leaving only the top 15% with display and the bottom 60% with touch. I am trying to activate ADB on it so that I can backup my internal storage.
I booted into TWRP so that I could backup the rest of my system, which I did successfully, but because of the bad touch screen I am unable to hit the ADB side load button. I'd like to reboot into the system because I have ADB enabled there, however I also cannot click the reboot to system button, only reboot to download and shutdown. Since I can't see most of the screen, it is also not possible to access the terminal and work from there.
Anybody know how I can escape TWRP or otherwise activate ADB? Thanks for the help.
Once USB Debugging successfully got enabled on Android device, ADB is supported as soon as device successfully booted up.
To turn device into ADB Sideload mode you run commands
Code:
adb devices
adb reboot sideload
jwoegerbauer said:
Once USB Debugging successfully got enabled on Android device, ADB is supported as soon as device successfully booted up.
To turn device into ADB Sideload mode you run commands
Code:
adb devices
adb reboot sideload
Click to expand...
Click to collapse
Like I said, I'm unable to boot into the system right now because I am stuck in TWRP. ADB is not enabled in TWRP upon boot, you have to press the ADB side load button, which I am unable to do.
AllanRSS said:
Like I said, I'm unable to boot into the system right now because I am stuck in TWRP. ADB is not enabled in TWRP upon boot, you have to press the ADB side load button, which I am unable to do.
Click to expand...
Click to collapse
To boot into NORMAL mode ( i.e. ADB mode ) you enter on Windows command prompt these commands, one-by-one
Code:
adb devices
adb reboot
jwoegerbauer said:
To boot into NORMAL mode ( i.e. ADB mode ) you enter on Windows command prompt these commands, one-by-one
Code:
adb devices
adb reboot
Click to expand...
Click to collapse
I can not use ADB. It is for this very reason I am asking how to enable ADB. But thank you for these valuable ADB commands, I'll be sure to reboot my system once I enable ADB