Hey guys,
I rooted my N1, then (only days later) somehow my microusb port got damaged, and now won't charge or connect to the computer. My guess is that HTC would honor a replacement request regardless of root because it's solely a hardware issue, unless someone thinks otherwise, but I am curious as to whether it's possible to unroot without USB anyway.
Ideas?
You could try the 'Unroot' button in Universal Androot?
Hmm, that just tells me that I'm not rooted.
Hmmm, you could try downloaind a terminal emulator and using that to remove /system/bin/su and /system/app.Superuser.apk although you'd need to us SU to gain the rights to delete them, so not sure if it would like that. Worth a go though.
Edit: Just tested it, that works fine, go for it.
Code:
su
mount -o remount,rw /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
cd ..
cd bin
rm su
exit
why don't you copy a passimg.zip on your sdcard and flash it in hboot?
adbWireless
Related
I currently have the 1080p 30fps camera mod on and I'm wanting to go back to the original, i have the camera.apk to go back on but when I try to push it, it says READ ONLY FILE SYSTEM.
I had a hunt around and found this but didn't work
adb shell sysrw
adb push (file name.apk /system/app/)
adb shell sync
adb shell sysro
then i found this
adb shell mount -o remount,rw,codepage=utf8,vfat,xattr,check=no /dev/stl5 /system
and that didn't work, Im pretty new to ADB etc and trying to get the hang of it so take it easy on me
Kickasskev said:
I currently have the 1080p 30fps camera mod on and I'm wanting to go back to the original, i have the camera.apk to go back on but when I try to push it, it says READ ONLY FILE SYSTEM.
I had a hunt around and found this but didn't work
adb shell sysrw
adb push (file name.apk /system/app/)
adb shell sync
adb shell sysro
then i found this
adb shell mount -o remount,rw,codepage=utf8,vfat,xattr,check=no /dev/stl5 /system
and that didn't work, Im pretty new to ADB etc and trying to get the hang of it so take it easy on me
Click to expand...
Click to collapse
you can use my zip in recovery
stock_Camera
LOOOOL this is the 1080p 30fps that i already have on my phone I wanna go back to stock.
I will put my STOCK camera.apk in the zip
Thanks
didn't work
Anymore idea's
Or Commands
Bump......
Sent from my LG-P990 using XDA App
i think you need to su first?
adb remount before adb shell
Hi, You can download the original LGE-Camera.apk file below...
Google or yahoo or find your way to get an app called: root manager(Paid app on market)
Not suppose to talk about 'where-to-download-paid-app' here... So i guess you need to google.
Copy the Camera.apk to SDCARD
Go to System>App>, Mount R/W, Delete the camera app.
Go back to SDCARD and cut/copy the camera.apk
Return to System>App>Paste file here.
You can see the 'Mount R/W' Button on the 'App' folder itself. So don't ask me how to mount R/W.
Cheers A reboot may be necessary.
in adb you need to enter
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Thanks for all the replys i will try them when i get home from work
Sent from my LG-P990 using XDA App
I tried to instal the LG Contact.apk this way (to replace the stock one)
Code:
C:\Program Files\Android\android-sdk\platform-
1908 KB/s (3175637 bytes in 1.625s)
pkg: /data/local/tmp/Contacts_lg.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Any idea ?
Don't install it, push it into place.
Rusty! said:
Don't install it, push it into place.
Click to expand...
Click to collapse
Yes, by you don't need to install those default apk. Just place it in system/app, and you will see it in your menu screen. If nothing happen, reboot your phone.
Hi all, I'm trying to sideload the new Google Music apk onto my CM7 Nook Color. As i reside outside the US, I don't have it available through the market. I did sign-up for the invite through a proxy network though and got the invite a few days back. Now don't ask me how, but after receiving the invite, somehow the new google music app appeared as a manual update on my Nexus One(2.3.4) and it works like an absolute charm on it. I 'adb pulled' this Music app off my Nexus One and tried to install it on my Nook Color through adb. Here's the steps I followed:
- Connected through adb wireless first.
- Tried 'adb install' first. That didn't work.
$ ./adb install MusicGoogle.apk
493 KB/s (375498 bytes in 0.742s)
pkg: /data/local/tmp/MusicGoogle.apk
Failure [INSTALL_FAILED_DEXOPT]
- Then tried transferring the apk to /system/app
$ adb push MusicGoogle.apk /data/local/tmp/
$ adb shell
# su
# mount -o rw,remount -t ext4 /dev/block/mmcblk0p5 /system
# chmod 777 /system/app
# cp /data/local/tmp/MusicGoogle.apk /system/app/
# chmod 755 /system/app
# mount -o ro,remount -t ext4 /dev/block/mmcblk0p5 /system
This didn't work either. The icon failed to show up in the app-drawer.
Where am I going wrong here? Is it becuase I took the apk from my N1?..I hardly think that should be a problem. Could someone from the US post their apk which they installed on their NC, from the Android Market?
Thanks.
Sorry if this is a dumb question, but is there any reason you don't just use Market Enabler?
MickMcGeough said:
Sorry if this is a dumb question, but is there any reason you don't just use Market Enabler?
Click to expand...
Click to collapse
I could always do that, but is there a reason why the above method shouldn't work? I've followed the above method many times to install apps on my rooted N1.
hungryTux said:
I could always do that, but is there a reason why the above method shouldn't work? I've followed the above method many times to install apps on my rooted N1.
Click to expand...
Click to collapse
I don't know if there's any reason that wouldn't work. I'm using Google Music Beta in Canada for a week or so now and I spent less time setting it up on my NC than I've spent replying in this thread
I'm not sure if the apk coming from your nexus one is being the reason the apk is not installing but sideloading is vary easy. all you have to do is place the apk on the root of your sd card and navigate from a file manager app like astro to the apk and press on it. the app manager will appear and ask if you'll like to install it, say yes. there, you're all done.
cm7 n111 6/18 OC kernel 300/600/800/1100/1200 conservative
I really just want to unroot my Captivate and I was wondering if there was a way to do so through adb or terminal. I am on stock 2.2.
okachowwa said:
I really just want to unroot my Captivate and I was wondering if there was a way to do so through adb or terminal. I am on stock 2.2.
Click to expand...
Click to collapse
Take a look at this. It's the one-click root/unroot.
I know you said you wanted terminal, and if you look at the batch files for this program, you should be able to see the commands being used to do the rooting/unrooting.
....Or you could use the program. Either way.
(One other thing - are you wanting to place your phone in a rooted state, or remove it from a rooted state? Rooting is putting it in the rooted state, unrooting is removing it from the rooted state. Not trying to be definition crazy, but knowing what you're wanting to accomplish sometimes requires different steps.)
jmtheiss said:
Take a look at this. It's the one-click root/unroot.
I know you said you wanted terminal, and if you look at the batch files for this program, you should be able to see the commands being used to do the rooting/unrooting.
....Or you could use the program. Either way.
(One other thing - are you wanting to place your phone in a rooted state, or remove it from a rooted state? Rooting is putting it in the rooted state, unrooting is removing it from the rooted state. Not trying to be definition crazy, but knowing what you're wanting to accomplish sometimes requires different steps.)
Click to expand...
Click to collapse
I'm definitely trying to unroot lol and thanks...and I didn't root with that however so should it still work the same?
EDIT: I got E:verification error thing when i used that method. As stated, I'm on 2.2.
Please you guys, I just need to know the commands, I have found some online, but I don't know if they are the same for the Captivate. Please help me. I have root to use the Terminal Emulator, so I need to confirm they are the same.
This is the one I found, is it the same for the Captivate?
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
rm /sdcard/Superuser.apk
rm system/xbin/busybox
rm /system/xbin/su
rm /sdcard/su
rm /sdcard/busybox
mount -t rfs -o remount,ro /dev/block/stl9 /system
exit (first "exit" takes you out of su)
exit (second "exit" takes you out of the terminal)
reboot
Anyone figured out how to do it? I've tried following the guides with no success (gingerbreak). Model is P970g and software is 10a. Country code is TLS.
Anyone have a Telus OB and been able to root it? How did you do it?
I've rooted a couple of them, both 10a on Telus, one of them was pretty easy using z4root. Another one wouldn't work with z4root, latest superoneclick, gingerbreak or manually using adb shell to gingerbreak, rageaggainstthecage & psneuter. I did finally get the stubborn one to root wither an older superoneclick; version 1.6.5. Attached it below as it doesn't seem available in CLShortFuse's thread anymore.
Goodluck
alexredford said:
I've rooted a couple of them, both 10a on Telus, one of them was pretty easy using z4root. Another one wouldn't work with z4root, latest superoneclick, gingerbreak or manually using adb shell to gingerbreak, rageaggainstthecage & psneuter. I did finally get the stubborn one to root wither an older superoneclick; version 1.6.5. Attached it below as it doesn't seem available in CLShortFuse's thread anymore.
Goodluck
Click to expand...
Click to collapse
I tried both z4 and the superoneclick you suggested to no avail.
Do you think it's safe to try flashing another vulnerable rom? 10b or 10c? I'm worried the basebands may be different and the phone will have no voice/data connection.
Running out of ideas.
Attempted to root another one, same model, same version and none of the previous methods worked, was able to root this one as well using a combination of SOC 2.1.1 and the attached ADB Shell.
1. Download and run SuperOneClick 2.1.1, choose psneuter and click Shell Root
2. It should get stuck on step #4, run task manager, end superoneclick and terminate any adb.exe processes. (You should have Shell Root now)
3. Extract ADB.zip and open a command prompt to where you extracted it.
4. Enter the following commands
Code:
adb push su /tmp/
adb push Superuser.apk /tmp/
adb shell
mount -o rw,remount -t ext3 /dev/block/mmcblk0p8 /system
cat /tmp/su > /system/bin/su
cat /tmp/superuser.apk > /system/app/Superuser.apk
chown root.root /system/bin/su
chmod 06755 /system/bin/su
chown root.root /system/app/Superuser.apk
chmod 0644 /system/app/Superuser.apk
reboot
The permissions on /system/bin/su didn't stick the first time for me, and the phone rebooted a couple times, but eventually it all went through. To verify permissions on su, type "adb shell", then "ls -l /system/bin/su". The permission should read -rwsr-sr-x, if it doesn't repeat the shell root process and type
Code:
adb shell
mount -o rw,remount -t ext3 /dev/block/mmcblk0p8 /system
chmod 06755 /system/bin/su
ls -l /system/bin/su
Ok, i've figured out what the problem is. As soon as the adb process from SOC is shut down, the phone soft reboots and I lose temporary root. I've tried the psneuter exploit in the same adb command shell, but it hangs just like SOC. I've tried to be "quick" and get the commands in before the reboot, but it isn't possible.
Suggestions on how I may bypass that? Otherwise i'll wait for the official 2.3 update in september and try again then.
One of the phones I tried it on, did the same thing, ended the adb process and phone would reboot, pushed a file, phone would reboot, set permissions, phone would reboot. Occasionally the phone would appear to hang, buttons flash at the bottom for awhile, phone becomes unresponsive. Just wait a minute or 2 and it should return to normal. I also tried creating a script to do all of the above before the device had time to reboot and it didn't help.
Persistence was the key.
Did you try that ? If following the instructions don't work for you, I let you know how it works for me.
EDIT : Sorry, forget link's thread : http://forum.xda-developers.com/showthread.php?p=14458927
Sent from my LG-P970 using xda premium
Hey i am having the same problem and am fearing bricking my phone from making a mistake. is there an easier method than those above mentioned?
Android 2.2.2
software: v10a
Sobralobo said:
Did you try that ? If following the instructions don't work for you, I let you know how it works for me.
EDIT : Sorry, forget link's thread : http://forum.xda-developers.com/showthread.php?p=14458927
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
This method worked when rooting my wife's P970g.
KDZ file
hey does anyone have the Telus firmware KDZ file? i will need it to restore my phone back to original state to cash in on a waranty (ended up bricking it, had to install a german 1&1 firmware to get it back)
s0dhi said:
This method worked when rooting my wife's P970g.
Click to expand...
Click to collapse
...which ROM did you use, the v10a EEU from the thread?
I'm worried cause on Telus 970g as well.
The_non_rootable said:
hey does anyone have the Telus firmware KDZ file? i will need it to restore my phone back to original state to cash in on a waranty (ended up bricking it, had to install a german 1&1 firmware to get it back)
Click to expand...
Click to collapse
http://lg-phone-firmware.com/index.php?id_mod=1
Hello guys, please help me out with this problem! I've been working on all day but my phone is still bad...
When I rooted my device BusyBox was supposedly installed by the toolkit I used to root (mskip's).
Then I installed BusyBox installer market app (Stericson's) and it said "BusyBox location could not be found". I thought it wasn't installed so I used the "smart install" with the default values, so it was installed to /system/bin and all the applets were listed as symlinked to /system/bin/busybox
After a while I realized that it was installed both in /system/xbin (by the root toolkit) and in /system/bin (by busybox installer). I used the uninstall option from the busybox installer app to remove it from /system/bin again and leave just one installation to avoid conflicts. This was not a good idea it seems. After uninstalling and rebooting, the phone started to work incorrectly, wifi doesn't work.. and most importantly, USB connection is dead with Android fully booted. the battery charges but the PC doesn't detect it. (It works on Recovery mode though).
I have an idea of what may be wrong. I think the "BusyBox installer" changed all the symlinks to system/bin/busybox, so when it was uninstalled, the phone was left without any of the applets of busybox even though the file /system/xbin/busybox is still present.
Or maybe I'm not really rooted anymore? However, the su binary is still present in /system/xbin/su but I still can't get to work commands like "mount".
How can I fix this problem? I will greatly appreciate any suggestions.
I think it might be fixed by installing busybox to /system/bin or even just copying the /system/xbin/busybox file to /system/xbin/busybox but because the phone is not working correctly I haven't been able to do that...
Here's the information I've gathered so far for you guys to PLEASE help me out with this:
SuperSU is installed and seems to works fine.
"BusyBox Free" installer app doesn't work. If I open it, it shows only black with the three buttons in the bottom but they can't be "clicked. It has been granted root permissions.
"ES File Explorer" gets root permissions but is unable to mount /system as writable (to copy the file).
In a terminal emulator application (Jack Palevich's), this is what I get:
Code:
$ which busybox
/system/xbin/busybox
$ ls
ls: not found
$ busybox ls
(works, outputs the directory content correctly)
$ mount -o remount,rw /system
mount: not found
$ busybox mount -o remount,rw /system
mount: permission denied (are you root?)
$ su
(the terminal emulator app has root permission, but when issuing "su" command, the cursor stays inactive for several minutes and when it finally responds, the following operations are still not succesful. The "su" doesn't seem to work.
$ busybox mount -o remount,rw /system
mount: permission denied (are you root?)
$ /system/bin/busybox --install -s /system/bin
busybox: /system/bin/zcat: Read-only file system
busybox: /system/bin/mountpoint: Read-only file system
busybox: /system/bin/nohup: Read-only file system
My plan is to make the USB work so I can use the toolkit again to restore a stock firmware and clean this mess. Oh, I have stock recovery and stock boot image if that's of any help to know it.
How can I issue the commands I need? or fix this problem?
I have basic linux experience so if you need the output of any command please let me know.
Any help is appreciated. Thank you!
... i think that flashing cwm recovery(.tar.md5) with odin and flashing a root+busybox.zip with cwm recovery should be the fastes way to fix this .... only thing is that it erease your "costum binary count" but with the "Triangel Away" app you can reset that counter ...
Thank you for the hint, enox. I'm will try to install the custom recovery now.
Thanks again enox for pointing me in the right direction. The phone is working again. I'm sharing what I did in case it helps someone in the future:
1) Installed the custom recovery 'twrp', provided by the toolkit (program_folder/recovery/recovery-twrp-2.4.3.0-GTI8190.tar) using odin with the phone in download mode.
2) Flashed this busybox uninstaller using twrp recovery. The phone wasn't working fine yet, so I continued to the following step.
3) Flashed a root+busybox.zip provided by the toolkit (program_folder/root/SuperSU-1.25-Busybox-RenameRecoveryRestore.zip) using twrp recovery.
At this point, the phone was working fine but to be sure that all symlinks were correct, I ran an additional cleaning script which you can find at the end of this post, along with my comments talking to myself while I was troubleshooting the problem.
I'll go to sleep now. Thank you.
Got a PM and I thought it would be better if I reply to it in the forum so others can benefit as well:
andr0id_n00b said:
hey i saw your problem here http://forum.xda-developers.com/showthread.php?t=2233942 and iam glad u solved your problem
can you please tell me what toolkit do you use ??
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
mskip's toolkit for Samsung Galaxy S3 Mini:
http://forum.xda-developers.com/showthread.php?t=2185700
Big thanks to him too, for providing that noob friendly yet full-featured toolkit
same with xperia mti27i
ive exactlly made the same but with my xperia mt27i android4.0 ics i dont i know what to do i dont have exp. with android so please help