Database Info

[Q] Rooting

Hi,
by following this guide
http://forum.xda-developers.com/showthread.php?t=1007782
I have completed everything.
After reading this guide here.
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
VI. Stop the Phone from Uninstalling the Custom Recovery Image
1. Once the phone is booted up, plug it in via USB cable and do NOT mount the storage.
2. Open a command prompt on the computer and type the following with hitting enter at the end of each line:
adb shell
cd etc
mount -o rw,remount /dev/block/mtdblock3 /system
mv install-recovery.sh install-recovery-no.sh
3. That will mount the system as writable and rename the file that overwrites the recovery image on reboot so that our custom recovery will stay.
4. Turn off the phone and turn it back on by holding down Volume Up and Power to get into fastboot mode.
5. Plug the phone in via USB cable while in fastboot mode and open the command prompt again and type the following with hitting enter at the end of each line:
cd\
cd c:\androidsdk\tools\
adb reboot bootloader
fastboot flash recovery recovery.img
5. Once it is done, you have just reflashed the recovery image and it will now stick. You are all done! You have an unlocked bootloader, a custom recovery image, and root access! If you want to now load a custom ROM head to the next procedure linked below.
Note : I haven't flash any custom ROM yet.
1.Is it necessary for me to Stop the Phone from Uninstalling the Custom Recovery Image if I want to flash a new Custom ROM?
1.a. After i reboot, My phone is still Rooted. How do i test it? I go into fastboot then select reboot. After that I use terminal Emulator and key in SU. which says I've granted superuser permission. Is this normal?
2. I like to understand more things about Android rooting and recovery.
what are the differences between the 2?

[ADB] Trying to backup - Birck? Hope not

Hi! I was trying to backup my Orange Monte Carlo following a Portuguese tutorial but I'm stuck in the middle and I've got no help! Hope you can provide some! These are the steps I followed (translated)
1 - Install ADB Made Easy;
2 - Open cmd;
3 - Activate cellphone debug mode;
4 - Connect via usb (without mass storage) and install drivers if request [it was requested and i installed];
5 - Run adb devices, it should show your device [it did];
6 - Run adb reboot bootloader, your cellphone will boot in Fastboot, wich is an Android image without menus [correct until here];
7 - Run fastboot devices, your device yor a question mark(?) should show up (advance to next step), else you miss drivers [step not completed];
cmd says 'fastboot' is not recognized as a command. Now my phone is stuck connected to the computer with an adriod pick and I have no clue on what to do next!

Don't know where you were going with this but to reboot your phone just pull the battery ..
Not bricked

shanman-2 said:
Don't know where you were going with this but to reboot your phone just pull the battery ..
Not bricked
Click to expand...
Click to collapse
Thank you! Do you have any idea why the last command doesn't work? I believe it has something to do with file location... I'm trying to backup my Monte Carlo. Next steps were to "fastboot boot recovery.img" and then backup.

It should be in the platform-tools directory of the android-sdk. Verify that it's there...if so cd to that directory and it should work

I already fixed it for myself, thanks! Now I can't seem to be able to install clockwork!
Doing <<fastboot boot "C:\Users\R&J\Downloads\recovery.img">> reboots the device but doesn't enter recovery.
Doing <<fastboot flash recovery "C:\Users\R&J\Downloads\recovery.img">> , <<fastboot reboot>> and <<adb wait-for-device reboot recovery>> results the phone entering android's default recovery (no acess to backup feature).
Any way to help? Thank you!

The first command <<fastboot flash recovery "C:\Users\R&J\Downloads\recovery.img">> is trying to write the recovery.img you downloaded to a recovery partition on your device. It may not be overwriting the original recovery.
try changing permissions by doing
adb shell
su
chmod 777 /recovery
then try to flash again

Lol it seems like I have been luck enough to solve my own problems, I have sucessfully installed ClockworkMod Recovery 4.0.1.4 unofficial MoDaCo Edition using a bat file . Now I can't seem to find a way to flash recovery back to stock. I though this was an option inside the modded recovery. Any tips? Thanks again!
EDIT: I have the stock recovery file . God... this tutorials I'm folowing aren't that noob friendly...

[Q] Transformer TF101 Recovery Loop

hey guys im having an issue with my asus tablet i rooted it i tried to install a different rom but after i restarted it on recovery i cant access my sd also when i press reboot goes back to the recovery menu but if i press vol down and power the cold boot works but everytime i turn it off and back on it boots to recovery menu does anybody knows how to fix this? any help is aprecciated.

Hi all,
I have the same problem with him, is there anyway to uninstall CWM Recovery?
Thanks in advance!

I found this fix its really easy just follow the steps
If you guys are able to cold boot into the OS, use Terminal Emulator to do what ADB would do. 1 - Cold boot into the OS and move files needed to internal sd storage. 2 - Reboot into your bad 5.5.0.4 cwm , install the new cwm through : install zip from sdcard , choose zip from ...
3 - Once installation is done , don't press "reboot system now" , do a cold boot directly (Vol down plus power button, wait till you get the option of cold boot or wipe data, choose cold boot)
4 - Once you've booted your rom ,
run terminal emulator. type : su (if superuser appp ask to you , allow). will give you a # type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
type : exit
type : reboot
NOTE: Someone say the above steps only work when they skipped the exit part so try it both way.

Typing 'exit' is not necessary as that only ends superuser status. You should be fine going straight to 'reboot.'

Need help preparing Xoom for official updates

Hey folks,
I´ve ran my MZ601 xoom on EOS builds over the last 1,5 years.
Obviously its unlocked and rooted. Currently its running CWM Recovery 4.0.0.4
Now I want to go back to stock to install the latest official updates to get the updated drivers for the UMTS radio/modem module.
After that I want to unlock and get root again to use any of the lastest custom Roms again.
Switching to a touch based recovery would be nice too.
I surfed around a bit and I´m rather confused which steps I need to perform in order to do this.
I guess I need to remove root and lock the bootloader again before I can install official updates ?
Could someone please toss me in the right direction? Maybe some step-by step list?

You'll presumably want Build H.6.1-38-1 for Retail Europe from here.
Returning to stock:
Extract the files from the link above to your adb/fastboot directory if you have one. If you don't have one I've uploaded them for you here.
Connect your Xoom to your PC then open command prompt from your adb folder. (Hold shift > right click on adb-fastboot folder > click Open Command Window Here)
Type adb devices and hit enter, if no devices are listed then ensure USB debugging is switched on in Settings > Development > and tick USB Debugging, then try again.
If it still doesn't appear then download Motorola USB drivers here and try again.
If fine then run:
adb reboot bootloader​Then run the following to flash the stock image:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock​
Flashing userdata.img is going to remove all your files so back everything up first.
This should unroot your Xoom anyway, not entirely sure if the lock is required to receive updates, but it's simple to unlock again.
Once booted and through initial setup you should receive several over the air updates. (I believe the stock image is Android 3.2)
Unlock:
Connect your Xoom again and open command window in the adb-fastboot folder as before.
Run:
adb reboot bootloader
fastboot oem unlock
fastboot reboot​You'll now be unlocked.
Install Touch Recovery and Root:
Next download ClockworkMod Touch recovery from here, rename it to just recovery.img for simplicity, and copy the image to the adb-fasboot folder.
Download Xoom Universal Root from here.
Copy that file to your sdcard.
Then run:
adb reboot bootloader
fastboot flash recovery recovery.img​(assuming you renamed it)
Once verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Important: When you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery.
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
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​Then select reboot in ClockworkMod recovery and boot as normal.
If you are unable to use adb in recovery, then you can enable this through Windows by doing the following:
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
Finally, run:
adb reboot recovery​If ClockworkMod touch recovery is still there then all is good!
Hopefully I've made sense! Any questions, just ask.
Repeat of downloads:
Download Motorola USB Drivers (Device Manager) here.
Download ClockworkMod Touch recovery here.
Download Xoom Universal Root here.

Wow, what a detailed guide
Thank you sir

No problem!
Let me know how it goes, hopefully shouldn't have any problems.

Resetting worked great :good:
Right now I´m in an OTA marathon
all that unlock, root and recovery stuff sounds familiar so I don´t expect any problems.
Thanks so far :good:

alecbond said:
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
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​Then select reboot in ClockworkMod recovery and boot as normal.
Finally, run:
adb reboot recovery​If ClockworkMod touch recovery is still there then all is good!
Click to expand...
Click to collapse
Ok, so this is not working
after I flash touch recovery and do thta reboot thing I can enter touch recovery, thats fine.
Flashing universal root, fine.
THEN,
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
gives me error since in recovery mode there ist no adb connection
Whatever when I choose to reboot the system, recovery warns me that it will get overwritten by boot and ask me to disable this.
Shall I do this?
EDIT: Nevermind, I decided to be a little brave and just confirmed that message.
Now touch clockwork seems to be persistent and I´m a happy Xoomer again

Sorry, I had meant to reply during my lunch break.
Edit: Realised the time on the second of your posts, so wouldn't have been much help on my lunch anyway
Well I believe I just learned something new!
Either that or I'd forgotten it asked.
I assume it disables the action rather than deletes those files.
My method was just so you can use the reverse rename in future to re-enable the overwrite on boot.
In future, not that you'll necessarily ever need this information, you can enable adb in recovery through windows by doing the following
When in recovery and connected to your PC, open Device Manager, find your phone, usually under 'Other Devices'.
Then right click > Update driver > Browse my computer > Let me pick from list > Pick your phone (either one if there's two shown)
Should confirm driver installed then adb should work.
I didn't include the above previously as I couldn't remember having to do it personally.
Glad to hear all is well though!

alecbond said:
You'll presumably want Build H.6.1-38-1 for Retail Europe from here.
Returning to stock:
Extract the files from the link above to your adb/fastboot directory if you have one. If you don't have one I've uploaded them for you here.
Connect your Xoom to your PC then open command prompt from your adb folder. (Hold shift > right click on adb-fastboot folder > click Open Command Window Here)
Type adb devices and hit enter, if no devices are listed then ensure USB debugging is switched on in Settings > Development > and tick USB Debugging, then try again.
If it still doesn't appear then download Motorola USB drivers here and try again.
If fine then run:
adb reboot bootloader​Then run the following to flash the stock image:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock​
Flashing userdata.img is going to remove all your files so back everything up first.
This should unroot your Xoom anyway, not entirely sure if the lock is required to receive updates, but it's simple to unlock again.
Once booted and through initial setup you should receive several over the air updates. (I believe the stock image is Android 3.2)
Unlock:
Connect your Xoom again and open command window in the adb-fastboot folder as before.
Run:
adb reboot bootloader
fastboot oem unlock
fastboot reboot​You'll now be unlocked.
Install Touch Recovery and Root:
Next download ClockworkMod Touch recovery from here, rename it to just recovery.img for simplicity, and copy the image to the adb-fasboot folder.
Download Xoom Universal Root from here.
Copy that file to your sdcard.
Then run:
adb reboot bootloader
fastboot flash recovery recovery.img​(assuming you renamed it)
Once verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Important: When you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery.
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
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​Then select reboot in ClockworkMod recovery and boot as normal.
Finally, run:
adb reboot recovery​If ClockworkMod touch recovery is still there then all is good!
Hopefully I've made sense! Any questions, just ask.
Repeat of downloads:
Download Motorola USB Drivers (Device Manager) here.
Download ClockworkMod Touch recovery here.
Download Xoom Universal Root here.
Click to expand...
Click to collapse
Hey, you did a great guide! Would you mind if I put that in the FAQ Thread?
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD

XxLordxX said:
Hey, you did a great guide! Would you mind if I put that in the FAQ Thread?
Click to expand...
Click to collapse
No problem, I'd be honored!

[Q] Cant get to recovery mode

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.