Dear All,
First thankyou so much for the great forum we have here, I am using Huawei Ideos u8150, the fone is network locked so I played around, being a total noob I started with installing sdk, and rooted my fone using z4root, rooting was successful
No when I try to copy a modified build.prop to the systems folder in root explorer, the file is copies but is not visible, also I have deleted the original build.prop & I am afraid to reboot the fone,
can restoring the fone to factory settings solve this ? also how come I copy the file to system folder, it gets copied and I still cant see it ?
I have tried pushing the file using ADB command line but the device refuses to mount (persmission denied)
I would really be thankful to anyone who can guide a noob like me, if you dont this forum has enough reasons to love it already,
cheers !
cknaveed said:
Dear All,
First thankyou so much for the great forum we have here, I am using Huawei Ideos u8150, the fone is network locked so I played around, being a total noob I started with installing sdk, and rooted my fone using z4root, rooting was successful
No when I try to copy a modified build.prop to the systems folder in root explorer, the file is copies but is not visible, also I have deleted the original build.prop & I am afraid to reboot the fone,
can restoring the fone to factory settings solve this ? also how come I copy the file to system folder, it gets copied and I still cant see it ?
I have tried pushing the file using ADB command line but the device refuses to mount (persmission denied)
I would really be thankful to anyone who can guide a noob like me, if you dont this forum has enough reasons to love it already,
cheers !
Click to expand...
Click to collapse
Moderators if by any chance I have placed this query in the wrong part of forum, please let me know in which part I should raise it, thanks !
In the top right hand corner or left it should be a r/o button. If you push that to r/w which is read/write you will be able to copy the bp correctly. Don't forget to mount as r/o which is read only before you exit RE. Then reboot. If you made a backup which you should have done before modding the bp you will be ok to reboot. If anything goes wrong just do a restore. Also you can Redownload the current rom your on to your cpu. Then extract it to a folder on your desktop. Then browse threw all the folders untill you see the stock build prop. Copy&paste it to your sd and that's your stock build prop. Hope this helps. Good luck
#Root/Hack_Mod-Always®
laie1472 said:
In the top right hand corner or left it should be a r/o button. If you push that to r/w which is read/write you will be able to copy the bp correctly. Don't forget to mount as r/o which is read only before you exit RE. Then reboot. If you made a backup which you should have done before modding the bp you will be ok to reboot. If anything goes wrong just do a restore. Also you can Redownload the current rom your on to your cpu. Then extract it to a folder on your desktop. Then browse threw all the folders untill you see the stock build prop. Copy&paste it to your sd and that's your stock build prop. Hope this helps. Good luck
#Root/Hack_Mod-Always®
Click to expand...
Click to collapse
thanks for the kind help, I have tried doing that, I have rooted it, the I click on the r/o button and then I did copy the new built.prop to systems folder, the copying process completes, doesnt report any error but still there is no file visible by the name of built.prop, I just cant find it, is it hidden ? or is it not being copied in the first place ? & thanks I would try to extract the stock built.prop, and copy it to the folder but I will do it as a last option till I dont find something else,
thanks a million for the help, would apprciate if you can point it what I am doing wrong
I just applied Daoist's CWM stock ROM update (should still be rooted, right?). It came up first time.
Then, I modded my build prop (set dpi to 120 because I like it that way). But maybe I screwed up the file name in Root explorer, because now I'm in a boot loop and if I try ADB PULL /system/build.prop it says "file not found."
I can't get SU through adb, so can't push build.prop to /system. ADB remount returns an error. permission denied. Transformer won't boot, so I can't do anything from it.
I CAN get to cwm, and have been trying to create an update.zip that will just copy build.prop to /system, but everything I have tried quits with "install aborted" message.
What can I do?
restore a nand and dont try and **** with it again, lol. no but really, restore a nand and then copy your build. prop and make a flashable zip and place on your sd card in case it happens again, so you can just flash it in cwm.
Resolved..
Well, why go back when you can go forward?
I went ahead and installed the Prime ROM. Looks like it is eating all my currently installed apps.
Y'all should know, though, that if your system can't find a build.prop it won't start. You can ADB to it and have a rudimentary set of commands, but your ability to significantly alter anything in your file system will be prohibited.
Lesson learned.
glg
as a side note most editors in android rename system files when you change them to "nameoffileyouedited".bak so if you pull and rename that file that might have fixed your problem. also try lcd dencity changer from the market. its a little less hazordous
mrevankyle said:
as a side note most editors in android rename system files when you change them to "nameoffileyouedited".bak so if you pull and rename that file that might have fixed your problem. also try lcd dencity changer from the market. its a little less hazordous
Click to expand...
Click to collapse
That is true. I had backups. But without a build.prop, the virtual machine won't start. There is no way to do a file operation to replace the backup. At least none that I found. I had to flash the whole system.
glg
HELP!
Ive screwed up my phone.
I played around with the build.prop file and now it wont boot.
Ive learned how to use SDK and ADB, but even with the computer detecting the device and all correct drivers installed (the device manager even lists the device in when its in fastboot mode)
I cant get ADB or Fastboot to see the device. The only mode I can use it fastboot, when I try to boot normally, it just loops.
I have a backup of my origional build.prop file, but I cant access the system directory in the phones root dir.
What can I do?
Thanks.
I have the same problem with my kindle fire. I messed with the build.prop, and it wont boot. Have you figured out how to restore the build.prop?
Can you get into recovery?
If so just reflash your ROM through there, if you flash the same zip then everything will stay the same and replace your build.prop with the original one
kiwiscole said:
HELP!
Ive screwed up my phone.
I played around with the build.prop file and now it wont boot.
Ive learned how to use SDK and ADB, but even with the computer detecting the device and all correct drivers installed (the device manager even lists the device in when its in fastboot mode)
I cant get ADB or Fastboot to see the device. The only mode I can use it fastboot, when I try to boot normally, it just loops.
I have a backup of my origional build.prop file, but I cant access the system directory in the phones root dir.
What can I do?
Thanks.
Click to expand...
Click to collapse
also if you want you can open the zip reflash the rom and get the build.prop and overwrite ... a little more complex but functional
Hi, I've just made an Online Nandroid backup of my stock rom. It's stored in the clockworkmod folder located on the internal storage, but whenever i try to copy it from that folder to my PC, it just pastes a folder named "35", which contains no files. I have no idea why it's doing this!
Help please?
B0B0D said:
Hi, I've just made an Online Nandroid backup of my stock rom. It's stored in the clockworkmod folder located on the internal storage, but whenever i try to copy it from that folder to my PC, it just pastes a folder named "35", which contains no files. I have no idea why it's doing this!
Help please?
Click to expand...
Click to collapse
What if you do?
Code:
adb pull /sdcard/clockworkmod
deej_roamer said:
What if you do?
Code:
adb pull /sdcard/clockworkmod
Click to expand...
Click to collapse
I'm having the same problem as the OP. I made a nandroid backup using clockworkmod and I can't figure out how to get it off the Moto G and onto my computer. The above adb command just brings over two files: .recovery_version and .last_install_path.
The nandroid backup does not seem to be placed on the emulated sdcard. I can find it by using the Rom Toolbox root browser. It is in /data/media/clockworkmod/backup.
But that directory is not visible when I connect the phone via usb. I try:
E:\install\Moto G Tools\MotoG-Tools>adb pull /data/media/clockworkmod/backup
and get:
remote object '/data/media/clockworkmod/backup' does not exist
Any ideas on how I can get the backup onto my PC?
Hello guys, proper path should be as below:
adb pull /mnt/shell/emulated/clockworkmod/backup /designated/folder/for/backup/backup.date
JP
just use a file explorer like es and move your backup to somewhere that is visible from your comp and then just copy it over .
quizmaniac said:
just use a file explorer like es and move your backup to somewhere that is visible from your comp and then just copy it over .
Click to expand...
Click to collapse
I tried that. With an 8GB Moto G I'm lucky to have enough space for one copy of the nandroid backup. When I tried to move the directory, it runs out of memory - I guess it is actually copying and deleting. I could try moving each file individually, but that is tedious and error prone and I could still run into the space problem.
---------- Post added at 11:40 PM ---------- Previous post was at 11:27 PM ----------
pacmanman said:
Hello guys, proper path should be as below:
adb pull /mnt/shell/emulated/clockworkmod/backup /designated/folder/for/backup/backup.date
JP
Click to expand...
Click to collapse
Thanks. That worked.
Would u please give proper instruction on how to do it, my nandroid backup seems hidden when I open it on pc
First time when I have a problem like this, I see the backup on phone but when I conect the phone to PC I can't find it. So, I use Total Commander and move the backup file in phone in other folder, like "download". After that I seen it to PC. Now, I use TWRP 2.8.7 and I make the backup to an OTG connected USB stick. It's simple after that to move the backup where I want.
G0rg0ne said:
First time when I have a problem like this, I see the backup on phone but when I conect the phone to PC I can't find it. So, I use Total Commander and move the backup file in phone in other folder, like "download". After that I seen it to PC. Now, I use TWRP 2.8.7 and I make the backup to an OTG connected USB stick. It's simple after that to move the backup where I want.
Click to expand...
Click to collapse
I try ur method, but seems not working either,
Im using philz last version. Installing total commander and
I got this message
You give root rights to Total Commander?
G0rg0ne said:
You give root rights to Total Commander?
Click to expand...
Click to collapse
Yes,
Could it be because the su or the recovery?
I use TWRP, but you must find it in this location: /storage/emulated/0/clockworkmod/backup/backup.date. If you not, you can try the adb command described by
pacmanman said:
Hello guys, proper path should be as below:
adb pull /mnt/shell/emulated/clockworkmod/backup /designated/folder/for/backup/backup.date
JP
Click to expand...
Click to collapse
or, you can try another file manager, like ES or RootExplorer
You know how to use ADB commands?
G0rg0ne said:
I use TWRP, but you must find it in this location: /storage/emulated/0/clockworkmod/backup/backup.date. If you not, you can try the adb command described by
or, you can try another file manager, like ES or RootExplorer
You know how to use ADB commands?
Click to expand...
Click to collapse
Already try that app & didn't work.
I'm trying to use same method as this (using adb) but I can't seem find proper instruction or sample on how to do it - at least easy way
Can u help me give instruction (with capture if u may) or at least pointing me to thread that discuss this.
Thx
First, you may have motorola drivers installed on your PC. You can find them from here.
Another thing you need is Fastboot. Unzip fastboot on your desktop on a folder.
Charge your device above 60% battery level to avoid shutdowns during the process.
Enable USB Debugging on your phone from Settings> Developer options. If you do not find Developer option under device settings, enter to settings/about phone and touch "Build number" 7 times to enable them.
Conect your phone via USB to PC.
Open folder where you have fastboot, right click it and open a comand prompt from there
In the comand prompt enter:
adb devices
now you will see if all is ok and your device has been recognized. You should see something like:
List of devices attached
random numbers and letters device
If not, probably don't have the drivers installed properly OR you failed to authorize your computer for USB debugging.
Now you can enter adb commands in terminal and pull your backup from your phone. Commands will be something like:
adb pull /mnt/shell/emulated/clockworkmod/backup /designated folder for backup/backup.date
You can learn more about Backup with ADB from Here
G0rg0ne said:
First, you may have motorola drivers installed on your PC. You can find them from here.
Another thing you need is Fastboot. Unzip fastboot on your desktop on a folder.
Charge your device above 60% battery level to avoid shutdowns during the process.
Enable USB Debugging on your phone from Settings> Developer options. If you do not find Developer option under device settings, enter to settings/about phone and touch "Build number" 7 times to enable them.
Conect your phone via USB to PC.
Open folder where you have fastboot, right click it and open a comand prompt from there
In the comand prompt enter:
adb devices
now you will see if all is ok and your device has been recognized. You should see something like:
List of devices attached
random numbers and letters device
If not, probably don't have the drivers installed properly OR you failed to authorize your computer for USB debugging.
Now you can enter adb commands in terminal and pull your backup from your phone. Commands will be something like:
adb pull /mnt/shell/emulated/clockworkmod/backup /designated folder for backup/backup.date
You can learn more about Backup with ADB from Here
Click to expand...
Click to collapse
OK, thx u I'll try as soon as I got free time,
One more question, should I connect my phone on recovery or normal condition ?
In "normal" mode , but not forget to enable USB debugging.
G0rg0ne said:
In "normal" mode , but not forget to enable USB debugging.
Click to expand...
Click to collapse
Hello Forgone, I try ur suggestion.
But seems doesn't work, have I did wrong
My phone detected but when I try adb pull, it shows this messages
You not give the right command to pull out. After "...clockworkmod/backup/" you must enter the backup name not the path where to download. It will download to adb folder. The name of backup file could be, how it suggest @pacmanman something like "backup.date" (where date is the date you make it). Sry, but you must find the name of that backup file or at least guess it.
G0rg0ne said:
You not give the right command to pull out. After "...clockworkmod/backup/" you must enter the backup name not the path where to download. It will download to adb folder. The name of backup file could be, how it suggest @pacmanman something like "backup.date" (where date is the date you make it). Sry, but you must find the name of that backup file or at least guess it.
Click to expand...
Click to collapse
Gorgone, if its not to much, can u give screenshot on how u do it?
I'm confused
Look at your picture. As you see in green what you do till here was good. Your device is recognize. Now, what I underlined with yellow was not OK. There you must put your Backup file NAME. The name is usual something like "backup.date" where date means the date you made the backup. It's nothing to do if you don't know that name, so at least try to guess it.
I use TWRP so my path will be a little different. TWRP is better for make and restore backups, you can even make a backup on an USB stick on OTG, so you don't ocupie the internal memory space, also you can easy move it where do you want.
I've got myself into quite a predicament. I was trying to install a dictionary for a 4.4 keyboard on my 4.1.2 torque, and in doing so I found that I may want to change the build.prop. Before I even reboot the device I see that that would only work if I were installing through the market, and so I replace the build.prop with an exact copy of the original file. I reboot and then the device will not boot. I guess something must have gone wrong with es explorer. I do not know how to fix the build.prop file because 1. I can't find the file available online yet and 2. this phone has no recovery, so I cannot access it through adb. I can however access it through fastboot when I put it in fastboot mode. This phone also has a download mode I magically got into, but it cancelled itself out after 10 seconds and I don't know how to get back into it or what purpose it would serve.
Does anybody know a way I may be able to push a new build.prop file to my phone? Perhaps I could use the fastboot flash command if I could find the build.prop info? This is my primary phone so any help would be very much appreciated.
Thanks,
Allan
I got the build.prop backup off my sd card, but I still don't know how to push it. Would it be possible to get a copy of the system partition through fastboot, inject the build.prop into it, then reflash? Wouldn't that just be doing the same thing that got me into this mess though?