Database Info

Stuck in a soft brick

Been on the site for a few years modding my phones, just found out that phones are a lot easier, the download of the room got corrupted and my own complacency from changing rooms on my phone so many times left my scooping to do a nandroid, dumb i know. So my tab sits at the splash screen, its unlocked and rooted, i was able to get into CMD but that no longer works after trying a one click brick fix, i can use Vol - and pow to get to that menu which recently list one potion as well, it now only has fast boot and wipe data, and with Vol + and power the screen goes black and the computer asks for vtx(?) drivers. Any help on where to go from here would be greatly appreciated, thanks
Sent from my SGH-T769 using xda app-developers app

flash cmw using fastboot and adb push your desired rom to your tablet's internal memory and flash with cmw?
Sent from my ASUS Transformer Pad TF300T

was working on that on my laptop but it's so cluttered with roms/mods/drivers from the phone, just switched to a nice clean comp going to work on it from here, hopefully it'll help, also not very experienced with adb, but there's enough tut's and advice on here so it shouldn't be to hard, thanks for replying

ok, I flashed CMW with fastboot, pushed the rom I wanted onm and flashed that with cmw, it installed and it didn't help, still sit's at the splash screen, I'm stumped

go into CWM
and use following ADB commands:
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
Enter
Wen this is ready the next one
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
Enter
That should be it

ok, ran those commands and nothing happened, don't know if this shows anything of signifigence:
~ # dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
1+0 records in
1+0 records out
100 bytes (100B) copied, 0.005003 seconds, 19.5KB/s
~ # dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
1+0 records in
1+0 records out
16 bytes (16B) copied, 0.004434 seconds, 3.5KB/s
also tried installing the rom again, I looked through the folders with adb quick push, not sure if it shows files or just folders, but all I see is folders, no files at all in any of them

you can try this unbrick tool
http://www.4shared.com/zip/7XYW-4c4/WSG_UnBricker_TF300T_V102.html
This will flash the ww.30 Version.

sadly no luck again, this is the one I tried before that removed my cold boot option from the vol - power menu, and removed cwm as well, this is frustrating, thanks for helping out though, I'd love to get this back up and running

Have you tried flashing a stock rom through CWM?

tried a stock deodexed rom, nothing, but I did find something that may be causing problems, I noticed errors on the unbricking app, then on ADB Quick Push I checked the last tab and saw this
"Devices found:
0123456789ABCDEF
Failed to mount as R/W"
if I don't have r/w access it's probably blocking the unbricking from writing the files needed, I tried using adb to change rights and it comes up with this:
"~ # mount -o remount,rw /system
mount -o remount,rw /system
mount: can't find /system in /proc/mounts
~ #"
I'm fastbooting in the cwm + root so I should be able to change it, and it was indeed rooted before the issues, or am I way of track with this r/w thing?

I'm starting to think there's something bigger going on behind the scene's here, the tab isn't retaining anything I do, all memory is gone, every restart it forgets where the clockwork mod folder is until I go into cwm and go into the folder then it shows up, when I fix the permissions under advanced in cwm, it keeps them until it reboots, and now I recall when it started doing all this I took it out of the leather case and the corner of the screen had come out of the casing, perhaps something jogged loose, I'll pop it open and give it a look I guess

thanks to everyone who helped me work on this issue, the problem has been solved, the onefix tool wasn't pushing through and erroring, another user had same problems and resolved issues through fastboot, using his steps it fixed my issues as well, thanks again everyone, post that fixed my tab http://forum.xda-developers.com/showthread.php?p=29142627#post29142627

[Q] Internal Memory Recovery -- help please

Hi,
I have a Verizon Samsung Galaxy S3 SCH-I535.
I have rooted it using this guide. I realize there was probably an easier way to root it, but regardless it worked fine, I have root access.
The phone is returned to factory condition, pretty much, but I need to recover data from it. There is no microSD card.
I have tried to follow this guide for recovering the internal memory without being able to transfer the internal memory to my computer. I'm stuck at the data transfer point.
I've followed the guide to the letter, except I'm trying to recover memory block /dev/block/mmcblk0p23 (and I've also tried simply /dev/block/mmcblk0), so I've modified the commands to the following:
Code:
adb forward tcp:5555 tcp:5555
adb shell
/system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0p23
And in the other Cygwin terminal:
Code:
adb forward tcp:5555 tcp:5555
cd /nexus
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p23.raw
Screenshots attached. I'm not sure why, but the data stays at 0 B/s no matter how long I let it run.
Am I missing something? Am I doing something wrong? I've installed Busybox on the phone (it's in xbin, not bin, hence the modified syntax). Cygwin (with pv and util-linux), Netcat, and ADB on the computer. USB debugging mode is enabled on the phone (ADB connection works).
I really need to pull the internal data off of this phone soon... can anyone help me get this figured out please? Thanks.

mastercsmc said:
Hi,
I have a Verizon Samsung Galaxy S3 SCH-I535.
I have rooted it using this guide. I realize there was probably an easier way to root it, but regardless it worked fine, I have root access.
The phone is returned to factory condition, pretty much, but I need to recover data from it. There is no microSD card.
I have tried to follow this guide for recovering the internal memory without being able to transfer the internal memory to my computer. I'm stuck at the data transfer point.
I've followed the guide to the letter, except I'm trying to recover memory block /dev/block/mmcblk0p23 (and I've also tried simply /dev/block/mmcblk0), so I've modified the commands to the following:
Code:
adb forward tcp:5555 tcp:5555
adb shell
/system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0p23
And in the other Cygwin terminal:
Code:
adb forward tcp:5555 tcp:5555
cd /nexus
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p23.raw
Screenshots attached. I'm not sure why, but the data stays at 0 B/s no matter how long I let it run.
Am I missing something? Am I doing something wrong? I've installed Busybox on the phone (it's in xbin, not bin, hence the modified syntax). Cygwin (with pv and util-linux), Netcat, and ADB on the computer. USB debugging mode is enabled on the phone (ADB connection works).
I really need to pull the internal data off of this phone soon... can anyone help me get this figured out please? Thanks.
Click to expand...
Click to collapse
Are you running cygwin as an administrator? Are you requesting superuser access by typing su after adb shell?

billard412 said:
Are you running cygwin as an administrator? Are you requesting superuser access by typing su after adb shell?
Click to expand...
Click to collapse
Hi billard, thank you for the response.
I have tried using su (# prompt instead of $ appears, so yes it is working) after adb shell, with no change in results.
I hadn't tried running Cygwin as administrator, but just made that change as well to see if it would make a difference. Still no dice.
I've also ensured NTFS permissions in the /nexus folder (C:\Cygwin\nexus) are "full access", and there are no issues there, either. Screen shot attached of latest attempt (Cygwin is "run as administrator"/su command used).

mastercsmc said:
Hi billard, thank you for the response.
I have tried using su (# prompt instead of $ appears, so yes it is working) after adb shell, with no change in results.
I hadn't tried running Cygwin as administrator, but just made that change as well to see if it would make a difference. Still no dice.
I've also ensured NTFS permissions in the /nexus folder (C:\Cygwin\nexus) are "full access", and there are no issues there, either. Screen shot attached of latest attempt (Cygwin is "run as administrator"/su command used).
Click to expand...
Click to collapse
Don't know why I didn't catch this sooner. But what lead you to believe it was mmcblk0p23 you needed to use? I'm not sure exactly what that partition is(if it exists) but the data partition is mmcblk0p15 I believe on the US S3's. Try that

billard412 said:
Don't know why I didn't catch this sooner. But what lead you to believe it was mmcblk0p23 you needed to use? I'm not sure exactly what that partition is(if it exists) but the data partition is mmcblk0p15 I believe on the US S3's. Try that
Click to expand...
Click to collapse
I was guessing it was the highest numerical memory block, and /system/dev/block ls lists 23 as the highest number.
I just tried with mmcblk0p15 and have the same exact frustrating 0 B/s indefinite results. -_-

[Q] CWM Recovery loading at startup and infinite boot animation issue

Hello,
I have nerve-breaking issue with CWM Recovery wich loads up every time i turn on my tablet. So if i wish to restart or to go to CWM i have to hold volume down button to get to bootloader and then select Android to get back to CWM.
So my first question is how do i resolve this problem with constant booting into CWM Recovery? so it would go to recovery only when i select reboot to recovery option in CWM
My next issue is that i have tried to install Ubuntu Touch for TF101 (from ubuntu touch wiki). And in installation guide it says you have to download cm-10.1-20130404-UNOFFICIAL-tf101.zip, and then quantal-preinstalled-phablet-armhf.zip. The fist zip i got successfully but the second link did not exist, so i checked their repository and found similar zip named saucy-preinstalled-phablet-armhf.zip (i tought it's a newer version) well, then i made data wipe and installed both as stated in guide, i also deleted cache and now when i try to boot my tablet i get to blue spinning CWM logo and it stays there for eternity.
So my second question is how to put some other rom on SD card so i can install another rom? or what i have to do to make Ubuntu Touch work?
My third thing that i noticed (for me it seems wrong) is that with every data wipe it makes new 0/ folder and it keeps everything before wipe in it. I made couple of data wipes and now my data structure looks something like this:
Code:
0/
0/
0/
0/
ASUS/
Alarms/
Albums/
AndroZip/
...other folders (apps and data from stock rom)
Alarms/
Android/
Autodesk/
DCIM/
...other folders (probably from first wipe)
Alarms/
Android/
DCIM/
Downloads/
...other folders (probably from second or third wipe)
legacy/
obb/
obb/
So my third question is if this is the correct data structure because it seems wrong for me? And how to resolve that issue?
My un-educated guess is that all three problems are connected, but my android experience and knowdlege is far to small to have a clue how to begin resolving this twisted problem.
I did some researching and as far it goes with second question i think i have soft-bricked tablet (maybe there is still hope?). So i would like to make it back to original rom or 4.2 jelly bean as i had till now without CWM Recovery issue, if possible of course
(Using ClockworkMod Recovery v5.8.3.4 now, and i think at beginning there was ROM Manager used, i bought used tablet)
Please help, thx

The issues are somewhat intertwined, and run back to using CWM 5.8.X.X
The first thing you MUST do is stop the CWM bootloop or you will not be able to install any other ROM or recovery.
If you can boot to a ROM, run a terminal window with SU permissions. If you cannot boot to a ROM, you will need to run from an ADB Shell from a computer when booted to recovery:
Code:
echo boot | dd of/dev/block/mmcblk0p3 bs=1 seek=0
Then reboot normally and your bootloop to CWM should be fixed.
Next, I HIGHLY HIGHLY recommend upgrading to TWRP 2.3.2.3 or higher. The /0/0/0/0 issue has to do with the new directory structure of Android 4.2 for multi-users. CWM 5.8.X.X cannot handle multi-users properly.
TWRP 2.3.2.3 can be updated using the GooManager app (tap the menu key in the top right and choose Install OpenRecovery Script).
IMO, TWRP is far superior to CWM as it has a file manager and terminal emulator.
I am running SidneyK's TWRP 2.6.3.0. He has a zip that can be flashed from CWM to update, however you have to have the boot loop issue resolved or it will not flash.

Ok, as you said i cannot boot to ROM so i tried with ADB Shell but it says
error: device not found
I have device connected on keyboard dock and cable from dock to pc
Any advices how to reslove that issue? Am i missing some drivers?
In device manager i can see that there is a Transformer device with yellow exclamation. I tried to install drivers from asus webpage but it wont install.
Should i get copy of live linux and try from there?
EDIT:
I got the connection working with ADB Shell but i got this response from code you provided
Code:
~ # echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes (5B) copied, 0.006079 seconds, 822B/s
Ok now i'm not getting to recovery after restart, but now my tablet is constantly restarting... after Asus eee image there is few secodnds of black screen and then it restarts itself.
Could this be due to my Ubuntu Thouch installation attempt?
Or how can i remove CWM Recovery and install TWRP whitout working ROM on tablet?

boonz said:
Maybe i should type?
Code:
echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
Click to expand...
Click to collapse
Damn, yeah, it should be ...of=dev/block/...
D'OH!

I made few more edits on previous post as i was trying diffrent things. So currently i'm at this position:
Code:
~ # echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes (5B) copied, 0.006079 seconds, 822B/s
Ok now i'm not getting to recovery after restart, but now my tablet is constantly restarting... after Asus eee logo there is few secodnds of black screen and then it restarts itself.
Could this be due to my Ubuntu Thouch installation attempt or should i push some basic ROM from asus webpage to tablet and replace it with Ubuntu Touch in order to proceed with your instructions?
Or how can i remove CWM Recovery and install TWRP whitout working ROM on tablet?
Thx

boonz said:
I made few more edits on previous post as i was trying diffrent things. So currently i'm at this position:
Code:
~ # echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes (5B) copied, 0.006079 seconds, 822B/s
Ok now i'm not getting to recovery after restart, but now my tablet is constantly restarting... after Asus eee logo there is few secodnds of black screen and then it restarts itself.
Could this be due to my Ubuntu Thouch installation attempt or should i push some basic ROM from asus webpage to tablet and replace it with Ubuntu Touch in order to proceed with your instructions?
Or how can i remove CWM Recovery and install TWRP whitout working ROM on tablet?
Thx
Click to expand...
Click to collapse
There are a few ways.
You can use ADB to push the TWRP.zip from sidneyk's thread in the dev section, install that from the internal storage.
If you have a TF101 (non 3G) you can use one of my repacked EasyFlasher in APX mode to push TWRP: http://forum.xda-developers.com/showpost.php?p=43986513
Another option is to use the .blob file (extracted from the zip) and use adb to install when in CWM recovery.
Push the blob file to the /sdcard/ (called twrp.blob for this example)
Use adb shell and execute:
Code:
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot normally (you need to see the progress indicator complete before rebooting to recovery). What I do is just hold the power button for 10 seconds, once the progress bar completes and it flashes black, hold VOL DOWN until you see the RCK message then tap VOL UP to boot to recovery. With any luck you will see TWRP.

Now i downloaded TWRP 2.6 for TF101 from teamw.in page and i got that twrp.blob file.
Then i executed adb push and it says it successfully copied file
But when i check in adb shell it says i cannot go or look into sdcard.
Am i missing some sort of permissions? or would live linux still be better option and using it with su might help?
Or is it ok and i should just run dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4?
Code:
C:\Program Files\Android\sdk\platform-tools>adb push C:\Users\BoonZ\Downloads\twrp.blob sdcard
1322 KB/s (4984908 bytes in 3.682s)
C:\Program Files\Android\sdk\platform-tools>adb shell
~ # cd sdcard
cd sdcard
/sbin/sh: cd: can't cd to sdcard

boonz said:
Now i downloaded TWRP 2.6 for TF101 from teamw.in page and i got that twrp.blob file.
Then i executed adb push and it says it successfully copied file
But when i check in adb shell it says i cannot go or look into sdcard.
Am i missing some sort of permissions? or would live linux still be better option and using it with su might help?
Or is it ok and i should just run dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4?
Code:
C:\Program Files\Android\sdk\platform-tools>adb push C:\Users\BoonZ\Downloads\twrp.blob sdcard
1322 KB/s (4984908 bytes in 3.682s)
C:\Program Files\Android\sdk\platform-tools>adb shell
~ # cd sdcard
cd sdcard
/sbin/sh: cd: can't cd to sdcard
Click to expand...
Click to collapse
Try doing cd /sdcard/
If that does not work, you can also just push the twrp.blob to the / directory and push it from there too.

frederuco said:
Try doing cd /sdcard/
If that does not work, you can also just push the twrp.blob to the / directory and push it from there too.
Click to expand...
Click to collapse
Ok superb, i have TWRP it says v2.3.2.3
How do i perform something like format or delete everything (so there will be no 0/0/0/ folders or whatsoever) and make my tablet usefull again. I would like to run jellybean again because i'm pretty used to it and delete that Ubunto Touch mess i made. Maybe little help here, so i don't mess anything up?
Thx

Go to the Wipe section.
Wipe the system, davlik and also the cache.
Choose the FORMAT DATA option to completely wipe the /data/ partition (this deletes everything in the /data/media/ aka /sdcard/ directory)
Then I would reboot back to recovery (suggested after a format data) and then install your ROM, applicable GAPPS and kernel if necessary.

mount loopback crashing phone

Not sure which section to post this question but I've been trying to create & mount a local file for a project idea. Failing right a the start I've been looking for information but struggling to find any logs to explain whats happening.
Phone Galaxy S5, flashed with LineageOS 15.1 (upto date)
Basically I've been trying to create a file with dd, making a filesystem then mounting.
Creating a file with dd on phone or external also running mkfs (tried exfat ext4 2fs) works fine.
The problem comes when mounting using adb or local shell app the command doesn't complete while phone reboots.
Sample shell commands used to help with understanding my issue
Code:
su -
cd /storage/(sdcard)
dd if=/dev/zero of=virtualfs bs=1024 count=10240
mkfs.exfat virtualfs
mkdir vir
mount -o loop ./virtualfs ./vir
Phone freezes, 5 seconds later reboots
I've tried running from a couple of terminals over adb with one running logcat but nothing is seen between command and reboot.
At this point I'm lost where to look for errors or what to attempt next.
Could anyone suggest how this could be done. Or how to get more information whats causing the reboot.
Thanks

Running "dd" using "busybox nc" stops w.o errors, random size every time

Phone: Nexus 5 running Lineage 18.1 and rooted with Magisk v25.2 (and BusyBox 1.32.0)
OS: Windows 11 Version 22H2 (OS Build: 22621.819)
Autopsy: 4.19.3
Hello,
Trying to dump my "/data"-partition from my Android-phone and analyze it in Autopsy.
If I run a `mount` command on my phone I can see the following information for my "/data"-partition:
Code:
/dev/block/mmcblk0p29 on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic,data=ordered)
I then proceed to image that partition by running:
Code:
dd if=/dev/block/mmcblk0p29 of=/sdcard/mmcblk0p29.img
it fails because my device runs out of diskspace which is kind of logical.
If I try:
[Console 1 (Windows)]
Code:
adb forward tcp:9191 tcp:9191
Code:
ncat 127.0.0.1 9191 > android_data.dd
[Console 2 (Phone)]
Code:
dd if=/dev/block/mmcblk0p29 | busybox nc -l -p 9191
I can see that it writes "android_data.dd" but that file always "stops" growing after a random size even though neither "Console 1" or "Console 2" outputs any errors.
Whats weird is that I need to install BusyBox after every reboot of my phone, perhaps that is normal?
Q1) I am dumping the right partition?
I have multiple partitions that are named something like /dev/D8RN3/.magisk/block/system_root on /system/bin/debuggerd` thinking that I might dump the "/data"-partition which isn't mounted as "root" and that might cause the issue below?
Q2) How can I get past the "error" that the file ("android_data.dd") stops growing?
I was able to get the entire file once (~ 27GB) but now the file stops growing after a random amount of size (which always differs).
There are no errors in either adb ("phone"-side) or PowerShell ("computer"-side).
Thanks for any suggestion - TheSwede86