Hello people,
I just bricked my phone I think... I rooted my phone, updated to android 2.3. Using debian here, I installed adb.
I unzipped a bunch of files to the root of the sd card: https://forum.xda-developers.com/attachment.php?attachmentid=509345&d=1296886842
Then, I ran the following commands:
```
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
flash_image recovery /sdcard/recovery.img
reboot recovery
```
Then my phone rebooted, I was like "yay success" but then it just displays the LG logo for 10 seconds, and then it shows a completely black screen with a white pixel on the top left. The screen keeps turning on and off every 7 seconds or so, indicating it's rebooting something.
What can I do to fix this? All I wanted was to install a custom android 4 ROM from here: https://www.androidpure.com/install...camera-on-lg-p500-optimus-one-cyanogenmod-10/
I didnt use Rom tool or whatever it's called, cause the servers for that app are long gone.
Thank you very much
and yeah, im unable to connect using adb. It just displays the black screen
Related
Hey guys,
Sadly, I've got Vista64, which works fairly well, FYI.
Anyways, because of it I can't install the USB drivers.. But I figure I'm just using them to access the terminal, which I, on RC29, apparently already have access to...
If I copy recovery.img to the SDcard and then use the filemanager to put it in /system, would I be able to flash it from the homescreen? What commands would I use?
Just
$ su
su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cd /system
cd /system
# cat /data/local/recovery.img > recovery.img
cat /data/local/recovery.img > recovery.img
# flash_image recovery recovery.img
flash_image recovery recovery.img
#
?? Is this going to do something bad...
Thanks
**I don't have write permission to /System using Android File Manager. I'm sorry I'm a linux newb here, what cmds do I need to use to overwrite that file?
grim1234 said:
Hey guys,
Sadly, I've got Vista64, which works fairly well, FYI.
Anyways, because of it I can't install the USB drivers.. But I figure I'm just using them to access the terminal, which I, on RC29, apparently already have access to...
If I copy recovery.img to the SDcard and then use the filemanager to put it in /system, would I be able to flash it from the homescreen? What commands would I use?
Just
$ su
su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cd /system
cd /system
# cat /data/local/recovery.img > recovery.img
cat /data/local/recovery.img > recovery.img
# flash_image recovery recovery.img
flash_image recovery recovery.img
#
?? Is this going to do something bad...
Thanks
**I don't have write permission to /System using Android File Manager. I'm sorry I'm a linux newb here, what cmds do I need to use to overwrite that file?
Click to expand...
Click to collapse
I have the same problem: I am using Windows Server 2008 x64 and there is no 64 bit driver for ADB. I ended up installing a Ubuntu VM:
http://www.koushikdutta.com/2008/10/developing-and-debugging-android.html
Well, I tired txting this to someone...
cp /sdcard/recovery.img /system
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system
cat /data/local/recovery.img > recovery.img
flash_image recovery recovery.img
Then booted into recovery mode and pressed alt-L...
And it doesn't work.
I guess it's VMWare time... zzz
Check out my post over at AndroidCommunity http://androidcommunity.com/forums/f28/i-have-rc30-and-root-6867/ this will allow you to install the modified upgrade without the adb, and sdk.
i have been try to obtain root access all day long on my New G1 phone i bought sunday and i notised the rc30 makes battery life better and well i wanted to update though the moded ver. from rc28 stock please some one direct me why i can get telnet to connect though local host on my phone and run the commands
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cd /system
cd /system
# cat /data/local/recovery.img > recovery.img
cat /data/local/recovery.img > recovery.img
# flash_image recovery recovery.img
flash_image recovery recovery.img
#
but i turn off my phone and then back on then i press alt L and noting happens mabie explain it to me a bit better id apresaite it
Check out my post has everything u need to know !
http://forum.xda-developers.com/showthread.php?t=443797
I have an Atrix on AT&T. Which means there's a bootloader encryption, and the carrier prevents non-market apk installations, which I have resolved since my phone is rooted and I have changed the boot animation already.
In order to do these things, I found Ghost Commander that would let me chmod my system directories...which is fine, but I feel kind of gimped that I can't do it on terminal.
Basically, what I want to be able to do is remount /system as rw using terminal.
This method doesn't work on both terminal and emulator on my phone. I have done:
Terminal:
Code:
sudo su
cd [sdk directory]
./adb devices
./adb shell
su
mount -o remount,rw -t ext3 /dev/block/mmcblk0p12 /system
and this is where I get stuck because I just get an Invalid argument error.
Here is some info about my sytem -
Usage: mount [-r] [-w] [-o options] [-t type] device directory
/dev/block/mmcblk0p12 /system ext3 ro,noatime,nodiratime, data=ordered 0 0
Been searching for the answers for a while now and tried all kinds of syntax, and now I'm here. What am I doing wrong? Thanks
Try:
mount -o remount,rw /system
The remount option automatically looks up the info for /system so you shouldn't have to bother with the details.
Hmm, I tried that thanks, and I still got 'Usage: mount [-r] [-w] [-o options] [-t type] device directory'
Hmm, I can't think of any reason that wouldn't work but it sounds like your phone is locked down pretty tight. Do you know if others have been able to remount /system?
What version of busybox do you have? Maybe you could try updating it. There are one or two free busybox updater apps on the market, if you can use them.
Have you tried just 'adb remount'?
Does the mount command require busybox? Do you have that properly installed?
That requires adbd itself to be run in root mode (this is different from being rooted on the phone) & you could do that only on insecure boot image. mount/unmount both happen to come from the busybox package. It would be hard to contemplate that Motorola actually changed that but nothing would stop them from. You could try updating the busybox utility onboard your phone. There is nothing with your usage of the command - it would work the same way on my Nexus S
I do have Busybox in /system/xbin. Thinking that maybe the xbin directory may need to have the rewrite permissions, I changed its permissions to 777 using the chmod command in phone Terminal. I did the remount command 'mount -o remount,rw -t ext3 /dev/block/mmcblk0p12 /system' in shell on the phone, and I THOUGHT I BRICKED! Haha, but it just turned off, and I rebooted to find that my button backlights were turned off...which I fixed with the brightness file.
Anyhow, I think I'll just use the chmod command because that seems to work. NeoA, I think you are right about the adbd to run in root mode, because I've seen discussions about that before.
Thanks for the feedback guys! At least I know I wasn't having syntax errors to say the least
So did it remount it as rw? The mount command was running before, just giving errors, but if it's running that should mean the permissions were ok.
try
Code:
busybox mount -o remount,rw /system
Fr4gg0r said:
try
busybox mount -o remount,rw /system
Click to expand...
Click to collapse
"mount: can't find /system/app in /proc/mounts"
but
Code:
busybox chmod 777 /system
is good enough for me, for now
marlasinger said:
Code:
busybox chmod 777 /system
is good enough for me, for now
Click to expand...
Click to collapse
Using chmod to change permissions won't actually give you rw access to the system partition since it won't change whether it's mounted as read-only or r/w. To be able to run the chmod command, the system must already have been mounted as r/w or you would have received a "Read-only file system" error. It must have gotten mounted as read/write when the remount command caused a reboot. You can see how /system is mounted by just typing "mount" in adb shell which will list all of the mounted partitions.
Hi,
I'm getting the following output while trying to flash custom recovery:
# su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
chmod 755 /system/bin/flash_image
# flash_image recovery /sdcard/recovery-RA-thunderg-2.2.1-GNM.img
flash_image recovery /sdcard/recovery-RA-thunderg-2.2.1-GNM.img
link_image[1934]: 4368 missing essential tablesCANNOT LINK EXECUTABLE
Setup:
Android 2.2.3.
Stock GB ROM rooted.
Stock Kernel.
I haven't even flashed a single ROM yet...I am getting this same error no matter which custom recovery I try to flash. Any ideas please? :crying:
mugenishere said:
Hi,
I'm getting the following output while trying to flash custom recovery:
# su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
chmod 755 /system/bin/flash_image
# flash_image recovery /sdcard/recovery-RA-thunderg-2.2.1-GNM.img
flash_image recovery /sdcard/recovery-RA-thunderg-2.2.1-GNM.img
link_image[1934]: 4368 missing essential tablesCANNOT LINK EXECUTABLE
Setup:
Android 2.2.3.
Stock GB ROM rooted.
Stock Kernel.
I haven't even flashed a single ROM yet...I am getting this same error no matter which custom recovery I try to flash. Any ideas please? :crying:
Click to expand...
Click to collapse
What phone are you using? Are you sure that the recoveries are for your phone? Also, are you sure you're rooted?
upconvert said:
What phone are you using? Are you sure that the recoveries are for your phone? Also, are you sure you're rooted?
Click to expand...
Click to collapse
I'm using LG Optimus One P500. Setup is as follows:
ROM: Stock GB 2.2.3 (rooted)
Kernel: Stock (everything else is stock, untouched)
Recovery: thunderg 2.2.1
I'm quite sure the phone is rooted. I just shifted from SuperUser to SuperSU. Root privileges are being granted fine. But the problem is still there in recovery mode. Root checker, Titanium Backup, SuperSU, adb shell ("SU") are all working fine with no errors...
You could try the flash image gui. It's on the play store, and I think it supports the P500.
upconvert said:
You could try the flash image gui. It's on the play store, and I think it supports the P500.
Click to expand...
Click to collapse
"flash image gui" from the play store works just fine to flash a new custom recovery. Thanks a lot for your suggestion.
I was just wondering whether there is something wrong with my setup that in the adb shell - the last step is consistently failing for every recovery I try.
I don't know. Glad it worked out, though.
Sent from my LG-VM670 using xda app-developers app
I've searched all over these forums trying to figure out how to uninstall Unofficial Safestrap 3.75, but have not had any luck. I did some mods to my S3 and want to remove SS 3.75 because each time the S3 reboots it first goes to the Samsung Custom screen that shows an opened padlock and then goes to the "Safestrap Disabled Screen" where you can push "continue" (or it does so in 10 seconds on its own) or Recovery. I've tried uninstalling it by using Link2SD, but I still get the screens mentioned above. The app doesn't show in the App Manager Drawer, so I'm not sure what to do. I would appreciate any help at all with this. Thanks!
Enter adb shell from your pc:
Code:
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system
Sea23.vn said:
Enter adb shell from your pc:
Code:
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system
Click to expand...
Click to collapse
Thanks a lot for your reply. This is a very time consuming process, and I'm still having trouble.
When I'm in the command prompt screen from sdk\PlatformTools and enter the first line of code su I get an error message saying "su is not recognized as an internal or external command"
btw, I entered command adb devices to make sure S3 is connected, and based on reply, it appears to be. I have attached a jpg showing both of the above situations. If you or anyone has an idea how to solve this glitch, I'd appreciate it!
Full code:
adb devices
adb shell
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system
Thank You!!!
Sea23.vn said:
Full code:
adb devices
adb shell
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system
Click to expand...
Click to collapse
Sea23-
Thanks very much!!! This drove me nuts!!! Geeeeezzzz.... Now the S3 boots up propertly! No more Safestrap screen. Thanks again!