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?
Related
i installed the lag fix on my phone today and after rebooting the screen is black it makes the boot up sounds but nothing follows. the bottom buttons work and light up, it connects via adb but i cannot access SU mode.
i also did the adb shell to allow non market apps to be installed and the funny thing is i cannot access clockworkmod recovery.
Can someone help me boot up into clockworkmod recovery when i boot up vol+and vol- it takes me to the orginal recovery.
Which rom are/were you running? I897UCJF6/JH2, or an I9000 variant?
Which lagfix did you use?
soklean said:
Can someone help me boot up into clockworkmod recovery when i boot up vol+and vol- it takes me to the orginal recovery.
Click to expand...
Click to collapse
try selecting reload packages in the stock recovery, for me that takes me into clockwork
I'd also be interested in a potential fix for this issue. I have a vibrant, however my co-worker has the captivate, and hit this same issue. Can't get SU via ADB. Can boot into recovery, and download mode, but would prefer to get back into the OS without reflashing if possible. He used the .bat file provided for RyanZA's lag fix. I'm not sure which version. He's also running the original stock Captivate firmware.
Do your SD cards mount when plugged into a computer?
Can you access /sdcard via adb shell?
max_warheads said:
Do your SD cards mount when plugged into a computer?
Can you access /sdcard via adb shell?
Click to expand...
Click to collapse
Yep!
Both /sdcard and /sdcard/sd mount and are accessible via adb shell. I'm assuming that I can't run su as it depends on the "allow" button being clicked through superuser.apk. I of course can't click that without a working screen
I'm wondering if a version of su that doesn't use superuser.apk would allow me to get in there and undo the lagfix.
Well if you knew the exact lagfix version and type you used, you might be able to get that packaged into an update.zip that would remove the fix for you... albeit, if you're not 100% certain, it could wax all your application data.
If it was RyanZA/Tatuyama/Zilch/Myself tweaking the lag fix, it's very dependent on *which* version it was. But, I might be able to whip a removal tool.
Hello Forum,
I have a problem with my Htc One S today i installed Trickdroid 8.0 and it worked fine so i wanted to install the tweaks too. So i selected what i wanted and when the phone started it got stuck at the bootloader screen. I thought it just needed some time but after 15 minutes i gave up and turnt it off. Then i went into the recovery to install the rom newly but it always says it can't mount the sd card. Already relocked the bootloader and tried to install the europe ruu 1.78 but i got error 131 i have read that might be, beacause mine was branded by T-Mobile (but no simlock or else)
Really need help appreciate any answer
Really no one knows how i can fix this ? Need to fix it pretty soon because i need my phone :/ I can't even turn mine off, so i just let the battery die don't think that's to good either
Boot into recovery and ref lash. What tweak did you do? Not all work with 8.0. Tweaks have not been updated for this version. Make sure to do a full wipe.
j0hnh0lmes said:
Boot into recovery and ref lash. What tweak did you do? Not all work with 8.0. Tweaks have not been updated for this version. Make sure to do a full wipe.
Click to expand...
Click to collapse
I can't reflash in recovery, because it always says "can't mount sd card"
Don't remember all of the tweaks i did but i did the nova launcher, remove sense, some apps, all of the tweaks on the first page and some other.
Okay now I did a "clear storage" and a "reset to factory defaults" with a stock recovery and after that i reinstalled the custom recovery again. Now I can access the sdcard again but it's empty of course. Then i bootet in recovery and tried to push the trickdroid zip on to the sdcard via adb like this "adb push Trickdroid_v8.0.0.zip /sdcard/Trickdroid_v8.0.0.zip" but then it says:
daemon not running starting it now on port 5037
daemon started successfully
protocol failure
and simply ends. How can I push the Rom really need help, because my phone has no rom at all right now ?
ah okay needed to use the adb in the android sdk folder not in the little fastboot folder i had it just worked
Not at home to double check your command line--sounds like that is issue
But, you can type adb devices first to see if phone is recognized
I usually cd to the directory I have adb/fastboot files in, put zip on C: root
and type: adb push C: "then the rest"
rugmankc said:
Not at home to double check your command line--sounds like that is issue
But, you can type adb devices first to see if phone is recognized
I usually cd to the directory I have adb/fastboot files in, put zip on C: root
and type: adb push C: "then the rest"
Click to expand...
Click to collapse
Thanks for your help but as i have written i already got it back working thread can be closed
Sorry,
I posted before your edit showed up--
Glad to hear.
steps for next time
Hi, just before the thread is locked.
What has helped me in more of these occassions:
1. Make sure you read the install instructions of the ROM builder (I overlooked the 'flash Boot.img' which was added after some version)
2. Make sure you don't 'custom' work your memory (no partitioning etc).
3. First install the ROM and do REQUIRED afterwork (most often: Data/factory reset. Which doesn't wipe your photo's or just your account information and saved settings that will interfere with new rom options)
4. after making sure it boots and it reboots.
5. If this is the case, make sure you get the tweak package pointed out by the rom builder.
6. If all else fails, first read up on XDA and rom builder's site (often community on XDA) THEN start actions well informed.
My nexus 7 (2013) just did the stuck on X during start up thing. I have a bunch of photos from my vacation on it that I would like not to lose.
I've been reading up on adb and so far have installed the SDK and toolkit. My PC recognizes that my nexus is attached when I put it into adb sideload mode.
But I'm too new to know where to go from there. There is a lot out there about using the sideloader to do various things but haven't found anything that would help me so far.
Can I somehow use an adb backup command if install a zip file with the proper commands?
Is there a way to reinstall the OS via adb sideload to get the nexus running again without wiping the internal storage?
There have been some methods mentioned that involve have USB debugging enabled or the bootloader unlocked.
But I don't have USB debugging enabled and my bootloader is locked. I couldn't find a way to enable USB debugging without the nexus being able to start up. It looks like unlocking the bootloader requires a factory reset.
You can try to use adb to get your pictures. It's located in %sdk_folder%/platform-tools.
Simply use this command to get your files
Code:
adb pull /sdcard/Pictures /destination_folder
You can also push files to your sdcard while using the push command. I would try this to push a backup to the sdcard.
Are you able to get in recovery mode (CWM etc.)?
lective renzak
Most adb commands gives me "error:closed"
adb devices gives <serial number> sideload
I can upload a zip file via sideload. I just uploaded a zip file with an empty text document. It gave me an error that the update package failed which was expected.
I know nothing about update packages.
Is there one I could install that would get the nexus working without wiping out my pictures?
I was able to install an OTA update over the adb sideloader. So at least something is working.
I was hoping that installing the update would fix things but the nexus still gets stuck on X when starting up.
I'm wondering if I can insert something into the update installer script to do a backup or pull....
There is an install-recovery.sh script that I could potentially edit and then back up.
I there a command I could put into it that would do something equivalent to an adb pull or backup?
If anyone could give me a place to start, I'd really appreciate it.
I am in the same situation as you I have found nothing and only your posts on other forums!
If you have the stock configuration with usb debugging off and the bootloader locked, you're stuck. At least I couldn't figure out anything after many hours and weeks of asking. Had to bite the bullet and do a wipe. I rooted it when I did the wipe so I could try various recovery tools.
I tried dr fone and hexamob recovery and some other ones but no luck.
The nexus toolkit helped me out a bunch to try out adb commands and install a rooted system.
Sorry I don't have better news.
For backup services, I think shutterfly gives you unlimited photo only backups. For others you can do a combination of google drive, dropbox, amazon, etc. Amazon has some special thing for music I believe.
do u have the link for OTA zip file
AM struck at the same point with my Samsung note 3 . i need the link for ota update so that i can update my OS using ADB sideload . i tried downloading a zip file from sammobile but its gives me an error
E: footer is wrong
E: signature verification failed
i don't know what else i can do .
i tried DR fone i shows my pictures but never completes the backup process and shuts down.
plz help guys
What's your problem with the note 3? Solution likely different than my nexus issue. The Samsung phones do have a power button issue. Either doesn't work or gets stuck in the pressed position so when you try to start it continues to restart. If that's the case try fiddling around with power button. I find it helpful to pull the phone apart so I can get at the actual button.
i checked the power button is fine because it say up in recovery mode but keeps restarting in safe mode or normal mode. i need to either backup my data on the device using the recovery mode or update my device so that i can fix the corrupted OS. but when i try to do a OTA update using adb sideload and a zip file that i downloaded from sammobile it gives me this error :
E: footer is wrong
E: signature verification failed
. or just help me to backup my pictures using the recovery so that i can just do a factory reset any help would be appreciated. Thanks
Haha, got the same problems. But I do have USB Debugging on - does not help anything. Crazy, if you consider that files are there but you have to delete them in order to correct the stubbornness of the OEMs....
I recently installed Linux mint and what not,
and figured out I'd be able to use ADB and fastboot commands off the bat.
So I wanted to try some,
1) adb devices ~ Got a response
2) adb shell ~ worked.
hmm, Lets try fastboot.
1) adb reboot-bootloader
2) fastboot erase cache (A harmless command as I believe)
2) fastboot reboot
Now, I wind up with no signal. APN's are removed and some apps don't function.
So i try and update CyanogenMod, And I'm greeted by an 'error' when trying to download the latest nightly.
At this point , I'm really tired and just leave my phone on and call it a night.
I wake up today and my battery is gone. Charge it for a an hour or so, and squeeze out 24%+ battery.
Try redownloading CM through chrome. No luck, still an error. A weird thought dawns on my that /sdcard0/ wasnt mounted.
So I try to go through in ES File explorer and it isn't able to explore anything except the system.
I boot into my recovery and I see my USB mount option is gone and no "internal sdcard" mount point.
Though i'm not getting any error in the logs.
So im just going to push the latest CM and Gapps and see this fixes it. Ill post my response after.
If anyone has any idea what happened, any response would be great Thank you
Update: 1
Weird, I am still able to access the Sdcard when the screen prompts me to the directory to install the zip.
unfortunately , I pushed CM to the /data/ folder before trying /sdcard0/.
But well see what happens when i re-install.
Hello people,
First of all, I'm not an expert so pardon on that.
I had a MicroSD card in my tablet and it was partitioned using GParted, 2 partitons - fat32 and ext4. I erased the whole tablet with Wipe option in TWRP and installed move2sd.zip.
Anyway... When I pressed Reboot to recovery, tablet restared, showed TWRP and screen went on and off showing TWRP logo, like it was trying to load TWRP. Now... Since I installed that .zip file it might have written some code to use MicroSD card as boot? I reinstalled TWRP by flashing it via fastboot and was able to enter TWRP again.
Now the stupid part... Since it read 0mb on internal card (tablet), I wanted to fix it by formating Data... It didnt do the trick cause /data and other folders couldn't have been found. That's where I restarted the tablet and pressed Wipe data on the screen with 3 icons (RCK, Android, Wipe data)... Since then I only see 2 screens - bootup screen with Asus logo and message: Device is unlock and the next screen is TWRP and it flickers again, goes on and off just as if it was trying to load TWRP.
I cannot reflash recovery cause there is no fastboot?
I just hope this is not an expensive paper...
djakolis said:
Hello people,
First of all, I'm not an expert so pardon on that.
I had a MicroSD card in my tablet and it was partitioned using GParted, 2 partitons - fat32 and ext4. I erased the whole tablet with Wipe option in TWRP and installed move2sd.zip.
Anyway... When I pressed Reboot to recovery, tablet restared, showed TWRP and screen went on and off showing TWRP logo, like it was trying to load TWRP. Now... Since I installed that .zip file it might have written some code to use MicroSD card as boot? I reinstalled TWRP by flashing it via fastboot and was able to enter TWRP again.
Now the stupid part... Since it read 0mb on internal card (tablet), I wanted to fix it by formating Data... It didnt do the trick cause /data and other folders couldn't have been found. That's where I restarted the tablet and pressed Wipe data on the screen with 3 icons (RCK, Android, Wipe data)... Since then I only see 2 screens - bootup screen with Asus logo and message: Device is unlock and the next screen is TWRP and it flickers again, goes on and off just as if it was trying to load TWRP.
I cannot reflash recovery cause there is no fastboot?
I just hope this is not an expensive paper...
Click to expand...
Click to collapse
You can still enter RCK ??
Not that this helps your situation, so apologies.
Just started getting the screen flicker/lines randomly when handeling it. So my guess was just the loosining of something internally.
I`m also freecarding it. So that hadden`t crossed my mind.
Time for a tear down vid I guess.
Best of luck tho.
I'll make a quick video. Be right back to you...
Edit: I cannot post a video due to XDA rules, but you can search for it: TF700 no fastboot, recovery stuck (search for recent uploads, d jakolis is my username on YouTube) If you guys cannot find it, I can email the link to you.
As you can see in the video, there is not much left to do with the tablet.
However, when I selected Wipe Data on bootloader, did it wipe kernel too? I'm asking this cause I had installed data2sd.zip along with its corresponding kernel.
What would happen if someone else with the same device installed the custom ROM on MicroSD card and handed me his MicroSD card to pop in my tablet? Would it boot off it? Would I be able to enter Android and maybe somehow re-flash recovery and stock kernel along with stock ROM?
You should still be able to connect via adb. Try adb pull /tmp/recovery.log and adb logcat.
_that said:
You should still be able to connect via adb. Try adb pull /tmp/recovery.log and adb logcat.
Click to expand...
Click to collapse
Tried adb pull /tmp/recovery.log and got recovery.txt file.
Adb logcat showed this: /sbin/sh: exec: line 1: logcat: not found
djakolis said:
Tried adb pull /tmp/recovery.log and got recovery.txt file.
Adb logcat showed this: /sbin/sh: exec: line 1: logcat: not found
Click to expand...
Click to collapse
Looks like your /data partition is not formatted properly. Try this (don't type "#" and the following comment):
Code:
adb shell # connect to a shell on the device
killall -19 recovery # suspend the recovery so that it doesn't interfere with formatting
make_ext4fs /dev/block/mmcblk0p8 # format /data
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1 # remove "wipe data" request
reboot
Wow... I don't know what to say. I'm looking at the fastboot screen! :highfive:
I didn't type the last line of your code because it rebooted itself after format data was complete - make_ext4fs... Is there any consequence for not typing the last line?
Alright, I'm in recovery right now. Question: What is installed on the tablet right now? If anything... May I proceed with installing stock ROM and maybe do nvflash process to have an unbrickable device?
P.S. What does it take to learn all these things? I'm curious cause I like coding, so if you feel happy to share it, I'm all ears.
djakolis said:
Wow... I don't know what to say. I'm looking at the fastboot screen! :highfive:
I didn't type the last line of your code because it rebooted itself after format data was complete - make_ext4fs... Is there any consequence for not typing the last line?
Click to expand...
Click to collapse
Maybe the "killall -19" stuff didn't work and the recovery was not suspended, so it may have somehow determined that the wipe was finished and initiated a reboot.
djakolis said:
Alright, I'm in recovery right now. Question: What is installed on the tablet right now? If anything... May I proceed with installing stock ROM and maybe do nvflash process to have an unbrickable device?
Click to expand...
Click to collapse
What is installed? Whatever recovery, kernel and ROM you installed last. No other apps since you just formatted /data.
Since the nvflash (flatline) process saves only BCT, bootloader, partition table and unlock token (basically all the stuff you need to get fastboot working on a hard bricked tablet), you can do that now.
djakolis said:
P.S. What does it take to learn all these things? I'm curious cause I like coding, so if you feel happy to share it, I'm all ears.
Click to expand...
Click to collapse
Lots of reading here, lots of googling and more reading. Experience with Linux on PCs helps too.
where can i wirte this codes i dont know , can anyone help me??? i have same problem
i can not connect device also in adb mode pc didnt accept the drivers
y3akup said:
i can not connect device also in adb mode pc didnt accept the drivers
Click to expand...
Click to collapse
If you can still enter recovery (which one do you have?) you can use the build in Terminal.
Otherwise you have to get the adb drivers installed and working. There is no other way if you do not have a working recover and cannot get into fastboot.
Try this tool: http://forum.xda-developers.com/showthread.php?t=2588979
Once you get the drivers installed boot the tablet to recovery and post what you get with this command:
Code:
adb devices
berndblb said:
If you can still enter recovery (which one do you have?) you can use the build in Terminal.
Otherwise you have to get the adb drivers installed and working. There is no other way if you do not have a working recover and cannot get into fastboot.
Try this tool: http://forum.xda-developers.com/showthread.php?t=2588979
Once you get the drivers installed boot the tablet to recovery and post what you get with this command:
Code:
adb devices
Click to expand...
Click to collapse
i tried this tool before but still in the device manager page i have transformer device with yellow flag
y3akup said:
i tried this tool before but still in the device manager page i have transformer device with yellow flag
Click to expand...
Click to collapse
You need to install the drivers - right click on the yellow ? and choose install drivers
Use these ones here:
http://www.androidfilehost.com/?fid=23329332407571009
http://www.androidfilehost.com/?fid=2332933240
now i have
0123456789ABCDEF recovery
but commands that from other posts didnt work
y3akup said:
now i have
0123456789ABCDEF recovery
but commands that from other posts didnt work
Click to expand...
Click to collapse
Try this command only:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
Copy and paste it into your cmd window
sorry but it says dd is not inside or outsite command and bla bla i cant translate directly but like this
is not recognized as an internal or external command, operable program or batch file
berndblb said:
Try this command only:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
Copy and paste it into your cmd window
Click to expand...
Click to collapse
now i could enter the recovery and nearly ten times i installed rom but still it couldnt open twrp and bootloader numbers i checked but i think i did something wrong what can i do now??
y3akup said:
now i could enter the recovery and nearly ten times i installed rom but still it couldnt open twrp and bootloader numbers i checked but i think i did something wrong what can i do now??
Click to expand...
Click to collapse
Splendid!
Now - did you a full wipe in TWRP before installing the rom? Select the Wipe option and swipe the button. Then re-install the rom.
On the last page of the Aroma installer you have the option of saving the installation log. Do it.
Then back to TWRP, go to Advanced and also save the recovery log.
If the ROM still doesn't boot, post both of those logs.
Also try to capture a logcat of the boot process
Code:
adb logcat -v long > logcat.txt
Post that one too.