Related
I had a friend root my phone and I know if I want to flash a new build I rename the file update and drag it to my android folder then restart the phone a certain way and press alt s to load the build.
I love my g1 and the 1.5 build Im using but I cant get any further because Ive scoured the internet and these threads and I just cant figure out what all of this computer jargon means and I dont understand how anybody does know without taking classes in it.
I think I should make a nandroid backup and partition my sd card to run apps but good lord what does this mean (regarding nandroid)???---
"anyone who has root on their G1 and has the engineering/dev spl bootloader [1] (or has a dev phone) + a recovery image with busybox and adbd running as root [2"
and this (regarding sd partition)???---
pre-requisite "You created the FAT32 / EXT2 combo partitions" I mean this is a PRE-REQUISITE! I found a thread regarding the fat/ext deal and didnt understand it either.
I know nobody is here to babysit but is there some website somebody can direct me to to begin understanding what Im reading, I mean I read through the sd partition for dummies thread and I literally understood MAYBE 10% of the words, if thats for "dummies" im clearly the "dumbest"
I have the will I just dont have the way, ive typed the language i dont understand into every search engine I know of and Ive learned nothing. You guys are born geniuses
and what the hell's a "script"
No offense intended, but I don't think you should root your phone or carry out any of the procedures outlined in the developer forum. Following instructions to the letter is important when you are performing unauthorized and unsupported hacks, and most of those instructions assume an intermediate-to-advanced level of computing understanding.
As far as "where you learn it", I assume it varies from person to person. Although in nearly all cases, you learn it slowly by absorption when you are immersed in computing culture. Eventually if you lurk enough and see a word enough times in a particular context, you gain an understanding of what it means without being explicitly told.
You learn as you read through forums and threads and asking questions. If you're lucky, someone will explain it to you.
A script is like a programming language that controls a software application.
Nandroid is a tool or script you can use to backup your phone. It takes a bit of knowledge to restore from the backup though and requires a separate thread
You can read all about SPL's here: http://forum.xda-developers.com/showthread.php?t=455860
Can't help you with busybox/adb/recovery image right now.
FAT32 and EXT2 are just file type partitions. Think of a hard drive as a box. You put a divider cutting the box down the middle to split it into 2 compartments so each compartment can store something different. That's essentially what you do to a SD card when you create a FAT32 and EXT2 partition.
I learned all this by totally screwing things up, then reading, and reading some more. Then using the search function of the forum and of course more reading.
Now I understand a good deal about ADB, terminal, and the many, many other things that come with a rooted phone,,
I don't agree with the post that said if you don't get it don't try it.....
But that is cause I learn by doing...
As mentioned, doing this is a little complicated. The wrong step can temporarily brick your phone and then you'd have to know how to fix it, which in a way also requires a certain level of knowledge. It's best to learn and absorb the information first and to NOT be in a hurry to implement what you learn.
DMaverick50 said:
I had a friend root my phone and I know if I want to flash a new build I rename the file update and drag it to my android folder then restart the phone a certain way and press alt s to load the build.
DMaverick50 said:
This will be invaluable to fixing a botched up hack. Although, many times you'll also have to wipe (alt-w) to clear out your personal settings and personal data.
DMaverick50 said:
I love my g1 and the 1.5 build Im using but I cant get any further because Ive scoured the internet and these threads and I just cant figure out what all of this computer jargon means and I dont understand how anybody does know without taking classes in it.
Click to expand...
Click to collapse
As mentioned, we all just love the stuff, and pick it up as we go. Most of us read extensively and have well set backgrounds on computers. If you want to get your degree in brain surgery, it helps to have basic knowledge of human anatomy, first.
DMaverick50 said:
I think I should make a nandroid backup and partition my sd card to run apps but good lord what does this mean (regarding nandroid)???---
"anyone who has root on their G1 and has the engineering/dev spl bootloader [1] (or has a dev phone) + a recovery image with busybox and adbd running as root [2"
Click to expand...
Click to collapse
Nandroid is a backup program build into the... "recovery mode" for lack of a better description. It's where you do the alt-s at. Alt-b creates a backup of your system. To restore it, you must read the thread sticky that walks you through it.
DMaverick50 said:
and this (regarding sd partition)???---
pre-requisite "You created the FAT32 / EXT2 combo partitions" I mean this is a PRE-REQUISITE! I found a thread regarding the fat/ext deal and didnt understand it either.
Click to expand...
Click to collapse
As mentioned, FAT32 and EXT2 are types of filesystems. Think of it as being told to store a box in a wearhouse. The filesystem, in a sense, would be like the isles, shelves, etc. that help you not just have a giant pile of stuff.
This is asking you to have an SD card that has been partitioned off into two partitions (a giant wall in the middle of the wearhouse) where on one side you have one way of storing things that is easily understandable by the average joe (windows, linux, apple) and one side that is much more complicated but much more efficient to store things that only the wearhouse manager understand (linux.)
DMaverick50 said:
I know nobody is here to babysit but is there some website somebody can direct me to to begin understanding what Im reading, I mean I read through the sd partition for dummies thread and I literally understood MAYBE 10% of the words, if thats for "dummies" im clearly the "dumbest"
Click to expand...
Click to collapse
No. We all started somewhere. Nobody here came here and understood everything over night. Most of us have YEARS of experience in the computer field, if not decades. As far as knowledge here, it takes months of READING to really start to understand things. Once you do, THEN things will make sense and then you're less likely to break your phone.
DMaverick50 said:
I have the will I just dont have the way, ive typed the language i dont understand into every search engine I know of and Ive learned nothing. You guys are born geniuses
and what the hell's a "script"
Click to expand...
Click to collapse
Read, read, read. That's my way.
And like mentioned, a script is just what it is in real life. Something you follow. If I gave you a movie script, you follow what it tells you to do while in the movie. In the computer world, it's the same. You write a script that tells the computer what to do.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I see you joined few days ago. I suggest you start from the begining. i.e. read all stickies. Every questions that you've asked here was asked before by someone else and answered multiple times.
To offer a glimpse of hope here: it's a lot easier for n00bs now as more and more people get comfortable with Android and Android tools and it's not just 2-3 guys who can answer a question. Also, at this point we have apps that will run a script for you, move your apps and caches to SD, overclock you CPU, etc etc etc.
Welcome to XDA and good luck
For the APPS2SD do this....
http://forum.xda-developers.com/showthread.php?t=500387
OH, first backup EVERYTHING on your SD card to your desktop.
Open the terminal program... I always do this **** in adb cause you wont catch me dead trying to type and read a small screen when adb is copy and paste.
type
su
cd /data
wget http://64.105.21.209/bin/lib/droid/sdsplit
chmod 555 sdsplit
/data/sdsplit -nd -fs 7500M (thats for an 8 gig card. so adjust it depending on what side card you have 4 gig = 3500M etc...)
Now you need to make sure you have an APPS2SD rom... That makes /system/sd available. Now you have to copy and make "aliases" from the old spot to the new... Million threads on that one. Just wanted to give props to "MartinFick"s script (bunch of commands in a file I guess you can say. You can run any partitioning sw on windows 7 or I would of gone that route...
i appreciate the replies. Ive been on this forum for about month checking throughout the day (instead of paying attention to my professors) but only signed up recently to post.
I do understand the concept of nandroid and the sd partition, I just get lost in the processes very quickly. In my life Ive only learned by screwing things up so im ready for almost anything. I dont want to get stuck without a phone though so Ill definitely try to get a better understanding before trying anything dramatic. I guess Ill keep looking for some website that has a search where I can just type in all of the language I dont understand, surely this type of site exists I just havent found it yet...
southsko said:
For the APPS2SD do this....
http://forum.xda-developers.com/showthread.php?t=500387
OH, first backup EVERYTHING on your SD card to your desktop.
Open the terminal program... I always do this **** in adb cause you wont catch me dead trying to type and read a small screen when adb is copy and paste.
type
su
cd /data
wget http://64.105.21.209/bin/lib/droid/sdsplit
chmod 555 sdsplit
/data/sdsplit -nd -fs 7500M (thats for an 8 gig card. so adjust it depending on what side card you have 4 gig = 3500M etc...)
Now you need to make sure you have an APPS2SD rom... That makes /system/sd available. Now you have to copy and make "aliases" from the old spot to the new... Million threads on that one. Just wanted to give props to "MartinFick"s script (bunch of commands in a file I guess you can say. You can run any partitioning sw on windows 7 or I would of gone that route...
Click to expand...
Click to collapse
The steps seem doable but it says to use jesusfreak's build, i am on dude's will this be a problem? thanks
Simple...we are the borg! The apparent knowledge is actually just one giant shared conscience, connecting our minds together from the time we log onto XDA...and we think you should join us. *Evil Laugh*
knight4linux said:
Simple...we are the borg! The apparent knowledge is actually just one giant shared conscience, connecting our minds together from the time we log onto XDA...and we think you should join us. *Evil Laugh*
Click to expand...
Click to collapse
ROFL.
DMaverick50 said:
I guess Ill keep looking for some website that has a search where I can just type in all of the language I dont understand, surely this type of site exists I just havent found it yet...
Click to expand...
Click to collapse
I'm not sure if that exists. You see, almost all of those terms were invented by people in THIS forum.
DMaverick50 said:
The steps seem doable but it says to use jesusfreak's build, i am on dude's will this be a problem? thanks
Click to expand...
Click to collapse
I did it on the dudes. Any (i think) build that enables the ext partition to be mounted to /system/sd will work...
So can I partition while on this regular build and then flash the apps2sd build or do I need to first download an apps2sd build and then do the actual partition?
some help
When it says to use the jf build that's just the one he used and is familiar with the steps the root hack the phone are the same no matter what. Now the thing you want to do is learn one proccess and stick with it weather it be abd, fastboot, or the sdcard method for beginners or noobs I do not suggest adb or fastboot cause it require knowing how to use a comand line and if you don't know what that is then don't try it. But like everyone says read about it first before you take the plunge also since you have a friend who can do it have him show you how he does it sometime seeing it done on the fly or being told while doing it with someone there to take over if things go wrong is always good. Have fun flashing and once you figure it out do it a few time to get used to it
DMaverick50 said:
I had a friend root my phone and I know if I want to flash a new build I rename the file update and drag it to my android folder then restart the phone a certain way and press alt s to load the build.
I love my g1 and the 1.5 build Im using but I cant get any further because Ive scoured the internet and these threads and I just cant figure out what all of this computer jargon means and I dont understand how anybody does know without taking classes in it.
I think I should make a nandroid backup and partition my sd card to run apps but good lord what does this mean (regarding nandroid)???---
"anyone who has root on their G1 and has the engineering/dev spl bootloader [1] (or has a dev phone) + a recovery image with busybox and adbd running as root [2"
and this (regarding sd partition)???---
pre-requisite "You created the FAT32 / EXT2 combo partitions" I mean this is a PRE-REQUISITE! I found a thread regarding the fat/ext deal and didnt understand it either.
I know nobody is here to babysit but is there some website somebody can direct me to to begin understanding what Im reading, I mean I read through the sd partition for dummies thread and I literally understood MAYBE 10% of the words, if thats for "dummies" im clearly the "dumbest"
I have the will I just dont have the way, ive typed the language i dont understand into every search engine I know of and Ive learned nothing. You guys are born geniuses
and what the hell's a "script"
Click to expand...
Click to collapse
heheh .. didn't we mention we're all a bunch of geeks - LOL - genius cannot be found here (pointing at self) .. i have been known to have a couple bright ideas now and again tho
"script" is just a funny way of saying "we did the work for you" .. all those lines of text that nobody wants to type over and over and over are all neatly packed into one little file .. type the name of the file and VOILA!! all those lines of text are spit into the little pocket sized computer and you have no blisters on your thumbs to show for it
now .. if we could only find a script that got us thru rush hour traffic
DMaverick50 said:
So can I partition while on this regular build and then flash the apps2sd build or do I need to first download an apps2sd build and then do the actual partition?
Click to expand...
Click to collapse
I did what I posted then flashed the APPS2SD rom and then transferred everything over, but when I flashed it it still had all my apps so I would say you can do it before also.
Remember to nandroid backup before you try and move all your files.
OT
Once you get adb running sending all these commands are so easy as you copy and paste and you can restore your phone back the way it was in 2 minutes...
southsko said:
I did what I posted then flashed the APPS2SD rom and then transferred everything over, but when I flashed it it still had all my apps so I would say you can do it before also.
Remember to nandroid backup before you try and move all your files.
OT
Once you get adb running sending all these commands are so easy as you copy and paste and you can restore your phone back the way it was in 2 minutes...
Click to expand...
Click to collapse
i see. im so much more confident attempting the partition after these posts im tempted to ask for the same help with nandroid since ive looked through the threads. But I guess i should head to one of them and start asking questions i know they run a pretty tight ship around here with duplicate threads and off-topic ones and what not...
nandroid was so much harder to read in the thread than it actually is
I'm hoping this thread may help other people.... and will try and help till I run out of beer.. anyway
restoring a backup when you are can connect with fastboot is so simple. Once you get adb working then dl and put fastboot in the tool dir. Then you go to your sd card /nadroid/randomcrap/whatever date/ and copy the 3 files below into the same tools directory.
from the command line on your computer type
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash data data.img
I flashed to one of the first cupcake roms and was like **** this! flashed right back to my old backup. ahhhhh!!!
southsko said:
nandroid was so much harder to read in the thread than it actually is
I'm hoping this thread may help other people.... and will try and help till I run out of beer.. anyway
restoring a backup when you are can connect with fastboot is so simple. Once you get adb working then dl and put fastboot in the tool dir. Then you go to your sd card /nadroid/randomcrap/whatever date/ and copy the 3 files below into the same tools directory.
from the command line on your computer type
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash data data.img
I flashed to one of the first cupcake roms and was like **** this! flashed right back to my old backup. ahhhhh!!!
Click to expand...
Click to collapse
Get ready to laugh..............adb? Fastboot? Everything else looks straight forward ( I assume I'm copying the 3 things to sd thru cpu)...
lmao...
Hi,
I know there's already a thread about Ubuntu, but I ran across this, and it looks a little different:
http://forum.xda-developers.com/showthread.php?p=10306407#post10306407
It looks like, instead of replacing the Nook Color ROM, they're booting Ubuntu from the (external, I think) sdcard.
Would it be possible to do something like this with the Gtab? If it is, maybe we could have an Android/Ubuntu dual boot?
Jim
http://nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-nexus-oneandroid/
The above is the based info on this. It looks like, basically, they run Ubuntu under chroot (in a jail).
This seems like it'd be cool, on a Gtab!
Jim
jimcpl said:
http://nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-nexus-oneandroid/
The above is the based info on this. It looks like, basically, they run Ubuntu under chroot (in a jail).
This seems like it'd be cool, on a Gtab!
Jim
Click to expand...
Click to collapse
Would it be fast like that? I used to run Android on an sd card on my old HTC Titan phone. It was slower than Molasses in winter.. Would be neat if it could be done, and was still fast.
Sprdtyf350 said:
Would it be fast like that? I used to run Android on an sd card on my old HTC Titan phone. It was slower than Molasses in winter.. Would be neat if it could be done, and was still fast.
Click to expand...
Click to collapse
Hi,
I don't know the answer to your question, but we run stuff under chroot all the time (mainly things like Apache httpd) for security reasons, and running under chroot doesn't add overhead. It's not like it's running a VM/hypervisor. Rather, chroot just isolates the app (in this case, Ubuntu) from "seeing" the rest of the system, so I think that if it could be done, the Ubuntu "instance" would run at native speed. Again, this would be more like a dual-boot configuration, rather than a VM type situation.
If you read through the 2nd link, it's kind of neat the way they did this, i.e., they got just a command line Ubuntu going first, then they used apt-get to bring in the X stuff on top of that, kind of like bootstrapping, at a little higher level. Also, similar to how the earlier versions of Windows worked, i.e., basically you'd boot to DOS (yikes !) then start Windows from there.
Jim
i want this soooooo bad.....
When I have some time, I wouldn't mind trying to get something like this working on Gtab, but at this point, I'd (we'd) need some guidance.
For example, would we need our own img file for the Gtab, or could we use the one that was linked on those sites? Those are, I guess, for Nexus One and for EVO, so the native code would be for Snapdragon. Would those work on the Gtab, which is Tegra 2?
I originally hesitated posting this in the Development forum, but maybe it should be. I don't know ...
Jim
There is an ubuntu image that runs on the external micro-sd card. You have to change the boot loader to run it. Right now you have to have an external mouse and keyboard.
http://forum.xda-developers.com/showthread.php?t=894960
It does not modify the internal storage so you can restore a boot image from Clockwork and boot back into android.
NMCBR600 said:
There is an ubuntu image that runs on the external micro-sd card. You have to change the boot loader to run it. Right now you have to have an external mouse and keyboard.
http://forum.xda-developers.com/showthread.php?t=894960
It does not modify the internal storage so you can restore a boot image from Clockwork and boot back into android.
Click to expand...
Click to collapse
Hi,
I read through some of that thread for awhile now (not too closely), but I had the impression that the Ubuntu in that thread replaced the normal Gtab ROM?
So, is the only thing that gets replaced on /sdcard the boot image? If that's the case, then it wouldn't allow a dual boot, without using CW and restoring the appropriate boot image?
Sorry, not arguing, but just trying to understand...
Jim
It uses a custom boot image to load ubuntu from the micro sd card. It will not boot android. You have to reflash the boot image to boot back into android. There is a post in that thread (#57) where a dual boot capable boot image is being asked for.
NMCBR600 said:
It uses a custom boot image to load ubuntu from the micro sd card. It will not boot android. You have to reflash the boot image to boot back into android. There is a post in that thread (#57) where a dual boot capable boot image is being asked for.
Click to expand...
Click to collapse
I think I remember that "request" in that thread ...
I guess that the nice thing about the approach at the beginning of this thread, if it could be possible, would be both runnable "images" (the Gtab/Android and the Ubuntu) would exist (but not run) simultaneously, the former on the internal SDCARD, and the latter on the external microSD card...
Jim
ext2 support?
Hi,
I've been reviewing the shell scripts that are used for this (downloaded from the link from the original NC thread), and it looks like almost everything would be ok, except:
- It looks like the ubuntu.img file is an image with an ext2 fs on it (they do a loop mount on it). I tried "busybox modprobe ext2" on my Gtab (stock TNT 3452), and it looks like it doesn't have the .so or whatever to support ext2. Does anyone know if it's possible to get ext2 support on the Gtab?
- I was hoping to at least try the mount, to see what's there, but since I can't, I'm still assuming that the ubuntu.img was compiled for the NC, so I'm still wondering if I could get it mounted, if the code in there would work? According to:
http://www.engadget.com/2010/10/28/nook-color-processor-revealed-arm-cortex-a8-based-ti-omap3621/
it's an "ARM Cortex A8", whereas the Gtab uses a Tegra 2, which I guess is an ARMV7?
Thanks,
Jim
jimcpl said:
Hi,
I've been reviewing the shell scripts that are used for this (downloaded from the link from the original NC thread), and it looks like almost everything would be ok, except:
- It looks like the ubuntu.img file is an image with an ext2 fs on it (they do a loop mount on it). I tried "busybox modprobe ext2" on my Gtab (stock TNT 3452), and it looks like it doesn't have the .so or whatever to support ext2. Does anyone know if it's possible to get ext2 support on the Gtab?
- I was hoping to at least try the mount, to see what's there, but since I can't, I'm still assuming that the ubuntu.img was compiled for the NC, so I'm still wondering if I could get it mounted, if the code in there would work? According to:
http://www.engadget.com/2010/10/28/nook-color-processor-revealed-arm-cortex-a8-based-ti-omap3621/
it's an "ARM Cortex A8", whereas the Gtab uses a Tegra 2, which I guess is an ARMV7?
Thanks,
Jim
Click to expand...
Click to collapse
if i remember correctly it's an arm 9 that shows up as a 7....
I have an LG Optimus T. Not the most ground breaking phone ever, but a heck of a deal for the money. Nonetheless, it's my phone, and I'm not really happy with the internal memory barrier I'm facing. For what it's worth, I have it rooted. I heard a way to partition your SD card (with part of it being allocated to ext3 file system) and re-flashing your phone somehow so the phone utilizes your ext3 partition on the SD card for housing applications. I heard several users in the IRC chat confirm this works well.
However, now that it's show time and I'm trying to do it, I'm a little confused. So please, be gentle, and I apologize if I'm re-hashing simple steps. I'm just trying to make sure I get what I'm supposed to do.
I'm working from this link here:
http://forum.xda-developers.com/showpost.php?p=10692249&postcount=1299
So from what I understand, the factory ROM can do fine, so I don't need to locate a custom ROM. That said, I just need to reset the phone to factory settings (thereby getting the factory ROM), run A2SD (is A2SD any different from A2SD Killer that they speak of in this post? I never heard of it), then go through the motions of the initial setup as it suggests (language choice, time zone, etc).
Then, prior to setting up my gmail account, I'm supposed to reboot to recovery. What does it mean reboot to recovery? Am I supposed to hold down the keys to do a factory reset? Is that what they mean by recovery?
I hate to ask these questions in a form of hand holding, but I just want to make sure I'm doing it right. After re-hashing this post several times and talking to 2 buddies about it without any further progress, I figured I'd just ask.
That said, can anyone help guide me in the proper direction? I'd greatly appreciate it.
Thanks!
make sure that you are looking at the right forum next time that link was for htc desire (use it only if it says its compatible for your phone)
before you start worrying about a2sd, you need a custom recovery, found here. once you flash recovery and boot into it, everything will be clear (ext, partition, flashing, etc)
for apps2sd, id suggest using ungazes data2sd (apps2sd and data2sd are basically the same thing, at least thats my understanding)
follow the steps there. if anythings unclear, post any questions and ill check back later
I did notice it was an HTC forum, but I was speaking with users who had other devices and claimed they used the same method, so I didn't think much of it. At that point I figured it was more of an Android thing vs an actual manufacturer thing.
When you speak of the custom recovery, what *exactly* does that entail? I was told Android phones have the hard factory reset that cannot be altered as long as you don't mess with /system under root terminal. That said, this phone is pretty much brand new. I have nothing on it that isn't already stored in the cloud somewhere (google contacts, gmail, work's email, etc).
What I'm trying to get at is, is a custom recovery needed only to get my phone back the way it was before I screwed with it? Or if I'm accepting to doing a hard factory reset, is that acceptable as well?
Thank you very much for the link. This seems a little more straight forward than the last one was. I'm also trying to understand the differences between handsets and Android versions here. For example, you mentioned the previous post was for HTC. It's a difficult thing for me to grasp because I come from a very heavy Linux background. If I mess with Ubuntu on one machine, then mess with Ubuntu on a top end server, then tinker with it on a laptop, it's still Ubuntu no matter what machine it's on. So it's hard for me to grasp the concept of Android acting differently on different machines (phones) and having different methods to different devices.
That said, it sounds like the link you posted to me is more of a generic "everything should work" type of scenario. After all, it's just moving /data. It would make sense that it would work that way, right? If not, please correct me, as I'd rather be wrong 1,000 times over again and be corrected than make 1 mistake and mislead someone or brick my phone.
Thanks for your response. Hopefully the recovery thing isn't too much of a hassle and I hope this ext thing can do the trick! What kind of difficulty is involved here? Is this fix, say, grandma approved? Or is that asking for a lot?
EDIT - Also, I noticed you spoke of Apps2SD. I have that installed... is that not acceptable to what I'm running? After all, it just seems to move what parts of the apps it can to the SD card. I was aiming to have the entire application base MOVED to the SD card. Is that what it does and I'm just a little confused??
i understand what you mean (how ubuntu on one machine is the same as ubuntu on another)
its the same thing with android EXCEPT that each android device is made different by the hardware (i.e. my phone is limited by the fact that its cpu is not powerful enough to run some apps; different components make up each device in contrast to lets say iphone, where each iphone is the same; my understanding is that each rom utilizes and has commands for each of these components so if they're different then youll need a rom unique for each device)
heres a general scope over recovery:
custom recovery - allows you to flash a rom, make/restore a nand backup, well it allows you to do a lot of things
stock recovery - only a hard reset (done automatically)
a hard reset wont cut it if you screw up your phone. youll need a custom recovery (which allows you to back up your entire system as a nand backup)
when you say apps2sd, i think you are talking about moving the app to the sd card in settings. thats not true apps2sd. true apps2sd moves the whole app to the sd card, giving you unlimited space to store apps (well actually you are only limited by your sd card)
if i missed anything, tell me. im multitasking right now (sorry)
Hahah, no you're doing quite well for multitasking! I understand what you mean, and it makes sense to me. I mean, after all, isn't it still the same analogy to Ubuntu? (at first I didn't think so, but now I think it may be more relevant) After all, if I'm running a dual proc 6 core system with 24gb of RAM, it'll certainly move Google Earth (aka, an app) faster than a Pentium 3 with 128mb of RAM would, even though they're both packin Ubuntu, Fedora, Debian, or whatever your flavor may be. So in theory, I suppose you can apply the same analogy from Ubuntu as you do Android. The catch is, Ubuntu (or any Linux distro for that matter) runs on old hardware great, so the gap between old computer vs super computer is less relevant than today's Android based smart phones, where 300mhz could mean whether or not you can run a certain app. Compared to real life, Ubuntu operates just as quick to me on my dual proc 6 core (12 core total) server with 24gb of RAM as it does my P4 1gb RAM box on my test bench.
Anyway, going back on topic a bit more... yeah I was thinking of the Apps2SD from the market. So I suppose the "real" Apps2SD is a true "mv -R" type of application (linux recursive move of data).
Okay, so get the market based App2SD out of my head. Gone. Done. Okay... the thing I'm still not understanding is the recovery. I mean, I'm looking at the hard factory reset as, say, a recovery "Ghost based" partition that some Windows computers often come with.
Example - Windows gets fubar'd. Reboot. F8. Recover system. And it dumps the recovery image on the main partition. Ta da! Just like it was when you bought it at Best Buy!
I mean, if I could get it back to factory, then I could just start over, right? Trying to put it into words as best I can... I was thinking of it like this.
Hard factory reset = Windows recovery image from Dell factory (back to day 1).
Nandroid custom reset = Own "self made" Clonezilla/Ghost image (customized with your stuff as a backup you made yourself)
That's what I was thinking. So that being said, am I absolutely positively required to do a custom backup? Can I not just rely on the hard factory reset to take me back to day 1 from when I got it from T-Mobile and (if I so desire) start the process over if I tank it? You see, I was told that it's nearly impossible for me to permanently brick an Android phone, as the hard reset, while inconvenient since it would wipe my stuff, would at least get me back to a bootable, functional ROM.
If I'm re-hashing unnecessary things and just need to focus on the fact I have no choice, by all means, e-slap me. Thanks for your help so far. I'm just trying to learn what I can! Your time is appreciated.
the thing is, a time may come when you cannot even boot your phone (lets say you were messing around and modding and all of a sudden you get stuck in a bootloop) and you try doing a factory reset but it doesnt work. this might be because something is corrupted. for android, a factory reset only wipes the data but does not restore anything. this is where custom recovery comes in handy. not only can custom recovery do a factory reset, it can restore a backup if your phone ever gets screwed up (unless you screw it up so much that you cant even access your recovery, then things get much more complicated). think of this backup as a system restore on windows (creating a restore point on windows is like creating a nand backup in custom recovery)
and dont worry about all the questions a few months back i never knew this myself so i understand
Well my friend, your patience is certainly appreciated. I understand a little better now. So let me throw out another analogy just to further solidify what little understanding I feel I have.
Factory reset = Windows restore point
Nandroid reset = Self made recovery image via Clonezilla/Ghost
Your point is a Windows restore point is only good as long as the system is solid. If your hard drive dies, suddenly your backed up restore point is useless. But... dump on that Clonezilla/Ghost image you have saved elsewhere and you're good to go.
That said, how should I get started? How do I make a Nand backup? Any guides you recommend? Will this back up my current apps, settings, etc?
Once done, how would I go about the actual Apps2SD method for making the SD card act as app storage? I assume it's that ungazes link you provided earlier?
Again, thanks for your help!
Figure this is where I should come in to help. You can install Amon_ra's recovery or clockworkmod onto your device (you can choose if there is both) but you should be able to do all that from a backup and restore menu in the custom recovery. You can go get the free version of rom manager and it should be able to install clock work recovery all without that much input from you, then you boot into recovery from rom manager. It shows you this simple yet amazing GUI that you never thought possible with something so small such as your android device. You are then given choices, do you want to flash a zip to mod your system such as custom roms, new keyboards, etc. Backup and restore (nandroid backup) or even mount it in USB mode which is useful if you never backed up, and didn't keep a copy of a custom rom on your SD card. (I never made that mistake of atleast the latter option. lol) So basically, the recovery is the "safemode" of android, only you don't get to access all of your stuff until you leave "safe mode"
and a bit of advice: NEVER flash anything without 50% or more battery.
It probably will atleast softbrick your device if it dies mid-flash.
oh, I see. Yeah I thought recovery was the actual PROCESS of pulling an old backup over, not so much operating in a sterile system environment such as safe mode.
About flashing, I would suspect it would best be done plugged in with AC power. I've had a laptop or two nearly die on me in my flashing days (went to the bathroom, came back, flashing red light, uh oh!) so I think I'll be good there.
So which applications do I need to get started? The problem I face is when I google something, there's no less than 600 ways to do all sorts of various tasks. So I have a hard time separating which one is best practice, which one is the old method, which one is definitely a bad idea, etc. So you say I can choose which ROM to use. Are they pre-built into whatever recovery software I need to use to get this job done? Or do I have to download them somewhere and put them on my SD card and then boot into recovery?
EDIT - hey how about this lil guy here?
http://code.google.com/p/android-roms/wiki/SPL
Came across it when I was googling for Nandroid Backup.
EDIT 2 - Or this guy. Looks to be the same step as the Nandroid step within the first link. Looks like the first link, while a bit more dated, is also a bit more thorough.
http://theunlockr.com/2010/02/06/how-to-backup-and-restore-your-android-phone/
Since you're rooted, you can run thiss https://market.android.com/details?id=com.koushikdutta.rommanager&hl=en and it will be able to install clocwork mod recovery. Then you just boot into it and whatever rom you want to use (found in the android development forum for your device) you install that zip from SD card and voila! You're golden with a new rom on your phone. It isn't completely needed though. lol
if i were you, i wouldnt use rom manager (it is known to cause problems). for now, use the recovery i posted in the second post. if you want to flash a rom, heres a list of most (if not all) roms for our phone.
as you start getting familiar things, you should start referring here
heres a general scope of things when it comes to flashing a custom rom:
1. boot into recovery
2. make a nand backup
3. you MUST wipe data/factory reset, cache, and dalvik cache. wiping the sd card is not necessary
4. flash the rom
5. boot normally (first boot can take awhile)
and remember, never flash more than one file without rebooting normally in between or else you might run into some problems
When you say wipe the dalvik, cache, etc, is that done during a factory wipe or do I need to do that in a separate step?
Edit- which rom would you suggest? I hear a lot about cm7. Thats the only one I recognize.
they are separate processes but they are found under the same category
so itll be like this:
wipe
wipe data/factory reset
wipe cache
wipe dalvik cache
wipe rotation settings
wipe battery stats
something like that (at least this is how it works for amonra recovery. for clockwordmod recovery, i believe they are categorized differently but its still the same idea)
Ahh, I gotcha. I remember reading instructions on clearing the dalvik-cache, so that's why I thought maybe I'd have to re-hash those links I found and do that in a separate step. But it sounds pretty streamlined!
Well, I'll give this a shot tonight. I'm still going back and forth on which ROM to use. I hear a lot about CM7, but I also heard of 1 or 2 users saying on CM7 they lost their Google Navigation or Google Latitude functionality, both things I utilize. I also had no idea the Opt T was supported on CM7. But then again, if it's anything like Linux distros, using one of the more popular ROMs has its benefits as those are normally the highest supported.
People weren't lying when they said stop googling and just go to XDA forums. Thanks for the help yet again, bro.
im using cm7 and both google navigation and latitude work for me. and i know that the link i gave you said optimus p500 roms, but all p500 roms work for the p509 (since they both use the same hardware). just remember not to flash any roms from any other forums, flash only from the p500 forum
glad i could help. if you need any more help, just refer to that forum or pm me (since i have the same phone as you)
Sweetnsour, I was just suggesting Rom manager to be able to flash clockwork, then he could flash amon_ra from inside clockwork. I think that's possible? It was more of a hint for a newer user. I remember being on the other side and since I don't personally own your device, I was just offering general android advice. Glad to see you corrected me though, anyway, good luck OP. Hope you enjoy your device modifications.
I come here with my tail between my legs ducking from any backlash I may get from any users here. I spent the better part of the evening Googling around, asking in IRC, and trying to get this part working.
I ran into several issues. Some of them are quite comical to me.
I Googled around, as well as utilized the links that were provided to me in this thread. I learned that Clockwork and Rom Manager are from the same dev team, but they are two separate products. Likewise, I was hearing other users confirm that Clockwork is the bees knees but that Rom Manager is kind of "ehh" with predictability and reliability.
After I ran into some road blocks I ended up asking in the IRC Android chat room. Some users in there directed me to some guides. I read through them. Of course, each one was different. So to a user like me, I have no idea which one is the better one to go with. The one guide kept talking about how I need to run a .sh script. So, of course, I download the files supplied and extract them. No .sh script. I ask in the IRC chat and I caught hell because I should read the directions more clearly. I read through them several times and got no where. Ultimately, some users in the IRC chat decided to link me to the guide they recommended. Later, I too ran into a road block there.
Moving along, I went into the XDA-Devs chat once I found myself at the next road block. There some users spoke to me about what I was trying to do. I linked to them the guides the Android users told me to use and they were wondering why I was using such old guides to do this simple task.
This is where my frustration is brewing. There are a million and one ways to do everything. There's no structure. No consistency at all. I've done a ton of reading and I still feel like I know next to nothing about doing a "simple" recovery. I know phones are different. I know ROMs are different. But holy hell. Doing "xyz" task on one Android phone vs the same task on another Android phone is as different from driving a lawnmower vs a dump truck.
At this point I installed Android SDK on my Ubuntu machine. However, "adb shell" was yielding a command not found error. It's nearly 2 am. I'm packing it up for tonight.
That said, let's back up a bit here. My goal is this. I have an LG Optimus T. I have it rooted. I would like to utilize Clockwork in order to do a recovery as Clockwork came heavily recommended by many sources I read about. Then, I would like to utilize the XDA site for a list of available ROMs for my phone and choose one of my liking.
Is this guide, right here what I should be using to get this job done?
Along with that, how exactly do I need to install SDK on Ubuntu so it works without headache?
Thank you to everybody who has been patient with helping me learn this stuff so far.
that guide works. after you flash the recovery from that guide, don't think that you are always stuck with it. you can always flash another recovery in recovery. as for sdk, do you need it to flash recovery? those commands to flash recovery can be done on the phone using a terminal emulator. (about installing sdk on ubuntu, I will check on that tmrw because I'm doing this on my phone, and over where I'm at I should be sleeping)
EDIT: and here's a list of roms for our phone http://forum.xda-developers.com/showthread.php?p=16535249
EDIT: for sdk, have you tried this?
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
Sent from my LG-P500 using XDA Premium App
Okay. I wasn't sure if it was safe to run those commands from the phone. I was tempted to but, ahh, figured I'd wait.
Now these instructions are exclusive to the Clockwork mod, correct? So if I get any other recovery (Amon Ra, for example) there will be specific instructions for that exact recovery too as well, right?
I'll give this a shot later and see where I end up. Thanks for your help!
Edit... It's a shame those commands aren't in an sh script already. Just a fun idea... What I'd add them to a blank text file and on the phone just chmod +x it and run it. Would that work??
the commands are fairly similar:
cwm (from your guide):
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
#cat /sdcard/flash_image > /system/bin/flash_image
#chmod 755 /system/bin/flash_image
#mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
#flash_image recovery /sdcard/recovery.img
#reboot recovery
amonra (from here):
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
# flash_image recovery /sdcard/recovery-RA-GNM-thunderg-1.1.0.img
# reboot recovery
after you flash either cwm or amonra, you wont have to do this again when you flash another recovery. to flash another recovery, you would just have to flash the recovery zip in recovery. these zips can be found here
Hi! I'm looking for a way to modify boot mechanism on my xoom to make it able to pick up any boot setup from SD automatically.
Currently I'm able to boot into linux console of debian installed on SD cart, but for that I must always keep a initrd snapshot in boot.img and as you understand this is not the best way of playing around with setup.
In the end I want to make it able to boot from LiveCD image made on SD card or USB drive just like you boot up from Live CD on a PC platform.
I understand that there's no such solution, so I'm looking for advices and nice articles that could help me in that.
One important thing: I don't want to keep a mini linux kernel in boot.img and then chroot to other environment, system must be as much independent as possible (in case, let's say I'll try to boot... in Windows XPE or such)
Looks like you've done some interesting things with your xoom, maybe you could post some details of what you've done so far and how you accomplished it so others could have a mess including me.
Try taking a look at the nook color development pages. The nook by default boots from SD, and they also have a dual boot option developed.
This is the same tutorial written by Wartickler at this link. Thanks for his efforts, his work is appreciated.
Here we bring minor changes to the tutorial for those of you who are facing problems accomplishing the procedures.
The Problem
Internal Memory doesn't mount as a drive like external memory does. External memory would allow you to use data recovery tools that scan for deleted files and return them to a usable state. These tools work because most operating systems don't go through and set all of those 1's and 0's to just 0's when you delete a file. Usually the operating system will just delete the reference pointer in the index that says that a file exists with such-and-such name and it's located at this position on the hard disk / memory location. There are destructive delete tools out there that will overwrite the spot of a deleted file multiple times to discourage recovery in just this manner. The issue is that data recovery tools need an actual mounted drive in order to dig deep and unearth those funny pictures of cats you so tragically deleted by accident. These newest batches of phones don't have external SDcards which are super easy to mount as drives. Internal memory mounts as MTP/PTP which is not treated as a mounted drive and cannot be scanned by these data recovery tools. But still there is a hope.....
The Process
My phone is the Samsung Galaxy s4 (GT-I9500) though I imagine this should work for ANY phone with Internal Memory. We will be using a Windows 7 machine to:
back up the entire internal memory partition to your computer as a single, massive .RAW file,
convert the .RAW file output to a VHD,
mount the VHD as a disk in Disk Manager,
scan the attached VHD volume for files that have been deleted and recover them,
The Requirements
A rooted Android phone, (try to root with a non-destructive method as this appears to protect those who must root from wiping the device data a second time),
BusyBox installed on your device,
Cygwin installed to [c:\cygwin] with pv and util-linux from the repo (at the package selection screen search for pv then util-linux and click on Default to change it to Install). Make sure to open Cygwin once to make sure that the /bin folder is created. Also, I made a folder at [c:\cygwin\samsung] to put the exported .RAW file,
Netcat (download the ZIP file and extract nc.exe to [c:\cygwin\bin]),
ADB - You can use minimal adb and fastboot which is 2MB only. Attached, find the link at the bottom of this post. (make sure adb.exe is in your path. Path is in System Properties -> Advances -> Environment Variables -> System variables -> Path and add to the end: ";C:\Program Files\Android\sdk\platform-tools" or where ever you placed your adb.exe),
USB Debugging enabled on your device,
VHD tool from the mighty M$. Put the VhdTool.exe file in [c:\cygwin\samsung],
Piriform Recuva or your favorite data recovery tool, (it appears Recuva only finds the more common file types like images, videos, etc. Those were the file types in which I was interested. If you are after more exotic file types perhaps you might share the software you used.)
A calm sense of peace and serenity that you will get your files back... :fingers-crossed:
The Work
*****Based on the number of people having trouble with this step it is now my recommendation that you choose to recover your entire memory block instead of just the data partition. In my phone's case that is mmcblk0. Please discover if yours is different.
[*]*****For identifying which block/partition you want to recover, install DiskInfo from Playstore. Open the app and click on Data (USERDATA) to see the partition name for yours. For our purpose here we are seeking to recover the userdata partition: /dev/block/mmcblk0p21
Turn on your phone
Connect the phone in ADB mode
Unlock the screen.
Open a Cygwin terminal and enter (This assumes your BusyBox installation is at [/system/bin/busybox]. It may be at [/system/xbin/busybox]):
*Remember to enter codes line-by-line. After you enter su, you have to grant permission on your mobile phone at the same time
Code:
adb forward tcp:5555 tcp:5555
adb shell
su
/system/bin/busybox nc -l -p 5555 -e /system/bin/busybox dd if=/dev/block/mmcblk0p21
Open another Cygwin terminal and enter:
Code:
adb forward tcp:5555 tcp:5555
cd /samsung
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p21.raw
[*]Depending on the size of partition it may take a while to backup.
We need to convert the .RAW file to a virtual hard drive. VhdTool.exe basically just puts a VHD footer on the end of the .RAW file. Open a Windows command prompt, go to [c:\cygwin\samsung], and type:
Code:
VhdTool.exe /convert mmcblk0p21.raw
Now we need to mount the VHD in Windows. Select the Start button-->right-click Computer-->select Manage.
Select Storage-->Disk Management.
In the menu select Action-->Attach VHD.
For Location enter [c:\cygwin\samsung\mmcblk0p21.raw] and select the OK button.
Right-click on the name (e.g. "Disk 1") to the left of the Unallocated space and select Initialize Disk.
Select the GPT (GUID Partition Table) radio button and select the OK button.
Right-click on the Unallocated space and select New Simple Volume...
In the Wizard select Next>, leave the default for the volume size, select Next>, select a drive letter (e.g. K), select Next>, MAKE SURE to select the 'Do not format this volume' radio button, select Next>, select Finish.
A box will pop up asking you to format the drive. You DO NOT want to format the drive at this time.
Right-click on the RAW space and select Format... MAKE SURE to change the File system to FAT32. Set the Allocation unit size dropdown to 'Default.' MAKE SURE that the Perform a quick format checkbox is CHECKED. You do not want to overwrite the entire new drive with all zeroes (0's) and destroy your data. Quick Format means that it will only attempt to destroy the index for the drive by establishing a new index. Without this box checked the Windows operating system will write zeroes (0's) across the entire volume, potentially destroying your data. Select the OK button.
A box will pop up saying that Formatting this volume will erase all data on it. That would be doubly true if you actually didn't check the 'Perform a quick format' checkbox. Double check that you actually did check the box and select the OK button. (Don't worry. This essentially leaves the volume in the exact same state that your phone's internal memory is living in right now: there is data on the drive...you just can't see it. It's coming back, I promise!)
Open the Piriform Recuva application. In the wizard select the 'Next >' button. Select the 'Other' radio button and select Next >. Select the 'In a specific location' radio button and enter: k:\ (assuming K is the drive letter you chose...) Select the Next > button. Select the Enable Deep Scan checkbox. This is the magical setting that finds files that have been deleted...but not really deleted. Select the Start button.
The application may take about an hour to do the 'Deep Scan.' It's time for more laps around the house! Once the application has returned its results you can choose which files to recover using the checkboxes. Select the 'Recover...' button and choose the location to which you wish to output your files.
?
Profit! :victory:
Good Luck :good:
help
M S T F said:
This is the same tutorial written by Wartickler at this link. Thanks for his efforts, his work is appreciated.
Here we bring minor changes to the tutorial for those of you who are facing problems accomplishing the procedures.
Good Luck :good:
Click to expand...
Click to collapse
You should add that the x86 version of Cygwin is needed, not the x64.
Do you also know that as of Android 4.3 this method doesn't work anymore?
yes
Lennyz1988 said:
Do you also know that as of Android 4.3 this method doesn't work anymore?
Click to expand...
Click to collapse
it works with 4.4.x and 5.1.1, it probably also works with 4.3. it's just an adb command after all.
Filoppi said:
it works with 4.4.x and 5.1.1, it probably also works with 4.3. it's just an adb command after all.
Click to expand...
Click to collapse
No its not that. As of Android 4.3 Google enabled Trim on our decives. That means when you delete a file its really gone. Not even a professional company can get it back.
I have tried the above methode and I could not get any data back. Thats when I started reading about Google enabling Trim and found out its impossible to get it back.
Did you try it on Android 4.3+?
try
Lennyz1988 said:
Do you also know that as of Android 4.3 this method doesn't work anymore?
Click to expand...
Click to collapse
Lennyz1988 said:
No its not that. As of Android 4.3 Google enabled Trim on our devices. That means when you delete a file its really gone. Not even a professional company can get it back.
I have tried the above method and I could not get any data back. Thats when I started reading about Google enabling Trim and found out its impossible to get it back.
Did you try it on Android 4.3+?
Click to expand...
Click to collapse
I have tried on my previous Samsung galaxy s3 (i9300) and my one plus one, both 64gb, i got at least 20% of the pictures back (.png, .jpg, ...), possibly even 50% since i had no idea how many i had on the device, some zip, most of .pdf and .doc and some other random stuff.
In both cases i did not manually delete the files from the phone, instead, i screwed up the partitions by deleting some system file, so after restarting, the SDcard/used data partition was empty.
i noticed though that even if my phone only had 500mb of free space available, the .raw partitions i extracted with this method were mostly empty, they only had about 10% of the data, so i guess some happened when android restarted, maybe yeah, some kind of trimming.
i think its worth trying anyway. just remember to not open any program or copy any file in the memory, as it would lower the chances to get anything back.
Filoppi said:
I have tried on my previous Samsung galaxy s3 (i9300) and my one plus one, both 64gb, i got at least 20% of the pictures back (.png, .jpg, ...), possibly even 50% since i had no idea how many i had on the device, some zip, most of .pdf and .doc and some other random stuff.
In both cases i did not manually delete the files from the phone, instead, i screwed up the partitions by deleting some system file, so after restarting, the SDcard/used data partition was empty.
i noticed though that even if my phone only had 500mb of free space available, the .raw partitions i extracted with this method were mostly empty, they only had about 10% of the data, so i guess some happened when android restarted, maybe yeah, some kind of trimming.
i think its worth trying anyway. just remember to not open any program or copy any file in the memory, as it would lower the chances to get anything back.
Click to expand...
Click to collapse
Yes but that's something different I think. Then you never deleted the files, they were there but not accessible.
If you look for example in the last 10 pages of the main thread, then no one is able to recover anything. Because it's simple not possible anymore. That's just how Trim works.
Lennyz1988 said:
Yes but that's something different I think. Then you never deleted the files, they were there but not accessible.
If you look for example in the last 10 pages of the main thread, then no one is able to recover anything. Because it's simple not possible anymore. That's just how Trim works.
Click to expand...
Click to collapse
I'm sorry for your loss.
Filoppi said:
I'm sorry for your loss.
Click to expand...
Click to collapse
What kind of response is that?
gonna try.
for those of u who want to know the blocks and partitions to recover the user data..
ls -l /dev/block/platform/*/by-name
after the adb shell will list them
127.0.0.1 5555 | pv -i 0.5 > mmcblk0p16.raw 0 B 0:00:02 [ 0 B/s]
i stuck at step 7 which is
0 B/s transfer rate
GoGopowerRanger said:
i stuck at step 7 which is
0 B/s transfer rate
Click to expand...
Click to collapse
That su is the most important part of command, if you miss it adb will not be able to transfer any data
M S T F said:
That su is the most important part of command, if you miss it adb will not be able to transfer any data
Click to expand...
Click to collapse
You should be honest with people. You should put in the op that it will only work on Android versions below 4.3. People are just getting false hope and wasting their time.
This method does NOT work anymore.
Lennyz1988 said:
You should be honest with people. You should put in the op that it will only work on Android versions below 4.3. People are just getting false hope and wasting their time.
This method does NOT work anymore.
Click to expand...
Click to collapse
This is not my method nor I have, my self said that 100% you will get what you have deleted. I have only brought minor changes to the tutorial for the sake of successful transfer of data to the pc.
Now if you feel responsible for the feeling of people, definitely I will appreciate if you find another way.
M S T F said:
This is not my method nor I have, my self said that 100% you will get what you have deleted. I have only brought minor changes to the tutorial for the sake of successful transfer of data to the pc.
Now if you feel responsible for the feeling of people, definitely I will appreciate if you find another way.
Click to expand...
Click to collapse
That's the thing. You just copy paste a tutorial that does not work. Why would you do that? I can imagine that you did not know that it would not work anymore. But now you do know. What do you hope to achieve? Raising your thanks meter? You give people false hope and you waste their time.
And about me finding another way....There is not even a professional company that can do it. It's impossible at the moment.
Lennyz1988 said:
That's the thing. You just copy paste a tutorial that does not work. Why would you do that? I can imagine that you did not know that it would not work anymore. But now you do know. What do you hope to achieve? Raising your thanks meter? You give people false hope and you waste their time.
And about me finding another way....There is not even a professional company that can do it. It's impossible at the moment.
Click to expand...
Click to collapse
I don't need thanks... why I should do.... it doesnt give me anything... I have got my own forum with its nice members.... if someone is in need of thanks, thats is you which is trying to show himself as a defender of others feeling, time, blah blah.......
I have recovered my file on a 4.4.2 android after a system crash which I had to reset the phone. if someone is in desperate need of something s/he will try anything and as far as I know trying this one doesn't harm anyone.
for you I have a recommendation, go and drink something cold and calm down!!!
Errr...
Awesome....the raw extraction worked on my S6 running Android 5.0.2. This time I tried it on a Mac and used Homebrew to install PV. Is there a way to get the entire image, even with the unused space?
Great
Thank you!
Worked on my sm-g900f
If you get nc/pv command not found , try this:
When you open cygwin terminal, start with this line: export PATH="/cygdrive/c/cygwin/bin";$PATH
The terminal should now know the location of them.
Same if you get that "adb: command not found" just type: export PATH=/cygdrive/c/XXXXX";$PATH
Just replace that XXXXX= to your location of adb.exe.
Hope it helps someone out of this ****