Related
Alright I'm on the atrix 2 ics leak . Everythings fine except for one thing , I can't get root!!:crying: It's driving me crazy
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
You are rooted!
Press any key to continue . . .
That's the error I keep getting. Please help !
marquavious said:
Alright I'm on the atrix 2 ics leak . Everythings fine except for one thing , I can't get root!!:crying: It's driving me crazy
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
You are rooted!
Press any key to continue . . .
That's the error I keep getting. Please help !
Click to expand...
Click to collapse
i keep getting the same error, if i move the .bat file to the root path of my computer i get this.
it says im root at the bottom but obviously im not.
i have tried 2-3 different root methods.
no luck as of yet
C:\Android>adb kill-server
* server not running *
C:\Android>adb wait-for-device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Android>adb shell mv /data/local/12m/batch /data/local/12m/batch.bak
C:\Android>adb shell ln -s /data /data/local/12m/batch
C:\Android>adb reboot
C:\Android>adb wait-for-device
C:\Android>adb.exe shell rm /data/local.prop
C:\Android>adb.exe shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
C:\Android>adb.exe reboot
C:\Android>adb.exe wait-for-device
C:\Android>adb.exe remount
remount succeeded
C:\Android>adb.exe push su /system/bin/su
cannot stat 'su': No such file or directory
C:\Android>adb.exe shell chmod 04755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Android>adb.exe push Superuser.apk /system/app
cannot stat 'Superuser.apk': No such file or directory
C:\Android>adb.exe shell chmod 0666 /system/app/Superuser.apk
Unable to chmod /system/app/Superuser.apk: No such file or directory
C:\Android>adb.exe shell "echo \"ro.kernel.qemu=0\" > /data/local.prop"
C:\Android>adb.exe shell rm /data/local.prop
C:\Android>adb.exe shell rm /data/local/12m/batch
C:\Android>adb.exe shell mv /data/local/12m/batch.bak /data/local/12m/batch
C:\Android>adb reboot
C:\Android>echo You are rooted!
You are rooted!
C:\Android>PAUSE
Press any key to continue . . .
matt99017d said:
i keep getting the same error, if i move the .bat file to the root path of my computer i get this.
it says im root at the bottom but obviously im not.
i have tried 2-3 different root methods.
no luck as of yet
C:\Android>adb kill-server
* server not running *
C:\Android>adb wait-for-device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Android>adb shell mv /data/local/12m/batch /data/local/12m/batch.bak
C:\Android>adb shell ln -s /data /data/local/12m/batch
C:\Android>adb reboot
C:\Android>adb wait-for-device
C:\Android>adb.exe shell rm /data/local.prop
C:\Android>adb.exe shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
C:\Android>adb.exe reboot
C:\Android>adb.exe wait-for-device
C:\Android>adb.exe remount
remount succeeded
C:\Android>adb.exe push su /system/bin/su
cannot stat 'su': No such file or directory
C:\Android>adb.exe shell chmod 04755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Android>adb.exe push Superuser.apk /system/app
cannot stat 'Superuser.apk': No such file or directory
C:\Android>adb.exe shell chmod 0666 /system/app/Superuser.apk
Unable to chmod /system/app/Superuser.apk: No such file or directory
C:\Android>adb.exe shell "echo \"ro.kernel.qemu=0\" > /data/local.prop"
C:\Android>adb.exe shell rm /data/local.prop
C:\Android>adb.exe shell rm /data/local/12m/batch
C:\Android>adb.exe shell mv /data/local/12m/batch.bak /data/local/12m/batch
C:\Android>adb reboot
C:\Android>echo You are rooted!
You are rooted!
C:\Android>PAUSE
Press any key to continue . . .
Click to expand...
Click to collapse
Your issue, is that when you move the script to C:\ you also need to move su and Superuser.apk to the same directory as well, or it will not find those files like it is complaining about. the bat file and the su and superuser.apk MUST all be in the same dir. Try moving them all to your root path.
jimbridgman said:
Your issue, is that when you move the script to C:\ you also need to move su and Superuser.apk to the same directory as well, or it will not find those files like it is complaining about. the bat file and the su and superuser.apk MUST all be in the same dir. Try moving them all to your root path.
Click to expand...
Click to collapse
OK when i moved the whole folder into c:\ android it worked!
thank you so much jim.
Now how to overclock? or do are we waiting for int't? {think thats what its called}
It worked for me too! Thanks Jim. Love you dude
Sent from my MB865 using xda app-developers app
matt99017d said:
i keep getting the same error, if i move the .bat file to the root path of my computer i get this.
it says im root at the bottom but obviously im not.
i have tried 2-3 different root methods.
no luck as of yet
C:\Android>adb kill-server
* server not running *
C:\Android>adb wait-for-device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Android>adb shell mv /data/local/12m/batch /data/local/12m/batch.bak
C:\Android>adb shell ln -s /data /data/local/12m/batch
C:\Android>adb reboot
C:\Android>adb wait-for-device
C:\Android>adb.exe shell rm /data/local.prop
C:\Android>adb.exe shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
C:\Android>adb.exe reboot
C:\Android>adb.exe wait-for-device
C:\Android>adb.exe remount
remount succeeded
C:\Android>adb.exe push su /system/bin/su
cannot stat 'su': No such file or directory
C:\Android>adb.exe shell chmod 04755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Android>adb.exe push Superuser.apk /system/app
cannot stat 'Superuser.apk': No such file or directory
C:\Android>adb.exe shell chmod 0666 /system/app/Superuser.apk
Unable to chmod /system/app/Superuser.apk: No such file or directory
C:\Android>adb.exe shell "echo \"ro.kernel.qemu=0\" > /data/local.prop"
C:\Android>adb.exe shell rm /data/local.prop
C:\Android>adb.exe shell rm /data/local/12m/batch
C:\Android>adb.exe shell mv /data/local/12m/batch.bak /data/local/12m/batch
C:\Android>adb reboot
C:\Android>echo You are rooted!
You are rooted!
C:\Android>PAUSE
Press any key to continue . . .
Click to expand...
Click to collapse
For some reason it took me several tries as well. Try moving the zip to your desktop then extracting it there and running the .bat file from the extracted folder and see if that helps. To the OP it looks like you dont have ADB set up in your path correctly
matt99017d said:
OK when i moved the whole folder into c:\ android it worked!
thank you so much jim.
Now how to overclock? or do are we waiting for int't? {think thats what its called}
Click to expand...
Click to collapse
Yeah we are waiting for init.d, there are a few of us looking at it right now, so hopefully not long.
Is there any partition that is preserved across such OTA/recovery updates? If I rooted 2.3.6 and installed a suid-root binary "su" in /system/xbin, and then applied the ICS update, it'll be probably gone as /system will be cleaned up by the update. Is there any other safe place I can park the suid binary so that post update it is available? If my SD card has a ext3 partition, I can put it there, only if the partition is mounted by root at startup. I wonder how OTA Rootkeeper works, where does it safely store suid su binary across updates?
hello
i'm a french guy so my english is very poor
Thank's for all too install ics on atris2 but i can(t root it.
I have the doo the same thing of this thread but nothing his right
what i can do?
what is the mod chouse when i plug the A2 with USB
thank's
when i launch root.bat i have
* daemon not running. starting it now *
* daemon starting successfull *
it's ok I just forgot to put debugging usb
thank's for all
kousik said:
Is there any partition that is preserved across such OTA/recovery updates? If I rooted 2.3.6 and installed a suid-root binary "su" in /system/xbin, and then applied the ICS update, it'll be probably gone as /system will be cleaned up by the update. Is there any other safe place I can park the suid binary so that post update it is available? If my SD card has a ext3 partition, I can put it there, only if the partition is mounted by root at startup. I wonder how OTA Rootkeeper works, where does it safely store suid su binary across updates?
Click to expand...
Click to collapse
No OTA rootkeeper did not work for this update. You CAN'T be rooted, it can cause the update to fail.
You really need to do it as I posted it. This root script works, but you must unzip it and put the folder on the desktop or in c:\. For Linux adb just need to be in your PATH, so it can be unzipped anywhere.
Oh and everything gets wiped when you do the fxz, so no place is safe to store su.
Sent from my SAMSUNG-SGH-I747 using xda premium
jimbridgman said:
No OTA rootkeeper did not work for this update. You CAN'T be rooted, it can cause the update to fail.
You really need to do it as I posted it. This root script works, but you must unzip it and put the folder on the desktop or in c:\. For Linux adb just need to be in your PATH, so it can be unzipped anywhere.
Oh and everything gets wiped when you do the fxz, so no place is safe to store su.
Click to expand...
Click to collapse
The update generally won't fail just because of rooting. Problem is, post rooting we install a lot of hacks, change a lot of system files. The updater-script notices them and refuse to update. I see updater-script checking the signature of 616 files, almost all files of /system/app, /system/bin, /system/app, /system/lib etc. However it recursively delete /system/data, /system/usr/bin, /system/data. If you touched any of these 616 files update will fail. Even if we didn't change the binaries, people play with build.prop and the updater-script would look for a sha1sum of 9ff9faedeb74bd02b3fe6a912e758f55d1437538.
However it does not sweep clean /system. It removes specific files; and then adds new ones. The root doesn't remain because of the following:
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
So the setuid bit of binary su is not retained. So we have to find another file system which is safe from these operations. Maybe I'll leave the suid- su binary at /
kousik said:
The update generally won't fail just because of rooting. Problem is, post rooting we install a lot of hacks, change a lot of system files. The updater-script notices them and refuse to update. I see updater-script checking the signature of 616 files, almost all files of /system/app, /system/bin, /system/app, /system/lib etc. However it recursively delete /system/data, /system/usr/bin, /system/data. If you touched any of these 616 files update will fail. Even if we didn't change the binaries, people play with build.prop and the updater-script would look for a sha1sum of 9ff9faedeb74bd02b3fe6a912e758f55d1437538.
However it does not sweep clean /system. It removes specific files; and then adds new ones. The root doesn't remain because of the following:
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
So the setuid bit of binary su is not retained. So we have to find another file system which is safe from these operations. Maybe I'll leave the suid- su binary at /
Click to expand...
Click to collapse
Don't tell people this, because what we have found is the safest method is to fxz back to stock before any OTA.
We don't want to confuse people here. I am not saying what you said is wrong, just that we all need to stay on the same page here... I am trying to get everyone to have the same abilities to update here... as well as you are posting this in the wrong place, this is someone asking for help rooting the ICS leak.
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.
Problem solved, by using an other usb adb driver, instead of universal adb driver ; thx petrov.0
Hi, sorry for my bad english,
I've trouble to understand what's wrong or I miss : want to run the 1st command umount /cache at the 4th step (unmount all partitions of the internal memory )
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ umount /cache
umount /cache
failed: Operation not permitted
1|[email protected]:/ $
Actually the phone are root, TWRP v2.8.6.0 by decker. I've also swap with twrp-2.8.7.0-idol3-6039y-with-gdisk instead of just run it one time : same trouble, Operation not permitted
Any idea ?
Just to be sure, when it writing go to device, we are under the TWRP -> Reboot -> System ... and we go to android ? And at this point I run adb shell, that ok ?
I would also say, that my first smartphone / 1st root / 1st trying
Ok I've discover what's wrong
Need writing on the commande line : adb shell su
SuperSu on the phone ask me an authorization about "adb shell", of course I say yes
Now i can see :
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell su
[email protected]:/ #
Symbol and "user" have change
shell --> root
$ --> #
Hope now all clear for the next step.
Unfortunaly, it's not to seem that, now I can't writing any caractere in command line
Have try :
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
su
[email protected]:/ # gdisk
gdisk
tmp-mksh: gdisk: not found
127|[email protected]:/ #
umount /and-sec directory not found
gdisk not works
...help !
You shouldn't reboot the device. Everything must be done while the phone is in the recovery.
Not sure to understand you
When i'm under TWRP, writing in command line adb shell --> error: device not found
I really need you can detail step by step until there.
bykarat said:
Not sure to understand you
When i'm under TWRP, writing in command line adb shell --> error: device not found
I really need you can detail step by step until there.
Click to expand...
Click to collapse
You do this from Windows, so you need drivers which recognize your device when is in the recovery. I'm not sure which drivers work with the phone. The vendor and the product IDs for the recovery are
Code:
idVendor=18d1, idProduct=4ee2
Yes the problem come from the usb driver, you have good see., despite the id vendor & product number are good
img15.hostingpics.net/pics/282113Sanstitre2.pngWhen I follow an tutorial for rooting, it mention to install "Universal adb driver", enought for that, but not for your Guide "Repartitioning of the internal memory"
Have use those ones of : (can't add link in this forum at this time) 54.247.87.13/softwareupgrade/Driver/ALCATEL_ADB_%20Driver%20Qualcomm_ADB.rar
I want to say lots of thank you for all that :victory:
bykarat said:
Yes the problem come from the usb driver, you have good see., despite the id vendor & product number are good
img15.hostingpics.net/pics/282113Sanstitre2.pngWhen I follow an tutorial for rooting, it mention to install "Universal adb driver", enought for that, but not for your Guide "Repartitioning of the internal memory"
Have use those ones of : (can't add link in this forum at this time) 54.247.87.13/softwareupgrade/Driver/ALCATEL_ADB_%20Driver%20Qualcomm_ADB.rar
I want to say lots of thank you for all that :victory:
Click to expand...
Click to collapse
Glad to see that you made it. There is a thanks button by the way . I will include the link to the drivers in the guide.
This is - parted command - , let you see, for example, the beggining and end from a partition and the size she have.
Install the zip with TWRP or CWM
boot the phone, and with debug mode ON, use adb like this:
adb shell
su
parted /dev/block/mmcblk0
print
parted command
https://mega.nz/#!q0wzSYCC!8rCjSQAPlPP4n8yfBFK8IWd-5LqYxbc7osINsrTxsd8
Find more options here:
https://www.gnu.org/software/parted/manual/parted.html
I have tried following command on ADB to extract partition, but failed.
source:fciotti.com/2017/02/26/clone-android-memory
Code:
chmod +r /dev/block/mmcblk0
returns
Code:
Bad mode
Code:
adb pull /dev/block/mmcblk0 "mmc.img"
returns
Code:
remote permission denied
I have post a question on stack exchange, and found a command working but failed after dumping 4gb on sdcard (not directly to pc) because of file system.
source:android.stackexchange.com/questions/185433/problem-with-coping-mmcblk0-to-pc?noredirect=1#
Code:
adb exec-out "su -c 'cat /dev/block/mmcblk0'" > mmc.img
but it create a 0kb img file.
Please anyone help.