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...
I'm thinking of creating a small archive of files, that when extracted to the SD card root, and applied, will root the phone and apply a firmware in only three steps.
It will only contain four files - the RC29 DREAIMG.nbh file necessary for downgrading, an update.zip that contains the latest SPL and Radio, the latest Cyanogen Recovery image, and a simple script that applies root, SPL/Radio, and your favorite firmware.
I'm not sure if it will work, but constructive criticism and ideas are welcome.
_______________________________________
First method: Root from SD card
This method puts all the necessary files on an SD card, and does not require a computer after that.
Basically, in a zip file, you have the RC29 DREAIMG.nbh, update.zip, and root script.
You extract this to the root of a FAT32-formatted SD card.
You reboot with camera+power, apply the DREAIMG.nbh, reboot.
Once the phone is booted, type in "sh /sdcard/root.sh".
From the exposed root terminal, it will begin the following:
Write the Cyanogen recovery image to flash, move image to system/recovery.img, remove image file
Place commands in /cache for recovery to apply the radio/spl combo package and if it exists, a custom firmware, in the correct order
reboot recovery, performing the above tasks automatically.
Benefits include:
- No telnet app required, not opening up a telnetd, more secure
- Only one command to enter
- No(?) risk on flashing the Hero-compatible radio/SPL out of order and bricking that way, as both are flashed at the same time
- Automates several of the processes in rooting, allowing for a quicker root
- Can be placed on a special "rootkit" sdcard, and used to quickly root your friend's phone in a matter of minutes, anywhere
_______________________________________
Second method: Root from PC
Another method I thought of uses no manual copying to the sdcard, but requires a PC with fastboot(?) and adb.
First, it pushes the RC29 DREAIMG.nbh to the sdcard, and issues a reboot to bootloader.
You press a few keys to write the image, and reboot.
--OR--
First, it pushes an update.zip containing the update just before T-Mobile patched the root kernel exploit, then it puts the commands to flash it and reboots into recovery. After that flashes, it reboots again.
From this point on, it's all automatic.
The script waits for the device to be ready, and adb install's the auto-root exploit apk, and launches the intent through adb shell am start [...]
At this point, the WiFi settings are probably not capable of downloading the Cyan recovery in the case of those of us without data plans, so it will need to be pushed.
Once the autoroot apk flashes the recovery, we must write parameters to flash the radio/spl combo package, and the custom firmware (if applicable), to /cache, and reboot.
At this point, the radio, SPL, and firmware should be pushed and written, so the script exits.
_______________________________________
If this sounds stupid, doesn't make sense, will auto-brick your phones, start global thermonuclear war, make all random numbers generated by your phone divisible by three, cause your meticulously placed lineup of G1 dominoes to collapse prematurely, or boot up the LHC and wind up creating a black hole, I am terribly sorry, but it's an idea I had at 2 in the morning, and it took me this time to research some things and write this post. It's about 5:30 AM now.
This is only an experimental concept. Some things might not be completely thought out. I'm tired, and hungry. I may create a proof-of-concept implementation of this, if I knew a bit more about the syntax of describing intents to launch in 'am', or the command syntax of the package:/META-INF/com/google/android/update-script file.
dont forget that for root from SDcard, EU users need a goldcard, so its still not that easy..
even for insta root from PC, you still need to downgrade, and for that we'll need a goldcard.
why not just use 1click root?
First you have one click root which does give you access to recovery with security off so possible to somehow go from there instead of downgrading and all that hassle. I personally to do not care to see the advancement of this app for the simple fact that there are already a wave of people that can not read and expect hand holding every second of the way and you want to make it even easier to confundle their minds.............are you nuts....
I already have a rooting sdcard for rooting other people's phone that contains one click recovery flasher, cyan 4.04 and the hard spl and it takes me 10 mins to do it just cause off the first boot up takes so long
also you cant have your pc reading the sdcard at the same time that the phone is
The concept is good but...theres many complications to have it done automatically.
I sure would like to see something like this. I have a G1 that I rooted the long way and a MT3G rooted with the one click method. I have enough knowledge to follow instructions and read, I partitioned my own card, so the G1 was doable. I dont have the time or the knowledge to go the long route with the MyTouch gold card ADB route and would love to be able to flash Hero ROMS when I get the bug. I have Cyan's latest on the MT now and its awesome like all his stuff but I would have played with Drizzy's ROMs. For someone like me with a little ability but far less than most people on here, something like this would be the bomb!
not sure if its possible or anything, but there should be some way for the script to check if the phone has a pvt board or not, and if not, it prevents the new spl from being flashed, should reduce noob bricks.
Leave root the way it is I think the harder it is to root your phone the less peaple are going to do it. I spent alot of time reading before I rooted, not so much to learn how to do it, but to decide if I wanted to make the jump. During this reading process I learned the ways of XDA, use search, where to place the right questions and where NOT to and finally read first then ask. With an autonatic root I would have loaded it then freaked out if something went wrong and started posting root questions all over the place. Leave well enough alone... Learning to root give you the right to pursue other adventures.
maybeoneday said:
Leave root the way it is I think the harder it is to root your phone the less peaple are going to do it.
Click to expand...
Click to collapse
Frankly, I didn't root my phone to feel special, so I don't see any benefit whatsoever in less people doing it.
I don't think this will work though. There's too many variables. As described it will only root US phones. UK phones would need RC7, so you'd have to include both and check if the current OS is CRC1 or CRC37 (or respective older/newer versions). But European phones outside the UK (like my German G1) will be on CRC37 too, and those won't take RC7 without a goldcard, so you'd have to automate goldcard creation as well. I'm sure the complications don't end here.
Also, shoving Haykuro's SPL onto inexperienced/unsuspecting/ignorant users' devices is just begging for trouble. Just use HardSPL - the rooting kit won't be able to run Hero-ROMs right away, but at least that won't brick the phone if flashing some rom downgrades the radio. (E.g., I know some official updates do that.)
1 click root is so simple and idiot proof (and im a total panzy noob lol)
i don t think there is any simpler way to do this lol
Frenchtom, nothing is idiot proof, have you been over to the q and a section, if there is a way to do something and good instructions, it will get screwed up cause of people not taking the time to read the complete directions and then read them twice to make sure they comprehend them
Okay, thanks for your input, everybody.
I did know about 1-click root, however I thought that depended on a kernel vulnerability that was already patched in the OTAs. I was looking at a more universal(ish) method, and I did not know about the "goldcard" issue. I did know that UK phones would need RC9, but I failed to include that as I really just wanted to get to bed.
Also, I don't think that root is anything "special", i.e. some sort of elitist egotist symbol that says "I haz root fone and I better than u". Seriously, more people should be allowed to use the more advanced features of their device at their own choosing, knowing that there are risks involved.
People who walk up to someone, say "I got a root phone", shows off some massive demo of awesomeness (i.e. Hero), and doesn't teach others to root the G1 themselves (or worse, charges for instructions that could be found free here) are really the antithesis of an open-minded community of developers adding more features as they feel, for what little donation money they get and the credit of doing something cool for other G1 users.
I do however agree that pushing features that can potentially insta-kill the device on the average person and their grandma, people that wouldn't know what the benefits of root are, and people who would never even have known that their G1 ran Linux (or what Linux is, for that matter), is just asking for trouble. A fair balance between educating people about the phone's internals and making easy-to-install root packages and stuff should be kept.
I learned a lot about Windows Mobile and embedded software when I first flashed a custom ROM to my HTC Wizard years ago. And I actually had a fear that if any small detail were left out, or if I breathed on the phone the wrong way, the flash would fail, white-screen, and brick out.
The G1 is no different, even though the flashing process has come a long way, we still have an IPL, SPL, bootloader mode, many different variations, board revisions, regional changes and operator customizations/lockdowns (I had a Cingular 8125 G3 btw), and many versions of Consumer, Engineering, and HardSPL that have to be treated very, very carefully, just like on the Wiz.
Anyway, anyone's free to try and build a better mousetra--- err, rootkit using my ideas. And thanks plenty to the dedicated developers here, the more enlightened users for helping me find out why this wouldn't work, all the users, without whom, we wouldn't have a reason to develop, and the 17%-or-so of you that dislike my idea.
When I learn a bit more, I might get into making something useful for Android.
repack dreamimg.nbh with everything, so one just has to flash the one image
Oh I am not saying that I think I am special just cause I have a rooted phone, I am also a person that is on here always trying to help walk someone through any issues that may arise,just saying making easier for people to break something because they did not read the instructions is quite common and think that it should take a little bit of work so that you learn in the process
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
If you are going to flash and ICS ROM after this tool please make sure to first install a GB then ICS otherwise your SD card will not be accessible. I am trying to find a fix but it has been illusive. This statement will be removed once a fix has been found and OP updated.
Now with CWM Touch!
This method uses NVFLASH to recreate all partitions and formats them, thereby getting rid of the file allocation pointers and hence renders data inaccessible without effort.
Note: I have never seen a file come back to life or its data affect other files without effort on the users part or a temporary glitch once the partitions and pointers have been overwritten. Please post a reply with evidence if you have seen it.
Benefits:
The contents of the zip file can be used to super clean G2X before a new ROM flash. This tool recreates all the partitions in the phone so wipes the pointers to all files (everything). The method it employes has existed from before. The files here will stop short of pushing a ROM, so that you can push your favorite ROM.
Prerequisites:
G2X (Will not work on O2X due to different partition table)
Desire to have a clean install of your favorite ROM
Backup your data
*** WARNING ***
This tool will wipe both phone internal memory and internal SD card. External SD card content is safe.
Don't say you haven't been warned!
What to do:
Download the attached Zip file.
Take out the battery (assuming you have backed up your data on external SD card, computer or elsewhere), connect the device via USB while holding VOL+ and VOL- together. Don't let go of the volume buttons until the device is recognized.
(I typically leave Device Manager open to see when it shows up in the list under "USB Controllers").
Launch flash.bat, sit back and wait until the process finishes (generally a good idea to open a command prompt, CD to the directory and then run the file).
Unplug, put battery in, reboot into CWM recovery (pushed by this tool) by holding VOL- first, then pressing and holding POWER).
Flash your favorite ROM.
Enjoy!
I made this package because I could not get the bluetooth to work with G2x GB 2.3.3 (and below). The issue was a disconnect problem where both the phone and headset would still think they were connected but in audio would not be routed for a call or media. After this procedure my phone has not had an issue for almost 3 weeks now. I have tried it with two ROMs and 3 different headsets without any issues.
I guess I will not toss this phone after all .
Putting it out there in the hope that it may help others solve some of their issues as well. I suspect bad data stays in places not touched by other methods.
Your comments are most welcome.
[Update]
Klathmon has made an newer version with CWM 5.0.2.8. RP by Klathmon can be found here:
http://forum.xda-developers.com/showpost.php?p=24768294&postcount=66
I have tested the windows version but linux one is untested. Use at your own risk.
[Update]
Now with CWM Touch!
Thanks to everyone who has contributed on this thread with a drive to positive change! You work/comments/suggestions are very much appreciated.
References:
http://forum.xda-developers.com/showthread.php?t=1248644. This link was the inspiration for the current work.
Link to CWM Touch development thread. I took the image posted there: http://rootzwiki.com/topic/22984-recovery-touch-enabled-cwm-5813/
[EDIT] The zip file should be fixed now. Darn work machine does something to the upload.
was just about to flash the new hellfire rom and saw this tool! will try it out and see how things go
edit: yeah corrupt zip on my end too.
The zip file seems to be corrupt. Could you re-upload plz
worked great on my end, no problems.
khanggle said:
worked great on my end, no problems.
Click to expand...
Click to collapse
The real test is how stable your ROM would stay with this method to wipe than any of the other methods.
I guess only time will tell .
wow this method really blaze hellfire much thanks to your( you) & (rom dev)
Ohh I like this. Thank you for sharing .
This thing is faster than nullifier, and I especially like how you don't need to be in CWM to use it. It just seems like doing it in "update mode" would allow better manipulation of the phone's internals.
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
He states in OP that it doesn't write anything, therefor doesn't "nullify". It formats and partitions.
dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA
mansa_noob said:
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.
MWBehr said:
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.
Click to expand...
Click to collapse
Done. OP updated to reflect. Thanks for clarifying that. It was not my intention to state that this tool does anything any other does, or does not.
I think we are all trying to do the same thing... get rid of the issues when swapping ROMs like _____. I can't seem to think of a good analogy here .
thanks for clarifying the OP, that makes much more sense
and no i wasnt trying to say you were reinenting the wheel, just trying to understand what your tool is actually doing
and also i do understand that it would take effort to get data off any type of storage device once the partition has been erased. i deal with wiping hard drives in a data center all the time. we use a DOD wipe tool that writes 1s and 0s over a drive a minimum of three full times to eradicate the data
but with this tool doing it outside of CWM, it sounds like it may do a better job of it
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).
dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
I was thinking the same thing but seems easy enough .. add the cwm img to the dir and edit the .cfg file. Hopefully that should get the new CWM flashed
So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA
mansa_noob said:
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).
Click to expand...
Click to collapse
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
PL0X_Kleiner said:
So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
i think it would be pointless unless you are super paranoid
dodgefan67 said:
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
i think it would be pointless unless you are super paranoid
Click to expand...
Click to collapse
Nobody is twisting any arms here... Use it if you want to, don't if you don't want to.
I saw benefit so posted so that others may benefit as well.
Sent from my LG-P999 using XDA
Ok so question, why are you killing all the data on your internal SD card? Why not just the individual partitions that the phone uses? Your destroying data that don't need to be destroyed before flashing a rom...
Sent from my LG-P999 using xda premium
It does not have to be destroyed. I just haven't had a chance to test without recreating emmc yet.
Next step. Likely tomorrow. Would like to test before release.
Sent from my LG-P999 using XDA
[edit] BTW, I do want to restate that there is some data that needs to be destroyed which is not being taken care of by other methods. I don't believe it is in the emmc, but rather it resides in one of the other partitions. Most methods out there are only working in the /data, /system and /cache domain.
My original problem (bluetooth disconnect) which happens to be a problem for some in the community even now was only completely fixed by this method.
So I apologize if Im posting in the wrong spot but I noticed yall are still working on the F6...so I figured this made sense...
I thought I knew exactly what I wasdoing but did not....I was lucky enough to find patience enough to read up before flashing...I see the threads posted on how to root, backup, and restore this phone...but all those threads explain it using so0ftware other than I have... Since I made some moves before truly knowing what I was doing...I'd like to just stick wiith what i got for the moment and see if yall, as the experts can guide me down the runway...
Heres What I have so far:
1. I DO have root access
2. I DO have SuperSU and it seems to be working in the sense that it keeps logs...but sometimes it gives me a binary error. (I have NOT et converted SuperSU into a system app...bc im unclear if its necessary after reading a few different threads)
3. I DO have Root Browser' which I use to shuffle things around. (I DO have the /system and /data folders relocated on my external SD)
4. I DO have Titanium Backup which I used to BU my USER APPS/SYSTEM DATA.
5. I DO have Flashify which I also used to BU my STOCK RECOVERY/KERNEL (I cant seem to figure out where that recovery is being default stored though...Ive been searching high and low.
NOTE: Although im happy I have made it this far...I dont wanna go any further until I know exactly what im doing. I fear that I have missed something small. Something that would be a no brainer to you experts.
I'm unclear of storage requirements...I BELIEVE that I must store all my rooted tools on the external bc the goal is to wipe everything NOT on ext SD.
What I THINK I know is that hypothetically since im backed up...or when im 100% certain everything is....I can just click REBOOT TO RECOVERY MODE under the menu using Titanium.
IF I happen to be correct up to that point....I think my next move is using Titanium to put back the things ive stored on my SD.
In my mind that leaves me with the same ROM...but without the fluff...and now the ability to save to ext SD.....
If I underestand right....currently there are no MOD upgrades available due to difficulty of unlocking the bootlag....or something that sounds likethat...
I have ZERO experience with any of this....I hope what I just shared is at least in the ballpark of the right direction..
THANK YOU for any and all help!
I
On a mission to take my LGF6 and make a man outta it!
On a mission to take my LGF6 and make a man outta it!
No one can help me? Am i just completely way off..or am i posting wrong?
On a mission to take my LGF6 and make a man outta it!