Related
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.
Trying to get Dexter's native ext2 support working.
I pulled my SD card (8gb) and using GParted within Ubuntu, deleted my FAT32 partition, created 1st partition FAT32 ~7gb, 2nd partition ext2 (1gb), 3rd partition SWAP (64mb)
I understand that with Dexter's 1.1b, when the phne is booted with the card in, it should find the ext2 partition and proceed to move my apps to this partition.
Note, I also tried ext3 in the same partition configuration.
Under memory/sd card sotrage, phone is reading ~6.9GB as expected of the FAT32 partition.
Am I missing a step? Nothing ever gets moved from the phone to the card's ext2 partition.
ext2,3 problem on dexters rom
Sorry first post noob, hopefully im doing this right
I used mini tool partition wizard... i tried ext2 then ext3, made them logical and primary, with the swap partition. (do we need that swap ..i haven't tried it without it).
And the entire memory card wouldn't be recognised/mount at all when turning on the phone. I had to remove the partitions to be able to use the memory card in the normal manner.
is there another step? i was hoping all i had to do was make the partition and it would be done.
help!
did u guys set the ext partition to active?
I did not mark any partition active (none of the many guides on the net say anything about setting partition flags). My layout (per parted) looks like this:
Code:
Number Start End Size Type File system Flags
1 1049kB 6818MB 6817MB primary fat32
2 6818MB 7892MB 1074MB primary ext2
3 7892MB 7959MB 67.1MB primary linux-swap
Which matches every screenshot I have seen of parted/Gparted in any formatting guide.
I did find one that had fat32 marked as lba, but that makes no difference.
R-D said:
I understand that with Dexter's 1.1b, when the phne is booted with the card in, it should find the ext2 partition and proceed to move my apps to this partition.
Note, I also tried ext3 in the same partition configuration.
Click to expand...
Click to collapse
What is the output of "mount" after your phone boots up? Check if it is mounted already. If not try to mount it manually. At least we'll know if the issue is in phone recognizing the partitions.
I realised what i did wrong ..I tried to make the ext2 partition after I 'installed/flashed' dexters rom ...this messed everything up for me.
So I re-did the entire process but made my ext2 partition first. Now its allgood
Don't know if that helps
Sent from my XT720 using XDA App
kousik said:
What is the output of "mount" after your phone boots up? Check if it is mounted already. If not try to mount it manually. At least we'll know if the issue is in phone recognizing the partitions.
Click to expand...
Click to collapse
Here's the default mount output:
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
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock7 /system yaffs2 ro 0 0
/dev/block/mtdblock9 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock8 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock6 /cdrom yaffs2 rw 0 0
tmpfs /tmp tmpfs rw,size=2048k 0 0
tmpfs /skttmp tmpfs rw,size=2048k 0 0
/dev/block/mtdblock0 /pds yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock7 /system/lw yaffs2 ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
none /acct cgroup rw,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
tmpfs /tmp tmpfs rw,size=2048k 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,size=0k,mode=000 0 0
When I try and mount it manually, which device name is preferred? I found the partitions (1 = fat32, 2 = ext2, 3 = swap) as these names:
/dev/block/vold/179:1
/dev/block/mmcblk0p1
/dev/block/vold/179:2
/dev/block/mmcblk0p2
/dev/block/vold/179:3
/dev/block/mmcblk0p3
I can mount partition 1 manually referencing either device name, but when I try to mount partition 2 it says: mount: No such device
I know it is the right device because I can mount the fat32 partition.
Thanks for your help.
Edit: I saw in dateno1's script in the dev thread, he is doing insmod /system/lib/modules/ext2.ko before the mount, I do not have this module (I know he has it in his download package) but should I already have this in /system/lib/modules? Does this exist already for anyone else? Or am I guessing at the wrong thing?
R-D said:
I can mount partition 1 manually referencing either device name, but when I try to mount partition 2 it says: mount: No such device
I know it is the right device because I can mount the fat32 partition.
Edit: I saw in dateno1's script in the dev thread, he is doing insmod /system/lib/modules/ext2.ko before the mount, I do not have this module (I know he has it in his download package) but should I already have this in /system/lib/modules? Does this exist already for anyone else? Or am I guessing at the wrong thing?
Click to expand...
Click to collapse
"No such device" is indication that the kernel module is not loaded properly.
You may have to insmod ext2.ko yourself to get it to work. If you do not have the .ko files, you can download from http://dateno1.egloos.com/27191 yourself and copy to /system/lib/modules. Also you can see this thread http://forum.xda-developers.com/showthread.php?t=929871 for reference.
Okay, mystery solved!
I am missing these modules as I grabbed the "original" 1.1b update (1.1a-update.zip). This original file was missing these modules and had an incorrect overclock module.
I just re-downloaded 1.1b again, and found that if I look in the ZIP file, it has the missing modules I didnt initially get.
In speaking with Dexter, it seems that he updated the 1.1b (1.1a-update.zip) file twice, but kept the same file and version name. So the 1.1b everyone else is using, is newer than the 1.1b I downloaded, as I downloaded it right after it was first posted and missed the next update as it had the same filename.
Essentially, what amounted to 1.1c was also released as 1.1b ...
So lesson is, either redownload and apply the 1.1b update, or update to 1.2 (or newer as they come).
Thanks for your help.
Oh ! Confusing this 1.1a/b/c !
is it nid to do it manually? 1.1b did detect my ext2.. but in 1.2 did not detect.. i try put ext2 and ext4 ald..
Hi, my phone is a samsung galaxy y PRO. Android 2.3.6 rooted
I am trying to disable the keypad backlights...
In here:
\sys\class\backlight\keypad-led\brightness
when i set it to 0, the lights turn off, and after that i change the file permissons to 444 with chmod.
But when i turn off screen and turn on again (stand by mode) the keypad lights turn on again, and when i go to edit the brightness file again, it shows the value 255.
Any solutions?? Also when i try to remove the file (via terminal with SU) i get a operation not permitted message.
Help please.
Thanks!
BTW, i will donate do the guy that makes it work!
Dumb question, is /system set as r/w?
Sent from my LG-P999 using xda premium
Yes, i tryied with total comander, setting system to r/w
Well, then the alternative is copy it via cwm and set the permissions in the script. I can't do it right now, I about to start work, but if no one has handled this by the time I am off and home, about 9:00pm CA time, I will get it set up.
Sent from my LG-P999 using xda premium
Please do that! I will get in here asap. Cya in a few hours.
Thank you for trying to help!
BTW, i tryed to install ClockworkMod via Rom Manager but it says that there is no support with my samsung galaxy y Pro (GT-B5510)...
Ok, i got a temporary ClockworkMod that i can use when needed...
Ok, did some researching of my own for your phone, check your pm.
Ok, this is sort of simple, the file is called "brightness" and its content must be a zero "0". Thats it. The file must be placed in "/sys/class/backlight/keypad-led/".
I don't know how the script you need should look like, but commands to change the file to disable keypad light should be:
echo 0 > /sys/class/backlight/keypad-led/brightness
And the permission command:
chmod 444 /sys/class/backlight/keypad-led/brightness
I know the basic of how it should look and what is needed for it to work, I have a zip I made for myself for copying over ringtones and notifications from a flashable zip. I need to have what partition it's on and (since I guess it's /sys and not /system) be able to mount /sys so Tue file can be copied. The ROM I found it's for your phone. There seems to be very limited data on your phone. Like I said, I have the zip mostly set up, I just need to make sure my mount command will work and for that I need more info. I think I have it but I can't verify that I do.
Sent from my LG-P999 using xda premium
How can i help? I have sent you some info about partition on private msg...
Here is the file... It is zipped, just extract it...
About the partition, Mount command shows: "sysfs /sys sysfs rw, relatime 0 0 "
BTW, i have been checking and the correct path to the file is: "/sys/devices/platform/keypad-led.0/backlight/keypad-led"
The other path i told you before was a link to this one... Sorry...
Complete result of mount command:
$ mount
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,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 /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl9 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp4370 0
/dev/stl10 /cache rfsrw,nosuid,nodev,relatime,vfat,llw,gid/uid/rwx,iocharset=cp437 0 0
/dev/stl6 /mnt/.lfs j4fs rw,relatime 0 0
/dev/stl12 /efs rfsrw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
/dev/stl11 /data rfsrw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
Can you do something with this? I hope so...
hmm, we may have to change our strategy, maybe not. I need to see about a couple of things before I have you try anything.
On an interesting note, I noticed that for /sys the values after realtime are 0 0, I'm mostly familiar with PC's and learn as I go on Android, but if that means what I think it means, that partition can't be modified at all while the system is booted.
On my phone that directory is mounted, but there are no files that I am able to view either via Droid Explorer or Root Explorer.
Do you know anyone else that could join us on this adventure? do you have anything else in mind? I am able to set the file to 0, but there are some events that set it back again to a certain value, like screen off and on, etc...
I dunno why or how, but i set it to 0, i apply chmod 444 but it still changes the file to a certain value...
News?
Yes.
Place the attached script in: /system/etc/init.d/
reboot and you should be good. Found the info here:
http://forum.xda-developers.com/showthread.php?t=1488492&page=4
Some say it works, some say it doesn't.
edit: file attached, just take it out of the zip file.
I don't have the folder /init.d/ in the /system/etc/ folder :|
This means i don't have init.d support...
Ok, i found a way to run it during boot time:
How to run the scripts during the boot using SManager:
Steps to run the scripts during the boot:
1. Test the scripts out completely before start to run on boot.
2. From the SManager tool, select su and boot icon. Exit the application and reboot the phone.
3. If you did not change the SManger config, then you will see the SManager log after the boot. Check if everything is fine. If the scripts run OK many times without any issue, then you can uncheck the option showing SManager log after the boot.
And during boot it writes 0 to the file and it changes its permissions to 444. But even without the permission to write on the file, the system is able to change the value in the file!
Hello here is a guide to Recover Deleted files from internal memory From Any android Phone
You Need
1.Rooted Android phone ( In my case i used Note 2 N7105 )
2.Install busybox ( Note : Install in /system/bin NOT at system/xbin )
3.Drivers Installed on your computer
4.Download The Recovery Tool.rar [ https://www.box.com/s/zw0sfprtlx4dqysd018o ]
5. Download Recuva [ http://www.piriform.com/recuva/download ]. This is the Software going to recover your file , or you can use your favourite Data recovery software . But i suggest Recuva
Steps :
1. Take your rooted phone . Go to Setting->Devoloper Option -> Tick on Stay awake and USB debugging
2.Connect your Phone to the Computer , Let the driver Install .
3.Extract Recovery Tool.rar to c:/ ( You will Find two folder AB and Cygwin )
4.Click Start -> Run ,
Type " CMD " Press Enter
5.Dos Window will open up Now Type " cd c:\ab\ " Press Enter
6. Type " adb devices " Press Enter
** Make sure it returning out Some numbers (IMEI) under list of devices
7.Type " adb Shell mount " Press Enter
Now this is something important , After the command adb shell mount it will give a long List you need to fine "dev/block/mmcblkop"xx" /data(or user data "
Note : The xx can be any number
In N7105 its " mmcblk0p16 " is data Partition .
The last two number (xx) will change from mobile to mobile . Just note the partition name . In my case its " mmcblk0p16 "
8.Close the CMD window . Go to My Computer->C:/->Cygwin->Open Cygwin Terminal
9.Type " export PATH="/cygdrive/c/ab":$PATH " Press Enter
10.Type " adb forward tcp:5555 tcp:5555 " Press Enter
11.Type " adb shell " Press Enter
12.Type " su " Press Enter
13.Grant Superuser Right on your Phone
14.Type " /system/bin/busybox nc -l -p 5555 -e /system/bin/busybox dd if=/dev/block/mmcblk0p16 " Press Enter
15.Minimize the window , Open another cygwin Terminal i.e. My Computer->C:/->Cygwin->Open Cygwin Terminal
16.Type " export PATH="/cygdrive/c/ab":$PATH " Press Enter
17.Type " adb forward tcp:5555 tcp:5555 " Press Enter
18.Type " cd /aa " Press Enter
19.Type " nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p16.raw " Press Enter
20. Now let it Run this will take long time for me it took me One hour to complete
21.After it Compltes Click start->Run Type " cmd " Press Enter
22. Type " cd c:\cygwin\aa\ " Press Enter
23.Type " VhdTool.exe /convert mmcblk0p16.raw " Press Enter
24.Now Close Everything .. Right Click My Comuter->Manage
25.Now Select Storage-->Disk Management.
26.In the menu select Action-->Attach VHD.
27.For Location enter " c:\cygwin\aa\mmcblk0p16.raw " and select the OK button.
28.Right-click on the name (e.g. "Disk 1") to the left of the Unallocated space and select Initialize Disk.
29.Select the GPT (GUID Partition Table) radio button and select the OK button.
30.Right-click on the Unallocated space and select New Simple Volume...
31.In the Wizard select Next>, leave the default for the volume size, select Next>, select a drive letter (e.g. K), select Next>, MAKE SURE to select
the 'Do not format this volume' radio button, select Next>, select Finish.
32.A box will pop up asking you to format the drive. You DO NOT want to format the drive at this time.
33.Right-click on the RAW space and select Format... MAKE SURE to change the File system to FAT32. Set the Allocation unit size dropdown to 'Default.' MAKE SURE that the Perform a quick format checkbox is CHECKED. You do not want to overwrite the entire new drive with all zeroes (0's) and destroy your data. Quick Format means that it will only attempt to destroy the index for the drive by establishing a new index. Without this box checked the Windows operating system will write zeroes (0's) across the entire volume, potentially destroying your data. Select the OK button.
34.A box will pop up saying that Formatting this volume will erase all data on it. That would be doubly true if you actually didn't check the 'Perform a quick format' checkbox. Double check that you actually did check the box and select the OK button.
35.Open the Piriform Recuva application. In the wizard select the 'Next >' button. Select the 'Other' radio button and select Next >. Select the 'In a specific location' radio button and enter: k:\ (assuming K is the drive letter you chose...) Select the Next > button. Select the Enable Deep Scan checkbox.
36.The application may take about an hour to do the 'Deep Scan.'
37.Once the application has returned its results you can choose which files to recover using the checkboxes. Select the 'Recover...' button and choose the location to which you wish to output your files.
No need to Thank me , This is not my work , i just gathered information and some Copy/Paste . Have a nice day
Note : Im not Responsible if you brick your phone . I did this and it worked for me . So im Sharing with you guys .
THANKS A LOT WARTICKLER , Its his work
Galaxy Nexus Users can look at his thread for - > http://forum.xda-developers.com/show....php?t=1994705
:laugh:
Reserved
I might need it
help identifying partitions
capt.nizam said:
7.Type " adb Shell mount " Press Enter
Now this is something important , After the command adb shell mount it will give a long List you need to fine "dev/block/mmcblkop"xx" /data(or user data "
Note : The xx can be any number
In N7105 its " mmcblk0p16 " is data Partition .
The last two number (xx) will change from mobile to mobile . Just note the partition name . In my case its " mmcblk0p16 "
Click to expand...
Click to collapse
Hello, I'm hoping to get some help.. as you can see this is my first post and I'm a total noob. I accidentally flashed my phone this morning have been working all day trying to recover some of the pictures. I've been at it all day and asking for help is my last resort.
When I run the "adb shell mount" command in step 7, I can't find "dev/block/mmcblkop"xx" anywhere. I did also try the same command with a captal S in Shell like in your post, but that seemed to just bring up help commands (I did look for mmcblkop in there too, nothing). I looked through all sorts of posts and searched for another way to identify the userdata partition for my phone, but couldn't find any other way to do it. The closest I found was this post ( http://forum.xda-developers.com/showthread.php?p=28115791 ) but due to my lack of knowledge, I don't know what program those commands work in. I tried running:
"su
ls -l/dev/block/platform/omap/omap_hsmmc.0/by-name/" command in cygwin terminal and a terminal emulator on my nexus but neither worked.
Eventually I just guessed and used "mmcblk0p12" since it was listed in the post I linked, and followed through the rest of your directions. It did work, but it seems like the partition I recovered didn't have any of my photos in it. It was a just a bunch of zip files containing folders with what seemed to be application info, lots of pictures of ads used in apps and app icons. So this gives me hope that maybe I can recover some of my data if I could locate the correct partition. ANY help would be greatly appreciated!
I have a Verizon Galaxy Nexus CDMA running 4.1.1
Kernel Version 3.0.31-g396c4df
Build number JRO03O
I used WugFresh Nexus Root Toolkit v1.6.2 this morning to unlock and root phone.
This is the data that is returned when I run the "adb shell mount" command:
c:\AB>adb shell mount
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
/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 ro,relatime,barrier
=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/efs /factory ext4 ro,relatime,barrier=1
,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache ext4 rw,nosuid,nodev,noati
me,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data ext4 rw,nosuid,nodev,noa
time,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,d
efault_permissions,allow_other 0 0
/dev/block/dm-0 /mnt/asec/com.discoverfinancial.mobile-1 ext4 ro,dirsync,nosuid,nodev
,noatime,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/com.duckduckgo.mobile.android-1 ext4 ro,dirsync,nosuid,node
v,noatime,barrier=1 0 0
/dev/block/dm-2 /mnt/asec/jp.co.canon.bsd.android.aepp.activity-1 ext4 ro,dirsync,nos
uid,nodev,noatime,barrier=1 0 0
Again, any pointers would be welcome. Thank you for reading.
Same Issue
I've been a stalker of Xda since I received my Nexus 7 a month ago, finally have a problem i can't just search my way through. The fact the file system has that stupid 0 folder and inside really messed me up.... when I deleted it. I'd like it back. and I need help.
I have the same issue as the person above, running adb Shell mount lists commands but adb shell mount shows almost the exact same thing as the above.
c:\AB>adb shell mount
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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 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
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,noatime,user_xattr
,acl,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw,nosuid,nodev,noatim
e,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=writeback,noauto_d
a_alloc,discard 0 0
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw,nosuid,nodev,noatime
,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=writeback,noauto_da
_alloc,discard 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_i
d=1023,default_permissions,allow_other 0 0
After running
[email protected] /aa
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p38.raw
(the 38 at the end is because I'm on a different device) I get
$ nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p38.raw
0 B 0:00:00 [ 0 B/s] [<=> ]
and than about three seconds later, i get
[email protected] /aa
again. Help?
thanks!
for phones unable to connect via "Mass Storage"...
hi all
Thanks to all those that made this recovery option possible!
What I learned:
i have a razr hd, latest update, therefore no mass storage conx ability, so the method described in this thread is CRUCIAL.
different phones have different data partition labels....long story short, install DiskDigger from PlayStore, open DiskDigger, allow superuser once, a list of "blocks" will be shown, specific to your phone.
look for the " /data " line
you want the info within the parentheses " (...) " after " /data " ;
i replaced the data block in instruction #14
[14.Type " /system/bin/busybox nc -l -p 5555 -e /system/bin/busybox dd if=/dev/block/mmcblk0p16 " Press Enter]
with my specific data block, or " /dev/block....... "
I have received a lot of help from this forum and hope this helps someone else
bad news for me is that I still lost a lot of my jpg's, but this thread helped me recover what little I could
Thanks for the Guide!
However i just manage to recover those photo and files which located in Whatsapp folder and Wechat Folder, I did not manage to recover all photo from Camera Folder.
Anyone encounter the same issue with me ?
1 Connect your Android device to the computer
You need to enable USB debugging on your Android phone. According to the Android OS version running on your device, choose a way to enable it.
1) For Android 2.3 or earlier: Enter "Settings" < Click "Applications" < Click "Development" < Check "USB debugging"
2) For Android 3.0 to 4.1: Enter "Settings" < Click "Developer options" < Check "USB debugging"
3) For Android 4.2 or newer: Enter "Settings" < Click "About Phone" < Tap "Build number" for several times until getting a note "You are under developer mode" < Back to "Settings" < Click "Developer options" < Check "USB debugging"
2 Scan your Android device for lost data
After enabling the USB debugging, you'll get the window as follows. Click "Start" to anaylize your device.
3 Preview and recover contacts, messages, photos and video from Android
When the scan completes, you'll get a scan result below. You can preview SMS, contacts and photos scanned out. Choose those you need and click "Recover" to preserve them on your computer.
Read more:
Ruuker said:
Hello, I'm hoping to get some help.. as you can see this is my first post and I'm a total noob. I accidentally flashed my phone this morning have been working all day trying to recover some of the pictures. I've been at it all day and asking for help is my last resort.
When I run the "adb shell mount" command in step 7, I can't find "dev/block/mmcblkop"xx" anywhere. I did also try the same command with a captal S in Shell like in your post, but that seemed to just bring up help commands (I did look for mmcblkop in there too, nothing). I looked through all sorts of posts and searched for another way to identify the userdata partition for my phone, but couldn't find any other way to do it. The closest I found was this post ( http://forum.xda-developers.com/showthread.php?p=28115791 ) but due to my lack of knowledge, I don't know what program those commands work in. I tried running:
"su
ls -l/dev/block/platform/omap/omap_hsmmc.0/by-name/" command in cygwin terminal and a terminal emulator on my nexus but neither worked.
Eventually I just guessed and used "mmcblk0p12" since it was listed in the post I linked, and followed through the rest of your directions. It did work, but it seems like the partition I recovered didn't have any of my photos in it. It was a just a bunch of zip files containing folders with what seemed to be application info, lots of pictures of ads used in apps and app icons. So this gives me hope that maybe I can recover some of my data if I could locate the correct partition. ANY help would be greatly appreciated!
I have a Verizon Galaxy Nexus CDMA running 4.1.1
Kernel Version 3.0.31-g396c4df
Build number JRO03O
I used WugFresh Nexus Root Toolkit v1.6.2 this morning to unlock and root phone.
This is the data that is returned when I run the "adb shell mount" command:
c:\AB>adb shell mount
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
/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 ro,relatime,barrier
=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/efs /factory ext4 ro,relatime,barrier=1
,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache ext4 rw,nosuid,nodev,noati
me,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data ext4 rw,nosuid,nodev,noa
time,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,d
efault_permissions,allow_other 0 0
/dev/block/dm-0 /mnt/asec/com.discoverfinancial.mobile-1 ext4 ro,dirsync,nosuid,nodev
,noatime,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/com.duckduckgo.mobile.android-1 ext4 ro,dirsync,nosuid,node
v,noatime,barrier=1 0 0
/dev/block/dm-2 /mnt/asec/jp.co.canon.bsd.android.aepp.activity-1 ext4 ro,dirsync,nos
uid,nodev,noatime,barrier=1 0 0
Again, any pointers would be welcome. Thank you for reading.
Click to expand...
Click to collapse
I know this is an old post, but I see no one answered your question.
Hers your answer here "/dev/block/platform/omap/omap_hsmmc.0" so I am going to guess that you use omap_hsmmc.0 instead of the mmclk0p
Seeing every phone is different and they don't all have user data at mmclk0p or have the samething dump out with adb shell mount.
This is what I did to find the correct info for my userdata.
Now when you are in terminal and type adb shell mount you may get stuff like this
/dev/block/platform/msm_dscc.1/by-name/userdata
Click to expand...
Click to collapse
Now to find the info needed to your user data, you will need terminal on your phone or, see i already had cygwin terminal open and connected to the phone with adb shell. I typed SU to become super user. I then followed this thread here http://forum.xda-developers.com/showthread.php?t=1743872 and used this command to get the info I needed( the command is wrong in that thread so I will correct it here.
Tpye this in terminal now
Code:
ls -l /dev/block/platform/omap/omap_hsmmc.0/by-name/
It should spit out something like this now
lrwxrwxrwx root root 2012-07-01 01:03 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-07-01 01:03 cache -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-07-01 01:03 dgs -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-07-01 01:03 efs -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-07-01 01:03 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-07-01 01:03 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-07-01 01:03 param -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-07-01 01:03 radio -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-07-01 01:03 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-07-01 01:03 sbl -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-07-01 01:03 system -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-07-01 01:03 userdata -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-07-01 01:03 xloader -> /dev/block/mmcblk0p1
Click to expand...
Click to collapse
In this case you will see userdata is mmcblk0p12. This is for a Nexus. I am using a Galaxy S3 and it works on it too. Mine was mmcblk0p15 instead. I hope this help some people out.
I had success recover deleted files from android phone memory card with an android phone data recovery guide:
how to recover data from android phone
The tutorial is really helpful and easy to follow. I recommend that you try it if you need to recover files from android phone.
Addings
Hi, first of all - thanks!
This saved all my vacation pictures!
Note: the link box.com/s/zw0sfprtlx4dqysd018o is obsolete
You can download cygwin and Android SDK separately instead, it will change some of the paths.
It doesnät matter if Busybox is in /bin or /xbin
One tricky thing about some Xperia phones:
These phones have a "virtual SD card where most of the deleted files are stored.
I don't understand why - there is no SD card slot - but that's how the design is made.
Nevertheless. When running the df command you'll notice this, and your files wont be stored in /data
My files were found in something like /SD/179:16
Good luck!
UNDELETE
There an android app called undelete, i found it on blackmart it might do the job for you
A big THANKS
tool.rar link is outdated can u upload it again
Thanks
Great guide.....
After doing most of it I realised I didn't have enough space to create my raw file.....
So now I don't know what I need to free up is it the d:/ or c:/ or my phone.....
I have the same problem
I have tha same problem.
According to the instruction I can't copy the raw file.
I check the path in my computer and I foud a raw file empty.
I have confirmed the partition name: mmcblk0p12.
Finally, have you solved your problem?
Va1ha1a said:
After running
[email protected] /aa
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p38.raw
(the 38 at the end is because I'm on a different device) I get
$ nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p38.raw
0 B 0:00:00 [ 0 B/s] [<=> ]
and than about three seconds later, i get
[email protected] /aa
again. Help?
Click to expand...
Click to collapse
is it possible to recover deleted titaniumbackup folders like this??
I wanna try this to get back my lost Data from Xperia Z Internal SD Card but i cant download it from https://www.box.com/s/zw0sfprtlx4dqysd018o
Maybe anyone got another link?
hi,
my device is Xperia Z1 rooted & locked bootloader, FW KK .757... when i try to do the command i get this adb wait-for-device - block until device is online
so i didn't find anything after typing ''adb Shell mount'' looks like it shows my phone as offline, but i followed all the steps correctly! usb debugging + screen awake!
why i got this?
thx
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.