I am not able to get the recovery menu working. the exclamation with the mobile is the last screen i reach. The menu doesnt appear evn after using the volume and the camera button. I've dont all this before. Dont know hat happened all of a sudden.
Volume up plus camera?
Are you sure your buttons are working (no hardware defect)?
Check if files (/sdcard/update.zip and /sdcard/OpenRecovery) are there and fine. You can try to copy fresh ones just in case.
Or try /system/etc/init.d/60autoboot_or and set execute permissions (755 will do).
Perhaps sdcard is corrupt?
hey thanks for the response. I'm sure the buttons are working. I think it the SD card problem. I'll format it.
Is there any way to boot into recovery when you are not rooted and when your camera is not working??
Related
I could use some help getting my bluetooth to work. I've tried several of the CM7 nightlys, their RC4, phiremod v5, v5.2, and v5.3. They all flash just fine, and work great, except when I try to turn on the bluetooth. When I go to the settings and try to turn it on, it just spends 30 seconds trying then goes back to having it off. I've flashed and re-flashed the system, and have read everything I can find, but don't know what I'm doing wrong.
My steps.
1) Downloaded 8gb_clockwork-0.1-ext4.tar.gz
2) Burned the contained img file to an sd card (used the dd command)
3) Copied system image to sd card (ie phiremod-nook-V5.3.zip)
4) Unmounted sd card and inserted it into my rooted nook
5) Turned nook on
6) Formated /system /data and /cashe
7) installed from sd card, selecting zipped image (ie phiremod-nook-V5.3.zip)
8) when complete, unmounted sd card
9) removed sd card
10) rebooted
11) it always fails to boot the first time, but works find after a restart.
Can anybody see what I'm doing wrong?
What works for me is pressing 'fix permissions' in rom manager then reboot and badabing.
Sent via Tehduck Uberdistro Encore RC4 n.33/Tapatalk Pro
luciferii said:
What works for me is pressing 'fix permissions' in rom manager then reboot and badabing.
Sent via Tehduck Uberdistro Encore RC4 n.33/Tapatalk Pro
Click to expand...
Click to collapse
That did the trick!, thank you very much luciferii
Just a note as I try to avoid "Fix Permissions" when possible-
Anyone with this problem MAY be able to turn bluetooth on by rebooting and enabling it as quickly as possible.
This seems to work most of the time for most people. Not always..
If not, fix permissions and a reboot does seem to take care of it the rest of the time.
rogerdugans said:
Just a note as I try to avoid "Fix Permissions" when possible-
Anyone with this problem MAY be able to turn bluetooth on by rebooting and enabling it as quickly as possible.
This seems to work most of the time for most people. Not always..
If not, fix permissions and a reboot does seem to take care of it the rest of the time.
Click to expand...
Click to collapse
Why would you avoid fix permissions? It just sets things to sane values.
As for me, the fix I heard and what worked for me was to turn off Wifi, Power off, power back on, turn on Bluetooth and let it init, then turn on Wifi. Now both will turn on.
khaytsus said:
Why would you avoid fix permissions? It just sets things to sane values.
Click to expand...
Click to collapse
Two reasons:
#1) While I am not afraid to mess with root access or abilities I also try to avoid doing so whenever I can. If I don't NEED to, I don't. Same way I work on my linux computers. And if I have done nothing to mess perms up they SHOULD be ok.
#2) I think the simplest fix is best, every time. (As long as it actually FIXES the problem, of course.)
If all that is actually NEEDED is a reboot and turning on bluetooth quickly, why do anything else?
I could use the help of you gurus trying to get some data off my phone since I sat on it yesterday and horribly mangled the screen. The screen wont come on but it sounds like the phone is still working. The screen also doesnt respond to touching it not surprisingly
Really all I want to do is get my texts off of the thing, but with the screen not working, and ADB seeming to be disabled, im not sure how to go about that.
Is there any way for me to:
A) Remotely enable ADB(im guessing no)
B) Remotely enable Wifi(so I can use an app that is already on my phone to control it from my computer)
Any help is appreciated!
BB
If you had a custom kernel on the phone before it broke there is an option in clockwork to restart adb you would just use up down vol buttons and power buttons. I will give you a Button sequence in a minute. Just gotta reboot my phone
[Edit ]
I just rebooted my phone and the dark core kernel does not have the option to restart but I do know some kernels do post what you are tuning and maybe someone else knows. Also there is the TV OUT option just plug into your tv and see if you don't get a picture maybe its on by default. Good luck(;~}
Sent from my phone on vacation
Thanks for the reply! I was unaware you could restart ADB from CWM. I am running Serendipity VII with the most up to date Serendipity kernel I will try to find out if they support it(if anyone reading this can look in CWM and give me the key sequence that would be so awesome)
http://forum.xda-developers.com/showthread.php?t=1107894
I thought about the TV out option but I would still be unable to input anything from the touchscreen so would be a bit limited with what I can do
Thanks for the assist!
BB
Baconbreath said:
Thanks for the reply! I was unaware you could restart ADB from CWM. I am running Serendipity VII with the most up to date Serendipity kernel I will try to find out if they support it(if anyone reading this can look in CWM and give me the key sequence that would be so awesome)
http://forum.xda-developers.com/showthread.php?t=1107894
I thought about the TV out option but I would still be unable to input anything from the touchscreen so would be a bit limited with what I can do
Thanks for the assist!
BB
Click to expand...
Click to collapse
The only thing I can think of, if find out where the texts live, ADB into the phone and pull them to your PC.
I use SMS Backup app, but if you don't already have it, it won't do you any good at this point.
You know, Maybe what you can try is a nandroid backup from ADB. You may be able to save the entire ROM and contents, then pull it from your device to your PC.
Also the key sequence for mount usb in recovery might be useful but you don't get access to system only the sd card.
Sent from my phone on vacation
That would be really helpful key combo too to get some photos off of it..and maybe Tibu backed up apps. Mental note: use google+ cloud storage for photos and video in the future
BB
I gave up on this for a while....but tonight I decided to give it a go again with results! Posting steps here in case someone else runs into this...
I took the phone full apart to see if there was any damage internally besides the mashed screen and I couldnt find any. Put it back together and oddly ADB started working!
After much searching...I was able to find this solution:
http://androidcommunity.com/forums/...s-storage-through-the-recovery-console-19999/
for a step by step, all I did was :
Adb root
Adb reboot recovery
Running:
ADb devices
Showed:
List of devices attached
32326B102E3E00EC recovery
then run:
adb shell
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
and the SD card became mountable and I was able to rescue my stranded data
BB
Hi. I flashed this rom on a xperia x1, but i think i forgot to make the step with "running Haret.exe" from WinMob.
Now, when i power on the phone it boots but when android starts it cannot find /system/sh .. and the rest of files.
only fastboot is working.
Is there any way i can put those files on sdcard if i run haret.exe on another x1? or from linux?
or, is there any way i could return to winmo ? (i cant get in tri-color screen either)
no one?
come on ..
So what's the problem with copying the files via the card reader? Or installing my CM7 and pushing the files to sdcard via recovery? Moreover, going back to tri-color should always work if you hold volume down on boot
i push volume down, power on .. then green letters appears .. then .. it asks for fastboot or normal boot ..
I have all files on SD, but when android boots it gives some errors, cannot find /system/bin/sh .. and many others.
adb starts anyway, but if i try to push anything i get error .. cannot find /system/xbin/sh .. same error i get on adb shell too:>
I will make some pics and i will upload them later.
If you have any other sugestions ..
It seems that i did not press long enough the buttons
I did it all with patience. Thanks for help
Try to reformat and divide your SD card again ... that might work ... cuz this is usually the case ... also, try another SD card as some of the cards have problems in general
Hi everyone. I've recently rooted my phone and installed Link2SD. Everything works fine. I can check the 2nd partition storage info in Link2SD. All apps are linked to sd etc..However when i power off and power back on my phone i get:
Mount warning: cannot boot 2nd partition automatically, quick reboot or re-create mount file something like that. When i do a quick reboot it fixes it until i power off my phone again.
Is this normal? (i read somewhere that Link2SD does this when you turn off your phone and its normal) If not what did i do wrong? Everything else works fine like i said.
Phone: Samsung Galaxy Mini (Dart) Stock firmware: Android 2.2 (thinking of upgrading to gingerbread)
Thanks in advance
Also quick questions:
1. i have an .apx file uploaded to dropbox. Through the dropbox app on my phone, I clicked it and I installed it on my phone through dropbox. Is the file saved to my sd card? or it just "Run"
2. when i try to type chinese, some characters show up as squares, like this character -> 不
why is that? (i tried a lot of input IME and they all only display some chinese not all)
3. you know the 4 bottom lights (touch light i think its called), sometimes they just stay lit on even when i turn off the screen or even when i'm charging it overnight. can i turn those off? sometimes it goes off, sometimes not...
Thank you very much in advance
this is not normal what you should do is
do a quick reboot
move every app again to internal
make partitions again
and then install link2sd and move apps
in short do everything again
----------
tap on the file again if it prompt you to install again without downloading then file is saved to your sdcard
else keep your finger tapped on file and then select export/save then select sdcard
---------------
you must not be having Chinese language in your mobile that
or try go keyboard with Chinese input (if available)
---------
what are you talking about 4 lights galaxy mini don't have any touch keys
+1 Thanks
I'm going to return the phone cause I did a factory reset and the chinese texts still seem bugged. (only a few are displayed and some show as squares). I'll retry Link2SD again when I get the new phone.
Factory reset apparently fixed the 4 touch keys for me. I mean the menu, home, back, search keys under the touch screen.
sometimes they would just stay lit 24/7 while charging lol..
you must be having carrier specific phone
originally it was locked. I unlocked it.
UPDATE:
turns out the Samsung Dart T499 doesn't have native chinese support So some chinese characters show and some don't ....
guess i could try looking for a custom rom ..
PS: this phone suks.
yeah I was right you have T-Mobile's dart that's why it is having touch keys
Yea its from T-Mobile in the USA. I'm in Canada so its Mobilicity. Though exact same phone just branded differently.
guess theres no fully working custom rom out for this phone. The only one i know of has camera problems
UPDATE:
Managed to figure out the (Mount Warning): mount 2nd partition on boot problem. I used Link2SD 1.7 on my SGH-T499 and everything works fine now... Newest version was giving me problems ...
I'm assuming the stock rom isn't fully working with the latest Link2SD version from Play Store..
I have a XT1068 / Moto G (2014) with Dual SIM and an external SD card. The phone is not locked to any specific network.
The phone froze when I was taking photos a couple of days ago and is now stuck on a restart loop. It loads so far as asking me to enter the password to decrypt the phone. After accepting the password, it restarts a split second after the Android logo is displayed. I only had the phone for a week, I have the stock firmware installed and haven't performed any fancy mods / didn't root the phone. I honestly have no idea why this happened in the first place
I know that a factory reset will fix the problem, but it will also wipe out the data/media on the internal storage. I desperately need to try to access that media before I perform the factory reset.
Some useful info...
Phone is using the encryption feature
Media is all stored on internal storage, but I have an external SD card if that helps the recovery process (provided that I don't lose the media on the internal storage!!)
USB Debugging was not activated before the bootloop started occurring, and I have no way of accessing the UI to activate it now.
[UPDATE #1]:
Using the phone's bootloader screen, I am accessing Recovery > Load from ADB
When I connect the phone to my laptop via USB and run adb devices, the phone is being detected and listed correctly.
The device has a status of sideload. Any attempts to run other commands like shell or pull give me an "error: closed" in the terminal window.
I need to get unfettered access to run ADB in full (not just the sideload command) while in recovery mode but without wiping out the internal storage.
Any ideas on what to do next?
Anyone?
Hi!
So I am having the EXACT same problem,
I managed to fix it by making sure the phone is off,
Then, press the power button and the down volume key
After about 3 seconds let go of both keys and some texts saying recovery, factory.. should come out
using the volume down button, navigate to the recovery and to select, press the up volume key
Wait for a little while and a dead android lying on it's back should come out saying 'no command'
Press the power button and the volume up button and then, only let go of the volume up button
You can lift the power button now..
Then, unlike the first menu , we navigate using both up and down volume keys and to select, just hold the power key for 1 second
using to down volume button, go to factory reset (yes you are going to factory reset)
then press the power button..
Then wait for about 5 mins to wait for it to reset..
If that method doesn't work, then Idk how else to help..
I hope it works!!:good: