Related
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!
Can someone please help?
I'm trying to edit the system\etc\bluez\main.conf file using root explorer.
I can edit the line I want, save and exit but it then reboots the phone automatically and the original unedited file is back.
What am I doing wrong?
BTW the phone is rooted and this is why I want to edit the file...
http://forum.xda-developers.com/showthread.php?t=676175
neomagik said:
Can someone please help?
I'm trying to edit the system\etc\bluez\main.conf file using root explorer.
I can edit the line I want, save and exit but it then reboots the phone automatically and the original unedited file is back.
What am I doing wrong?
BTW the phone is rooted and this is why I want to edit the file...
http://forum.xda-developers.com/showthread.php?t=676175
Click to expand...
Click to collapse
As we don't have write access to /system on a normal booted desire, you have to do all your work in recovery-mode.
I can get into recovery mode ok but how do I edit the file I want from there?
The options I have are:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip from sdcard
- Wipe
- Partition sdcard
- Other
- Power off
Extract the file out of the rom, change it, than push it back to the rom.
You can do that from ADB shell while your phone is in recovery.
You can find commands how to backup files and push/delete them back to ROM on this forums, or you can search it on internet.
dont forget to mount /system
adb shell in a new terminal screen
then mount /system
I can't figure out what I'm doing wrong.
I've tried the method suggested by allla and ivicask ie, using adb commands in recovery mode and I get the same result as using root explorer, the file appears to have copied successfully it reboots but the original file is back again
I've also tried vastlopers method and after lots of reading found that the device needs to be booted normally to 'remount' however when I try to push the file now it says "Directory not empty"
It seems to me that this adb method is just a long winded alternative to root explorer, none of which get the desired result.
Please help?
Bump. Bump.
I've now tried adb file explorer but can't figure out how to install Busybox on my device.
I'm out of ideas. Someone must know how to edit/overwrite the main.conf file.
I'm being told elsewhere on this Forum that the Desire cannot yet be fully rooted for r/w access to the /system/ folder. Is this correct?
neomagik said:
I'm being told elsewhere on this Forum that the Desire cannot yet be fully rooted for r/w access to the /system/ folder. Is this correct?
Click to expand...
Click to collapse
Yes it is. It's also written in the root tutorial!
galaxy nexus 4.1.1 (JRO03C).
backed up & restored all apps and sdcard using GNex Toolkit v7.8.
after restoring, sdcard seems to be read-only, applications complain about "open failed: EACCES Permission denied" when trying to open files in /storage/sdcard0/... . tried remount, didn't help. directory permissions look fine to me.
what am i doing wrong?
how about trying to open /sdcard/?
and dont use a toolkit..
sent from my i9250
I bet you've done something on toolkit. I always backup and restore, but I have no problem at all
Can you install app from play store? If so, install root browser. It has a feature where you can change permission.
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
bk201doesntexist said:
how about trying to open /sdcard/?
Click to expand...
Click to collapse
what do you mean by opening /sdcard ? the message above comes from an application which worked fine before backup-restore.
i can read files from /sdcard, it's just that the applications cannot write there.
e.g. camera does not work either.
kyokeun1234 said:
I bet you've done something on toolkit. I always backup and restore, but I have no problem at all
Can you install app from play store? If so, install root browser. It has a feature where you can change permission.
Click to expand...
Click to collapse
i've had this exact same problem twice in a row when restoring to two different nexuses (nexi?)
so i'm trying to find out what am i doing wrong.
yes, i can install applications. i already have ES file explorer installed; which permissions should I change? all permissions look fine to me.
All the permissions should be checked. I dunno about es file explorer, but on root browser, you'll have to check all the permissions like this
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
op, have you tried fixing permissions in recovery?
sent from my i9250
kyokeun1234 said:
All the permissions should be checked. I dunno about es file explorer, but on root browser, you'll have to check all the permissions like this
Click to expand...
Click to collapse
mine permissions for /sdcard (/storage/sdcard0) are 775. is this a problem? it won't let me change them to 777...
bk201doesntexist said:
op, have you tried fixing permissions in recovery?
Click to expand...
Click to collapse
how do i do this? i've found this page: wiki.cyanogenmod.com/wiki/Fix_permissions (cannot post links), but running "fix_permissions" from terminal emulator gives me
Code:
[email protected]:/ $ su
[email protected]:/ # fix_permissions
sh: fix_permissions: not found
or do i have to boot into recovery first? (22 -> 4 from gnex toolkit)? how do i run terminal emulator then?
sorry, i'm really new with android..
qot said:
how do i do this? i've found this page: wiki.cyanogenmod.com/wiki/Fix_permissions (cannot post links), but running "fix_permissions" from terminal emulator gives me
Code:
[email protected]:/ $ su
[email protected]:/ # fix_permissions
sh: fix_permissions: not found
or do i have to boot into recovery first? (22 -> 4 from gnex toolkit)? how do i run terminal emulator then?
sorry, i'm really new with android..
Click to expand...
Click to collapse
boot into recovery, run the menus, but i think on cwm it's under Advanced > Fix permissions. wth? using a toolkit to BOOT into recovery? jeez... just power down the device, press vol up+vol down+power, select Recovery with vol keys, press start to boot into your currently installed recovery.
bk201doesntexist said:
boot into recovery, run the menus, but i think on cwm it's under Advanced > Fix permissions. wth? using a toolkit to BOOT into recovery? jeez... just power down the device, press vol up+vol down+power, select Recovery with vol keys, press start to boot into your currently installed recovery.
Click to expand...
Click to collapse
when I do this, i get a lying android with an exclamation mark in read triangle. is this "recovery"?
it does not seem to respond to any key, volume or power...
... somehow i got the following menu:
Code:
Android system recovery <3e>
Volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
which one should i select to fix permissions?
i've also found an app in play market called "fix permissions"
when i run it, i can select an application and it says "Permissions fixed, UIDs aligned".
however, nothing changes, sdcard is still not writable.
okay, you dont have a custom recovery installed. look for cwm latest non-touch, or twrp.
the stock recovery doesn't have this option.
is it only me or this is becoming quite freakin old very fast, we replying to "i used a toolkit to do"? i know this is q&a, but how in the hell how are we supposed to troubleshoot this?
i can only think of "redo things manually like it's supposed to." and to myself i think "witness the simplicity of command line interfaces and weep".
sent from my i9250
bk201doesntexist said:
okay, you dont have a custom recovery installed. look for cwm latest non-touch, or twrp.
the stock recovery doesn't have this option.
is it only me or this is becoming quite freakin old very fast, we replying to "i used a toolkit to do"? i know this is q&a, but how in the hell how are we supposed to troubleshoot this?
i can only think of "redo things manually like it's supposed to." and to myself i think "witness the simplicity of command line interfaces and weep".
Click to expand...
Click to collapse
i'd be glad to redo things manually, or whatever it takes to make sdcard writable again. this is really a nuisance.
i've downloaded "recovery-clockwork-6.0.1.0-maguro.img" and did the following from fastboot:
Code:
C:\Fastboot>fastboot devices
01498B0C1200F013 fastboot
C:\Fastboot>fastboot flash recovery recovery-clockwork-6.0.1.0-maguro.img
sending 'recovery' (4894 KB)... OKAY [ 0.703s]
writing 'recovery'... OKAY [ 0.757s]
finished. total time: 1.460s
C:\Fastboot>fastboot reboot
rebooting...
finished. total time: 0.006s
however, when i reboot into recovery again, i still get "Android system recovery <3e>"
am i doing something wrong?
I've also tried this with "fastboot flash recovery openrecovery-twrp-2.2.2.0-maguro.img" instead, no errors, same result.
check for /system/recovery-from-boot.p. is it there? rename it to recovery-from-boot.p.bak.
reflash recovery.
note: you can try 'fastboot boot recovery.img'.
sent from my i9250
bk201doesntexist said:
check for /system/recovery-from-boot.p. is it there? rename it to recovery-from-boot.p.bak.
Click to expand...
Click to collapse
yes, this worked. thanks!
however, even after i've installed twrp and ran "fix permissions", the problem remains exactly the same: applications complain about not being able to write to sdcard; camera does not work, etc. etc..
forget your data and start fresh manually by flashing factory images manually through fastboot.
sent from my i9250
It's not a permissions issue, it's an ownership issue...
If you have any directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
danger-rat said:
It's not a permissions issue, it's an ownership issue...
If you have any directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
Click to expand...
Click to collapse
yeah, thats it, i forgot. thanks.
sent from my i9250
danger-rat said:
It's not a permissions issue, it's an ownership issue...
If you have any directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
Click to expand...
Click to collapse
that was it, thank you so much!
danger-rat said:
It's not a permissions issue, it's an ownership issue...
If you have any directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
Click to expand...
Click to collapse
thanks a ton!
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.
Ok I have a firetv 2 and am already rooted but I don't really understand on how to install the recovery tool. I assume that I can just install it without having to run a custom rom or am I wrong. I don't really want to have to reset my whole FTV if I don't have to. Is there a link with a how to on just installing TWRP? Thanks
fomoco460 said:
Ok I have a firetv 2 and am already rooted but I don't really understand on how to install the recovery tool. I assume that I can just install it without having to run a custom rom or am I wrong. I don't really want to have to reset my whole FTV if I don't have to. Is there a link with a how to on just installing TWRP? Thanks
Click to expand...
Click to collapse
Ok so the best place for what your looking for is here -
http://www.aftvnews.com/how-to-root-the-amazon-fire-tv-2/
Give aftvnews the credit for this guide
& underneath is the guide, credit for recovery & guide this is to rbox
Installation
You can copy the files to /sdcard, a USB storage device, or an sdcard. I will be using /sdcard in the instructions, but you can replace it with /storage/usbotg for USB or /storage/sdcard1 for an sdcard.
Copy the zip file to your destination.
Connect adb
Code:
adb connect IPADDRESS
Open an adb shell
Code:
adb shell
Run the zip file (replace vX with the actual version you downloaded). This will automatically run su, so make sure to accept the prompt if necessary.
Code:
sh /sdcard/firetv2_recovery_vX.zip
Reboot
Hope this helps if so press than thanks button
Hm for some reason my filesystem is R/O. When I use adbfire to try and make it r/w is fails.
fomoco460 said:
Hm for some reason my filesystem is R/O. When I use adbfire to try and make it r/w is fails.
Click to expand...
Click to collapse
Did you ran the su command after rooting? If so have you agreed to its permissioned when asked (pop up screen that will appear on the screen)?
BTW, Instructions above reflect installing zip file from sdcard., you need to push this zip file to the sdcard dir first.
fomoco460 said:
Hm for some reason my filesystem is R/O. When I use adbfire to try and make it r/w is fails.
Click to expand...
Click to collapse
Do you have root? Are you using the latest version of adbfire? Maybe this thread Is not the best place to ask, try the adbfire thread & ask the Dev himself?
Thanks for your help. I did have root but I just decided to just start fresh and install a new rom. Looks like everything's working now.