Database Users

Can't select options in Clockwork Recovery 1.7.3

Oops.
So I got 'Rom Manager' from the app store thinking it would simplify my rom flashing tendencies. I loaded the Clockwork Recovery on last night, did a backup and tried to flash Damage1.0 over 0.99.
Now DC1 is freezing on the nexus startup screen and when I boot into Clockwork, I can't select any of the options; I have to remove the battery.
Can anyone help?

There is alwaready a thread about this

Um... where? Sorry if this is a repost.

JMadr said:
Um... where? Sorry if this is a repost.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=648762

Got it.
But can anyone suggest anything for my specific case? I'm entirely dead in the water here.

JMadr said:
Got it.
But can anyone suggest anything for my specific case? I'm entirely dead in the water here.
Click to expand...
Click to collapse
when you're in recovery you still have access to the flash_image functionality. So all you really have to do is get the old recovery img and put it on the root of your sd card. then just do
Code:
flash_image recovery /sdcard/recovery-whatever-heroc.img
and that should put an old recovery on for you, then you will be able to flash other roms as much as you want. have fun

I appreciate the reply. I'm not quite sure what you mean though. I can't mount my phone because I can't boot - so I can't put any files I don't have onto the memory card. Also, how would I input that code if my computer can't see that I have my device connected?
Sorry, if my questions are annoying. This is the first time I've ever had a problem with any of this stuff. Help would be greatly appreciated... I really cant afford a new phone right now.

JMadr said:
I appreciate the reply. I'm not quite sure what you mean though. I can't mount my phone because I can't boot - so I can't put any files I don't have onto the memory card. Also, how would I input that code if my computer can't see that I have my device connected?
Sorry, if my questions are annoying. This is the first time I've ever had a problem with any of this stuff. Help would be greatly appreciated... I really cant afford a new phone right now.
Click to expand...
Click to collapse
adb wont even read it? if you do "adb devices"? ( in recovery mode )

you need to download the android sdk
http://developer.android.com/sdk/index.html
then you can run the command
adb shell
which will give you a command line on the phone.
If you don't have the old recovery on there then you can run something like
adb push fileOnYourComputer /sdcard/whateverName.img

if he flashed the clockwork recovery he has to have the android sdk for adb

venumx said:
if he flashed the clockwork recovery he has to have the android sdk for adb
Click to expand...
Click to collapse
It looks like you can flash it from the app
http://forum.xda-developers.com/showthread.php?t=639153
This is the problem with apps like that and automated processes for rooting. When the phone goes BOOM we need to go back to basics to explain things.

I downloaded the SKD, but I really have no idea what to do at this point. I'm trying to use terminal to execute commands, but nothing is coming back. What am I doing wrong?
Would anyone mind PMing me a walkthrough for pushing files/flashing updates via OSX? I would really appreciate anyone's help.

unzip it
open up a terminal
cd into wherever you unzipped it into
Code:
cd tools/
./adb devices
if you see your phone then you can do all the command we have been telling you
push the old recovery onto the phone
Code:
./adb push fileONComputer /sdcard/NAME.img
go into the phone
Code:
./adb shell
and run the flash
Code:
flash_image recovery /sdcard/NAME.img

centran said:
It looks like you can flash it from the app
http://forum.xda-developers.com/showthread.php?t=639153
This is the problem with apps like that and automated processes for rooting. When the phone goes BOOM we need to go back to basics to explain things.
Click to expand...
Click to collapse
yeah i agree automatic programs that do this for people hurt them more than they help them haha, the automatic ones should just be a convenience to those who know what they're doing !!

Problem solved! Another victory for y'all at XDA. Thanks a bunch to all that helped.

Cant flash another recovery image!!!

It used to work along time ago, this is my new refurb that i rooted a few days ago, im on the 1.5.2 recovery image and im trying to flash the new 1.6 but i dont what the crap im doing wrong. i keep getting error messages i used to be able to do this in 10 seconds. i already have the image on the root of my card can anyone help.
Plus those bastards sent me a refurb that has dead pixels that are white in the blk screen wtf sprint, thats pure whack customer service.
EDIT: problem solved, i was trying this whole time to flash another recovery inside recovery, i actually left the phone on and pushed the recovery lol no more ghanja.

see the # symbol when you enter teh shell? that means you have root already and su isn't necessary. Also try unplugging then plugging back in, the phone from the usb. The file not found error probably means that the sd card is mounted. do an ls from /sdcard to make sure

Also try "adb mount" over "mount -a".

DISABLE usb debugging.
i know, its the little things we overlook. i just did this last night and forgot to disable it.

i did and its still not working.........i dont understand, let me upload another pic. and i already tried adb mount and fastboot still no luck

i kept getting these errors what i did and found easiest with no errors is save the recovery in the sd card. download terminal emulator then in terminal emulator su then enter
then type flash_image recovery /sdcard/nameofimage.img
someone please make sure my prompts are right as i hadn't done it in awhile.

I am trying to do the exact same thing and getting the exact same errors. The file is definitely on the sd card, I am typing the name correct, and USB debugging is off.
Anyone have any other ideas or ways to update to the newest recovery image?

Maitiu said:
I am trying to do the exact same thing and getting the exact same errors. The file is definitely on the sd card, I am typing the name correct, and USB debugging is off.
Anyone have any other ideas or ways to update to the newest recovery image?
Click to expand...
Click to collapse
hahaha dude it used to work perfectly, i been trying and trying for the past couple of hours. (scratching head)

Demoyo23 said:
hahaha dude it used to work perfectly, i been trying and trying for the past couple of hours. (scratching head)
Click to expand...
Click to collapse
you try using the terminal emulator method directly on the phone? only way i can get to work and works everytime.

I'm working on that now, but I tried that a few days ago and got different errors, I'll post what the specific error was when I get there in a few minutes. For some reason Superuser Permissions is force closing right now.
Yeah even from the terminal emulator, I get a "not found" error.

I just updated today from RA1.5.2 to RA1.6.2. I used the Recovery Flasher to update to the newer version as that is what I had originally used to get 1.5.2 installed.
These were original instructions from theunlockr .com:
7. Save both the Recovery-RA-HEROC-v1.5.2.img and the FlashRec.apk to your computer, then copy them both to your SD card (do NOT put them inside any folders on the SD card, just put them on the SD card itself).
8. Unplug the phone from the computer once they are downloaded to the SD card.
8. Goto the Market and download Linda File Manager or any file manager program if you do not already have one.
9. Open the file manager and goto SDCard and then find the FlashRec apk file and click it. If asked tell it to use Package Installer to open it. It should automatically install the apk.
10. Open the FlashRec program and click on Backup Recovery Image and wait for it to finish.
11. Once done, click on the empty text box in the FlashRec program and type (again remember we have replaced the recovery image from the one in the video so type what is written here, NOT what is written in the video!):
/sdcard/recovery-RA-heroc-v1.5.2.img
Then click on the Flash Custom RecoveryImage button and wait for it to finish.

Just barely.

That's still not working flashrec won't back up it keeps saying failed. And it won't flash a custom img. This refurb is cursed I had no problem doing it all on my original.
-------------------------------------
Sent via the XDA Tapatalk App

Demoyo23 said:
It used to work along time ago, this is my new refurb that i rooted a few days ago, im on the 1.5.2 recovery image and im trying to flash the new 1.6 but i dont what the crap im doing wrong. i keep getting error messages i used to be able to do this in 10 seconds. i already have the image on the root of my card can anyone help.
Plus those bastards sent me a refurb that has dead pixels that are white in the blk screen wtf sprint, thats pure whack customer service..
Click to expand...
Click to collapse
Type 'adb devices' in... Whenever I see the '/' before the '#' it means that it isn't recognizing my phone.

Just do it through adb. I did mine through adb the 1st, 2nd and 3rd time. After looking at the dirwctiona, I think it might be easier and should work.
-------------------------------------
Sent via the XDA Tapatalk App

Make sure the phone is connected as charge only, once it is type
ls /sdcard
AND PASTE THE RESULTS HERE
It sounds like you don't have the sdcard mounted or if you do you may be typing the file wrong compared to what is on the sdcard.
Don't panic, this had nothing to do worth the phone being refurbished, it is only a simple file not found error that once you fun that command can easily be solved.

liquidtenmillion said:
Make sure the phone is connected as charge only, once it is type
ls /sdcard
AND PASTE THE RESULTS HERE
It sounds like you don't have the sdcard mounted or if you do you may be typing the file wrong compared to what is on the sdcard.
Don't panic, this had nothing to do worth the phone being refurbished, it is only a simple file not found error that once you fun that command can easily be solved.
Click to expand...
Click to collapse
it keeps telling me permission denied lol

Type in
"adb shell" then
"ls /sdcard"
Without the quotes exactly as I typed them one at a time and paste the results.

dirkydirk23 said:
i did and its still not working.........i dont understand, let me upload another pic. and i already tried adb mount and fastboot still no luck
Click to expand...
Click to collapse
did you try fastboot boot recovery [dir on your computer]

Do a search for adb shell recovery. It should tell you how to do it. You are going to have to mount the system before doing anything else...and also change the recovery image to something Like recovery.ing as it is easier to type and less likely to be mis-typed
-------------------------------------
Sent via the XDA Tapatalk App

[HOW TO][UPDATED GUIDE] Unlocking & Rooting your XOOM!

UPDATED XOOM FLASHING GUIDE 02/02/12​
I recently bought a US Xoom MZ604 and had trouble flashing it initially. I came to a realization that the newer models of Xoom reinstalls the Stock Recovery after you flash a custom Recovery (eg. CWM, Rogue Recovery etc). This is uber frustrating for newer Xoom owners, especially those who are new to the flashing community, simply because you don not know exactly what's going on.
Also, I could not find any proper, full and updated guide to flashing your Xoom. So i decided to take the initiative to do so.
WARNING: I DO NOT TAKE ANY RESPONSIBILITY IF YOUR XOOM TURNS INTO A USELESS BRICK. BY FOLLOWING THIS GUIDE, YOU WILL VOID YOUR XOOM WARRANTY WITH MOTOROLA. YOU HAVE BEEN WARNED TO EXERCISE CAUTION WHILE FOLLOWING THIS GUIDE. STRICTLY FOLLOW THIS GUIDE AND I ASSURE YOU, NOTHING WOULD GO WRONG.
In order to follow this guide, you need fundamental knowledge of ADB and Fastboot for Android. Search around the forum for this knowledge.
STEP 1: Obtaining Required Materials
a.) Download the latest version of Android SDK from HERE and install it into your the root of your C: drive.
b.) Download the latest version of Java SE from HERE and install.
c.) Download and Install the latest version of Motorola USB Drivers from HERE.
STEP 2: Unlocking your Bootloader
What is a Bootloader?
In literal terms, bootloader is code that is executed before any Operating System starts to run. The concept of bootloaders is universal to virtually all Operating systems that inculcates operating systems on your PC, laptop, smartphones, and other such devices. Bootloaders basically package the instructions to boot operating system kernel and most of them also have their own debugging or modification environment. As the bootloader kicks off before any piece of software on your device, it makes it extremely processor specific and every motherboard has it’s own bootloader. Source: http://www.addictivetips.com/mobile/what-is-bootloader-and-how-to-unlock-bootloader-on-android-phones-complete-guide/
Click to expand...
Click to collapse
1.) Make sure your Xoom is turned on. Connect it to your PC via USB.
2.) On your PC, open up File Explorer and Browse to:
C:\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
3.) In that directory, make sure nothing is selected, SHIFT+Right Click into empty space and select "Open command window here".
4.) Command Prompt will open up. Type the following command:
adb reboot bootloader
Click to expand...
Click to collapse
Your XOOM will reboot into the bootloader showing "Starting Fastboot Support Protocol".
6.) Type the following command into the Command Prompt to unlock your bootloader:
fastboot oem unlock
Click to expand...
Click to collapse
7.) Read the warning and follow the instructions on the Xoom Tablet itself from this point onwards. Use the Volume Down key to navigate to 'Accept' the agreement and press Volume Up to select.
8.) Once selected, your Xoom will now unlock and format itself, meaning, all data will be cleared and you will back to a factory rest.
9.) Reboot your Xoom with the following command:
fastboot reboot
Click to expand...
Click to collapse
10.) Exit Command Prompt.
STEP 3: Rooting your Xoom
1.) Download the latest version of "Universal Xoom Root" from this thread. Place the .ZIP file into the root of your SD card.
2. Download this version of "ClockworkMod Recovery - Modified for Motorola Xoom" and place it into this directory:
C:\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
This will your new Recovery. MAKE SURE THAT IT IS IN .IMG FORMAT.
2.) With your Xoom still connected to your PC, type the following commands into Command Prompt (open up using the same method as STEP 1) to install your new Recovery.
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Click to expand...
Click to collapse
3.) Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery. If you miss this window and somehow end up booting your Xoom normally, repeat from STEP 3, section 2 onwards again. DO NOT CLOSE THE COMMAND PROMPT WINDOW.
4.)To root your Xoom, please perform the following:
"install zip from sdcard" -> "Choose zip from sdcard", then select the Xoom-Universal-Root.zip file you downloaded.
Note: use the volume buttons to navigate and the power button to select
Click to expand...
Click to collapse
After the root flashes itself, DO NOT REBOOT YOUR XOOM!
5.) Now you have to rename the 2 notorious files, that reinstall your Stock Recovery over CWM, into a format that is unreadable by the bootloader. In the already opened Command Prompt, type the following commands:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
Click to expand...
Click to collapse
6.) Reboot with CWM. Let your Xoom boot normally.
To test whether the root and flashing of CWM has been successful, type the following into your command prompt:
adb reboot recovery
Click to expand...
Click to collapse
If you are able to access the new Recovery, CONGRATULATIONS, you have successfully UNLOCKED & ROOTED your Xoom.
I would like to thank the Xoom Android community for your valuable commitment to into Xoom Android Development. Without you guys, the Xoom wouldn't feel much powerful in terms of usage. Also, I'd like to extend my gratitude to okantomi for his help when I first started out.
Those those experienced users of Xoom, please kindly help the newbies like me answer their questions in this thread. Could I also request the mods to sticky this thread for reference.
NOTE: For users who would like to revert to the original recovery, type the following into ADB: (tip provided by wontoniii)
adb shell mv /system/recovery-from-boot.p.old /system/recovery-from-boot.p
adb shell mv /system/etc/install-recovery.sh.old /system/etc/install-recovery.sh
adb reboot
Click to expand...
Click to collapse
Reference Threads:
1.) [Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]
2.) [ROM][Nightly][ICS] Team Eos WiFi Nightlies (Wingray/MZ604)
3.) [Root] Universal Xoom Root - ANY XOOM ANY UPDATE

Just my opinion, I would not recommend to everybody the step3/point6 as you do it...
I would just do something like:
adb remount
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
Click to expand...
Click to collapse
This can be easily reverted with:
adb remount
adb shell mv /system/etc/install-recovery.sh.old /system/etc/install-recovery.sh
Click to expand...
Click to collapse
In case someone could want the old recovery back without flashing anything

wontoniii said:
Just my opinion, I would not recommend to everybody the step3/point6 as you do it...
I would just do something like:
This can be easily reverted with:
In case someone could want the old recovery back without flashing anything
Click to expand...
Click to collapse
I believe your method is better, at least there's still a recovery to revert to in case something goes wrong. I'll add it to the guide. Thanks for the suggestion!
Sent from my Xoom using Tapatalk

My tool can do it automatically, check on the signature LordAIOTool, and if you guys can please test and tell me the results
---------- Post added at 08:57 PM ---------- Previous post was at 08:39 PM ----------
wontoniii said:
Just my opinion, I would not recommend to everybody the step3/point6 as you do it...
I would just do something like:
This can be easily reverted with:
In case someone could want the old recovery back without flashing anything
Click to expand...
Click to collapse
I liked your idea too, will put on my tool (can I?)

XxLordxX said:
I liked your idea too, will put on my tool (can I?)
Click to expand...
Click to collapse
Sure, no prob

Thread moved to General.

This seams to be a good guide can anyone tell me if it works it is more detailed than the other guide ???? and why was it moved to general

This guide is great and easy and very updated i dont know why other people dont use it. One thing tho you should be more clear on how to reboot into recovery tell them to press volume up + power then let go then wait three seconds and after logo and press only the volume down

Having a problem with using your guide
Ok, I'm a noob. I am probably missing something simple. When I type "adb reboot bootloader" at the command prompt it says "Device not found." My Xoom is connected via USB (Same cable it came with). Xoom appears in my explorer window I can browse through the files; I even transferred files to the SD card. It is just not detected from the command prompt window when I start the unlocking procedure. Any assistance would be appreciated. Using Xoom 4G, Android 3.2.4; Windows 7

Make sure that adb debugging is checked. You can find this under Applications > Development settings.
Before you type, check if your device is listed
Code:
adb devices
This should list your device.
dstruble said:
Ok, I'm a noob. I am probably missing something simple. When I type "adb reboot bootloader" at the command prompt it says "Device not found." My Xoom is connected via USB (Same cable it came with). Xoom appears in my explorer window I can browse through the files; I even transferred files to the SD card. It is just not detected from the command prompt window when I start the unlocking procedure. Any assistance would be appreciated. Using Xoom 4G, Android 3.2.4; Windows 7
Click to expand...
Click to collapse

kewlguru said:
Make sure that adb debugging is checked. You can find this under Applications > Development settings.
Before you type, check if your device is listed
Code:
adb devices
This should list your device.
Click to expand...
Click to collapse
That did the trick I figured it was something simple like that. Thanks for the help.

Superb Guide!
Many thanks, I spent the best part of a day trying various methods but found this to be the most n00b friendly
1 point it may be worth adding is to use adb you must have java installed on your pc, without you get error "adb.exe is not a valid win32 application"

first time root/flash rom question
Hi all..to start with sorry if im asking in the wrong place. I have a stock Xoom with an unmodded ICS I also own the Bionic. Also I have never rooted or flashed anything so I am a super noob (soon to change though).
I wated to be able to have USB host functionality and be able to have SD card read/write assess so last week I started searching Google which led me to this wonderful sight of great help. There might be too much help because after tons of reading there is more than one way to do what I want. Can someone please point me in the best way to root and which rom I should use that will give me the least about of trouble.
Thanks in advance

Don_Don said:
Hi all..to start with sorry if im asking in the wrong place. I have a stock Xoom with an unmodded ICS I also own the Bionic. Also I have never rooted or flashed anything so I am a super noob (soon to change though).
I wated to be able to have USB host functionality and be able to have SD card read/write assess so last week I started searching Google which led me to this wonderful sight of great help. There might be too much help because after tons of reading there is more than one way to do what I want. Can someone please point me in the best way to root and which rom I should use that will give me the least about of trouble.
Thanks in advance
Click to expand...
Click to collapse
Ihave similar story m8. I spent the majority of yesterday reading and learning how to root. This is by far the easiest guide to follow to ulock and root your xoom.

I just want to correct a small error here.
In Step 6 of Step 3, you say you want to check and make sure that the new bootloader is on there correctly.
I think you mean to say check and make sure the new "Recovery" is on there and the adb command would be "adb reboot recovery".
Am I wrong? If so, please disregard.

At which point do I back up data already on Xoom? Will there be any data loss?

Don_Don said:
At which point do I back up data already on Xoom? Will there be any data loss?
Click to expand...
Click to collapse
You have to backup your data before unlocking the bootloader, which is the VERY FIRST step.

gbenj said:
I just want to correct a small error here.
In Step 6 of Step 3, you say you want to check and make sure that the new bootloader is on there correctly.
I think you mean to say check and make sure the new "Recovery" is on there and the adb command would be "adb reboot recovery".
Am I wrong? If so, please disregard.
Click to expand...
Click to collapse
Yes you are right. Thanks for pointing that it, it could have confused some. I'll rectify that right away.

Ok so I have a question about this rooting process and I haven't seen the answer yet. My question is will this process work weather your xoom is running ICS or HC?

TADitto said:
Ok so I have a question about this rooting process and I haven't seen the answer yet. My question is will this process work weather your xoom is running ICS or HC?
Click to expand...
Click to collapse
Yes, this process will work regardless of your OS.

[HOWTO] Remove/disable boot up startup sound from HTC One

Hi all,
Couldn't find this info for this handset specifically, so thanks to Jayshah's howto for the HTC Desire in this post (H/T to him!) I found the equivalent location in the HTC One filesystem for the startup sound audio file.
So then, if, like me, you strongly dislike the HTC "Quietly brilliant" boot sound, here's two different methods to disable it entirely. You could also extend these to replace the sound with one of your own.
1. Alter the xml file that references the sound file
Pre-requisites:
Handset is rooted
Root-enabled file manager app installed (e.g. Total Commander)
Howto steps:
Detailed in this post later in the thread.
2. Remove/hide the startup sound file
Pre-requisites:
Handset is rooted and has a custom recovery partition (e.g. TWRP or CWM)
ADB install and working on desktop computer
Howto steps:
1. Put your phone into recovery
2. Open adb shell
3. Mount /system
4. Change directory to /system/customize/resource
5. Rename or delete HTC_Sense5_Boot.mp3
Code:
mount /system
cd /system/customize/resource
mv HTC_Sense5_Boot.mp3 HTC_Sense5_Boot_mp3.disabled
As noted by Jayshah, you could install Silent Boot from the Play store, but why add something else eating processor cycles when this solution is guaranteed and requires no additional code?

Thanks for this, worked a charm and didn't need to S-OFF!

Helpful! thank you very much bro.
Helpful! thank you very much bro.
dr_diem said:
Hi all,
Couldn't find this info for this handset specifically, so thanks to Jayshah's howto for the HTC Desire in this post (H/T to him!) I found the equivalent location in the HTC One filesystem for the startup sound audio file.
So then, if, like me, you strongly dislike the HTC "Quietly brilliant" boot sound, here's how to disable it entirely:
Pre-requisites:
Handset is rooted
Put your phone into recovery
Get a working adb shell
1. Mount /system
2. change directory to /system/customize/resource
3. rename or delete HTC_Sense5_Boot.mp3
Code:
mount /system
cd /system/customize/resource
mv HTC_Sense5_Boot.mp3 HTC_Sense5_Boot_mp3.disabled
As noted by Jayshah, you could install Silent Boot from the Play store, but why add something else eating processor cycles when this solution is guaranteed and requires no additional code?
Click to expand...
Click to collapse

Brilliant thank you. Will do this soon.

dr_diem said:
Hi all,
Couldn't find this info for this handset specifically, so thanks to Jayshah's howto for the HTC Desire in this post (H/T to him!) I found the equivalent location in the HTC One filesystem for the startup sound audio file.
So then, if, like me, you strongly dislike the HTC "Quietly brilliant" boot sound, here's how to disable it entirely:
Pre-requisites:
Handset is rooted
Put your phone into recovery
Get a working adb shell
1. Mount /system
2. change directory to /system/customize/resource
3. rename or delete HTC_Sense5_Boot.mp3
Code:
mount /system
cd /system/customize/resource
mv HTC_Sense5_Boot.mp3 HTC_Sense5_Boot_mp3.disabled
As noted by Jayshah, you could install Silent Boot from the Play store, but why add something else eating processor cycles when this solution is guaranteed and requires no additional code?
Click to expand...
Click to collapse
"Get a working adb shell" meaning what? Having a working fastboot? could you please explain?

M_Shaaban said:
"Get a working adb shell" meaning what? Having a working fastboot? could you please explain?
Click to expand...
Click to collapse
Do some searching here on the forums - adb stands for Android Desktop Bridge and is freely downloadable as part of the Android SDK. It enables you to access your Android device in various ways from your desktop computer. adb shell is a way to open an interactive shell (a 'command prompt') on the Android device. There are howtos on these forums (and indeed all over the 'net) that'll explain how to get ADB set up for your desktop OS.
Ian

dr_diem said:
Do some searching here on the forums - adb stands for Android Desktop Bridge and is freely downloadable as part of the Android SDK. It enables you to access your Android device in various ways from your desktop computer. adb shell is a way to open an interactive shell (a 'command prompt') on the Android device. There are howtos on these forums (and indeed all over the 'net) that'll explain how to get ADB set up for your desktop OS.
Ian
Click to expand...
Click to collapse
I did do that and I could reboot to recovery by entering command "adb reboot recovery" but then when I enter adb shell, it says device not found. What should I do? Could there be a quick video tutorial on how to do so?

M_Shaaban said:
I did do that and I could reboot to recovery by entering command "adb reboot recovery" but then when I enter adb shell, it says device not found. What should I do? Could there be a quick video tutorial on how to do so?
Click to expand...
Click to collapse
Oh okay you're probably almost there. I couldn't say exactly what's causing that message (I see the same myself from time to time by rebooting the phone usually solves the problem). Try booting the phone normally and seeing whether adb shell works when the phone is in it's normal interactive usable state. If that works then you could Google on 'adb shell not working in recovery mode' or somesuch, but you need to confirm that it works at all first of all.

dr_diem said:
Oh okay you're probably almost there. I couldn't say exactly what's causing that message (I see the same myself from time to time by rebooting the phone usually solves the problem). Try booting the phone normally and seeing whether adb shell works when the phone is in it's normal interactive usable state. If that works then you could Google on 'adb shell not working in recovery mode' or somesuch, but you need to confirm that it works at all first of all.
Click to expand...
Click to collapse
OK will try and do that. Thanks!
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added 16th December 2013 at 12:00 AM ---------- Previous post was 15th December 2013 at 11:35 PM ----------
dr_diem said:
Oh okay you're probably almost there. I couldn't say exactly what's causing that message (I see the same myself from time to time by rebooting the phone usually solves the problem). Try booting the phone normally and seeing whether adb shell works when the phone is in it's normal interactive usable state. If that works then you could Google on 'adb shell not working in recovery mode' or somesuch, but you need to confirm that it works at all first of all.
Click to expand...
Click to collapse
@dr_diem adb shell works fine with phone is on. Now time to find a solution to be working on recovery. My phone is rooted but I flashed stock recovery back after rooting. Is that OK? Or must it be done via custom recovery? Did it do it via stock or custom recovery? Also my Windows is 8.1 but I can access fastboot (commands and all) without a problem. On stock recovery >adb shell > device not found!

M_Shaaban said:
OK will try and do that. Thanks!
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added 16th December 2013 at 12:00 AM ---------- Previous post was 15th December 2013 at 11:35 PM ----------
@dr_diem adb shell works fine with phone is on. Now time to find a solution to be working on recovery. My phone is rooted but I flashed stock recovery back after rooting. Is that OK? Or must it be done via custom recovery? Did it do it via stock or custom recovery? Also my Windows is 8.1 but I can access fastboot (commands and all) without a problem. On stock recovery >adb shell > device not found!
Click to expand...
Click to collapse
I've just done some quick Googling and indeed yes a custom recovery is required to use adb whilst in recovery (according to this page that seems pretty sure of itself). Apologies that my howto didn't make that clear (that being because I didn't know about the requirement at the time!); I'll update it in that regard now.
Ian

dr_diem said:
I've just done some quick Googling and indeed yes a custom recovery is required to use adb whilst in recovery (according to this page that seems pretty sure of itself). Apologies that my howto didn't make that clear (that being because I didn't know about the requirement at the time!); I'll update it in that regard now.
Ian
Click to expand...
Click to collapse
I flashed CWM custom recovery and still adb device is not found! What could be the problem here?

M_Shaaban said:
I flashed CWM custom recovery and still adb device is not found! What could be the problem here?
Click to expand...
Click to collapse
I'm sorry but I am out of ideas on this I can only suggest you do some extended web and/or xda-developers searching to learn reasons for this error. I'm quite sure you'll find the answer given the size of our community; please do post back here when you find it.
Good luck!
Ian

M_Shaaban said:
I flashed CWM custom recovery and still adb device is not found! What could be the problem here?
Click to expand...
Click to collapse
Since this guide requires root anyway, I'm going to assume you already have Root access. If so, just install a root file manager (I like Root Browser), navigate to /system/customize/resource, and rename HTC_Sense5_Boot.mp3 to anything else. As long as it's not called HTC_Sense5_Boot.mp3, it won't play. Save and reboot. If you'd like to disable it altogether, navigate to /system/customize/resource/CID and open default.xml. Find:
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/att_bootup_one.zip" audio="/system/customize/resource/HTC_Sense5_Boot.mp3"/>
</BootConfiguration>
and remove the last part so it looks like this:
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/att_bootup_one.zip" />
</BootConfiguration>
Now save and reboot.

homeslice976 said:
Since this guide requires root anyway, I'm going to assume you already have Root access. If so, just install a root file manager (I like Root Browser), navigate to /system/customize/resource, and rename HTC_Sense5_Boot.mp3 to anything else. As long as it's not called HTC_Sense5_Boot.mp3, it won't play. Save and reboot. If you'd like to disable it altogether, navigate to /system/customize/resource/CID and open default.xml. Find:
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/att_bootup_one.zip" audio="/system/customize/resource/HTC_Sense5_Boot.mp3"/>
</BootConfiguration>
and remove the last part so it looks like this:
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/att_bootup_one.zip" />
</BootConfiguration>
Now save and reboot.
Click to expand...
Click to collapse
I used Root Browser. I edited the XML file and worked like a charm. But seems like it's taking a bit longer to boot, could editing boot configuration cause this?
Sent from my HTC One using XDA Premium 4 mobile app

M_Shaaban said:
I used Root Browser. I edited the XML file and worked like a charm. But seems like it's taking a bit longer to boot, could editing boot configuration cause this?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I certainly wouldn't think so. I've been disabling bootsounds this way since my Inspire

homeslice976 said:
I certainly wouldn't think so. I've been disabling bootsounds this way since my Inspire
Click to expand...
Click to collapse
Ah OK. Thanks a lot anyway
Sent from my HTC One using XDA Premium 4 mobile app

Hi, I tried to change this with root explorer. First i renamed the audio file. But it was restored after reboot. Then i changed in the xml file. same here restored? wtf? Have just got the latest sense 6 if that can have something to do with Thierry.
Edit: worked from recovery. But still, strange that root explorer didn't work?

You saved me. I was going crazy ... all tips I could find were for Android 2, or were turning sound off at shutdown => does not work after crash.

Thankss
Thnaks for the info

Do I need to be S-OFF to perform that?
Because when I restarted my phone after edition of the XML config file the changes we gone. Original file remains.

Hdx 8.9 3th gen install android

I rooted my tablet by using king root but I don't know what to do for android. Can someone tell me how to do that. I'm in the latest version and using windows computer

Practically said:
I rooted my tablet by using king root but I don't know what to do for android. Can someone tell me how to do that. I'm in the latest version and using windows computer
Click to expand...
Click to collapse
Wait - I responded to a PM and directed you to the appropriate thread. Please check your mail and proceed accordingly. The HDX forums have a wealth of information that should allow you to unlock your device and install a custom ROM with minimal effort.

Thanks for answer @Davey126 I red your mail but I still have some questions. I bought this tablet yesterday and this is my very first Android experience. I got how to root and unlock my device but I don't know the rest I mean is there any thread for very beginners ?

Practically said:
Thanks for answer @Davey126 I red your mail but I still have some questions. I bought this tablet yesterday and this is my very first Android experience. I got how to root and unlock my device but I don't know the rest I mean is there any thread for very beginners ?
Click to expand...
Click to collapse
If your device is currently unlocked you should be able to launch a custom recovery environment called TWRP. That's where most device maintenance is performed such as installing different versions of 'android' otherwise known as custom ROMs. Try this:
- power off device
- press and hold <power>+<vol-up> until Kindle Fire logo appears
- immediatlely release power button followed by volume 1-2 seconds later
- wait a few more seconds for next screen to appear
- what happens?
To exit recovery mode long press power until device shuts off. A short press will start the device normally.
Your response will determine next steps. If TWRP is present you're just a few steps away from installing a custom ROM. If stock Amazon recovery appears (just two options) then there is more work to be done.

Davey126 said:
If your device is currently unlocked you should be able to launch a custom recovery environment called TWRP. That's where most device maintenance is performed such as installing different versions of 'android' otherwise known as custom ROMs. Try this:
- power off device
- press and hold <power>+<vol-up> until Kindle Fire logo appears
- immediatlely release power button followed by volume 1-2 seconds later
- wait a few more seconds for next screen to appear
- what happens?
To exit recovery mode long press power until device shuts off. A short press will start the device normally.
Your response will determine next steps. If TWRP is present you're just a few steps away from installing a custom ROM. If stock Amazon recovery appears (just two options) then there is more work to be done.
Click to expand...
Click to collapse
I dont get this mean
Run:
Code:
adb shell
su
dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
how can i run this

Practically said:
I dont get this mean
Run:
Code:
adb shell
su
dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
how can i run this
Click to expand...
Click to collapse
I'm stuck at waiting for any device screen and there is fastboot text on my tablet

Practically said:
I dont get this mean
Run:
Code:
adb shell
su
dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
how can i run this
Click to expand...
Click to collapse
In Windows Dos prompt
Practically said:
I'm stuck at waiting for any device screen and there is fastboot text on my tablet
Click to expand...
Click to collapse
Your driver not installed properly. Pls just follow my thread tips.

@kkcheong sorry for bother you just to clarify my situation. I rooted my tablet and spent 8 hours yesterday to unlock it but couldn't. First of all code_generator.bat works fine it creates unlock.code file. however When i apply the unlock bat I got an error on my tablet screen which says unlock code is not correct. Can you help me about what to do by explaining to very very very noob person. Another issue is i cant copy the 2 files to root folder i tried es browser and root browser.

1. I think your ADB driver not properly install. Check your Hardware Device in your windows for ADB. If no such ADB in your Hardware means you have install ADB properly
2. You cannot copy to root? You maybe need to enable R/W with root explorer or es explorer root.
Practically said:
@kkcheong sorry for bother you just to clarify my situation. I rooted my tablet and spent 8 hours yesterday to unlock it but couldn't. First of all code_generator.bat works fine it creates unlock.code file. however When i apply the unlock bat I got an error on my tablet screen which says unlock code is not correct. Can you help me about what to do by explaining to very very very noob person. Another issue is i cant copy the 2 files to root folder i tried es browser and root browser.
Click to expand...
Click to collapse

Practically said:
@kkcheong sorry for bother you just to clarify my situation. I rooted my tablet and spent 8 hours yesterday to unlock it but couldn't. First of all code_generator.bat works fine it creates unlock.code file. however When i apply the unlock bat I got an error on my tablet screen which says unlock code is not correct. Can you help me about what to do by explaining to very very very noob person. Another issue is i cant copy the 2 files to root folder i tried es browser and root browser.
Click to expand...
Click to collapse
Suspect vulnerable bootloader (and cubed TWRP) have not been installed as outlined in step #2 of the unlock thread OP.

I can transfer the two file to root folder. Now what should I do. Sorry for long questions but I have limited opportunity for using a computer since I don't have. I use friend of mine's. I want to make sure I got every step correctly. In the post I can do generate code thing. I successfully generate unlock.code file but the whe I write adb shell in cmd I got error something like adb is not recognised. Do you have any idea of any script file that do these things automatically.
So
Step 1 Done
Two files was copied to root folder
But stuck at code thing. Btw I don't have any driver issue since I can enable fastboot and get Unock code is wrong error

Practically said:
I can transfer the two file to root folder. Now what should I do. Sorry for long questions but I have limited opportunity for using a computer since I don't have. I use friend of mine's. I want to make sure I got every step correctly. In the post I can do generate code thing. I successfully generate unlock.code file but the whe I write adb shell in cmd I got error something like adb is not recognised. Do you have any idea of any script file that do these things automatically.
So
Step 1 Done
Two files was copied to root folder
But stuck at code thing. Btw I don't have any driver issue since I can enable fastboot and get Unock code is wrong error
Click to expand...
Click to collapse
You need to access the device via adb to issue the commands listed in step #2 of the unlock post:
- boot into FireOS and unlock device
- enable USB debugging from the FireOS settings menu (Google if you need help finding it)
- tether device; you may get an authorization prompt on device (look for it)
- there may be a notification indicating device is connected in 'charge mode'; switch it to 'file transfer' also known as 'MTP'
- open a Windows command prompt and navigate to folder where adb/fastboot commands live
- issue commands referenced in above post
If the host you are using does have (or you can't find) adb/fastboot installing the following package may be beneficial: https://forum.xda-developers.com/showpost.php?p=42407269&postcount=1