Related
So, nobody answered and I had to create this topic.
1) I have RC29
2) When I try to use the MOUNT command in pTerminal I ALWAYS get:
roootfs / rootfs ro 0 0
etc.
3) When I use
mount -o remount rw /system
I ALWAYS get:
mount: Operation not permitted.
4) When:
cd /system
cat /sdcard/recovery_testkeys.img > recovery.img
I ALWAYS get:
cannot create recovery.img: read-only file system
PS All files are there. The update's name is written right - update.zip. I've used pTerminal.
So, do I have the Root Access or not and am i doing smth wrong??
Appreciate any help\advices.
Thanks.
Have you tried doing this through the telnetd way?
BAD_BOY_KIEV said:
So, nobody answered and I had to create this topic.
1) I have RC29
2) When I try to use the MOUNT command in pTerminal I ALWAYS get:
roootfs / rootfs ro 0 0
etc.
3) When I use
mount -o remount rw /system
I ALWAYS get:
mount: Operation not permitted.
4) When:
cd /system
cat /sdcard/recovery_testkeys.img > recovery.img
I ALWAYS get:
cannot create recovery.img: read-only file system
PS All files are there. The update's name is written right - update.zip. I've used pTerminal.
So, do I have the Root Access or not and am i doing smth wrong??
Appreciate any help\advices.
Thanks.
Click to expand...
Click to collapse
You have to use the telnetd command first to exploit the root access. There are other threads that tell you how. Basically telnet into the phone then execute the commands.
If you look in your PM box. i sent you a link with step by step instructions yesterday!
Cannot root RC29 - read only file error
Hi,
I did it also thru Telnet but get the same message...any tips to root the phone? I am still sending that automatic SMS...
Thanks, M
If you have any suggestions on making this guide better or to correct any mistakes I may have made please let me know.
This guide is intended for any Linux OS and includes detailed instructions. It should work with another Linux OS although I have only verified these steps using Ubuntu 9.10 aka Karmic. includes detailed instructions. This will work with software versions 1.29.651.1 and 1.56.651.2 (aka Android 1.5). It will cover the steps necessary to root, flash the new recovery image, create a full backup. I am not responsible for any damage done to your phone using this guide. Root at your own risk.
Step 1: Download the Android SDK from http://developer.android.com/sdk/index.html The linux file is called android-sdk_r06-linux_86.tgz. Extract the files to your home user directory so that you now have the folder /home/USERNAME/android-sdk-linux. Please note you must replace USERNAME with your own.
Step 2: Download the asroot2 exploit file from http://forum.xda-developers.com/attachment.php?attachmentid=244212&d=1257621154 Extract asroot2.zip to /home/username/android-sdk-linux/tools folder.
Step 3: Download the Hero recovery image from http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1g DO NOT OPEN. Simply place this file in /home/username/android-sdk-linux/tools as well.
Step 4: USB Debugging should be disable before connecting your phone via the USB cable. Connect your phone and now enable USB Debugging.
Step 5: Open a terminal found under Applications>Accessories>Terminal
Step 6: You will now enter a series of commands which I will place in code boxes to indicate the entire command.
A.
Code:
cd ~/android-sdk-linux/tools
B.
Code:
sudo su
C.
Code:
./adb push asroot2 /data/local/
D.
Code:
./adb shell
E.
Code:
chmod 0755 /data/local/asroot2
F.
Code:
/data/local/asroot2 /system/bin/sh
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#Now for a few last commands.
G.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
H.
Code:
cd /system/bin
I.
Code:
cat sh > su
J.
Code:
chmod 4755 su
You are now officially rooted. A few more steps and you will have flashed the recovery image.
K.
Code:
exit
L.
Code:
exit
This will return the command line to ~/android-sdk-linux/tools.
M.
Code:
./adb push recovery-RA-heroc-v1.6.2.img /sdcard
N.
Code:
./adb shell reboot
This will cause to power off then back on automatically. Wait till the phone is fully booted to continue.
O.
Code:
./adb shell
P.
Code:
su
Q.
Code:
cd /sdcard/
R.
Code:
flash_image recovery recovery-RA-heroc-v1.6.2.img
FLASHING TO THE RECOVERY TAKES SEVERAL SECONDS-- BE PATIENT. ENTER THE NEXT COMMAND ONLY AFTER THE COMMAND PROMPT RETURNS TO THE # (ROOT SYMBOL).
S.
Code:
reboot recovery
Step 8: This is the last command; You may now close the terminal. It will cause your phone to boot into recovery mode; it should take no longer than 30 secs.
The third option on the list is "- Backup/Restore"; select it. Now, select the first option "- Nand backup". The phone will prompt you to press HOME to confirm which is want you want to do. The backup will begin. You will see the screen say, "Performing backup : .........." When done, the bottom of the screen will say "Backup complete!" and you will be given the menu options again. Go back to the main menu and select reboot system.
Step 9: Once your phone is fully booted, mount the sdcard. You will see a folder called "nandroid"; I highly recommend you copy this to your pc in case you lose your sdcard data or reformat it. Your phone is rooted, 100% backed up, and ready to install a custom rom if you wish!
[email protected]:/home/lepri/android-sdk-linux/tools# sudo su lepri
[email protected]:~/android-sdk-linux/tools$ su root
Password:
[email protected]:/home/lepri/android-sdk-linux/tools# /adb push asroot2 /data/local/
bash: /adb: No such file or directory
[email protected]:/home/lepri/android-sdk-linux/tools# ./adb push asroot2 /data/local/
828 KB/s (74512 bytes in 0.087s)
[email protected]:/home/lepri/android-sdk-linux/tools# ./adb shell
$ chmod 0755 /data/local/asroot2
$ /abd shell
/abd: not found
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/493/fd/3
SUCCESS: Enjoy the shell.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cd /system/bin
# cat sh > su
# chmod 4755 su
# exit
$ exit
[email protected]:/home/lepri/android-sdk-linux/tools# ./adb shell
$ su
# cd /sdcard/
# flash_image recovery recovery-RA-heroc-v1.2.3.img
Thanks for guide but I dont think it worked for me, HTC logo stays on but thats it... have to pull out battery to start the phone phone works but no joy with recovery image ((
I have HTC hero with sim(If this info any use to you)
lepri13 said:
[email protected]:/home/lepri/android-sdk-linux/tools# sudo su lepri
[email protected]:~/android-sdk-linux/tools$ su root
Password:
[email protected]:/home/lepri/android-sdk-linux/tools# /adb push asroot2 /data/local/
bash: /adb: No such file or directory
[email protected]:/home/lepri/android-sdk-linux/tools# ./adb push asroot2 /data/local/
828 KB/s (74512 bytes in 0.087s)
[email protected]:/home/lepri/android-sdk-linux/tools# ./adb shell
$ chmod 0755 /data/local/asroot2
$ /abd shell
/abd: not found
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/493/fd/3
SUCCESS: Enjoy the shell.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cd /system/bin
# cat sh > su
# chmod 4755 su
# exit
$ exit
[email protected]:/home/lepri/android-sdk-linux/tools# ./adb shell
$ su
# cd /sdcard/
# flash_image recovery recovery-RA-heroc-v1.2.3.img
Thanks for guide but I dont think it worked for me, HTC logo stays on but thats it... have to pull out battery to start the phone phone works but no joy with recovery image ((
I have HTC hero with sim(If this info any use to you)
Click to expand...
Click to collapse
You have a GSM HERO not a CDMA. This guide is intended for CDMA heros only.
Updated for recovery 1.5.1 image.
I keep getting the same error of insufficient permissions for device. What am I doing wrong? I disable USB debugging before I plug my phone in. Then I plug my phone in and enable USB debugging and then actually connect my mounting the SD card.
Edit: Ok. I found how to fix the insufficient permission problem...
Code:
./adb kill-server
sudo ./adb start-server
That will get your permissions correct but once I did that, I ran across a new error once I did ./adb shell the second time after the "chmod 0755".
Code:
[email protected]:/home/justin/android-sdk-linux_86/tools# ./adb push asroot2 /data/local/
711 KB/s (74512 bytes in 0.102s)
[email protected]:/home/justin/android-sdk-linux_86/tools# ./adb shell
$ chmod 0755 /data/local/asroot2
$ ./adb shell
./adb: not found
Whats wrong now?
I couldn't edit my post anymore but I found that it works if I just skip the second ./adb shell. It just caused problems for me because I was already in shell and was coming up with errors. I skipped it and my root smoothly after that.
Part I skipped...
You must replace username with your own actual username.
C. "./adb push asroot2 /data/local/"
D. "./adb shell"
E. "chmod 0755 /data/local/asroot2"
F. "./adb shell"
G. "/data/local/asroot2 /system/bin/sh"
For some reason the forums are letting me edit my posts. I know I'm wasting space but I would like to give credit to jnwhiteh for the ./adb fix. I searched for it and found it in a different part of the forums.
Problem flashing recovery
Thank you for the Howto.
I have no problem with the howto, until i try to flash recovery. It seems its going ok without error messages, but when i try to boot in recovery mode it does'nt work. Remains with the HERO logo in the screen and nothing happens.
Anyone can help me.
goshi0 said:
Thank you for the Howto.
I have no problem with the howto, until i try to flash recovery. It seems its going ok without error messages, but when i try to boot in recovery mode it does'nt work. Remains with the HERO logo in the screen and nothing happens.
Anyone can help me.
Click to expand...
Click to collapse
You're not giving the terminal enough time to flash the image probably. Give it like 10 secs to be on the safe side.
flash image not found
everything works fine up until i get to the part where you actually flash the recovery image, at which point i get an error reading : flash_image: not found
this is my code for the last part.
"[email protected]:/home/amills/android-sdk-linux/tools# ./adb push recovery-RA-heroc-v1.5.2.img /sdcard
1106 KB/s (3356672 bytes in 2.962s)
[email protected]:/home/amills/android-sdk-linux/tools# ./adb shell reboot
[email protected]:/home/amills/android-sdk-linux/tools# ./adb shell
# su
# cd /sdcard/
# flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image: not found"
goyanks said:
everything works fine up until i get to the part where you actually flash the recovery image, at which point i get an error reading : flash_image: not found
this is my code for the last part.
"[email protected]:/home/amills/android-sdk-linux/tools# ./adb push recovery-RA-heroc-v1.5.2.img /sdcard
1106 KB/s (3356672 bytes in 2.962s)
[email protected]:/home/amills/android-sdk-linux/tools# ./adb shell reboot
[email protected]:/home/amills/android-sdk-linux/tools# ./adb shell
# su
# cd /sdcard/
# flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image: not found"
Click to expand...
Click to collapse
is the phone fully booted when you run the flash_image command?
theresthatguy said:
is the phone fully booted when you run the flash_image command?
Click to expand...
Click to collapse
Yes, sense has booted up and everything, if this matters, my current recovery image is Amon Ra v1.2.3 and i had Eclair 2.1 v1.8 on it up until last night, as of now i have Fresh 1.1
If you're going to transfer the recovery image to the sdcard using adb push (as opposed to using usb-storage to drag/drop) you need to make sure that usb storage is turned off and the sdcard is mounted when you push the file.
My guess is that the sdcard wasn't mounted, and the file went to the (empty) /sdcard directory. Then when the sdcard is mounted, you can't see it. If you just reboot and do:
Code:
./adb shell
cd /sdcard
ls
does the recovery image file show up in the list?
I'm assuming that "flash_image: not found" means that the image file isn't where you're telling it to look.
buck2202 said:
If you're going to transfer the recovery image to the sdcard using adb push (as opposed to using usb-storage to drag/drop) you need to make sure that usb storage is turned off and the sdcard is mounted when you push the file.
My guess is that the sdcard wasn't mounted, and the file went to the (empty) /sdcard directory. Then when the sdcard is mounted, you can't see it. If you just reboot and do:
Code:
./adb shell
cd /sdcard
ls
does the recovery image file show up in the list?
I'm assuming that "flash_image: not found" means that the image file isn't where you're telling it to look.
Click to expand...
Click to collapse
no, it's there, when i tyle "ls", i get the following list returned.
Code:
# ls
2.1v1.8_heroc_7_signed.zip flashrec-1.1.3-20091107-2.apk
BetterTerm15.apk fresh-cdma-hero-1.1.zip
DCIM google_maps_navigation
HTC Sync media
LOST.DIR nandroid
Music prettybattery-googlecode-com
PicSay recovery-RA-heroc-v1.2.3.img
ToggleSettings recovery-RA-heroc-v1.5.2.img
Wallpaper rosie_scroll
aHome rssreader
albumthumbs tmp
aosp_heroc_20091217d.zip uloops
dolphinbrowser_gestures waze
furthermore, when i try to flash the recovery image now, i get no such error, instead I get a seemingly infinitely repeating series of "out of memory errors"
Code:
# flash_image recovery recovery-RA-heroc-v1.5.2.img
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: read error at 0x00080000 (Out of memory)
mtd: read error at 0x000a0000 (Out of memory)
mtd: read error at 0x000c0000 (Out of memory)
mtd: read error at 0x000e0000 (Out of memory)
mtd: read error at 0x00100000 (Out of memory)
mtd: read error at 0x00120000 (Out of memory)
mtd: read error at 0x00140000 (Out of memory)
mtd: read error at 0x00160000 (Out of memory)
mtd: read error at 0x00180000 (Out of memory)
mtd: read error at 0x001a0000 (Out of memory)
mtd: read error at 0x001c0000 (Out of memory)
mtd: read error at 0x001e0000 (Out of memory)
mtd: read error at 0x00200000 (Out of memory)
mtd: read error at 0x00220000 (Out of memory)
mtd: read error at 0x00240000 (Out of memory)
errors
I'm going to try rebooting the device and start from there. :|
this is bizzare, the first two times i attempted this (both times in Kubuntu 10.04 Alpha), i was able to flash the image with no trouble whatsoever.
------------------------------------------------------
i dont know what was up, fixed it and 1.5.2 is working great. thanks for the advice everyone. : )
problem :-(
Here's where I get to in the procedure, what's going on?
Code:
$ chmod 0755 /data/local/asroot2
$ /data/local/asroot2 /system/bin/sh
[1] Killed /data/local/asroot2 /system/bin/sh
$
Many thanks
David
swatsbiz said:
Here's where I get to in the procedure, what's going on?
Code:
$ chmod 0755 /data/local/asroot2
$ /data/local/asroot2 /system/bin/sh
[1] Killed /data/local/asroot2 /system/bin/sh
$
Many thanks
David
Click to expand...
Click to collapse
Do you have a non-Sprint hero? If say I recommend you check out the rooting a non-sprint hero thread.
Thanks so much for this great howto!
Looking down the road..... can the phone be unroot/restored from linux?
diordnahero said:
Thanks so much for this great howto!
Looking down the road..... can the phone be unroot/restored from linux?
Click to expand...
Click to collapse
After you flash a custom rom, no. You will need to RUU from a Windows box.
Doesn't work from a VM or from Mac Bootcamp either. Need to have a Windows-only craputer.
I have been googling far too long for an explanation of how to change the Read, Write, Execute options on individual system and data apps, when I remembed how fast someone usually answers my n00b questions here. It is not even clear to me what the differences are between the Write and Execute options. Can someone give me a link to a tutorial regarding this?
I did read the suggested threads, not helpful, and one I didn't understand about remounting the "entire /system partion to read-write".
thanks. d
To be more specific, I want to change the permission on certain system apps so I can uninstall them.
If your phone is rooted then you need a file manager that will remount the system partition as RW ( read write). Or you can use adb with your first command being adb remount.
Sent from my HTC Vision using XDA App
As ESKIMOn00b started to explain, the process of removing apps from the /system partition isn't a matter of individual file or folder permissions. Android secures the /system partition by preventing it from being written to under normal circumstances. If you have rooted your device then you have the ability to become the root user and run most if not all commands.
ADB provides a nice convenience command, 'adb remount', that will allow you to modify the /system partition. This command will only work if you have root user privileges but will unlock all of the apps for you to remove. Be careful though, you shouldn't just delete APK's directly out of /system/app as the package manager in Android might not keep up with your deletions. The best way to go about it (after remounting /system read/write) is to use the 'pm uninstall' command:
# pm uninstall com.myapp
To figure out the package names you can use 'pm list packages' and it will dump a huge list of all installed apps on the device. You'll need to hunt through and find the right ones. Most developers use obvious naming schemes such as Amazon's MP3 Store: com.amazon.mp3.
Hope this helps!
-ObsidianX
I have root and some recent experience w/the AndroidSDK. Using the SDK on my SonyEricsson phone:
c:\Users\dSpr> cd c:\AndroidSDK\tools
c:\AndroidSDK\tools>dir
{list}
c:\AndroidSDK\tools>adb devices
{0123456789ABCDEF device}
c:\AndroidSDK\tools>adb ls /system/app
{list}
c:\AndroidSDK\tools>adb shell
$ pm list packages
{list}
Note the shell command produces a $ instead of a #, but it still gives me a list.
But w/the $ and the command adb remount this:
$adb remount
adb remount
adb: permission denied.
If: tools>adb remount
This: remount failed; Operation not permitted
Same operation w/my QT7 and tools>adb shell produces a #. In fact, I don't even have to I don't have to use the adb remount command on my first uninstall, just
#rm /system/app/{app}.apk
#pm uninstall {package name}
I don't recall that I used the remount command between uninstalls-don't think I did or I would have noted it because I was keeping careful track of what I was doing. I can't test it because I have no apps on that device to uninstall.
Get the same result when using the terminal with the su command on the phone itself.
This is why I thought I had to change the Read/Write permissions.
What are you telling me that's not getting thru.
Thank you both very much.
d
to remount your system, you can try this
Code:
adb shell
Code:
su
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
hesperides said:
to remount your system, you can try this
Code:
adb shell
Code:
su
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Click to expand...
Click to collapse
Nope. adb shell results in a $. su results in a su w/out the $ and after some (close to a minute) hesitation: Permission denied $
Debugging is on, as is mock locations. I am also having the exact same problem with my new enTourage Pocket eDGe, but it isn't that bothersome because it doesn't have a lot of garbage like the cell phone.
d
To those of you who followed link here: don't rush ahead and execute adb command. Read the thread in its entirety, since it contains typos and trial n error.
Gl, hf
Hi. I've been stupid. U may flame me but plz also provide some advice to swallow it with.
I followed bad advice and flashed cwm 5xxxx. After that tried to run superwipe, which got stuck after a few steps. To my horror i realized i had run it from internal. Of course it wiped itself and i got stuck mid-partinioning i think.
Since cwm don't read ext sd i tried to push new recovery via easyflasher, but i can't seem to get a driver that lets my pc interact with the device.
Instead discovered i have adb acess if connected when device is in cwm. From there tried to run PERI v 0.4. At first step, trying to push recovery i get a message of no space available. I think this is due to borked partitioning with superwipe. I guess I can repartition with cwm, but now I've messed so much up I don't wanna do anything more without proper advice.
Thanks
bump
If you have adb access, then use it to push a new rom.
"adb push {shiny new rom or recovery} /sdcard/"
You might have to change /sdcard/ to whatever cwm 5x uses?
Then you can just flash it from cwm.
EDIT: I just saw that you have the tf101G - it might work, but you probably have to find the right rom or recovery.
sent from my transformer
gee one said:
If you have adb access, then use it to push a new rom.
"adb push {shiny new rom or recovery} /sdcard/"
You might have to change /sdcard/ to whatever cwm 5x uses?
Then you can just flash it from cwm.
EDIT: I just saw that you have the tf101G - it might work, but you probably have to find the right rom or recovery.
sent from my transformer
Click to expand...
Click to collapse
Good advice, problem is that im not very savvy. How do i execute that command and what if i need to repartition the internal sd?
When running oneclickrecovery i get following prompts:
Uh-oh! I'm softbricked or have a recovery-bootloop! D:
Never fear sir and/or madam! PERI is here! -trips-
Adb needs to be fully working for this to work properly.
Note that this will wipe your current recovery.
Also note that this may not work, don't taze me bro!
Run? Close if you want to cancel.
Press any key to continue . . .
List of devices attached
0123456789ABCDEF recovery
If you see your device here this will work, if not fix adb.
Press any key to continue . . .
running fix...
dd: writing '/dev/block/mmcblk0p3': No space left on device
4097+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.345431 seconds, 5.8MB/s
rebooting tab, if at any step it doesn't reboot turn off and turn back on
Once back into an adb possible state continue...
Press any key to continue . . .
Pushing new recovery...
1331 KB/s (4599884 bytes in 3.374s)
Running wolf's exploit...
mv: can't rename '/data/local/tmp': No such file or directory
Going...
ln: /data/local/tmp: No such file or directory
Done!
Now lets reboot your TF again...
Continue when back into ADB again...
Press any key to continue . . .
Flashing new recovery...
dd: can't open '/sdcard/recoveryblob': No such file or directory
Done!
Continue to reboot your tab, do the button combination to test recovery.
(Hold volume-down as it's rebooting and press vol-up to enter recovery)
Press any key to continue . . .
Hopefully that fixed everything!
Press any key to continue . . .
Of course nothing was fixed and I still have cwm 5xxx which can't flash from ext sd. If I can only get another recovery I can flash any rom and that's that.
In device manager the device shows up as android adb interface when booted into cwm. I also have a device named android composite adb interface, but with a warning sign on it.
This is getting tiresome...
Edit: tried using quick adb pusher, but get message that i cant mount as r/w. In cwm cant mount data or sdcard/.android_secure.
Fun thing is I dont have root either.
It looks like your partitions are unformatted.
I think you need to get to a root shell via adb in recovery
- put your phone on recovery and plug into your computer
- type "adb remount" (you might get an error) then type "adb shell"
- you'll be in a terminal shell
- type "mount" to see how/what your sdcard is doing. Look for the line that has /sdcard on it. It might be something like /dev/block/mmcblk0p1 mounted at /sdcard blah blah...
- now to format your sdcard, type "mke2fs /dev/blah/whereever/your/sdcard/is/mounted/from/above"
- allow it to complete and type "exit". you might have to reboot your tab to get everything to remount
- once your tqab is back in recovery, type on your computer "adb push [some new recovery that uses the external sdcard or a new rom] /sdcard"
- if you have recovery bootloops, google around, there is a fix that wipes the reboot command from the misc partition. You can type it from an adb shell it's something like "dd if=/dev/block/zero of=/be/carefule/because/you/have/a/tf101G bs=1 count=13"
- Google is your friend. Linux is your friend. This is a bit of a high level overview, so you'll have to fill in the details yourself. Keep in mind that I don't have a tf101G and I never tried this before (a benefit of never using superwipe!)
Good luck!
OK. I'd like to try the method u describe but as I mentioned I'm really not tech savvy. I don't even know how to get to the point where I type "adb remount". Do I just open a cmd prompt? Tried that - didn't work.
I have downloaded sdk manager for when I did some stuff with my phone earlier and have the basic packages installed.
Are you on Windows? I think it's a path issue. You either need to put everything in the same folder and run everything from there or put adb in your path. I don't use Windows, so that's probably the best advice I can give you. "which adb" and "echo $PATH" probably won't work in Windows like they do in linux.
Ehm.. too techie answer for me to comprehend.
Yes I'm on win 7.
Put what in same folder as what?
Run from there by right clicking empty space in folder and choosing cmd?
What do you mean by putting adb in my path?
For some reason, lots of people on windows just put the recovery/rom and adb in the same folder and run it from there in the command prompt. Put it all in one place and use the cd command in the terminal to get there.
sent while running with scissors
Lol. Don't cut urself man. I might need your help again
I'll try later when kids asleep.
Allright. Learning curve is steep but im clinging on to it:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount failed: Success
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # 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)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nosuid,nodev,relatime,user_xattr,ac
l,barrier=1,data=ordered)
~ # mke2fs /dev/block/mmcblk0p2
mke2fs /dev/block/mmcblk0p2
mke2fs 1.41.11 (14-Mar-2010)
/dev/block/mmcblk0p2 is apparently in use by the system; will not make a filesys
tem here!
~ # exit
exit
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Any ideas?
You're almost there... You're /cache partition is already formatted (ext4) Be careful since you can really mess things up with the wrong commands or mis-typed commands.
It looks like you need to mount your sdcard manually. I'm not sure which partition it is. I'll check the stock rom in a little while- I have to run some errands while it downloads.
OK, I downloaded the stock rom and had a look at the /etc/recovery.fstab file in the stock recovery. Should be what we need.
Put your tablet in recovery. Then, in a windows terminal, type "adb remount" and then "adb shell" This wil put you into an android terminal. I don't know if you need read/write permissions in CWM? Who knows? Typing commands in here is the same as typing commands on your tablet (if anyone used the command line any more).
type "ls /dev/block/" and you should see a long list of - look for mmcblk1p1 or mmcblk1. It will probably be the first one.
type "ls /" and look for /sdcard. If it's not there type "mkdir /sdcard" This step creates the mount point if it doesn't exist.
Now type "mount /dev/mmcblk1p1 /sdcard" - Substitute whichever one is in your /dev/block directory from above.
EDIT: If you get errors that it's not formatted or "specify the type" then we'll have to format it first. "mke2fs /dev/block/mmcblk1p1"
Now, in a different windows terminal, type "adb push [a new rom/recovery] /sdcard/"
In CWM, you should be able to flash whatever you pushed there.
If it flashes, but you get bootloops or boot back into CWM, you probably have the dreaded CWM bootloops. You can fix that by typing "dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=15" in the terminal as the first step after "adb shell" For this you will need root access (with the # prompt, not $) Type "su" if you don't ahve the # prompt. It might work? Note that this is experimental and wipes out a bit of your misc partition. I have no idea of what else is on there, so there might be unintended consequences.
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Success
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # ls /dev/block/
ls /dev/block/
loop0 loop3 loop6 mmcblk0p1 mmcblk0p4 mmcblk0p7 platform
loop1 loop4 loop7 mmcblk0p2 mmcblk0p5 mmcblk1
loop2 loop5 mmcblk0 mmcblk0p3 mmcblk0p6 mmcblk1p1
~ # ls /
ls /
cache proc system
data res tmp
default.prop root ueventd.goldfish.rc
dev sbin ueventd.rc
etc sdcard ueventd.ventana.rc
init staging
init.rc sys
~ # mount /dev/mmcblk1p1 /sdcard
mount /dev/mmcblk1p1 /sdcard
mount: mounting /dev/mmcblk1p1 on /sdcard failed: No such file or directory
~ #
I tried pushing anyway, but can't still mount sdcard on cwm from pad interface.
As for the sdcard contents, I have nothing there that can't be deleted.
use "mount /dev/block/mmcblk1p1 /sdcard" No need to repeat the ls commands.
Sorry for not answering rapidly. Baby chose this night to be at his worst.
First
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Success
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # mount /dev/block/mmcblk1p1 /sdcard
mount /dev/block/mmcblk1p1 /sdcard
~ #
New cmd
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push cwm-6.0.1.2-t
ouch-external.zip /sdcard/
1332 KB/s (5070063 bytes in 3.715s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Can't mount sdcard frow cwm. Can I also flash new rck manually?
Tried reboot and mounting again manually, but cwm won't mount.
Maybe try "mount /dev/block/mmcblk1 /sdcard" ???
I get invalid argument on that command.
What if we forget cwm and try format to default partinioning and push stock?
You could try pushing the stock rom to your tablet and then flashing it via the staging partition. The rom is about 522M, so you might need the sd card, but otherwise, you can push it anywhere it will fit. Staging partition is /dev/block/mmcblk0p4. Google around, the info is certainly in this forum. As long as you can get a root shell via adb, you can flash it. The stock rom is on the Asus sight. Just keep unzipping it until you see the blob file.
Of course, you can flash anything you want via the staging partition, if it's packed in a blob format. You might consider flashing a rooted rom instead of the stock.
I have stock on hd. Shall I mount staging via same commands as i mounted sdcard? Push there via adb. Then what command to flash the blob? The blob has no file extension. Shall i keep it that way?
Edit: ok i tried to unpack the recoveryblob from my desired version of cwm, but tool stopped working during process of writing recoveryblob.sos. I got the tool here http://forum.xda-developers.com/showpost.php?p=21620550&postcount=24
Next problem:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Success
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # mount /dev/block/mmcblk0p4
mount /dev/block/mmcblk0p4
mount: can't find /dev/block/mmcblk0p4 in /etc/fstab
~ #
Edit 2: I finally managed to get apx working if it somehow can help.
Hello guys I've run into a weird problem.
I installed SlimLP alpha builds, everything was fine. One day, after trying to format /system etc. before flashing latest version, the tab started rebooting itself every 20 seconds. I tried to uninstall some apps, when I rebooted the tab the apps were back. I booted back into CWM recovery and when I tried to flash old version of this rom, it just stuck at the start. Moreover, when I try to exit recovery it always says "Root access probably lost. Fix?" But that does nothing.
I went into Odin and tried flashing two different stock roms, but it gave error "Complete(Write) operation failed" at system.img .It displayed my model number as "i9505" I then tried to flash through old Odin(v1.75) and it worked. But when I rebooted, it went back into SlimLP. I tried flashing TWRP and latest cwm version but it went back to previous version. The "download count" in Download Mode remained constant. I tried formatting /system and /data through cwm. There was no error but tab still boots straight into SlimLP.
I then tried my luck with ADB in cwm by trying to change file permission. With "chmod 755 /system" it gave the error "Read-only file system" With "mount" , it gave error "Operation not permitted". I booted into slimlp, quickly enabled root for "apps and ADB" through developer options and tried the commands but same error.
I also tried "NAND wipe all" in Odin, but it stuck at "Erase...." and then gave error after sometime.
Is there a way to completely wipe the OS now so I can flash stock one through Odin?
Which recovery version of cwm you have? Probably it will be lower than 6.0.4.4
It is 6.0.4.5
If you're tab still boots then try installing twrp using app called rashr
Tab reboots after 20 seconds, can't install app in that duration.
I9505 means you flashed the wrong firmware to your tablet, I 9505 is an international S4 phone rom.
You need a new tablet.
Reading is very important when it comes to flashing your Samsung devices.
Pp.
PanchoPlanet said:
I9505 means you flashed the wrong firmware to your tablet, I 9505 is an international S4 phone rom.
You need a new tablet.
Reading is very important when it comes to flashing your Samsung devices.
Pp.
Click to expand...
Click to collapse
I downloaded the correct firmware from sammobile, checked many times. Also, I flashed from other Odin version, which didin't display any model number. I just checked Odin3, and even without the device connected, it displays i9505 at top.
EDIT: Well downloaded Odin3 from another site, It didn't show any model number. Guess "i9505" was just a title edit.
I think there is a big in cwm, there are many having this problem with that recovery, all Android andi about it, try sending private message to him, our some other developer
Thanks, I'll try that and post it here.
Please do the following:
Boot/try to boot system
Try to get a dmesg using adb
Boot into recovery
Use adb to pull last_kmesg
Please get a recovery.log after wiping.
Attach the files here.
Send from OnePlus One using Tapatalk
Android-Andi said:
Please do the following:
Boot/try to boot system
Try to get a dmesg using adb
Boot into recovery
Use adb to pull last_kmesg
Please get a recovery.log after wiping.
Attach the files here.
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
I tried the commands like "adb shell dmesg > dmesg.txt" But got error "access is denied" Then I copied dmesg from console window, and pulled other files.
ssqw1 said:
I tried the commands like "adb shell dmesg > dmesg.txt" But got error "access is denied" Then I copied dmesg from console window, and pulled other files.
Click to expand...
Click to collapse
Can you upload the cwm you flash first and send me on pm?
Want to check if it's for our tab.
Will check your logs later.
Send from OnePlus One using Tapatalk
Did you used rommanager for cwm?
Send from OnePlus One using Tapatalk
Nope
Looks like a broken EMMC...
Please boot into recovery and use "adb shell":
Code:
adb shell mount -t ext4 /dev/block/mmcblk0p9 /system
if it mounts without problems do the same for data
Code:
adb shell mount -t ext4 /dev/block/mmcblk0p10 /data
Moutns without problem?
Please unmount now.
Code:
adb shell umount /system
adb shell umount /data
Let´s try to check the partitions now:
Code:
adb shell e2fsck -vf /dev/block/mmcblk0p9
adb shell e2fsck -vf /dev/block/mmcblk0p10
if you got error messages, please inform me.
Maybe we can reformat the partition by using adb shell.
Android-Andi said:
Looks like a broken EMMC...
Please boot into recovery and use "adb shell":
Code:
adb shell mount -t ext4 /dev/block/mmcblk0p9 /system
if it mounts without problems do the same for data
Code:
adb shell mount -t ext4 /dev/block/mmcblk0p10 /data
Moutns without problem?
Please unmount now.
Code:
adb shell umount /system
adb shell umount /data
Let´s try to check the partitions now:
Code:
adb shell e2fsck -vf /dev/block/mmcblk0p9
adb shell e2fsck -vf /dev/block/mmcblk0p10
if you got error messages, please inform me.
Maybe we can reformat the partition by using adb shell.
Click to expand...
Click to collapse
It mounts without problem. Here are the results for checking:
First command:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell e2fsck -vf /dev
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
1699 inodes used (2.59%)
16 non-contiguous files (0.9%)
1 non-contiguous directory (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 1355
182363 blocks used (69.57%)
0 bad blocks
0 large files
1148 regular files
207 directories
0 character device files
0 block device files
0 fifos
0 links
335 symbolic links (335 fast symbolic links)
0 sockets
--------
1690 files
Second:
Code:
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/mmcblk0p10: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>?
It doesn't proceed, tried typing Y, Yes and all other keys.
Can you give me the output from:
Code:
adb shell ls -l /dev/block
Please from recovery and booting rom.
Have you tried flashing stockrom + pit file to repartition?
Send from OnePlus One using Tapatalk
For reference http://forum.xda-developers.com/showthread.php?t=2627490
Send from OnePlus One using Tapatalk
Please give me mount output too.
Code:
adb shell mount
Sorry for the late reply, here are the files.
EDIT: I tried flashing the pit file with stock rom 2 times with Odin version 1.75, it flashed successfully but tab booted straight into SlimLP again.