Database Info

"Fast Boot" not full shutdown

I've been doing alot of thinking the past 24 hours about what this Fast Boot option is and I think I've come up with the answer.
Fast Boot (available in the Settings > Applications menu) is nothing more than a deep hibernation phase for the phone. What initially got me thinking about this is the inability to power the phone off in fast boot mode and then access recovery when powering on. I discovered that when unchecking Fast Boot, the phone takes a bit longer to power down as well, and from there I was able to access recovery (with a very unflattering size 18 font).
Another test of mine, and this was the fun one, was installing Paul O'Brien's Visionary to temp root. It was successful as I was granted SU access in Android Terminal Emulator. With Fast Boot checked, I power cycled the phone and it did it's magical 3-second power on. I tried to get SU access via Terminal and...it worked! When unchecking fast boot and power cycling, I had to re-root the phone.
Perhaps these findings can help these awesome hardcore devs with creating a workaround for creating a permanent root solution. So the bottom line is unless you need to access recovery mode, keep your phone with Fast Boot on, and you won't lose root!

I can confirm this as working. Also any programs you remove, will not reappear until a restart is performed.

bubonik said:
I can confirm this as working. Also any programs you remove, will not reappear until a restart is performed.
Click to expand...
Click to collapse
Hey, how is the WiFi tether?
Sent from my HTC Glacier using XDA App

PlankLongBeard said:
Hey, how is the WiFi tether?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Version 2.0.5 works like a dream
Sent from MyTouch 4g via XDA App

allen099 said:
Version 2.0.5 works like a dream
Sent from MyTouch 4g via XDA App
Click to expand...
Click to collapse
Is there a way we can flash the leaked rom through fastboot or recovery. Deleted peep and Some other tmobile stuff trying to get back in case of update. I'm still on 2.2.
Never Mind I figured it out. Fastboot oem and the fastboot the Rom. It was the longest flash ever but I got everything back.
* Download fastboot from here
* Extract the fastboot zip to the same directory as the ROM
* Turn your 4G on with the action button held (fastboot mode)
* Type 'fastboot-windows oem rebootRUU' (case sensitive, replace windows with mac or linux as required)
* Type 'fastboot-windows flash zip PD15IMG_Glacier_TMOUS_1.14.531.1_Radio_12.28.60.140e_26.03.00.04_M2_release_152476_
signed.zip
* Let this finish, then type 'fastboot reboot' and apply the OTA
This worked for me. It isn't necessary to download fasboot if you already have it extracted in the tools folder of your android sdk. The commands were easy, it was the flash that took awhile. Also you will have to apply visionary root first to get into bootloader from your computer.

kamasi36 said:
Is there a way we can flash the leaked rom through fastboot or recovery. Deleted peep and Some other tmobile stuff trying to get back in case of update. I'm still on 2.2.
Never Mind I figured it out. Fastboot oem and the fastboot the Rom. It was the longest flash ever but I got everything back.
* Download fastboot from here
* Extract the fastboot zip to the same directory as the ROM
* Turn your 4G on with the action button held (fastboot mode)
* Type 'fastboot-windows oem rebootRUU' (case sensitive, replace windows with mac or linux as required)
* Type 'fastboot-windows flash zip PD15IMG_Glacier_TMOUS_1.14.531.1_Radio_12.28.60.140e_26.03.00.04_M2_release_152476_
signed.zip
* Let this finish, then type 'fastboot reboot' and apply the OTA
This worked for me. It isn't necessary to download fasboot if you already have it extracted in the tools folder of your android sdk. The commands were easy, it was the flash that took awhile. Also you will have to apply visionary root first to get into bootloader from your computer.
Click to expand...
Click to collapse
I'd hesitate to start modding without Clockworkmod or another Recovery system. I haven't tried using RomManager yet...does it detect and install for this phone?

allen099 said:
I'd hesitate to start modding without Clockworkmod or another Recovery system. I haven't tried using RomManager yet...does it detect and install for this phone?
Click to expand...
Click to collapse
Yeah if you don't know what you're doing you should wait on the unrevoked team. This method is a fix for anything removed by people who know how to use adb and fastboot to their original factory rom. There isn't any way that I am aware of that will allow us to overwrite the system and flash anything other than stock signed rom by way of the above.

allen099 said:
Another test of mine, and this was the fun one, was installing Paul O'Brien's Visionary to temp root. It was successful as I was granted SU access in Android Terminal Emulator. With Fast Boot checked, I power cycled the phone and it did it's magical 3-second power on. I tried to get SU access via Terminal and...it worked! When unchecking fast boot and power cycling, I had to re-root the phone.
Click to expand...
Click to collapse
Of course it did. Here's why...
When you do a "fast boot" it is similar to hibernation on x86 - meaning the memory contents is written to "disk" and restored via the bootloader of the OS. This works the same way on Linux, Windows, OS X, etc.
The MyTouch 4G is the same. When you root the phone with Visionary (or manually with a forkbomb exploit), you are re-mounting /system as r/w. From this point on, Linux is caching writes to "disk" (which are never happening.) This is the so-called "buggy" behavior of the eMMC (though I would argue it's very much deliberate, and not a bug at all.)
Now, when you hibernate, the entire contents of RAM is written to r/w storage, including the filesystem cache. When the RAM image is restored on power-on (fast boot), the cached changes to /system are restored along with the rest of the memory state of the device at that time. You will also find that the same background apps are running, just as you left them as well.
While this is interesting (for now), all HTC has to do is drop the Linux cache (either periodically via cron, or during the fast-boot init) and the changes would be reverted. Frankly I'm surprised they didn't do this already, since it would essentially kill our soft-root once and for all.

HamNCheese said:
While this is interesting (for now), all HTC has to do is drop the Linux cache (either periodically via cron, or during the fast-boot init) and the changes would be reverted. Frankly I'm surprised they didn't do this already, since it would essentially kill our soft-root once and for all.
Click to expand...
Click to collapse
If they dropped the cache during fast-boot, shutdown would require a longer time to write the changes to /data - either that or if the cache were flushed at fastboot-up, it wouldn't be able to "boot" up so quickly.

kamasi36 said:
Is there a way we can flash the leaked rom through fastboot or recovery. Deleted peep and Some other tmobile stuff trying to get back in case of update. I'm still on 2.2.
Never Mind I figured it out. Fastboot oem and the fastboot the Rom. It was the longest flash ever but I got everything back.
* Download fastboot from here
* Extract the fastboot zip to the same directory as the ROM
* Turn your 4G on with the action button held (fastboot mode)
* Type 'fastboot-windows oem rebootRUU' (case sensitive, replace windows with mac or linux as required)
* Type 'fastboot-windows flash zip PD15IMG_Glacier_TMOUS_1.14.531.1_Radio_12.28.60.140e_26.03.00.04_M2_release_152476_
signed.zip
* Let this finish, then type 'fastboot reboot' and apply the OTA
This worked for me. It isn't necessary to download fasboot if you already have it extracted in the tools folder of your android sdk. The commands were easy, it was the flash that took awhile. Also you will have to apply visionary root first to get into bootloader from your computer.
Click to expand...
Click to collapse
Are these instructions your own or are they re-posted? Is the action button the same as the menu button? I assume that if fastboot were turned off on the phone, none of these changes persist, i.e. bloatware deletions, beyond a full reboot?

EVO Design root method

I just wanted to put this out for people looking for a root method with the Design. The Super Tool hasn't worked for me when using the design. I have figured out a way that has work more than a few times now. Here is exactly what I've done to get Unlock Bootloader and able to flash a recovery.
1. Use HTC Unlocker at htcdev.com to unlock bootloader. Must have all files instaled. They will have all the files at htcdev. Follow instructions to the end and you have unlocked your bootloader.
2.http://forum.xda-developers.com/showthread.php?t=1239821 Download the su file and the recovery file that are below the YouTube video.
3. Put the two file into your sdk tool folder where you adb and fastboot.
4. Open a command prompt at that folder. Shift right click on folder and you can open a command prompt right where you need it.
5. in command prompt type "adb push recovery.img /sdcard/"
"adb push su-2.3.6.3.zip /sdcard/" with out quotes.
6. Get to fastboot using "adb reboot bootloader" in command prompt or do a battery pull, hold power and down volume then have your phone connected at fastboot where it should say fastboot usb.
7. Type "fastboot flash recovery recovery.img"
8. Once its finished unplug and hit power button while fastboot is highlighted.
9. Now you see you can use the volume down button to navigate down to recovery. When you are on it hit power button and it will boot into recovery.
9.5 I suggest selecting backup restore and making a back up of your system at this point. I have seen that in using this method if you ever let the phone completely die you can get a problem or two and it is nice to have a backup that is fresh and clean that you can start over with. If this ever does happen to you just navigated yourself to recovery like you are now and when you click backup/restore you can restore your system.
10. Using volume key navigate to instal from zip. "install zip" and then pick the "su-2.3.6.3.zip" Now superuser is installed
11. Navigate back and and reboot to system.
YEA.
This is pretty simpled down explanation but if you get stuck it usually can get worked out. I haven't seen much for ROMs for this phone yet but at least you get superuser and all the goodies that come from having that, Tether anyone, not to mention all the bloat ware you can remover with rootuninstaller from the market. Just dont use rootuninstaller to remove critical like sprintzone and so on.
Ive had good luck using this method and if anyone is developing a rom for it that would be awesome. You dont have S-off so you must do all your flashing using the skilled know how that TWRP offers using command prompts to flash img. and so on but it is not bad and it gets easier and easier to do the more you get hooked on flashing but like I said there isnt much out yet for this phone.
Hope this helps some of you.
Much Love and Many shout outs to TWRP and everyone over there who are just killing it.

Reboot with su command?

I noticed when I do a su and reboot command from terminal emulator the phone reboots instantly. After the reboot I found the /proc/last_kmsg entry... so my question is..... Is it safe to reboot like this?
Sent from my Nexus S 4G using XDA

Ok course.
Try
Su
Reboot recovery too
Sent from my Nexus S®

Something is definitely different from a regular reboot. The last_kmsg shows that the kernel think there was an error and basically does an EMERGENCY remount of a ext4 partition (not sure which one, only has block name). The last_kmsg created by doing a "adb reboot" does not show this type of warnings in the logs.

apparently, because it takes instant to reboot, unlike a proper reboot from your power menu. some devs recommend not to reboot in this method because it can cause data corruption

Its like a battery pull I think...
Sent from my Nexus S 4G using XDA

Is there a way to invoke the original reboot command?
I know it's an old thread, but I find no solution still..
I also want to safetly reboot android from a command line. I have root, naturally.
The "root" command is unsafe, as mentioned.
Is there a way to invoke the original reboot command? I have a MIUI rom, and there is a power menu in wich there is a standard reboot command. Do you know how to invoke the same command from a rooted SSH shell, or from a scheduled script?
I'm looking to find the comand in wich the phone shutdown or reboots showing the Jelly Bean logo and the progression bar.
Another soution could be to install a "reboot app" and invoke the intent of that app. But I still have not find an app that really safety reboots the system, unmonting drives, stopping process and so on...
Thank you for your kind reply.

[GUIDE] How To S-Off; Permanent Root; Custom Recovery

How to Achieve Permanent Root and S-Off:​
To get permanent root, you need to S-Off. So lets start with that first. This process will NOT wipe your device. It also works for OS X users. This guide will work on software version 1.55.605.2 (which as of 04/19/2014 is the latest OTA) and below.
--- S-OFF Instructions ---​First, you'll need to download adb, enable its use and setup debugging.
adb is part of the android SDK. You can download it here (OS X users must scroll down and download the OS X version). It does not need to be installed, just unzip it into its own folder. You can also download a zip that contain only adb and fastboot.
once you have adb, you'll need to download the drive for your M8, which can be had from HTC's driver page:
http://www.htc.com/us/software/htc-sync-manager/.
Then install it. It will install the driver necessary for adb to work. After the installation is finished, uninstall HTC Sync immediately (do this regardless of whether or not you need it; you can reinstall it later if you still want it). This will leave the driver package installed, but remove HTC sync.
Now, back to the phone. Disable all security you have on, including PINs, Pattern Locks, passwords, etc. If you have an exchange forced security policy, you will need to disable the account. You can readd it later.
Enable access to developer options. Jump into the Settings. Then you’re going to scroll down to the bottom and tap on ‘About’, next tap on ‘Software Information’. Now you’ll need to tap on ‘More’, which will give you a new menu. Now just tap on the build number 9 times and you’ll enable Developer options.
Go into developer options menu and enable USB Debugging.
Next, go to Security page and enable "Unknown sources".
Now install weaksauce from here:
http://forum.xda-developers.com/showthread.php?t=2699089
If you followed the directions correctly, you should have SuperSU installed and root access. (You can use superuser as well).
Plug in your phone into your computer. Its best to use the factory cable provided with the phone. Use a USB 2.0 type port if possible (USB3.0 ports typically have a blue tab; I have personally used a USB 3.0 Device on Windows 8.1u to perform this without any problems, but your mileage may vary).
Your phone will ask if you if you trust your computer (RSA). Choose "Always Allow".
Ensure adb is working by opening a command prompt (terminal on OS X), navigate to the adt-bundle-[XXXXX]/sdk/platform-tools and typing "adb devices" without quotes. Your phone should show up. Ensure the working directory is the directory that adb is in. Otherwise, transferring firewater may fail. On Windows, you can shift-right-click inside the folder adb is in and click open command prompt to open a cmd in that directory.
Now go download firewater from here:
http://firewater-soff.com/instructions/ Make sure to use the weaksauce method (second method). Do NOT use the temproot method.
The firewater file should be called "firewater" without any quotes or extensions (like .bin). Ensure your browser did not partially download or corrupt it.** Make sure its in the same folder as adb. Then follow directions on the firewater site. Be aware the yes/no prompt is case sensitive, so make sure to answer it with an uppercase Y as in "Yes" not "yes". During the process, you will need to enable adb shell to get root. Make sure your phone screen is on so you can see the root request. Grant it and the S-Off process will continue. Otherwise, it will hang there and eventually time out. Sometimes, the process will fail and the phone will reboot. This is okay. Just restart the process. It can sometimes take multiple tries.
When completely successfully, you now have S-OFF. Your phone's bootloader is also unlocked in the process; you do NOT need to perform any additional steps to unlock the bootloader. However, you do not have permanent root. The root that weaksuace provides goes away on reboot and must be reapplied again on startup.
**The filesize seems to vary depending on what OS/browser is used to download it. It should be around 4,519,496 (on disk) in size. If you can't execute firewater, try redownloading it.
Getting permanent root:
-Flash a custom recovery and flash a zip with su.
-[Optional] Return to stock recovery This option is for people who don't want a custom recovery.
Be aware, once rooted and S-Off'ed, you do NOT need the kernel module that enables system write access*. All system changes will survive hard reboots (adb reboot).
-- Recovery Rooting: --​
Move the supersu zip onto your internal sdcard. It can be downloaded here:
http://forum.xda-developers.com/showthread.php?t=1538053
You can use Superuser as well. Its your preference, but this guide uses SuperSU.
Uninstall weaksauce. It's no longer needed.
Uninstall SuperSU. It will be reinstalled when you flash the supersu zip. If you have SuperSU Pro installed, you can leave that in place, as that app only holds a key.
From adb, type:
adb reboot bootloader
Flash a custom recovery. CWM and TWRP are available. Use the fastboot method. Follow the directions here:
TWRP - http://teamw.in/project/twrp2/226
CWM - http://forum.xda-developers.com/showthread.php?t=2708520
Reboot into Recovery
Flash the supersu zip you downloaded.
Reboot and you're done. You have s-off and permanent root.
You can delete the downloaded supersu zip off your internal sdcard; its not longer needed.
-- Manual Root --​Perform all steps noted in section "Recovery Rooting" above.
-Download the stock recovery:
http://forum.xda-developers.com/showthread.php?t=2723112
-Ensure the stock recovery img file is in the same folder as fastboot.
-Run the following command from command line: "fastboot flash recovery stockrecovery.img" without the quotes.
-Wait for the process to finish
-Reboot the phone. You now have the stock recovery along with root. With the stock recovery installed, you can now accept OTAs provided you haven't modified/deleted any stock system files. Any new OTAs you take will remove any files/folders you added to the system partition and will remove your root. However, with S-off, this can be undone. If you lost loot after taking an OTA, simply start from the beginning of the section "Recovery Rooting".
-- Common Tweaks --
All of these are optional and are NOT required. However, you may find some benefit to them.​-- Wifi Tether Enabled --​This is unnecessary if you are on a More Everything plan or are paying for hotspot/tethering. You can force enable the native tethering application:
http://forum.xda-developers.com/showthread.php?t=2708548
-- Device Wipe after ten attempts --​I really dislike this "feature". Here is how to disable it. This works regardless if you enabled the security or its mandated by an exchange policy.
I use Root Explorer to make this change, but you can use any text editor. Make sure to mount system as R/W. Root explorer can do this from within the app.
Edit this file:
/system/customize/ACC/default.xml
change this:
Code:
<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">10</item>
to this
Code:
<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">0</item>
Reboot and its disabled.
-- Power Saver Mode --​Enable "Power Saver" mode using these directions. It's disabled and hidden by default.
http://forum.xda-developers.com/showthread.php?t=2701909
-- *Unsecured Kernel --​By default, the stock kernel prevents write access to /system. S-off and root should allow you to makes changes to system. However, some people have reported difficulties using ROM toolbox and other mods (like changing boot animations). In some cases, these issues can be resolved by flashing an insecure kernel:
http://forum.xda-developers.com/showthread.php?t=2708686
-- HTC Sense Broswer --​The stock ROM now includes Chrome as the default browser and omits the Sense Browser. Users who prefer the Sense Browser can download it here:
http://forum.xda-developers.com/showthread.php?t=2708597
-- HTC Flashlight --​The stock HTC flashlight app.
http://forum.xda-developers.com/showthread.php?t=2697025
-- Disable HTC Sync Virtual CDROM --​This disables the virtual CD-ROM from mounting.
http://forum.xda-developers.com/showthread.php?t=2709386
-- Donations --​Don't forget to donate to the developers involved in getting you here. Donations for firecracker go to [email protected] (paypal). Donations for weaksuace go to [email protected] (paypal). If I missed anyone, let me know.

FAQ​Been getting some interesting PMs. Here is some of the popular questions.
Do I need a Java card for this?
No. You just need a PC/Mac, a USB 2.0 cable and the M8. Since a public S-off method is now available, that method is obsolete and its not recommended anymore.
Do I have to change or reset my CID?
No, that is only necessary for people who s-off'ed via a Javacard.
Do I need to do any of this if I S-off'ed via Javacard?
No, this method ends with the same result.
Can I reverse this and return to completely stock?
Yes, absolutely none of the stuff done here is permanent. You can unroot, relock the bootloader, and S-On as many times as you want. You can flash an HTC RUU to return to completely stock in one go. Note: Be careful with S-On'ing a device. If you S-On a device via a newer RUU and that RUU has no known exploits, you may not be able to S-Off again until an exploit is found.
Do I need to unlock my bootloader after this?
No, the firewater exploit will S-Off and unlock your bootloader.
Will this work on a Mac?
Yes, please read the directions more carefully.
Will this work on USB 3.0 ports as that is all I have?
Usually. On OS X, I've had success using a USB 3.0 port (since recent MBPs only include USB 3). On Windows, the answer seems to be maybe, depending on your OS. Your best bet would be to try on a Windows 8,8.1,8.1u1 machine as that OS includes native support for USB 3.0; that way you aren't relying on vendor specific driver support like on Win7 or below. I have personally done this exploit on USB3 on a Surface Pro.
Will this brick my phone?
There is always a chance, but I have honestly never heard of such a thing happening. Worst case is usually a full reset of the phone.
Will this wipe/format the external SDcard?
No.
How do I flash this via ODIN?
This has absolutely nothing to do with ODIN. That is for Samsung devices. You should not even have ODIN running when do any part of this guide.
How to I convert to a Google Play edition ROM?
Wait for a developer to make one. I will post a link here if/when that happens.
See here:
http://forum.xda-developers.com/showthread.php?t=2716306
Does this affect Google Wallet or ISIS?
Yes and no. Google wallet works just fine. ISIS will detect its rooted and refuse to work. You'll need to shield root from ISIS to use it. Directions on how to do that can be found via google.
Will this work on non-Verizon HTC M8's?
Yes, though you will need to use a different recovery.
Will this unlock my device for other carriers?
No....because your device is already unlocked in its stock form. AWS band rules force Verizon to keep all their LTE devices unlocked.
Will this jailbreak my device?
No. Wrong type of phone.
I can get red triangle exclamation mark with a black screen. How do I fix this?
You are in the stock recovery. Hold power and volume up and you will get a menu. You can choose reboot system now to get out of there.

appreciate the write up. ill check back here when i find a reason to unlock it

Has anyone done it yet? It's just sitting at "adb wait-for-device push firewater /data/local/tmp" for at least 5 minutes now.

sfreemanoh said:
Has anyone done it yet? It's just sitting at "adb wait-for-device push firewater /data/local/tmp" for at least 5 minutes now.
Click to expand...
Click to collapse
I have done everything mentioned in this guide. And it works just fine.
Make sure you are connected via USB2. Also make sure your phone is on and unlocked (as in, no security PIN, pattern, password etc.). Is USB debugging on?
When you type "adb devices" from command prompt, is your device listed?

Yeah, nvm, it's fine now. When I first connected it via debugging, I didn't hit the "Always allow" option on my phone, so after the adb reboot it wasn't allowed to reconnect. Just had to disable debugging and re-enable it, it's all set now.

sfreemanoh said:
Yeah, nvm, it's fine now. When I first connected it via debugging, I didn't hit the "Always allow" option on my phone, so after the adb reboot it wasn't allowed to reconnect. Just had to disable debugging and re-enable it, it's all set now.
Click to expand...
Click to collapse
Cool. I'll add that to the guide.

I have not had time to thank and will.
At work and going to hook it up when I get home this morning so I hope no one screws with you guys and gets it pulled.
Very much appreciate all the work they put into it.
Thank you very much for the dummy proof write up
These guys around here are getting to good.
Thank you thank you thank you.

Worked Perfect! Thank you guys!

thank you so much! now i can sleep at night knowing that verizon doesn't have control of my device anymore haha!!

Im happy to see that s-off was achieved and Im going to unlock my phone right now
but quick question, I'm new to this s-off stuff so I don't know how it works entirely.
But once we unlock the bootloader
is there any way to lock it again in case we need to send the phone to HTC?
sorry for the noob question but just a question that popped into mind.

So I don't quite understand. I am S-off with the Unofficial CMWR from InvisibleK and I flashed SuperSU zip v1.94. Do I need the system write access kernel module to write to system or no?
Great guide by the way. Thanks

I have been trying for the past hour, but I cannot get adb to connect. Am I missing a step?
I downloaded the htc synch, installed the drivers, uninstalled synch. I already had weaksauce root. I downloaded sdk, extracted the bundle. I downloaded firewater, moved it to the same folder with adb.
Everytime I try to run adb it just scrolls and then closes almost immediately. I thought it was my java at first. I updated that. The computer says I'm connected through HTC drivers. I'm debugged/unknown sources...
Running windows 8.1 64bit. I don't know what else to do at this point.

blacknet101 said:
Im happy to see that s-off was achieved and Im going to unlock my phone right now
but quick question, I'm new to this s-off stuff so I don't know how it works entirely.
But once we unlock the bootloader
is there any way to lock it again in case we need to send the phone to HTC?
sorry for the noob question but just a question that popped into mind.
Click to expand...
Click to collapse
Absolutely. Everything in this guide can be reversed. You can return everything back to stock via an RUU.
nicholi2789 said:
So I don't quite understand. I am S-off with the Unofficial CMWR from InvisibleK and I flashed SuperSU zip v1.94. Do I need the system write access kernel module to write to system or no?
Great guide by the way. Thanks
Click to expand...
Click to collapse
You do not. I have modified and added a few system files and they have persisted through several hard reboots.

MultiDev said:
Absolutely. Everything in this guide can be reversed. You can return everything back to stock via an RUU.
Click to expand...
Click to collapse
Hmmm! Thanks for the reply buddy! may i ask? Where can we find these RUU files? In case we need to go back to Stock?

JelloB said:
I have been trying for the past hour, but I cannot get adb to connect. Am I missing a step?
I downloaded the htc synch, installed the drivers, uninstalled synch. I already had weaksauce root. I downloaded sdk, extracted the bundle. I downloaded firewater, moved it to the same folder with adb.
Everytime I try to run adb it just scrolls and then closes almost immediately. I thought it was my java at first. I updated that. The computer says I'm connected through HTC drivers.
Running windows 8.1 64bit. I don't know what else to do at this point.
Click to expand...
Click to collapse
Java has nothing to do with adb. You don't need it installed to any of this guide.
You need to use adb from a shell. On, windows, you need to open a command prompt. Type "cmd" with the start screen open and hit enter. Then at the prompt, use the "cd" command to navigate to the correct directory where adb is located.

When i run the "adb wait-for-device push firewater /data/local/tmp" command it come back with "failed to copy 'firewater' to '\data\local\tmp': Read-only file system". I'm lost. I have root access and everything.

MultiDev said:
Java has nothing to do with adb. You don't need it installed to any of this guide.
You need to use adb from a shell. On, windows, you need to open a command prompt. Type "cmd" with the start screen open and hit enter. Then at the prompt, use the "cd" command to navigate to the correct directory where adb is located.
Click to expand...
Click to collapse
I knew I was missing something simple. It's been a while since I've used adb. Will try now...thanks.

trying to modify the default.xml to get rid of the 10 try's and wipe pattern lock and it doesn't appear I have access to read write from it still... trying with the ES note editor when going to the file with ES File Explorer. I've ran the wp_mod.ko as directed and I haven't rebooted.
I'm wondering if I'm missing something, or maybe there's a better way to do it via command line?

blacknet101 said:
Hmmm! Thanks for the reply buddy! may i ask? Where can we find these RUU files? In case we need to go back to Stock?
Click to expand...
Click to collapse
They are available from HTC. I'll have to find the exact links. Also, many android sites will host them too.
Slimfast35 said:
When i run the "adb wait-for-device push firewater /data/local/tmp" command it come back with "failed to copy 'firewater' to '\data\local\tmp': Read-only file system". I'm lost. I have root access and everything.
Click to expand...
Click to collapse
You need root access to write there, shell does not normally have access. Beaware that weaksauce takes a minute or two before after a restart before enabling root again. So wait till you have access again before trying it.
meest said:
trying to modify the default.xml to get rid of the 10 try's and wipe pattern lock and it doesn't appear I have access to read write from it still... trying with the ES note editor when going to the file with ES File Explorer. I've ran the wp_mod.ko as directed and I haven't rebooted.
I'm wondering if I'm missing something, or maybe there's a better way to do it via command line?
Click to expand...
Click to collapse
You do not need the kernal module actually; I have removed that from the guide. I haven't used ES Note before, but no matter what, you must mount system as R/W before you can change anything. Its by default R/O or Read Only. Root explorer has a button that auto mounts it and then you can make your edit.

Please help to unbrick

Hi,
I am looking for some help as I did something stupid...
I came across some posting that explained that the moto has an unused partition under /cache that could be used for the dalvik-cache.
So I tried to move the dalvik-cache there and link /data/dalvik-cache to this new location.
Now the problem is that I get an "unfortunately the location-service has stopped" message all the time that makes the device unusuable (as soon as I press ok the same warning appears again).
When I try to boot into recovery I get a "dead android robot".
I can however access the device via adb, unfortunately I am not able to get a root shell. My device is rooted, but su in an adb-shell just hangs.
If I could only get a root-shell I could undo my changes and hopefully my device will work again, but I have to idea on what to try...
Can anone help me here?

morgonhed said:
Hi,
I am looking for some help as I did something stupid...
I came across some posting that explained that the moto has an unused partition under /cache that could be used for the dalvik-cache.
So I tried to move the dalvik-cache there and link /data/dalvik-cache to this new location.
Now the problem is that I get an "unfortunately the location-service has stopped" message all the time that makes the device unusuable (as soon as I press ok the same warning appears again).
When I try to boot into recovery I get a "dead android robot".
I can however access the device via adb, unfortunately I am not able to get a root shell. My device is rooted, but su in an adb-shell just hangs.
If I could only get a root-shell I could undo my changes and hopefully my device will work again, but I have to idea on what to try...
Can anone help me here?
Click to expand...
Click to collapse
The dead android bot is normal for stock recovery, if you didn't install a custom one. You can always flash a custom recovery using fastboot, and wipe the dalvik-cache and regular caches. Or, in the "dead android bot" screen, you can press the Vol+ key for about 15 secs, then tap the Power button, then scroll using the Vol buttons to something that says wipe cache. You might have to wipe dalvik-cache as well, if you can. I forget where the options are, since I haven't used the stock recovery in so long, sorry!

Ok, I managed to get beyond the "dead android" and from the menu I did a "wipe cache parition". That ran for some minutes, then it rebooted.
But after that I still have the same problem. The continuous "unfortunately the location-service has stopped" messages still persist.
Any other ideas?

Do you have an unlocked bootloader? If you do, the simplest solution may be to flash back to a stock ROM.

audit13 said:
Do you have an unlocked bootloader? If you do, the simplest solution may be to flash back to a stock ROM.
Click to expand...
Click to collapse
Yes my bootloader is unlocked. But I don't want to loose too much...
I believe the problem is only a permission-problem in my new /cache/dalvik-cache directory (/data/dalvik-cache now links there).
So all I would need is a way to get a root-shell (the device is rooted).
I can do a "adb shell" as normal user but that does not have the permissions to even look into /cache and for whatever reason when I type "su" I don't get an error nor do I become root but the command simply hangs...
The system as such still seems to work, e.g. my Moto still connects to my hotspot and I can ping it from there.
The even seems to be an "adb root" command, but that does not work on my adb. Is there a version of adb somewhere that would honor adb root?
Anyone with another idea on how to get a root-shell in my situation

Sorry, I don't know enough about adb commands to change the directory back to the default.
I assume you have usb debugging enabled and your computer is a trusted machine?

USB debugging is definitely enabled, whether or not I've set up my PC as trusted I don't remember.
If I didn't could that explain why I can get a shell but not as root or would you without a trusted computer not even get a shell?

Ok, issue resolved.
I've flashed clockworkmod recovery and cleared the dalvik-cache with that. That did the trick.
And moving my 300MB dalivk-cache to /cache seems to have worked and frees up memory for me, even better.
Finally the reason I could not get root in the adb shell was that when I type su in the adb-shell a superuser-request pops up on the phone that you have to acknowlege. But with constant warnings poping up I did not even see that...
Thanks for all support.

For the Developer options, look under Root access. Did you grant root access to ADB and apps?
When you type su, look at the phone's screen. Are you prompted to grant root access to ADB?