Hi,
I tried the trickdroid ROM but i dont see any benefits, instead there are downsides, like wifi disconnecting and so on. I would like to go back to the original Stock ROM but i do not have the boot.img and nandroid does not back it up along with my backup. Without it, my wifi does not work.
Where can i get this boot.img, or can someone give it here? Thanks!
onlinechi said:
Hi,
I tried the trickdroid ROM but i dont see any benefits, instead there are downsides, like wifi disconnecting and so on. I would like to go back to the original Stock ROM but i do not have the boot.img and nandroid does not back it up along with my backup. Without it, my wifi does not work.
Where can i get this boot.img, or can someone give it here? Thanks!
Click to expand...
Click to collapse
http://www.4shared.com/file/k-UJs2Eo/RUU_VILLEC2_U_ICS_40_hTC_Asia_.html?aff=7637829
You can try this stock. by the way , I'm using Trickdroid V1.0,I do not have WiFi problem at all.You have to manually flash the boot img using fastboot.
i have strange problems where my 3g or wifi will stop connecting on TD. Even if i go to airplane mode it does not recover. I have to reboot phone. But last time i did not do a backup of my boot.img.. thats why i need it now
Is it possible that i just get the boot.img instead of downloading the whole giant file? thanks!
onlinechi said:
Is it possible that i just get the boot.img instead of downloading the whole giant file? thanks!
Click to expand...
Click to collapse
RUU file is a install script setup launcher where you can install onto your window then connect your phone to usb , execute this file , then follow the instruction on the screen . I do not have the boot img.
onlinechi said:
Is it possible that i just get the boot.img instead of downloading the whole giant file? thanks!
Click to expand...
Click to collapse
Possible to extract only the boot.img but not without downloading the whole big file.
Open the .exe and make sure that it fully started.
Don't click anything, just go to windows icon and search for %temp%.
You will now find some folders, just search through these folders for the ROM.zip.
If you found it, you can copy it to your desktop or somewhere else.
Extract it with WinRar,7-zip or something like that and take the boot_signed.img.
Now copy the two files into the folder where the fastboot.exe is placed (if you have installed the Android SDK, it should be in platform-tools)
Plug in your One S, go into the bootloader and go into fastboot mode.
Navigate with the cmd in the folder with the fasboot.exe and the two .img's.
Now type in that:
Code:
fastboot flash boot boot_signed.img
-----------------
This was copied from a thread in One X made by Setsuna666 and pasted there from user: torxx (http://forum.xda-developers.com/showthread.php?t=1609190), but applies for any RUU file extraction. It is not from me, but this method works.
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?
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
So I changed the boot animation to something different. The animation is so heavy the phone lags halfway in between and now my phone can't even get past the boot animation screen. It's stuck at the boot animation. Anyway to revert this?
Download the default boot animation from here: http://forum.xda-developers.com/google-nexus-5/themes-apps/bootanimation-nexus-5-animations-t2789918
Scroll down a bit and you'll find the default Lollipop animation. Download the zip which is supposed to be manually installed.
Put it in system/media/bootanimation.zip
You can use Aroma File Manager for this. AromaFM is a flashable zip which brings up a file manager in your recovery
experience7 said:
Download the default boot animation from here: http://forum.xda-developers.com/google-nexus-5/themes-apps/bootanimation-nexus-5-animations-t2789918
Scroll down a bit and you'll find the default Lollipop animation. Download the zip which is supposed to be manually installed.
Put it in system/media/bootanimation.zip
You can use Aroma File Manager for this. AromaFM is a flashable zip which brings up a file manager in your recovery
Click to expand...
Click to collapse
I can't even access my phone's storage so how am I suppose to use the zip? Are you saying I can flash the zip file while the phone is in fastboot/recovery?
If you're using TWRP as a recovery you can access your storage. It does support MTP.
Yeah, the file manager has to be flashed just like a ROM.
experience7 said:
If you're using TWRP as a recovery you can access your storage. It does support MTP.
Yeah, the file manager has to be flashed just like a ROM.
Click to expand...
Click to collapse
And that's the problem. I'm running a stock rom (4.4.2) with no TWRP or CWM.
The phone is rooted and the boot-loader is unlocked.
Bootloader unlocked. So where's the problem?
Download latest TWRP and execute
fastboot flash recovery twrp.img
to flash it.
Or simply
fastboot boot twrp.img
to launch it once. You don't even need to flash it.
experience7 said:
Bootloader unlocked. So where's the problem?
Download latest TWRP and execute
fastboot flash recovery twrp.img
to flash it.
Or simply
fastboot boot twrp.img
to launch it once. You don't even need to flash it.
Click to expand...
Click to collapse
AYEEEEE!!! I see where you're going with this now. I think I get it now. I'll try tonight or maybe in a couple of hours and then I'll come back if any problems. Once finished I'll let you know with a thanks
By the way: After copying the new (default lollipop) bootanimation.zip to /system/media do a 'fix permissions' in TWRP. Not quite sure if the option is available in TWRP but if it is, just do it. It won't do any harm
Alright I flashed TWRP and it's working but the file manager kinda sucks. I mean it's picking up the files and their aren't any options to copy and paste. The boot animation is stored in /system/media and when I go into the system folder all I see is "bin" and nothing else. I don't understand what's the problem
Man, the file manager does not suck. A little more respect to the developer! You should be thankful, not disrespectful!
Enable hidden files in the file manager and you'll see them. And it also does provide copy/paste functionality. I've used it several times.
EDIT: If you still don't see them after enabling hidden files you have to mount the system partition.
experience7 said:
Man, the file manager does not suck. A little more respect to the developer!
Enable hidden files in the file manager and you'll see them. And it also does provide copy/paste functionality. I've used it several times.
Click to expand...
Click to collapse
I searched everywhere and I don't see an option to enable hidden files. How did you enable hidden files?
It's in the lower right corner if I remember correctly. Three dots which will bring up a menu.
...
experience7 said:
It's in the lower right corner if I remember correctly. Three dots which will bring up a menu.
Click to expand...
Click to collapse
What version of TWRP are you using? I don't see three dots anywhere. The bottom always has a back button on the right, a button to launch terminal in the center and a home button on the left
Dude. It has nothing to do with TWRP version at all. You didn't even launch Aroma File Manager... that's the point.
Read my previous posts again, take your time & don't double post (there's an option to edit if you have to).
experience7 said:
Dude. It has nothing to do with TWRP version at all. You didn't even launch Aroma File Manager... that's the point.
Read my previous posts again, take your time & don't double post (there's an option to edit if you have to).
Click to expand...
Click to collapse
Sorry for being impatient.
Do I flash Aroma the same way I flashed TWRP? If so will this cause any problems or anything? TWRP can't install Aroma from SD because my computer won't even pick up my phone
If you're in TWRP, connect your phone to your computer. It should be detected just like any Android phone since it's also using MTP.
Aroma File Manager has to be flashed in TWRP (install zip). That's why you had to flash TWRP in the first place.
experience7 said:
If you're in TWRP, connect your phone to your computer. It should be detected just like any Android phone since it's also using MTP.
Aroma File Manager has to be flashed in TWRP (install zip). That's why you had to flash TWRP in the first place.
Click to expand...
Click to collapse
Better yet as soon as I connected my phone to my PC, TWRP's file manager started working. I deleted the corrupted bootanimation.zip that made my phone lag in the first place. However it keeps failing to move the other bootanimation.zip into /system/media (I backed up the stock boot in /system/media by renaming it
EDIT: Never-mind I got it. I renamed the file from 0bootanimation.zip to "android" and then to bootanimation.zip
I restarted my phone and it's just stuck in the boot loop. The animation is occurring forever and nevermind it just started.
Thank you experience7!!! Massive vouch for you man. You saved me so much trouble. Much love from me =D
As said before... TWRP uses MTP to enable file transfer between your computer and your phone. However, you'll only see your internal storage (pictures, videos and stuff like that) - not the system partition. That's why you should use Aroma File Manager! It lets you access the system partition directly on the phone and provides everything you need (copy/paste/delete and so on).
I have no idea what file you actually deleted. But I'm pretty sure it was not the one in /system/media.
experience7 said:
As said before... TWRP uses MTP to enable file transfer between your computer and your phone. However, you'll only see your internal storage (pictures, videos and stuff like that) - not the system partition. That's why you should use Aroma File Manager! It lets you access the system partition directly on the phone and provides everything you need (copy/paste/delete and so on).
I have no idea what file you actually deleted. But I'm pretty sure it was not the one in /system/media.
Click to expand...
Click to collapse
And that's the most weird part of all...
1) TWRP file manager started working as soon as I connected my phone to my PC. I didn't need to flash AromaFM. TWRP worked like a charm
2) I deleted the laggy bootanimation.zip and replaced it with the stock one I backed up. I backed up the stock animation by renaming it to a different file. However TWRP always failed to rename the stock animation to bootanimation.zip. So I renamed it entirely different (to android) and then back to bootanimation.zip and it worked like a charm.
Does that make sense now? I don't know what the hell just happened but I ain't complaining
Hi guys,
I was testing and editing build.prop file on my phone and something strange happened!.
I just rebooted the phone just to test if my edited build was showing and the next thing you know upon reboot my pattern and fingerprint locks weren't recognized, as if someone had changed them, I was like WHAT THE HELL! Even my backup pin wasn't working. I didn't now messing up with build.prop could do such a thing! :laugh:
Fortunately, I had a backup of my prop file in my downloads folder BUT I couldn't restore it using TWRP manager and couldn't see ROOT Files on my Windows PC. I tried many root explorers for PC but they didn't show the root files.
In the end, I managed to use ADB Commands push/pull to do the job and THANK GOD it worked, I got my build.prop restored! :victory:
REMEMBER:
1. ALWAYS BACKUP BUILD.PROP if you are going to mess with it.
2. ALWAYS HAVE DEBUGGING MODE ENABLED in developer options, so you could workaround with the files using ADB commands (I had that enabled already ).