Cant' mount internal memory - Nexus 10 Q&A, Help & Troubleshooting

Hello,
I have a little problem with my manta, usually I wouldn't create a new post but this time I don't really understand what's happening...
I was surfing (using chrome) when the tablet froze and rebooted.
But instead of going to the rom, I came across a page asking me for a password. (The one I attached)
Of course, I never created a password before so it can't unlock it.
On this page I can see that my settings were erased (I use English as system language and French for the keyboard). And it seem to be in the developer's language.
FYI the rom I use is the LiquidSmooth + KTManta kernel
But the problem isn't over...
After a reboot to recovery mode, TWRP also ask for a password. (Still none defined before)
Without this password it can't mount any partition :/
So I can't use my rom and I can't install another one.
Does anyone could have some information about that ?

Related

Get contacts/calendar from bricked G1

Hello,
I have a rooted my G1 with ADP 1.5 and this worked well for weeks
But then I tried to install apps2sd, with entirely bricked my phone (stops with the blinking android label)
I still have access via fastboot and system recovery utility, so reflashing should not be the problem.
But since I have disabled syncronising with google and, as always when you brick something, made no backup, I need access to the calendar and contacts.
Does anyone know how to get them back anyhow (some wired plain xml would be fine)
Or does flashing not affect the personal data? (I do not dare to test)
Maybe someone can help me??
Thanks in advance
Bricked = dead. Won't turn on. No recovery. No SPL. No fastboot.
You've soft bricked, which as you said you can recover from.
Anyway, you could try pulling the entire contents of /data and having a poke around in there, as it will still be intact.
Well, since I am not an native english speaking person, I did not know that there is an difference between bricked and softbricked
But anyway, how can I still access /data ? (I find tons of manuals for reflashing, but none of accessing a softbricked phone )
Actually you should be able to flash a ROM and get your phone back to normal without removing anything from /data. Try a donut/cupcake ROM, that should fix your problem.
contacts and calendar should be able to be seen from any computer.
odomandr said:
contacts and calendar should be able to be seen from any computer.
Click to expand...
Click to collapse
Umm.....What?!
via gmail contacts. they automatically backup i think
Log on to your Google account via a PC and the Interweb thingie and in your email section should be your contacts. Calender has its own seperate section. Dont know if this is what you are after, Hope it helps.
Well I have disabled syncronisation with google, because many friends of me dont want to have their adresses and numbers stored at googles servers and I respect that. (Well I should think about another sync method)
So I tried to flash the rom with the cracked one I used before, which didn't work, and then tried the original ADP Rom from HTC. This still is not booting, but now I have acces via adb, with I had not before.
My Problem now is, that I can access /data only with root rights, so I can not use adb pull, nor ddms (and adb file explorer can not even connect, but I am still searching if I have done anything wrong there)
Any idea how to use any file explorer with root rights ( Don't care if for Linux or Windows)
Best regards,
anymad
have u tested this.
do a nandroid backup,
flahs a new rom.
after the new rom runs, turn your phone into fastboot mode and flash the data.img out of your nandroid backup
fastboot flash data data.img
if the calender and contacts data are storen in data.img you should get it back
anymad said:
Well I have disabled syncronisation with google, because many friends of me dont want to have their adresses and numbers stored at googles servers and I respect that. (Well I should think about another sync method)
Click to expand...
Click to collapse
Your friends are dumb and your data is secure on Google's servers. Turn sync back on and never have issues like this with things that should never be issues.
Yeah, thank you very much kingchris, based on your idea I got it.
For all who search this, here is what I have done:
1. install the recovery image from cyanogen mod (http://www.cyanogenmod.com/downloads/recovery-image)
2. make an backup
3. wipe everything
4. flash with another image (I took this one : http://www.android-hilfe.de/root-ha...g1/8791-cyanogenmod-full-updates-4-2-6-a.html) but I think it does not matter which one you take
5. restored the nandroid backup to get the data back on (thought I could just select data, but it seems to do full always)
6. reflash again with new image (without wiping before !!)
(I think you could save time when at step 5 you do what kingchris said and make a "fastboot flash data data.img" with the backup from nandroid)
This is what worked for me, but of course I give no warranty at all!

[Q] Bluetooth Keyboard (HID profile?)

Hi,
My brother's desperate to get a bluetooth keyboard working with his HTC Hero (UK). Currently runs the stock HTC 2.1-update1.
It's easy enough to pair them (we've tried two) but they remain paired but unconnected. With my Galaxy S (stock 2.2.1) they work fine. I gather this is because the Hero doesn't support the SPP or HID profiles.
We've also tried most of the apps we can think of: Keypro (sits on 'connecting'), Blueinput (force-closes when you click to select they keyboard), the JP one (sits on 'connecting'). Looking at the forum for keypro it looks like they're aware of this issue and haven't yet been able to correct it.
I've heard rumours that people running custom ROMs (eg based on Cyanogenmod) have been able to get keyboards working.
So - has anyone managed to get a bluetooth keyboard working with one of these devices, and if so how? Would prefer a solution that keeps Sense installed but he says he'll let me go to vanilla android.
Thanks in advance.
For the benefit of future users (and because the forum seems to be littered with questions like this!) we managed to get it working by installing FroydVillain 1.7.2.
Main problem was the lack of a flash_image binary to install the nandroid recovery image, but we copied over one we downloaded and it worked without issue.
Keyboard was recognised immediately and works fine as an HID device.
That's interesting! But could you detail, what were the steps of this successful installing? I also have an old bt keyboard, which I'm unable to use with the hero... Thank's if you can explain any more...
Mostly we used the instructions from http:##www|villainrom.co.uk/vBwiki/index.php/Installing_Custom_ROMs , though with a change for flashing the rom as the binary wasn't available on his phone.
More specifically - use the Froydvillain download mirrors at http:##www|villainrom.co.uk/forum/showthread.php?3698 and the wiki page above, and download:
Froydvillain 1.7.0
Froydvillain 1.7.1 upgrade
Froydvillain 1.7.2 upgrade
Universal Androot
AmonRA Recovery image
Stick everything onto the SD card - either using a USB cable and your phone, or we just used a USB card reader.
Install Universal Androot. We used HTC sync and just double-clicked on the .apk but you could also use a file manager (the wiki recommends Astro).
Install Android Terminal Emulator from the market.
Root the phone using Androot (he was running the latest 2.1 so we used the 2.0-2.2 root button).
The next bit is where we differed from the wiki instructions. They tell you to type:
Code:
su
flash_image recovery /sdcard/[I]<name of recovery image file>[/I]
reboot recovery
We found that there was no flash_image binary on my brother's phone (the error read 'flash_image: not found' so downloaded one - there's a copy at http:##cyanogen-files.carneeki.net/flash_image.zip ; I can't remember exactly where we got the one we used.
The instructions we found with the binary suggested something complicated involving remounting the system partition (it's normally read-only so you can't copy the binary there). Equally, you can't run it directly from the sd card without remounting as it's set not to allow executables. We just ran it from the data partition:
Copy the flash_image file to the sd card and use:
Code:
su
cp /sdcard/flash_image /data/flash_image
chmod 700 /data/flash_image
/data/flash_image recovery /sdcard/[i]<name of recovery image file>[/i]
sync
Then just power off the phone and turn it back on with the 'Home' button pressed. You should find yourself in recovery mode using your new recovery image.
We then used Backup/Restore > Nand backup to backup the current ROM to the SD card. Then from the Wipe menu we ran through each option in turn to ensure a fully fresh setup (I gather this isn't essential, but is advised). Lastly we used Flash zip and sequentially flashed 1.7.0, 1.7.1, then 1.7.2.
Then we rebooted, and waited... and waited... and waited... The VillainROM logo with the scary red-eyed android pulsated for about 30 minutes before I gave up and removed the battery. I took out the SD card and turned the phone back on; this time it was only a few minutes before we found ourselves with a fully functional (and factory-fresh) phone.
We put the sd card back in and set up the phone as normal; then turned on bluetooth and paired the phone with the keyboard (with ours it was a matter of typing a PIN on the keyboard and pressing enter, and duplicating the number on the phone) - it was instantly recognised as an HID device and worked perfectly!
Hope that's of some use - as I mentioned before it's essentially the same as the standard instructions except for the step involving the missing flash_image binary.
[edit: sorry, I'm not allowed to post links it seems! You'll have to cut and paste, and replace the '##' with '//', and the '|' with '.']
Thank you, you were very kind! But it seems basically only a normal fv installation on a rooted phone... Only I become a bit confused with all the /data/system operations... I can try installing fv 1.72, but at the moment I don't want to give back my floyo 1.20, which is more responsive (in my phone), but gives no sinal of accepting to connect the paired bt...
Yes - it was just a new ROM install which did the job - only the lack of flash_image and the lengthy bootup before we removed the sd card confused us so hopefully it's useful to someone trying the same.
I've not heard of Floyo - but the reason I decided to try FroydVillain was that it was CyanogenMod-based rather than HTC sense based as I heard that HTC don't include bluetooth HID support in their ROMs.
The CyanogenMod changelog http:##wiki.cyanogenmod.com/index.php?title=Changelog suggests that HID support has been included since 6.0.0 so I'd expect anything based on CyanogenMod since that should be fine. I chose FroydVillain simply because my brother's not very techy and I wanted a fairly mainstream ROM for him...
Not so simple...! Out of curiosity, I went to install froyd villain, but as I imagined the result was the same! "Paired but not connected"... It seems that when you rooted the hero, something remained in /system, no idea what was it! If a developer could read this, perhaps he could understand what happened... Floyo is simply another rom based on cm... the difference is all in the rooting process, seemingly...
Not for me
Hi Guys,
as I have been running Froyd Villain 1.7.2 for a rather long time now I thought I might give it a try. As there is an Apple Bluetooth keyboard dusting around here I had quite high hopes.
The pairing process worked well and it shows an Icon with the BT Symbol encased in Black and two arrows. In the BT settings it tells me that I am connected to a BT device, never the less, no matter what input field I choose, I cannot type on the BT keyboard. There is no other Input method I could choose from either so it's still not working for me.
Damn.
What keyboard where you using?

Utility to repair Archos 70 IT

Hi all. Looking for a tool - a program which will restore the system in my Archos 70 IT. Urukdroid I installed 1.6 and I want to return to the original rom regaining a place in the internal memory because even after uninstalling Urukdroid not release the memory space that it occupied. I am interested in a tool that can restore the system when the tablet is not included. Can anyone help me. Thank you in advance.
Forgive my poor English.
1. download latest firmware from archos.com
2. reboot into recovery (powen on + hold down "vol down")
3. recovery -> repair/format -> reformat device (sry not really sure how the menus are called exactly) THIS WILL DELETE ALL THE DATA ON YOUR DEVICE AND RECREATE PARTITIONS
4. u will be asked for the previously downloaded firmware file (upload via usb connection and w8 for flash)
5. you are done - your device will we ini original state wiht latest firmware
The only sentence I don't get is:
I am interested in a tool that can restore the system when the tablet is not included
what do u mean by?
But I think u should be fine with the method described above. Since all partitions will recreated and formated u got the original stock stettings after.
FrEcP Thank you for your response. To return to the way I read the original system. Is there a program like that can save RKAnoid archos 7 for my 70IT?
wow - it's really hard to understand you
Maybe write in in your own language and try using google translate after.
I know google is not perfect either - but it's understandable most time.
Do u search for some backup program to save your data and apps before u wipe your system? Then u may try something like TitaniumBackup
If u meant RKAndroid wich is described here:
This software is for the Archos7 (home tablet) wich was a gen6 device as far as I know. The gen8 (Archos 70IT) doesn't need it for flashing the firmware.
Are u sure u have a gen8 device or is it the old gen6 archos7?
PS: next time please dont post in development section of this forum. And open those threads in "app" or "general" secion

[APP][ICS] EncPassChanger -- set different device encryption and lock screen password

Android 3+ has a nice feature -- device encryption. You can encrypt the contents of your device with a password, and after that this password must be entered during device boot, otherwise the data is permanently lost.
The bad thing is that this password is set to the screen lock PIN / password. So you either set a short password or PIN, that you can enter quickly each time you unlock your phone from sleep (but this provides weak encryption), or set a long password and have to type it 20-30 times during the day.
This stupid behavior may be fixed easily. Android provides command-line tool called 'vdc', an interface to Android Volume Manager. As written in "Notes on the implementation of encryption in Android 3.0" [1], it has a command 'cryptfs changepw', that allows changing encryption password. Of course this command must be executed as root.
vdc has some other commands related to encryption, one of them is 'cryptfs verifypw', that allows to validate the supplied password.
I'm currently writing an application that will assist user with changing encryption password. This is my first public application for Android. You can find a source code on GitHub [2]. It is very simple, but maybe android gurus here may find what to make better.
Comments and pull requests are welcome
Thanks!
[1] http source.android.com/tech/encryption/android_crypto_implementation.html
[2] https github.com/kibab/encpasschanger
Updated 30.06.2012: Added APK file!
Kibab said:
Android 3+ has a nice feature -- device encryption. You can encrypt the contents of your device with a password, and after that this password must be entered during device boot, otherwise the data is permanently lost.
The bad thing is that this password is set to the screen lock PIN / password. So you either set a short password or PIN, that you can enter quickly each time you unlock your phone from sleep (but this provides weak encryption), or set a long password and have to type it 20-30 times during the day.
This stupid behavior may be fixed easily. Android provides command-line tool called 'vdc', an interface to Android Volume Manager. As written in "Notes on the implementation of encryption in Android 3.0" [1], it has a command 'cryptfs changepw', that allows changing encryption password. Of course this command must be executed as root.
vdc has some other commands related to encryption, one of them is 'cryptfs verifypw', that allows to validate the supplied password.
I'm currently writing an application that will assist user with changing encryption password. This is my first public application for Android. You can find a source code on GitHub [2]. It is very simple, but maybe android gurus here may find what to make better.
Comments and pull requests are welcome
Thanks!
[1] http source.android.com/tech/encryption/android_crypto_implementation.html
[2] https github.com/kibab/encpasschanger
Click to expand...
Click to collapse
Sorry im noob
What will change visualy?
Or screenshot?
Sent from my LT26i using XDA Premium HD app
Thank you for this. I wanted a more simple password for the unlock, but a longer more complicated password for the decryption. You should put it on the market and charge $.99USD (or equivalent in your currency) as it's quite useful. I'd buy it
Thank you!
Actually I have registered myself as Google Play Developer, now I'm waiting for approval. As soon as my registration is approved, I will update this thread
Although I'm going to make a free and donate versions, because I believe that will help to make Android better, and people who want to say "Thank you" will buy Donate version anyway
uDroid said:
Sorry im noob
What will change visualy?
Or screenshot?
Sent from my LT26i using XDA Premium HD app
Click to expand...
Click to collapse
Nothing will change visually, hence no screenshot. What's important is that you may set strong password for decrypting the internal storage, but keep using simple password (or PIN) to unlock the screen.
P.S. I have verified that my app works on Jelly Bean too.
I have finally published an application on Google Play! Currently there is a free version, Donate version will come a bit later
The link is: https:// play.google.com/store/apps/details?id=com.kibab.android.EncPassChanger
Enjoy!
Thanks for that app, that is also what annoyed me
Thanks for this. I've been trying to work out why encryption wont work on any ROM on my HOX (dies with unable to get size of block device cryptfs), and you have given me a good lead to investigate with vdc. Information on encryption in android is sparse, and almost all threads here on XDA get no replies.
Thanks again.
I've been tempted to use device encryption recently, but there is a distinct lack of information about it, particularly on custom ROMs...
Might need to give it a go, just the lack of backup abilities might be an issue...
pulser_g2 said:
I've been tempted to use device encryption recently, but there is a distinct lack of information about it, particularly on custom ROMs...
Might need to give it a go, just the lack of backup abilities might be an issue...
Click to expand...
Click to collapse
I use CM10 on the Galaxy Nexus (maguro). Encrypted. Actually, only /data is encrypted. /system stays unencrypted. And this App works as described.
For Backup use TWRP. It asks for your password to decrypt storage.
You can then backup, restore, flash, install whole ROMs, wipe and what not.
>> I would like to see this app in Play Store <<
I should read before I post:
Kibab said:
I have finally published an application on Google Play! Currently there is a free version, Donate version will come a bit later
The link is: https://play.google.com/store/apps/details?id=com.kibab.android.EncPassChanger
Enjoy!
Click to expand...
Click to collapse
Thanks for that
btw. The encrypted /data partition lets you have two boot animations, one that is shown before code has been entered (the one in /system/media) and one after the correct code entry (the one in /data/local).
zurchpet said:
I use CM10 on the Galaxy Nexus (maguro). Encrypted. Actually, only /data is encrypted. /system stays unencrypted. And this App works as described.
For Backup use TWRP. It asks for your password to decrypt storage.
You can then backup, restore, flash, install whole ROMs, wipe and what not.
>> I would like to see this app in Play Store <<
btw. The encrypted /data partition lets you have two boot animations, one that is shown before code has been entered (the one in /system/media) and one after the correct code entry (the one in /data/local).
Click to expand...
Click to collapse
Hmm... I have i9100 (S2), so I would need to see about putting TWRP onto it...
Yeah, only data and SD are encrypted... Can TWRP cope with encrypted SD btw?
Great, it's easier than to change on command line
This should just be default android behavior
pulser_g2 said:
Hmm... I have i9100 (S2), so I would need to see about putting TWRP onto it...
Yeah, only data and SD are encrypted... Can TWRP cope with encrypted SD btw?
Click to expand...
Click to collapse
Yes, SD is encrypted too. And TWRP can only read from it after correct code entry. Don't know about the external SD though (since the Galaxy Nexus doesn0t have one).
zurchpet said:
Yes, SD is encrypted too. And TWRP can only read from it after correct code entry. Don't know about the external SD though (since the Galaxy Nexus doesn0t have one).
Click to expand...
Click to collapse
Wish I had a second phone, then I could just research this
Quite awesome. Now, can I use a strong password for encryption and then pattern lock for normal day to day use? That would be my ideal situation. I heart pattern lock!
Just trying to clarify how this works... so you keep your normal 'short' pin unlock code for unlocking the screen, but set a long code for decryption, and this code will only be requested once per boot, during bootup? Is this correct?
Thanks
How it works
Yes Sir. You are correct.
adrianblack said:
Quite awesome. Now, can I use a strong password for encryption and then pattern lock for normal day to day use? That would be my ideal situation. I heart pattern lock!
Click to expand...
Click to collapse
Unfortunately it's not possible to use pattern lock while using device encryption, Android forbids it. Patching Android framework will help, but this is completely another story and possible suggestion for ROM makers such as Cyanogenmod.
Is the 16 character Android limitation present, when using this tool? I currently use a 16 character device encryption/unlock pass phrase. I'd like to strengthen the device pass phrase some more.
I don't know if this is even possible during the device boot sequence, but being able to use a Yubikey with an OTG cable would be awesome!
RF

[Q]The graphics in gaming, overclocking my phone to 1.2 Ghz

Hello, first of all I want to let you know that I do not know enough English to make yourself write posts in the forum, so I use an interpreter (by Google)
I am "happy" (irony) GT-S5360 holder. I have a preloaded firmware on it, PurePerfomances, two partitions on the SD card (one per application, because I'm using Link2SD) and, of course, root
The first problem with which struggling for a long time and have not found online mention of it, the problem with the graphics in games. In some games there are "graphic artifacts," ie, spoils graphics, intercede for example. Some squares. This problem only occurs in games (with applications using normally) and not all. Do you have any idea of ​​what can be done?
The second problem is my phone to 1.2Ghz overclock by installing a kernel Merruka. So what's the problem? I do not know how to do it. I once tried to do the same, but ended up reinstalling the firmware. Of course I made a backup, but ive loaded kernel Merruka other CWM and backup were thread, because the system and the old kernel did not want to restore. Installations understand this:
- Make a backup in CWM
- Choose from SD card file "kernel + update.zip" and install it
- Choose from SD card file "EXT4-Converter-signed.zip" and install it
- Restore from backup data, system and cache (not restore the kernel)
- If you receive an error "E: error mount [...]" I have to reset the recovery. Missed something? Once when I installed Merruka wanted to push him forcefully by Odin, sure why not work, but I prefer to be sure of whizzes
Again, sorry for the wall of text with Google Translator and ask for quick help
Please mention the name of the ROM you are using.Also,Merruk can't restore backups (It's a bug I guess) and added to it Merruk doesn't really overclock your device to 1.2 GHZ.It's just a placebo effect,nothing else.
I used Stock ROM
Some idea of ​​the graphics?
Sent from my Galaxy Y (GT-S5360), Firmware ^^

Resources