Related
I know Bake Snack said it was as easy as doing it thru ClockworkMod, and selecting 512mb partition, then selecting OM for swap. But for some reason I have a feeling that it's only a EXT2 partition. And I need a EXT4.. Does anyone know how to accomplish this? Anyone have any script's laying around for achieving this??? Any help would be greatly appreciated!! Thanks so much fella's for you time. I gotta hit the sheets now, but i'll check for any replies when I get up.. thank you very much...
Oh BTW: Im running windows 7, incase anyone needs to know
EDIT: Forgive me if this is supposed to be in questions...
EDIT: Also, I do know you have to upgrade to EXT4, and if thats all I gotta do then I need to know how to do that, plezzzzzz.....
well in regular linux world, you format filesystems with mkfs, just typing 'mount' into the command like should yield what file systems are mounted, what fs they are and where they are mounted. So to format your sda1, you would 'mkfs.ext4 /dev/sda1'. whether this works the same way in android its hard to say. good luck!
its actually ext 3, you can check this by running the a2sd check in terminal... pretty sure their is no way for ext 4 as of right now.
i did the a2sd using hero_overs rom and method but im not sure if it worked properly.. can anyone plz tell me how i can confirm that i have apps2sd on my phone? i followed all the steps and on the last step after i tped in 'su' in terminal then typed a2sd it showed that lod.. it said things like a2sd installed or w.e. but in the end it said swap partition not found.. so idk if it worked for me..
y2bangali said:
i did the a2sd using hero_overs rom and method but im not sure if it worked properly.. can anyone plz tell me how i can confirm that i have apps2sd on my phone? i followed all the steps and on the last step after i tped in 'su' in terminal then typed a2sd it showed that lod.. it said things like a2sd installed or w.e. but in the end it said swap partition not found.. so idk if it worked for me..
Click to expand...
Click to collapse
Swap isn't the same as a2sd, it's basically a drive-space extention of ram, not sure if android can use swap like linux can?
As far as telling if it worked, "ls -l /data" (no " ") and you should see something like "app -> /system/sd" on one of the lines.
Sent from my SPH-D700 using XDA App
y2bangali said:
i did the a2sd using hero_overs rom and method but im not sure if it worked properly.. can anyone plz tell me how i can confirm that i have apps2sd on my phone? i followed all the steps and on the last step after i tped in 'su' in terminal then typed a2sd it showed that lod.. it said things like a2sd installed or w.e. but in the end it said swap partition not found.. so idk if it worked for me..
Click to expand...
Click to collapse
When you started the pertitioning process, you chose a 512mb partition size, then you were supposed to choose "OM" for swap size which in turn means that you arent choosing a swap size. So at the end of Terminal Elu's script run, you see'ing " swap partition not found " is normal.... I know that when I installed A2sd, my terminal said the same as yours did. But I do know that it IS working cuz I got Root Explorer and found where my apps are going cuz once you download them from the Market, they dont show up in your apps drawer until you re-boot your phone.....
I just used my g1 to change to ext4 using AR recovery ... I know some dont have router their G1's or mt3g's but it worked for me
Sent from my SPH-D700 using XDA App
atkailash said:
Swap isn't the same as a2sd, it's basically a drive-space extention of ram, not sure if android can use swap like linux can?
As far as telling if it worked, "ls -l /data" (no " ") and you should see something like "app -> /system/sd" on one of the lines.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
lol can u be a bit more specific plz? do i type that in android terminal?
y2bangali said:
lol can u be a bit more specific plz? do i type that in android terminal?
Click to expand...
Click to collapse
Yes, sorry forgot to say that
Sent from my SPH-D700 using XDA App
sniperkill said:
I know Bake Snack said it was as easy as doing it thru ClockworkMod, and selecting 512mb partition, then selecting OM for swap. But for some reason I have a feeling that it's only a EXT2 partition. And I need a EXT4.. Does anyone know how to accomplish this? Anyone have any script's laying around for achieving this??? Any help would be greatly appreciated!! Thanks so much fella's for you time. I gotta hit the sheets now, but i'll check for any replies when I get up.. thank you very much...
Oh BTW: Im running windows 7, incase anyone needs to know
EDIT: Forgive me if this is supposed to be in questions...
EDIT: Also, I do know you have to upgrade to EXT4, and if thats all I gotta do then I need to know how to do that, plezzzzzz.....
Click to expand...
Click to collapse
http://aliwaqas.info/how-to-partition-sd-card-for-apps2sd-a2sd-android-complete-guide/ and you can use EASEUS Partition Master 6.5.2 Home Edition and just folow tutor and its is advised to use ext3
I cannot flash roms or kernel. It won't boot recovery!!! I have stock rooted shift. How do I make a custom recovery? And install roms and kernel
Probably the easiest way is to download ROM manager from the market. The first option in the app is flash clockworkmod. Very fast and automagic. Have fun! Happy flashing.
I have that and kernel manager. Flashed it twice after it didn't work the first time. It hangs up on the HTC boot logo after I try to boot recovery
turn off your phone
power it on while holding vol down.
does the first line say S-OFF or S-ON?
S on I didn't do nand
I've tried a few more things. I used visionary to root my phone. Was that the wrong thing? It all works. But I can't flash. Lol
thronnos said:
I've tried a few more things. I used visionary to root my phone. Was that the wrong thing? It all works. But I can't flash. Lol
Click to expand...
Click to collapse
That's just a temp root. Go into the development section and use the GUI Root and recovery tool...worked for me.
Sent from my PG06100 using XDA App
Alright, is there a way to do this without a computer
thronnos said:
Alright, is there a way to do this without a computer
Click to expand...
Click to collapse
Yeah if you want you can use terminal emulator on your phone just open it up hit su get your super user permissions then start the commands the first time I rooted I did it using adb the second time I rooted I lost my adb and just chrome to phoned all the codes from my pc to root it from my phone
Sent from my PG06100 using Tapatalk
Alright!! Thank you all who have been helping. I have only a few more questions because I'm a little slow ^_^ ok, first. From the emulator I typed Su and gave permission.... now what? I looked for the commands in development and couldn't find. I'm trying to turn s off. I don't care so much about perm or temp root right now as long as I get that annoying s on to be s off. Lmao. I need commands please!!! Assume I have no access to a computer!
Check out the development subforum. It's a sticky thread by bcnice20.
i dont need a signature
Alright I have that, now its not explained there but in order to do that via the terminal do I need to dl the framework and sdk to my phone? I do not have a running computer right now. I had a crap amd system which is officially dead. It's now all spare parts. So doing the shell on a computer isn't going to work for me :/ yes, I'm difficult. Lol
thronnos said:
Alright I have that, now its not explained there but in order to do that via the terminal do I need to dl the framework and sdk to my phone? I do not have a running computer right now. I had a crap amd system which is officially dead. It's now all spare parts. So doing the shell on a computer isn't going to work for me :/ yes, I'm difficult. Lol
Click to expand...
Click to collapse
if you search that thread, there should be an answer.
thronnos said:
Alright I have that, now its not explained there but in order to do that via the terminal do I need to dl the framework and sdk to my phone? I do not have a running computer right now. I had a crap amd system which is officially dead. It's now all spare parts. So doing the shell on a computer isn't going to work for me :/ yes, I'm difficult. Lol
Click to expand...
Click to collapse
the commands given in that thread is the exact ones you would need, but since you're using a terminal emulator in your phone, you don't need adb.
do step 1
skip step 2
do step 3,4,5 via your terminal
do step 6
extra points:
once you're perma-rooted, you can go straight to installing Rom Manager, and flash clockworkrom that way.
then reboot your phone to recovery, and do a nandroid backup.
once that's done, you're all set.
Thank you dude!!!!!!! That rocks!!! I'm at work and I'm doing it right now. This is way more important than work ^_^ anyone else addicted to Android?
thronnos said:
Thank you dude!!!!!!! That rocks!!! I'm at work and I'm doing it right now. This is way more important than work ^_^ anyone else addicted to Android?
Click to expand...
Click to collapse
+1
When the perm root method was finally developed I was at work with no access to a PC. I ended up rooting via phone terminal just because I couldn't bear to wait a couple hours until I got home.
^ Shift Faced
Could someone explain step 1 and 3 for me if I'm using android terminal emulator. I tried it but nothing happened. My device is temprooted. I download the file into the download folder. I use root explorer to extract it... where?? I tried a couple places even the root folder (Its not in SD card) then once its good how do I check the md5 from the terminal. I type Su to get permission then what? The string in the post doesn't seem to do anything no matter how I type it. Or maybe I just don't know the command. I'm fairly new to this kinda thing. :/
That's awesome. I'm feeling the same way. I don't want to wait for a computer it might be a few weeks I'm impatient now lol
Wait, I got part of it. I just need to know how to save the file to the root of the SD card and then how to check the md5sum. Once I know that I'm good to go
Sent from my PG06100 using XDA App
thronnos said:
Wait, I got part of it. I just need to know how to save the file to the root of the SD card and then how to check the md5sum. Once I know that I'm good to go
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Download root explorer and long press the file in your download folder, then back out to your sd card directory and select move. You should be able to check mdsum5 in the term app using the commands given
Sent from my PG06100 using XDA Premium App
To outline my situation, I have installed CWM to my phone, and flashed version 2.5.1.2 of Galaxy S i9000 (but the recovery boot doesn't show as CWM) on a Samsung InFuse 4G (this part I managed to find by scouring the forums) with Firmware version 2.2.1, Kernel 2.6.32.9, with Build FROYO.UCKH1. This is as far as I have gotten because I cannot seem to get a backup of my phone's ROM made. So, my question is can someone explain (without jargon, I haven't quite learned it yet) in simple steps how to resolve this issue and help me continue my way to flashing a custom ROM? I've checked and read so many other guides, but they are confusing because the steps aren't (sad to say) dumbed down for me. Here's an example of what I read:
1: dl CWM (actually had to go look this up and figure out what it was)
2: flash CWM (my phone model wasn't on the list, but after an extensive search found out that I could use the Galaxy S i9000 [supposedly])
3: boot into CWM Recovery (can't do it, for some reason it won't load on my phone.)
4: perform backup with CWM (as before, can't do it, read I could use Titanium backup but no depth was given)
5: dl a rom and place it on your sd card (this one is understood, short and to the point)
6: boot into CWM and flash rom
Unfortunately, when I start out on a new OS (already owning Windows and getting good at Linux) I tend to not even understand these so-called "Dummies Guides." I need something filled with minimal jargon that is short and sweet. Any information would be helpful
Also, I would like to know the likelihood of bricking my phone (based off of its specs) if it is possible to find out...
I'm a little bit confused here. How come you've flashed an i9000 (Galaxy S) firmware onto an Infuse? I think we can work out your backup problems though
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
DeltaOps said:
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
Click to expand...
Click to collapse
Gotcha. Sounds like the recovery hasn't flashed properly. Did you have the phone rooted before flashing the recovery?
Here is an awesome thread with video guides on just about everything you could need. Here is another. I take it you've already followed at least one of these to get the recovery flashed, so it might pay to try the 3E recovery instead and see if that works.
You may need to go right back to stock and start over. If you do, AdamOutler has got you covered right here.
I'll stay subscribed in case you need anything else, best of luck mate
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
DeltaOps said:
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
Click to expand...
Click to collapse
It may have 'fake flashed' and not worked at all. Both stock and modified recovery will say 3E, the difference is in the version numbers although I can't picture them off the top of my head. If CWM had worked, you would not be seeing 3E, you would see the typical array of CWM options. The modified 3E does not give you the same options CWM does, it just gives you the option to flash an 'unsigned' image from Recovery.
I have never had any luck with ROM Manager personally, although a lot of people swear by it. I found it especially flaky flashing recoveries to any device, very hit-and-miss. I personally prefer, and recommend, flashing recoveries manually via ADB. A little trickier, but a lot more trustworthy.
That said, try flashing recovery through RM again before taking any further steps. Flashing a recovery over a recovery won't hurt
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
DeltaOps said:
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
Click to expand...
Click to collapse
ADB is a command-line interface between your PC and your phone. You enable USB debugging and connect the phone via USB to the computer. Once you have the correct drivers installed, you can then use ADB (part of the Android SDK available for download) to send commands to your phone, as well as push and pull files. This requires full root, which you already have.
For example you can grab the recovery.img for CWN on the Infuse and tell ADB to 'flash recovery recovery.img' and actually ensure it flashes.
There are some excellent ADB tutorials floating around, this one in particular got me started. Make sure you do a bit of reading first though: the wrong command can royally screw you.
After you're familiar, you should be able to use ADB to push a recovery to your phone, whether it be unsecured 3E, or CWM.
I'll stay subscribed for any queries you may have
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
DeltaOps said:
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
Click to expand...
Click to collapse
Don't know about Linux, but ADB works through a Windows command prompt so its pretty much the same. You will need to have ADB, Fastboot plus whatever you wish to flash (recovery.img) in a 'working' directory, then run a command prompt from that directory.
You will probably need to download the recovery.img file.from XDA. It may be zipped up (they usually are).
Sent from my Galaxy Note using XDA Premium
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
DeltaOps said:
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
Click to expand...
Click to collapse
I don't think that's the correct format to pull directory structure. I'll have to read up on that one
Fastboot is another tool you can use to flash bootloaders, radios, recoveries etc through the command prompt.
Sent from my Galaxy Note using XDA Premium
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
DeltaOps said:
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
Click to expand...
Click to collapse
Yeah, you'll have to give it a target directory, I think it's like this '.\sdcard' to write them to the SD card?
Sent from my Galaxy Note using XDA Premium
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
DeltaOps said:
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
Click to expand...
Click to collapse
I'm sure that with the correct command, you will be able to pull the structure to your hard drive. I'm not sure if it's .\C:/ or not, I'll have a look when I'm on a proper rig and can do a proper search
Sent from my Galaxy Note using XDA Premium
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
DeltaOps said:
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
Click to expand...
Click to collapse
Glad you got it and glad to help. There are a hell of a lot of good people here If there's anything else you need, feel free to PM me.
Good luck buddy!
Sent from my Galaxy Note using XDA Premium
Is there perhaps any way to perform a ROM backup with ADB?
DeltaOps said:
Is there perhaps any way to perform a ROM backup with ADB?
Click to expand...
Click to collapse
Ooh good question. I don't think so, but I'm not sure. I know you can pull directories like /system/ and whatnot, but as for repackaging them into a working backup, that may be a bit more involved. I would use ADB to.push a working CWM and do it that way, but it sounds.like you're a bit better at the command-line stuff than I so you may be able to work it!
Sent from my Galaxy Note using XDA Premium
The image was provided by Mr Rusty over on the P990 thread and i asked him if we can have an update..well he gladly helped out so don't forget to thank Mr Rusty over on his Thread..
I repacked and added a script that you will just run in order to flash this CWM version..(Thanks to Russ for the script)
From his Thread:
By request a quick explanation of the difference between the two recoveries:
Usually, your recovery image will look on the external SD card for ROMs to flash, and backups to restore, and the external version here is no different. For the most part that is fine and dandy (unless you don't have an SD card I guess), however the stock O2X mounts it's internal SD card as /sdcard, which confuses ROM Manager a fair bit.
The internal version of the recovery mounts the internal storage as /sdcard as well, so ROM Manager can find backups it's made etc.
NOTE: Backups made with v5 are not compatible with earlier versions.
Click to expand...
Click to collapse
BIG Credits goes to Koush as well for his great work for innovating the CWM..
Get it Here: CWM 5.0.2.8 For P999 or from Here
Instructions on HOW to use/WHAT to do:(For Windows)
- Once you have downloaded the Package from the link Above..extract it to a Folder..
- Inside the folder all you have to do is look for the flash-recovery_xp.bat file..
- now turn your G2x OFF..
- remove the BATTERY and make sure your G2x is not connected to the PC via USB
- Press the VOLUME DOWN button together with the VOLUME UP..
- now CONNECT the USB Cable..
- If by all means Windows prompts for a new DEVICE you have to install the APX drivers from here(extract the package and manually install from this source)..
- Else if windows does not prompt OR you are already done installing the APX drivers you can now proceed on Running the flash-recovery_xp.bat by double clicking it..
- Choose 1 and Then press Enter..Wait for a few seconds till it prompts you that the FLASH was successful..IMHO you ought to wait another 5 more seconds after the prompt for not to have issues..
- After that Reboot into CWM by Pressing Power Button together with VOLUME DOWN til you see the LG Logo with waves..upon seeing that now release the buttons and wait for the CWM menu..
For Linux/Ubuntu Users:
- Download the Package
- Extract the folder somewhere
- Now turn your Phone OFF and DO NOT plug the USB cable yet..
- Now while Phone is OFF press VOLUME UP and DOWN together and now PLUG the USB cable in..keep them held together throughout the process..
- Run the Terminal and locate the Directory on where the Files are located..
- Type the ff:
Code:
chmod +x flash-recovery.sh
./flash-recovery.sh
- Once DONE you can now reboot..
FAQ:
Q: I am getting NVflash errors?
A: You might be on a BAD Cable or either way upon installing the drivers do a reboot..also DO THIS ON WINDOWS XP..on Windows 7 there are circumstances that the device is not recognized properly..also make SURE your unit is a P999 or P999DW(my unit is P999DW and touch WORKS!!) and not P990 or SU660..
Q: My device is not Recognized?
A: You have to download the APX drivers from one of the instructions above
Changelog: Github Source
Thanks and also vote for the page..
Seems the Chinese are on to this files too..lolz..
Thank you!! It flashed perfectly, no issues here.
Troy.
thegreenfamily04 said:
Thank you!! It flashed perfectly, no issues here.
Troy.
Click to expand...
Click to collapse
Glad it worked??
So internal and external mounting are all fine with this one?
Sent from my LG-P999 using xda premium
Wow thanks man. I may have to ask a out posting the CWM touch to the G2x.
Sent from my LG-P999 using xda premium
Just flashed it with no problems , when are we getting the touch CWM? Now that will look sexy
thy for your work. coming from ClockworkMod 5.0.2.0 what are the differences / improvements? could someone explain please?
thanks in advance
Just an update: I flashed a MIUI rom (Look in my sig) used the "Nullifier 2.0" (Double wipe) and flashed the current Trinity Kernel all with no issues
Phone is running GREAT now! Thank you once again
Troy.
Волк said:
Wow thanks man. I may have to ask a out posting the CWM touch to the G2x.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I was thinking the exact same thing. Seems strange to me that Koush made it for the O2x and not for us.
Im getting a nvflash error when trying to install the new clockwork.
It says check apx driver and usb cable. The drivers are already installed so Im thinking its the usb cable, but not sure.
MWBehr said:
I was thinking the exact same thing. Seems strange to me that Koush made it for the O2x and not for us.
Click to expand...
Click to collapse
the recovery's on a different partition, might make it a pain in the ass to access the touch drivers...
or he might just like the o2x more (everyone likes those Europeans more than us anymore)
Touch Recovery
I'm just gonna throw this out there, just because I wanted to try, I flashed the O2x Touch Recovery to my G2x. Everything as far as the application goes worked, touch to select, ect. The only problem is when you ask it to do something, the mounts are wrong, naturally. What I'm getting at is that both devices use cwm 5020, obviously, mounts changed. How hard would it be to decompile both versions of 5020 and apply the differences to the new touch recovery app?
p.s. for those who wonder how I flashed touch to my G2x, I just swapped out the recovery images in the one-click nvflasher, pretty simple. when you're done, put back correct file, nvflash again.
mustangtim49 said:
I'm just gonna throw this out there, just because I wanted to try, I flashed the O2x Touch Recovery to my G2x. Everything as far as the application goes worked, touch to select, ect. The only problem is when you ask it to do something, the mounts are wrong, naturally. What I'm getting at is that both devices use cwm 5020, obviously, mounts changed. How hard would it be to decompile both versions of 5020 and apply the differences to the new touch recovery app?
p.s. for those who wonder how I flashed touch to my G2x, I just swapped out the recovery images in the one-click nvflasher, pretty simple. when you're done, put back correct file, nvflash again.
Click to expand...
Click to collapse
It's all in the ram disk. Just swap out the vold.fstab in the ram disk. Recovery images are simply boot.imgs.
Interesting, because the differences are only 1 partition. And using the O2x CWM to wipe /system (iirc) would just wipe our internal SD. Ours is partition 7 theirs is partition 8, our partition 8 is the internal SD. Since the phones are 99% the same, it should be that simple. and I need to get up early... I do have one untested tool for decompiling a boot.img....
@Kairi: Can you mirror this on Dropbox? Or somewhere not blocked by my work? Wifi at home is down and I am just chewing away at my data with having to tether.
Волк said:
Interesting, because the differences are only 1 partition. And using the O2x CWM to wipe /system (iirc) would just wipe our internal SD. Ours is partition 7 theirs is partition 8, our partition 8 is the internal SD. Since the phones are 99% the same, it should be that simple. and I need to get up early... I do have one untested tool for decompiling a boot.img....
@Kairi: Can you mirror this on Dropbox? Or somewhere not blocked by my work? Wifi at home is down and I am just chewing away at my data with having to tether.
Click to expand...
Click to collapse
http://db.tt/rEpbpRfA here you go. Really interested on what you can do with it
Sent from my LG-P999 using Tapatalk
Волк said:
Interesting, because the differences are only 1 partition. And using the O2x CWM to wipe /system (iirc) would just wipe our internal SD. Ours is partition 7 theirs is partition 8, our partition 8 is the internal SD. Since the phones are 99% the same, it should be that simple. and I need to get up early... I do have one untested tool for decompiling a boot.img....
@Kairi: Can you mirror this on Dropbox? Or somewhere not blocked by my work? Wifi at home is down and I am just chewing away at my data with having to tether.
Click to expand...
Click to collapse
that might work. Id try it out myself if i didn't f up my Linux install...
Nvidia graphics got the best of me there too
Sent from my LG-P999 using Tapatalk
Works as advertised! Thanks!
works great! thanks!
So, my idea worked? I'm not at home and since I'm a collision tech by trade, my boss don't like me playing with my phone. Volk, if you read this pm me and fill me in if you can. Thanks brother.
[email protected]
I have a non-rooted Galaxy Tab 2 7.0 P3113 that was factory reset, so I'm trying to dump the data partition sector-by-sector to microSD to try to recover data.
Since there is no way to mount the internal memory as a hard drive through USB, it makes the most sense to use an aftermarket recovery which can read the sectors and write them to an image file on the microSD.
But I don't know if CWM or TWRP can do this. Obviously they can back up to microSD, but I've never heard of someone having issues with the 4gb file size limit of FAT32. That means the backups are always smaller than the full size of the internal memory!! Somehow they have a way of distinguishing used space from empty space, but the empty space is exactly what I need to copy in order to recover files.
Which brings me to the next issue-- the size of the partition images. TWRP apparently supports exFAT so that shouldn't be a problem. CWM seems to require some hacks. So does anybody know how to force TWRP to backup ALL sectors of a partition to microSD?
Edit: The DD command would also work but I don't know if it's enabled when you ADB in to a Galaxy in TWRP. I can't just try it because I lost the USB cable.
You can use Android Terminal Emulator on the phone and use the dd command providing you have Busybox installed.
Posted from my Fascinate using XDA Premium
MultipleMonomials said:
You can use Android Terminal Emulator on the phone and use the dd command providing you have Busybox installed.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
The problem is that requires rooting and downloading/installing a big app, which will overwrite a bunch of data... Right? Unless you can keep the files confined to the system partition I guess.
Just found out that TWRP can split up the backup so it can even use a FAT32 microSD. Pretty cool.
I just wish I could find out if it backs up the "empty" sectors. I emailed Team Win and they didn't reply.
I imagine that you could write a CWM zip that would copy the terminal emulator apk to the /system partition, but if I were you I would just shell out for a stock USB cord to use with ADB shell. You can find them online cheaply, and if you plan on doing any sort of rooting/customizing, you'll need one.
Posted from my Fascinate using XDA Premium
MultipleMonomials said:
I imagine that you could write a CWM zip that would copy the terminal emulator apk to the /system partition, but if I were you I would just shell out for a stock USB cord to use with ADB shell. You can find them online cheaply, and if you plan on doing any sort of rooting/customizing, you'll need one.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
Oh I ordered a cord. I just meant I couldn't try it right away.
I tried some ADB shell stuff before I lost the cord and I couldn't even get it to list partitions. They really lock it down I guess. As I understand, you do have ADB access from TWRP, but I don't know if all the commands work or if you have root access.
Edit: It turns out TWRP backs up the boot and system partition as IMG files using the DD command, but all the others are backed up as simple zip files. I guess they decided no one would want to get a raw image of the data partition. Seems strange because extracting files from raw sectors is a common method of recovering files from camera memory cards etc, so why not a tablet/phone?
http://www.icsforums.com/forum/showthread/13239
Try the adb root command.
Posted from my Fascinate using XDA Premium
MultipleMonomials said:
Try the adb root command.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
That would give root access while you're connected to the Recovery with ADB shell? Just type "root"?
So long as the device is actually rooted... Oh. Darn. I just remembered that the stock ROM has a bug that stops this from working. There's a kernel (flashed with ODIN) that fixes this for p5xxx, but it's not for 3xxx tabs. Maybe that's because they don't have the bug, though. Try it and see, but it may or may not work.
Posted from my Fascinate using XDA Premium
MultipleMonomials said:
So long as the device is actually rooted... Oh. Darn. I just remembered that the stock ROM has a bug that stops this from working. There's a kernel (flashed with ODIN) that fixes this for p5xxx, but it's not for 3xxx tabs. Maybe that's because they don't have the bug, though. Try it and see, but it may or may not work.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
Well it's not rooted to begin with.
I'd be happy to root IF I can root without writing anything to the data partition. So far that seems to be impossible.
What Android version are you using? I might be able to modify the standard root zip to use the /system partition exclusively.
Posted from my Fascinate using XDA Premium
MultipleMonomials said:
What Android version are you using? I might be able to modify the standard root zip to use the /system partition exclusively.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
Wow, that's possible? I think that would be useful for a lot of people trying to recover data.
Oh and what about the cache partition? Does the camera app store pictures temporarily there? If so that would be another source to try to recover pics from. Or do apps ever store docs there? Or is it not worth trying to preserve?
I was planning to use CF Auto Root but I asked Chainfire about it and he said that it can format the data partition if it becomes unreadable, so I didn't want to risk it.
Android 4.0.3
Kernel version 3.0.8-378347-user
[email protected] #1
Build number IML74K.P3113UEALD3
Model number GT-P3113
Well I guess this is all moot because I can't even figure out how to flash TWRP for the P3113. I downloaded an the .img file, Odin recognizes my device, and I got it into Download Mode, but I don't know how to set up the img as a tar.md5. You would think whoever made that .img would have provided instructions on flashing it, or just uploaded it as a tar.md5 since that's what you need. That's something that really annoys me about the Android community-- folks assume everybody knows what they're doing.
But the worst is all the threads where people ask how to flash TWRP to a Galaxy Tab 2 7.0 with Odin, and the replies are all "Just use CWM".
I found a download for the TWRP 2.2 for some Galaxy phone but I can't even examine the format of the tar.md5 because the freaking download site requires registration. Even if I duplicated the format, no idea if it would work. http://forum.xda-developers.com/showthread.php?p=30694404
I think all you need to do is rename the file to "recovery. img" and use 7-zip to put it inside a tar archive, then flash the tar with ODIN.
Posted from my Galaxy Tab 2 with CM10.1
MultipleMonomials said:
I think all you need to do is rename the file to "recovery. img" and use 7-zip to put it inside a tar archive, then flash the tar with ODIN.
Posted from my Galaxy Tab 2 with CM10.1
Click to expand...
Click to collapse
Apparently it's not that simple. Somehow you have to integrate an MD5 checksum with Linux console commands http://androidadn.com/2012/09/how-to-convert-img-files-to-tar-md5-to-do-a-flash-with-odin3/
Edit: Better thread http://forum.xda-developers.com/showthread.php?t=1484304
This is the IMG file I'm talking about http://rootzwiki.com/topic/27140-recoverytouchtwrp211galaxy-tab-2-7-and-10662012/
Edit: I do have a Macbook running 10.6 Snow Leopard so I think this might work http://www.macupdate.com/app/mac/14503/gui-tar
Edit: It can create a .tar but I don't know how to turn it into a tar.md5
Also, I was reading about Heimdall. Anybody know if it will work with just the .img file? http://www.thepowerbase.com/2012/04/slay-odin-with-the-mighty-heimdall/
Yeah, if you can get Heimdall running, you should be able to flash TWRP with that.
Posted from my Fascinate using XDA Premium
---------- Post added at 07:01 AM ---------- Previous post was at 06:58 AM ----------
I will warn you, however, that I think that by default TWRP backs up to /sdcard, which is located in /data/media, so make sure to switch that.
Posted from my Fascinate using XDA Premium
MultipleMonomials said:
Yeah, if you can get Heimdall running, you should be able to flash TWRP with that.
Posted from my Fascinate using XDA Premium
---------- Post added at 07:01 AM ---------- Previous post was at 06:58 AM ----------
I will warn you, however, that I think that by default TWRP backs up to /sdcard, which is located in /data/media, so make sure to switch that.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
There's now a TWRP for the Tab 2 7.0! http://forum.xda-developers.com/showthread.php?p=38809460&posted=1#post38809460
I installed TWRP and now I'm trying to use ADB to see if I have root access. But Windows fails to install drivers for the tablet while in recovery mode
Well I've tried every driver I can find but I can't install the tablet in TWRP Recovery mode. Windows sees it as "GT-P3113"
Wait... Can't I load a rooted system image onto the tablet from Odin? Wouldn't that leave the other partitions unaffected?