I went into Terminal Emulator and typed
Code:
su
bootanimation
. . . just to see if it would play, and it did! But now I can't make it stop. Only things I can do are turn the screen off and on again, or hold the back button to kill Terminal Emulator ("Stop app via long-press" feature in CM7). Is there a way to make the bootanimation stop so that I just go back to Terminal Emulator?
jdkoren said:
I went into Terminal Emulator and typed
Code:
su
bootanimation
. . . just to see if it would play, and it did! But now I can't make it stop. Only things I can do are turn the screen off and on again, or hold the back button to kill Terminal Emulator ("Stop app via long-press" feature in CM7). Is there a way to make the bootanimation stop so that I just go back to Terminal Emulator?
Click to expand...
Click to collapse
From with in the Terminal Emulator no.
If you use the ADB commands you can press and hold Control and tap C.
Lol I didn't know you could do that and so tried and ssame result battery pull fixed it though royalginger 1.6
Sent from my HTC Glaciee using XDA Premium App
Messing with terminal like this is not a good idea. You can mess somethint up and even brick yourself so hard.
I know first hand when I messed up on a line or the command in terminal when pushing a custom splash.
Sent from my HTC Glacier using XDA Premium App
coupetastic-droid said:
Messing with terminal like this is not a good idea. You can mess somethint up and even brick yourself so hard.
I know first hand when I messed up on a line or the command in terminal when pushing a custom splash.
Click to expand...
Click to collapse
Your concern is appreciated, but this statement is somewhat over-exaggerated and will likely frighten some of the n00bs out there who aren't familiar with terminals and shell commands. I'm not flashing a bootloader or anything nearly as invasive, I'm just playing the bootanimation without actually rebooting the phone. If I mistype the command, it's simply going to tell me it's an invalid command. There is really nothing to be worried about here.
I know first hand when I messed up on a line or the command in terminal when pushing a custom splash.
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
I know first hand also. my victim (G1) still sits next to my mt3g waiting to be unbricked someday
Sent from my HTC Glacier using XDA Premium App
jdkoren said:
Your concern is appreciated, but this statement is somewhat over-exaggerated and will likely frighten some of the n00bs out there who aren't familiar with terminals and shell commands. I'm not flashing a bootloader or anything nearly as invasive, I'm just playing the bootanimation without actually rebooting the phone. If I mistype the command, it's simply going to tell me it's an invalid command. There is really nothing to be worried about here.
Click to expand...
Click to collapse
If you go into your ADB commands and type
Code:
adb shell
bootanimation
it will bring up the phones boot animation. You are not flashing anything nor are you tampering with any of the /system or the /bin files.
To get out of it just simply hold the Control button and tap C on the keyboard.
seriously nothing can go wrong with those commands.
try this:
hold the power button, the volume down key, and the trackpad button
just tested...it works
great for people who have heavy duty cases such as otterbox and trident
I just connected Bluetooth keyboard, it makes it easier and can press CTRL+C to exit animation.
I can fix them both in like 2 minutes
Related
First off let me say this is 1000000% easier than RSD Lite in my opinion.
If you like this guide just give me a little thanks
You will need a few things downloaded.
The sbf: Download In this folder you are really only going to need the DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_SECURE.sbf file. You can delete the second one.
The sbf_flash file: Download
Once you download both put them in your home folder(user name folder) open terminal and type these things step by step
Plug your phone in via USB now and turn it off and press up on the keyboard to go into the bootloader.
1. "chmod +x sbf_flash"
2. "sudo ./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_SECURE.sbf
Now your phone should start flashing. Let it do its stuff and it should reboot in about 20-30 minutes.
Hope it helped!
BTW this works if you are bricked
Thanks for the info. I've been wondering this; now I don't have to set up a windows VM when things go south. I usually find most things easier in Linux (once you get used to Linux).
Sent from my DROID2 using XDA App
A note to people who try and do the SBF. Wipe your data and cache in recovery if you have a boot loop after flashing. I have verified this method works, but I had to wipe my data and cache afterwards to get past an infinite boot loop.
Maybe someone can help me out. I've installed Ubuntu (first time user), and I have followed the directions up to the terminal part.
Plug your phone in via USB now and turn it off and press up on the keyboard to go into the bootloader.
1. "chmod +x sbf_flash"
2. "sudo./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_ SECURE.sbf
When I try these commands, here is what I get:
[email protected]:~$ chmod +x sbf_flash
[email protected]:~$ sudo./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_ SECURE.sbf
bash: sudo./sbf_flash: No such file or directory
Also tried:
sudo ./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_ SECURE.sbf
sudo: unable to execute ./sbf_flash: No such file or directory
It shows up in the username folder (David), but for some reason I get no such file.
If someone can point out what I'm doing wrong, that would be great. Thanks.
draya1986 said:
Maybe someone can help me out. I've installed Ubuntu (first time user), and I have followed the directions up to the terminal part.
Plug your phone in via USB now and turn it off and press up on the keyboard to go into the bootloader.
1. "chmod +x sbf_flash"
2. "sudo./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_ SECURE.sbf
When I try these commands, here is what I get:
[email protected]:~$ chmod +x sbf_flash
[email protected]:~$ sudo./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_ SECURE.sbf
bash: sudo./sbf_flash: No such file or directory
Also tried:
sudo ./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_ SECURE.sbf
sudo: unable to execute ./sbf_flash: No such file or directory
It shows up in the username folder (David), but for some reason I get no such file.
If someone can point out what I'm doing wrong, that would be great. Thanks.
Click to expand...
Click to collapse
Put a space between sudo and ./sbf_flash. It is not one command.
Sent from my DROID2 using Tapatalk
this forum is so awsome thank to all the people that post and help !
Matt4542 said:
First off let me say this is 1000000% easier than RSD Lite in my opinion.
If you like this guide just give me a little thanks
You will need a few things downloaded.
The sbf: Download In this folder you are really only going to need the DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_SECURE.sbf file. You can delete the second one.
The sbf_flash file: Download
Once you download both put them in your home folder(user name folder) open terminal and type these things step by step
Plug your phone in via USB now and turn it off and press up on the keyboard to go into the bootloader.
1. "chmod +x sbf_flash"
2. "sudo./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_SECURE.sbf
Now your phone should start flashing. Let it do its stuff and it should reboot in about 20-30 minutes.
Hope it helped!
BTW this works if you are bricked
Click to expand...
Click to collapse
How does this work if you are bricked? I am stuck at getting to the M logo on boot and can only get to Android Recovery Console. I can't turn off the phone after i plug in the USB and hitting up arrow i've never seen before. Also, the phone when at the recovery console isn't recognized as anything; even in windows
EDIT: Hmm, i was not using bootloader mode sorry, trying again!
Link is broken for sbf_flash.
Sent from my DROID2 using XDA App
zibrah3ed said:
Link is broken for sbf_flash.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Ya, I noticed that too. Pretty easy to find it searching on google though and I think its not specific to model of phone. I found a link to it here:
http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Motorola_Droid
patchm00 said:
Ya, I noticed that too. Pretty easy to find it searching on google though and I think its not specific to model of phone. I found a link to it here:
http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Motorola_Droid
Click to expand...
Click to collapse
Thanks I wasn't sure if it was specific to this phone or not. I had found another copy using the google.
patchm00 said:
How does this work if you are bricked? I am stuck at getting to the M logo on boot and can only get to Android Recovery Console. I can't turn off the phone after i plug in the USB and hitting up arrow i've never seen before. Also, the phone when at the recovery console isn't recognized as anything; even in windows
EDIT: Hmm, i was not using bootloader mode sorry, trying again!
Click to expand...
Click to collapse
I WAS using the bootloader, and RSD lite says the "Failed flashing process. Phone [0000]: Phone is not compatible with multi-interface super-file. [0x703B]; phone connected." I have no idea on what to do now.
Sent from my DROID2 using XDA App
I followed the steps and now I am stuck in bootloader.... The process seems to have been completed, but when I turn on phone it directly goes into bootloader.
It shows the following.....
Bootloader
D2,35
Err:A5,70,70,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
Data Cable
Which sbf did you use and did you get the OTA update (2.3.2)?
Might I interest you in this threadit has the same instructions with more explanation just ignore the stuff about the livecd because you already have linux.
duongtran said:
I followed the steps and now I am stuck in bootloader.... The process seems to have been completed, but when I turn on phone it directly goes into bootloader.
It shows the following.....
Bootloader
D2,35
Err:A5,70,70,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
Data Cable
Click to expand...
Click to collapse
Boot into recovery by holding x and power, then press the search key at the android. Wipe data and cache, then reboot.
I figured it out! Thanks for info newk8600. I was using the sbf found in this thread, but I needed the newer sbf(2.3.20) because I somehow got the OTA update. I have no clue how I got it because I never updated my phone in over 3 weeks. The last time I updated my phone was Fission beta or alpha. But either way thanks developers for everything you guys saved my expensive paperweight.
Matt4542 said:
First off let me say this is 1000000% easier than RSD Lite in my opinion.
If you like this guide just give me a little thanks
You will need a few things downloaded.
....
Once you download both put them in your home folder(user name folder) open terminal and type these things step by step
Plug your phone in via USB now and turn it off and press up on the keyboard to go into the bootloader.
1. "chmod +x sbf_flash"
2. "sudo ./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_SECURE.sbf
Now your phone should start flashing. Let it do its stuff and it should reboot in about 20-30 minutes.
Hope it helped!
BTW this works if you are bricked
Click to expand...
Click to collapse
Thanks! But can you tell me it this will also work on the motorola milestone ? (other SBF file ofcourse!) because I tried updating to 2.2 but RSD lite wasn't able to find my phone or something.
Maybe someone else has an idea what the cause would be for it not to function as it should ?
I bet it would work for the milestone also with the correct .SBF file. Just make sure you use the same syntax with the correct filename: sudo ./sbf_flash [sbf_file_name] (make sure the file doesn't have spaces or it won't find the right file).
I wrote a small script.
DOSBF (kind of like DORoot and DOOverclock). You just got to give it permissions and run it, and yeah.
www.kimete.com/download.html
Awesome! Sounds easy.
Sent from my DROID2 using XDA App
newk8600 said:
Awesome! Sounds easy.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
It is actually! Super easy!
hey all. anyone know if we can turn s-off on wildfire yet? kninda frustraiting... its root but not really root
bassmonkey said:
hey all. anyone know if we can turn s-off on wildfire yet? kninda frustraiting... its root but not really root
Click to expand...
Click to collapse
To me this is a 100% genuine "WTF?" statement... I don't get what you mean mate, please explain..
bassmonkey said:
hey all. anyone know if we can turn s-off on wildfire yet? kninda frustraiting... its root but not really root
Click to expand...
Click to collapse
Not yet till Alpharev v2 realesed
Sent from my HTC Legend
gyroing said:
Not yet till Alpharev v2 realesed
Sent from my HTC Legend
Click to expand...
Click to collapse
Thanks dude, I've just came from having a totally customized hero
N despite the screen rez I'm loving this phone but no access to system folder is pants
Sent from my HTC Wildfire using XDA App
niksakl said:
To me this is a 100% genuine "WTF?" statement... I don't get what you mean mate, please explain..
Click to expand...
Click to collapse
As far as I can tell its a new security thing HTC have added to the hboot, basically makes the system folder read only even with root (think that's correct??)
Sent from my HTC Wildfire using XDA App
bassmonkey said:
Thanks dude, I've just came from having a totally customized hero
N despite the screen rez I'm loving this phone but no access to system folder is pants
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Well , it's not totally locked down. You can access it (Read and write) if you boot into recovery. Not the smoothest solution but it works. Also there is AUFS but i don't think i have gotten that to work at all. Maybe it needs to be enabled, haven't really checked but i boot into recovery when i need to change something.
You can change the /system permission with a terminal emulator as Better Terminal Pro on the phone or by the phone connected to your pc via
Code:
> adb shell
doing in both cases:
Code:
# chmod -R 777 /system
when you restart the phone, /system will be reset to the original 755 permissions.
thanks for the response guys
71baker said:
Well , it's not totally locked down. You can access it (Read and write) if you boot into recovery. Not the smoothest solution but it works. Also there is AUFS but i don't think i have gotten that to work at all. Maybe it needs to be enabled, haven't really checked but i boot into recovery when i need to change something.
Click to expand...
Click to collapse
how do you do it through recovery? im guessing thatd be with adb?
Tetractys said:
You can change the /system permission with a terminal emulator as Better Terminal Pro on the phone or by the phone connected to your pc via
Code:
> adb shell
doing in both cases:
Code:
# chmod -R 777 /system
when you restart the phone, /system will be reset to the original 755 permissions.
Click to expand...
Click to collapse
in terminal i entered su
chmod -R777/system
which then gave me; usage: chmod <mode> <file>
i then entered; /system and got permission denied??
bassmonkey said:
thanks for the response guys
how do you do it through recovery? im guessing thatd be with adb?
in terminal i entered su
chmod -R777/system
which then gave me; usage: chmod <mode> <file>
i then entered; /system and got permission denied??
Click to expand...
Click to collapse
If you have written the command exactly as you report is obvious that the os return an error. try to write as i did... (with blanks in between)
of course your phone had to be passed the Unrevoked 3.21 procedure!
http://forum.xda-developers.com/forumdisplay.php?f=701
Anyway if you are not very much concerned in linux shell commands, i would suggest you to wait another more automatic method.
Tetractys said:
If you have written the command exactly as you report is obvious that the os return an error. try to write as i did... (with blanks in between)
of course your phone had to be passed the Unrevoked 3.21 procedure!
http://forum.xda-developers.com/forumdisplay.php?f=701
Anyway if you are not very much concerned in linux shell commands, i would suggest you to wait another more automatic method.
Click to expand...
Click to collapse
lol.'not concerned' very diplomatic yeah, kind of a windoze boy n therefore not really up on linux.
i did root with 3.21 and i tried the chmod command with all the spaces and terminal just gave me 'bad mode' (it also gave me bad mode when i tried adb) so i tried as i posted. bummer but nevermind, come on alpharev 2
71baker said:
Also there is AUFS but i don't think i have gotten that to work at all. Maybe it needs to be enabled, haven't really checked but i boot into recovery when i need to change something.
Click to expand...
Click to collapse
You can enable AUFS in Jacob's latest kernel by typing "aufs --enable" in a terminal emulator app in android, and then reboot the phone.
Alright im kinda of new to the mytouch 4g scene. However im have a good understanding of what is going on,just not with the 4g lol.here's my problem I bought this phone off ebay and I went to root it and it said already rooted. I get all super user permission even after turning phone of on and off. When I go to check if s is off it is on? What's going on is this phone only temp rooted? If so how do i perm root i know there are many methods just want to know the best. Its 2.2.1. Thanks in advance. If
Sent from my SGH-T959 using XDA App
Vjarndt said:
Alright im kinda of new to the mytouch 4g scene. However im have a good understanding of what is going on,just not with the 4g lol.here's my problem I bought this phone off ebay and I went to root it and it said already rooted. I get all super user permission even after turning phone of on and off. When I go to check if s is off it is on? What's going on is this phone only temp rooted? If so how do i perm root i know there are many methods just want to know the best. Its 2.2.1. Thanks in advance. If
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
It seems like your already perm rooted. But, s off is required for u to flash custom roms.
Sent from my HTC Glacier using XDA App
Thanks. I just pushed the root file and it turned it off. I was praying for a min. Lol
Sent from my SGH-T959 using XDA App
Vjarndt said:
Thanks. I just pushed the root file and it turned it off. I was praying for a min. Lol
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Good job
Sent from my HTC Glacier using XDA App
Vjarndt said:
Thanks. I just pushed the root file and it turned it off. I was praying for a min. Lol
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
How did you push the root file? I'm stuck on the same thing!
PostaHTC I see you made alot of posts I am guessing you just did TempROOT and you didn't invokes the sh command. Did you download the root.sh? If so after TempROOT to get PermROOT from console type in sh <file> make sure you have root dir under /sdcard
I've done it step by step and still nothing I just got it out the box 2days ago so I just did a hard reset I'm just waiting on someone to tell me what I am doing wrong
Can you tell me exactly what to do because I rooted my 1st myTouch but this one is acting crazy! I have all the files /sdcard my question is when you temp-Root the phone do you type the commands then perm-root? Like I'm lost
Well since you are up to the PermROOT I take it you have TempROOT, if so as you saying you have root.sh in root dir inside /sdcard so it would look like /sdcard/root/root.sh for the absolute path. Also you have console right? If not go download Terminal Emulator. Then type in "su" and press enter SU=Super User or @wheel,root permission base. Then use "cd /sdcard/root" press enter CD = Change Directory. Then do "sh root.sh" and press enter as sh is shall execute command. So it would look like this below:
su
cd /sdcard/root
sh root.sh
Now just do restart and make sure you have S=OFF as you will see it on top in HBoot screen. When you are back on go open Visionary+ and unclick TempROOT on boot and click TempROOT now. Then look below and click on Attempt PermROOT Now.
STHNS said:
Well since you are up to the PermROOT I take it you have TempROOT, if so as you saying you have root.sh in root dir inside /sdcard so it would look like /sdcard/root/root.sh for the absolute path. Also you have console right? If not go download Terminal Emulator. Then type in "su" and press enter SU=Super User or @wheel,root permission base. Then use "cd /sdcard/root" press enter CD = Change Directory. Then do "sh root.sh" and press enter as sh is shall execute command. So it would look like this below:
su
cd /sdcard/root
sh root.sh
Now just do restart and make sure you have S=OFF as you will see it on top in HBoot screen. When you are back on go open Visionary+ and unclick TempROOT on boot and click TempROOT now. Then look below and click on Attempt PermROOT Now.
Click to expand...
Click to collapse
I have everything I need the files and all...I have the files on the SD Card not the root folder When I turn it off it is still saying S-On
Well in that case from console type in
su
mkdir /sdcard/root
mv /sdcard/root.sh /sdcard/root/
cd /sdcard/root
sh root.sh
If you don't want to do it manually then you can do it easily via FileExp go use Astro or Root Explorer. From what you are saying I have my money on you didn't properly do TempROOT. I say go do TempROOT again then try what I suggested for PermROOT.
UPDATE: Here I found you Youtube videos how to do step by step.
TempROOT> http://www.youtube.com/watch?v=gylaXOCNzqU
PermROOT> http://www.youtube.com/watch?v=Sy_aqKoeev4
Use the howto from Theunlockr video posted above it maybe easier for you to follow.
sthns said:
well in that case from console type in
su
mkdir /sdcard/root
mv /sdcard/root.sh /sdcard/root/
cd /sdcard/root
sh root.sh
if you don't want to do it manually then you can do it easily via fileexp go use astro or root explorer. From what you are saying i have my money on you didn't properly do temproot. I say go do temproot again then try what i suggested for permroot.
Update: Here i found you youtube videos how to do step by step.
Temproot> http://www.youtube.com/watch?v=gylaxocnzqu
permroot> http://www.youtube.com/watch?v=sy_aqkoeev4
use the howto from theunlockr video posted above it maybe easier for you to follow.
Click to expand...
Click to collapse
i tried the unlockr it didn't work ugh
Same problem, my device is permanent rooted from visionary but still had s-off after this procedure.
Sent from my HTC Glacier using XDA App
onboard nand flash query for STHNS
Thank you STHNS you said Good news for you lol I looked in to it when I was comparing it with iPad and if I remember correctly the 16gb on Samsung GT is using NAND flash memory from SanDisk""""""
Can you please tell me the size , length, breadth and thickness of the sandisk 16gb inside storage,,
I'm S-On, And I Can Still Flash Custom Roms And Everything.
Slim6 Launcher And Open Gapps 6.0 Nano Are On My Device
Htc One M8
Glad to see something going on here. If you need any assistance, quote me. Have Rooted plenty of these devices
Sent from my One using XDA mobile app
Hi..!! Everyone I tried everything, I was going to unlock and root my xoom but I got stuck at this step:
7. fastboot flash boot rootboot.img
I get this error: "can't load rootboot.img"
I run fastboot reboot command and works, after reboots I try adb devices and my xoom shows but if I run adb remount I get this error:
"remount failed: Operation no permitted"
I tried everything search everywhere, update everything and NADA, I'm on a Windows 7 64bit.
Thanks and I hope somebody can direct me to the right path..
You will want to grant root access again using the adb commands. This happened to me once. You don't have permission to do this because it needs to have root access to carry on this operation. Try the root commands again to grant root access and then see what it does when trying to flash the rootboot files.
If that's not it come let us know. XDA will have your answer for sure.
Sent from my Droid using XDA Premium App
diablo2224 said:
You will want to grant root access again using the adb commands. This happened to me once. You don't have permission to do this because it needs to have root access to carry on this operation. Try the root commands again to grant root access and then see what it does when trying to flash the rootboot files.
If that's not it come let us know. XDA will have your answer for sure.
Sent from my Droid using XDA Premium App
Click to expand...
Click to collapse
I get stuck on step 7 of this guide below, so I think I never get to the point of getting root, but if I'm doing something wrong and I have to run some other commands please let me know.
1. Download the Motorola Xoom Root Zip file and unzip it. Download
2. Place the files in the SDK Tools folder.
3. adb reboot bootloader (You can skip the next 3 steps if you’ve unlocked with fastboot previously)
5. fastboot oem unlock (wait for reboot)
6. adb reboot bootloader
7. fastboot flash boot rootboot.img
7. fastboot reboot (wait for reboot)
8. adb remount
9. adb shell push su /system/bin
10. adb shell ln –s /system/bin/su /system/xbin/su
11. adb shell chmod 4755 /system/bin/su
12. adb push Superuser.apk /system/app
And thanks for making some time to reply, I try to get some help on other threads with no response.
dumb question: is rootboot.img in the same directory as everything else?
It sounds to me like your flashboot can't find it.
That's a good point from the poster above. I had trouble at the start with this and the SDK tools folder because I never messed with the adb shell too often because there never really has been a need for me to do so up until I got the Xoom.
OP... like this reply says above me, I am agreeing to as well. It looks like it might not be finding your rootboot. Make sure all root files are located in the very root of the SDK tools folder, and make sure all root files are not inside a folder. If they are please drag them into the tools folder and slap them all in there. It looks like a mess but it works. Do the same type of thing if you plan on flashing an overclock kernel. Always make sure that all files are NOT in folders when flashing something like this, and that they are always placed in the very root of the tools folder located within the SDK folder. Hope this helps.
About my above post... woops. I wasn't paying attention totally. It was late. I was thinking about when you are trying to install an overclock kernel and run into this problem that says that you cannot remount in adb. It does have to do with root access though.
Thank you very much guys I found what was my problem, I was running ADB straight from CMD window without navigating to my tool folder and always worked so I thought running step 7 will work, but NO I had to cd c:.....bla bla navigate to tool folder and do step 7.
Now I'm happily Rooted thanks again for your time guys, now to set up again my beautiful screens.
I'm having that problem where i'm trying to flash Tiamat Kernel on my Xoom and when i get to the remount i'm getting - remount failed: Operation not permitted . When you say grant root access again you talking about pointing it to the platform folder ?.
It sounds like those having problems are not very familiar with adb. Don't worry, we have all been there at one point. I would suggest that you use the one click method. No its not really a one click, more like a one click at a time method. But, it goes slow and you can see what it is doing as it goes along and has a nice tutorial from the op.
Sent from my HTC HD2 using XDA Premium App
jase33 said:
It sounds like those having problems are not very familiar with adb. Don't worry, we have all been there at one point. I would suggest that you use the one click method. No its not really a one click, more like a one click at a time method. But, it goes slow and you can see what it is doing as it goes along and has a nice tutorial from the op.
Sent from my HTC HD2 using XDA Premium App
Click to expand...
Click to collapse
No i'm not so good at it but i'm willing to or i want to learn . I used it for the first time when my Xoom was soft brick from installing a theme , i restored it with ADB and then use ADB to root ,so that's twice , the first time i rooted my Xoom i used the one click method because i was so afraid of ADB . Today the third time i was using it to flash a Kernel and at the remount i got into the problem above .
jawonder said:
No i'm not so good at it but i'm willing to or i want to learn . I used it for the first time when my Xoom was soft brick from installing a theme , i restored it with ADB and then use ADB to root ,so that's twice , the first time i rooted my Xoom i used the one click method because i was so afraid of ADB . Today the third time i was using it to flash a Kernel and at the remount i got into the problem above .
Click to expand...
Click to collapse
Are you trying to push something thru a ADB...???
Sent from my Xoom using XDA Premium App
lokko21 said:
Are you trying to push something thru a ADB...???
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Yes i'm trying to flash a kernel but at the remount step it's telling that : remount failed : operation is not permitted .
Ok..
I cleared delvik cache.. battery and decided to try out a new kernel.. now it hangs..
Now I only have an 8 gig.. I guess i cleared out the backup to save space because as I went to look for it, it was gone. Now I cant get any roms on the phone to reflash.. and i deleted the ROMs on there...
How do I get a rom on the phone to reflash it. Any help would be greatly appreciated.
Thanks
Chris
Bump
Can anybody help with this? Basically is there a way to get files on the phone in recovery mode?
I'm sort of new... I see the side load but not sure how to use it. Says load the files on once activated but not sure how the relates to the computer. Or where I put the commands to do it. Thanks.
Chris
Sent from my SGH-I747 using xda app-developers app
You are running a custom recovery right?
You can use adb to push files when booted into a custom recovery.
The command used would be
Code:
adb push nameofzip /storage/emulated/0
To read more on adb check out efrants sicky http://forum.xda-developers.com/showthread.php?t=2010338 adb commands are about half way down on the OP.
When u say custom recovery do u mean CWM? I do have that... and my computer registers the phone when I plug it in. But nothing pops up. I don't think USB debugging is on...
I'll check out the link.
Sent from my SGH-I747 using xda app-developers app
Yep, that is a custom recovery. If you have questions post them here. I'll be around for a little while.
I think I am so close.
I got the adb and fastboot files, and upon checking devices in fastboot, it does say that my device is connected.
But I cant get the adb driver to put the files on my phone.
Im using "adb push -d C:\android1\cm-10.1-20121214-NIGHTLY-mako.zip
And it says device not found?
Sorry for the questions, but thank you for the help.
Chris
(and im in the directory where the adb file is located)
(Once I get this resolved... im always gonna have one backup on my phone)
wizshaw said:
I think I am so close.
I got the adb and fastboot files, and upon checking devices in fastboot, it does say that my device is connected.
But I cant get the adb driver to put the files on my phone.
Im using "adb push -d C:\android1\cm-10.1-20121214-NIGHTLY-mako.zip
And it says device not found?
Sorry for the questions, but thank you for the help.
Chris
(and im in the directory where the adb file is located)
(Once I get this resolved... im always gonna have one backup on my phone)
Click to expand...
Click to collapse
Ok. The best way is to open the command prompt from the folder in which you have adb. The easy way to do that is hold down shift and right click. Then choose open window here.
Next, once you are booted into recovery type
Code:
adb devcies
If it returns a number then proceed to push the file. (Its easy to make a typo so change the file to something easy like cm10.zip)
So you would type
Code:
adb push cm10.zip /storage/emulated/0
I erased everything the other day by mistake and total noobishness Lol. I just used wugs tool kit to flash the stock image back. Might be useful if struggling with adb etc.
Sent from my Nexus 4
slymobi said:
I erased everything the other day by mistake and total noobishness Lol. I just used wugs tool kit to flash the stock image back. Might be useful if struggling with adb etc.
Sent from my Nexus 4
Click to expand...
Click to collapse
What is anyone going to learn by using a toolkit?! I commend the OP for putting in the time to learn how to use adb. So in the future if they were to run into a problem they would know how to easily fix it.
Sent from my Nexus 4
I got it guys.
I realized that fastboot and adb only get activated in their respective UI's... And i refined my CMD commands a bit after a little more reading.
Problem solved. And i learned more about the android platform in the process. Time well spent.
I want to formally thank you guys. This is why this community is great.
Chris