Flash_Image command not found - myTouch 3G Slide Q&A, Help & Troubleshooting

Hello All,
I just updated my ROM to CR_Mod_2.13.531.1_OTA's
And then when I went to reboot into recovery I got the red Triangle exclamation, and thus decided to reflash my recovery image by using the terminal, and even in adb, I get "Flash_image" command not found, and I've tried googling (So please spare me the rude comments about learning to use it) and come with little to luck with finding a method of what went wrong with this. If anyone can shed some light on this, and what I can do to fix it so I can get into my recovery again would be a great help.
-Thanks

soulysephiroth said:
Hello All,
I just updated my ROM to CR_Mod_2.13.531.1_OTA's
And then when I went to reboot into recovery I got the red Triangle exclamation, and thus decided to reflash my recovery image by using the terminal, and even in adb, I get "Flash_image" command not found, and I've tried googling (So please spare me the rude comments about learning to use it) and come with little to luck with finding a method of what went wrong with this. If anyone can shed some light on this, and what I can do to fix it so I can get into my recovery again would be a great help.
-Thanks
Click to expand...
Click to collapse
same here friend when i find teh answer ill be sure to let u know

so when in terminal to try place Flash_image into /system/bin:
cp /sdcard/flash_image /system/bin
I get:
cp: can't create ' /system/bin/flash_image ' cannot allocate memory

When you get to the triangle with the Exclamation point
All you have to do is stay at that screen and click
VOLUME UP and POWER
then it will show you the options.

soulysephiroth said:
so when in terminal to try place Flash_image into /system/bin:
cp /sdcard/flash_image /system/bin
I get:
cp: can't create ' /system/bin/flash_image ' cannot allocate memory
Click to expand...
Click to collapse
You have to have s-off and /system mounted as r/w to do that. Otherwise you have to push it to /system/bin while in clockwork recovery.
@ xologist, I think they're looking to flash the clockwork recovery image, not the update.zip and stock recovery old way.
To mount system r/w within android tyoe mount -o rw,remount /system and try the copy again.
Sent from my T-Mobile myTouch 3G Slide

Well thats problem, I can't even access my recovey, thats why I'm trying to flash a new image. everytime I try I always get
"Error writing recovery: No space left on device"

soulysephiroth said:
Well thats problem, I can't even access my recovey, thats why I'm trying to flash a new image. everytime I try I always get
"Error writing recovery: No space left on device"
Click to expand...
Click to collapse
That means you don't have s-off. There's a stickied thread in the development section, an alpharev live linux CD that you can use to patch your phone's bootloader to allow you to write to protected partitions like /system, recovery, etc.

Related

Busybox?

Root from Paul didn't come with one, and seeing as we can't get full system access (from what i understand) im curious as to if we can actually get busybox?
The 'busybox on rooted desire' on MoDaCo didn't help at all.
I've installed bb via Titanium, yet Metamorph didn't recognise it anywhere.
Cheers in advance for help
It comes with A2SD - but you can push the busybox binary to /system while the phone is in recovery.
If you pushed bb yourself, use its absolute path (like /data/somewhere/busybox) or put its path in your $PATH to get it going. I personally, without root, put busybox in the free-to-write-to /sqlite* directory (I put * because I don't recall the full name) and it runs fine from there.
do you have a link to apps2sd & does it come with a guide as to how to install it so noobs can understand?
A2SD was taken down "temporarily".
http://android.modaco.com/content/h...ide-now-with-new-improved-easier-root-method/
Sorry
Although this still seems to work:
http://android.modaco.com/content/htc-desire-desire-modaco-com/307398/apps2sd-miniguide/
LeszekSwirski said:
Although this still seems to work:
http://android.modaco.com/content/htc-desire-desire-modaco-com/307398/apps2sd-miniguide/
Click to expand...
Click to collapse
Bare in mind I think it was taken down as (for some) it 'removed root' and also got some phones stuck in a reboot loop. Bad times.
GANJDROID said:
Root from Paul didn't come with one, and seeing as we can't get full system access (from what i understand) im curious as to if we can actually get busybox?
The 'busybox on rooted desire' on MoDaCo didn't help at all.
I've installed bb via Titanium, yet Metamorph didn't recognise it anywhere.
Cheers in advance for help
Click to expand...
Click to collapse
You didn't read to the end of that thread
* install Titanium
* run Titanium
* click the "problems" button and install Busybox
* boot into recovery
* adb shell from my Mac
* mount /system
* cp /data/data/com.keramidas.TitaniumBackup/files/busybox /system/bin
* cd /system/bin
* ./busybox --install -s .
Click to expand...
Click to collapse
By what I've read, though, Metamorph dies on its arse because of the lack of system rw access.
Loccy said:
You didn't read to the end of that thread
Click to expand...
Click to collapse
Aye, I read that, but no Mac, and I can't get to the folder where Titanium saved bb to (assuming that because it's not on the sd card in any data or the titanium folders) the phone system(?)
jayshah said:
Bare in mind I think it was taken down as (for some) it 'removed root' and also got some phones stuck in a reboot loop. Bad times.
Click to expand...
Click to collapse
Had heard about that, but I think he may be working for a solution?
From what I can remember from the rooting guide he said it was 'currently unavailable'
GANJDROID said:
Had heard about that, but I think he may be working for a solution?
From what I can remember from the rooting guide he said it was 'currently unavailable'
Click to expand...
Click to collapse
Yeah, hence it's hopefully only temporary.
GANJDROID said:
Aye, I read that, but no Mac, and I can't get to the folder where Titanium saved bb to (assuming that because it's not on the sd card in any data or the titanium folders) the phone system(?)
Click to expand...
Click to collapse
Install Titanium. Then get your phone into recovery using Paul's Linux ISO. In the Linux console (i.e. where you'll have typed ./step2.sh to get the recovery up), you should be able to do adb shell from there. Then follow my instructions from mount /system onwards.
I didn't follow Pauls guide as I only have access to Windows, so I used the lanarchy guide, which I think might have been taken from The Unlockr.
Maybe fill me in w/ bb according to that?
i am a bit ashamed to ask this but:
....
* boot into recovery
* adb shell from my Mac
* mount /system
....
boot into recovery -> ok
adb shell from mac.. ok? hm, i have macos as a seperate installation and i used it for rooting, so there is a pushfiles folder with recovery-mac.sh.. sudo ./recovery-mac.sh?
How do i mount /system then? Don't know where to navigate to find access to the sdcard . @volumes there are only my harddrive partitions, can't see the sdcard?
No idea, sorry, first time (ok, second time after root) i get in touch with adb, mac, sudo wtf?
Ok, all you need is some kind of environment where adb actually works.
Get your phone into recovery (the green menu screen) using whatever means or method you have.
Then, if you have Windows, you'll need the Android SDK. Ditto on a Mac. Anything with adb so that you can plug your device into your computer, do adb shell, and get a shell window up. Then
mount /system
onwards.
The key is that your phone needs to be in recovery before you do adb shell, otherwise you have no r/w access to /system.
ah! ok, perfect. The android sdk is on my windows computer, the push-files on my mac, that's the problem
thanks for your help!
the recovery is not the problem, but mount /system did nothing because there is no android sdk on my mac.. got it now i think.
mount system -> ok
copy busybok -> ok
when i try to install i get dozens of lines with "no such file or directory".
reboot -> phone not booting, hangs when displaying the HTC Logo omg
flash rom again?
same problem as watercool. Loads of "No such file or directory" messages.
But, I rebooted and it went through as normal, booted the OS fine.
hm, dont want to wipe again, pff..
flashed AhmgskMod mod again without wiping, everything ok now
watercool said:
mount system -> ok
copy busybok -> ok
when i try to install i get dozens of lines with "no such file or directory".
reboot -> phone not booting, hangs when displaying the HTC Logo omg
flash rom again?
Click to expand...
Click to collapse
Sounds like you missed the . off of the end of the
./busybox --install -s .
command.
You need that . if you're following my instructions.
ok, i did it with and without the "."
With the dot there was no response (so probably it installed correctly?).
Anyway it didn't boot afterwards. i will try it again
edit: ok, tried again and my phone stucks @ htc screen
i think busybox is installed but for some reason it doesn't boot (using the ahmgsk mod)
anyway, thanks for your kind help!

"mount /dev/block/mtdblock3 /system:not found"

im trying to get rom manager to work and have read the instruction on puttin reboot file in the tools folder of sdk ...ok so far
HERE'S the NOOB bit!
when i type "mount /dev/block/mtdblock3 /system"
i get an error "
whats up with that ....not sure if i should have switched my phone off or hadit in recovery at this point...i did try the whole process with phone in recovery but i couldnt get adb shell going if phone wasnt on
remember,when you dont know...you REALLY dont know
Sorry to be so basic...but if i can just get this to work ,ill be over the finish line!
PS. the Clockwork recovery on RM is 1.8.1.7 (if that helps)
Assuming you have the update.zip already on you SD card.
Power up the phone while holding down volume -.
Connect to USB.
Select recovery using the volume buttons and confirm with power.
On the red exclamation mark; press volume up and power.
Flash the update zip from SD card. (Might be controlled by optical trackpad)
Code:
./adb-linux shell mount /system
Thanks ,
I have already flashed the update and all works fine, I can enter recovery no problem, just not sure why I'm getting the error when trying to to do the above step, ill try again tonight I guess
Because you're specifying an invalid device to mount.
Try only
mount /system (if you are in the shell)
or
./adb-linux shell mount /system
instead.
InspectorFrost said:
im trying to get rom manager to work and have read the instruction on puttin reboot file in the tools folder of sdk ...ok so far
HERE'S the NOOB bit!
when i type "mount /dev/block/mtdblock3 /system"
i get an error "
whats up with that ....not sure if i should have switched my phone off or hadit in recovery at this point...i did try the whole process with phone in recovery but i couldnt get adb shell going if phone wasnt on
remember,when you dont know...you REALLY dont know
Sorry to be so basic...but if i can just get this to work ,ill be over the finish line!
PS. the Clockwork recovery on RM is 1.8.1.7 (if that helps)
Click to expand...
Click to collapse
You can mount /system via recovery menu.. does it give You the same error?

[GUIDE] Flash any recovery easily on the phone using flash_image

Background
To update (flash) a recovery image onto your phone allows you to update or replace your recovery environment on your phone. There are a number of ways to flash a new recovery image, some of the more commonly used methods are using a tool such as ROM Manager or using development tools such as Fastboot. There is also a third method using a standalone utility "flash_image" which allows the flashing of recovery using the terminal emulator on the phone.
flash_image is not a new tool, it has been used on Android since the beginning, many custom ROMs include the utility as part of the ROM itself though not all stock ROMs (including the stock ROM on the G2) include it.
Requirements
1. A permanently rooted (with S-OFF) phone
2. The flash_image binary
3, A recovery image that is compatible with your phone and ROM
3. A terminal emulator application on the phone or use of an ADB shell
Overview:
1. Get the flash_image binary and recovery image onto your phone
2. Copy or move the flash image binary to your system and make executable
3. Use flash_image to update your recovery environment
Stage 1: Get flash_image and recovery image on your phone
1. Download the flash_image binary (not needed if you are running a custom ROM that includes this binary)
2. Download the recovery image you wish to use
You can either directly download the files onto your phone or onto your PC and transfer to your phone. Probably the easiest way to do this is to connect your phone to your computer via USB and mount USB storage, then copy the files to your SD Card. Alternatively you can use ADB Push, bluetooth file transfer or several other methods.
Stage 2: Copy or move the flash image binary to your system and make executable
In terminal emulator:
su
mount -o remount, rw /system
cd /sdcard (or wherever you downloaded/copied the file)
cp flash_image /system/bin
cd /system/bin
chmod 777 flash_image
Click to expand...
Click to collapse
Stage 3: use flash_image to update your recovery environment
In terminal emulator:
su (not needed if using the same terminal session used in the steps above)
cd /sdcard (or wherever you downloaded/copied the recovery image)
flash_image recovery recovery.img (use the appropriate file name for the image file you are flashing)
Click to expand...
Click to collapse
Reboot into recovery and verify that the correct recovery environment is installed
Notes
Any of the commands that call for using a terminal emulator on the phone should work fine using an ADB shell if you prefer.
This was tested on G2 but I can't think of why it would not work on Desire Z or any other phone for which this version of flash_image works. Obviously different phones have different compatible recovery images.
I've attached a zip file containing the flash_image binary that I extracted from the CM 6.1 update zip. I suspect most custom ROMs already have flash_image.
If you are wondering "Why should I use this method over using ROM Manager?" you could be using a recovery image that ROM manager doesn't support, for example ClockWorkMod Recovery 3.x which is required for some experimental ROMs.
If you are wondering "Why should I use this method over using fastboot?" The two main reasons are you can't use fastboot if you are not with a computer with working ADB and using fastboot requires that you have previously flashed the engineering HBOOT.
This is my first guide so I'm open to suggestions or feedback.
Nice one
Though I would suggest that
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
could be simplified to :
Code:
mount -o remount,rw /system
Edit - actually /system isn't even on /dev/block/mtdblock3, and it's not a yaffs2 file system, I suspect that's come from another phone model ?
"dd" will do exactly the same, but no need to install extra stuff since its already there.
dhkr123 said:
"dd" will do exactly the same, but no need to install extra stuff since its already there.
Click to expand...
Click to collapse
I wouldn't have a problem using dd myself. But I would have thought it was much more risky, since instead of typing something relatively user-friendly like "recovery", you're typing in /dev/xyz/abc or similar, which if you get it slightly wrong could be disastrous ?
Excellent, worked for me, flashed CW 3.0 without fastboot
steviewevie said:
Nice one
Though I would suggest that
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
could be simplified to :
Code:
mount -o remount,rw /system
Edit - actually /system isn't even on /dev/block/mtdblock3, and it's not a yaffs2 file system, I suspect that's come from another phone model ?
Click to expand...
Click to collapse
Interesting, I've been using that command since forever (since I first rooted my G1 in early 2009) and it definitely does work on my G2 as well as my wife's MT4G.
I just tried "mount -o remount,rw /system" on my phone and it does not work, mount gives me the "Usage:" messages which seems to mean it wants more parameters.
steviewevie said:
I wouldn't have a problem using dd myself. But I would have thought it was much more risky, since instead of typing something relatively user-friendly like "recovery", you're typing in /dev/xyz/abc or similar, which if you get it slightly wrong could be disastrous ?
Click to expand...
Click to collapse
Unless you run wpthis before dd, you're perfectly safe. The radio partitions are all protected by the power-on write protect feature of the eMMC AS WELL as the linux kernel write protect on low addresses. Worst you can do is blow away your system, data, cache, misc, boot, or recovery partitions, and these are trivial to recover from.
raitchison said:
Interesting, I've been using that command since forever (since I first rooted my G1 in early 2009) and it definitely does work on my G2 as well as my wife's MT4G.
I just tried "mount -o remount,rw /system" on my phone and it does not work, mount gives me the "Usage:" messages which seems to mean it wants more parameters.
Click to expand...
Click to collapse
Depends on whether or not the mount command can tell the associations between the devices and mount points, which is determined by either system configuration, or what mount command you are using (i.e. android's mount or busybox mount).
raitchison said:
Interesting, I've been using that command since forever (since I first rooted my G1 in early 2009) and it definitely does work on my G2 as well as my wife's MT4G.
I just tried "mount -o remount,rw /system" on my phone and it does not work, mount gives me the "Usage:" messages which seems to mean it wants more parameters.
Click to expand...
Click to collapse
Sorry, there should have been an extra space, this works on my phone :
Code:
mount -o remount, rw /system
I don't have a "/dev/block/mtdblock3" on my system. My system partition is mounted on /dev/block/mmcblk0p25, and it is ext3 not yaffs2.
What ROM are you running ? I am running the stock DZ 1.34 ROM. I wonder if you are running Gingerbread ?
steviewevie said:
Sorry, there should have been an extra space, this works on my phone :
Code:
mount -o remount, rw /system
I don't have a "/dev/block/mtdblock3" on my system. My system partition is mounted on /dev/block/mmcblk0p25, and it is ext3 not yaffs2.
What ROM are you running ? I am running the stock DZ 1.34 ROM. I wonder if you are running Gingerbread ?
Click to expand...
Click to collapse
I'm running the Stock G2 T-Mobile post-OTA ROM, definitely not Gingerbread.
Edit: I just tried your method and it works, I will update the guide because your way is simpler and sounds like a safer choice.
you could just rename the CW 3.x.x recovery to the exact named recovery slap it in the cloclwork download folder after you delete the old one and flash it with CW just a quicker trick for GB roms
Not sure that's actually quicker, at least I don't think it would be for me, especially if you are changing recoveries with any frequency (like if tying out Gingerbread ROMs then going back to a 2.2 ROM) because you'd need to constantly rename your recovery images. With my method you would only need to leave the two files named as they are, or for expediency you could rename to recovery.img and recovery3.img then when you wanted to switch you could just execute:
flash_image recovery recovery.img
Click to expand...
Click to collapse
or
flash_image recovery recovery3.img
Click to expand...
Click to collapse
Depending on which recovery you wanted at that point & time.
As I said in the guide, there are already a number of options available, using ROM Manager and fastboot are the most commonly seen in guides but your method and mine are other options for people for whom they work better.
Works!!!
Hi my friends!
It worked for me flawlessly. I was using virtuos 0.9 on my desireZ
Great description, but file did not work for me
It's a very good description that a novice like me can follow. And, I am sure the provided file works for many of you, since many of you reported it to work. After following this guide, and not getting it to work (Stopping Signal error), I decided to find another binary file for flash_image, and the other flash_image file worked for me on my Sprint CDMA Hero. My phone currently has aospMod v0.9.9.2 | AOSP 2.2.1(12/10/2010), if it matters.
One can download a flash_image from here http://cyanogen-files.carneeki.net/flash_image.zip
Then unzip and place on sdcard - follow all the steps in the original post of this thread.
It is my understanding that this file is not unique for different android phones, but if I am incorrect, someone please reply to this thread to correct me.
Again, great job in summarizing the steps.
Regards,
Sanjiv
so darn easy! thank you!
Also usable for splash screen ??
Just curious,
Anybody tried to use flash_image to flash a custom splash screen ?
Something like :
flash_image splash1 customsplash.img
very good post for a newbie like me, just want to make sure, do i need to do the stage 2 every time I flash the recovery?
jaoyina said:
very good post for a newbie like me, just want to make sure, do i need to do the stage 2 every time I flash the recovery?
Click to expand...
Click to collapse
No, you only need to do stage 2 once, whenever you update/change recoveries from that point forward just use stage 3.
Is there a way I can reflash a recovery without access to the ROM?
I'm stuck at the HTC splash screen, so I'm basically stuck in my current (broken) recovery.
sanjivp2000 said:
One can download a flash_image from here (..)[/URL]
Click to expand...
Click to collapse
The flash_image in the start post did not work for me, the one above did.
Also, my HTC Hero was missing the cp command.
Instead, I used: cat /sdcard/flash_image > /system/bin/flash_image
Successfully flashed recovery again

[Q] How to put a ROM on read-only /sdcard, while adb shell not working

I've been searching my _ off for two days now to find a solution for my problem, but I can't find one working for me.
What I do have right now:
NO working ROM (I believe because of a failed atempt to revert to a backup in CWM)
Access to my bootloader (unlocked through HTCDev)
Access to my recovery (Which is the latest CWM)
Fastboot/adb working
Phone boots upon the HTC logo screen
NO ROM zipfile on the SD-Card (I accidentilly deleted that, I still hate myself for that)
I've managed to push to ROM file into both /data and /system, which (ofcourse) isn't usefull to flash from because they don't show up in CWM.
What I've tried:
Reverting to a Nandroid backup, I've 2 on the sdcard. Both don't pass the part where /system is being restored.
'asd shell' to push files, or mount the SD card, does not work. First I had the error saying '--exec /system/bin/sh failure: file or dir not found (2)'. I managed to push the sh file into system, (and I believe into /system/bin), and the error changed to '[...] No directory (20)'
asd push /sdcard/; doesn't work because /sdcard is read-only.
In CWM I can't mount as USB storage, is says something about a file which can't be found.
TWRP recovery doesn't work on my device, I can touch whatever I wan't, the only button responding is the power button, which causes a locked recovery, which I can't unlock. (You need to swipe for that, which my phone seems to ignore).
I've read almost every topic on XDA and whatever Google could give me, but most solutions somewhere relied on the asd shell, or pushing into the /sdcard, or simply assume I still can mount as USB storage.
Does anyone have any suggestions left on howto get a ROM into the /sdcard so I can flash it? I would be thanking you forever!
Thanks in advance!
No ADB shell, then adb push *filename* /sdcard?
Maybe sideload a ROM?
Sent from my GT-I9300 using Tapatalk 4 Beta
I can't push files to the /sdcard since it's an read-only directory.
I tried the sideload part, but instead of executing something, it shows me the help of adb.
Any clue how to fix my shell, or get a ROM on it?
Tried typing 'adb remount' a few times and trying again?
Also, you should update your CWM to latest version so you can mount sdcard
tomascus said:
Tried typing 'adb remount' a few times and trying again?
Also, you should update your CWM to latest version so you can mount sdcard
Click to expand...
Click to collapse
I tried using remount, but that is to remount the /system partition right? I can put the ZIP on the /system partition. But CWM can't install from there.
I'm using the last version of CWM, but it gives me an error about a file not being found, so I can't mound as USB Storage device.
I returned the phone, to the store. I pretty much gave up after another few hours of struggling.

Moto 360 5.0.1 update file

http://android.clients.google.com/p...ned-metallica-LWX48P-from-KNX01S.98cdf4ca.zip
to update:
Go into a shell on the watch with su and...
mount -o rw,remount /dev/block/mmcblk0p15 /cache
mv /sdcard/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip /cache/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/cache/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
Nice ty
See above
abuttino said:
See above
Click to expand...
Click to collapse
I was trying to do it thought ADB I'm just new to this and I ended up re posting in the wrong thread.
Im Not new to flashing via recover on phones but on adb through commands I always feel sketchy about it.
I keep getting permission denied
Ive ran root a few times I have the drivers install right for sure not sure what im doing wrong
NUGZZ420 said:
I keep getting permission denied
Ive ran root a few times I have the drivers install right for sure not sure what im doing wrong
Click to expand...
Click to collapse
Throw an "su" command in the shell before anything else. It will only work if you're rooted.
I don't really get it how to connect via shell to my watch. Is it the same as installing apk's over adb bluetooth debugging bridge?
Could you provide further instructions how to install the update manually?
Thanks!
Kamekazegoldi said:
I don't really get it how to connect via shell to my watch. Is it the same as installing apk's over adb bluetooth debugging bridge?
Could you provide further instructions how to install the update manually?
Thanks!
Click to expand...
Click to collapse
Is your watch rooted? If not, you can't do it
No further questions thanks!
abuttino said:
http://android.clients.google.com/p...ned-metallica-LWX48P-from-KNX01S.98cdf4ca.zip
to update:
Go into a shell on the watch with su and...
mount -o rw,remount /dev/block/mmcblk0p15 /cache
mv /sdcard/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip /cache/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/cache/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
Click to expand...
Click to collapse
Worked (almost) perfect! Except, the "mv" command caused it to error out with "Invalid Arguement:Cross-Device Link" (Due to the implementation of blocked cross device linking with the mv command, bypassable by just cp'ing) Just replaced it with "cp" and the problem was solved.
Though this has already been said, the 4.4w1 insecure boot.img no longer roots 5.0.1. Probably due to incompatibilliuies, I'll work up a new rooted boot.img this weekend. Sadly looks like its going to require flashing the boot.img, not just booting it.
How do you go on a shell on your watch?
You have to have the bootloader unlocked and rooted hooked up via Modded USB cable. Then use the super tool script iin the dev section to install drivers for fastboot. Then back out to that folder make sure you not clicked on anything right click anywhere I think but I right click on the fastboot file while holding the SHIFT key and open in command window the type adb devices to make sure you hooked up right and you have accepted it on your phone Witch you must click accept the adb on your phone to accept the computer access. Once you know your hooked up right type adb shell and boom there you go.
having some trouble.
I've got shell, and then su, i've got a prompt with #
Tried the mv command, and like that other guy, got a cross link error. So i tried cp instead of mv, and now get no such file or directory...
I should mention I'm doing this from adb on Windows. Am I missing something??
Prfndhatrdofman said:
having some trouble.
I've got shell, and then su, i've got a prompt with #
Tried the mv command, and like that other guy, got a cross link error. So i tried cp instead of mv, and now get no such file or directory...
I should mention I'm doing this from adb on Windows. Am I missing something??
Click to expand...
Click to collapse
Try this its what worked for me
coming from KNX01S, but I keep running into "Status 7" with the stock recovery and "Error executing updater script" with TWRP. Anybody have any better luck flashing this?
SOLVED!: I removed the get prop lines in the beginning of the update script and sideloaded in TWRP!
If anybody would like the modified package it can be found here: https://dl.dropboxusercontent.com/u/...360/update.zip
This was not my fix only copied and pasted
NUGZZ420 said:
Try this its what worked for me
coming from KNX01S, but I keep running into "Status 7" with the stock recovery and "Error executing updater script" with TWRP. Anybody have any better luck flashing this?
SOLVED!: I removed the get prop lines in the beginning of the update script and sideloaded in TWRP!
If anybody would like the modified package it can be found here: https://dl.dropboxusercontent.com/u/...360/update.zip
This was not my fix only copied and pasted
Click to expand...
Click to collapse
That Dropbox link seems to be down, do you still have that modified TWRP zip?
Found the original post, here's the original link: https://dl.dropboxusercontent.com/u/9407677/Moto 360/update.zip
Looks like the link text got shortened when copying/pasting, but it's all good now! Thanks for sharing!
Prfndhatrdofman said:
having some trouble.
I've got shell, and then su, i've got a prompt with #
Tried the mv command, and like that other guy, got a cross link error. So i tried cp instead of mv, and now get no such file or directory...
I should mention I'm doing this from adb on Windows. Am I missing something??
Click to expand...
Click to collapse
Make sure your using "/cache" instead of "/cache/"
nissanskylinebam said:
That Dropbox link seems to be down, do you still have that modified TWRP zip?
Found the original post, here's the original link: https://dl.dropboxusercontent.com/u/9407677/Moto 360/update.zip
Looks like the link text got shortened when copying/pasting, but it's all good now! Thanks for sharing!
Click to expand...
Click to collapse
Sorry I had been running all day and beat here my own just in case it helps same zip just my own link
5.0.1 update zip Mirror https://www.dropbox.com/s/naliirhnblh6ihg/update.zip?dl=0
npjohnson said:
Worked (almost) perfect! Except, the "mv" command caused it to error out with "Invalid Arguement:Cross-Device Link" (Due to the implementation of blocked cross device linking with the mv command, bypassable by just cp'ing) Just replaced it with "cp" and the problem was solved.
Though this has already been said, the 4.4w1 insecure boot.img no longer roots 5.0.1. Probably due to incompatibilliuies, I'll work up a new rooted boot.img this weekend. Sadly looks like its going to require flashing the boot.img, not just booting it.
Click to expand...
Click to collapse
Look forward to flashing the Rooted boot.img.
Thank you for doing it.
Update Today
In past day i have update to 5.0.1 LWX48P release. Today i have received automatic update on my watch to 5.0.1 LWX48T release. I don't know what is change but in past day I noticed a problem centering of my display; after update now the display is centered
http://shabbypenguin.com/?developer=Tools&folder=Superuser
flash that in TWRP to get root
latest update: https://mega.co.nz/#!dNBnyT7Q!qtPkmgOV-jrajJAAKDLE6cQWVHyDGi3OsEwmTq5jfOU LWX48T-from-LWX48P follow OP's instructions but change teh file names

Categories

Resources