Database Info

Jailbreaking G1

breaking..ok, old news: RC30 (jailbreak fix)
http://www.tgdaily.com/content/view/40063/140

Curious about this. Im not in the know enough to do anything with root, but for all of you that have access, if others update, will they be able to use anything that you develop or create with access to root? hopefully....

I 'm wondering how can I prevent this. I'm in about the same boat as you honda. Root is a stranger to me... But, I'm sure it would suck if I get stuck out side of the loop :/

sonikamd said:
I 'm wondering how can I prevent this. I'm in about the same boat as you honda. Root is a stranger to me... But, I'm sure it would suck if I get stuck out side of the loop :/
Click to expand...
Click to collapse
If you look there is another thread where someone else posts what to do... although he hasn't got the files on the forum yet he is having some issues uploading them.

sonikamd said:
I 'm wondering how can I prevent this. I'm in about the same boat as you honda. Root is a stranger to me... But, I'm sure it would suck if I get stuck out side of the loop :/
Click to expand...
Click to collapse
JUST DON'T UPDATE TO RC30. It's that simple.
If you don't understand how to get root, just wait till someone (I would but haven't had time) makes a very detailed yet simple method.

Ah, I'm still running RC19 and have yet to experience Google's update process.
I thought the update was mandatory and done without user input, just a "congratulations, you phone is now a little slower!"
So we can just deny the update with the stock sw?

sonikamd said:
So we can just deny the update with the stock sw?
Click to expand...
Click to collapse
When you get the OTA update, it pops up a message window asking if you want to install. You say either say yes, or "not right now". I think it will keep bugging you to install, and possibly go ahead and automatically install it if you say "not right now" enough times. (I'm not positive about that.. I just remember seeing something like that when I was looking through the source for the updater app).

I think it works like Windows updates, it gives you option to update now or later and if neither is hit in a certain time it will install it automatically. I am going to test this when my update comes. I will hit Update later and see what it does. but i have read others comments saying they never seen the update now or later window and got the new version anyhow.

I'm on the train right now so someone else (or me) can post detailed directions. But if you get root and rename/remove /etc/security/otakeys.zip they (probably) can't update you automatically.
While that file is in place they might be able to upgrade without prompting (anyone want to search the code for info?)
UPDATE: They -can- forcibly update you: http://forum.xda-developers.com/showthread.php?goto=newpost&t=443328

google should wonder ppl do thing themselves...wen they have to come up with 3 update in less than a month....there always worried about security and not functionality..lol...i mean cmon i had to buy a new sdcard jus to get RC 29...cause it sure wasnt commin to me via OTA....i wonder wat i have to do to get RC 30..

SmartBrother90 said:
google should wonder ppl do thing themselves...wen they have to come up with 3 update in less than a month....there always worried about security and not functionality..lol...i mean cmon i had to buy a new sdcard jus to get RC 29...cause it sure wasnt commin to me via OTA....i wonder wat i have to do to get RC 30..
Click to expand...
Click to collapse
Correct spelling and punctuation may be a good place to start

sonikamd said:
Ah, I'm still running RC19 and have yet to experience Google's update process.
I thought the update was mandatory and done without user input, just a "congratulations, you phone is now a little slower!"
So we can just deny the update with the stock sw?
Click to expand...
Click to collapse
Well, I accepted RC29 and I've noticed the phone is faster and has better battery life.
I've also been very conservative with usage because I'm waiting to install and run apps from the SD card.

jailbreaking the t-mobile RC30 update
From what I have read so far it is not possible to re do the images on the G1 because of the RC30 patch from T-Mobile. Mainly because you do not have root, and the second because without root you can't remount the /system partition as RO.
adb allows you to mount the /system partition as RW. Would this not do the trick.
Code:
./adb shell
#mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p1 /sdcard vfat ro,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0
This was the out put that I got. Now to run the remount from adb.
Code:
adb remount
-
remount succeeded
now to make sure that this really worked.
Code:
./adb shell
-
# mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 rw 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p1 /sdcard vfat ro,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0
as you can see the /system directory is not in rw mode and not ro mode.
To test to see if this is the case.
Code:
vi test.push (:wq)
adb push test.push /system
adb shell
# cd /system
# ls
test.push
lib
media
framework
fonts
etc
build.prop
bin
usr
sounds
recovery.img
app
lost+found
As we can see this did seem to work. I do not have a T-Mobile RC30. I have mine jailbroken already. with the steps that JesusFreke laid out.
I was wondering if it would be possible to do the same steps but with using adb to mount the fs in rw, and then using adb push to push the recovery.img to the device into the /system dir.
doing another push of the test.push file seems to take.
Code:
adb push test.push /system
vi test.push (i incerted the leter i)
adb push test.push /system
0 KB/s (2 bytes in 0.048s)
adb shell
# cat /system/test.push
i
#
So this might be the break that people are looking for that have the T-Mobile RC30. JesusFreke I know that you said that you have one with an RC30 from T-Mobile. Would you be willing to try this at the risk of bricking the phone? I know that is a $400 question, or anyone else for that matter.
If you do try it, please let me know the results. I have a friend, whos wife has the RC30 from T-Mobile. He is not willing to risk his wife's wrath.

It works on emulator.exe but will the live RC30 adb server accept remount? I notice that there are no references to remount in the official documentation. Alas I don't have any official RC30 G1 to test with.

Id bewilling to trythis right now. I have a Modded RC30 that I will update to the official RC30 that I am sending back anyways for defects. Anyone wanna tell me how to flash mine back to Official RC30 and Ill get to trying.

mouseclone said:
From what I have read so far it is not possible to re do the images on the G1 because of the RC30 patch from T-Mobile. Mainly because you do not have root, and the second because without root you can't remount the /system partition as RO.
adb allows you to mount the /system partition as RW. Would this not do the trick.
Code:
./adb shell
#mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p1 /sdcard vfat ro,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0
This was the out put that I got. Now to run the remount from adb.
Code:
adb remount
-
remount succeeded
now to make sure that this really worked.
Code:
./adb shell
-
# mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 rw 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p1 /sdcard vfat ro,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0
as you can see the /system directory is not in rw mode and not ro mode.
To test to see if this is the case.
Code:
vi test.push (:wq)
adb push test.push /system
adb shell
# cd /system
# ls
test.push
lib
media
framework
fonts
etc
build.prop
bin
usr
sounds
recovery.img
app
lost+found
As we can see this did seem to work. I do not have a T-Mobile RC30. I have mine jailbroken already. with the steps that JesusFreke laid out.
I was wondering if it would be possible to do the same steps but with using adb to mount the fs in rw, and then using adb push to push the recovery.img to the device into the /system dir.
doing another push of the test.push file seems to take.
Code:
adb push test.push /system
vi test.push (i incerted the leter i)
adb push test.push /system
0 KB/s (2 bytes in 0.048s)
adb shell
# cat /system/test.push
i
#
So this might be the break that people are looking for that have the T-Mobile RC30. JesusFreke I know that you said that you have one with an RC30 from T-Mobile. Would you be willing to try this at the risk of bricking the phone? I know that is a $400 question, or anyone else for that matter.
If you do try it, please let me know the results. I have a friend, whos wife has the RC30 from T-Mobile. He is not willing to risk his wife's wrath.
Click to expand...
Click to collapse
The RC30 you have from JesusFreke gives the adb daemon root permissions. What you listed will not work on a Google RC30.

Koush said:
The RC30 you have from JesusFreke gives the adb daemon root permissions. What you listed will not work on a Google RC30.
Click to expand...
Click to collapse
Meaning that as soon as you type in adb shell and hit enter it will not even start the daemon?

Get official RC30 zip (here), use SignApk.jar from AndroidMod.zip (here) on it and place it in root of sdcard as update.zip. Reboot into recovery and Alt+S.

ballaholyk84 said:
Meaning that as soon as you type in adb shell and hit enter it will not even start the daemon?
Click to expand...
Click to collapse
Most likely it just gives the shell at $ instead of #.
Edit: gah, dyslexic.

Koush said:
The RC30 you have from JesusFreke gives the adb daemon root permissions. What you listed will not work on a Google RC30.
Click to expand...
Click to collapse
I was thinking that was just for the adb shell command. The adb remount is something that is in the helpfile from the SDK. Just typing in adb will give you the list of commands to use.
If not going though the shell how ever, did they disable all of adb's root privs? If you have one and try the remount and get a success, the adb still has root privies, just not on with the adb shell command.
Really this is just a thought. I wish that I really had a device to test it on.

/efs not mounted - need help from Linux experts and others rooted i580x users!!!

After a sleepy ODIN flash, using SPICA ops with G3 firmware => STUPID??? NO, not done yet , next ODIN flash segment, accidentally stick clear phone EFS via Debug options (DOUBLE CRAZY!!!) NOW i lost the precious IMEI and /efs partitions corrupted as well.
i've got the fixed nv_data.bin and both stl4.img and bml4.img from [email protected] (attached). Thanks for his kindness and supportive to the community!
But even with those i still can't fix the issue!!!! /efs did not mounted via mount command...
as in a GOOD G3, mount command result will be as below:
Code:
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/stl6 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
/dev/block/stl7 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
/dev/block/stl8 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
[B]/dev/block/stl4 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0[/B]
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,f mask=0702,dmask=0602,allow_utime=0020,codepage=cp4 37,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
in my case the bold line just missing... so this is must be the problem.
I tried to do the same as SPICA's method as below:
Code:
$su
#dd if=/sdcard/bml4.img of=/dev/block/bml4
#reboot
It's OK then but...
Code:
$su
#dd if=/sdcard/stl4.img of=/dev/block/stl4
/dev/block/stl4: cannot open for write: Invalid agrument
With this error my /efs cannot be mount... and still missing from the mount command. I'm just a linux noob so pls help me out. How can i restore the stl4 partition properly???
My girlfriend now really mad at me due to she don't have her beloved phone this christmas already. OMG!!!!!
and to all rooted i580x user Pls kindly help compare your "good" /efs folder... maybe mine missing something???? due to one time Erase Phone EFS using Odin Debug Options.
Mine /efs now as below:
Code:
/efs/nv_data.bin
/efs/imei/.nvmac.info
/efs/.files/.dm33 (empty folder)
/efs/.files/.dx1 (empty folder)
/efs/.files/.mp301 (empty folder)
And if you can do adb shell, it'll be very kind of you by sharing your good backup stl4 and bml4 - for research purpose (those partitions did not content any of yours personal data - so PLS HELP!!!). Pls do the backup partions as below and share your img here if possible.
Code:
$su
#cat /dev/block/stl4 > /sdcard/efs_dev-block-stl4.img
#cat /dev/block/bml4 > /sdcard/efs_dev-block-bml4.img
TIA and Best Regards
P/S: when do the ls /dev/block/stl* the stl4 is there but cannot restore using the backup img. it's weird...
Code:
#ls /dev/block/stl*
/dev/block/stl1
/dev/block/stl10
/dev/block/stl2
/dev/block/stl3
/dev/block/stl4
/dev/block/stl5
/dev/block/stl6
/dev/block/stl7
/dev/block/stl8
/dev/block/stl9
same for bml4...

I suggest you remove the images.zip
This contains your IMEI, so anyone can clone it.

Szaby59 said:
I suggest you remove the images.zip
This contains your IMEI, so anyone can clone it.
Click to expand...
Click to collapse
This zip only bml4.img and stl4.img, the fixed nv_data.bin still inside the phone @ SAMSUNG SC . Now they still can not redo IMEI yet so i must find someway else.

kenblat said:
This zip only bml4.img and stl4.img, the fixed nv_data.bin still inside the phone @ SAMSUNG SC . Now they still can not redo IMEI yet so i must find someway else.
Click to expand...
Click to collapse
fixed ur phone yet? noob idea: can u try flashing but this time with the right ops?

were you able solve the problem? I am facing exactly same problem.

[CWM] ClockWorkMod for Asus Padfone 2

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm trying to port Asus Padfone 2 to cyanogenmod.
Here a working CWM for Asus Padfone 2
Version: v6.0.2.8
TRY IT BEFORE TO FLASH!!!!
for test:
Code:
fastboot boot recovery.img
If you are sure and you will flash it:
Code:
fastboot flash recovery recovery.img
CHANGELOG
Code:
Adb now is working
------
Fixed /sdcard/ mount error
Warning: if you format /data/ you will format /sdcard because it is a mount point of /data/media/

-reserved-

I haven't tried it yet, I'm about to download it, but if this works I love you man!
Edit: It worked! Thank you a billion times for your work!

Thank you for starting this project. I am really excited about a CM version on this nice device. I only hope that the camera will be as good as well.
---------- Post added at 07:15 PM ---------- Previous post was at 07:12 PM ----------
Lidenburg said:
I haven't tried it yet, I'm about to download it, but if this works I love you man!
Edit: It worked! Thank you a billion times for your work!
Click to expand...
Click to collapse
Did you try a nandroid and restore already? Than we can use UOT kitchen for modding like circle battery and more

That good news xD
Awaiting next few days, have if any Rom out
thanks for your work
PD: flas this rom:
http://www.modaco.com/topic/360444-deodexed-wwe-rom-for-the-padfone-2/
Does it will work?

R: [CWM] ClockWorkMod for Asus Padfone 2
We need to test the wipe option. In particolar the wipe of the userdata (sdcard)
Sent from my PadFone 2 using xda app-developers app

Just tried it now, sdcard won't mount and we can't do a backup since it can't mount the backup path (which is in the sdcard)
gmxt and sdcard won't mount, I think OP needs to specify their mountings in the recovery.fstab

R: [CWM] ClockWorkMod for Asus Padfone 2
/sdcard/ doesn't exist. I saw the same error in tcwm or modaco recovery. The correct mount point is /data/media/
The gmxt partition have a wrong fs, i will fix it soon.
Edit:damn italian auto correct!
Sent from my PadFone 2 using xda app-developers app

I think the /sdcard mount is at dev/block/mmcblk1p1 and gmxt at /dev/block/platform/msm_sdcc.1/by-name/gmxt

That is the information i can get:
Code:
sh-4.2# cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
tmpfs /Removable tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/platform/msm_sdcc.1/by-name/asuskey3 /asuskey3 ext4 rw,nosuid,nodev,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,fmask=0177,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/asusdata /data/asusdata ext4 ro,nosuid,nodev,relatime,noauto_da_alloc 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1015,group_id=1015,default_permissions,allow_other 0 0
sh-4.2#
I'm not a dev and i dont have skills but what we have in this:
/dev/block/platform/msm_sdcc.1/by-name/userdata
and this:
/dev/fuse /storage/sdcard0

Here's the recovery.fstab used in the modaco custom recovery, which i never tried, but I didn't hear anyone mention the sdcard not being mounted, so it should work

i decompress the "boot.img" file and check the files in ramdisk. I found one file calls "init.asus.sdcard.sh" and i open then i saw this
Code:
#!/system/bin/sh
mount -o bind /data/media /storage/sdcard0
something usefull?
in attach i post the ramdisk files of stock boot.img

This makes me question my previous comment, I'm new to android programming aswell, but from what I know that should mount the sdcard to data/media when the phone boots

sdcard mount problem fixed

Great news i will try soon.
I'm trying port cm roms but im lost... i think is great for us make little team ti port.
Sent from my PadFone 2 using xda app-developers app

dangeroustry said:
sdcard mount problem fixed
Click to expand...
Click to collapse
with recovery in attach i cant mount data/media over usb. what is the option?
mount /sdcard or mount /data?
also the adb cannot recognize the device...

R: [CWM] ClockWorkMod for Asus Padfone 2
For upload file you nerd to use the sideload function. In the recovery select adb sideload. From the pc use adb sideload <filename> and it will be flashed
Sent from my PadFone 2 using xda app-developers app

Can someone make a youtube video of it please

mikepronin said:
Can someone make a youtube video of it please
Click to expand...
Click to collapse
+10000

mikepronin said:
Can someone make a youtube video of it please
Click to expand...
Click to collapse
youtube video?
doing what?

[BOUNTY] 30$ for unbricking my phone (Asus Padfone Infinity A80)

Hi everyone,
I have a bricked Asus A80, which is repairable if someone has the skills. But I don't. So I need someone's help.
I have tried a lot of procedures but none of them have worked. I will display the details below.
For the one who will give me the correct procedure to unbrick my phone, I will pay him 30$ with Paypal. A small buck, but I have nothing more right now. And all effort deserves reward.
Thanks for your assistance.
Problem :
- Phone stuck on boot screen with the message "Invalid Kernel !" written on the top of the screen.
Pros
- I can access fastboot
- I can boot custom recovery from fastboot
- I can access ADB from booted custom recovery
- I have another working Asus A80 to dump stuff if needed
Cons
- I can't boot to stock recovery
- Flashing complete roms from booted custom recovery works but does not change anything
- I can't flash boot.img nor recovery.img, or at least I did not succeed
Here is all the historic of what I've tried, what worked and what did not, with all the error messages :
http://padfoneclub.com/pl/forum/forum_viewtopic.php?12268.15
This where I am right now. So anyone willing to help?
Thanks guys.

Hello... I read your link. Maybe you are trying to write in a Read only partition(FAILED remote: Security is Enable, close 'flash' function !!)... Try to remount it like Read/Write...! But first you need to know the mount points.. To do that type:
Code:
adb shell su
adb mount
You will get some mounts points. So find the partition you want to mount and type:
Code:
adb mount -o rw,remount <mount point> <pertition name>
For example on SGS3 device the mount point of system is /dev/block/mtdblock3. So the command is:
Code:
adb mount -o rw,remount /dev/block/mtdblock3 /system
Are you that you have an insecure kernel and that your bootloader is unlocked...?

First of all, thanks for answering, I'm grateful. :good:
So the anwser is that no, bootloader is not unlocked, since I actually bricked my phone using Asus' unlocking tool apk. It did not unlock the bootloader, and it corrupted my recovery. And that's why I have this invalid kernel message (I guess).
And since I've tried flashing half a dozen roms after that, I don't have root access anymore. So I can't get su commands to work.
I tried your procedure, and here is what I've got :
Code:
C:\Android>adb shell su
/sbin/sh: su: not found
C:\Android>adb shell
~ # su
su
/sbin/sh: su: not found
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /storage type tmpfs (rw,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,relatime,mode=775,gid=1000)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type ext4 (rw,nodev,noati
me,nodiratime,data=ordered)
~ #
So it seems every partition is read/write...

Okay then try thiw command and post the results..!
Code:
adb shell
adb cat /proc/mount
But if don't have root privileges then I think it's difficult to unbrick it...
If you can root it again by custom recovery...?

Yeah I know, that's why I've been struggling. Asus A80 has almost not dev community, so I have close to 0 solution. Bootloader unlocking is acheived with an app, for root I used framaroot...No root package to flash...But since I have another working Asus A80, maybe I can work something out?
So here are the results :
Code:
C:\Android>adb shell
~ # ←[6ncat /proc/mount
cat /proc/mount
cat: can't open '/proc/mount': No such file or directory
~ # ←[6n

Oh you write wrong the command it's:
Code:
adb shell
adb cat /proc/mounts
It's mounts not mount...!

Lol ok now it's working :
Code:
~ # ←[6ncat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p30 /data ext4 rw,relatime,data=ordered 0 0
/dev/block/mmcblk0p30 /sdcard ext4 rw,relatime,data=ordered 0 0
/dev/block/mmcblk0p25 /cache ext4 rw,relatime,data=ordered 0 0
~ # ←[6n

Okay I get condused...! I can't see the /system partition...! I don't know what is going on. I will try to root it again. Can you still boot onto recovery mode and install zips...?

Well that would explain certain things...But I dont' know why it doesn't not show up since I flashed several official roms and it did work the whole process to the end...
I can boot to CWM or TWRP, but not sure if I can flash unsigned code...

I can sign zips for CWM recovery...! But I don't know what files I have to install. I will inform you when I find out. I'm working on it..! :good:
When you boot on CWM can you mount the /system partition form there.I think there is an option tha you can mount /system

Yes it works, I can mount/unmount /system, or at least I have no error message when I do so...
Let me know if you need any other information or to try something else. :good:

Ok first I want you to try again the command:
Code:
adb shell
adb cat /proc/mounts
And then turn off you device and run the command
Code:
adb logcat > C:/Users/xxxx/Desktop/logcat.txt
When you execute this command turn on your device until you the error then open the file an tell me what it says.
To tell you the truth if we can't see the system partition it's difficult to unbrick it becuase we can't root it..!

When I do this, adb is stuck hanging on 'waiting for device'. When I turn it on, it shows splash screen with the 'Invalid Kernel' error message, but not adb access, only fastboot. To get adb access, I boot to cwm with "Fastboot boot recovery.img"...

What is your rom version...?

Just giving a suggestion, you said you tried flashing a new kernel and boot.img but nothing happened. How exactly did you flash these images?

I could not remember so I just flashed this one :
http://dlcdnet.asus.com/pub/ASUS/Mo...ity/WW_PFI_user_11_8_10_24_UpdateLauncher.zip
And CWM log for the flash was :
Code:
Restarting adb...
Finding update package...
Opening update package...
Installing update...
Writing sbl3 image...
Writing rpm image...
Writing sbl2 image...
Writing sbl1 image...
Writing tz image...
Writing aboot image
Writing modem image...
And then it just stopped, no reboot, it is written "script succeeded, result was [t]" under the droid...But I don't know if everything was properly formated and written...
After that, I tried mounts again, here is the result :
Code:
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /storage type tmpfs (rw,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,relatime,mode=775,gid=1000)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type ext4 (rw,nodev,noati
me,nodiratime,data=ordered)
~ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nodev,noatime,nodira
time,data=ordered 0 0
~ #
Do you have everything you need? I can do other stuff if you want. Remember that I have another Padfone Infinity, with root access, if you want to compare partitions...

TheArc said:
Just giving a suggestion, you said you tried flashing a new kernel and boot.img but nothing happened. How exactly did you flash these images?
Click to expand...
Click to collapse
Hello, thanks for your message.
I have access to fastboot, so I just boot the custom recoveries with "fastboot boot recovery.img".
I have cwm, twrmp, 4.1 stock recovery, and 4.4 stock recovery available. I can boot them, but not flash them.

On your other phone can you run the mount commands and post me the result..?
Thank you..!

Ok I just need to charge it a little bit. I will let you know in less than an hour.

Beretta93 said:
Hello, thanks for your message.
I have access to fastboot, so I just boot the custom recoveries with "fastboot boot recovery.img".
I have cwm, twrmp, 4.1 stock recovery, and 4.4 stock recovery available. I can boot them, but not flash them.
Click to expand...
Click to collapse
I believe you're supposed to place the boot.img in the adb folder and do this "fastboot flash boot boot.img" that will flash a new image.

Soft Bricked Android Recovery Options

I have read through XDA and have not found a solution yet, hoping someone has a way to save the data on the device.
The Pixel 3 soft bricked with the latest Blueline version - not unlocked. It is a Verizon device so it blocked flashing (OEM flashing option greyed out in dev tools) without a wipe.
None of the recovery software finds the device that I've tried (Dr. Fone, Recoverit, etc)
ADB pull commands do not pull any files, but does find the directories and correct disk usage.
I cannot run apps with ADB on the device so phone to phone transfers have not worked.
I do get the android USB options when I connect it to another device, but none of them result in the phone being found.
PC finds that a "pixel 3" is connected however does not show any folder structure or mount the device in file explorer.
I have been looking around, reading, and trying to find any way to recover the content with no luck. Any other things I could try/tips/techniques. I am desperate to do whatever I can before wiping the device...
Many thanks.

Bump... am I SOL?

Instead of
Code:
adb pull
try
Code:
mkdir C:\Android-Recovered-Files
adb exec-out "cat /sdcard/*" > "C:\Android-Recovered-Files"
or
Code:
mkdir C:\Android-Recovered-Files
adb exec-out "dd if /sdcard" > "C:\Android-Recovered-Files\recovered.iso"

Thanks for replying.
I tried the commands the ex-out "cat" returns if the directory exists or not the latter one creates a recovery ISO- but they are all 15 bytes in size.
These are the commands I tried since I'm on a mac:
Code:
user$ adb exec-out "dd if /sdcard" > /Applications/android/test/recovered.iso
user$ adb exec-out "dd if /storage" > /Applications/android/test/recovered2.iso
user$ adb exec-out "dd if /dev" > /Applications/android/test/recovered3.iso
The DF results for the device are as follows:
Code:
adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/dm-4 793964 791584 0 100% /
tmpfs 1814200 984 1813216 1% /dev
tmpfs 1814200 0 1814200 0% /mnt
/dev/block/dm-5 184784 184228 0 100% /system_ext
/dev/block/dm-6 412656 411384 0 100% /vendor
/dev/block/dm-7 1904024 1898324 0 100% /product
tmpfs 1814200 0 1814200 0% /apex
/dev/block/sda14 81872 71408 10464 88% /vendor/firmware_mnt
/dev/block/dm-8 116561900 104065324 12365504 90% /data
/dev/block/dm-9 1696 1668 0 100% /apex/[email protected]
/dev/block/loop7 3988 3960 0 100% /apex/[email protected]
/dev/block/loop8 560 532 20 97% /apex/[email protected]
/dev/block/loop9 6568 6540 0 100% /apex/[email protected]
/dev/block/loop10 18148 18120 0 100% /apex/[email protected]
/dev/block/loop11 4488 4460 0 100% /apex/[email protected]
/dev/block/loop12 24640 24608 0 100% /apex/[email protected]
/dev/block/loop13 8072 8044 0 100% /apex/[email protected]
/dev/block/loop14 924 896 12 99% /apex/[email protected]
/dev/block/loop15 844 816 12 99% /apex/[email protected]
/dev/block/loop16 5360 5328 0 100% /apex/[email protected]
/dev/block/loop17 5112 5076 0 100% /apex/[email protected]
/dev/block/loop18 3864 3836 0 100% /apex/[email protected]
/dev/block/loop19 4880 4852 0 100% /apex/[email protected]
/dev/block/loop20 7728 7700 0 100% /apex/[email protected]
/dev/block/loop21 232 92 136 41% /apex/[email protected]
/dev/block/loop22 110924 110896 0 100% /apex/[email protected]
/dev/block/loop23 81320 81292 0 100% /apex/[email protected]
/dev/block/loop24 232 28 200 13% /apex/[email protected]
/dev/block/loop25 332 300 28 92% /apex/[email protected]
/dev/block/loop26 2384 2352 0 100% /apex/[email protected]
/dev/block/loop27 4744 4716 0 100% /apex/[email protected]

I tried this on a different (working Samsung) android device with similar results. An ISO file is generated but on the other device the SDcard directory generates a 957KB ISO file which seems small

As I can see there was a typo in my previous post
Line
Code:
adb exec-out "dd if /sdcard" > "C:\Android-Recovered-Files\recovered.iso"
must be
Code:
adb exec-out "dd if=/sdcard" > "C:\Android-Recovered-Files\recovered.iso"
Equal sign was left out. Sorry for this.

That command seems to do the same action. It creates an empty ISO file.

As your penultimate post shows a partition mounted as /sdcard does NOT exist on your device.
Thought you were smart enough to determine the correct partition's name to get dumped.

Centity said:
I have read through XDA and have not found a solution yet, hoping someone has a way to save the data on the device.
The Pixel 3 soft bricked with the latest Blueline version - not unlocked. It is a Verizon device so it blocked flashing (OEM flashing option greyed out in dev tools) without a wipe.
None of the recovery software finds the device that I've tried (Dr. Fone, Recoverit, etc)
ADB pull commands do not pull any files, but does find the directories and correct disk usage.
I cannot run apps with ADB on the device so phone to phone transfers have not worked.
I do get the android USB options when I connect it to another device, but none of them result in the phone being found.
PC finds that a "pixel 3" is connected however does not show any folder structure or mount the device in file explorer.
I have been looking around, reading, and trying to find any way to recover the content with no luck. Any other things I could try/tips/techniques. I am desperate to do whatever I can before wiping the device...
Many thanks.
Click to expand...
Click to collapse
Verizon doesn't allow their bootloader to be unlocked

jwoegerbauer said:
As your penultimate post shows a partition mounted as /sdcard does NOT exist on your device.
Thought you were smart enough to determine the correct partition's name to get dumped.
Click to expand...
Click to collapse
I tried "/", "*", "/system/", "/dev/", "/Storage/", "/mnt/" all with the same results. If that's the directory how do I identify the partition name associated with the DF results directory?

I think I now know why dumping a partition doesn't work at you:
1. Android isn't rooted: dd must be run as root.
2. The partition to get dumped isn't mounted as RW.
Hence to dump /data partition you'ld run
Code:
adb devices
adb shell "su -c 'mount -o rw,remount -t auto /'"
adb exec-out "su -c 'dd if=/dev/block/dm-8'" > "C:\Android-Recovered-Files\recovered.iso"
FYI:
I've a self-written Android-Backup-Tool what perfectly does the job

jwoegerbauer said:
I think I now know why dumping a partition doesn't work at you:
1. Android isn't rooted: dd must be run as root.
2. The partition to get dumped isn't mounted as RW.
Hence to dump /data partition you'ld run
Code:
adb devices
adb shell "su -c 'mount -o rw,remount -t auto /'"
adb exec-out "su -c 'dd if=/dev/block/dm-8'" > "C:\Android-Recovered-Files\recovered.iso"
FYI:
I've a self-written Android-Backup-Tool what perfectly does the job
Click to expand...
Click to collapse
Unfortunately I don't think that I can install your backup tool in my device's current state, correct?
I'm receiving an error for the 2nd command:
Code:
/system/bin/sh: su: inaccessible or not found
The device is unlocked and USB debug is on. From what I read it looks like su doesn't work unless it's rooted either.

bumping to see if anyone has any idea

try it would list all partition (hopefully ...)
Code:
adb shell
ls -la /dev/block/platform/bootdevice/by-name

ineedroot69 said:
try it would list all partition (hopefully ...)
Code:
adb shell
ls -la /dev/block/platform/bootdevice/by-name
Click to expand...
Click to collapse
Hey, thank you for the suggestion. I wasn't able to get it to work with "by-Name" but was able to get this:
Code:
blueline:/ $ ls -la /dev/block/platform/bootdevice/by-name
ls: /dev/block/platform/bootdevice/by-name: No such file or directory
s -la /dev/block/platform/ <
total 0
drwxr-xr-x 3 root root 60 1972-04-21 12:00 .
drwxr-xr-x 6 root root 2780 2021-02-14 18:47 ..
drwxr-xr-x 3 root root 60 1972-04-21 12:00 soc
s -la /dev/block/platform/bootdevice/ <
ls: /dev/block/platform/bootdevice/: No such file or directory
1|blueline:/ $
To be honest, I'm not sure what I'm looking at here... how can I use this info?

Centity said:
Hey, thank you for the suggestion. I wasn't able to get it to work with "by-Name" but was able to get this:
Code:
blueline:/ $ ls -la /dev/block/platform/bootdevice/by-name
ls: /dev/block/platform/bootdevice/by-name: No such file or directory
ls: /dev/block/platform/bootdevice/: No such file or directory
To be honest, I'm not sure what I'm looking at here... how can I use this info?
Click to expand...
Click to collapse
As you can see both "ls" commands you applied miserably failed due to fact that the named partitions simply don't exist.

the command miserably failed it it work it should look like this .. also what are you trying to backup anyway ??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I'm trying to recover anything that I could from a soft bricked pixel 3. Mostly I'd like to recover my photos/videos/documents that I never backed up to a cloud/other device. I can access some of the settings on the phone and it looks like the images are there - but looks like all of the ADB commands to help me access this data fail.
I'm wondering if this is some kind of encryption/decryption failure.
Long story short - one day I woke up and without any sign the phone was just stuck on "Pixel is starting". I tried deleting apps from the settings menu, clearing cache, but can't access anything on the device no matter what I try.
I'm waiting until March's android updates come out since I can still side-load newer versions of the OS, but am not holding out much hope at this point.
My phone was not rooted and OEM flashing is blocked.

bumping for tips