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
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
Ok, so here is what puzzles me:
I have a MT3G, SuperOneClick rooted, with RA 1.7.0, busybox 1.18.4, all apps requiring superuser permissions are working flawlessly (Titanium, SetCPU, Root Explorer, Droid Wall, etc). Fix_permissions works with RA (other/fix uid mismatches) and ROM Manager, but when I open the emulator and type $su #fix_permissions, it gives me
bash: fix_permissions: command not found
In adb shell fix_permissions, permission is denied. All useful ideas how to solve this are much appreciated, thanks...
Anyone?
Sent through XDA App
Ok, I don't want to open a new topic, but really need some advice here! I just used Root Check in advanced mode, before it ran it asked for and received superuser permissions, then the detailed results were:
Congratulations! You have root access!
Alternate su bin location:
/sbin/su: Permission denied
Root user id:
uid=0(root)
Root group id:
gid=0(root)
Click to expand...
Click to collapse
Seriously, guys, please help, I dont have a clue whether I have a permanent root or not. I forgot to mention I'm using the T-Mobile OTA Froyo 2.2.1 FRG83D. I've rooted this same ROM once, 5-6 months ago, when it was pushed out, I had no problems, fix_permissions were working. Then I nandroid backed it up, so I can restore it if I don't like the other ROMs I used later (which were Ginger Yoshi RC7 -a great ROM, but the launcher was constantly restarting, and then back to Super D - most stable one, but lots of the good apps are not for 1.6 anymore). However, when I tried to restore Froyo, it didnt work, so I had to start over, using the following steps to get the OTA and root it. Please, let me know if I missed something or did it wrong:
1. I flashed sappimg.nbh with hboot to get to unrooted Cupcake
2. Flashed DRC92 and DMD64 Donut updates with stock recovery <3e>
3. Got the OTA Froyo from T-Mobile (*#*#checkin*#*#)
4. Used SuperOneClick to root, then restarted the phone
5. Using Droid Explorer, I installed a terminal emulator, then I uninstalled Superuser (have read in several threads people saying they had problems with it when it comes with SuperOneClick), using
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# rm /system/app/Superuser.apk
# pm uninstall com.noshufou.android.su
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
# exit
$ exit
and reinstalled it from the market.
6. Installed the latest busybox with Busybox Installer.
7. Pasted flash_image and recovery.img (Amon RA 1.7.0) to the sdcard, then installed recovery:
$ su
# mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
# rm /system/etc/install-recovery.sh
# cd sdcard
# mount -o remount,exec /dev/block//vold/179:1 /sdcard
# ./flash_image recovery /sdcard/recovery.img
# exit
$ exit
8. And finally I started removing the unnecessary system apps (Amazon, MyFaves, etc) with the emulator, using the same method I did to remove Superuser in step 5
Click to expand...
Click to collapse
Now, as I mentioned before, I cannot run fix_permissions through the emulator, but it runs through ROM Manager and RA (fix package uid mismatches).
Why is that? Is it the ROM, which causes the problem?
I'm clueless, please help!
Hi, I'm enter on my transformer by :
adb shell
and I want do that :
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
cd /data/app
rm com.mhuang.overclock*
cd /data/data
rm com.mhuang.overclock*
cd /data/dalvik-cache
rm *mhuang.overclock*
exit
But when I execute su, it don't work :
/data/app # su
Segmentation fault
Can you help me ?
Thanks
Just reflash your rom without wiping data unless your trying to flash a rom that is overclocked by default
If it's in your data partition, then it's not a system file. Try this:
adb uninstall com.mhuang.overclocking (use the full package name)
EDIT: saw your other thread about borking your TF. follow badfrog's trick and flash a rom with a non-overclocking kernel, which will limit setcpu.
If adb uninstall don't work, which rom with overclock by default propose me ? Révolution HD ?
Sorry for my english, i'm french ?
Prime has a stock kernel as default
http://forum.xda-developers.com/showthread.php?t=1251044
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