Related
is it possible that we can root our vogue-android phones or enable superuser functionallity? tia
simple answer is no we cannot. ive asked this and it's not possible, this is not a rom we flash to our vogues. one reason i chose to not use android right now. if you want to root your phone you will have to buy a g1 or hero, etc....
fixxxer2008 said:
simple answer is no we cannot. ive asked this and it's not possible, this is not a rom we flash to our vogues. one reason i chose to not use android right now. if you want to root your phone you will have to buy a g1 or hero, etc....
Click to expand...
Click to collapse
well...why isnt it possible? i kno we cannot flash android, cant we just change something in the system.img to give us superuser?
jamezelle said:
well...why isnt it possible? i kno we cannot flash android, cant we just change something in the system.img to give us superuser?
Click to expand...
Click to collapse
there are alot of things we cannot do that real android phone users can. maybe when the devs make a rom we can flash it will be possible. trust me ive looked into this and i don't think there's a way to make us superusers all the time or root the phone. what id like to see is for usb mass storage to work so we don't have to use abd all the time.
fixxxer2008 said:
there are alot of things we cannot do that real android phone users can. maybe when the devs make a rom we can flash it will be possible. trust me ive looked into this and i don't think there's a way to make us superusers all the time or root the phone. what id like to see is for usb mass storage to work so we don't have to use abd all the time.
Click to expand...
Click to collapse
well i guess all we can do is hope lol thanks
fixxxer2008 said:
there are alot of things we cannot do that real android phone users can. maybe when the devs make a rom we can flash it will be possible. trust me ive looked into this and i don't think there's a way to make us superusers all the time or root the phone. what id like to see is for usb mass storage to work so we don't have to use abd all the time.
Click to expand...
Click to collapse
Nonsense, adb gives you root access as do all recent ion builds. There are actually things we have that a real android phone can't easily do, e.g. change resolution, use sd for data. What you are probably complaining about is having a read only system partition but even this you could change if you wanted.
what are you trying to achieve by being superuser?
You can become superuser, the problem lies in the fact that current system images uses cramfs for their system.img. If you use DD to create a ext2 .img file and clone the cramfs .img file into it, you can have read write ability. The .img will be a good chunk bigger though.
if someone REALLY wants an ext2 image of one of my builds I'm happy to share. PM me with which build and the reason you want it/what you want to be able to change.
dzo said:
Nonsense, adb gives you root access as do all recent ion builds. There are actually things we have that a real android phone can't easily do, e.g. change resolution, use sd for data. What you are probably complaining about is having a read only system partition but even this you could change if you wanted.
Click to expand...
Click to collapse
thanks for clarifying this
zenulator said:
what are you trying to achieve by being superuser?
Click to expand...
Click to collapse
certain apps need the ability
Just to add some clarification to the already fine answers that are here...
The reason we use cramfs right now is because it's read-only. We used ext2 before, but being read-write, there was too much activity on the SD card, and caused some people's cards to fry. Making the system read-only has improved this, and I can't recall anyone's cards frying since that move was made.
AFAIK, a flashable ROM is still being worked on, the idea being not only that this will free our SD cards to be true removable media, but also allow us to go back to a read-write filesystem. (Someone correct me if I'm wrong.)
It has nothing to do with the phone not being "rooted." It's just read-only to save our hardware atm.
craig0r said:
Just to add some clarification to the already fine answers that are here...
The reason we use cramfs right now is because it's read-only. We used ext2 before, but being read-write, there was too much activity on the SD card, and caused some people's cards to fry. Making the system read-only has improved this, and I can't recall anyone's cards frying since that move was made.
AFAIK, a flashable ROM is still being worked on, the idea being not only that this will free our SD cards to be true removable media, but also allow us to go back to a read-write filesystem. (Someone correct me if I'm wrong.)
It has nothing to do with the phone not being "rooted." It's just read-only to save our hardware atm.
Click to expand...
Click to collapse
well I'm not sure if we could run anything beyond 1.5 on our flash, as they said the g1 doesnt have enough memory to run the official hero rom. I'm confused about the cheaper HTC qvga android phones that run donut but without touchflo..heres a vid a link
http://www.androidauthority.com/index.php/2009/08/21/htc-click-stars-in-youtube-video/
double post
doublepost
doublepost 3
id like to see the system images rooted from the start, that way we can run all of the "root only" apps on the market.
devs is this even possible? if not that really sucks as it limits us from doing what others can do with real android based phones.
I got a uk glow worm on the 27th (2 days before release ) and one of the first things that I tried to do was to root with glownooter. Bad idea! I thought that I had bricked my device. I had to use a lot of trickery to recover from a loading screen lock-up and once I did the first thing that I did was backup my nook (Which i should have done before).
UPDATE!
Please try my new ROOT install pack HERE:
http://forum.xda-developers.com/showthread.php?p=34216660#post34216660
This can be used to root and install the most requested things of this thread in just one zip.
Here is a quick guide to most things you will need to do to get started. I will update this guide as I discover and build new modifications.
To Backup and Restore
Follow this guide. Please do this BEFORE any other tinkering!
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
Its important to check your backup before proceeding! Please listen to roustabout and dont skip this step... He knows what he's talking about
roustabout said:
I'd like to suggest an addition to the backup method that many folks are using - always test your restore, but dont test it (the first time) on your device.
Your backup file should be about 2 gig.
find a 2 gig or larger flash drive or sdcard and restore your backup image to that drive.
when you're done, there should be 8 partitions, as there were on your Nook to begin with.
If you can't get that working - you're not ready to root yet. Until you're sure you can restore, don't start making changes, please.
People turn up all the time having screwed themselves over by restoring a partial backup and not knowing it, or having restored only one partition from a complete backup and having blown out the partition table.
Click to expand...
Click to collapse
Thanks roustabout
To Root!
Make sure you use the CWM file suitable for your SD Card. I used "2gb_clockwork-rc2" because my card was 2gb+.
http://forum.xda-developers.com/showthread.php?t=1360994 (Thanks mali100)
Use WinImage with admin rights to restore CWM virtual hdd image to your SD.
Download tinynoot-1-of-2 and tinynoot-2-of-2
http://forum.xda-developers.com/showthread.php?t=1650593 (Thanks to eded333 and roustabout)
Put on CWM boot SD.
Install them in CWM back to back (I didn't bother with the restart in the middle as it should not make a difference considering the file content). After a restart you should have root access and an android launcher on your 1.2.0 Nook (among other files). If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
To Add Apps
Using ADB to install apps is easy. Extract this to your C drive:
http://dl.dropbox.com/u/13673492/ADB + Fastboot + Drivers.zip
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Setup ADB over USB
OK I have taken the liberty of building a quick driver mod to support your nook through USB. It works for me. First you need to have the android SDK if you don't already (sure you do but just in case ).
http://developer.android.com/sdk/index.html
Make sure you tick to install the android USB driver when the SDK is installed.
Browse to extras\google\usb_driver in your SDK folder (wherever you put it) and replace android_winusb.inf with my file:
http://dl.dropbox.com/u/13673492/android_winusb.inf
Next go to C:\Users\your_user_account\.android and replace adb_usb.ini with my file:
http://dl.dropbox.com/u/13673492/adb_usb.ini
In device manager, point google ADB driver to this and hopefully that should get you set up!
To test type
Code:
adb devices
Its working if you get something like this:
Code:
* daemon not running. starting it now on port ____ *
* daemon started successfully *
List of devices attached
[YOUR NOOK] device
And then try
Code:
adb install app_of_your_choice.apk
UPDATE
Install Multitouch Kernel With Overclocking
Install the CWM zip using your clockworkmod SD card
http://forum.xda-developers.com/showthread.php?t=1906507
:good: Thanks to johnjtaylor for discovering that this kernel works works.
Hopefully this more comprehensive guide will get others with this software to start playing around.
If this helps, be polite and say thankyou
Have you setup ADB yet? If you can connect with ADB and get a shell, you can execute a 'df' at the shell prompt to see how much free space is available in each partition. On my NST (no glowlight) apps seem to be installed in /data/app so see how much free space is there. On the NST, this appears to be the same partition that books purchased from B&N are placed in, so if you have a lot of books from B&N, you may have to archive some to install apps. Of course all this is going on the assumption that the NST Glow is similar to the NST in this regard.
David0226 said:
Have you setup ADB yet? If you can connect with ADB and get a shell, you can execute a 'df' at the shell prompt to see how much free space is available in each partition. On my NST (no glowlight) apps seem to be installed in /data/app so see how much free space is there. On the NST, this appears to be the same partition that books purchased from B&N are placed in, so if you have a lot of books from B&N, you may have to archive some to install apps. Of course all this is going on the assumption that the NST Glow is similar to the NST in this regard.
Click to expand...
Click to collapse
Thanks for replying. I'm actually working setting up ADB now. As for books I only just got my nook so all of my titles are epub format on an sd card so i wouldn't think it would be that. As soon as I get ADB set up I will post back my results incase it helps anyone else with this new software version.
Can you look in the documentation that comes with the reader for any reference to 'third party software' or 'GPL software'. They should list where to download / apply for the source code somewhere. Once we can see the source code we can compare it against the existing versions and identify any significant issues.
I set up ADB.
Plenty of space in all partitions including /data for the apps that I want. Managed to install through "adb install some_app_i_want.apk" so problem resides with the amazon app store. Not really an issue for me because I have a specific set of apps that I want and don't need to browse the app store.
I will try to work out what's wrong for others.
staylo said:
Can you look in the documentation that comes with the reader for any reference to 'third party software' or 'GPL software'. They should list where to download / apply for the source code somewhere. Once we can see the source code we can compare it against the existing versions and identify any significant issues.
Click to expand...
Click to collapse
Thanks. I'm looking for it now
No reference to GPL. Only references to third party software are to tell me that my warranty is no longer valid (no surprise there!)
Is there any other place I can find this info thats not the documentation?
loney01843 said:
No reference to GPL. Only references to third party software are to tell me that my warranty is no longer valid (no surprise there!)
Is there any other place I can find this info thats not the documentation?
Click to expand...
Click to collapse
Nothing obvious from the uk.nook.com website. On the US site the 'support' section links to terms of service which contain the links to the open source code (see http://www.barnesandnoble.com/container/nook_lnav.asp?pid=43307 and search for NOOK 1.1.5 OSS Release ), but I can't see an equivalent on the UK site. It's an oversight, but such things happen with a new product launch.
You can email them at [email protected] . The relevant paragraph from the US site is:
1. Notwithstanding anything to the contrary in this Agreement, certain components of the Software are licensed subject to the General Public License Version 2.0, a copy of which is attached as Exhibit A (the "GPL License"). You may not use these components except in compliance with the GPL License. In addition, you may have additional rights with respect to such components under the GPL License, including, without limitation, the right to obtain the source code for such components from us. You may obtain a copy of such source code by contacting us through the contact information provided on the Web Site. We will provide such source code in accordance with the GPL License.
I don't legally have the right to request the source code myself, because I don't own a UK NOOK yet. (Yeah, thinly veiled excuse for laziness!)
staylo said:
Nothing obvious from the uk.nook.com website. On the US site the 'support' section links to terms of service which contain the links to the open source code (see http://www.barnesandnoble.com/container/nook_lnav.asp?pid=43307 and search for NOOK 1.1.5 OSS Release ), but I can't see an equivalent on the UK site. It's an oversight, but such things happen with a new product launch.
You can email them at [email protected] . The relevant paragraph from the US site is:
1. Notwithstanding anything to the contrary in this Agreement, certain components of the Software are licensed subject to the General Public License Version 2.0, a copy of which is attached as Exhibit A (the "GPL License"). You may not use these components except in compliance with the GPL License. In addition, you may have additional rights with respect to such components under the GPL License, including, without limitation, the right to obtain the source code for such components from us. You may obtain a copy of such source code by contacting us through the contact information provided on the Web Site. We will provide such source code in accordance with the GPL License.
I don't legally have the right to request the source code myself, because I don't own a UK NOOK yet. (Yeah, thinly veiled excuse for laziness!)
Click to expand...
Click to collapse
You're obviously not that lazy. Thanks for looking and gathering all of the extra info I need. I'll send B&N an e-mail and see what they say. I wouldn't be surprised if they didn't want to hand it out considering you can use it for an easy root setup and install the amazon and kobo stores which could financially damage their advance into new territories! What are we to do! Can't even subscribe to a newspaper or magazine through the nook store yet!
I'll let you know when / if I get a response
There is a setting in nook touch tools that you need to "arm," to allow software from unknown sources to be installed before the Amazon appstore can install software on a tinynooted device.
The setting is a tickbox, "Allow non-Market apps"
Untick it if it is ticked by default, then re-tick it to get apps to install.
roustabout said:
There is a setting in nook touch tools that you need to "arm," to allow software from unknown sources to be installed before the Amazon appstore can install software on a tinynooted device.
The setting is a tickbox, "Allow non-Market apps"
Untick it if it is ticked by default, then re-tick it to get apps to install.
Click to expand...
Click to collapse
Thanks for the reply but I actually tried that. No joy. However perhaps it is this that is not working and not amazon app store. Im just installing through ADB instead. I wonder if I can enable unknown sources through ADB. Something to look at I guess!
UK tinynoot attempt failing
loney01843 said:
Thanks for the reply but I actually tried that. No joy. However perhaps it is this that is not working and not amazon app store. Im just installing through ADB instead. I wonder if I can enable unknown sources through ADB. Something to look at I guess!
Click to expand...
Click to collapse
I tried using the tinynoot process from roustabout's thread here http://forum.xda-developers.com/showthread.php?t=1650593 and am stuck on the final reboot with a "Your NOOK is starting up..." message. Could you let me know if you used a different tinynoot method/set of files?
smerrett said:
I tried using the tinynoot process from roustabout's thread here http://forum.xda-developers.com/showthread.php?t=1650593 and am stuck on the final reboot with a "Your NOOK is starting up..." message. Could you let me know if you used a different tinynoot method/set of files?
Click to expand...
Click to collapse
Yep thats what I used. You on 1.2.0 and did you back up?
I didn't backup first and to get out of the starting message I used this:
http://forum.xda-developers.com/showthread.php?t=1289233&highlight=restore
Then I made a backup using this:
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
I hope this helps!
loney01843 said:
Yep thats what I used. You on 1.2.0 and did you back up?
I didn't backup first and to get out of the starting message I used this:
http://forum.xda-developers.com/showthread.php?t=1289233&highlight=restore
Then I made a backup using this:
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
I hope this helps!
Click to expand...
Click to collapse
Thanks for the tip on screen freeze but the link to the images on that post don't work for me. I am on 1.2 and made a backup before attempting any rooting - have managed to reinstate my original nook so quite pleased with myself.
Is there any point in rooting until someone can find a way of getting apps onto the 1.2 NSTG?
smerrett said:
Thanks for the tip on screen freeze but the link to the images on that post don't work for me. I am on 1.2 and made a backup before attempting any rooting - have managed to reinstate my original nook so quite pleased with myself.
Is there any point in rooting until someone can find a way of getting apps onto the 1.2 NSTG?
Click to expand...
Click to collapse
Great that you got a backup. If you want custom apps you can either wait for a different root kit or push ahead (since you have a safety net).
As I said, it worked for me.
If you don't mind searching for the .apk files you want you can use this:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
This has worked fine for me so far. Just don't try for custom kernels yet as they seem to give me troubles.
I will work more on this tomorrow including adjusting framework for gapps.
loney01843 said:
Great that you got a backup. If you want custom apps you can either wait for a different root kit or push ahead (since you have a safety net).
As I said, it worked for me.
If you don't mind searching for the .apk files you want you can use this:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
This has worked fine for me so far. Just don't try for custom kernels yet as they seem to give me troubles.
I will work more on this tomorrow including adjusting framework for gapps.
Click to expand...
Click to collapse
Thanks also for the code but as this is my first foray into rooting I think I'll hang around and watch for a bit! Perhaps if I start learning some more I may feel confident enough to try it.
Do you have copies of the files needed for the factory reset - the links are still not working for me.
Thanks again and sorry for bothering you. Hope tomorrow is productive for you.
smerrett said:
Thanks also for the code but as this is my first foray into rooting I think I'll hang around and watch for a bit! Perhaps if I start learning some more I may feel confident enough to try it.
Do you have copies of the files needed for the factory reset - the links are still not working for me.
Thanks again and sorry for bothering you. Hope tomorrow is productive for you.
Click to expand...
Click to collapse
http://dl.dropbox.com/u/13673492/n2T-Recovery_0.2.img
This is the file needed to force factory reset. However a quality backup like you have is far more important.
For anyone who wants to give this a go, here is a quick guide for root access and app installs using windows tools until I can make something more complete:
Make sure you use the CWM file suitable for your SD Card. I used "2gb_clockwork-rc2" because my card was 2gb+.
http://forum.xda-developers.com/showthread.php?t=1360994
(Thanks mali100)
Use WinImage with admin rights to restore CWM virtual hdd image to your SD.
Download tinynoot-1-of-2 and tinynoot-2-of-2
http://forum.xda-developers.com/showthread.php?t=1650593
(Thanks to eded333 and roustabout)
Put on CWM boot SD.
Install them in CWM back to back (I didn't bother with the restart in the middle as it should not make a difference considering the file content). After a restart you should have root access and an android launcher on your 1.2.0 Nook (among other files). If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
Using ADB to install apps is easy. Extract this to your C drive:
http://dl.dropbox.com/u/13673492/ADB + Fastboot + Drivers.zip
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Hopefully this more comprehensive guide will get others with this software to start playing around.
Click thanks if this guides helpful.
loney01843 said:
If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Hopefully this more comprehensive guide will get others with this software to start playing around.
Click thanks if this guides helpful.
Click to expand...
Click to collapse
Great - thanks to your more detailed instructions, I have persevered and the second attempt at installing the tinynoot zips worked. Your post gave me the confidence to try installing apks for the first time and for anyone else who is unfamiliar with the processes used, I found these two pages useful for:
navigating within a command prompt (how naive): pcstats.com/articleview.cfm?articleid=1723&page=3
Pasting text into a command prompt (ditto): megaleecher.net/Copy_Paste_Text_Dos_Window
Sorry, as a newb I'm not trusted to post outside links yet. It took a couple of attempts of pasting and pressing enter to work out how to install using the adb code but it's not as hard as I expected.
I have tried installing the 1 Mobile Market which works but it is unable to install apps itself (not enough space).
Also, I have just installed NoRefreshToggle and can't seem to get it to work. Any thoughts - is 1.2 to blame? Really want this to work as Business Calendar Free is just a series of blinks at the moment!
Great! I'm glad you pushed onward and have root.
I am going through possibilities of other ways to install apps and mods.
No refresh is something that I would like as well but I think that the framework may need editing for 1.2.0. For fast mode a new kernel will need to be made or existing one modified.
Be aware that installing kernels not designed for this firmware can give you some serious problems.
Once I can setup app markets, I will work on these other modifications.
Stay tuned :good:
Take a look at the overclock kernel - it's got a lot of the norefresh features baked in, and gives you a nice ability to control both clock and kernel tuning (via the governor control.)
You're right, you can flash the two zips back to back with no ill effect, I was mistaken about what the second zip was doing.
I mistyped when I typed "nook touch tools," I meant nook color tools.
I'm very interested that the amazon store is not working in 1.2. I will see if the software's available for my device, so I can try to see what's happened.
As of now, the us bn site does not mention an os 1.2 for the glowlight.
Webos Ports has released Open webOS for Touchpad and now has new name of LuneOS.
This be another OS for our touchpad
Warning its still early Alpha. I hope it also get some supports
http://webos-ports.org/wiki/Tenderloin_Info
I have data reset my Touchpad and installed android Kitkat via the great Touchpad Toolbox by jcsullins. I like to dual boot between android and LuneOS
The difficult part is to do step 1. of install with no webOS. installed. I have tried but have limited knowledge of android / linux file systems
1. Create an ext3fs lvm partition of at least 1GB (use Tailor or Meta-Doctor to achieve this). It must be named ext3fs ! Tailor automatically uses this name for an ext3 partition.
If some dev or android guru's could help by creating a android app or script to create ext3fs partition and allow it to be mounted. (maybe another option for Touchpad Toolbox)
LuneOS is based on android kernel/drivers and even list android version in settings / about.
The future plan is to be able to install on any rooted android device. Currently installs on Galaxy Nexus, Nexus 4, Nexus 7 (2012), and Touchpad.
You could always use the touchpad toolbox to reinstall webos then follow the instructions there…
chris5s said:
You could always use the touchpad toolbox to reinstall webos then follow the instructions there…
Click to expand...
Click to collapse
I tried it and was lot of work for create one partition, I corrupted my webos boot and the lune.OS image had bug of no WiFi connection.(webos Ports were quick to update new image that worked). Had to data reset and start again. After seeing that lune.OS is android based has to be a easier way for us who now only have android. I don't plan to go back to webos as apps are loosing there support and browser so outdated. Line.OS is using modern browser engine, so even not many apps should be able to use websites apps.
I think atm its a very major WIP, and as such installation etc is for the very hardy lol.
Once more development has taken place then it will become easier to install and use.
Btw, think maybe this thread should be in a different forum?
Anyway, thanks for the info!
chris5s said:
I think atm its a very major WIP, and as such installation etc is for the very hardy lol.
Once more development has taken place then it will become easier to install and use.
Btw, think maybe this thread should be in a different forum?
Anyway, thanks for the info!
Click to expand...
Click to collapse
It should be in the "Other Touchpad Development" forum
I think what could help you might be this topic : http://forum.xda-developers.com/showthread.php?t=1426244
If you try to do something like this, just knowing what are the partition space and name value you need instead for android /data/media and the luna webOS port and you might be able to do something.
General Idea :
#1 : Using the recovery from the link, make the partition you need for luna and make a single partition of android which is the media store line, don't do the other line if you don't need it, they are legacy dual boot value.
#2 : Untar your installing file, you might want to refer to the old Arch Linux installer or Ubuntu Installer, they are pretty easy to code.
#3 : Boot Toolbox and install your android.
I hope for you this Luna WebOS port don't use the old media partition from Android non data/media because it will be a pain to get enough space for each partition to share between the 2 OS.
Edit : Ok, so you really need WebOS... Ok, just follow the full tutorial from the link or use the toolbox by following the onscreen tutorial (toolbox's the better option). I was thinking it was something like the Ubuntu Touch install or other Linux.
Atari-San said:
I think what could help you might be this topic : http://forum.xda-developers.com/showthread.php?t=1426244
If you try to do something like this, just knowing what are the partition space and name value you need instead for android /data/media and the luna webOS port and you might be able to do something.
General Idea :
#1 : Using the recovery from the link, make the partition you need for luna and make a single partition of android which is the media store line, don't do the other line if you don't need it, they are legacy dual boot value.
#2 : Untar your installing file, you might want to refer to the old Arch Linux installer or Ubuntu Installer, they are pretty easy to code.
#3 : Boot Toolbox and install your android.
I hope for you this Luna WebOS port don't use the old media partition from Android non data/media because it will be a pain to get enough space for each partition to share between the 2 OS.
Edit : Ok, so you really need WebOS... Ok, just follow the full tutorial from the link or use the toolbox by following the onscreen tutorial (toolbox's the better option). I was thinking it was something like the Ubuntu Touch install or other Linux.
Click to expand...
Click to collapse
You may be able to set Lune OS and Android on the same /data/media and then set permissions in each OS to only allow each respected OS read its own "sdcard".
Sent from my LGLS990 using XDA Free mobile app
Hey guys,
I have two questions.
1. How can I install a new nightly? There are so many different files for one date.
2.Can I replace webos with lunaOs? and how can I do it?
There are 2 types of luneOS images, one Dev and one non Dev, Dev has a lot of inbuilt logging for developers.
There is now a luneOS forum at
http://forums.webosnation.com/luneos/
The luneOS install has been updated and easier to understand.
May be able to use this info to install luneOS on data media.
http://forum.xda-developers.com/showthread.php?t=2761381
Hello
i have the Gold Galaxy S5 & a 64GB SDCard from Samsung.
The phone and SDCard are encrypted and have worked fine for a long while.
One day I tried accessing the files stored in the SDCard by connecting my S5 via USB 2 to my laptop (Ubuntu 15.10); and It failed to mount since.
I have created an image of the SDCard using 'dd' in Linux.
Therefore, I would rule out a hardware failure.
Furthermore, only once this card was mounted on this phone and I had a glimpse of my pictures, again it failed to copy anything out via USB.
Currently, when I put the SDCard into the phone it shows notifications saying:
... Preparing SD Card
... SD Card safe to remove
As I still have the phone encrypted - and I presume the encryption key are present.
Is there some way that I can copy the encryption key out of the phone? Use those to read the image of the SDCard?
The partition table of this SDCard does not appear to be correct - is it encrypted as well? Is this expected?
It is really annoying to have this happening when I was copying the data out of the phone as a backup ...
It would be really great to have my data back.
Your suggestion on how to solve this problem will be most welcome.
bumping ....
Thx
Since the moment that you damaged the encryption key protecting the card, the data over this card does not belong to you any more.
Kiriakos-GR said:
Since the moment that you damaged the encryption key protecting the card, the data over this card does not belong to you any more.
Click to expand...
Click to collapse
sorry
how did I 'damage' the encryption key?
I tried reading the SDCard in the same phone.
I have older backups of the phone that included the SDCard - would that help?
Thanks,
You better ask further questions in a forum specialized to Ubuntu 15.10
Kiriakos-GR said:
You better ask further questions in a forum specialized to Ubuntu 15.10
Click to expand...
Click to collapse
Doesn't sound like a problem on ubuntu's side unless it wrote some header or something when it tried to read.
Sent from my SAMSUNG-SM-G900A using Tapatalk
The card was mounted in the Phone - Ubuntu accessing it through the USB3
And it just stopped working - just like that!
But, could actually understand that it was something like that.
Would it be possible to reuse an old image (done with dd) of this USB to try and resurrect these files?
for info:
- where are the keys kept?
- surely the phone has some.
Cheers
nkdbr said:
for info:
- where are the keys kept?
- surely the phone has some.
Cheers
Click to expand...
Click to collapse
If I was aware of that? I would require 1000$ payment so to share it.
Message to all:
1) As long Samsung provides software tools only compatible with Microsoft Windows and Android, this translates that other OS platforms them are not supported.
2) Any attempt hacking phone encryption this is illegal.
3) One desperate owner who lost access to SD-card, he should physically visit Samsung service center, demonstrate proof of ownership for phone and card, and ask their help.
Kiriakos-GR said:
If I was aware of that? I would require 1000$ payment so to share it.
Message to all:
1) As long Samsung provides software tools only compatible with Microsoft Windows and Android, this translates that other OS platforms them are not supported.
2) Any attempt hacking phone encryption this is illegal.
3) One desperate owner who lost access to SD-card, he should physically visit Samsung service center, demonstrate proof of ownership for phone and card, and ask their help.
Click to expand...
Click to collapse
Android=Linux in a very basic sense. Even then, it's not 'not supported', furthermore as I said earlier, itse extremely unlikely plugging the phone in would break it regardless of the OS.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Rakuu said:
Android=Linux in a very basic sense.
Click to expand...
Click to collapse
I do agree and I did my homework about Android in old tablet about a year ago.
Rakuu said:
furthermore as I said earlier, itse extremely unlikely plugging the phone in would break it regardless of the OS.
Click to expand...
Click to collapse
When you use any OS this working with command line, this translates that if you are a terrible commander? you army this to be also drowned in the river because of you.
This is what it did happened here too.
Can someone post an installable version of "Sailfish Utilities" to this thread?
xreactx said:
Can someone post an installable version of "Sailfish Utilities" to this thread?
Click to expand...
Click to collapse
I would post the standard package which is installable, but I don't have sufficiently high status to post attachments or links yet. I succeeded in installing the package on a oneplus x after some tinkering. In the port for that device, the root partition is ext4 rather than btrfs, so I installed btrfs-progs. I also needed to install manually sailfish-utilities-all-translation-pack first (I assume that if you install from Store, this latter would be downloaded automatically as a dependency, but btrfs-progs would probably not be, since it is part of the basic install on the Jolla phone.)
mgfm99 said:
I would post the standard package which is installable, but I don't have sufficiently high status to post attachments or links yet. I succeeded in installing the package on a oneplus x after some tinkering. In the port for that device, the root partition is ext4 rather than btrfs, so I installed btrfs-progs. I also needed to install manually sailfish-utilities-all-translation-pack first (I assume that if you install from Store, this latter would be downloaded automatically as a dependency, but btrfs-progs would probably not be, since it is part of the basic install on the Jolla phone.)
Click to expand...
Click to collapse
Has anyone solved the Android capability issue for "Ported Devices" (i.e. getting android apps to run on Nexus 5).
xreactx said:
Has anyone solved the Android capability issue for "Ported Devices" (i.e. getting android apps to run on Nexus 5).
Click to expand...
Click to collapse
Yes, it's called sfdroid.