I was messing around with the ONE-click-lag-fix thingy on this thread
http://forum.xda-developers.com/showthread.php?p=8353541#post8353541
someone posted a "fix"
""you can fix the jpk issue by doing this:
after the failure, reboot the phone.
then with root explorer delete the file linux.ex2 in folder /data/ext2 this will give you back the space
open terminal emulator on phone and type:
su
busybox mount -o remount,rw /system
press home button and reapply the lagfix.
wait...
profit!"
So I went into my phone in /data and found linux.ex2 (although it wasn't in /ext2 it was just in /data) and I deleted it
and used the terminal commands etc.
I reset my phone and it books into the logo then turns black and turns off
I don't have the 3 button recovery mode enabled... I have ADB and stuff though
WHAT do I do ?
Please oh please tell me I didn't brick my phone
Please tell me how to fix this and I will give you $50 or $100 paypal right away
If it is bricked, what do I do to go about getting it replaced ?
Try: adb reboot recovery
And try a factory reset
Otherwise, you can boot into download mode by: adb reboot download and flash via Odin.
kalpik said:
Try: adb reboot recovery
And try a factory reset
Otherwise, you can boot into download mode by: adb reboot download and flash via Odin.
Click to expand...
Click to collapse
Where do I get ADB again (im at work) is there a tutorial ?
btw if this works Ill need your paypal info
You can use mke2fs to re-create linux.ex2
Ex. mke2fs /data/linux.ex2
This could get you booted up again. Then you could uninstall/reinstall the lagfix.
frankencat said:
You can use mke2fs to re-create linux.ex2
Ex. mke2fs /data/linux.ex2
This could get you booted up again. Then you could uninstall/reinstall the lagfix.
Click to expand...
Click to collapse
What do you mean? can you please explain this further?
what's mke2fs ?
Funkadelick said:
Where do I get ADB again (im at work) is there a tutorial ?
btw if this works Ill need your paypal info
Click to expand...
Click to collapse
ADB tutorial: http://forum.xda-developers.com/showpost.php?p=7239659&postcount=3
WAIT!!!!!!!: Before you do anything else!!! Look for /sdcard/linux.ex2 and see if it exists. This should be a backup that can be restored. Copy this back to data and you should be good to go. Might take a while to copy but it should work.
frankencat said:
WAIT!!!!!!!: Before you do anything else!!! Look for /sdcard/linux.ex2 and see if it exists. This should be a backup that can be restored. Copy this back to data and you should be good to go. Might take a while to copy but it should work.
Click to expand...
Click to collapse
I'm fairly new -- this is the problem
What do you mean "look" for it ? I can't even open up my phone -- it goes black on the boot screen (i shouldn't have deleted linux.ex2)
So I would assume this would be done through ADB ? I'm downloading it now
frankencat said:
WAIT!!!!!!!: Before you do anything else!!! Look for /sdcard/linux.ex2 and see if it exists. This should be a backup that can be restored. Copy this back to data and you should be good to go. Might take a while to copy but it should work.
Click to expand...
Click to collapse
I would need to know the commands to type to "restore" this file basically once I get ADB running
and if it works, please PM me your paypal info
I downloaded the android development SDK -- but when I ran it i got this: "Failed to fetch URL http://dl-ssl.google.com/android/repository/repository.xml, reason: dl-ssl.google.com"
Is this b/c I'm at work ? (firewall)
do I need to connect in order to use ADB ?
You said you have ADB so do this...hook up your phone and fire up a command window on you pc.
type in "adb shell"
this should get you into adb shell (duh).
next type "su"
Now enter the following one at a time on order. The last line will reboot your phone.
/data/lagfixtemp/busybox rm -rf /data/data;
/data/lagfixtemp/busybox rm -rf /data/system;
/data/lagfixtemp/busybox rm -rf /data/dalvik-cache;
/data/lagfixtemp/busybox rm -rf /data/app;
/data/lagfixtemp/busybox rm -rf /data/app-private;
/data/lagfixtemp/busybox mv /data/bak/data /data/;
/data/lagfixtemp/busybox mv /data/bak/system /data/;
/data/lagfixtemp/busybox mv /data/bak/dalvik-cache /data/;
/data/lagfixtemp/busybox mv /data/bak/app/app-private /data/;
/data/lagfixtemp/busybox mv /data/bak/app /data/;
/data/lagfixtemp/busybox mv /system/bin/playlogosnow /system/bin/playlogos1;
reboot
Funkadelick said:
I downloaded the android development SDK -- but when I ran it i got this: "Failed to fetch URL http://dl-ssl.google.com/android/repository/repository.xml, reason: dl-ssl.google.com"
Is this b/c I'm at work ? (firewall)
do I need to connect in order to use ADB ?
Click to expand...
Click to collapse
You don't need to run anything. Just download it and unzip the files to a directory on your computer like C:\android-sdk-windows
Then add the tools directory to you PATH setting
C:\android-sdk-windows\tools
Let me know if you don;t know how to do that and I will walk you through it.
frankencat said:
You said you have ADB so do this...hook up your phone and fire up a command window on you pc.
type in "adb shell"
this should get you into adb shell (duh).
next type "su"
Now enter the following one at a time on order. The last line will reboot your phone.
/data/lagfixtemp/busybox rm -rf /data/data;
/data/lagfixtemp/busybox rm -rf /data/system;
/data/lagfixtemp/busybox rm -rf /data/dalvik-cache;
/data/lagfixtemp/busybox rm -rf /data/app;
/data/lagfixtemp/busybox rm -rf /data/app-private;
/data/lagfixtemp/busybox mv /data/bak/data /data/;
/data/lagfixtemp/busybox mv /data/bak/system /data/;
/data/lagfixtemp/busybox mv /data/bak/dalvik-cache /data/;
/data/lagfixtemp/busybox mv /data/bak/app/app-private /data/;
/data/lagfixtemp/busybox mv /data/bak/app /data/;
/data/lagfixtemp/busybox mv /system/bin/playlogosnow /system/bin/playlogos1;
reboot
Click to expand...
Click to collapse
Jesus christ how did you know all this stuff ? gonna try it out ill let you know how it goes -- brb
frankencat said:
You don't need to run anything. Just download it and unzip the files to a directory on your computer like C:\android-sdk-windows
Then add the tools directory to you PATH setting
C:\android-sdk-windows\tools
Let me know if you don;t know how to do that and I will walk you through it.
Click to expand...
Click to collapse
I got adb up and running
but please explain (in detail) your solution you mentioned in the previous page --
"You can use mke2fs to re-create linux.ex2
Ex. mke2fs /data/linux.ex2
This could get you booted up again. Then you could uninstall/reinstall the lagfix."
Please in details explain what you mean and show commands. Thanks
frankencat said:
You said you have ADB so do this...hook up your phone and fire up a command window on you pc.
type in "adb shell"
this should get you into adb shell (duh).
next type "su"
Now enter the following one at a time on order. The last line will reboot your phone.
/data/lagfixtemp/busybox rm -rf /data/data;
/data/lagfixtemp/busybox rm -rf /data/system;
/data/lagfixtemp/busybox rm -rf /data/dalvik-cache;
/data/lagfixtemp/busybox rm -rf /data/app;
/data/lagfixtemp/busybox rm -rf /data/app-private;
/data/lagfixtemp/busybox mv /data/bak/data /data/;
/data/lagfixtemp/busybox mv /data/bak/system /data/;
/data/lagfixtemp/busybox mv /data/bak/dalvik-cache /data/;
/data/lagfixtemp/busybox mv /data/bak/app/app-private /data/;
/data/lagfixtemp/busybox mv /data/bak/app /data/;
/data/lagfixtemp/busybox mv /system/bin/playlogosnow /system/bin/playlogos1;
reboot
Click to expand...
Click to collapse
when I type adb shell I get
error: device not found
am I doing something wrong ?
I rebooted my phone (galaxy S logo / start up screen) then it goes black as usual -- then I connected the cable and ran ADB from CMD.exe and typed ADB shell and got that error
Add C:\android-sdk-windows\tools to you computer's PATH...
- Open System Properties by right-clicking on My Computer
- Click on Advanced tab
- Click on Environment Variables
- Find PATH in System Varibles (bottom window) and open it for editing by either double-clicking or selecting it and clickin Edit button
- Scroll all the way to the end of the PATH string and enter a semi-colon ; at the end
- Paste the path to the sdk tools directory right after the semi-colon (C:\android-sdk-windows\tools)
- Click OK, OK, OK all the way out.
Now type "PATH" (without the quotes) in the command window and you should see the new path in the window. If not then close the window and open a new one. The tools dir should now be in the path and you are ready to use ADB.
You probably do not have have USB debugging enabled. Do you know if you eneabled that before or not? Also, did you make an nandroid backup before you started this?
And yes, it is because of Jesus Christ that I know this stuff.
<><
frankencat said:
Add C:\android-sdk-windows\tools to you computer's PATH...
- Open System Properties by right-clicking on My Computer
- Click on Advanced tab
- Click on Environment Variables
- Find PATH in System Varibles (bottom window) and open it for editing by either double-clicking or selecting it and clickin Edit button
- Scroll all the way to the end of the PATH string and enter a semi-colon ; at the end
- Paste the path to the sdk tools directory right after the semi-colon (C:\android-sdk-windows\tools)
- Click OK, OK, OK all the way out.
Now type "PATH" (without the quotes) in the command window and you should see the new path in the window. If not then close the window and open a new one. The tools dir should now be in the path and you are ready to use ADB.
Click to expand...
Click to collapse
I did all of this - i type in PATH and I see the new path etc.
But when i type adb shell it still says "device not found"
frankencat said:
You probably do not have have USB debugging enabled. Do you know if you eneabled that before or not? Also, did you make an nandroid backup before you started this?
And yes, it is because of Jesus Christ that I know this stuff.
<><
Click to expand...
Click to collapse
I don't think I enabled it -- as this happened spontaneously -- is there any way to fix this ? or am I seriously screwed ?
Not screwed, there is always a way.
Try this, pull your battery to power down your phone and then put the battery back in but DONT power it back up.
Now you have to do this all at the same time...hold down the up and down volume buttons and press down the power button. Hold all three buttons until you see the black Vibrant screen. KEEP HOLDING the up and down volume buttons until you see the yellow diags screen and then the green recovery screen.
Using the up/down volume keys to move, select "Reinstall Packages" and press the power button to select.
Tell me what you see...
Related
ok so im trying to get rid of some apk that r no longer on my g1 they r just on my ext 3. i went into terminal and tried 2 sets of sripts. the 1st one was:
su
cd /system/sd
ls app
rm pk blah blah
basically when i ran this i got no such file in directory message. so i searched and tried this next:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /ststem
it said: device or resource busy
can anyone help? im on cm 3.6.8.1 with ext3. i dont have my pc with ubuntu on it it crashed.
do rm *.apk to remove all of them
alritewhadeva said:
do rm *.apk to remove all of them
Click to expand...
Click to collapse
yea i know that command but im just trying to get rid of one not all
pistol4413 said:
yea i know that command but im just trying to get rid of one not all
Click to expand...
Click to collapse
its case sensitive remember that..ur typing it wrong. not a mounting issue
su
cd /system/sd/app
ls
rm *APPNAMEASLISTEDABOVE*
Jonno12345 said:
su
cd /system/sd/app
ls
rm *APPNAMEASLISTEDABOVE*
Click to expand...
Click to collapse
Umm I tried that. I said I tried it in the 1st post. And I'm 100 percent sure I typed it right I wrote down the name on a seprate peice of paper and checking it twice.
In your first post, you're listing all the applications in the app folder, but then trying to remove them from the /system/sd folder. You need to cd into the app folder, then do the rm command, or do rm ./app/*APP NAME*
Atleast try following my steps before concluding they are not right .
Ok tried it ur way and same results:
Su
Cd /system/sd
Ls app
Rm com.bg.smsbk.apk
Rm: can not remove 'com.bg.smsbk.apk' No such file or directory
And like I said I tried this 1st b4 I posted, and I checked the spelling
You're missing a VERY important part of my instructions
su
*********** cd /system/sd/app **************
That /app part isn't for show, that is necessary.
Then use ls, not ls app
Follow my instructions to the letter, and you'll find a much better success rate .
Even better, tell me the name of the app and I can tell you exactly what to type
Lol I truer ur commands didn't work same result. And by the way cd/system/sd/app is the same as this:
Cd /system/sd
Ls app
My command involve a few extra sets but either way they r the same as urs
pistol4413 said:
Lol I truer ur commands didn't work same result. And by the way cd/system/sd/app is the same as this:
Cd /system/sd
Ls app
My command involve a few extra sets but either way they r the same as urs
Click to expand...
Click to collapse
try going into the recovery console
<enter>
mount /system
rm /system/sd/app/xxxxxxxxxx.apk
reboot
if you can't get anything else to work then download root explorer and delete the .apk using it.
pistol4413 said:
Lol I truer ur commands didn't work same result. And by the way cd/system/sd/app is the same as this:
Cd /system/sd
Ls app
My command involve a few extra sets but either way they r the same as urs
Click to expand...
Click to collapse
What he's saying is that when you type rm blah, you are trying to remove something from /system/sd/ when you need to be removing it from /system/sd/app therefore, you need to cd /system/sd/app to have the plain vanilla rm, otherwise, you need to rm app/blah.
I hate typing in the full names so what I do, is take a specific part of the apk filename that no other file has i.e.
If i was trying to delete com.flargh.apk, I would type
cd /system/sd/
ls app
rm app/*flargh* <- these asterisks are necessary, they are wildcards (just if you didn't know, I didn't want to clarify with another post down the line)
This way, its harder to mess up as you only need to type in a small portion of the actual filename.
h.nocturna said:
I hate typing in the full names so what I do, is take a specific part of the apk filename that no other file has i.e.
If i was trying to delete com.flargh.apk, I would type
cd /system/sd/
ls app
rm app/*flargh* <- these asterisks are necessary, they are wildcards (just if you didn't know, I didn't want to clarify with another post down the line)
This way, its harder to mess up as you only need to type in a small portion of the actual filename.
Click to expand...
Click to collapse
Great tip. I love it. Makes things so much simpler. Works like a charm.
@OP, your initial problem is that you were trying to do this from terminal, which is impossible if you are on apps2sd because the ext3 partition is in use whenever the phone is booted normally. therefore, you MUST reboot into recovery to mess with your ext3 partition in ANY WAY.
-BMFC
pistol4413 said:
Lol I truer ur commands didn't work same result. And by the way cd/system/sd/app is the same as this:
Cd /system/sd
Ls app
My command involve a few extra sets but either way they r the same as urs
Click to expand...
Click to collapse
This is not the same thing at all, this is:
cd /system/sd
You're now in the /system/sd folder
ls app
You're listing everything in the /system/sd/app folder
rm *app*
You're still in the /system/sd folder, so it's trying to remove the file from there, NOT the app folder you listed. My method would put you in the correct folder. You can use your method, but before the rm command, type 'cd app', that would work, but it adds unnecessary steps.
can someone give me a tutorial on how to update the user.conf..i have looked at the compcache threads and linux swap but im not getting it...i want to be able to update it through terminal emulator and do i have to do nething to the userinit.sh if i change the user.conf...because numerous configs i have done for swappiness and linux swap...etc, have shown no difference..can somone give me a walkthrough...thanks so much..sry if i have a lot of questions just want to make myself more knowledgeable so i can hopefully return the favor to somone else one day
i do not know if you can edit it through the terminal sorry. i do know that you do not have to change the userinit.sh if you change user.conf, also i do know that you can open it up with PSPad (thats what i use) on a computer edit it there and push it back to phone and reboot. sorry i couldn't answer all of your questions
well i have had no problems editing it...its just putting it back nd making sure it works..now i have no problem using adb if u know of a tutorial to use it on mac...or know how to use it on mac
when you put it back on the phone did you make sure to chmod 755 it after you put it back on the phone and reboot?
then to text it with adb just type adb shell sh /system/sd/userinit.sh -s and see if the new values you put in are reflected in the output of that command
david1171 said:
when you put it back on the phone did you make sure to chmod 755 it after you put it back on the phone and reboot?
then to text it with adb just type adb shell sh /system/sd/userinit.sh -s and see if the new values you put in are reflected in the output of that command
Click to expand...
Click to collapse
delete this post; see below...
david1171 said:
when you put it back on the phone did you make sure to chmod 755 it after you put it back on the phone and reboot?
then to text it with adb just type adb shell sh /system/sd/userinit.sh -s and see if the new values you put in are reflected in the output of that command
Click to expand...
Click to collapse
this applies to tools and location of user.conf on cyanogen's roms ->
-transfer it to the root of your sdcard from your pc or mac to the g1.
-unmount sdcard from dropdown on the g1
-open up terminal on the g1
type and hit enter afterwards: cp /sdcard/user.conf /system/sd
type and hit enter afterwards: dos2unix /system/sd/user.conf
type and hit enter afterwards: chmod 664 /system/sd/user.conf
type and hit enter afterwards: exit
reboot
see this is my problem..it does not find it in system/sd...it is in system/bin so am i suppsed to copy it back to /system/bin or system/sd
and can someon explain what the difference is between chmod 664 and chmod 755 nd why i should do them
bonkasnucca said:
see this is my problem..it does not find it in system/sd...it is in system/bin so am i suppsed to copy it back to /system/bin or system/sd
and can someon explain what the difference is between chmod 664 and chmod 755 nd why i should do them
Click to expand...
Click to collapse
i think chmod 755 gives it read/write permissions. do not know about 664. try putting it in system/sd with adb then chmod 755 it and see if that works
david1171 said:
i think chmod 755 gives it read/write permissions. do not know about 664. try putting it in system/sd with adb then chmod 755 it and see if that works
Click to expand...
Click to collapse
775 = rwx-rwx-rx. conf file does not need executable in u-g nor x in o groups.
664 = rw-rw-r
if it is in /system/bin do this:
open up terminal
dos2unix /sdcard/user.conf
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/user.conf /system/bin
chmod 664 /system/bin/user.conf
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
exit
exit
reboot
I have Sprint signed 2.0 ruu and I have the phone rooted successfully.
My problem is this, when I try to flash the recovery image it says "file not found"
I've tried flashing from terminal on phone and from CMD on pc.
I have searched and searched with no luck.
please anyone help. Also how to use nand Restore what is the file that is being restored.
Also how to add removed apps from DC 2.0.72 rom step by step please.
Thanks
make sure debugging is turned on in the phone
settings>applications>development>usb debugging
Here is a guide that you can try
http://forum.androidcentral.com/htc-hero-roms-hacks/9542-how-repair-your-bootloader-after-using-2-1-ruu.html
or try these instructions
http://forum.xda-developers.com/showthread.php?t=583291
Theres some others you can do, but its a males it more difficult after doing the 2.1 RUU
Thanks for the reply
Still showing flash image not found
I tried those websites with no luck!! Does this not work after installing the 2.1 ruu?
C:\AndroidSDK\tools>adb shell
# su
su
# cd /sdcard
cd /sdcard
# flash_image recovery recovery-ra-heroc-v1.6.2-blue.img
flash_image recovery recovery-ra-heroc-v1.6.2-blue.img
flash_image: not found
# [1] Killed su
# exit
exit
C:\AndroidSDK\tools>adb shell
# su
su
# cd /sdcard
cd /sdcard
# flash_image recovery recovery-ra-heroc-v1.5.2.img
flash_image recovery recovery-ra-heroc-v1.5.2.img
flash_image: not found
# flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image: not found
# exit
exit
# adb push recovery-RA-heroc-v1.5.2.img /sdcard
adb push recovery-RA-heroc-v1.5.2.img /sdcard
adb: not found
#
joshuadb20 said:
I tried those websites with no luck!! Does this not work after installing the 2.1 ruu?
C:\AndroidSDK\tools>adb shell
# su
su
# cd /sdcard
cd /sdcard
# flash_image recovery recovery-ra-heroc-v1.6.2-blue.img
flash_image recovery recovery-ra-heroc-v1.6.2-blue.img
flash_image: not found
# [1] Killed su
# exit
exit
C:\AndroidSDK\tools>adb shell
# su
su
# cd /sdcard
cd /sdcard
# flash_image recovery recovery-ra-heroc-v1.5.2.img
flash_image recovery recovery-ra-heroc-v1.5.2.img
flash_image: not found
# flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image: not found
# exit
exit
# adb push recovery-RA-heroc-v1.5.2.img /sdcard
adb push recovery-RA-heroc-v1.5.2.img /sdcard
adb: not found
#
Click to expand...
Click to collapse
No that will not work. pm me and I will fix it with you on gtalk.
Since you ran the test ruu you do not have flash_image on your phone. You need to push flash_image to /system/bin/flash_image. I will attach it as a .zip below. Put the .zip in your sdk folder then follow these adb instructions to rename and push it:
Code:
adb remount
adb push flash_image.zip /system/bin/flash_image
Be sure to type it as above to correctly rename it..it is not really a .zip but XDA forces the rename to attach..
You have to give flash_image permission now, so type this:
Code:
adb remount
adb shell chmod 0755 /system/bin/flash_image
Now you should be able to flash the custom recovery if you have indeed rooted your phone and gave permissions to flash_image.
Thankyou thankyou thankyou
I love you guys, This fixed my issue, it drove me nutts all night last night.
Thank you very much!!! Your posting solved my all day issue, im happy :-*
C:\>cd androidsdk\tools\
C:\AndroidSDK\tools>adb shell
$ su
su
# cd /sdcard/
cd /sdcard/
# flash_image recovery recovery-ra-heroc-v1.2.3.img
flash_image recovery recovery-ra-heroc-v1.2.3.img
flash_image: not found
# adb remount
adb remount
adb: not found
#
I am having the same issue on my phone except I can't get the the flash_image file to even work. See above for example of my outcome. Am I not rooted fully? I am using universal androot and getting the Superuser icon and everything. Please help if you can. This is driving me crazy.
91nbtsi said:
...
# flash_image recovery recovery-ra-heroc-v1.2.3.img
...
Click to expand...
Click to collapse
Are you sure it is not named recovery-RA-heroc-v1.2.3.img ?
kjjjjshab said:
Are you sure it is not named recovery-RA-heroc-v1.2.3.img ?
Click to expand...
Click to collapse
I am pretty new to this, so it is case sensitive? I will try and see.
jeez guys. just plug your phone into your computer and drop the heroc-...img into your sdcard's root folder.
then:...\tools> adb shell
ls (to see what's in your current directory)
cd sdcard (to hop onto your sdcard)
su (if not already root)
flash_recovery recovery-.......3.img
reboot recovery
kjjjjshab said:
Are you sure it is not named recovery-RA-heroc-v1.2.3.img ?
Click to expand...
Click to collapse
It is the command "flash_image" that is not found - not the img file
I have the same problem - but in posting it I see that everyone is looking at the error as though it relates to9 the img file
91nbtsi said:
C:\>cd androidsdk\tools\
C:\AndroidSDK\tools>adb shell
$ su
su
# cd /sdcard/
cd /sdcard/
# flash_image recovery recovery-ra-heroc-v1.2.3.img
flash_image recovery recovery-ra-heroc-v1.2.3.img
flash_image: not found
# adb remount
adb remount
adb: not found
#
I am having the same issue on my phone except I can't get the the flash_image file to even work. See above for example of my outcome. Am I not rooted fully? I am using universal androot and getting the Superuser icon and everything. Please help if you can. This is driving me crazy.
Click to expand...
Click to collapse
Here is what you need to do
Code:
adb shell
cd sdcard
flash_image recovery xxxxxxxxxxxx.img
reboot recovery
You should not need to remount, but if you need to or for future reference you type in adb remount from the command prompt and not in adb shell
diogenesthesceptic said:
It is the command "flash_image" that is not found - not the img file
I have the same problem - but in posting it I see that everyone is looking at the error as though it relates to9 the img file
Click to expand...
Click to collapse
Read an earlier post, download the file and do what the post instructs. You need the flash_image file on your phone
danknee said:
Since you ran the test ruu you do not have flash_image on your phone. You need to push flash_image to /system/bin/flash_image. I will attach it as a .zip below. Put the .zip in your sdk folder then follow these adb instructions to rename and push it:
Code:
adb remount
adb push flash_image.zip /system/bin/flash_image
Be sure to type it as above to correctly rename it..it is not really a .zip but XDA forces the rename to attach..
You have to give flash_image permission now, so type this:
Code:
adb remount
adb shell chmod 0755 /system/bin/flash_image
Now you should be able to flash the custom recovery if you have indeed rooted your phone and gave permissions to flash_image.
Click to expand...
Click to collapse
Mine says "remount failed: Operation not permitted" when I try to remount.
LARPkitten said:
Mine says "remount failed: Operation not permitted" when I try to remount.
Click to expand...
Click to collapse
If you are in recovery and trying this you do not need to remount. If you are booted into Android try
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
you might also replace /dev/block/mtdblock3 with /dev/mtd/mtd1
and then chmod
I am having this problem as well.
Okay if your having a problem with the ole "flash_image not found" saying do this open up command prompt and type
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
then open up another command prompt with the old one still running and type this
Code:
adb push flash_image /bin
adb shell chmod 0755 /system/bin/flash_image
Now you should be good to flash your recovery
Asadullah said:
Okay if your having a problem with the ole "flash_image not found" saying do this open up command prompt and type
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
then open up another command prompt with the old one still running and type this
Code:
adb push flash_image /bin
adb shell chmod 0755 /system/bin/flash_image
Now you should be good to flash your recovery
Click to expand...
Click to collapse
I'm getting all the same errors everyone else on here is getting. Is flash_recovery a file that is required? I don't mean the .img file, but is it some kind of command file?
I used Qemu local.prop method to set /system/fonts folder as 766 and bricked my KFHD with the following steps:
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
adb shell
echo ‘ro.kernel.qemu=1′ > /data/local.prop
exit
adb reboot
adb shell mount -o remount,rw /system
adb push myfont.ttf /system/fonts
adb shell
cd /system/fonts
mv DroidSans.ttf DroidSans.ttf.bak
ln -s myfont.ttf DroidSans.ttf
chmod -R 06766 /system/fonts
rm /data/local.prop
exit
adb reboot
Click to expand...
Click to collapse
Now my KFHD does gets stucked in
"Your Kindle doesn't seem to be able to boot"
Is that because I changed the permission? Or is it because I did not reboot first after changing permission, and than delete local.prop? Which step was wrong? I am worried that doing that again would cause the same problem. I assume that the only way to recover from this would be to get into fastboot mode with factory cable. But I still want to keep fonts folder as writable.
When you edit files like this, with a device like a KFHD, odds are they deal with the framework-res.apk And if you mess with files that deal with framework-res.apk, your bound to get boot loop. But anyways, can you get adb? If not, fast boot might be your best friend. Cables are available that can boot to it, and if you see the system img. Files in the android development section, you can use fasboot to flash those. It's not the easiest solution, but it is something.
Sent from my Fire HD with root!
Hello,
I downloaded the latest version of busybox on my o4x, after I downloaded that, I turned off my device. When I tried to turn it back on, it got stuck on the 'loading apps' page, so I can't basicly do nothing with the phone. I let it load apps for like 10 hours (while on the charger) but that didn't work, and I let my phone run out of battery and after a couple of hours turn it back on, that also didn't work.
Does anyone know how to fix it, or can at least tell me what the problem is?!
Thanks,
Luuk
Try to clear dalvik cache, so that it gets rebuilt. Then try again. If you don't have CWM installed, you might as well be able to do it manually, but unfortunately I don't know the commands for that atm.
luuk.vandeven said:
Hello,
I downloaded the latest version of busybox on my o4x, after I downloaded that, I turned off my device. When I tried to turn it back on, it got stuck on the 'loading apps' page, so I can't basicly do nothing with the phone. I let it load apps for like 10 hours (while on the charger) but that didn't work, and I let my phone run out of battery and after a couple of hours turn it back on, that also didn't work.
Does anyone know how to fix it, or can at least tell me what the problem is?!
Thanks,
Luuk
Click to expand...
Click to collapse
I had the same problem. You can start the P880 in stock recovery and connect it to pc. After the drivers are installed, you have access via adb. Because you installed busybox, i think your device is rooted. So you cann access your P880 with "adb shell", in the shell "su", then you have to mount system and you can push another busybox (e.q. from root, the o4xr directory contains a functionally busybox) to your phone (/system/xbin)
Just download o4xr.zip from the "How to Root" thread.
Then do the following:
- extract o4xr.zip and switch to that folder
- adb shell "su -c 'mount -o remount,rw -t ext4 /dev/block/mmcblk0p33 /system'"
- adb push busybox /sdcard/
- adb shell "su -c 'cat /sdcard/busybox > /data/local/busybox'"
- adb shell "su -c 'chmod 777 /data/local/busybox'"
- adb shell "su -c 'cat /sdcard/busybox > /system/xbin/busybox'"
- adb shell "su -c 'chmod 777 /system/xbin/busybox'"
- At this point the device will reboot itself automatically (Don't know why?), if not: adb shell 'su -c reboot'
- Delete /sdcard/busybox
- Done
I´ve done all this and its booting again with no problems....
Allright, it all sound really complicated to me. I will do my very best! But how exactly do I boot my phone in stock recovery mode, volume up and power button at the same time?
Bogeyof said:
I had the same problem. You can start the P880 in stock recovery and connect it to pc. After the drivers are installed, you have access via adb. Because you installed busybox, i think your device is rooted. So you cann access your P880 with "adb shell", in the shell "su", then you have to mount system and you can push another busybox (e.q. from root, the o4xr directory contains a functionally busybox) to your phone (/system/xbin)
Just download o4xr.zip from the "How to Root" thread.
Then do the following:
- extract o4xr.zip and switch to that folder
- adb shell "su -c 'mount -o remount,rw -t ext4 /dev/block/mmcblk0p33 /system'"
- adb push busybox /sdcard/
- adb shell "su -c 'cat /sdcard/busybox > /data/local/busybox'"
- adb shell "su -c 'chmod 777 /data/local/busybox'"
- adb shell "su -c 'cat /sdcard/busybox > /system/xbin/busybox'"
- adb shell "su -c 'chmod 777 /system/xbin/busybox'"
- At this point the device will reboot itself automatically (Don't know why?), if not: adb shell 'su -c reboot'
- Delete /sdcard/busybox
- Done
I´ve done all this and its booting again with no problems....
Click to expand...
Click to collapse
luuk.vandeven said:
Allright, it all sound really complicated to me. I will do my very best! But how exactly do I boot my phone in stock recovery mode, volume up and power button at the same time?
Click to expand...
Click to collapse
Vol- & Power. Vol+ & Power will bring you to "Emergency mode", this might work as well. Just make sure you have adb access.
Hello
Thanks for the guidance' the only thing is that "adb push busybox /sdcard/" is not recognized so I pushed the file into /temp I created and then continued accordingly
yishay said:
Hello
Thanks for the guidance' the only thing is that "adb push busybox /sdcard/" is not recognized so I pushed the file into /temp I created and then continued accordingly
Click to expand...
Click to collapse
Normally u can push directly through /data/local without the /sdcard step. But its ok to push it to any other local tem-folder before moving it to /system/xbin...
Search for total commander the pc version and the adb plugin then you can access the phone file system, il post what next to do,
* total commander - http://www.ghisler.com/ - officall free version
adb plugin -- http://www.totalcmd.net/plugring/android_adb.html
---------- Post added at 03:53 PM ---------- Previous post was at 03:43 PM ----------
basically what you need to do is said in this extract from a previous post i had done
open total commander and then click configuration and then click options then next click the plugins tab followed by the the WFX button,
then point it at the installed adb plugin,
Once you have done that click the Drive tab in total commander it will be set a drive C:/ and change to Network Neighbourhood, now go to your phone and plug in your usb lead while powering it up and holding the power key and volume up and not releasing until it starts.
Now in total commander click adb in the explorer part and it access you into your phones file system so click on the root folder then click the system folder and then click the Xbin folder i replace the busybox inside with the busybox file which is in o4xr
Please
Hello,
Thanks for the support, but I don't understand anything from your post. I'm not a real geek, and know how all this stuff works, so my phone is still dead. Lg won't take it back for repair, and other phone companies can't manage to fix my phone. So can you please give me some more specific instructions, sorry that i'm a noob, but I miss my phone .
I only understood the 'download the onxr4 file and extract it', after that I lost it:silly:.
Bogeyof said:
I had the same problem. You can start the P880 in stock recovery and connect it to pc. After the drivers are installed, you have access via adb. Because you installed busybox, i think your device is rooted. So you cann access your P880 with "adb shell", in the shell "su", then you have to mount system and you can push another busybox (e.q. from root, the o4xr directory contains a functionally busybox) to your phone (/system/xbin)
Just download o4xr.zip from the "How to Root" thread.
Then do the following:
- extract o4xr.zip and switch to that folder
- adb shell "su -c 'mount -o remount,rw -t ext4 /dev/block/mmcblk0p33 /system'"
- adb push busybox /sdcard/
- adb shell "su -c 'cat /sdcard/busybox > /data/local/busybox'"
- adb shell "su -c 'chmod 777 /data/local/busybox'"
- adb shell "su -c 'cat /sdcard/busybox > /system/xbin/busybox'"
- adb shell "su -c 'chmod 777 /system/xbin/busybox'"
- At this point the device will reboot itself automatically (Don't know why?), if not: adb shell 'su -c reboot'
- Delete /sdcard/busybox
- Done
I´ve done all this and its booting again with no problems....
Click to expand...
Click to collapse
Try reflash the *.KDZ .
See this thread :-
http://forum.xda-developers.com/showthread.php?t=2069723
Then boot into recovery [ (power on) + (vol-) ] .
Then wipe cache ,, and do factory resert . This will delete all your apps .
Good Luck .
Sent From LG-P880
Try Use THANKS Button If I Helped
Kdz flash
luuk.vandeven said:
Hello,
I downloaded the latest version of busybox on my o4x, after I downloaded that, I turned off my device. When I tried to turn it back on, it got stuck on the 'loading apps' page, so I can't basicly do nothing with the phone. I let it load apps for like 10 hours (while on the charger) but that didn't work, and I let my phone run out of battery and after a couple of hours turn it back on, that also didn't work.
Does anyone know how to fix it, or can at least tell me what the problem is?!
Thanks,
Luuk
Click to expand...
Click to collapse
do the kdz flash. Easiest and safest. Worked for me with the same prob like you.
Did that
I already did that al long time ago, didn't work though. I'm considering to buy a new phone, I've been having these prpblems for several weeks now.
OS_Hacking said:
Try reflash the *.KDZ .
See this thread :-
http://forum.xda-developers.com/showthread.php?t=2069723
Then boot into recovery [ (power on) + (vol-) ] .
Then wipe cache ,, and do factory resert . This will delete all your apps .
Good Luck .
Sent From LG-P880
Try Use THANKS Button If I Helped
Click to expand...
Click to collapse
luuk.vandeven said:
I already did that al long time ago, didn't work though. I'm considering to buy a new phone, I've been having these prpblems for several weeks now.
Click to expand...
Click to collapse
Why don't you just send it to LG for repair. They'll fix it for you and you'll get it back as good as new. And after you have done that, stop messing around with busybox.
luuk.vandeven said:
I already did that al long time ago, didn't work though. I'm considering to buy a new phone, I've been having these prpblems for several weeks now.
Click to expand...
Click to collapse
What doy exactly mean? You tried that but didn't work or you are unable to do a kdz flash? Please be clear.
!!
OS_Hacking said:
Try reflash the *.KDZ .
See this thread :-
http://forum.xda-developers.com/showthread.php?t=2069723
Then boot into recovery [ (power on) + (vol-) ] .
Then wipe cache ,, and do factory resert . This will delete all your apps .
Good Luck .
Sent From LG-P880
Try Use THANKS Button If I Helped
Click to expand...
Click to collapse
Dude...
You are my man! I've got the problem solved, so thank you!!