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?
Related
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
I've got myself into quite a predicament. I replaced the build.prop on my kyocera torque with what should have been an exact copy of the original. However, now the phone 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 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 but I don't know if that's helpful.
Does anybody know a way I may be able to push a new build.prop file to my phone? Or a way that I could access the file system on the phone to build a system image from my system file with the correct build.prop? Or could someone just send me a system.img? This is my primary phone so any help would be very much appreciated.
Thanks,
Allan
After trying and trying and failing, I have finally figured out a way to port a rom to the Cube T7.
This has proven the only method (in my experience) to work. All the standard methods have failed
each time.
WARNING!!!!! THIS COULD BRICK OR DAMAGE YOUR PHONE
YOU ARE TRYING THIS AT YOUR OWN RISK. I WILL NOT BE HELD RESPONSIBLE
FOR WHAT HAPPENS TO YOUR DEVICE!!!!
Things you need.
latest Spftool
and the Rom package
NOTE:You need to know that you can't just flash the package I put together. You will
need to use the TWRP recovery that comes in the package to transfer file from your external sd to
the system folder and so forth. Also the proper permission to set.
Step 1: Flashing the images.
I've already pulled the correct img from each folder and put it together for you.
The only thing that you will need to do is extract the folder and use the spf tool to
install the firmware.
Note** In order to keep the 3.97 app storage, I've had to make sure to use the
Spf tool to do a full format except for the bootloader.
Step 2: Repairing the Rom
In the rar package, I included all the files need to fix the rom so
it will work smoothly on your phone. The files can be located in
the "system" folder which will need to be copied to your external sdcard
At this point you will already have flash the images and turn on the phone.
You will notice that the after you turn it on, you will get a warning that says "Cpu overheating"
or at least to that affect. This is not true by the way, this is from the fact the tp settings are off
from the original rom. Either way the warning will force boot your phone which again is fine.
Once this happens you will need to go to recovery.
Once in recovery make sure that you go ahead and mount your
system partition.
With this done you will be able to go to /system/etc/.tp
This folder contains the files that control the thermal manager for
the rom. You want to delete this folder. YES DETELE IT!!!
Once deleted, go to the system folder that you should have copied to your
external Sdcard. You need to copy /system/etc/tp to the exact location that you
just deleted the original.
Once you've done this you will need to set the permissions for the folder and the
files contained. The folder needs to be set to 0755 and the files inside need to be set to 0644.
Once done its best to go ahead and use the recovery to flash UPDATE-SuperSU-v2.46.zip to root your device before
restarting. Once restarted you will need to use root explorer or es explorer root function to
copy all the files to there correct locations and set their permissions. Each file is in its corresponding
folder as it should be in the system partition. All you will need to do is copy and past from the folder on the external and
paste to the same folder in the system partition. For those that may not know, all files will be set to 0644/rw--r--r-- and folders that you copy over will be 0755/rwxr-xr-x (if your using root explorer, just un check the group and others on the "Write" permissions.
Whats not working?
I can't figure out how to get the camera to working.
I've used standard tuts to try and copy the right files or libs
but not luck as of yet. If anyone figures out a way please share!!!
Also, if you have the fold case, the screen does not come on when you
open the fold. Also when double tapping the screen, this does not take it out of sleep
mode. From what I've seen those are the only things that dont work. If you see something
else, please report it to this thread.
Also in the package you will find the Carliv 3.3 recovery version for our phone.
Thanks to kushyree from needrom.com for building it for us.
He also has been assisting me in trying to port other roms to our phone. We owe him a lot of thanks.
Let me know if you guys need any help with this. I will do the best I can to try and help out. Enjoy.
I'm currently trying to change my system sounds on my phone. Any time I copy any files into the System folder my phone reboots. This happens even in TWRP. I would like to replace my Charger_Connection.ogg but am at a wall I can't find a work around to on google. Is there any way to prevent my phone from resetting in order to successfully copy to the System folder? My phone is currently rooted with TrapKernel. Any help would be appreciated.