Related
What is an app (THAT WON'T FC OR FAIL) that will quickly get my N1 into recovery, fastboot, bootloader, etc mode. I had "Quickboot" for my old Magic, but it simply doesn't work with Nexus...
Any words of wisdom or is everyone else doing it the hard way like me?
hmarcus said:
What is an app (THAT WON'T FC OR FAIL) that will quickly get my N1 into recovery, fastboot, bootloader, etc mode. I had "Quickboot" for my old Magic, but it simply doesn't work with Nexus...
Any words of wisdom or is everyone else doing it the hard way like me?
Click to expand...
Click to collapse
You must be rooted for this ...
To reboot into recovery ... use the terminal (after su command) or use GScript to run this command ....
Code:
reboot recovery
To reboot into bootloader ... use the terminal (after su command) or use GScript to run this command ....
Code:
reboot bootloader
Again, I use GScript (Find it in the market) ... and if you can spare it ... throw rogro82 a donation , which does the "su" for me and make it a quick easy GUI on button press.
It never fails and never FC's.
~enom~
on terminal emulator, if you press menu, then press initial command, and type in su in the box, itll automatically do su for you everytime you launch the terminal emulator.
enomther said:
You must be rooted for this ...
To reboot into recovery ... use the terminal (after su command) or use GScript to run this command ....
Code:
reboot recovery
To reboot into bootloader ... use the terminal (after su command) or use GScript to run this command ....
Code:
reboot bootloader
Again, I use GScript (Find it in the market) ... and if you can spare it ... throw rogro82 a donation , which does the "su" for me and make it a quick easy GUI on button press.
It never fails and never FC's.
~enom~
Click to expand...
Click to collapse
awesome! worked with no problem. thank you!
informative thread.
any way to make termial > reboot recovery in to a script with an icon on the home screen? so if you wanted to quickly reboot in to recovery you could just tap it and the phone reboot. is that possible?
edit again: appears gscript does basically that.
Gscript is amazing, it has a bit of a delay with the N1 but works. I used quick boot on my G1 but doesn't work on N1 yet, hopefully developer will update cause its very easy to use!
Power, volumn down, hold trackball to restart then hold down the trackball again for bootloader.
Quick boot has been updated and works for my Nexus one G1.
I'm at a total loss here on why certain things don't have access to root on my phone:
Running Enom's latest rom.
all reboot commands are "not permitted" in terminal. Quick boot doesn't reboot. And drocap doesn't have access to root either; however, torch works, ad-free works, etc.
I've removed all super user permissions and reauthorized them and it doesn't help. USB debugging is enabled.
Does anyone have thoughts on this???
hmarcus said:
What is an app (THAT WON'T FC OR FAIL) that will quickly get my N1 into recovery, fastboot, bootloader, etc mode. I had "Quickboot" for my old Magic, but it simply doesn't work with Nexus...
Any words of wisdom or is everyone else doing it the hard way like me?
Click to expand...
Click to collapse
Running Quickboot on my rooted N1 without issue....but the command line stuff is much more bulletproof.
djnutz said:
I'm at a total loss here on why certain things don't have access to root on my phone:
Running Enom's latest rom.
all reboot commands are "not permitted" in terminal. Quick boot doesn't reboot. And drocap doesn't have access to root either; however, torch works, ad-free works, etc.
I've removed all super user permissions and reauthorized them and it doesn't help. USB debugging is enabled.
Does anyone have thoughts on this???
Click to expand...
Click to collapse
I got the same issue, and I got no idea either. I tried to start again from scratch, back to my nandroid before any custom - same issue
djnutz said:
I'm at a total loss here on why certain things don't have access to root on my phone:
Running Enom's latest rom.
all reboot commands are "not permitted" in terminal. Quick boot doesn't reboot. And drocap doesn't have access to root either; however, torch works, ad-free works, etc.
I've removed all super user permissions and reauthorized them and it doesn't help. USB debugging is enabled.
Does anyone have thoughts on this???
Click to expand...
Click to collapse
I'm pretty sure that this is dependent on the version of Terminal Emulator that you use. I had this problem once on my MyTouch and got around it by installing a different one (think that's when I bought Better Terminal Emu.).
Quick boot works for the Nexus one now. The icon is not the best looking but works.
Quickboot works every time for me.
As the title says i am completely unable to boot into download mode. I gave tried every method other than adb (I can't for the life of me figure out how to use adb) and my device simply WILL NOT boot into download mode. This is a rather discouraging issue for me, since it disables me from flashing kernels with odin3...
I have tried booting while plugged in and turned off with Odin open, tried with the phone unplugged and turned off (volume down + power) and every method simply starts the phone as normal, or loops boot animations until I release the buttons. And both volume buttos +power simply leads to recovery mode.
Please help >.
you aren't /completely/ unable. You just refuse to use the easiest way. ADB is ridiculously easy to use, you plug your phone in and type stuff into the command prompt. If you aren't able to use a computer, I'm not too sure you should be messing with your phone anyway.
1.Remove the battery, sim card, sdcard if you have one
2.Insert the battery
3.Hold both Volume buttons
4.Plug in the USB cable and continue holding both Volume buttons
Even easier than navigating is shift clicking on the tools folder and opening the prompt that way.
Sent from my SAMSUNG-SGH-I897 using XDA App
masterofthebass said:
you aren't /completely/ unable. You just refuse to use the easiest way. ADB is ridiculously easy to use, you plug your phone in and type stuff into the command prompt. If you aren't able to use a computer, I'm not too sure you should be messing with your phone anyway.
Click to expand...
Click to collapse
I don't refuse, I just don't know how. Almost every tutorial takes for granted you know how to use adb pretty well...
Sent from my SAMSUNG-SGH-I897 using XDA App
rkorzuch said:
1.Remove the battery, sim card, sdcard if you have one
2.Insert the battery
3.Hold both Volume buttons
4.Plug in the USB cable and continue holding both Volume buttons
Click to expand...
Click to collapse
You're my hero. Thank you.
djgleebs said:
I don't refuse, I just don't know how. Almost every tutorial takes for granted you know how to use adb pretty well...
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I'm going to guess you are using windows.
1. download android sdk (google it)
2. open up a command prompt (windows+r cmd)
3. navigate to the sdk tools folder (using cd to change directories)
4. type whatever adb command you are supposed to. (adb reboot download in this case)
Please next time when you have questions, post in the general. Unless you are helping with development, post it in the general with all your questions. Please also learn how to read and learn how to use the search button.
Sent from my GT-I9000 using XDA App
Why doesnt anyone read the stickies anymore??
I think the easiest way is (from rooted phone):
Open Terminal Emulator
>su <ENTER>
>reboot download <ENTER>
Easiset way is to google Android SDK. Open the folder, then open the tools folder. In there you will see adb. Drag adb onto your command window that you've opened to run commnads and then type in what you want it to do, ie: reboot recovery, reboot download then hit enter.
masterofthebass said:
I'm going to guess you are using windows.
1. download android sdk (google it)
2. open up a command prompt (windows+r cmd)
3. navigate to the sdk tools folder (using cd to change directories)
4. type whatever adb command you are supposed to. (adb reboot download in this case)
Click to expand...
Click to collapse
Step 3 is not necessary unless you are using adb push or adb pull.
Open command prompt, type command. Using ADB is not a skill. There are a whole 5 commands. adb shell, adb pull, adb push, adb reboot, and adb remount.
I have a P5113 that's been running the CM 11 nightlies just fine until a few days ago. For some unknown reason, the internal storage is stuck in read only mode which is causing applications to fail and the tablet to reboot every few minutes. I've tried using CWM recovery to do a factory reset as well as wipe cache and reformat all partitions with no effect. Have also tried to install the latest CM 11 but after reboot the older version of the image is still installed. I also cannot write or delete any files from the file system as they reappear after a reboot. I've tried to use Odin to install a factory ROM but it keeps failing and I've tried to write a PIT file to fix the partition which has also had no affect. I've tried using adb to set read/write permissions but after a reboot, the permission revert back to read only.
I would like to know if there is anything else that can be done to repartition the internal storage and reload a factory ROM so that I can start over.
Thanks
....Mike
michaelgwilson007 said:
For some unknown reason, the internal storage is stuck in read only mode
Click to expand...
Click to collapse
As you seem to know your way around: Could you try and fetch a logcat as well as the kernel dmesg output upon boot and post it for review (pastebin or similar)? If it even fails with re-flashing a Stock ROM maybe the logs give a hint about what's going on (maybe the NAND chip became corrupted leaving fsck without a possibility to fix the filesystem?).
BoneWithABeagle said:
As you seem to know your way around: Could you try and fetch a logcat as well as the kernel dmesg output upon boot and post it for review (pastebin or similar)? If it even fails with re-flashing a Stock ROM maybe the logs give a hint about what's going on (maybe the NAND chip became corrupted leaving fsck without a possibility to fix the filesystem?).
Click to expand...
Click to collapse
Thanks for the reply. I've been doing a lot of reading to work my way around. I have never reviewed the logs or know where they are but I'll see if I can figure it out. Any info on how to extract this info would be greatly appreciated.
....M
michaelgwilson007 said:
Thanks for the reply. I've been doing a lot of reading to work my way around. I have never reviewed the logs or know where they are but I'll see if I can figure it out. Any info on how to extract this info would be greatly appreciated.
....M
Click to expand...
Click to collapse
You already used "adb", so access to Settings -> Developer Options must already be enabled and "USB debugging" turned on.
Now, simply connect the tablet to the PC and open a Command Promt (or Terminal if you're on Linux). Issue a restart on the Tablet (if turned on). Once the "Galaxy Tab 2.0" kernel logo shows up issue "adb logcat >> Downloads\logcat.txt" (Windows) or "adb logcat >> Download/logcat.txt" (Linux - you may need to add a "sudo" before adb if your udev rules aren't properly set).
adb will now display "connecting" and once Android has start "adbd", should happen rather early in the boot process, it will start logging into the text file. Once the ROM has fully booted up wait for a minute, so the system settles with starting up everything, before you press CTRL+C to interrupt adb logging.
Next would be "adb shell dmesg >> Downloads\dmesg.txt" (Windows) or "adb shell dmesg >> Downloads/dmesg.txt" (Linux). That dumps the kernel output into a text file. IF you get a error here it may relate to...: 1. Your ROM is not rooted. / 2. "adb+apps" is not set in the Developer options / 3. You are running a Sammy Stock ROM where adbd has no root powers.
If you're on a Stock ROM ... Install Chainfire's adbd Insecure (you need root!), run the app, apply the patch and reboot. Now adbd behaves like in CM or OMNI (root priviledges).
You can review the text files for yourself. If you see any obvious errors that should give you a hint about what's going on. If not, then put them up for review. Though... be warned: The files contains some private data (like the MAC address of the tablet as well as some information from your WiFi). If you don't want it to be displayed to the greater public send me a PM.
BoneWithABeagle said:
You already used "adb", so access to Settings -> Developer Options must already be enabled and "USB debugging" turned on.
Now, simply connect the tablet to the PC and open a Command Promt (or Terminal if you're on Linux). Issue a restart on the Tablet (if turned on). Once the "Galaxy Tab 2.0" kernel logo shows up issue "adb logcat >> Downloads\logcat.txt" (Windows) or "adb logcat >> Download/logcat.txt" (Linux - you may need to add a "sudo" before adb if your udev rules aren't properly set).
adb will now display "connecting" and once Android has start "adbd", should happen rather early in the boot process, it will start logging into the text file. Once the ROM has fully booted up wait for a minute, so the system settles with starting up everything, before you press CTRL+C to interrupt adb logging.
Next would be "adb shell dmesg >> Downloads\dmesg.txt" (Windows) or "adb shell dmesg >> Downloads/dmesg.txt" (Linux). That dumps the kernel output into a text file. IF you get a error here it may relate to...: 1. Your ROM is not rooted. / 2. "adb+apps" is not set in the Developer options / 3. You are running a Sammy Stock ROM where adbd has no root powers.
If you're on a Stock ROM ... Install Chainfire's adbd Insecure (you need root!), run the app, apply the patch and reboot. Now adbd behaves like in CM or OMNI (root priviledges).
You can review the text files for yourself. If you see any obvious errors that should give you a hint about what's going on. If not, then put them up for review. Though... be warned: The files contains some private data (like the MAC address of the tablet as well as some information from your WiFi). If you don't want it to be displayed to the greater public send me a PM.
Click to expand...
Click to collapse
Thanks for the guidance. I'll work on getting the log files when I get home. I'm currently on CM11 with root so hopefully I'll be able to dump the kernel without too much trouble.
Once I get the files, I'll send you a PM.
.......M
Just to wrap the thread up so it won't hang around without some conclusion as we had a private exchange...
The logs showed that there's a major problem, along with some smaller ones, going on. The kernel is spamming a "command error" message, in a infinite loop at some high repetition rate, in relation to mmcblk0 to the kernel console, and logcat shows re-occurring problems with "MtpServer" which eventually crashes the "VM" (Dalvik).
Since michaelgwilson007 already attempted the "last resort" solution to flash back to Stock with a PIT for his type of SGT2 (as he said his "sdcard0" partition wasn't even there) to restore NAND partitioning and Stock firmware... the PIT goes through but he then gets a NAND write error while attempting to flash the stock firmware. Relating what the logs have to tell to what's going on the device we seem to agree that the likelyhood of the NAND chip being defective (dead flash memory cells) is very high.
Case isn't really solved, but at least we worked out a 99% probability of a hardware malfunction.
If some of the kernel dev, knowing a bit more about the low-level layer, happens to have an idea - feel free to maybe add some idea.
I sent @michaelgwilson007 a PM. You could try running an ADB command from recovery to reformat the internal storage partition. Just make sure to wait until it finishes. The instructions are in the PM.
Sent from my Nexus 4 using XDA Premium HD app
shakatu said:
I sent @michaelgwilson007 a PM. You could try running an ADB command from recovery to reformat the internal storage partition. Just make sure to wait until it finishes. The instructions are in the PM.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for your assistance. It turns out that I had a corrupt NAND chip based on a few other tests. I replaced the motherboard and I'm good to go again.
I'm having the exact same problem, but it's not stuck, and I can certainly open apps, or run the system, can't seem to delete or rewrite or even write anything. From a brief search I came to this thread, any solution other than giving it to Samsung service for repair?
Following
I have my Samsung note 3, and it will never be unlocked. So i was thinking about moving to this. Is the Verizon edition unlocked for custom roms?
Sent from my SM-N900V using XDA Free mobile app
scoreboard said:
I have my Samsung note 3, and it will never be unlocked. So i was thinking about moving to this. Is the Verizon edition unlocked for custom roms?
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
It doesn't come unlocked, but you can unlock it. That's why are a lot of us are on this phone. I had an S5 ordered, but decided against it, when I saw there wasn't any progress being made on it. I cancelled my order, bought my M8, and haven't looked back. Give me an unlocked bootloader, or give me death.
You can S-OFF (which unlocks bootloader) & root it immediately after getting it.
I came from a locked Galaxy S4 and have to say this phone is snappier than an iPhone & as unlockable as a door thats compatible with all keys ;D. Love love loveeee this phone and highly recommend it! Go for it!
I unlocked mine the moment I got home with it, no OTA update required as some people have said to do before unlocking it & as far as I've seen no ones had an actual "Oh no! They made it impossible to unlock like Sammysung!" moment.
Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...
Frausbite77 said:
Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...
Click to expand...
Click to collapse
Have u tried the weak sauce app for root then fire water to s-off?
Sent from my Insanely powered M8 using Tapatalk
holla420 said:
Have u tried the weak sauce app for root then fire water to s-off?
Sent from my Insanely powered M8 using Tapatalk
Click to expand...
Click to collapse
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.
Frausbite77 said:
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.
Click to expand...
Click to collapse
U must not being in the right directory
Sent from my Insanely powered M8 using Tapatalk
Frausbite77 said:
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.
Click to expand...
Click to collapse
What that guy above me said, if you using Windows make sure you right click+shift in the platform tools directly then see if it shows up with adb devices, if not check your drivers.
Frausbite77 said:
Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...
Click to expand...
Click to collapse
HTCDEV unlock doesn't work for the Verizon variant. To s-off just follow this step by step guide:
http://forum.xda-developers.com/showthread.php?t=2708628
PRO TIPS: Let's say that your adb and fastboot files are located in C:\Program Files\Android. Add this directory to your system path by pressing the Windows key and typing "environment". After a few letters you'll see an option called "Edit the System Environment Variables". Click on this option. The system properties windows will open to the Advanced tab. Click the Environment Variables button. In the System Variables field you'll see a variable called Path. Click on it and choose edit. In the variable value field you'll see a list of paths separated by semi colons. We want to add the path of your adb and fastboot files to the system Path variable so that adb and fastboot commands can be executed anywhere. For the example location I used above you would add the following to the end of the list:
;C:\Program Files\Android
To test, open a command prompt and type "adb". This should launch adb with no parameters. Now you can use adb and fastboot commands anywhere. When you download the firewater script file, you can just leave it in the Downloads directory. If you use Chrome you could click the arrow next to the file and choose "show in folder". Then shift+right click an empty portion of the Downloads directory window and choose "open command window here" (you can also shift+right click on folders icons to accomplish this). Should be easy to s-off now.
NOTES:
*Once adb is setup issue the command "adb devices" to ensure your phone is recognized. The first time you will get a popup on your phone asking if you want to allow the PC adb access. Make sure you check "always allow".
*Before you issue the "su" command wait about 30 seconds to allow WeakSauce to root the phone after reboot. If you get an error saying "su not found" it's because WeakSauce has not yet rooted the phone. Wait 10 seconds and try again.
*When you issue the "su" command wake your phone's display and look for a SuperSu request. Allow it obviously.
*It's possible that the process may fail. If it does just try again. If it keeps failing try a different USB 2.0 port. Also make sure you're using the best USB cable that you have. The one that came with the phone should work.
Doc Ames said:
HTCDEV unlock doesn't work for the Verizon variant. To s-off just follow this step by step guide:
http://forum.xda-developers.com/showthread.php?t=2708628
PRO TIPS: Let's say that your adb and fastboot files are located in C:\Program Files\Android. Add this directory to your system path by pressing the Windows key and typing "environment". After a few letters you'll see an option called "Edit the System Environment Variables". Click on this option. The system properties windows will open to the Advanced tab. Click the Environment Variables button. In the System Variables field you'll see a variable called Path. Click on it and choose edit. In the variable value field you'll see a list of paths separated by semi colons. We want to add the path of your adb and fastboot files to the system Path variable so that adb and fastboot commands can be executed anywhere. For the example location I used above you would add the following to the end of the list:
;C:\Program Files\Android
To test, open a command prompt and type "adb". This should launch adb with no parameters. Now you can use adb and fastboot commands anywhere. When you download the firewater script file, you can just leave it in the Downloads directory. If you use Chrome you could click the arrow next to the file and choose "show in folder". Then shift+right click an empty portion of the Downloads directory window and choose "open command window here" (you can also shift+right click on folders icons to accomplish this). Should be easy to s-off now.
NOTES:
*Once adb is setup issue the command "adb devices" to ensure your phone is recognized. The first time you will get a popup on your phone asking if you want to allow the PC adb access. Make sure you check "always allow".
*Before you issue the "su" command wait about 30 seconds to allow WeakSauce to root the phone after reboot. If you get an error saying "su not found" it's because WeakSauce has not yet rooted the phone. Wait 10 seconds and try again.
*When you issue the "su" command wake your phone's display and look for a SuperSu request. Allow it obviously.
*It's possible that the process may fail. If it does just try again. If it keeps failing try a different USB 2.0 port. Also make sure you're using the best USB cable that you have. The one that came with the phone should work.
Click to expand...
Click to collapse
Thank you for letting me know about the HTC Dev...I have a mac and set up ADB...it shows my phone off line...i get the message that says allow this computer and check always...i run adb devices and now it just returns blank...i reinstall drivers which is htc sync but the problem persists....
Frausbite77 said:
Thank you for letting me know about the HTC Dev...I have a mac and set up ADB...it shows my phone off line...i get the message that says allow this computer and check always...i run adb devices and now it just returns blank...i reinstall drivers which is htc sync but the problem persists....
Click to expand...
Click to collapse
Try 'adb kill-server' then issue 'adb start-server' then try 'adb devices'. If that doesn't work, try a different USB port. If still no joy try a different USB cable. If that doesn't work try restarting the Mac, restarting the phone, spinning around in an office chair three times, and blowing into a Nintendo cartridge. If that doesn't work I don't know what else to suggest besides trying it on a different computer or maybe in Windows. I've never had an issue with ADB so if somebody else has any ideas for Frausbite77 please chime in.
Edit: I googled this Mac ADB guide. I don't know if it really matters, but it says to have ADB/fastboot in the /usr/bin directory. Check it out. There's a script file and when run it installs the Android SDK tools to the appropriate folder. Also check the comments. Somebody else has probably had the same problem as you:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Edit 2: After reading a user's comment that the script was broken I looked at the script and it was, in fact, broken. I fixed it. Follow the guide but use this zip instead:
Doc Ames said:
Try 'adb kill-server' then issue 'adb start-server' then try 'adb devices'. If that doesn't work, try a different USB port. If still no joy try a different USB cable. If that doesn't work try restarting the Mac, restarting the phone, spinning around in an office chair three times, and blowing into a Nintendo cartridge. If that doesn't work I don't know what else to suggest besides trying it on a different computer or maybe in Windows. I've never had an issue with ADB so if somebody else has any ideas for Frausbite77 please chime in.
Edit: I googled this Mac ADB guide. I don't know if it really matters, but it says to have ADB/fastboot in the /usr/bin directory. Check it out. There's a script file and when run it installs the Android SDK tools to the appropriate folder. Also check the comments. Somebody else has probably had the same problem as you:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Edit 2: After reading a user's comment that the script was broken I looked at the script and it was, in fact, broken. I fixed it. Follow the guide but use this zip instead:
Click to expand...
Click to collapse
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!
Frausbite77 said:
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!
Click to expand...
Click to collapse
That's the proper command line for using Adb on a Mac. It won't work without using ./ before the command.
Sent from my HTC6525LVW using Tapatalk
Frausbite77 said:
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!
Click to expand...
Click to collapse
My bad. I should have mentioned that to execute a file in a Unix-like operating system you need to enter the full or relative path if it's not in your $Path environment variable. That's why you needed to add a './' before the command. The './' indicates that the file is in the current directory. That's probably why that guide recommended putting adb and fastboot in /usr/bin. If you want to fix it so that adb and fastboot commands can be run from anywhere open a terminal, change to the directory where adb and fastboot are located, and issue the following commands:
sudo mv adb /usr/bin
sudo mv fastboot /usr/bin
That will move adb and fastboot into /usr/bin which is in your $Path so you can issue the commands anywhere without using './'. I'm glad you got your M8 s-offed and recovery installed. If you're looking into custom ROMs, I can personally recommend ViperOne as a great stock option and LiquidSmooth as an AOSP option. Try em' out. Now that you have recovery you can just restore a backup if you don't like your current ROM.
Doc Ames said:
My bad. I should have mentioned that to execute a file in a Unix-like operating system you need to enter the full or relative path if it's not in your $Path environment variable. That's why you needed to add a './' before the command. The './' indicates that the file is in the current directory. That's probably why that guide recommended putting adb and fastboot in /usr/bin. If you want to fix it so that adb and fastboot commands can be run from anywhere open a terminal, change to the directory where adb and fastboot are located, and issue the following commands:
sudo mv adb /usr/bin
sudo mv fastboot /usr/bin
That will move adb and fastboot into /usr/bin which is in your $Path so you can issue the commands anywhere without using './'. I'm glad you got your M8 s-offed and recovery installed. If you're looking into custom ROMs, I can personally recommend ViperOne as a great stock option and LiquidSmooth as an AOSP option. Try em' out. Now that you have recovery you can just restore a backup if you don't like your current ROM.
Click to expand...
Click to collapse
Thanks for the advice...actually i was just going to ask about some roms...just flashed viper rom and gonna give it a go...thanks for all the help...
Frausbite77 said:
Thanks for the advice...actually i was just going to ask about some roms...just flashed viper rom and gonna give it a go...thanks for all the help...
Click to expand...
Click to collapse
You'll love it. A couple thing to note though. For some reason the 1.6 download doesn't actually contain the 1.6 OTA so you'll want to go to 'About phone' and update to 1.6. Also I believe that ViperOne defaults to power saver mode. You can change this by using the toggle in the notification drawer. If you want to add power saver and extreme power saver to the settings menu follow this guide:
http://forum.xda-developers.com/showthread.php?t=2710946
Doc Ames said:
You'll love it. A couple thing to note though. For some reason the 1.6 download doesn't actually contain the 1.6 OTA so you'll want to go to 'About phone' and update to 1.6. Also I believe that ViperOne defaults to power saver mode. You can change this by using the toggle in the notification drawer. If you want to add power saver and extreme power saver to the settings menu follow this guide:
http://forum.xda-developers.com/showthread.php?t=2710946
Click to expand...
Click to collapse
wow, man viper rom is insane, thanks for the update heads up...i wouldn't have even thought to do that...guess i have tons of reading to catch up on...thanks...
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?