Hello,
I have LG Optimus Elite Android 2.3.7...it was rooted...
I accidentally deleted /system/bin/sh...gee..oh my god..
The problem is that I am not even able to adb to my phone now..
If I do adb to that phone, it is complained about /system/bin/sh doesn't exist something...
Gee...........
Obviously, factory reset didn't help cuz it didn't restore the sh...
What would be my option ??
When I just reboot my phone, it is just stay "Welcome to" screen...Even though I touched the begin, it won't go next..I think because..
my /system/bin/sh file is deleted..so my phone can't execute anything from the phone shell..
What would be my option to recover my phone?
Please help
Thanks,
Get a copy of sh and
> adb push sh /system/bin/
But /system is read-only so you need to mount read-write. But you cannot because
> adb shell
Cannot execute sh because it is not there.
You need to restore from nandroid backup. Failimg that, restore back to stock with Odin.
anotherguy19 said:
Get a copy of sh and
> adb push sh /system/bin/
But /system is read-only so you need to mount read-write. But you cannot because
> adb shell
Cannot execute sh because it is not there.
You need to restore from nandroid backup. Failimg that, restore back to stock with Odin.
Click to expand...
Click to collapse
I would follow his advice. Good luck!
Thanks for your suggestion.
BTW, nandroid backup -> I don't think I can use it because I don't have original backup rom?
Odin -> does this also work for LG phone?
anotherguy19 said:
Get a copy of sh and
> adb push sh /system/bin/
But /system is read-only so you need to mount read-write. But you cannot because
> adb shell
Cannot execute sh because it is not there.
You need to restore from nandroid backup. Failimg that, restore back to stock with Odin.
Click to expand...
Click to collapse
goforandroid said:
Thanks for your suggestion.
BTW, nandroid backup -> I don't think I can use it because I don't have original backup rom?
Odin -> does this also work for LG phone?
Click to expand...
Click to collapse
No, you can't use nandroid backup. A nandroid is an image file of your system partitions. PC users typically know this as ghosting or cloning. To linux users, it's just a dd. You create the image yourself from a working copy. You don't need the original ROM. You can make a backup of your /system partition (nandroid) any time you have a working copy.
PS I'm an idiot. LG was literally the first thing u said. And you are correct. You need to use LG Flash Tool.
See 1942836
Unfortunately, 1942836 is not the same model I have.
I don't think I can use that instruction.
It really makes me crazy since I can't use adb at all....
I tried creating update.zip and put it in sd card to install..however, as you may know, signature verification failed.
if I could get key file to create signed zip file other than test one, that may work.
Is there anyway I can bypass the signature verification??????
Thanks,
anotherguy19 said:
No, you can't use nandroid backup. A nandroid is an image file of your system partitions. PC users typically know this as ghosting or cloning. To linux users, it's just a dd. You create the image yourself from a working copy. You don't need the original ROM. You can make a backup of your /system partition (nandroid) any time you have a working copy.
PS I'm an idiot. LG was literally the first thing u said. And you are correct. You need to use LG Flash Tool.
See 1942836
Click to expand...
Click to collapse
Can't you reflash your system?
I think you need /bin/bash for adb to start, so without it, you can't push anything from your computer to your phone i guess..
What bootloader do you use?
1bymany said:
Can't you reflash your system?
I think you need /bin/bash for adb to start, so without it, you can't push anything from your computer to your phone i guess..
What bootloader do you use?
Click to expand...
Click to collapse
Obviously, before happening this issue, I was able to use adb...
And..now..if I issue adb, then nothing shows up in the list of devices attached section...I guess because it can't communicate somehow with /system/bin/sh I just accidentally deleted.
I know that I can use Odin to install CWM for Samsung phone....I just found that there is LG Flash tool program on the internet does simialr thing like Odin for LG phone..however, I am not sure where I can find the dll that I can use from LG Flash tool program.
Any idea?
Thanks,
goforandroid said:
Obviously, before happening this issue, I was able to use adb...
And..now..if I issue adb, then nothing shows up in the list of devices attached section...I guess because it can't communicate somehow with /system/bin/sh I just accidentally deleted.
I know that I can use Odin to install CWM for Samsung phone....I just found that there is LG Flash tool program on the internet does simialr thing like Odin for LG phone..however, I am not sure where I can find the dll that I can use from LG Flash tool program.
Any idea?
Thanks,
Click to expand...
Click to collapse
You will indeed have to reflash your device, as you don't have any other way of putting the bash binairy back.
I guess, as you are rooted, you know how to reflash your device. If you don't, search the forum
grtz
anotherguy19 said:
Get a copy of sh and
> adb push sh /system/bin/
But /system is read-only so you need to mount read-write. But you cannot because
> adb shell
Cannot execute sh because it is not there.
You need to restore from nandroid backup. Failimg that, restore back to stock with Odin.
Click to expand...
Click to collapse
perfect
Related
I'd been trying to figure out how to set up a few simple things in my rooted, post-MR, but otherwise stock CDMA Hero. Namely, ADB Remount permissions (/default.prop file), set up Superuser to properly manage permissions for apps that require root, and install Busybox. Ideally, I wanted to set these up manually. Turns out it's not as simple as one might hope. ADB Remount, for example, requires that you modify and repackage the boot.img/recovery.img.
So, what I've got here is a minimal update.zip file you can apply to your phone via the recovery console. Nothing crazy, it's just MoDaCo's ROM 1.1, but with everything taken out except for the aforementioned items. Once you patch your phone, just these items will be configured and your phone will still look, run, etc. the same as before. Also, a2sd will be copied to your /system/bin directory, but it's something that had to stay in the file for some reason, otherwise the phone wouldn't boot. Probably a setting Paul built into the boot.img.
In any case, here it is. It's working well for me. Hope it helps some of you out too.
****
Thanks goes to Paul of course (MoDaCo) camalot (Droid Explorer) and dagnasty for telling me about the auto-sign plugin that's available in Droid Explorer.
Instructions for manually installing Busybox over here:
http://forum.xda-developers.com/showthread.php?t=591303
****
I responded on ppcgeeks:
mercado79 said:
IAlso, a2sd will be copied to your /system/bin directory, but it's something that had to stay in the file for some reason, otherwise the phone wouldn't boot. Probably a setting Paul built into the boot.img.
Click to expand...
Click to collapse
Yup. It's a script that was added to the boot.img-ramdisk that copies all of your apps to your sd when apps2sd's requirements are met.
So if the sdcard is not partitioned correctly then ap2sd will not run, yes?
Smacky55 said:
So if the sdcard is not partitioned correctly then ap2sd will not run, yes?
Click to expand...
Click to collapse
"Correctly" is relative. If there is no EXT partition on the sdcard, then the ROM won't try to move your applications to it. But the script runs regardless.
Sorry, meant if sdcard isn't partitioned at all. Thanks for the answer.
flipzmode told me in another thread that even though this script is included, that doesn't mean that the update.zip i posted will enable apps2sd for anyone. there's more required in order to get it to work (i stripped most everything out).
A few simple questions. re -stock 1.56... rom
1) in the zip system folder, its refers to /xbin ; does that require that /system/xbin be pre-existent, or will it create it ?
2) busybox is in /system/bin on mine. Do I need to remove it?
a) if so then due to the "busybox --install -s /system/bin"
command , how do i remove the current symbolic busybox entry points?
b)have $PATH changes been applied to overwrite the current export
3) empty init.sh file?
4) google meta references?
I think I may understand the need to get bootstrap-"root" permissions established, is there another way as well?
Thanks for dealing with these noobie questions.
Thanks for this. worked out great.
willy900wonka said:
A few simple questions. re -stock 1.56... rom
1) in the zip system folder, its refers to /xbin ; does that require that /system/xbin be pre-existent, or will it create it ?
2) busybox is in /system/bin on mine. Do I need to remove it?
a) if so then due to the "busybox --install -s /system/bin"
command , how do i remove the current symbolic busybox entry points?
b)have $PATH changes been applied to overwrite the current export
3) empty init.sh file?
4) google meta references?
I think I may understand the need to get bootstrap-"root" permissions established, is there another way as well?
Thanks for dealing with these noobie questions.
Click to expand...
Click to collapse
sorry willy man. not sure what i can tell you. i'm pretty close to being a newbie myself. i never fully understood what the script was doing. i simply took the original modaco update and compared it to another script paul had posted on his forums last fall.
if you unzip the file, you should be able to see everything that's going on. the file structure is super simple, so modify it to suit your needs and give it a try. worst case, you'll need to revert to a nandroid backup. oh, and don't forget you'll need to sign the file and zip it back up in order to flash it onto the phone.
come to think of it, i guess maybe i should update the script using the latest modaco rom, though i'm not sure how helpful it'd be for everyone. to be honest, i've since bitten the bullet and moved on to flipz's rom and the gumbo kernel. runs beautifully!
Ok, so I formated the card, put the .zip file on the sdcard and tried to press home+power to enter the recovery council. When I hold home and press power I am taking to a screen that has an exclamation point and an image of the phone.
Can anyone help?
partylatino420 said:
Ok, so I formated the card, put the .zip file on the sdcard and tried to press home+power to enter the recovery council. When I hold home and press power I am taking to a screen that has an exclamation point and an image of the phone.
Can anyone help?
Click to expand...
Click to collapse
Boot the phone by holding home only. And...I'm assuming you have the recovery console installed and are rooted.
I think the problem is that a recovery boot image was not previously installed. A green screen with a set of options should've appeared.
http://forum.xda-developers.com/showthread.php?t=596879
I prefer 1.2.3
mercado79 said:
Boot the phone by holding home only. And...I'm assuming you have the recovery console installed and are rooted.
Click to expand...
Click to collapse
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?
partylatino420 said:
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=596879 explanation
code from : http://forum.xda-developers.com/showthread.php?t=583291
13:
Code:
adb push recovery-RA-heroc-v1.5.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
14:
Code:
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
http://tinyurl.com/yc96j2z
partylatino420 said:
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?
Click to expand...
Click to collapse
Your google search didn't turn anything up on "recovery council" because the operative use would have actually been "recovery console"..
that did it!! Thanks guys!!!
um, what???
mercado79 said:
So, what I've got here is a minimal update.zip file you can apply to your phone via the recovery console.
Click to expand...
Click to collapse
Apply via the recovery console? Sorry, still very new to this. Thanks!
Recovery Console
Go to the recovery console by holding down home when you power your Android. In that menu, you should see something that says 'flash update from SD card'... or something like that... then you choose the .zip that he has so kindly provided us.
Oh, and you have to put the .zip file that he provided on the SD card if that isn't already obvious :/
I also renamed it update.zip once I copied it to my SD card. Hope this clears it up a little. I just rooted my Hero yesterday.. so I am on the same NOOB level.
Do I need to wipe before flashing this / will this wipe my phone if I flash it?
fallonjp said:
Do I need to wipe before flashing this / will this wipe my phone if I flash it?
Click to expand...
Click to collapse
You shouldn't need to wipe your phone; however I really don't think it's a good idea to use this. I put this together last year when we were still running Android 1.5 so it's WAY out of date. Just go with Nfinite's ROMs. He keeps them almost completely stock (depending on which you choose) and they can serve as great back-up / go-to ROMs.
Dear all,
it is time for me to pay back. I have found a lot of information and tips from this forum. However, when I bricked my device by erasing the efs folder (trying to install Linux on my N8013 Tablet) I only found partial fixes, like creating the directory FactoryApp and the file factorymode with ON inside it.
I have searched forums and forums and I could not find a comprehensive answer. I tinker and tinker with my device and at last I recovered the efs folder and it does not get wiped out on boot.
Before today, I had to boot my Tablet and create the FactoryApp and file factorymode with ON inside it to make my Tablet not showing the Factory Test have stopped and to show the lock screen. Now all is back to normal.
When in recovery mode CWM the efs would not mount!!
Thanks to too many people, I have been visiting so many sites I do not remember the names of all!!! Thank you all!!
Ok, this is the procedure it worked for me.
1.- Install CWM recovery in your rooted tablet.
2.- Install ADB in your pc to be able to communicate with the tablet via com window. Install busybox as well.
3.- google a nv_data.bin file if you find one. I found one. I could find the download link if someone ask for it.
4.- BOOT your Tablet in Recovery mode push both the power and the volume up button (the farthest to the power button). When the First letters appear, release the power button, not the volume up until entering in recovery mode.
5.- Go to your PC, connect the USB cable to your tablet and go to C:\Program Files\Android\android-sdk\platform-tools>
6.- Type adb shell and hit return
7.- if you see # good, you have access to your tablet. Do not type su because does not work. You are root (I assume).
8.- type busybox df -h and check you do not have the efs mounted. In fact it does not even appear.
9.- Try to mount mmcblk0p3 (mount -w -t ext4 /dev/block/mmcblk0p3 /efs ) YES 0p3. I have found a lot of forums saying it is 0p1 but not in the Galaxy Note N8013. I tried with the 0p1 and did not work.
10.- Of course did not mount!!! That is the error. So we have to....
11.- Now try to make that partition, by typing mke2fs /dev/block/mmcblk0p3
12.- Now try to mount it again by typing mount -w -t ext4 /dev/block/mmcblk0p3 /efs It worked!!
13.- Now you have to keep the downloaded nv_data.bin file in the root of your sdcard, and a text file named factorymode with the letters ON inside.
14.- do busybox ls -ltr and you will see there is a folder called sdcard -> /data/media
15.- create a folder inside the /efs/ folder named FactoryApp
16.- Copy the factorymode from the root of your sdcard to the /efs/FactoryApp folder by typing: busybox cp /data/media/factorymode /efs/FactoryApp
17.- Copy the nv_data.bin from your sdcard to your efs folder by typing: busybox cp /data/media/nv_data.bin /efs
18.- Now change permissions to all those files inside efs with 0744 by typing: busybox chmod 0744 /efs/FactoryApp/factorymode
Do it with all!!
19.- Now change owner of the directory efs down with: busybox chown 1001.1001 /efs (I think there is a switch to change all at once, but I forgot so I changed all directories and folders inside efs.
11.- in CWM go to advanced and fix permissions.
12.- Boot in recovery mode.
13.- Try to mount efs partition and it works!!! Check with ADB that all your files are there and a lot more.
14.- Reboot the Tablet and the efs is there for good.
15.- Install in your computer EFS Pro and do a backup ofthe efs folder.
16.- I am sure the IMEI is not the good one, but the N8013 is not used as a phone anyway.
Please be careful and backup all the partitions of your tablet before doing this. It worked for my N8013 but I do not know if it will brick yours or if you have another model.
Thanks to:
XDA forum
arizzle.com even I did not use his efs image, but I used the instructions he provided. http://www.arizzle.com/android/gt-n8013/
SPT Team: http://forum.gsmhosting.com/vbb/archive/t-1296409.html
Da-G XDA forum: http://forum.xda-developers.com/showthread.php?t=882039
alvhergon at: http://www.htcmania.com/showthread.php?t=177297
People at community hosting: http://www.communityhosting.net/sgsunlock/i9000.html
Of course EFS Pro, ADB, busybox, ODIN, CWM Recovery developers!!
I hope this serve for somebody with my same problem. I gather all that information, put it together in this post and fixed my two months old tablet!!! Now I can go back to install Ubuntu again
Thanks for reading up to here!!
hey man,
thanks for your tut, my device is n8000 and it doesn't boot due to me installing tablet rom by mistake anyway, i did everything you did except i used .jar root explorer from here in the forums and transfered the files after i mounted it and choose 0p1 , im not sure what went wrong but anyway after that i used the commands to give permission and owner like you but they get wiped after restart, any ideas ?
dieselz said:
hey man,
thanks for your tut, my device is n8000 and it doesn't boot due to me installing tablet rom by mistake anyway, i did everything you did except i used .jar root explorer from here in the forums and transfered the files after i mounted it and choose 0p1 , im not sure what went wrong but anyway after that i used the commands to give permission and owner like you but they get wiped after restart, any ideas ?
Click to expand...
Click to collapse
Geez, I am far from an expert here. What folder/partition gets wiped out? efs? Because searching the web I realized the 0p1 is /system (maybe I am wrong) and 0p3 is /efs.
Did you try " mke2fs /dev/block/mmcblk0p3" or with 0p1? What happened?
Did you try "-w -t ext4 /dev/block/mmcblk0p3 /efs It worked!!" What happened?
I think, those are the most important steps, because it allows you to mount in recovery mode the /efs partition.
Later on, an important step is " cp /data/media/nv_data.bin /efs" but I do not know why?
Of course changing owership...
I am very sorry is not working for you. Please, try it again. I know what frustrating it is!!! I have had my tablet broken for more than two months and by trial and error finally got it working. I could send you the nv_data.bin file if you wanted. However, it will set your serial number to 000000 and I assume a wrong IMEI. But I do not use my tablet as a phone anyway.
I hope it helps!! Thanks for reading!!
nv_data.bin please help!
hey man! i have the same problem!!! i flashed a galaxy tab rom on my note 10.1, can you please post the nv_data.bin link.? i also tried to flash stock rom with odin but it still doesn't boot up
darko454 said:
hey man! i have the same problem!!! i flashed a galaxy tab rom on my note 10.1, can you please post the nv_data.bin link.? i also tried to flash stock rom with odin but it still doesn't boot up
Click to expand...
Click to collapse
Let me search for it and I will send it to you.
tripijb said:
Let me search for it and I will send it to you.
Click to expand...
Click to collapse
There you go!!
Thanks !! But should I reset the binary counter and return it or I'm better just playing with it???
Sent from my SPH-L710 using Tapatalk 2
darko454 said:
Thanks !! But should I reset the binary counter and return it or I'm better just playing with it???
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Reset the counter and return it at the last option. Just follow my instructions above and see if you could fix it!!! So far is bricked, isn't it?
Good luck!!!
Well I got it to boot but in factory mode... so I'll follow your instructions ! I'll get back to you. Thanks
Sent from my SPH-L710 using Tapatalk 2
darko454 said:
Well I got it to boot but in factory mode... so I'll follow your instructions ! I'll get back to you. Thanks
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Do it step by step!!!! let me know if it worked!!! It took me two months of search to find out the solution I posted!!!
tripijb said:
Do it step by step!!!! let me know if it worked!!! It took me two months of search to find out the solution I posted!!!
Click to expand...
Click to collapse
hey man sorry to bother i cant find text file named factorymode with the letters ON inside??
darko454 said:
hey man sorry to bother i cant find text file named factorymode with the letters ON inside??
Click to expand...
Click to collapse
No bothering at all!!!
Please help
tripijb said:
No bothering at all!!!
Click to expand...
Click to collapse
15.- create a folder inside the /efs/ folder named FactoryApp how do i do that>>???
Im stuck on this step!!
Is this right???
is this right?? please help i don't know what im doing!:crying:
i accidentally put in this command how do i go back??
C:\Android\platform-tools> im a mess please help???
darko454 said:
is this right?? please help i don't know what im doing!:crying:
i accidentally put in this command how do i go back??
C:\Android\platform-tools> im a mess please help???
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2111485
Do I have to do everything again?
Sent from my SPH-L710 using Tapatalk 2
Now what is wrong? Sorry to be a noob
darko454 said:
Do I have to do everything again?
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
What did i do???
Please help!!!! What should I do next?
Sent from my SPH-L710 using Tapatalk 2
Help Me!!
Hey i seem to do everything correct, untill i get to step 5, witch seems to be missing a step??
In platform-tools folder, what do i open up to get access to the tablet??
I get compleatly lost in step 6, i get a message saying......(in attachments).
I got N8013
darko454 said:
15.- create a folder inside the /efs/ folder named FactoryApp how do i do that>>???
Im stuck on this step!!
Click to expand...
Click to collapse
Geez I forgot, if you are in a PC using ADB use the command window and do mkdir to create a directory.
However, let me take a look at my step by step procedure to put myself in context.
I have been disconnected due an emergency trip, but I will be back in couple of days. Sorry for the late reply!!!
I screwed up my phone, there's not launcher, touchwiz, and system ui fail, setting app fails. Everything is screwed up. I'm really new to this, but is there any way to install these things (I have the apks) from recovery?
Ardentes said:
I screwed up my phone, there's not launcher, touchwiz, and system ui fail, setting app fails. Everything is screwed up. I'm really new to this, but is there any way to install these things (I have the apks) from recovery?
Click to expand...
Click to collapse
Push all your stock launcher,systemui,settings apk from stock ROM into a flash able zip
Sent from my GT-S7500 using xda app-developers app
Techix18 said:
Push all your stock launcher,systemui,settings apk from stock ROM into a flash able zip
Sent from my GT-S7500 using xda app-developers app
Click to expand...
Click to collapse
Soooo, not to sound like a noob, or whatever, but... how do I do that?
re-flash your stock rom/custom rom
akosicarlo said:
re-flash your stock rom/custom rom
Click to expand...
Click to collapse
I don't have the stock rom, all I have is the backup, and the backup is missing the system.img file
you backed up your custom rom?
find it on recovery
Backup and Restore -> Restore
akosicarlo said:
you backed up your custom rom?
find it on recovery
Backup and Restore -> Restore
Click to expand...
Click to collapse
I backed up a stock rom, using mtkdroidtools, however after telling it to prepare the block so that I can use sp flash tools, it gets all of the files ready, but there is no system.img file
what device u are using with?
Ardentes said:
Soooo, not to sound like a noob, or whatever, but... how do I do that?
Click to expand...
Click to collapse
Download your stock firmware and extract the system file from the firmware and grab whatever you need from the stock system file and put it into this sample.zip that i have attached.If you want to add any more things,pls add additional codes into the updater script
If you have cwm recovery then you can use adb to push the respective files to their places and set permissions
sorry for any ty¶°s
Techix18 said:
Download your stock firmware and extract the system file from the firmware and grab whatever you need from the stock system file and put it into this sample.zip that i have attached.If you want to add any more things,pls add additional codes into the updater script
Click to expand...
Click to collapse
I'm getting signature verification failed. Installation aborted
professor_proton said:
If you have cwm recovery then you can use adb to push the respective files to their places and set permissions
sorry for any ty¶°s
Click to expand...
Click to collapse
Unfortunately I don't have cwm, kinda wishing I did though
Ardentes said:
Unfortunately I don't have cwm, kinda wishing I did though
Click to expand...
Click to collapse
"One simply doesn't mess with phone without having a custom recovery "
Still if your ROM boots and your rooted and you have adb on your PC (its a must bro , I personally can't live without it )
Type (not the part in *le something* )
Adb shell *le presses enter*
Su *le presses enter again*
Mount -o rw, remount /system /system *le does it again*
Exit *enter*
Exit *enter*
Example if you want to push systemui
adb push SystemUI.apk /system/app/SystemUI.apk
*enter*
Similarly push all other apps
Adb shell *le presses enter again*
Su
Chmod 644 /system/app/SystemUI.apk
Change the SystemUI.apk to what ever app you want to replace
This Is one of these moments we realise how important adb and custom recoveries are
sorry for any ty¶°s
professor_proton said:
"One simply doesn't mess with phone without having a custom recovery "
Still if your ROM boots and your rooted and you have adb on your PC (its a must bro , I personally can't live without it )
Type (not the part in *le something* )
Adb shell *le presses enter*
Su *le presses enter again*
Mount -o rw, remount /system /system *le does it again*
Exit *enter*
Exit *enter*
Example if you want to push systemui
adb push SystemUI.apk /system/app/SystemUI.apk
*enter*
Similarly push all other apps
Adb shell *le presses enter again*
Su
Chmod 644 /system/app/SystemUI.apk
Change the SystemUI.apk to what ever app you want to replace
This Is one of these moments we realise how important adb and custom recoveries are
sorry for any ty¶°s
Click to expand...
Click to collapse
It isn't recognizing my phone
Ardentes said:
It isn't recognizing my phone
Click to expand...
Click to collapse
Debugging not enabled ???
it hurts when I help someone and they say thanks Instead of pressing the button
professor_proton said:
Debugging not enabled ???
it hurts when I help someone and they say thanks Instead of pressing the button
Click to expand...
Click to collapse
I can't enable debugging, the rom boots fine, as soon as it gets to the lock screen, there are no settings, because setting stops working, touchwiz stops working and so does systemui, and they constantly stop working to the point that I can't do anything.
Ardentes said:
I can't enable debugging, the rom boots fine, as soon as it gets to the lock screen, there are no settings, because setting stops working, touchwiz stops working and so does systemui, and they constantly stop working to the point that I can't do anything.
Click to expand...
Click to collapse
Well that sucks ! And the screwup of the year award goes to you !
Well then the last resort would be flashing stock rom using Odin
professor_proton said:
Well that sucks ! And the screwup of the year award goes to you !
Well then the last resort would be flashing stock rom using Odin
Click to expand...
Click to collapse
I'd love to... if my phone could go into download mode... or if I had the stock rom....
Ardentes said:
I'd love to... if my phone could go into download mode... or if I had the stock rom....
Click to expand...
Click to collapse
Which phone do you have ???
it hurts when I help someone and they say thanks Instead of pressing the button
professor_proton said:
Which phone do you have ???
it hurts when I help someone and they say thanks Instead of pressing the button
Click to expand...
Click to collapse
Its a gt-i9500 galaxys s4 clone. but it has only samsung logos, so I can't determine the original manufacturer.
i saved original build prop in my pc and and i want pull in my device with adb i do not have any info about this step my device go directly to black screen in firmware update
how i can push my build prop in my lg g3 d850 with pc win 7 64bit
help my
anasmilan said:
i saved original build prop in my pc and and i want pull in my device with adb i do not have any info about this step my device go directly to black screen in firmware update
how i can push my build prop in my lg g3 d850 with pc win 7 64bit
help my
Click to expand...
Click to collapse
Download android sdk, install it as google tells you. Go to the folder your build prop is at, hold shift, press the right mouse button, press on open command prompt. Type this in it:
adb shell
su
stop
mount -o rw, remount /system
push build.prop /system/build.prop
mount -o ro, remount /system
reboot
If you cant do that, you can always reflash the firmware
push not found
Remorcer said:
Download android sdk, install it as google tells you. Go to the folder your build prop is at, hold shift, press the right mouse button, press on open command prompt. Type this in it:
adb shell
su
stop
mount -o rw, remount /system
push build.prop /system/build.prop
mount -o ro, remount /system
reboot
If you cant do that, you can always reflash the firmware
Click to expand...
Click to collapse
i moved the build prop file to platform-tools file in sdk and i try go to command prompt with shift and Type this command
adb shell
su
stop
mount -o rw, remount /system
push build.prop /system/build.prop
tell me push: not found
see the pic
and i try the flash tools with the same tot & dll
the flash tools error
read model is deffrent
I use pushbullet for small stuff like this then just move it and set permissions with root explorer
Sent from my LG-D850 using Tapatalk 2
no android in device
screwyluie said:
I use pushbullet for small stuff like this then just move it and set permissions with root explorer
Sent from my LG-D850 using Tapatalk 2
Click to expand...
Click to collapse
the phone go direct to frimware update how i can use pushbullet in this mode?
anasmilan said:
i moved the build prop file to platform-tools file in sdk and i try go to command prompt with shift and Type this command
adb shell
su
stop
mount -o rw, remount /system
push build.prop /system/build.prop
tell me push: not found
see the pic
and i try the flash tools with the same tot & dll
the flash tools error
read model is deffrent
Click to expand...
Click to collapse
I wrote a script, it should be easier now.
Put build.prop into the Puuuuush folder and run PUSH_BUILD.PROP
EDIT: Sorry, I told you the wrong commands. it should be fixed now with this tool.
Remorcer said:
I wrote a script, it should be easier now.
Put build.prop into the Puuuuush folder and run PUSH_BUILD.PROP
EDIT: Sorry, I told you the wrong commands. it should be fixed now with this tool.
Click to expand...
Click to collapse
Does it work if i can only power on the phone in download mode?
I have my phone soft bricked because of a corrupted build.prop and i need to replace it.
anasmilan said:
the phone go direct to frimware update how i can use pushbullet in this mode?
Click to expand...
Click to collapse
my bad, I thought you were just looking to transfer the file
unless I've missed something you can't do ADB in recovery or download mode. which has always seemed stupid to me.
you'll need to use ODIN to flash the rom again
screwyluie said:
my bad, I thought you were just looking to transfer the file
unless I've missed something you can't do ADB in recovery or download mode. which has always seemed stupid to me.
you'll need to use ODIN to flash the rom again
Click to expand...
Click to collapse
ODIN is for samsung phones.
After I modified the build.prop file I forgot to change the file rights and now it is stuck on a black screen with the led on green/blue
I have a backup of the original file on the SD.
The phone can get into download mode.
I have already tried the factory reset but nothing.
I have tried the unroot metod from the post:
http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827
But I got this message:
PID: BS02S140706002625
IMEI:
Model: D850
DLL: D850
BIN: LGD850AT-01-V10D-310-410-JUN-19-2014+0
SWV: LGD850AT-00-V10D-310-410-JUN-19-2014+0
SWOV: LGD850AT-00-V10D-ATT-US-JUN-19-2014+0
Device Model is different!
Check Phone or DLL!
My phone model is the AT&T LG G3 32Gb D850 Metalic Black
Please, can someone helpme?
I am desperate!
Sorry I'm a Samsung guy, lg tool or whatever it is.
There is a file from the g2 that makes it so the model doesn't matter you'll need that
Sent from my LG-D850 using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=2827381
You mean this file
Same thng happened to me
Ok i edited the build.prop, apparently I did something wrong, I can only boot to black screen with blue/green flashing led. I did back up my original build.prop, and I can get phone into download mode....just not sure what to do from here. I am using a mac, but I can get to a PC if needed. Any help would be GREATLY appreciated.
DIRKxxxDIGGLER said:
Ok i edited the build.prop, apparently I did something wrong, I can only boot to black screen with blue/green flashing led. I did back up my original build.prop, and I can get phone into download mode....just not sure what to do from here. I am using a mac, but I can get to a PC if needed. Any help would be GREATLY appreciated.
Click to expand...
Click to collapse
I'm really desperate, anyone that can help me get my phone back up I would really appreciate it....just get it back to stock or anything. I am willing to donate to anyone that can help me get my phone up. I know I'll get ripped apart for messing with my phone that was above my ability, I have learned my lesson I understand, just need help please. Thanks for anyone that can get me back up.
DIRKxxxDIGGLER said:
I'm really desperate, anyone that can help me get my phone back up I would really appreciate it....just get it back to stock or anything. I am willing to donate to anyone that can help me get my phone up. I know I'll get ripped apart for messing with my phone that was above my ability, I have learned my lesson I understand, just need help please. Thanks for anyone that can get me back up.
Click to expand...
Click to collapse
Woot! got it fixed!
How did you end up fixing it?
Sent from my LG-D850 using XDA Free mobile app
I have a clockworkmod file in the root of sdcard. I can see it in ES File Explorer but I cannot see it when I connect the phone to my computer. I use clockworkmod recovery only by booting into it when I need to...not by flashing it.
Although it dissappears when I delete it in ES File Explorer, if I refresh the screen it is still there. Anyone know what this file is exactly and how to get rid of it for good?
I tried another app called File Manager by Gira.me. It shows this file as ...
Path: /storage/emulated/0/clockworkmod
Type: */*
Size: 0 B
Last modified: Unknown
Permissions: ---
MD5: Unknown
When I try to delete it it says "Not enough permissions". There must be some way to delete this file.
Boot cwm, adb shell, rm the file
beekay201 said:
Boot cwm, adb shell, rm the file
Click to expand...
Click to collapse
I get the same message in adb shell "permission denied". I finally got rid of this by flash booting into TWRP. The file manager included allowed me to delete the clockworkmod folder. However, there was now also a TWRP folder so I deleted that one also before rebooting the system.
Thanks for the suggestion.
xda6969 said:
I get the same message in adb shell "permission denied". I finally got rid of this by flash booting into TWRP. The file manager included allowed me to delete the clockworkmod folder. However, there was now also a TWRP folder so I deleted that one also before rebooting the system.
Thanks for the suggestion.
Click to expand...
Click to collapse
Stuff like this happens when recoveries (or anything that stores files on your SD), puts files in the wrong place. CWM is doing it because it's designed for Jellybean systems.
It's time to move on to TWRP.
Aerowinder said:
Stuff like this happens when recoveries (or anything that stores files on your SD), puts files in the wrong place. CWM is doing it because it's designed for Jellybean systems.
It's time to move on to TWRP.
Click to expand...
Click to collapse
I like TWRP better now but it did the same thing. After leaving Recovery, when I looked at the contents of the sdcard in a File Manager, I had a 0 byte folder that I couldn't delete. I was then forced to boot back into TWRP and delete from there. I wish these recoveries would clean up after themselves when you exit them.
xda6969 said:
I like TWRP better now but it did the same thing. After leaving Recovery, when I looked at the contents of the sdcard in a File Manager, I had a 0 byte folder that I couldn't delete. I was then forced to boot back into TWRP and delete from there. I wish these recoveries would clean up after themselves when you exit them.
Click to expand...
Click to collapse
There isn't anything to clean up, TWRP makes that folder because that's where it stores nandroids.
Try this in a terminal emulator:
su
restorecon -FR /data/media/0/*
Reboot into recovery to recreate TWRP folder, then see if you can delete from Android.
Aerowinder said:
There isn't anything to clean up, TWRP makes that folder because that's where it stores nandroids.
Try this in a terminal emulator:
su
restorecon -FR /data/media/0/*
Reboot into recovery to recreate TWRP folder, then see if you can delete from Android.
Click to expand...
Click to collapse
Do you need to be rooted for that? If you don't, the next time it happens I will try it but it's clean now so I will leave it as is. Can a nandroid backup be used just to restore app data? I don't flash custom recoveries, I just boot into them. I would boot into TWRP, do a Nandroid of my app data, then copy the contents of the TWRP folder to my PC. Then I could do a complete wipe of the phone, recreate the TWRP folder, put the Nandroid backup in it, install the apps and restore their data.
xda6969 said:
Do you need to be rooted for that? If you don't, the next time it happens I will try it but it's clean now so I will leave it as is. Can a nandroid backup be used just to restore app data? I don't flash custom recoveries, I just boot into them. I would boot into TWRP, do a Nandroid of my app data, then copy the contents of the TWRP folder to my PC. Then I could do a complete wipe of the phone, recreate the TWRP folder, put the Nandroid backup in it, install the apps and restore their data.
Click to expand...
Click to collapse
Yes, you need to be rooted for restorecon command (su). A lot of people had troubles like yours when they moved to Lollipop (me too). Now that the recoveries have been updated, it's no longer an issue for most. You may still need to run the command, though. I suppose if you did a full wipe in stock recovery, it would fix the problem.
Your question about restoring app data with nandroid is vague and could be answered in a few ways. With your issue, the data partition is actually where the problem is, so I wouldn't recommend restoring the partition.
Instead, you might use Titanium Backup or something similar to back up only app data. But you need root for that.
Easiest solution is to root, fix issue, then, if you really want to, unroot. Don't need to wipe anything.