Philz AdvCWM v6.57.9 CWM v6.0.5.1 for GT-N8013 - Galaxy Note 10.1 Original Development

Philz AdvCWM v6.57.9 CWM v6.0.5.1 for GT-N8013 - Galaxy Note 10.1 Original Development

I no longer own a note 10 n8013 and as such will be shutting down this thread.
What resources I have will remain in place however.
See the devhost link in my signature.
okay to keep this quick and simple
this is my most recent compile of philz for galaxy note gt-n8013.
source, cm11 https://github.com/CyanogenMod
including vendor_smdk4412-common
including hardware_samsung
including device_samsung_smdk4412-common
including device_samsung_n80xx-common
and any device tree with modification or not will do. as to specifics i used graphics..c and keys and default_recovery_keys.c
from philz source https://github.com/PhilZ-cwm6/philz_touch_cwm6
and kernel source GT-N8000_JB_Opensource_Update7.zip version XXCMC5,MD1 from http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=gt-n8000 because kk source has mental problems :silly:
anyway devhost link http://d-h.st/users/moonbutt74/?fld_id=39850#files
special thanks to @jika23 for testing/feedback
m

Hi, would you be able to compile one for n8000? N8000 hasn't been updated for a while.
Thank u in advance...

stingbandel said:
Hi, would you be able to compile one for n8000? N8000 hasn't been updated for a while.
Thank u in advance...
Click to expand...
Click to collapse
I don't think it will be a problem, if you would boot to recovery, connect through abd shell and run;
parted /dev/block/mmcblk0
and then at parted prompt;
(parted) print all
and post output here.
I have a few projects in front of me so you're help getting that information would be appreciated.
m

Ok will do. I will post asap. Thanks once again...

Hi, I try to use the adb but it says there is no command parted. I boot to philz recovery, plug in my note then runthe adb. When I type the command you write, it says no parted command. Could you guide me more? Maybe I am missing something. Thank you so much

stingbandel said:
Hi, I try to use the adb but it says there is no command parted. I boot to philz recovery, plug in my note then runthe adb. When I type the command you write, it says no parted command. Could you guide me more? Maybe I am missing something. Thank you so much
Click to expand...
Click to collapse
ahh, okay
in linux terminal run
adb shell
wait for the server to start and connect then you will see your command prompt.
either $
or #
if it's the first, type su and press enter, if you have rooted device and or your recovery is correct you will gain a root prompt/shell
#
now type
parted /dev/block/mmcblk0
if parted is built into recovery it will take a second or two then return with the following prompt
(parted)
at that prompt type
print all
it will return with the information i need. select the entire output , copy it and past it into your next post.
if parted is not present, then i need you to out by mmcblk0# what partitions are /boot /recovery /system /cache /data /efs

Related

[Q]How to fsck /data or /system?

Does anybody know of a way to fsck the system or data partitions? I've run into a few times where I had data errors on /data, and the only way I could think of to fix them was to do a backup and restore. I was worried about losing data during the backup process, as the filesystem was already questionable.
I have e2fsck in my rom, but I can't run it from a normal shell as the filesystems are already mounted. Is there a way to make a rom automatically check and repair the filesystems on boot, and if so, how can I control the options it passes to fsck? Are there other ways to get to an unmounted system or data partition? Does clockworkmod have any kind of shell or fsck utilities built in? Are there other recovery programs that may have something like that?

You should be able to boot into CWM, unmount the partitions, connect with adb and run it from there. At least if your version of CWM has fsck in it.
Sent from my SPH-D700 using xda premium

You should be able to do it while booted into recovery through ADB.
Boot to recovery
connect usb cable to PC
run `adb shell`
Code:
unmount /data
unmount /system
fsck /dev/block/stl9
fsck /dev/block/stl10
syntax for above commands needs to be checked.

toadlife said:
You should be able to do it while booted into recovery through ADB.
Boot to recovery
connect usb cable to PC
run `adb shell`
Code:
unmount /data
unmount /system
fsck /dev/block/stl9
fsck /dev/block/stl10
syntax for above commands needs to be checked.
Click to expand...
Click to collapse
Just tried this out myself. Here's the correct syntax for the fsck command:
Code:
e2fsck -fv /dev/block/stl10
EDIT: Forgot to mention also that unmount should actually be umount. Or you could just use the CWR menus to unmount partitions.

zman0900 said:
Just tried this out myself. Here's the correct syntax for the fsck command:
Code:
e2fsck -fv /dev/block/stl10
Click to expand...
Click to collapse
How bout mtd?
sent from my always aosp epic

Please consider posting questions in Q&A next time. Thank you.

Sorry for the "newbie spam"! But that worked perfectly - I didn't realize that adb shell worked when booted from cwm. That's exactly what I was looking for.

zman0900 said:
Just tried this out myself. Here's the correct syntax for the fsck command:
Code:
e2fsck -fv /dev/block/stl10
EDIT: Forgot to mention also that unmount should actually be umount. Or you could just use the CWR menus to unmount partitions.
Click to expand...
Click to collapse
Thanks for this, this is why i love xda!
I have e2fsck in my /bin
On a samsung galaxy s2 i9100
How do i identify my /system & /data blocks
I cant remember how to find out!
So mine would be
e2fsck -fv /dev/block/????
Thanks

Colliebudz said:
Thanks for this, this is why i love xda!
I have e2fsck in my /bin
On a samsung galaxy s2 i9100
How do i identify my /system & /data blocks
I cant remember how to find out!
So mine would be
e2fsck -fv /dev/block/????
Thanks
Click to expand...
Click to collapse
If you run mount with no arguments, it will show a list of mounted partitions like "xxx on /system".

Colliebudz said:
Thanks for this, this is why i love xda!
I have e2fsck in my /bin
On a samsung galaxy s2 i9100
How do i identify my /system & /data blocks
I cant remember how to find out!
So mine would be
e2fsck -fv /dev/block/????
Thanks
Click to expand...
Click to collapse
Better to do /dev/block/platform/(your processor)/by-name/xxxx. Less chance of error

Colliebudz said:
Thanks for this, this is why i love xda!
I have e2fsck in my /bin
On a samsung galaxy s2 i9100
How do i identify my /system & /data blocks
I cant remember how to find out!
So mine would be
e2fsck -fv /dev/block/????
Thanks
Click to expand...
Click to collapse
the easiest was to find what /system and /data mount points actually are
cat /etc/fstab
to see a list of mount points.

toadlife said:
You should be able to do it while booted into recovery through ADB.
Boot to recovery
connect usb cable to PC
run `adb shell`
Code:
unmount /data
unmount /system
fsck /dev/block/stl9
fsck /dev/block/stl10
syntax for above commands needs to be checked.
Click to expand...
Click to collapse
How do I get the Moto X in Recovery mode to accept the adb command?
Because when I put in Recovery (Android Robot lying down) mode, the command adb and fastboot are not recognized.

rod.gui said:
How do I get the Moto X in Recovery mode to accept the adb command?
Because when I put in Recovery (Android Robot lying down) mode, the command adb and fastboot are not recognized.
Click to expand...
Click to collapse
Flash a custom recovery first. (CWM/TWRP)
Sent from Motorola Photon Q 4G LTE @ CM11

My phone is Huawei G525. It doesn't have CWM or any custom stuff, just rooted.
My problem is that it reports an imagic flagged inode and it recommends to fsck the partition (/system). The logs are saved in sdcard folder.
I can use adb and fastboot, but fastboot shell doesn't work and /system is mounted when i can use adb.
Is there any solution for me to run e2fsck on /system partition?
Or is there the case to worry about that error? The phone works fine...no random reboots, no crashes, no force closes.
Another thing...I've tried to make a romdump and system archive is damaged. Cannot be opened even with 7-zip.

mandgeo said:
My phone is Huawei G525. It doesn't have CWM or any custom stuff, just rooted.
My problem is that it reports an imagic flagged inode and it recommends to fsck the partition (/system). The logs are saved in sdcard folder.
I can use adb and fastboot, but fastboot shell doesn't work and /system is mounted when i can use adb.
Is there any solution for me to run e2fsck on /system partition?
Or is there the case to worry about that error? The phone works fine...no random reboots, no crashes, no force closes.
Another thing...I've tried to make a romdump and system archive is damaged. Cannot be opened even with 7-zip.
Click to expand...
Click to collapse
G525 DOES have CWM recovery available, find and install one so that you can fsck from recovery using adb.
Sent from Google Nexus 4 @ CM11

AndyYan said:
G525 DOES have CWM recovery available, find and install one so that you can fsck from recovery using adb.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
As far as I understand from here... http://bbs.dospy.com/thread-16432606-1-823-1.html , the bootloader needs to be unlocked. I've submitted for an update code and i'll wait. The chinese guy talks about U8950, but there are five different types. I've selected the first one, U8950-1. Maybe i'm lucky.
I've also tried to boot directly into the recovery found here... http://www.needrom.com/mobile/huawei-g525-u00/ , but that command is not allowed, maybe because the bootloader is locked. That was the only recovery i found that seems to be in english.
I'll try the same procedure to boot into recovery (fastboot boot recovery.img) because i don't want to mess things more that they are. I didn't found any tutorial in english and google translate is confusing.
Thanks!
LE. Does anybody know if Huawei rewrites the custom recovery if it's not the stock one.

mandgeo said:
As far as I understand from here... http://bbs.dospy.com/thread-16432606-1-823-1.html , the bootloader needs to be unlocked. I've submitted for an update code and i'll wait. The chinese guy talks about U8950, but there are five different types. I've selected the first one, U8950-1. Maybe i'm lucky.
I've also tried to boot directly into the recovery found here... http://www.needrom.com/mobile/huawei-g525-u00/ , but that command is not allowed, maybe because the bootloader is locked. That was the only recovery i found that seems to be in english.
I'll try the same procedure to boot into recovery (fastboot boot recovery.img) because i don't want to mess things more that they are. I didn't found any tutorial in english and google translate is confusing.
Thanks!
LE. Does anybody know if Huawei rewrites the custom recovery if it's not the stock one.
Click to expand...
Click to collapse
Well, you know this forum is dedicated for discussion about Samsung Epic 4G, not Huawei G525... But to help you out I might be able to dig in a bit more later this week when I have time. I'm a Chinese myself and can (hopefully) understand these procedures.
Sent from Google Nexus 4 @ CM11

AndyYan said:
Well, you know this forum is dedicated for discussion about Samsung Epic 4G, not Huawei G525... But to help you out I might be able to dig in a bit more later this week when I have time. I'm a Chinese myself and can (hopefully) understand these procedures.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
My phone is a Note 2 LTE N7105 - I realise not the same as this thread, but this is the only thread I have found that is discussing this. My /data partition needs an fsck, however, while I can adb to the phone when it is booted, I can't when it is in recovery.
I have TWRP 2.7.1.0 installed, and everything else works fine. When the phone is booted, I get the GT-N7105 driver appearing in portable devices in device manager, but when recovery is booted, I just get t0lte in "other devices".
Seems like the Samsung USB driver only works when the phone is properly booted, and doesn't match when booted to recovery.
Any ideas how to work around this?

paulkoan said:
My phone is a Note 2 LTE N7105 - I realise not the same as this thread, but this is the only thread I have found that is discussing this. My /data partition needs an fsck, however, while I can adb to the phone when it is booted, I can't when it is in recovery.
I have TWRP 2.7.1.0 installed, and everything else works fine. When the phone is booted, I get the GT-N7105 driver appearing in portable devices in device manager, but when recovery is booted, I just get t0lte in "other devices".
Seems like the Samsung USB driver only works when the phone is properly booted, and doesn't match when booted to recovery.
Any ideas how to work around this?
Click to expand...
Click to collapse
Yes, the workaround is to not use stupid Windows.
Works fine on linux.

run terminal app:
su
touch /forcefsck
Then reboot. It might depend on your ROM, but give it a go.

[Q] HELP - I have been reading all over XDA and I'm still bricked . . .

Ok, comparatively speaking, I'm a noob. I have successfully rooted and installed custom ROMs on a few devices, but my original Kindle Fire is giving me trouble. Despite being a noob, I'm fairly well versed having read all the guides. I have also been reading the forums for weeks and I can't seem to unbrick my Fire. I have read countless threads from people with similar problems or some of the same problems, but for one reason or another, their eventual solution won't work for me. Here is my sitch:
successfully rooted with KFU
successfully flashed firefirefire bootloader and TWRP recovery
When I tried to flash a CyanogenMod ROM I was getting stuck on the bootanimation. I tried to flash the boot.img from within the ROM .zip and I was still getting stuck on the bootanimation.
Long story short - In trying to fix this I wiped pretty much everything.
I made my own factory cable and was able to get my boot loader and recovery back on, but I still have no ROM.
firefirefire works correctly again and I can get into TWRP recovery without a problem
However, once in TWRP, I can't mount USB. The correct boxes are checked and I get:
E:unable to mount storage
E:unable to mount /sdcard
My 64bit Vista PC recognizes the Kindle in the device manager as android phone/adb composite device, but that is all I can get from it. When I open a command line I can't get adb to recognize device and fastboot gives a bunch of ?'s where it should give me a device # and no adb or fastboot commands work. I have installed, wiped, installed, re-installed and restarted the computer, device, android sdk and kindle fire drivers umpteen times.
Is there anything I seem to be missing?
Thanks in advance for any assistance!
Sent my plea from my rooted Nexus 10 using XDA Premium HD app

I think SoupKit is your best option. It has an option to fix your sdcard mounting problem.
"That's a special kind of stupid. The kind that makes me laugh."

Ok, I'm totally new to Linux and the only internet connection I have is a phone, but I suppose it's possible. I'll figure this out and then proceed. Is Ubuntu fine for this? It looks like I can set it up alongside Windows. And keep my wife happy . . .
Sent from my Nexus 10 using XDA Premium HD app

dhwty8 said:
Ok, I'm totally new to Linux and the only internet connection I have is a phone, but I suppose it's possible. I'll figure this out and then proceed. Is Ubuntu fine for this? It looks like I can set it up alongside Windows. And keep my wife happy . . .
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
You don't have to use SoupKit, but it will be less problematic for you. If you can ever get your driver issue worked out, there is a guide stickied in the General forum that will help you with the mounting issue.
"That's a special kind of stupid. The kind that makes me laugh."

I believe my driver issue may have something to do with lots of android devices getting plugged into my pc.
I seem to be able to get fastboot again. It takes too many steps done in just the right order, but it is repeatable finally.
I've seen this sticky that you mentioned:
I've done the fastboot oem format with the success, but I can never seem to get adb commands to work.
I've read that the fire needs to be in recovery for adb, but I can't get adb to recognize device. Do I need to be anywhere in particular in recovery?
I have TWRP 2.3.1.1
If I'm on the home screen and enter 'adb devices' on my pc command line, I get 'list of devices attached' but nothing is listed.
Terminal command won't work because sdk and adb are on pc. ADB sideload fails because of mounting problem too, but then you probably already knew this.
If I need anything else or to be anywhere else on either pc or fire to get adb to work, I wouldn't know it . . .
Thanks for your time, really dude.
HTC One S, official CM10 Nightly, XDA Premium

Well, there is one thing...but I haven't attempted it yet.
Since you have access to recovery, there is an option to run terminal commands, and I know you can run 'parted' from there.
Use the guide in the General forum to fix the sdcard. You won't be using adb so you wouldn't enter 'adb shell'. Instead, enter 'su' to gain root privileges (although I don't think you even need to do that).
In TWRP select "Advanced" > "Terminal commands" > "Select Folder"
I can't see any reason it wouldn't work in your situation.
"That's a special kind of stupid. The kind that makes me laugh."

O k, when i tried the first command set starting with: 'echo' nothing happened
When i went to the second longer set, it accepted the first command saying:
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted)
'(parted) print' resulted in nothing happening and following 'umount /system' command resulted in this: 'umount: can't umount /system: Invalid argument'
system folder is there - I checked
HTC One S, CM10 Nightly, XDA Premium

You wouldn't mess with the system, data or cache partitions...only the sdcard. You would have to skip forward to that part of the tutorial. I'll mess around with it today to see if there's anything you need to know.
"That's a special kind of stupid. The kind that makes me laugh."

You rock, I skipped down, but am getting 'invalid argument' with any umount command. I'm still working on ubuntu, but am contending with bad sectors on hd and haven't been able to separate out a partition yet. . .
HTC One S, CM10 Nightly, XDA Premium

dhwty8 said:
You rock, I skipped down, but am getting 'invalid argument' with any umount command. I'm still working on ubuntu, but am contending with bad sectors on hd and haven't been able to separate out a partition yet. . .
HTC One S, CM10 Nightly, XDA Premium
Click to expand...
Click to collapse
Sorry...I had a brain fart.
The "umount sdcard" command is to make sure the sdcard isn't mounted before you start modifying it. If the sdcard is already unmounted, you can't unmount it again and you will receive the "invalid argument" error.
[Edit:] And the commands will work in TWRP by the way.

got the GNU parted welcome message
entered the following into twrp terminal command:
(parted) rm12
(parted) mkpartfs primary fat32 2309 7690
(parted) rm12
(parted) mkpart primary 2309 7690
(parted) name 12 media
(parted) quit
mount /sdcard
I got no messages along the way that anything was happening - just went to next command line
After mount command i got this:
'mount: mounting /dev/block/mmcblk0p12 on /sdcard failed: Invalid argument.
Thanks,
HTC One S, CM10 Nightly, XDA Premium

dhwty8 said:
got the GNU parted welcome message
entered the following into twrp terminal command:
(parted) rm12
(parted) mkpartfs primary fat32 2309 7690
(parted) rm12
(parted) mkpart primary 2309 7690
(parted) name 12 media
(parted) quit
mount /sdcard
I got no messages along the way that anything was happening - just went to next command line
After mount command i got this:
'mount: mounting /dev/block/mmcblk0p12 on /sdcard failed: Invalid argument.
Thanks,
HTC One S, CM10 Nightly, XDA Premium
Click to expand...
Click to collapse
Lack of an error message usually means the command was successful. Reboot (should mount the sdcard) and try installing a ROM to see if it worked.

rebooted - no go - status the same as before
HTC One S, CM10 Nightly, XDA Premium

dhwty8 said:
rebooted - no go - status the same as before
HTC One S, CM10 Nightly, XDA Premium
Click to expand...
Click to collapse
Well it looks like using TWRP's terminal emulator won't work. Shame, I really hoped it would work for you. Oh well.
You're going to have to either get your Windows drivers worked out or set up a Linux LiveUSB so you have a platform to successfully run terminal commands from.

O k I've got the drivers working to the the point that I can send fastboot commands, but I "just can't get adb to connect."
On cm10 and having trouble sharing my phones connection with my computer to get linuxliveusb and soupkit setup properly [wifi tether or pdanet+].
. . . to be continued . . .
HTC One S, CM10 Nightly, XDA Premium

Not sure at all if this will help but when I was having driver issues with windows i followed this and it worked, long time ago but might be worth a shot.
open a CMD window and type
echo %path:;=&echo.%
That will show all the entries, each on a new line so they are easier to read. Make sure there is a path entry for C:\WINDOWS\system32. If there is not add the following:
%SystemRoot%\system32

Im not a kf user but I see you can't put a rom on your sd card and that twrp doesn't mount it.. perhaps you could pop your sdcard onto a sdcard reader load a rom there and put sd back to phone then flash via recovery?
Sent from my SGH-T999 using xda premium

Rail205 - I'll try that thanks . . .
Shahkam - It's an original Kindle Fire - I don't think it has a removable sdcard.
Sent from my Nexus 10 using XDA Premium HD app

[GUIDE] Backing up a phone with broken display

I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Prerequisites
Rooted phone with broken display/digitizer/etc. Display is nonfunctional for whatever reason.
ADB for your platform. Downloads for Windows, Mac, and Linux can be found at my dev-host.
Drivers installed (Windows), rules file set up (Linux + Mac). Drivers for windows can be found here. Rules file for Linux can be found here.
Recovery file attached to this post. (twrp.img)
External sdcard with at least 2 GB free space inserted in your broken phone.
openrecoveryscript.txt file attached to this post.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Backing up your broken device
Extract the ADB zip somewhere convenient.
Move the twrp.img recovery file into the ADB extracted directory.
Move the openrecoveryscript.txt file into the ADB directory.
Open a command prompt / terminal window in the ADB directory.
Windows: Windows Key + R => Type in "cmd" then click "RUN".
Linux: Open a terminal window by selecting it from your applications.
ALL:
Code:
cd /path/to/ADB/directory
Pull the battery from your phone, place it back in and boot into recovery (VolUp + Home + Power).
Connect your phone to your computer
Make sure that the following command returns "XXXXXX recovery" before proceeding to the next step.
Code:
./adb devices
Expected output:
Code:
List of devices attached
XXXXXXX recovery
Now to install TWRP recovery to your device. Type the following commands ( after each line). Linux users: Make sure you prepend each command with "./", as in "./adb ...". ALL Make sure you type the commands in CAREFULLY.
Code:
adb push twrp.img /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
Wait until the last command above returns an output similar to below before proceeding to the next step:
Code:
12916+0 records in
12916+0 records out
6612992 bytes (6.3MB) copied, 1.094278 seconds, 5.8MB/s
Now pull your phones battery and reboot into recovery once again.
Run the following command to make sure your phone has booted into recovery completely.
Code:
adb devices
Expected output
Code:
List of devices attached
XXXXXXX recovery
Type the following to set up a script that will backup your phone to your external sdcard.
Code:
adb push openrecoveryscript.txt /cache/recovery/openrecoveryscript
Reboot your phone once more. This time, TWRP will begin backing up your ROM.
Wait for the backup to finish. You will know it is finished when you feel your phone reboot once more.
Optionally, you can check the state of your backup by running the following command and reading the last couple lines of it's output.
Code:
adb shell cat /tmp/recovery.log
Click to expand...
Click to collapse
Click to expand...
Click to collapse
That's it! Your entire system (/system, /data, /cache, and boot) will be backed up to your external sdcard. Just pop the sdcard in your replacement phone and you're good to go.
Enjoy and donate to the TWRP devs! This would not be possible if TWRP did not use the OpenRecoveryScript scripting engine!

Hellua nice guide :thumbup:
TEAM MiK
MikROMs Since 3/13/11

Man Cnexus! You are everywhere! Lol.
Nice guide. This will save lots of people :thumbup:
------------------------
Sprint Galaxy S3 "Supernexus" Thanks To Cyanogenmod
Whiplashh Rom
Look it up.

Is this method specific to the S3? I have an old S2 that I need to recover some photos from.

Hmm...boot your S2 into recovery, then connect it to your computer, run the following command and post the output for me.
Code:
adb shell ls

Hopefully I never need this guide but I think it should be a sticky. Good job!

This seems very helpful thank you.
This is a good option as well
https://code.google.com/p/androidscreencast/

CNexus said:
I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Click to expand...
Click to collapse
Thanks so much for the how-to.
I have a rooted Sprint Galaxy S3 with a broken display. I'm having a problem with getting it into recovery mode.
I believe when I hold down VolUp+Home+Power and reboot, it's loading a menu that's prompting me to select one of the boot options. It otherwise just sits there and never actually boots.
I've tried to use adb to boot it into recovery mode, but it also just sits there until I press the home key, at which point it just boots into normal mode.
Is there a way I can bypass any menus or does anyone with a working system know which option I should select at the menu?
Thanks,
Alex

Is your display broken? What does "adb devices" show when you're in that mode?

[GUIDE] Backing up a phone with broken display

Or you can use skip's unified toolkit.
I literally just used it. Moving the backup to my new device right now.

loserskater said:
Or you can use skip's unified toolkit.
I literally just used it. Moving the backup to my new device right now.
Click to expand...
Click to collapse
Whatever floats your boat :good:

Sorry, had to
Sent from my SGH-I747 using Tapatalk 2

Actually, this process might directly meet my needs.
You mentioned that the recovery image and script were attached to the initial post, though I must be missing something in that I don't see where they might be. Perhaps you could offer a pointer, please?
- ooofest

Ah sorry, you can find the files here
http://forum.xda-developers.com/showthread.php?t=2353828
Don't use the twrp.img from there though...go to the twrp website and download the latest .img file for your phone (d2att)
Sent from my S3 on Sense 5 (you jelly?)

CNexus said:
Ah sorry, you can find the files here
http://forum.xda-developers.com/showthread.php?t=2353828
Don't use the twrp.img from there though...go to the twrp website and download the latest .img file for your phone (d2att)
Click to expand...
Click to collapse
Thanks - I downloaded the appropriate files, but wonder if this can be used on a stock phone.
That is, I was able to push twrp.img to /tmp/twrp.img, but cannot write in the next step:
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
/dev/block/mmcblk0p18: cannot open for write: Permission denied
This is a stock AT&T phone, in recovery mode, never been rooted.
- ooofest

You need to be rooted for this to work.

CNexus said:
You need to be rooted for this to work.
Click to expand...
Click to collapse
Ya know . . . I need to read things more carefully. Was so excited to see something that might possibly help. Sorry about that.
It's been awhile since I looked into rooting the Galaxy S III and will look around, but don't recall that this can be rooted from recovery, unfortunately. And, it seems that USB Debugging is not turned on when it boots to the lockscreen.
Hm.
- ooofest

[GUIDE] Backing up a phone with broken display

Don't forget to attach your script.txt file!
Also, I was thinking if its easy enough to just edit your existing script, maybe post ones that can wipe data/factory reset and possibly some other functions available in TWRP?
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Don't forget to attach your script.txt file!
Click to expand...
Click to collapse
Ah, whoops! Files can be found here until I can get to a computer: http://forum.xda-developers.com/showthread.php?p=43332650
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.

DocHoliday77 said:
Also, I was thinking if its easy enough to just edit your existing script, maybe post ones that can wipe data/factory reset and possibly some other functions available in TWRP?
Click to expand...
Click to collapse
I don't want to reinvent the wheel, but there areapps that can do that I'll post a couple scripts later though :thumbup:
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.

CNexus said:
I don't want to reinvent the wheel, but there areapps that can do that I'll post a couple scripts later though :thumbup:
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.
Click to expand...
Click to collapse
Which apps? I'm currently in a position where I need to erase my phone but the screen doesn't work.

porfymartinez said:
Which apps? I'm currently in a position where I need to erase my phone but the screen doesn't work.
Click to expand...
Click to collapse
Ah. Replace the text inside the openrecoveryscript.txt with this following
Code:
wipe data
wipe cache
wipe dalvik
wipe system
Optionally, add the following (to the script I wrote above) to wipe your internal storage.
Code:
mount data
cmd rm -r /data/media
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.

Develop Bugs

welcome