Related
I have been trying for some time now,pushing files via adb commands onto nexus one but keep getting cannot copy file read only file error.I am fully rooted and unlocked.I have also reinstalled the android sdk but always get the same error when I push the image file.has anyone experienced this with their phone. I have a feeling its something to do with the SD card but can't be sure.any help would be appreciated. Thanks.
I know you must be thinking "Jedi"how can he can he call himself an androidjedi when he can't sort this simple problem (to some of you),but I must say even a Jedi needs to learn!
try adb remount before your command
Dunno if this will help but have tried changing the system to rw then try to push
Tried that no cigar
are you trying to push it into your sdcard or the phone system??
and remember the whole folder name has to be in the push so it woul have to look like
C:\Users\Android>ad push "C:\Users\Android\Downloads\Android\Nexus 1\Phone.apk" /sdcard/files
has to have full path of where you are pushing it from/too.. i have mine sdk setup to use adb in any directory as well why you dont see it in the sdk directory
@ilostchild
Thanks i will try that later today and let you know
As for pushing the file - i am trying to push it to the sd card - but i am not really sure as i am following instructions in the [HOW-TO] Revert HBOOT 0.35.0017 to 0.33.0012 thread in the forum
as i need to downgrade my Hboot from #17 to 12
are the commands different for pushing a file to the phone?
the more i think about i think i need to flash the file to the phone - but i will try your adb command format of specifying the location of the file in the comp
androidjedi said:
the more i think about i think i need to flash the file to the phone - but i will try your adb command format of specifying the location of the file in the comp
Click to expand...
Click to collapse
Ooo you want to push to sdcard.. ok then yea, you would type it like this
C:\android-sdk-windows\tools> adb push C:\Users\Android\Downloads\Android\signed-passion-FRF50-from-
ERE27.1e519a24.zip /sdcard*
if you dont have the option to use adb in any directory, then you have to be in the android sdk directory and in tools
cd android-sd-windows
cd tools
adb push(drag the file you want to push in the command prompt window) /sdcard*
sorry i know its detailed and im sure you know all these things.. but it kinda gets the questions out of the way for future problems to come
ilostchild said:
Ooo you want to push to sdcard.. ok then yea, you would type it like this
C:\android-sdk-windows\tools> adb push C:\Users\Android\Downloads\Android\signed-passion-FRF50-from-
ERE27.1e519a24.zip /sdcard*
if you dont have the option to use adb in any directory, then you have to be in the android sdk directory and in tools
cd android-sd-windows
cd tools
adb push(drag the file you want to push in the command prompt window) /sdcard*
sorry i know its detailed and im sure you know all these things.. but it kinda gets the questions out of the way for future problems to come
Click to expand...
Click to collapse
thanks for spending time on this-i am new to the android world so any help is welcome-however detailed or not
thanks will try that
ilostchild said:
Dunno if this will help but have tried changing the system to rw then try to push
Click to expand...
Click to collapse
how do i change the system to read write as i am still getting cannot copy file read only file error
androidjedi said:
how do i change the system to read write as i am still getting cannot copy file read only file error
Click to expand...
Click to collapse
do adb shell
su
Mount -o remount,rw /dev/block/mtdblock3 /system
then exit and exit
then do push
ilostchild said:
do adb shell
su
Mount -o remount,rw /dev/block/mtdblock3 /system
then exit and exit
then do push
Click to expand...
Click to collapse
tried that did the push and all i got was 950 KB/s <0 bytes in 76044.000s>
looks like its not pushing the file not sure what to do now
androidjedi said:
tried that did the push and all i got was 950 KB/s <0 bytes in 76044.000s>
looks like its not pushing the file not sure what to do now
Click to expand...
Click to collapse
Umm if you got that mesage you may have pushed it in right..
ilostchild said:
Umm if you got that mesage you may have pushed it in right..
Click to expand...
Click to collapse
does not seem to have worked for some reason as after flashing it should reboot in htc mode and then i would be able to flash a rom with the hboot12
May i ask what are you trying to push into your phone/sdcard?
ilostchild said:
May i ask what are you trying to push into your phone/sdcard?
Click to expand...
Click to collapse
I am trying to follow the instructions on the thread which can be found in the the following link forum.xda-developers.com/showthread.php?t=726258
basically trying to flash two image files that enable downgrading the Hboot from 0.35.0017 to 0.33.0012
androidjedi said:
I am trying to follow the instructions on the thread which can be found in the the following link forum.xda-developers.com/showthread.php?t=726258
basically trying to flash two image files that enable downgrading the Hboot from 0.35.0017 to 0.33.0012
Click to expand...
Click to collapse
managed to do it after just following the instructions and inoring what i thought was an error i managed to downgrade my happy days have a good weekend
will no doubt ask you for help another time cheers and thanks a lot
Welcome and congratz
Sent from my Nexus One using XDA App
I was trying to update the status bar on my i9000m/JH2. I must have done something wrong when zipping, signing, or zipaligning the file. I was able to apply the update.zip without any errors through recovery mode. But when i rebooted, I was met with continuous force close windows. I had my original backed up and wanted to place that into /sdcard and then simply run it from recovery mode to 'undo' the damage i did.
/sdcard appears empty when I run abd to my phone while in recovery mode. If i attempt to push a file to it, i get 'permission denied'. Do i need to manually mount /sdcard in recovery mode to be able to overwrite /sdcard/update.zip (can this be done)?
*snip*
On sec...
nudge nudge
Reflash is only option now. Recommend in future you leave recovery update.zip on SD card and use root explorer to copy over new f/w. That way if no good you can recover easier.
Sent from my GT-I9000M using XDA App
If u get adb running why not just push it then ?
adb shell stop
adb push framework-res.apk /system/framework/framework-res.apk
adb shell start
lgkahn said:
Reflash is only option now. Recommend in future you leave recovery update.zip on SD card and use root explorer to copy over new f/w. That way if no good you can recover easier.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
I ended up reflashing shortly after it happened. I'll look into root explorers.
Daneshm90 said:
If u get adb running why not just push it then ?
adb shell stop
adb push framework-res.apk /system/framework/framework-res.apk
adb shell start
Click to expand...
Click to collapse
I was able to get adb running, but I didn't see /system when listing. Did i need to mount it?
onaquest said:
I was able to get adb running, but I didn't see /system when listing. Do i need to mount it?
Click to expand...
Click to collapse
/system should still be already mounted. Otherwise u wudnt see a homescreen.
Just try the commands.
Daneshm90 said:
/system should still be already mounted. Otherwise u wudnt see a homescreen.
Just try the commands.
Click to expand...
Click to collapse
One other detail is that the phone wasn't rooted At the time I thought that might have been preventing me from seein /system.
This is all educational for me, I was wondering what other options I had before reflashing. Thanks for all the input guys. I ended reflashing with Odin a few days ago.
The Superboot root method boot.img for 2.3.2 is now live thanks to Paul over at Android @ MoDaCo.
"Superboot is a boot.img that when flashed, will root your device the first time you boot (installing su and the superuser APK). No need to flash the system partition, no need to use ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just flash the boot image using the instructions below and you're done!"
Using Superboot
- Download the zip file and extract
- Connect Nexus S via USB cable (with debugging enabled - Settings->Applications->Development->Check "USB Debuggging")
- Boot into bootloader mode - (Turn on while holding 'volume up')
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
*Again, All credit goes to Paul at Android @ MoDaCo*
Cool I'm rooted already but nice to see easier ways of doing it for the noobs. Appreciate the work.
Sent from my Nexus S using Tapatalk
Updated today to 2.3.2 and lost root. Used this and I'm back up and running ! Thank you!!!
Sent from my Nexus S using XDA App
2.3.2
can u do this being rooted or do you have to revert to stock
For some reason this didn't work for me. I tried it twice but each time the phone rebooted I still didn't have root. Do I have to unlock fastboot?
qreffie said:
For some reason this didn't work for me. I tried it twice but each time the phone rebooted I still didn't have root. Do I have to unlock fastboot?
Click to expand...
Click to collapse
i think you would
fastboot
fastboot satus failinvalid command
finally regain root, thank you!!!
qreffie said:
For some reason this didn't work for me. I tried it twice but each time the phone rebooted I still didn't have root. Do I have to unlock fastboot?
Click to expand...
Click to collapse
Yes. These instructions assume you have already unlocked your bootloader.
Sent from my Nexus S using Tapatalk
maybe a noob question: if I just root my Nexus S using this method (no custom rom installation), will I still be able to get OTA updates from google?
dakiz71 said:
maybe a noob question: if I just root my Nexus S using this method (no custom rom installation), will I still be able to get OTA updates from google?
Click to expand...
Click to collapse
Yes. You may have to re-root after updates but your phone will prompt you when OTA updates are available just like normal.
Sent from my Nexus S using Tapatalk
annndrewww said:
Yes. These instructions assume you have already unlocked your bootloader.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Figures. The answer was staring me in the face the whole time. I think I even remember unlocking it last time I rooted this way. I guess I should just leave it permanently unlocked then so it doesn't keep wiping every time I go to root after an update.
Hi,
I can't get it to work on my mac.
When I put the renamed as "superboot" folder on the desktop, I open the terminal and type in:
~/Desktop/superboot/chmod +x install-superboot-mac.sh./install-superboot-mac.sh
it doesn't find that path.
Could somebody help me as a noob?
Thank you!
Am I the only one that did not lose root after the latest 2.3.2 update?
DarkAgent said:
Am I the only one that did not lose root after the latest 2.3.2 update?
Click to expand...
Click to collapse
I used the superboot method for 2.3.1 and also did not lose root in with the 2.3.2 update.
Sent from my Nexus S using Tapatalk
You shouldn't.
P
Windows 7
For me install-superboot-windows is waiting for device long without success :\
No matter ... i had to force my pc recognize Nexus once more
Thank you. This seems simple. I'm stuck with my XP recognizing my Nexus S USB Driver after installing SDK and Google USB Driver even after trying to "update" driver under Device Manager and redirect the directory to Google USB Driver? I'm very confused.
philbs17 said:
Hi,
I can't get it to work on my mac.
When I put the renamed as "superboot" folder on the desktop, I open the terminal and type in:
~/Desktop/superboot/chmod +x install-superboot-mac.sh./install-superboot-mac.sh
it doesn't find that path.
Could somebody help me as a noob?
Thank you!
Click to expand...
Click to collapse
Ok buddy heres what you need to do, on the MAC, this is how i do it.:
DL the .zip in the OP.
Extract it on you're desktop
Rename the Extracted file to Nexus (thats what I name it)
youre device needs to have the bootlader Unlocked.
Open Terminal and type
cd desktop
cd nexus
chmod +x install-superboot-mac.sh (press enter)
./install-superboot-mac.sh (press enter)
then you're done. hope this helps.
Let me know.
Simply amazing! Thanks for the breakdown.
Hi, all, after test for a many times, I finally made the boot.img of HKTW 2.3.4 with
Code:
adb remount
command support. So excited ha?
I think most of you know that the advantage of this command support.
You can push any files to system partition with adb remount first.
The result:
Code:
$adb devices
List of devices attached
TA207034Z2 device
$ adb remount
remount succeeded
That's it, click me:
PLEASE download from the attachment, I'm really sorry that my site was down.
Original Post @: http://ligux.com/t-71-1-1.html
HOW-TO:
1. You should have an unlocked atrix 4g and flash HKTW 2.3.4.
2. You should have CWM recovery, search forum to flash one by Tenfar.
3. Goto fastboot to flash this img. This forum has the way to flash the img
No one interested in this?So disappointed
Actually; I would be really interested; it's just GREAT you can push files to /system/ through adb and makes things easier. Sadly, I'm still on 1.8.3. since I can't stand using HKTW rom on my atrix (I need the phone at my work and can't rely on a debug build)... Do you think I can use this on AT&T stock 1.8.3.??? (after bootloader unlock, obviously)
Adb remount is supported on 2.3.4 boot already.
Adb root
Adb remount
Sent from my MB860 using Tapatalk
_Dennis_ said:
Adb remount is supported on 2.3.4 boot already.
Adb root
Adb remount
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
There is "adb root" command exist. I didn't know that before. My experience is outdated. I'm sorry. But if flash this boot.img, it's not necessary to run "adb root" command first
fernandodistinto said:
Actually; I would be really interested; it's just GREAT you can push files to /system/ through adb and makes things easier. Sadly, I'm still on 1.8.3. since I can't stand using HKTW rom on my atrix (I need the phone at my work and can't rely on a debug build)... Do you think I can use this on AT&T stock 1.8.3.??? (after bootloader unlock, obviously)
Click to expand...
Click to collapse
I don't think this will work on 1.8.3. Because this is based on android 2.3.4. BTW, after I test for about some days, I think this build is stable and the battery go better than 2.2.2. I did run a livewallpaper on my device and leave there for a ninght, the battery was still 100%
flzyup said:
I don't think this will work on 1.8.3. Because this is based on android 2.3.4. BTW, after I test for about some days, I think this build is stable and the battery go better than 2.2.2. I did run a livewallpaper on my device and leave there for a ninght, the battery was still 100%
Click to expand...
Click to collapse
did u reset your battery stats when flashing 2.3.4
firefox3 said:
did u reset your battery stats when flashing 2.3.4
Click to expand...
Click to collapse
No, I didn't do that
link is down
joeryu said:
link is down
Click to expand...
Click to collapse
Sorry, my host was down for some reason, I'm trying to fix it ASAP
joeryu said:
link is down
Click to expand...
Click to collapse
I uploaded the zip file to the attachment, please check.
I'm rooted and am trying to mount the system to remove bloatware apps... However everytime Titanium Backup removes it and I reboot it's still there...
Anyone have any ideas?
System is protected: you can't modify it while the phone is booted. You'll have to make a zip or whatever to delete it in recovery.
You have to be kidding me...
I've spent all day long trying to root this bastard phone and that didn't work then I managed it and now I can't disable, remove any apps ?
So much for HTC being dev friendly
fkofilee said:
You have to be kidding me...
I've spent all day long trying to root this bastard phone and that didn't work then I managed it and now I can't disable, remove any apps ?
So much for HTC being dev friendly
Click to expand...
Click to collapse
It seriously took you all day to root? What went wrong?
Did you try just freezing the app instead?
Brand new trick from HTC?Didn't have it in hox+
Sent from my Nexus 4 using Tapatalk 2
afilopou said:
Brand new trick from HTC?Didn't have it in hox+
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
So you can no longer go into ES explorer, mount root/system go to system > apps and delete whatever you want ?
Sent from my HTC Incredible S using Tapatalk 2
The recovery flashed but wouldnt boot , managed to get round it when i discovered POB with his superboot Thank god for the desire C
Then i realised that i couldnt flash anything because I manged to install 6.0.2.8 as a boot img, and 6.0.3.0 as a proper recovery.
Then i didnt have any files on the device to flash boohoo so i managed to get ADB sideload working through the AIO One Toolkit... And managed to flash AHRD finally getting a working device,
As you see Im a seasoned vet at these things but the HTC One has been the first device that has stumped me....
----------------------
The apps issue is not unkwown for HTC however they havent done this for a while.... Back with the G2 they did exactly the same thing and yes ive frozen them but there should be away to remove system apps for us through root.... But i cant remember how, Throwing it into ADB Shell and requesting SU along with a Remount works fine but still would like to remove the apps.
Im also looking for someone with a locked phone... (Sim Locked) i have a theory and it worked on the Desire C Anyone wanna help?
fkofilee said:
I'm rooted and am trying to mount the system to remove bloatware apps... However everytime Titanium Backup removes it and I reboot it's still there...
Anyone have any ideas?
Click to expand...
Click to collapse
Delete the apps with titanium and power off the phone. Don't do a restart.
Already tried that ^_^
You need to flash a custom kernel with a modified ramdisk to disable system protection Without doing that you're like deleting an app on windows with deepfreeze on it
Is that the only solution?
There are so many bloated useless and intrusive (cr)apps on this phone it's unbelievable.
Other solution is boot in recovery and delete it there. Either thru adb while in recovery mode, flashable zip or through file manager(if you're using TWRP). Other than that nope
Hmmm I'm thinking adb through recovery here but how do I got about doing this?
fkofilee said:
Hmmm I'm thinking adb through recovery here but how do I got about doing this?
Click to expand...
Click to collapse
the joys of a s-on devices
read up on adb commands...
or use the zip I attached and edit line 18 in this format with the apps you want to get rid of, use a file explorer to get the proper names.
make a backup first in case you mess up something
Code:
delete("/system/app/xxxxx.apk", "/system/app/xxxx.odex", "/data/app/xxxxx.apk");
The best way to remove apps in recovery is through adb:
Code:
adb shell
sysrw
rm /system/app/abc.apk
the simple way is ROM CLEANER, but isn't available yet for the One.
cheers
fkofilee said:
Hmmm I'm thinking adb through recovery here but how do I got about doing this?
Click to expand...
Click to collapse
type the following commands.
Code:
adb shell
su
cd /system/app/
ls
rm <insert the name of the apk you want to delete here which can be found in the list shown by the ls command>
Riyal said:
type the following commands.
Code:
adb shell
su
cd /system/app/
ls
rm <insert the name of the apk you want to delete here which can be found in the list shown by the ls command>
Click to expand...
Click to collapse
I dont have a One, and dont plan on having one (ever, thanks to this thread! I think I'll stick to Sony, they have instructions to unlocking bootloader on their official website)
BUT, if the system is locked, it should be locked trough ADB too, so I guess what I'd try is install busybox, custom recovery, go into recovery, connected it to the PC (or a mac, but since we're on no-apple forum, I'll assume PC), mounting system there and doing your thing.
You can install busybox and custom recovery right?
Edit: never mind, I should really learn to read. Sometimes I think I'm dyslexic a little, just for words, not letters.
I did not see the 'recovery' part mentioned.
Anywho, mounting system is what you forgot, so at least I said something helpful
ogdobber said:
the joys of a s-on devices
read up on adb commands...
or use the zip I attached and edit line 18 in this format with the apps you want to get rid of, use a file explorer to get the proper names.
make a backup first in case you mess up something
Code:
delete("/system/app/xxxxx.apk", "/system/app/xxxx.odex", "/data/app/xxxxx.apk");
Click to expand...
Click to collapse
MacHackz said:
The best way to remove apps in recovery is through adb:
Code:
adb shell
sysrw
rm /system/app/abc.apk
Click to expand...
Click to collapse
limx said:
the simple way is ROM CLEANER, but isn't available yet for the One.
cheers
Click to expand...
Click to collapse
Riyal said:
type the following commands.
Code:
adb shell
su
cd /system/app/
ls
rm <insert the name of the apk you want to delete here which can be found in the list shown by the ls command>
Click to expand...
Click to collapse
issak42 said:
I dont have a One, and dont plan on having one (ever, thanks to this thread! I think I'll stick to Sony, they have instructions to unlocking bootloader on their official website)
BUT, if the system is locked, it should be locked trough ADB too, so I guess what I'd try is install busybox, custom recovery, go into recovery, connected it to the PC (or a mac, but since we're on no-apple forum, I'll assume PC), mounting system there and doing your thing.
You can install busybox and custom recovery right?
Edit: never mind, I should really learn to read. Sometimes I think I'm dyslexic a little, just for words, not letters.
I did not see the 'recovery' part mentioned.
Anywho, mounting system is what you forgot, so at least I said something helpful
Click to expand...
Click to collapse
All Wonderful Ideas folks, however i had a go at this last night, it was a fricking nightmare even mounting ADB through recovery